Cell custom properties

Specifies whether to disable the remote host jobs capability in the job manager when you are not using the capability. When this property is set to true, the remote host jobs capability is disabled. When the property is set to false, the remote host jobs capability is enabled. The default value is false.

Specifies a value of displayServerInFront to display the name of the cell, node, and server in front of the output for the ps -ef command. Use of this property is intended to help you identify the process ID of a server. The property has no impact on the server process.

By default, the autoRestart attribute for the server monitoring policy is set to false because the Automatic Restart Management (ARM) is typically used to manage automatic restarts of the application servers. The autoRestart attribute for the server monitoring policy is defined in the server.xml file.

If you set the autoRestart attribute to true, you indicate that you do not want to use ARM to manage your server automatic restarts. For this situation, you must set com.ibm.websphere.process.terminator.deletepid to true to keep the servers in the cell from restarting in response to a stopImmediate command. Otherwise, the servers in the cell keep restarting in response to a stopImmediate command.

By default, caching for authorization is disabled. Caching can be enabled by setting this property value to true.

When this property is set to true, there should be fewer RACF® authorizations.

Specifies, in milliseconds, the length of time the node agent waits for cluster data to be gathered after a client submits the first request for that cluster. You do not need to specify a value for this property if the IBM_CLUSTER_ENABLE_PRELOAD custom property is set to true because the data is already loaded during the server startup process.

If the amount of time that is specified for this property is not sufficient for the amount of cluster data that needs to be gathered, NO_IMPLEMENT: No Cluster Data Available exceptions might still occur the first few times that a client sends requests to a cluster. Specifying an appropriate length of time for this property or specifying a value of 0, which eliminates the timeouts completely prevents the NO_IMPLEMENT: No Cluster Data Available exceptions from occurring because the cluster data is gathered within the specified length of time.

Specifies the number of threads in the thread pool that are used to run the custom advisors.

There is one thread pool that is used to run all the custom advisors configured on a proxy server. Conditions can occur based on the pooling interval and other circumstances where more custom advisors are needed to run at the same time than there are threads in the pool. By configuring more custom advisors than there are threads in the pool, some custom advisors are queued up and run as soon as a thread becomes available.

Specifies whether publishing of updates to the ActiveClusterSet is delayed. Enabling this custom property provides a performance improvement in large SIBus topologies and configured destinations, which results in a reduction of Messaging Engine Start and Stop times.

When this property is set to true, publishing of updates is delayed.

When this property is set to false, updates are published immediately.

Specifies whether publishing of updates to the ClusterDescription is delayed. Enabling this custom property provides a performance improvement in large service integration bus (SIBus) topologies and configured destinations, which results in a reduction of messaging engine start and stop times.

When this property is set to true, publishing of updates is delayed.

When this property is set to false, updates are published immediately.

Specifies whether the preload logic runs at server startup on the node agent. Without preload, a node agent only loads the data for a cluster after the node agent receives the first request for that cluster.

When this property is set to true, cluster data is loaded on the node agent at startup, and does not have to be created and propagated at run time.

When this property is set to false, the cluster data is created and propagated the first time there is a request to a cluster, which sometimes causes NO_IMPLEMENT: No Cluster Data Available exceptions the first few times a client sends requests to a cluster.

Specify this custom property with a value of true to override the cookie name at the server, application, or module level so that the proxy server can maintain session affinity with multiple applications on different clusters. The proxy server can maintain the session affinity since it can recognize session cookies other than JSESSIONID.

If you change any session management configuration, wait until all members of the cluster have been updated with the new configuration before doing a ripple start of the cluster. Otherwise, session failover might not work.

If you change the application or module session management configuration, wait until all members of the cluster have been updated with the new configuration before stopping and then restarting the application. Otherwise, session failover might not work.

Specify this custom property with a value of true to indicate that a cookie name is specified in a web.xml file or in a ServletContextListener instance. The setting to true allows the proxy server to maintain session affinity with multiple applications on different clusters. The proxy server can maintain the session affinity since it can recognize Servlet 3.0 session cookies other than JSESSIONID.

