[Rowan]

Hi there,

I would like to know how do transactions in OTM get prioritized. Basically the work flow i.e. a user does a transaction like editing a shipment in OTM, this gets assigned a transaction ID and so on...

Rohan

[bob_romijn]

Hi,

This will not be the complete answer, but as far as I know:
- Transmission comes in and will be processed as first come first serve
- Within a Transmission you have transactions. Within the transmission you can assign transactions to be handled first. Think of, first do the location transaction before you do the transorder transaction (to be sure the location is available). However the given example is not exactly neccessary because that is somehow done by OTM anyway (At least it never failed on my side and I do not give any priority).

The should give you a direction.

[chrisplough]

OTM doesn't have the concept of integration or transmission/transaction priorities or QOS (for instance making transactions from one customer higher than others, to bump them up to the front of the line). Instead, the integration server is a better place to put this type of business logic.

However, as Bob has noted - you can use the behavior of OTM in various ways. For instance, locations will be processed within a transmission before transorders, etc. Also, depending on how you send integration to OTM, you can force behaviors. If you send all of your integration transactions in a single transmission, they will be processed serially, one after another. However, if you break them up within your integration server and post each transaction as a separate transmission, then they will be processed in parallel. This important if you need to maintain order for some reason. By the same token, you can utilize thread groups to do the same -- to force various types of integration transmissions to get processed serially, in a first-in, first-out basis.

Again, though - OTM is still fairly simplistic in it's integration handling and does not offer QOS.

--Chris