Sterling OMS Understanding multiApi

By | 12/12/2019

Sterling OMS multiApi

Sterling OMS Understanding multiApi : With one single API call, we can internally call multiple APIs using the Multi API. Most importantly, all the APIs that are called will have the same commitment boundary. That is, either all of them succeed or all of them fail. If in case, one of them throws an exception, the entire work done so far will be rolled back.

Use case for multiApi

Lets say customer has requirement where create, schedule, release order in single transaction. This scenario taken only to explain multiApi. If one of the API fails it should rollback the transaction. Meaning if schedule fails order creation should not happen.

How multiApi input XML looks ?


<MultiApi>

<API FlowName=”API1″ IsExtendedDbApi=”” Name=” API1″ Version=”OlderVersion can be given here”>
<Input/>
<Template/>
</API>

<API FlowName=”API2″ IsExtendedDbApi=”” Name=” API2″ Version=”OlderVersion can be given here”>
<Input/>
<Template/>
</API>

<API FlowName=”API3″ IsExtendedDbApi=”” Name=” API3″ Version=”OlderVersion can be given here”>
<Input/>
<Template/>
</API>

</MultiApi>


Example to Create, Schedule and Release an Order using MultiAPI

See below example sample how multiApi can be used to create, schedule and release order.

Input XML:

Test using API Tester?

HTTP API Tester

API Output

Important Tips

  • This api allows to call service and/or API
  • We can call api/service with template XML for each api/service
  • Single database commit happens if all the api/service does not have any error.

Any question please email to support@activekite.com

2 thoughts on “Sterling OMS Understanding multiApi

    1. admin Post author

      Yes it should work. If you have created new table, need to create services to insert/update/delete/get/getList. So these services can be called via multiapi.

      Reply

Leave a Reply

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