Java Message Service (JMS)
Table 1 shows the Java™
Message Service (JMS) properties for Distribution Manager.
| Parameter | Values (Default) | Description |
|---|---|---|
| jmsStart | true or false (true) | Controls whether the JMS message server is started or not. If set to false, messages are not published to the servers and the server data is not refreshed automatically. |
| jmsUseJNDI | true, false (false) | Controls the use of JNDI lookup. If set to true, JNDI lookup is used to get a TopicConnectionFactory object and a Topic object. If set to false, straight WebSphere® MQ calls are used to get an MQConnection. If using JNDI, the jmsURL, jsmInitialContext, and jmsConnectionFactory properties must be set. If not using JNDI, the jmsHostName, jmsChannelName, jmsPortNum, and jmsQmgrName properties must be set. |
| jmsPublishTime | 86400000 | The number of milliseconds a message stays on the subscriber queue before it expires. It allows servers which are not active when a message is published to receive the message when the server is started before the message has expired. The default is 24 hours. |
| jmsURL | C:/JNDI | The URL for the JNDI provider |
| jmsInitialContext | com.sun.jndi.fscontext.RefSContextFactory | The name of the initial context factory to use to create the initial context used for JNDI lookups. Refer to the documentation for the associated JNDI provider. |
| jmsConnectionFactory | TCF_PayDir | The name of the TopicConnectionFactory created in the JNDI name space to house the messages published by the Distribution Manager |
| jmsCCDT | MQCCDT.TAB | The file name for the MQ client channel definition table (CCDT) file to use. If a file name
is specified in this property, the host name, port, channel, and client properties in this configuration are
not used. For secure connections, the cipher suite property is ignored when a file name is specified in this property. The properties relating to the key store and trust store must still be provided. For more information about specifying the name of the CCDT file, refer to Providing the MQ client channel definition table (CCDT) file name property. |
| jmsHostName | HOST1 | The host name or address of the server where the WebSphere MQ queue manager resides |
| jmsChannelName | S_HOST1 | The WebSphere MQ channel name |
| jmsPortNum | 1415 (1414) | The port number on which the WebSphere MQ listener is listening |
| jmsQmgrName | QM_HOST1 | The name of the WebSphere MQ queue manager being used to house messages published by the Distribution Manager |
| jmsClient | false | Target JMS system is a client system. |
| jmsCipherSuite | SSL_RSA_WITH_3DES_EDE_CBC_SHA | The name of the JSSE CipherSuite associated with the WebSphere
CipherSpec specified for the user’s WebSphere MQ queue
manager. For more detailed information, refer to Table 2. |
| jmsKeyStore | C:/keys/mqkey.jks | The fully qualified name of the file containing the key store |
| jmsKeyStorePassword | password | The password used to access the key store |
| jmsTrustStore | C:/keys/mqkey.jks | The fully qualified name of the file containing the trust store |
| jmsUserId | N/A | The user ID used to access the WebSphere MQ queue manager |
| jmsPassword | N/A | The password used to access the WebSphere MQ queue manager |
Table 2 shows the corresponding CipherSuite names for the
CipherSpec name specified in WebSphere MQ configuration. Set the
jmsCipherSuite property in the Distribution Manager configuration file to the CipherSuite name that
matches the CipherSpec being used.
| CipherSpec | CipherSuite |
|---|---|
| NULL_MD5 | SSL_RSA_WITH_NULL_MD5 |
| NULL_SHA | SSL_RSA_WITH_NULL_SHA |
| RC4_MD5_EXPORT | SSL_RSA_EXPORT_WITH_RC4_40_MD5 |
| RC4_MD5_US | SSL_RSA_WITH_RC4_128_MD5 |
| RC4_SHA_US | SSL_RSA_WITH_RC4_128_SHA |
| RC2_MD5_EXPORT | SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5 |
| DES_SHA_EXPORT | SSL_RSA_WITH_DES_CBC_SHA |
| RC4_56_SHA_EXPORT1024 | SSL_RSA_EXPORT1024_WITH_RC4_56_SHA |
| DES_SHA_EXPORT1024 | SSL_RSA_EXPORT1024_WITH_DES_CBC_SHA |
| TRIPLE_DES_SHA_US3 | SSL_RSA_WITH_3DES_EDE_CBC_SHA |
Providing the MQ client channel definition table (CCDT) file name property
A CCDT file contains information that defines an MQ channel. If you generated a CCDT file for this Payment Feature Services component or function, copy the CCDT file to a directory location that can be accessed by the component. The name of the CCDT file for this component must be specified in the CCDT property for the component.
The CCDT property for the Payment Feature Services components is specified as
follows:
CCDTpropertyname = filespec- CCDTpropertyname
- is the name of the property for this Payment Feature Services component.
- filespec
- is the name of the CCDT file that was created for this component. The filespec can be
specified in any of the following formats:
- File name without a path
- The CCDT file must be in a directory that is found using the class path. An example of this format is:
CCDTpropertyname = MQCCDT.TAB - File name using a relative path
- The relative path depends on the specific directory structure. In the following example, the CCDT file is
in the profiles directory that is a peer of the current
directory.
CCDTpropertyname = ../profiles/MQCCDT.TAB - File URL
- Providing the file name as a file URL is supported. Examples of this format are:
- For AIX: CCDTpropertyname = file:///home/ftm/shared/v304/pfs/componentdirectory/properties/MQCCDT.TAB