This topic lists the proxy servers in the cell. A proxy server resides within a WebSphere Application Server Network Deployment node. A proxy server is used to classify, prioritize, and route HTTP and SIP requests to servers in the enterprise as well as cache content from servers. On this page you can create, delete, or modify a proxy server.
To view this administrative console page, click Servers > Proxy Servers .
To configure the proxy server to route work to V6 WebSphere Application Servers in another cell, use core group bridge settings (Servers > Core groups > Core group bridge settings), which sets up communication between cells.
Currently, configuring the proxy server to route work to a V6 WebSphere Application Server - Express cell requires advanced configuration.
Both generic server clusters and URI groups are also accessible in the administrative console under Related Items for the proxy server.
Specifies a logical name for the proxy server. For WebSphere Application Server, server names must be unique within a node.
If you have multiple nodes in a cluster, the server names must also be unique within the cluster. You cannot use the same server name within two nodes that are part of the same cluster. WebSphere Application Server uses the server name for administrative actions, such as referencing the server in scripting.
The name of the node where the proxy server resides.
Indicates the WebSphere Application Server version you are running.
Indicates the protocol or protocols that the proxy server is configured to handle.
This is based on the type of transport chains that are configured. If there are transport chains configured that terminate with SIPProxyInboundChannel, then SIP displays. If there are transport chains configured that terminate with HTTPProxyInboundChannel, then HTTP displays. If both types of chains are configured then HTTP,SIP displays.
Indicates whether the proxy server is started, stopped, or unavailable.
If the status is unavailable, the node agent is not running in that node and you must restart the node agent before you can start the server.
Related reference
Generic server cluster members
Routing rules
URI groups