Running the agent server

The agent server utility starts the processing for transactions generated by time-triggered transactions (agents). You can start multiple instances of an agent server by running the script as many times as needed.

You can start the agent server script by running:
Note: If you configure agents to use TIBCO JMS, ensure the prefetch parameter for queues is set to 1.
Note: If you configure agents or integration servers to use JBoss Messaging, uncomment the following "Attribute" xml element in remoting-bisocket-service.xml under:
<PATH>/jboss-eap-5.1/jboss-as/server/all/deploy/messaging directory: <attribute name="ping
Frequency" isParam="true">214748364</attribute>
Note: Agent and integration servers implement their own, self-managing connection pools. However, the following two properties in the <INSTALL_DIR>/properties/jdbc.properties file define the minimum and maximum number of connections:
  • <databasePool>.initsize - Initial size of the database pool. This is the minimum number of database connections to keep in the pool.
  • <databasePool>.maxsize - Maximum size of the database pool. This is the maximum number of connections to keep in the pool.

For more information about database pool properties, read the commented descriptions in your jdbc.properties file.