Use conversation ID (useConvID)

This property indicates whether an IMS conversation is using the same connection for all iterations of the conversation or different connections.

By default, a subsequent iteration of a conversation on a shareable persistent socket is rejected by IMS Connect (if the socket is different between iterations) because IMS Connect cannot find the relevant information for the socket that is used in the first iteration.

When this property is set to true, IMS assigns a unique conversation token that must be passed back and forth between the Java™ application and IMS Connect. IMS Connect no longer keeps track of the conversational status of the client. As a result, the VIEWHWS IMS Connect command will not display the CONV status for the client unless the command is entered when IMS Connect is processing a conversational iteration. This approach to manage the iterations of a conversation is called the client-managed conversation state programming model, as opposed to IMS Connect-managed conversation state programming model.

Important: The default is false for backward compatibility. For applications that are migrating to use IMS TM Resource Adapter Version 12 or later, if you are not using shareable socket connections for different iterations of a conversational transaction, no change is required. For new application development, set this property to true to take advantage of using different shareable persistent socket connections for the different iterations of a conversational transaction.