Use this page to create a new proxy server. The proxy server is responsible for routing HTTP requests and caching content from backend servers.
To view this administrative console page, click Servers > Proxy Server > New
The following settings are configured within the wizard that appears in this console page.
You must select a node, which your proxy server will occupy.
Only Network Deployment nodes will appear in the selection list. A proxy server can reside only in a Network Deployment node.
Specifies a logical name for the proxy server. For WebSphere Application Server, server names must be unique within a node.
The name field is required and is a user defined field. The name field cannot contain the following characters: # \ / , : ; " * ? < > | = + & % ' The name defined must be unique among proxy servers in a cluster and cannot begin with a . or a space. A space will not generate an error, but leading and trailing spaces will be automatically deleted.
This field allows you to select an application server template upon which to model the servers for the new proxy server. You may select a default template, or you can choose to map an existing application server.
Mapping preexisting proxy servers can be a great 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.
If you are creating multiple proxy servers in the same node, then you will want to be sure and select the option to generate unique ports.
There are certain advanced scenarios pertaining to port mapping that may require unique ports. For example, a load balancer can load balance requests to the proxy servers within the same node assuming each proxy server is listening on a unique HTTP port.
Related reference
Administrative console buttons
Administrative console page features
Administrative console scope settings
Administrative console preference settings
Object names