Secure Agent Services > Process Server > Configuring thread pool profile to improve throughput
  

Configuring thread pool profile to improve throughput

When you use event-based connectors such as AMQP and Kafka, you can increase the number of threads by increasing the thread pool size in the default thread pool profile. To increase the thread pool size, update the aeEngineConfig.xml.mustache file on the Secure Agent machine.
By default, the thread pool size is limited to 10 threads and a maximum of 10 messages can be processed concurrently by the connections. Informatica recommends that you increase the thread pool size only if you want to increase throughput, because additional threads occupy some resources, and too large pools are not recommended. The thread pool size applies to all event-based connections.
You can also configure the thread pool profile settings on the Server Configuration page in Application Integration Console. When you configure the thread pool profile settings on both the Server Configuration page and the aeEngineConfig.xml.mustache file on the Secure Agent machine, the properties configured on the Server Configuration page take precedence. For more information about the thread pool profile settings on the Server Configuration page, see Server Properties.
To configure the thread pool profile, perform the following steps:
    1Log in to the Secure Agent machine.
    2Go to the following directory:
    <Secure Agent installation directory>/downloads/package-process-engine.<latest_version>/package/app/webapps/process-engine/WEB-INF/classes
    3Open the aeEngineConfig.xml.mustache file in a text editor and search for the following entry:
    <entry name="IAeESBManager">...</entry>
    4Within the IAeESBManager entry, search for the subentry named camelContext.
    Based on the status of the cluster.enabled option, you will find the following entries:
    5Append a new threadpoolProfile subentry within the camelContext entry.
    If the cluster.enabled option is disabled, add the following lines:
    <entry name="camelContext">
    <entry name="Class" value="com.activee.rt.camel.core.AeDefaultCamelContext"/>
    <!-- New subentry -->
    <entry name="threadpoolProfile">
    <entry name="PoolSize" value="<PoolSizeValue>"/>
    <entry name="MaxPoolSize" value="<MaxPoolSizeValue>"/>
    <entry name="MaxQueueSize" value="<MaxQueueSizeValue>"/>
    <entry name="KeepAliveTime" value="<KeepAliveTimeValue>"/>
    <entry name="TimeUnit" value="SECONDS"/>
    <entry name="AllowCoreThreadTimeout" value="true"/>
    <entry name="RejectedPolicy" value="CallerRuns"/>
    </entry>
    </entry>
    If the cluster.enabled option is enabled, add the following lines:
    <entry name="camelContext">
    <entry name="Class" value="com.activevos.socrates.connectors.camel.AeSocratesCamelContext"/>
    <!-- New subentry -->
    <entry name="threadpoolProfile">
    <entry name="PoolSize" value="<PoolSizeValue>"/>
    <entry name="MaxPoolSize" value="<MaxPoolSizeValue>"/>
    <entry name="MaxQueueSize" value="<MaxQueueSizeValue>"/>
    <entry name="KeepAliveTime" value="<KeepAliveTimeValue>"/>
    <entry name="TimeUnit" value="SECONDS"/>
    <entry name="AllowCoreThreadTimeout" value="true"/>
    <entry name="RejectedPolicy" value="CallerRuns"/>
    </entry>
    </entry>
    6 Increase the thread pool size as required.
    Note: The pool is used by all the running event-based connections on the Secure Agent.
    7Save the aeEngineConfig.xml.mustache file.
    8Restart the Secure Agent for the change to take effect.