Proxy cluster member settings
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.
When a proxy server is part of a proxy server cluster, the only HTTP proxy server setting that can be set at the proxy server level is Local outbound TCP address. The other HTTP proxy server settings must be set at the proxy cluster level. gotcha To view this console page, click Servers > Clusters > Proxy server clusters > proxy_cluster_name > Cluster members > cluster_member_name.
Member name
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 listed on the proxy servers page.
(zos) Short name
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 we specify a short name for a cluster member, the name:
- Must be one to eight characters in length
- Must contain only uppercase alphanumeric characters
- Cannot start with a number
- Must be unique in the cell
If we do not specify a short name, the system assigns a default short name that is automatically unique within the cell. We can change the generated short name to conform with the naming conventions.
(zos) Run in 64 bit JVM mode
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 Toolbox is set up to start all of the application servers in 64-bit mode. However, we can change the settings for the WebSphere Customization Toolbox such that all of the application servers start in 31-bit mode. We can also unselect this setting for a subset of the application servers if you only want specific application servers to start in 31-bit mode.
There is no interdependence between the modes in which we are running different servers. Therefore, we can run some of the servers in 64-bit mode and some of the servers in 31-bit mode. However, you should eventually convert all of the servers to run in 64-bit mode because support for running servers in 31-bit mode is deprecated.
Run in development mode
Enable this option may reduce the startup time of an proxy server. This might include JVM settings, such as disabling bytecode verification and reducing Just in Time (JIT) compiler compilation costs. Do not enable this setting on production servers.
(iseries) This option is not supported in an i5/OS environment.
Specifies 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.
Information Value Data type Boolean Default false
Parallel start
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.
Information Value Data type Boolean Default true
Start components as needed
Select this property if we want the proxy server components started as they are needed by an application running on this proxy server.
When this property is selected, proxy server components are dynamically started as they are needed. When this property is not selected, all of the proxy server components are started during the startup process. Therefore, selecting this property usually results in improved startup time because fewer components are started during the startup process.
Avoid trouble: If we are running other WebSphere products on top of the Application Server, make sure that those other products support this functionality before you select this property.gotcha
Reference topic