If you configure both Servlet 3.0 non-default cookies and non-default cookies at the server, application, or module level, the Servlet 3.0 cookies have the highest precedence.

If you change any session management configuration, wait until all members of the cluster have been updated with the new configuration before doing a ripple start of the cluster. Otherwise, session failover might not work.

If you change the application or module session management configuration, wait until all members of the cluster have been updated with the new configuration before stopping and then restarting the application. Otherwise, session failover might not work.

Specifies whether references to identities are deleted when there are no ClusterObservers registered for notifications on those identities. When an identity is deleted, all related posts on the BulletinBoard about that identity are cleared. Setting this property to true enables the references to identities that do not have any ClusterObservers registered on them to be deleted.

Typically there are many destinations defined in a Service Integration Bus (SIB) hierarchical scenario. If this property is set to false, and a product, such as the WebSphere® Process Server is installed after WebSphere Application Server, the Workload Management (WLM) does not properly allow data stored on the Bulletin Board to be garbage collected. This situation can cause a slow memory leak if certain tasks, such as the installing and uninstalling applications, are repeated without restarting the process. If the process is restarted all posts associated with that server are automatically removed, thus preventing the memory leaks.

Specify whether a Java™ thin client or server process can make continuous connection attempts until the cluster data is available to pass back to the client. The cluster data is then used for all future attempts.

Specify a value, in milliseconds, to indicate the amount of time the ripplestart function waits for processes to shut down before restarting them. If you attempt a ripplestart and the processes have not shutdown before the start operation begins, one or more of the processes will not restart.

Starting with Version 6.1.0.37, Workload management (WLM) uses a new procedure for compressing and extracting data that is sent between processes. This procedure reduces compression time in large WebSphere Process Server and service integration bus topologies that have 2,000 or more destinations. This procedure also prevents compressed data from being lost if a series of bytes to be compressed might not be compressed because every byte is unique. This situation might potentially cause a loss of data because of how WLM previously handled the uncompressed data.

This optimized compression and decompression procedure is appropriate for most environments. However, if this procedure causes problems in your environment, add the IBM_CLUSTER_USE_LEGACY_COMPRESSOR custom property to your cell settings, and set it to true. When you set this property to true, WLM handles data compression and decompression the same way that it did before Version 6.1.0.37 or later was installed.

If you add this custom property to your cell settings, you must synchronize the nodes, and restart all the processes in the cell before this change goes into effect.

Specifies whether your system supports interaction with either WebSphere Business Integration Version 5.1 clients or WebSphere Process Server for Multiplatforms Version 5.0.2 clients. If WebSphere Business Integration Version 5.1 clients, or WebSphere Process Server for Multiplatforms Version 5.0.2 clients need to send data to your system you must set this property to true. When this property is not included in your cell configuration settings, or if it is set to false, there is an interoperability issue where the data stream being passed back and forth becomes corrupted, which results in the following exception:

Exception stack trace: javax.naming.NamingException:
Error during resolve.  Root exception is rg.omg.CORBA.NO_IMPLEMENT:Trace from server:
  server_name at host host_name

ODCF8010I: Peer layer setting up.

Before you disable Intelligent Management, ensure that these capabilities are not required. By default, Intelligent Management is available, and it is activated by setting configuration options. Most capabilities are inactive until you change a specific Intelligent Management configuration. If Intelligent Management capabilities are not required, set the cell custom property to false, and all Intelligent Management capabilities become disabled. To completely disable Performance Monitoring Infrastructure (PMI), set LargeTopologyOptimization to false.

If this value is set to false, the Performance Monitoring Infrastructure (PMI) metrics that are controlled by Intelligent Management (see Table 1) are disabled. However, any custom or default PMI metrics that are not set by Intelligent Management remain active. For more information about PMI, see Performance Monitoring Infrastructure (PMI).

If profiles were created while Intelligent Management was enabled, and if later Intelligent Management is disabled, set the environment variable LargeTopologyOptimization_console=disable, then create the profiles again and the Intelligent Management panels do not display in the administrative console. If you do not create the profiles again, Intelligent Management panels continue to display in the administration console, but they are not operational.