Agent criteria
Agent criteria is defined for time-triggered transaction.
Agent criteria provides information such as organization for which the agent needs to run, how
many threads need to be run in this agent. The agent criteria that are provided by Deployment Accelerator are parametrized, and allows the attributes
in agent criteria to be provided in property files such as the
customer_overrides.properties file.
For example, agent criteria is defined for the Schedule time-triggered (agent) transaction. When an Agent Server is started, the server runs with configured number of threads for the Schedule time-triggered transaction. If more processing threads are needed, the number of threads can be increased or more instances of the Agent Server can be run. For recommendations on how to estimate the threading levels, see Agent thread levels.
Deployment Accelerator also provides purge criteria for
Order Purge time-triggered transaction.
The agents are segregated and associated with the appropriate agent servers. Segregation is done based on the functionality and also to optimize the load on the servers. The agent criteria can be used to trigger the agents.
| Criteria ID | Runtime Properties | |||
|---|---|---|---|---|
| Schedule Trigger Message | Schedule Trigger Message Interval (Min.) | No. of Threads | Agent Server | |
| SDA_CLOSE_ORDER | N | NA | 3 | SDAAgentServer1 |
| SDA_CNSDL_ADDNL_INV | N | NA | 3 | SDAAgentServer1 |
| SDA_CLOSE_SHIPMENT | N | NA | 3 | SDAAgentServer1 |
| SDA_ORDER_PURGE | N | NA | 1 | SDAAgentServer1 |
| SDA_PUBLISH_SHIP_ADVICE | N | NA | 3 | SDAAgentServer1 |
| SDA_RESERVATION_PRG | N | NA | 3 | SDAAgentServer1 |
| SDA_CNSLDT_TO_SHIP | N | NA | 3 | SDAAgentServer1 |
| SDA_SCHEDULE_ORDER | Y | 15 | 3 | SDAAgentServer1 |
| SDA_RELEASE_ORDER | Y | 15 | 3 | SDAAgentServer1 |
| SDA_SUPPLYTEMPPRG | N | NA | 3 | SDAAgentServer2 |
| #{EnterpriseCode}_FULL_SYNC | N | NA | 3 | SDAAgentServer2 |
| SDA_PAYMENT_COLLECTION | Y | 60 | 3 | SDAAgentServer2 |
| SDA_PAYMENT_EXECUTION | Y | 60 | 3 | SDAAgentServer2 |
| SDA_ORDER_MONITOR | Y | 15 | 3 | SDAAgentServer2 |
| SDA_RTAM_ACTIVITY | Y | 15 | 3 | SDAAgentServer2 |
| MASTER_DATA_UPLOAD_SCHEDULER | Y | 30 | 1 | SDADataAgentServer1 |
| MASTER_DATA_UPLOAD_RUNNER | Y | 30 | 1 | SDADataAgentServer1 |
| MASTER_DATA_UPLOAD_SUMMARIZER | Y | 30 | 1 | SDADataAgentServer1 |
The configurations that are provided by Deployment Accelerator enable customers to start the agent servers without having to manually configure them in the
Applications Manager. As the server name and queue configurations are parametrized, it allows the
queue configuration to be provided in the property files. Queue configurations are commonly provided
in the customer_overrides.properties file. In an ideal scenario, agents can be
started without deploying the Sterling Order Management System Software application.
Viewing the agent criteria details
- Launch the Applications Manager.
To launch the Applications Manager, from the Application Console menu, click Configuration > Launch Applications Manager. The Applications Manager opens in a new window.
- From the menu, click Applications > Application Platform.
- Double-click Process Modeling. The Process Modeling window opens.
- From the Process Types, select Order Fulfillment process type.
- Click the Transactions.
- From the tree in the application rules side panel, expand select the appropriate time-trigerred transaction. The Transaction Detail window opens.
- Click Time Triggered tab.
- In the Agent Criteria Definitions panel, select and double-click the appropriate agent criteria. The Agent Criteria Details window opens.