Cell custom properties

You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set configuration properties for a cell. Defining a new custom property for a cell enables you to configure a setting beyond that which is available in the administrative console. The following is a list of custom properties that are already available to configure for a cell.

To specify a custom property for a cell:

  1. In the administrative console click System Administration > Cell > Custom Properties
  2. On the Custom Properties page, click New.
  3. On the settings page, enter the name of the custom property that you want to configure in the Name field and the value that you want to set it to in the Value field.
  4. Click Apply or OK, and then click Save to save your configuration changes..
  5. Restart the server on which the cell resides.

Following is a list of custom properties provided with the product.




Related tasks
Configuring cells

IBM_CLUSTER_CALLBACK_TIMEOUT

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 in that situation, the data is pre-loaded during the server startup process.

If the amount of time 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 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.

Property IBM_CLUSTER_CALLBACK_TIMEOUT
Data type integer
Default 180000, which is equivalent to 3 minutes

IBM_CLUSTER_ENABLE_PRELOAD

Specifies whether the pre-load logic should run 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 runtime.

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.

Property IBM_CLUSTER_ENABLE_PRELOAD
Data type boolean
Default false

IBM_CLUSTER_PURGE_NOTIFICATIONS

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 on top of 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, thereby preventing the memory leaks.

Property IBM_CLUSTER_PURGE_NOTIFICATIONS
Data type boolean
Default false

IBM_CLUSTER_RIPPLESTART_NOTIFICATION_TIMEOUT

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.

Property IBM_CLUSTER_RIPPLESTART_NOTIFICATION_TIMEOUT
Data type integer
Default 300000 milliseconds (5 minutes)

IBM_CLUSTER_WBI_SUPPORT

Specifies whether your system supports interaction with either WebSphere Business Integration Version 5.1 clients or WebSphere Process Server for Multiplatforms Verion 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
Avoid trouble: This property can also be specified as an application server custom property. However if this property is specified at both levels, the value specified for the property at the server level takes precedence over the value specified for this property at the cell level.

To enable the property at the server level, in the administrative console click Servers > Server Type > WebSphere application servers, and then under Server Infrastructure, click Administration > Custom Properties.

gotcha
Property IBM_CLUSTER_WBI_SUPPORT
Data type boolean
Default false

com.ibm.websphere.management.launcher.options custom property

Specify 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.

Property com.ibm.websphere.management.launcher.options
Data type String
Default None
[Version 6.0]

IBM_CLUSTER_ENDPOINT_WAIT

Specify a value, in seconds, to indicate the amount of time that you want the session manager to wait for endpoint data to be received. Typically, specifying a value of 5 for this property enables the endpoint data, that is used to create the structures that track and route the sessions, to be received. If a timeout situation occurs because the data is not received, you can increase the value specified for this property.

Property IBM_CLUSTER_ENDPOINT_WAIT
Data type Integer
Default None


Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=ragt_cell_customprops
File name: ragt_cell_customprops.html