Intelligent Management: middleware server custom properties and variables

Middleware server variables and custom properties define properties for middleware servers, such as the maximum heap size for assisted lifecycle servers.


SERVER_MAX_HEAP_SIZE variable

The SERVER_MAX_HEAP_SIZE variable defines the maximum heap size for assisted lifecycle servers. If the variable is not defined, the default maximum heap size value for the server type is used.

We can use wsadmin scripting to set the SERVER_MAX_HEAP_SIZE variable. Follow the directions in the topic on modifying variables using wsadmin scripting.

To set the SERVER_MAX_HEAP_SIZE variable using the console, click Servers > All servers > server_name > Variables. Specify the maximum heap size in megabytes.

Avoid trouble:

When the excessive memory usage health policy is triggered for WebSphere Application Server Community Edition servers, the percentage of the heap size specified in the runtime task message is inaccurate.

Configure the maximum heap size for each WebSphere Application Server Community Edition server when you configure the excessive memory usage health policy for WebSphere Application Server Community Edition servers.

Set the SERVER_MAX_HEAP_SIZE variable at the server level. The default value is 64 MB.

In the console, click Servers > All servers > Variables.

For more information, read the topic on middleware server custom properties and variables. gotcha

Server type Maximum heap size
JBoss 512 MB
Apache Tomcat 64 MB
Liberty profile 64 MB
WebSphere Application Server Community Edition 64 MB
BEA WebLogic 400 MB


UseJMXSecureConnector custom property

The UseJMXSecureConnector custom property specifies whether JMX (JMX) security is enabled for a WAS Community Edition Version 2.1 server or later server.

To enable JMX security, additional steps are required beyond setting the custom property. Read about the additional steps in the topic on Configuring JMX security for WebSphere Application Server Community Edition.

To set the UseJMXSecureConnector custom property, click Servers > Other middleware servers > WebSphere Application Server Community Edition servers > wasce_server_name > Custom properties > New. Set the value to true to enable JMX security.

Value Description
Value True or false
Default false


Related concepts

  • Middleware nodes and servers


    Related tasks

  • Configure assisted life-cycle WebSphere Application Server Community Edition servers
  • Configure JMX security for WebSphere Application Server Community Edition Version 2.1 servers
  • Configure JBoss servers
  • Configure Apache Tomcat servers
  • Configure BEA WebLogic servers
  • Modify variables

  • Intelligent Management: middleware server custom properties and variables