2. Sterling Components

These are nodes which can be used to perform different actions in Sterling application.



Sterling API

Sterling API Node is used to trigger the out of the box sterling APIs. Click here for more information on the Sterling API node.

Sterling Service

Sterling Service Node is used to trigger the customized sterling APIs. Click here for more information on the Sterling Service node.

JMS Publisher

JMS Publisher Node is used to post the messages to the MQs. JMS Publisher node publishes messages to any standard queue that is configured to Sterling process/server. Sterling process/server in turn picks up the messages and processes the message based on the business rules. Click here for more information on the JMS Publisher node.



JMS QueueBrowser

JMS QueueBrowser is used to browse for a message in the queue as per the given search criteria. The queue browser reads the last 1000 messages and returns the message which matches as per the selection criteria. Queue browsers are used to read the messages from the message queues such as IBM Broker and JMS. A client uses a Queue Browser object to look at messages on a queue without removing them. Click here for more information on the JMS QueueBrowser node.

Sterling SOAP Request

Sterling SOAP Request node is an XML-based protocol for accessing web services over HTTP. Click here for more information on the Sterling SOAP Request node.

Did you find what you were looking for?

Automation Analytics and AI in a box

Contact Us

HfS Hot Vendor

Option3's Automation capabilities featured in HfS Research's Hot Vendors List for Q3, 2018

Access your copy here