Optimizing the start-up time for an independent integration server in IBM ACE
Here in this blog, we are going to learn How to optimize Integration Server start-up time in IBM ACE? IBM App Connect provides integration platforms for different systems. However, we develop the services to satisfy client requirements and we deploy them into integration servers. Based on some situations like many applications and message flows with less CPU it impacts the server startup time.
Server startup slower is not good practice. So we need to optimize the server startup time. IBM ACE introduces the ibm int command to optimize the start-up time for independent integration servers. This optimization with IBM int command supports ACE 22.214.171.124 or later versions. We can also optimize the server by disabling some properties in the server config yaml files.
- Create an independent integration server.
- Deploy some services on the server and test them.
- Stop and start the independent integration server.
- Take the initialization readings from the console
- Stop the server and apply the optimization command below mentioned.
ibmint optimize server –work-directory <serverDirectory>–verbose
- components.yaml file created at the root of the server directory.
- Set the NodeJS as false, restart the server, and note down the start-up time.
We don’t have the option to use optimization commands before ACE 126.96.36.199. To handle this scenario start-up time we need to disable the unused properties like GlobalCache: false, recordReplyEnable: false, etc..,
The above snap shows that the local independent integration server takes around 13 seconds to start-up and readings are taken before running the optimization command
The above picture represents the root directory of an independent integration server. Server.components.yaml file created after running the optimization command.
The above picture states that the start-up time taken by the server is around 4 seconds. These logs are taken after running the optimization command.
If we try to deploy the other applications in the server, it gives “BIP2377E Integration server ‘<server name>’ has been optimized. It is not possible to deploy to an integration server that has been optimized”. This happens due to the user’s own protection. This optimization makes the server sensitive to deploying the content. This phenomenon is not a problem for independent integration servers in containers because if a user wants to deploy the resources, the container should be down and place the resources and restart the container.