JMS-Provider-Specific Settings
Use
Make specifications for the JMS provider. These specifications are the same for the receiver and sender adapter.
Prerequisites
...
1. You have created a new communication channel of adapter type JMS or have opened an existing one.
2. Select the JMS provider for the JMS adapter under Transport Protocol.
Features
SonicMQ JMS Provider
Field |
Value |
QueueConnectionFactory Java Class |
This is the SonicMQ implementation of the QueueConnectionFactory. A JMS client, in this case the adapter, uses a QueueConnectionFactory object to generate QueueConnection objects of a JMS provider. The default value for SonicMQ 3.0 is progress.message.jclient.QueueConnectionFactory. |
Queue Java Class |
A queue object encapsulates a provider-specific queue name. This enables a client to make the queue JMS API methods known. The default value for SonicMQ 3.0 is progress.message.jclient.Queue. |
IP Address or Server Name |
IP address or server name on which the JMS provider runs. The value is localhost it this is a local machine. |
Server Port |
|
JMS Queue |
Enter the name of the queue. |
WebSphereMQ (Non-JMS)
Field |
Value |
QueueConnectionFactory Java Class |
See above under SonicMQ JMS Provider. The default value for WebSphereMQ 5.3 is com.ibm.mq.jms.MQQueueConnectionFactory. |
Queue Java Class |
See above under SonicMQ JMS Provider. The default value for WebSphereMQ 5.3 is com.ibm.mq.jms.MQQueue. |
IP Address or Server Name |
|
Server Port |
|
Queue Manager Name |
Enter the display name of the queue manager. |
Channel Name |
Access channel for all queues |
JMS Queue |
|
Character Set ID (CCSID) for non-ASCII Names |
Specifies the character set for the above-specified name. This entry does not affect the character set of the transferred messages. |
Transport/Network Protocol |
TCP/IP The JMS adapter communicates with the MQ Series server using TCP/IP sockets. WebSphereMQ Communication takes place using dynamic libraries (Microsoft: files with the extension .DLL; Unix: files with the extension .SO or .SL).
In a 64-bit operating system, the libraries must also be 64 bit. If this is not the case, see SAP Note 790963.
|
JMS-Compliant |
Specify whether the receiver uses the JMS API or the WebSphereMQ API. |
Create Connection on Demand |
Allows you to create connection on demand/message basis. In the Keep Connection Alive Period text box, enter the duration for which you want the connection to be active. It takes the following values:
● Keep Alive = 0: Channel disconnects immediately after send is complete. ● Keep Alive > 0: Channel is scheduled to disconnect after the time duration specified in keep alive, once the message is sent.
¡ Connection on demand establishes connection only after the first message arrives. ¡ In case, another messages arrives when the existing keep alive period is not complete, the existing disconnect job gets terminated and a new disconnect job with the keep alive value is scheduled. Effectively, the connection gets extended based on the time of arrival of the new message. ○ If you do not use connection on demand, connections get established on a channel start. ○ Reconnection to the JMS provider in the event of a provider failure is not supported when you use the Connection On-Demand option.
|
Access JMS Provider with JNDI (Java Naming and Directory Interface)
You can use this setting to use the SAP JMS provider.
Field |
Value |
JNDI Lookup Name of QueueConnectionFactory |
See above under SonicMQ JMS Provider. The default value is jmsfactory/default/QueueConnectionFactory. |
JNDI Lookup Name of JMS Queue |
See above under SonicMQ JMS Provider. The default value is jmsqueues/default/sapDemoQueue. |
Name of JNDI Initial Context Factory |
Allows access to JNDI. If you want to use another registry, specify it here. For more information, see SAP Note 802754. The default value is com.sap.engine.services.jndi.InitialContextFactoryImpl. |
JNDI Server Address |
If you are using the SAP J2EE JMS provider, the following entry is sufficient: <host>:<port> If you want to use OpenJMS, for example, you must enter the following: http://<host>:<port>/ |
JNDI Logon User |
|
JNDI Logon Password (with confirmation) |
|
(Read) JMS Provider Administered Objects from File
A JMS provider must provide functions for serializing JMS-administrable objects as Java objects in a file. Connection and access parameters are set. The files must be copied to each cluster server.
Field |
Value |
File Name of Serialized QueueConnectionFactory Java Object |
|
File Name of Serialized Queue Java Object |
|
Access JMS Provider Generically
Enter parameters and values for the generic JMS provider in the table.
In the WebsphereMQ case, for example, the table contains the following values:
Name |
Value |
JMS.QueueConnectionFactoryImpl.classname |
com.ibm.mq.jms.MQQueueConnectionFactory |
JMS.QueueConnectionFactoryImpl.method.setHostName |
java.lang.String p24537 |
JMS.QueueConnectionFactoryImpl.method.setChannel |
java.lang.String JAVA.CHANNEL |
JMS.QueueConnectionFactoryImpl.method.setTransportType |
java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP} |
JMS.QueueConnectionFactoryImpl.method.setQueueManager |
java.lang.String QM_p24537 |
JMS.QueueImpl.classname |
com.ibm.mq.jms.MQQueue |
JMS.QueueImpl.constructor |
java.lang.String postcard |
JMS.QueueImpl.method.setTargetClient |
java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ} |