Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Proxy server collection
This topic lists the proxy servers in the cell. A proxy server resides within a 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. We can use this page to create, delete, or modify a proxy server. From the console...
Servers > Server Types > WebSphere proxy servers .
To configure the proxy server to route work to WASs 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 WAS Express cell requires advanced configuration. See the information on routing rules to learn more about setting the advanced configuration routing rules.
To configure the proxy server to route work to an application server that is not a WAS, the following advanced configuration is required:
- Define a generic server cluster. From the admin console,
click...
Servers > Clusters > Generic server clusters.
- Define a URI group. From the admin console, click
Environment > URI groups.
- Create routing rules.
From the admin console,
click...
Servers > Server Types > WebSphere proxy servers > proxy_server_name
> Proxy Server Properties > Routing rules .
Both generic server clusters and URI groups are also accessible in the admin console under Related Items for the proxy server. >
Specifies a logical name for the proxy server. For WAS, server names must be unique within a node.
If we 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.
Security level
The current overall security level of the proxy server.
The overall security level is determined based on the custom security settings. The possible values for Security level are High, Medium, Low, and Not applicable. The overall security level is equal to the security level of the setting that is considered the least secure. For example, to have an overall security level of High, all settings must be configured to the values associated with a HIGH level of security. If any of the settings are configured with a less secure value, the overall security level is the value of that setting.
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. If a transport chain includes both a SIP and an HTTP channel, SIP,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 you can start the server.
| Started | The server is running. |
|---|---|---|
| Stopped | The server is not running. |
| Unknown | Status cannot be determined.
A server with an unknown status might, in fact, be running but has an unknown status because the application server that is running the admin console cannot communicate with this server. |
Set up the proxy server
Related
Generic server cluster members
Route rules
Route rules configuration
URI groups
Environment entries collection