To allow for business flexibility in a service-oriented architecture (SOA), a key implementation is business process choreography. Business process choreography ensures that business applications are made up of flexible and adaptable elements, so you can rapidly change the applications to meet business demands. Instead of having one huge application that cannot be easily modified for new business processes or needs, you compose your business applications based on your business process model. With IMS TM Resource Adapter, you can reuse your IMS conversational transactions in composite business applications that are served by IBM WebSphere® Process Server.
You must indicate to IMS Connect that this conversation needs a unique conversation ID to keep track of the conversation by setting the IMSInteractionSpec class useConvID property to true in your Service Component Architecture (SCA) component for the business process choreography application.
This setting triggers IMS to assign a unique conversational token and returns it to IMS Connect in the output message of the first iteration. This conversational token can then be passed back and forth between the business process choreography application and IMS Connect, and onto OTMA.
For more information about the conversational support provided by IMS Connect and OTMA and related restrictions, see the topic "IMS Connect conversational support" in IMS Version 12 Communications and Connections.
For more information about the dynamic interaction specification support provided in WebSphere Process Server, see the JCA EIS binding-related topics in the WebSphere Process Server documentation.