This topic provides information to create and configure
a proxy server.
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 WebSphere Application Server Network Deployment, two profiles
are created: a stand-alone application server profile, which is the
default profile, and a deployment manager profile, which is 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.
Procedure
- Create a proxy server in the administrative console by
clicking Servers > Proxy Servers.
- Click New.
- Select the node on which you want the proxy server to reside.
- Enter a name for the new proxy server and click Next.
- The supported protocols HTTP and SIP are
selected for you. Select HTTP if your proxy server will route requests
to and from a Web container. Select Session Initiation Protocol (SIP)
if your proxy server will route requests to and from a SIP container.
Determine whether or not to generate unique HTTP ports by selecting
or clearing Generate unique HTTP ports. Click Next.
Note: If
you create multiple proxy servers on the same node for vertical scaling,
then you might select the option to generate unique ports to avoid
port conflicts. Certain advanced scenarios pertain to port mapping
that might require unique ports. For example, a load balancer can
load balance requests to the proxy servers within the same node, assuming
that each proxy server is listening on a unique HTTP port. For the
proxy server to accept requests for a specific virtual host, it is
necessary to add the unique HTTP ports that are generated to the host
alias of the virtual host. It might also be necessary to modify the
port values that the wizard generates, if these ports conflict with
other local servers on the same node.
- Select a proxy server template on which to base your proxy
server. Click Next. You can select a default template,
or you can choose to map to an existing proxy server.
Tip:
Mapping
to a pre-existing proxy server is a time-saving technique. You can
build one proxy server and apply all of the specific configurations
your environment needs, and then use that proxy server as a template.
- Review the summary panel and click Finish.
Results
You now have a functional proxy server
that automatically routes HTTP requests to the WebSphere Application
Server cell that the proxy server belongs to or SIP requests to and
from a SIP container. To enable routing to another WebSphere Application Server
cell, configure your cell to communicate with other WebSphere Application
Server cells.