Serviceability enhancements for stability and optimized resource usage

Restart the agent server

The Restart server process for a single agent server restarts all agent servers. The state of all agent servers is reset to the Starting state and then moves to the Running state.

If you modify the property that mandates to restart the server, use the Restart Server process instead of stopping and starting the server.

Export Logs for an agent or integration server

The file that is exported to ecurep or COS contains the multiserver-agent name. But this file contains the log of the selected agent server.

The file that is exported to ecurep or COS contains the multiserver-integration name. But this file contains the log of the selected integration server.
For example, 

COS- oms-ccc20-qa-11-0636406090484557b606cf3e7cbf7a72-oms-ccc20-qa-11-multiserver-integration-01-758bb44d7c-6jntg_BUCagentserver.tar

Starting a server that is configured with a queue, but the queue is not created in the IBM MQ server

When a server is started, the platform validates if a queue is present or is in the IBM MQ server before the JVM is initiated. You can view the following error in the logs and the server state will be Failed.

<Attribute Name="ErrorCode" Value="Queue configured in subflow doesnot exist"/>

If you search logs for a particular agent such as createOrderServer, the filter is appname:multiserver-agent-01 AND thread:Thread*createOrderServer*.

For an integration server, the filter name is appname:multiserver-integration-01.

For the createOrderServer integration server, the filter is appname:multiserver-integration-01 AND thread:Thread*createOrderServer*.

Deployment/CDT/Apply Environment certificate process time

Processes are faster because of reduced number of deployments are needed to run similar workloads.

Number of threads for a server

When you configure more than 2 threads for a server and start the server, the extra threads are bypassed as the server will always run only with 2 threads. However, if you want to increase the throughput of a server, increase the number of instances for the server. The number of threads will also increase in multiples of 2.

The filename is changed for the export log tar file. For example,
oms-<tenantid>-<envid>-xxxxxxxxx-oms-<tenantid>-<envid>-multiserver-integration-01-xxxxxxxx-6jntg_createOrderServer.tar

The file contains the log for createOrderServer.

Using static variables for the custom agent or service implementations to track or store variable data can cause issues, specifically when such logic could be used across multiple functional components. It can also cause issues in regular servers, where agent or integration servers are running in multiple JVMs or instances.
A similar issue might be observed when the servers are running in a multiserver. If such variables are set to different values by different components, they can cause issues while running on the same JVM. However, static variables can be used to get non-variable data for which values remain the same for the entire life span of the JVM.

To configure or add a server in the Server configuration tab of Self Service, ensure that the server is already configured in Sterling Order Management System. The Self Service then automatically fetches the names of the servers that are configured in Sterling Order Management System and displays in the drop-down list.

If you start a server using Self Service, and if the server is not configured in Sterling Order Management System, the Start server operation fails. You can view the following error message in the process report.

Configure the server names correctly.

Invalid Servers:<Server name>