we are using standard OOTB Web Services for creating customer and publishing updates to the registered systems in our OCH solution. We have been using so far HTTP transport. Since client came up with new non functional requirements, we need to switch to queues. We are integrated with Fusion MW and all communication from/to OCH is going through Fusion. Assumption is that queues will be managed on Fusion side.
what is the roadmap/key activities/customization in order to switch to new queueing transport mechanism for Create Person and Publish/Subscribe. Asumptin is that it will be JMS queues.