steps to configure a sample JMS server that supports JTA. Suppose a weblogic server or cluster has already been created. Let's call it SampleServer.
Notes. It may be necessary to create the queue and the subdeployment and to target it to a JMS server. But you do not have to do this for connection factory. In the webblogic10 sample application medrec, you can see from the admin console that three queues are configured. But there is no connection factory. But JMS won't work without a factory. So where is the factory? The medrec source code reveals the secret. It turns out that weblogic has two predefined factories that can be used. The JmsClientImpl.java in medrec defines the following:
private String connectionFactoryName = "weblogic.jms.XAConnectionFactory";
Then the code uses this name as the JNDI name to look up the connection factory. For more information, look at the weblogic document on it.
- Create a Non-XA DataSouce
- Create a persistent JDBCStore. Use the non-XA DataSource created above. Don't forget to assign the store a prefix name, say 'Example'. A table ExampleWLStore should be created in the database if the configuration will be successful. Target the JDBCStore to SampleServer.
- Create a JMS server. Use the JDBCStore created above. Target it to SampleServer
- Create a JMS module. Target it to SampleServer
- In the JMS module, create subdeployment. Target the subdeployment to the JMS server.
- Create a Queue and a Queue Connection Factory in the JMS module and associate them with the subdeployment. Assign a JNDI name to the queue and the factory. Notice that when creating the queue connection factory, the xa-connection-factory-enabled flag should be set to 'true'.
Notes. It may be necessary to create the queue and the subdeployment and to target it to a JMS server. But you do not have to do this for connection factory. In the webblogic10 sample application medrec, you can see from the admin console that three queues are configured. But there is no connection factory. But JMS won't work without a factory. So where is the factory? The medrec source code reveals the secret. It turns out that weblogic has two predefined factories that can be used. The JmsClientImpl.java in medrec defines the following:
private String connectionFactoryName = "weblogic.jms.XAConnectionFactory";
Then the code uses this name as the JNDI name to look up the connection factory. For more information, look at the weblogic document on it.
