Performance tunings performed

BMC Helix Innovation Suite was used heavily during the performance tests. To support the given user load, the following default settings were changed:

• Jetty server threads — Jetty server is a built-in component of the Remedy AR System server. REST call requests sent to BMC Helix Multi-Cloud Broker are accepted by the jetty server and then processed by BMC Helix Multi-Cloud Broker. The Jetty Max Threads value was changed from the default value of 200 to 400. This setting is available in the arsystem/jetty/etc/jetty.xml file. 
• Database connections — Added the parameter Max-Database-Connections with value 400 to the BMC Helix Multi-Cloud Broker ar.conf. By default, this parameter is not available in the ar.conf file. 
  If BMC Helix Multi-Cloud Broker is unable to launch, and the errors with java.sql.SQLException:ConnectionPoolingConnection error in the ardebug.log file. The error indicates that the system requires additional database connections. 
• Additional information — Jetty logs were enabled to get response time of the REST calls coming from BMC Helix Integration Service connectors. These logs are similar to access logs of the web server. This is helpful while drilling down the response time of REST calls at BMC Helix Innovation Suite.