Activating JMS Transport on the Server Side
1. Go to the Software AG_directory /profiles/CTP/workspace/wsstack/repository/conf directory and open the axis2.xml configuration file.
2. Uncomment the sections that define the transport receiver and transport sender with name="jms":
<transportReceiver name="jms" ... />
<transportSender name="jms" ... />
3. Define the custom connection factories. You can define custom connection factories as parameters under JMS transport receiver. They can be used by the services deployed over JMS transport. Refer to the axis2.xml configuration file to see the sample connection factories that the JMS transport receiver configuration includes.
Note:
One of the connection factories is named as the default for use by services that do not explicitly specify the connection factory they want to use in their services.xml configuration file.
Each connection factory specifies parameters for an initial naming factory class, a naming provider URL, and the JNDI name of an actual JMS connection factory. Web Services Stack can run with the default configuration of Apache ActiveMQ, if you use it. In this case, you only have to uncomment the JMS transport receiver and JMS transport sender configuration in the axis2.xml file.
Note:
You must always run the message broker before you start Web Services Stack.