This topic lists the proxy servers in the cell. A proxy server resides within a WAS Network Deployment node.
A proxy server is used to classify, prioritize, and route HTTP requests to servers in the enterprise as well as cache content from servers. We can use this page to 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.
To configure the proxy server to route work to an application server which is not an IBM WAS or a pre-V6 WebSphere Application Server cell, the following advanced configuration is required:
- Define a generic server cluster. From the administrative console, click Servers > Generic Server Clusters.
- Define a URI group. From the administrative console, click Environment > URI Groups.
- Create routing rules. From the administrative console, click Servers > Proxy Servers > server_name > Proxy Server Properties > Routing rules.
Both generic server clusters and URI groups are also accessible in the administrative console under Related Items for the proxy server.
- Name
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. We cannot use the same server name within two nodes that are part of the same cluster. WAS uses the server name for administrative actions, such as referencing the server in scripting.
- Node
The name of the node where the proxy server resides.
- Version
Indicates the WAS version you are running.
- Protocol
Indicates the protocol or protocols that the proxy server is configured to handle. This information is based on the types of transport channels that are included in the transport chains that are configured for the proxy server.
For example, if a transport chain includes an HTTP channel, HTTP displays in this field.
- Status
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 restart the node agent before we can start the server.