Other Considerations

When you are designing your system architecture there are several general recommendations and best practices you might consider. These best practices cover end-to-end order tracking and ensure that you do not lose any data.

OrderRef

Order ID must be unique in all TIBCO Order Management - Low Latency orders. If the two flags mapOrderIdWithRef=true and validateDuplicateOrder=true are enabled for OrderRef and if you submit an order without a unique OrderRef, the Order Management system does not accept that order, rather it gives an error for latest order.

Note: User Defined Formats in the TIBCO Order Management - Low Latency have limited out-of-the-box searchability.

General Recommendations

It is important when you are designing your architecture to incorporate procedures that prevent order data loss. It is a good practice to review the following procedures before designing your architecture solution:

  • Ensure that your architecture solution includes end-to-end order tracking capability and visibility similar to that used in the order system of the TIBCO Order Management - Low Latency.
  • Include recovery and repair capabilities in your design. For example, you need a plan for handling a situation when a fulfillment process call fails to connect to a back-end system. Having a plan in place prevents you from having to stop the order.
  • Determine the interfaces that the operation needs to complete this work. Resending an order might not be a viable or reasonable option.
  • Include target group representatives when planning manual steps and activities.
  • Validate your error and exception handling approach with other representatives in the order processing chain from front-end solutions to back-end systems.
  • Ensure that your solution architecture accounts for the different capabilities in each system area. For example, a front-end system might not be able to resubmit an order after it is submitted.