Agent Vs Integration Server : Processes that run in the background to perform various tasks.
Even though both servers performs background activities has below differences
| Name | Description |
|---|---|
| Time Triggered Transaction | Program running at specific time intervals. Example RELEASE.0001 transaction |
| Agent Server | The process that runs the time-triggered transactions is known as an agent server. Example: DefaultAgent |
| Integration Server | The Process that manages asynchronous services, such as messages to and from external systems. Example: Order Fulfilment Order Fulfilment Services Edge Deployment ProcessCreateOrder |
| Agent Server | Integration Server |
|---|---|
| The process that runs the time-triggered transactions is known as an agent server. | An Integration Server is a process that manages asynchronous services, such as messages to and from external systems. |
| Multi-thread : Supported | Multi-thread : Supported |
| Multiple instances : Support | Multiple instances : Support |
| Can run multiple time triggered transaction: Yes | Configured via Service Definition Framework |
How to create Agent Server in Sterling Order Management System ?
- Go under any time triggered transaction
- Click the green color + symbol under “Agent Criteria Definition”section
- Enter Server name and click save
How to create Integration Server in Sterling Order Management System ?
- Go under “Service Definitions” create new service
- Drag and drop JMS or file component
- Connect the component with any other component (For example email or export_db)
- Click on the connector as shown in below image
- Go under server tab
- Click the green color + symbol
- Enter Server name and click save
How to find server is Agent Server or Integration Server ?
This information is available in yfs_server table. We can find using below query.
select server_type from yfs_server where servername=’?’;
Server type :
- 00 – Integration Server
- 01 – Agent Server
Time-triggered transactions
A time-triggered transaction is a program that performs a variety of individual functions, automatically and at specific time intervals. It is not triggered by conditions, events, or user input.
- Automatically : Schedule Trigger message every N minutes (Configuration under time triggered transaction)
- Manually: Trigger from $U process; triggeragent.sh <Criteria Name>
Three types of time-triggered transactions
- Business process transactions – responsible for processing day-to-day transactions. Example RELEASE.0001
- Monitors – watch and send alerts for processing delays and exceptions. Example ORDER_MONITOR_EX
- Purges – clear out data that may be discarded after having been processed. Example SUPPLYTEMPPRG
You can also read about Sterling OMS 9.4 Certification
Pingback: ibm sterling order management tutorial add item sku - Learn IBM Sterling Order Management System
Nice article!
Thank you.
if there are many messages stuck in Queue because of Integration Server down. what we will do in this situation?
If we understand your question correct, when integration server is down, all message will stay in queue until server is started. Hope this helps !!!
Please explaing get jobs, execute jobs, jms queues
Thanks for your request. We are working on it. Will get posted soon.
Pingback: Sterling OMS Creating Integration Server - Learn IBM Sterling Order Management System
Good one 🙂
Besides the different types of time-triggered transactions specified here, there are task based & non task based agents. Do you know how the task based agents get their task record (if not manually created using manageTaskQueue API)?
Satheesh,
Good question. That task_q entry decision is made by pipeline transaction configuration. This configuration available under transactions Others tab. Look for This transaction is task based checkbox. if this checkbox selected an entry will be made to yfs_task_q table. For example
Create order next transaction is schedule order. Schedule order has “This transaction is task based” enabled. So during order creation when order moved to created status system finds what is next transaction and if the transaction enabled for task_q. if yes entry made into yfs_tak_q table.
Hope this helps. if not clear please write to us. Thanks
Thank you so much for the explanation!
This really helpful
Pingback: Sterling OMS Non TaskQ Agent - Learn IBM Sterling Order Management System
very nice explanation