Use this page to create advanced configurations for a proxy server. You can modify an existing proxy server to perform advanced routing options, such as routing requests to a non-WebSphere Application Server cell, and to perform caching. The options to configure the proxy server from this panel are under Proxy Server Properties.
To view this administrative console page, click Servers > Proxy Servers > server_name
On the Configuration tab, you can edit proxy server setting fields.
Configuration tab
Specifies a logical name for the proxy server. Proxy server names must be unique within a node. However, for multiple nodes within a cluster, you may have different proxy servers with the same proxy server name as long as the proxy server and node pair are unique.
For example, a proxy server named proxy1 in a node named node1 in the same cluster with a server named proxy1 in a node named node2 is allowed. Configuring two proxy servers named proxy1 in the same node is not allowed. WebSphere Application Server uses the proxy server name for administrative actions, such as referencing the proxy server in scripting.
| Data type | String |
| Default | proxy1 |
Enabling this option may reduce the startup time of a proxy server. This may include JVM settings such as disabling bytecode verification and reducing JIT compilation costs. Do not enable this setting on production servers.
That you want to use the JVM settings -Xverify and -Xquickstart on startup. After selecting this option, save the configuration and restart the proxy server to activate development mode.
The default setting for this option is false, which indicates that the proxy server will not be started in development mode. Setting this option to true specifies that the proxy server will be started in development mode (with settings that will speed server startup time).
| Data type | Boolean |
| Default | false |
Select this field to start the proxy server on multiple threads. This might shorten the startup time.
That you want the proxy server components, services, and applications to start in parallel rather than sequentially.
The default setting for this option is true, which indicates that the proxy server be started using multiple threads. Setting this option to false specifies that the server will not be started in using multiple threads (which may lengthen startup time).
Note that the order in which the applications start depends on the weights you assigned to each of them. Applications that have the same weight are started in parallel. You set an application's weight with the Starting weight option on the Applications > Enterprise Applications > application_name page of the Administrative Console. For more information about the Starting weight option, see Enterprise application settings.
| Data type | Boolean |
| Default | true |
Related reference
Proxy server collection
Administrative console buttons
Administrative console page features
Administrative console scope settings
Administrative console preference settings
Object names