This
topic provides information to create and configure a proxy
server. When creating a proxy server, only the application server
profile
can be used as the target node.
About this task
The proxy server
routes requests to application server nodes.
The proxy server can dynamically route requests to all on-demand configuration
(ODC) enabled application servers without additional configuration.
When
you install the product, two profiles are created: a stand-alone application
server profile, which is the default profile, and a deployment manager
profile,
which is called dmgr. When creating a proxy server, do not choose
the deployment
manager profile. Only the application server profile can be used as
the target
node.
Results
You now have a functional proxy server that automatically
routes HTTP
requests to the cell that the proxy server belongs to or SIP requests
to and
from a SIP container. To enable routing to another cell, configure
your cell
to communicate with other cells.
Avoid trouble: When using the proxy server, one should
use the default port.
If any other port is used, any HTTPS URL redirection might go to the
wrong
port. This is because the virtual host named default_host might also
be using
this new port. The HTTPS redirection is based on the first HTTPS port
that
it finds in the default_host.
gotcha
Avoid trouble: As
the number of SIP containers grow in a deployment, the larger the
heap settings
need to be on the SIP proxy server. For example, a deployment of
20 containers
requires a minimum heap size of 60 MB, so a -Xmo60m parameter should
be added
to the Generic JVM arguments field on the Java virtual machine panel
of the
admin console. However, a deployment of 70 containers requires a
larger value
such as 200 MB (-Xmo200m). See the information center topic
Java
virtual
machine settings for more information about Generic JVM arguments.
gotcha