ibmint optimize server command

Use the ibmint optimize server command to optimize the startup time of an integration server.

Usage notes

Your installed version of IBM® App Connect Enterprise must be 12.0.4.0 or later to be able to run the ibmint optimize server command. For more information about how and when to use the ibmint optimize server command, see Optimizing the startup time for an independent integration server.

Supported platforms

Windows
Linux®
Linux on POWER®
Linux on Z
AIX®
IBM z/OS® Container Extensions (zCX)

Purpose

You can use the ibmint optimize server command to optimize the startup time for an integration server. Optimization is achieved by disabling unused server components so that they are no longer initialized, thus saving CPU time on startup. The command automatically detects unused components by scanning the contents of the server's work directory, examining the server.conf.yaml file, the deployed flows, and other contents to determine which components are needed for the server to function correctly.

Optimization can also reduce the base memory foot-print of the IntegrationServer process. Total memory usage then continues to be reduced but by an amount that varies widely depending on the amount of message processing.

Syntax

Parameters

--work-directory directory: The path to the integration server's work directory to be optimized. A server.components.yaml file is written that indicates which components to exclude.

--enable component name: Specify that a particular component must be enabled. This parameter takes precedence over the work directory analysis. Can be specified multiple times to enable multiple components. The names of available components can be found in the sample.server.components.yaml file that is shipped in the product. For more information, see Optimizing the startup time for an independent integration server.
--disable component name: Specify that a particular component must not be enabled. This takes precedence over the work directory analysis. Can be specified multiple times to disable multiple components. The names of available components can be found in the sample.server.components.yaml file that is shipped in the product. For more information, see Optimizing the startup time for an independent integration server.
--default-application application name: The name of application under which the server places any independent resources.
--verbose: Output details from the work directory analysis to show which components were found to be required and so on.
--trace filePath: Send verbose internal trace to the specified file.

Examples

The following shows a command that would optimize the work directory C:\Work\Development\V12\Server1:

ibmint optimize server --work-directory C:\Work\Development\V12\Server1

The following shows a command that would optimize the work directory C:\Work\Development\V12\Server1, override enabling the JVM and disable two other components:

ibmint optimize server --work-directory C:\Work\Development\V12\Server1 --enable JVM --disable NodeJS --disable ResourceManagers/GlobalCache