Agent getters

All time-triggered (agent) transactions are driven by tasks in their message queue. A queue may serve one or more transactions. We strongly recommend you configure one queue for each high volume transaction.

The tasks are placed into the messaging queue by a getter. A getter’s job is to put qualified orders (in this example, orders that are in the Scheduled state) into the ScheduleSalesOrderQueue queue. You can specify the number of tasks a getter picks up each time it runs. By default, getters pick up a batch size of 5,000 tasks. In some cases, you may be able to achieve higher throughput by increasing the batch size.

Like the time-triggered (agent) transactions, a getter is also driven by work tasks in the queue - in this case, by a getter work task instead of a transaction work task. The getter work task is created by a trigger server.

Consider the following recommendations when configuring the Agent Servers:

• Agent thread levels
• Getters that can accept enterprise code as an additional parameter
• For JMS Servers:
  • Dedicated JMS Servers
  • Excessive agent scheduling
  • Dedicated JMS Destinations
  • JMS Persistence
• JMS getter and message queue PUT performance

For getters with enterprise code, see Getters with enterprise code.