Agent vs Integration Server in Sterling Order Management System

By | 05/18/2017

Agent Vs Integration Server : Processes that run in the background to perform various tasks.

Even though both servers performs background activities has below differences

NameDescription
Time Triggered TransactionProgram running at specific time intervals. Example RELEASE.0001 transaction
Agent ServerThe process that runs the time-triggered transactions is known as an agent server.
Example: DefaultAgent
Integration ServerThe Process that manages asynchronous services, such as messages to and from external systems.
Example: Order Fulfilment  Order Fulfilment Services  Edge Deployment  ProcessCreateOrder

Agent ServerIntegration 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 : SupportedMulti-thread : Supported
Multiple instances : SupportMultiple instances : Support
Can run multiple time triggered transaction: YesConfigured 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

Agent Vs Integration Server

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

Integration Server Creation

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

12 thoughts on “Agent vs Integration Server in Sterling Order Management System

  1. Pingback: ibm sterling order management tutorial add item sku - Learn IBM Sterling Order Management System

  2. shekar

    if there are many messages stuck in Queue because of Integration Server down. what we will do in this situation?

    Reply
    1. admin

      If we understand your question correct, when integration server is down, all message will stay in queue until server is started. Hope this helps !!!

      Reply
  3. Sneha

    Please explaing get jobs, execute jobs, jms queues

    Reply
    1. admin

      Thanks for your request. We are working on it. Will get posted soon.

      Reply
  4. Pingback: Sterling OMS Creating Integration Server - Learn IBM Sterling Order Management System

  5. Satheeshkumar Thangaraj

    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)?

    Reply
    1. admin

      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

      Reply
      1. Satheeshkumar Thangaraj

        Thank you so much for the explanation!

        Reply
  6. Pingback: Sterling OMS Non TaskQ Agent - Learn IBM Sterling Order Management System

Leave a Reply

Your email address will not be published. Required fields are marked *