If you are using activation specifications, use the administrative
console to create and configure the activation specifications as described
in
Configuring an activation specification for the default messaging provider or
Creating an activation specification
for the WebSphere MQ messaging provider. Create two activation
specifications, one for each endpoint listener. The default JMS resources
and associated names that the synchronous SOAP over JMS endpoint listeners
expect are provided in the following table. However, you can use any
JNDI name for the activation specification, provided that the EAR
file has the same JNDI reference in the administrative console
"Binding
enterprise beans to listener port names or activation specification
JNDI names" panel. If you use different resources and names in
this step, change the defaults when you subsequently configure the
endpoint listener. You must also stop then restart the application
server.
Table 2. Default JMS resource and
associated name expected. The first column of this table
lists the JMS resources, the second column shows the expected default
JNDI names for endpoint listener 1, the third column shows the expected
default JNDI name for endpoint listener 2, the fourth column shows
the expected queue name for endpoint listener 1, and the fifth column
shows the expected queue name for endpoint listener 2.
JMS resource |
default JNDI name (endpoint listener 1) |
default JNDI name (endpoint listener 2) |
destination JNDI name (endpoint listener
1) |
destination JNDI name (endpoint listener
2) |
activation specification |
eis/SOAPJMSChannel1 |
eis/SOAPJMSChannel2 |
jms/SOAPJMSQueue1 |
jms/SOAPJMSQueue2 |
If you are using listener ports with any supported
JMS provider, use the administrative console to create and configure
the listener ports in the message listener service as described in
Adding a new listener port.
Create two listener ports (one for each endpoint listener). The default
JMS resources and associated names that the supplied SOAP over JMS
endpoint listeners expect are provided in the following table. If
you use different resources and names in this step, then change the
defaults when you subsequently configure the endpoint listener.
Table 3. Default JMS resources and expected names. The first column of this table lists the JMS resources, the
second column shows the expected default JNDI names for endpoint listener
1, the third column shows the expected default JNDI name for endpoint
listener 2, the fourth column shows the expected queue name for endpoint
listener 1, and the fifth column shows the expected queue name for
endpoint listener 2.
JMS resource |
default name (for use with SOAP over JMS endpoint listener
1) |
default name (for use with SOAP over JMS endpoint listener
2) |
listener port |
SOAPJMSPort1 |
SOAPJMSPort2 |
connection factory |
jms/SOAPJMSFactory1 |
jms/SOAPJMSFactory2 |
destination |
jms/SOAPJMSQueue1 |
jms/SOAPJMSQueue2 |