The Response Mail Receiver now supports a JMS channel in addition to the POP and SOAP channels for message download. When used with a JMS queue provider, the Response Mail Receiver allows for inbound and outbound delivery of mail via JMS.
Download and receive messages from JMS Queues.
Send and upload messages to JMS Queues.
Configure separate JMS queues for upload and download (Secure Channel).
Specify SMTP as outbound channel with JMS Queue for an inbound channel (Non-secure Channel).
BASE64 encode/decode while sending and receiving messages to and from the JMS Channel.
Support for IBM systems by incorporating EBCDIC to ASCII conversion after reading a message from the JMS Channel. Both conversion requirements must be configurable and allow the administrator to enable and disable them.
Before using the JMS feature, these prerequisite steps must be followed:
Copy the JMS client library files (jar or zip files) provided by the messaging software (MQ, JBoss, and so on.) over to the Response Server machine.
Add the JMS client library files to the classpath for Response:
For UNIX, the "setkanaenv.sh" script file needs to be modified.
For Windows, users will need to use "regedit" to modify the Response classpath.
Here is an example of WebSphere MQ JMS client library files that need to be copied to the Response server machine:
com.ibm.mq.jar
com.ibm.mqjms.jar
dhbcore.jar
Here is an example of JBoss JMS client library files that need to be copied to the Response server machine:
jnp-client.jar
jbossmq-client.jar
jboss-common-client.jar
jbossall-client.jar
jboss-client.jar
Additionally, consult your messaging software’s documentation for exact library files needed for JMS client communication.
After the steps are completed, you must restart the Response Server.
Users can then proceed to configuring the JMS Mailbox in the System Admin Client. Refer to the JMS Mailbox Dialog for help on setting up a JMS Mailbox.