Migrating from Messaging Toolkit

Edit me

Migrating from JMS operators of the Messaging toolkit

The following information will help you to easily migrate from the JMS operators of the Messaging toolkit to the appropriate operators in the JMS toolkit.

Migrating JMSSource operators

To migrate your application’s JMSSource operator, do the following:

• Use com.ibm.streamsx.jms instead of com.ibm.streamsx.messaging.
• If you used parameter messageIDOutAttrName, use the parameter’s new name jmsMessageIDOutAttrName now.

Other changes

The operator now uses the annotation method to generate the operator model XML file, thus you may encounter the following changes:

• The operator now re-uses the initDelay parameter of the base class
• The code template has been removed, as it seems the annotation method does not provide a mechanism to define code templates anymore: ```XML

Basic JMSSource template

### Migrating JMSSink operators
 
To migrate your application's JMSSink operator, do the following:

- Use com.ibm.streamsx.jms instead of com.ibm.streamsx.messaging

#### Other changes

The operator now uses the annotation method to generate the operator model XML file,
thus you may encounter the following changes:

- The code template has been removed, as it seems the annotation method does not provide
a mechanism to define code templates anymore:
```XML
<codeTemplate name="JMSSink">
	<description>Basic JMSSink template</description>
	<template>
		() as ${sinkPrefix}Sink = JMSSink(${inputStream})   {
			param
				connection : &quot;${ConnectionSpecificationName}&quot;;
                access : &quot;${AccessSpecificationName}&quot;;
        }
    </template>
</codeTemplate>