Revision: 8914
Author: rhatdocs
Date: Tue Dec 8 17:47:34 2009
Log: [Mobicents][Sip Servlets] Progressive edit of chapters 1, 2
http://code.google.com/p/mobicents/source/detail?r=8914
Modified:
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-SIP_Servlets_Server-Configuring.xml
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-binary-SIP_Servlets_Server_with_Tomcat-Installing_Configuring_and_Running.xml
=======================================
---
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-SIP_Servlets_Server-Configuring.xml
Sun Oct 11 20:47:59 2009
+++
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-SIP_Servlets_Server-Configuring.xml
Tue Dec 8 17:47:34 2009
@@ -4,7 +4,7 @@
<!-- chapter id nickname: bsssc --><section
id="bsssc-binary-SIP_Servlets_Server-Configuring">
<title>Configuring</title>
<para> </para>
- <section id="bsssc-binary-SIP_Servlets_Server-Adding_SIP_Connectors">
+<!--Note - Developer: Should there be content here? Or is a paragraph
being used as a break here?--> <section
id="bsssc-binary-SIP_Servlets_Server-Adding_SIP_Connectors">
<title>Configuring SIP Connectors</title>
<para>SIP Connectors are added in the same way as HTTP Connectors: by
adding a <literal><Connector></literal> element under the
<literal><Service></literal> element in the container's
<filename>server.xml</filename> configuration file.</para>
<para>For example, to add a SIP Connector on the IP address
<literal>127.0.0.1</literal>, on port <literal>5080</literal>, using the
UDP transport protocol, you should insert the following XML element:</para>
@@ -118,7 +118,7 @@
<varlistentry>
<term>staticServerAddress</term>
<listitem>
- <para>Specifies what load-balancer server address is insterted
in Contact/Via headers for server-created requests. This parameter is
useful for cluster configurations where requests should be bound to a
load-balancer address, rather than a specific node address.</para>
+ <para>Specifies what load-balancer server address is inserted in
Contact/Via headers for server-created requests. This parameter is useful
for cluster configurations where requests should be bound to a
load-balancer address, rather than a specific node address.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -134,7 +134,7 @@
</section>
<section
id="bsssc-binary-SIP_Servlets_Server-Configuring_Application_Routing">
<title>Application Routing and Service Configuration</title>
- <para>The application router is called by the container—whether JBoss
or Tomcat—to select a SIP Servlet application to service an initial
request. It embodies the logic used to choose which applications to invoke.
An application router is required for a container to function, but it is a
separate logical entity from the container. The application router is
solely responsible for application selection and must not implement
application logic. For example, the application router cannot modify a
request or send a response.</para>
+<!--Note - Editor: Paragraph sounds wrong :)--> <para>The application
router is called by the container—whether JBoss or Tomcat—to select a SIP
Servlet application to service an initial request. It embodies the logic
used to choose which applications to invoke. An application router is
required for a container to function, but it is a separate logical entity
from the container. The application router is solely responsible for
application selection and must not implement application logic. For
example, the application router cannot modify a request or send a
response.</para>
<para>For more information about the application router, refer to the
following sections of the JSR 289 specification: Application Router
Packaging and Deployment, Application Selection Process, and Appendix C.
</para>
<para>In order to configure the application router, you should edit
the <literal>Service</literal> element in the container's
<filename>server.xml</filename> configuration file:</para>
=======================================
---
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-binary-SIP_Servlets_Server_with_Tomcat-Installing_Configuring_and_Running.xml
Mon Dec 7 23:12:01 2009
+++
/trunk/servers/sip-servlets/sip-servlets-docs/en-US/task-section-binary-SIP_Servlets_Server_with_Tomcat-Installing_Configuring_and_Running.xml
Tue Dec 8 17:47:34 2009
@@ -152,7 +152,7 @@
<title>Setting the <envar>CATALINA_HOME</envar> Environment Variable
on Linux</title>
<step>
<para>The <envar>CATALINA_HOME</envar> environment variable must
point to the location of your Tomcat installation. Any Mobicents server
which runs on top of the Tomcat servlet container has a topmost directory,
i.e. the directory in which you unzipped the zip file to install the
server, and underneath that directory, a <filename>bin</filename>
directory. <envar>CATALINA_HOME</envar> must be set to the topmost
directory of your Mobicents server installation.</para>
- <para>Setting this variable in your personal
<filename>~/.bashrc</filename> file has the advantage that it will always
be set (for you, as a user) each time you log in or reboot the system. To
do so, open <filename>~/.bashrc</filename> in a text editor (or create the
file if it doesn't already exist) and insert the following line
anywhere in the file, taking care to substitute
<filename><mobicents_server></filename> for the topmost directory of
the Mobicents server you installed:</para>
+ <para>Setting this variable in your personal
<filename>~/.bashrc</filename> file has the advantage that it will always
be set (for you, as a user) each time you log in or reboot the system. To
do so, open <filename>~/.bashrc</filename> in a text editor (or create the
file if it doesn't already exist) and insert the following lines
anywhere in the file, taking care to substitute
<filename><mobicents_server></filename> for the topmost directory of
the Mobicents server you installed:</para>
<screen>export
CATALINA_HOME="/home/<username>/<path>/<to>/<mobicents_server>"</screen>
<para>Save and close <filename>.bashrc</filename>.</para>
</step>
@@ -184,7 +184,7 @@
</section>
<section id="bssswticar-binary-SIP_Servlets_Server_with_Tomcat-Running">
<title>Running</title>
- <para>Once installed, you can run the Tomcat Servlet Container by
executing the one of the startup scripts in the <filename>bin</filename>
directory (on Linux or Windows), or by double-clicking the
<filename>run.bat</filename> executable batch file in that same directory
(on Windows only). However, we suggest always starting Tomcat using the
terminal or Command Prompt because you are then able to read—and act
upon—any startup messages, and possibly debug any problems that may arise.
In the Linux terminal or Command Prompt, you will be able to tell that the
container started successfully if the last line of output is similar to the
following:</para>
+ <para>Once installed, you can run the Tomcat Servlet Container by
executing one of the startup scripts in the <filename>bin</filename>
directory (on Linux or Windows), or by double-clicking the
<filename>run.bat</filename> executable batch file in that same directory
(on Windows only). However, we suggest always starting Tomcat using the
terminal or Command Prompt because you are then able to read—and act
upon—any startup messages, and possibly debug any problems that may arise.
In the Linux terminal or Command Prompt, you will be able to tell that the
container started successfully if the last line of output is similar to the
following:</para>
<programlisting><