Use this page to manage the members of a proxy cluster. A proxy cluster of proxy servers is managed together and participate in workload management.
To view this administrative console page, click
proxy_cluster_name cluster_member_name.Specifies the name of the proxy server in the proxy cluster. On most platforms, the name of the server is the process name. The member name must match the name of one of the servers that are listed on the proxy servers page.
Specifies the short name for this cluster member. This field only appears if you are running on z/OS®.
The short name is used as the WLM APPLENV name for all proxy servers that are part of this cluster.
If you do not specify a short name, the system assigns a default short name that is automatically unique within the cell. You can change the generated short name to conform with your naming conventions.
Specifies that the application server runs in 64-bit mode, which is the default setting. Running in 64-bit mode provides additional virtual storage for user applications. This field only displays for the z/OS platform.
By default, the WebSphere® Customization Tools are set up to start all of your application servers in 64-bit mode. However, you can change the settings for the WebSphere Customization Tools, such that all of your application servers start in 31-bit mode. You can also unselect this setting for a subset of your application servers if you only want specific application servers to start in 31-bit mode.
There is no interdependence between the modes in which you are running different servers. Therefore, you can run some of your servers in 64-bit mode and some of your servers in 31-bit mode. However, you should eventually convert all of your servers to run in 64-bit mode because support for running servers in 31-bit mode is deprecated.
Enabling this option may reduce the startup time of an proxy server. This might include Java virtual machine (JVM) settings, such as disabling bytecode verification and reducing Just in Time (JIT) compiler compilation costs. Do not enable this setting on production servers.
Specifies that you want to use the JVM settings, -Xverify and -Xquickstart, on startup. After selecting this option, save the configuration and restart the server to activate development mode.
The default setting for this option is false, which indicates that the server is not started in development mode. Setting this option to true specifies that the server is started in development mode, using settings that decrease server startup time.
Data type | Boolean |
Default | false |
Specifies whether to start the server on multiple threads. When you start the server on multiple threads, the server components, services, and applications start in parallel rather than sequentially, which might shorten the startup time.
The default setting for this option is true, which indicates that the server uses multiple threads when it starts. Setting this option to false specifies that the server uses a single thread when it starts, which might lengthen startup time.
Data type | Boolean |
Default | true |
Select this property if you want the proxy server components started as they are needed by an application that is running on this proxy server.