Intelligent Management: node agent custom properties
We can use custom properties to modify the node agent configuration, and to configure timeout values for the node agent.
ServerStartupTimeoutMillis
The ServerStartupTimeoutMillis custom property specifies the amount of time that the node agent waits, during the middleware server startup, before the node agent times out and stops trying to start the server. If the middleware server starts before the timeout value, the agent stops waiting and continues with the startup processing.
Value Description Scope Cell, node, or server level Default 75000 (75 seconds) Units milliseconds
ServerShutdownTimeoutMillis
The ServerShutdownTimeoutMillis custom property specifies the amount of time that the node agent uses to determine whether a server has successfully stopped.
Value Description Scope Cell, node, or server level Default 75000 (75 seconds) Units milliseconds
MiddlewareAgentProcessScanIntervalMillis
The MiddlewareAgentProcessScanIntervalMillis custom property specifies a time interval at which the node agent scans the configured servers to reestablish monitors for all the running middleware servers. If we set the value to zero, the repeated scans are disabled.
Value Description Scope Cell, node, or server level Default 60000 (60 seconds, or one minute) Units milliseconds
ServerInitializedTimeoutMillis
The ServerInitializedTimeoutMillis custom property is the amount of time that a node agent uses to determine if a middleware server is started or not, after performing the start server operation and binding to the middleware server process. If the node agent cannot determine if the server is running, the default assumption is that the middleware server is not running.
Value Description Scope Cell, node, or server level Default 30000 (30 seconds) Units milliseconds
MiddlewareServerStartWaitTime
The MiddlewareServerStartWaitTime custom property is used to configure the middleware server initialization time. After a middleware server starts, additional time for the server to initialize is required. If the node agent reports that the middleware server has started too soon, HTTP requests directed to that middleware server might fail. We can use this custom property so that the node agent does not report that the server has started for a fixed period.
Value Description Scope Cell, node, or server level Default 75000 (75 seconds) Units milliseconds
WASCEAppStatusRetryCount
The WASCEAppStatusRetryCount custom property allows us to configure the number of retries when running the WASCE command to determine if an application is started on the WebSphere Application Server Community Edition server.
Value Description Scope Cell, node, or server level Default 3 Units retry
WASCEAppStatusRetryDelayTime
The WASCEAppStatusRetryDelayTime custom property allows us to configure the delay between retries when running the WASCE command to determine if an application is started on the WebSphere Application Server Community Edition server.
Value Description Scope Cell, node, or server level Default 10000 (10 seconds) Units milliseconds
Related concepts
Middleware nodes and servers
Related tasks
Add middleware servers to configurations