Administration and Administration services custom properties

This topic discusses the administration and administration services custom properties that you can set on the administrative console.

To view the administration services custom properties administrative console page that goes with this topic, click Servers > Server Types > WebSphere application servers > server_name > Administration > Administration services > Custom properties.

Specify a property and its value as a name-value pair on the administration services custom properties page.

To view the administration custom properties administrative console page that goes with this topic, click Servers > Server Types > WebSphere application servers > server_name > Server Infrastructure > Administration > Custom properties.

Specify a property and its value as a name-value pair on the administration custom properties page. The property is set on the administration custom properties page of the application server that the plugin is routing requests to.

com.ibm.websphere.mbeans.disableRouting

When a custom managed bean (MBean) is registered directly with the MBean server that runs in a WebSphere Application Server process, the MBean object name is enhanced by default to include the cell, node, and process names as key properties. To turn off the default behavior, set the following custom property on the application server.

With this enhancement, in a WebSphere Application Server Network Deployment environment, the MBean that is registered on an application server is addressable through a client that is connected to the deployment manager.

If this custom property is set, an administrative client needs to connect directly to the application server on which the MBean is registered to invoke methods. The MBean cannot participate in all the distributed functions of the administrative system.

One or more MBean object names tagged with <on>...</on>. You can specify the object name of your MBean or a pattern that matches the names of several MBeans.

Example:

If you register a custom MBean with the WebSphere:type=custom,name=custommbean1 object name and another custom MBean with the WebSphere:type=custom,name=custommbean2 object name, each of the following values is valid:
  • <on>WebSphere:type=custom,name=custommbean1</on>

    The value disables the MBean object name modification for this MBean.

  • <on>WebSphere:type=custom,*</on>

    The value disables the MBean object name modification for both MBeans.

  • <on>WebSphere:type=custom,name=custommbean1</on><on>WebSphere:type=custom,name=custommbean2</on>

    The value disables the object name modification for both MBeans.

Plugin_PersistTimeOut_Reduction

Use the Plugin_PersistTimeOut_Reduction property to fine tune the ConnectionTTL feature in the Webserver plugin. ConnectionTTL reviews the amount of time since a stream was last used. If the time indicates that the stream is too old, the plugin cancels that stream and opens a new one to service the request. The Webserver plugin has an internal default value of 28 seconds for ConnectionTTL, which is derived from the application server transport's persistent time out default of 30 seconds minus a reducer of 2 seconds. Based on your requirements, you can adjust the 2 second reducer time using the Plugin_PersistTimeOut_Reduction property.

Information Value
Data type Integer
Range one half of the value set for the application server transport's persistent time out value
Default 2