Install the JMS Interface

This topic provides a high-level overview on how to add JMS support to the gateway. It assumes that the target middleware system has been correctly installed and configured and that you are familiar with the JMS specifications.
gateway92
This topic provides a high-level overview on how to add JMS support to the
Layer7 API Gateway
. It assumes that the target middleware system has been correctly installed and configured and that you are familiar with the JMS specifications.
The Gateway can work with various message-oriented middleware (MOM) systems, including:
  • TIBCO EMS
  • IBM MQ
  • MQ Native
  • JMS over MQ
  • webMethods Broker
  • WebLogic JMS
  • WebSphere JMS
For the supported versions, see "Message Queuing Products" in Requirements and Compatibility
The MOM systems are accessed through the JMS interface. To enable JMS destinations on the Gateway, you must install the appropriate client libraries first.
Contact your middleware system provider for the client libraries. Due to licensing issues, these libraries are not included with the
Layer7 API Gateway
.
Required Client Libraries
For IBM MQ v7.1.x, the following libraries are required:
MQ Native
  • com.ibm.mq.jar
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.pcf.jar
  • connector.jar
JMS using MQ
  • com.ibm.mq.jar
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mqjms.jar
  • connector.jar
  • dhbcore.jar
  • jms.jar
  • jta.jar
If a .bindings file is being used to configure a JMS destination, ensure these files are also included:
fscontext.jar
and
providerutil.jar
. These files may be obtained from the IBM MQ client.
For IBM MQ 8.0, the following libraries are required:
MQ Native:
  • com.ibm.mq.allclient.jar
  • com.ibm.mq.traceControl.jar        
  • fscontext.jar                                       
  • jms.jar                                                  
  • providerutil.jar
Technical Note:
When configuring for IBM MQ 8.0, if any "TLS_ECDHE_ECDSA" cipher suite is used, the IBM MQ 8 server certificate must be encrypted using the ECDSA algorithm. If using the IBM Key Management to generate a certificate, use the SHA512withECDSA algorithm to generate the certificate.
 
For TIBCO EMS, the following libraries are required:
  • tibjmsapps.jar
  • tibjmsadmin.jar
  • tibrvjms.jar
  • tibjms.jar
  • tibcrypt.jar
To use an SSL connection with the EMS server, ensure these libraries are in the CLASSPATH:
  • tibcrypt.jar
  • slf4j-api-1.5.2.jar
  • slf4j-simple-1.5.2.jar
These JAR files are included with the TIBCO Enterprise Message Service installation.
Installing the Client Libraries
To install the client libraries:
  1. Access the Gateway main menu.
  2. Copy the appropriate client libraries using SCP to the following directory:
    /home/ssgconfig
  3. Move the client libraries:
    from:
    /home/ssgconfig
    to:
    /opt/SecureSpan/Gateway/runtime/lib/ext
    And then change the permissions and owner:
    # chmod 644 /opt/SecureSpan/Gateway/runtime/lib/ext/*.jar
    # chown layer7.layer7 /opt/SecureSpan/Gateway/runtime/lib/ext/*.jar
  4. (Perform this step only for IBM MQ 8.0 with an SSL connection)
    Update the
    system.properties
    file:
    1. Open this file in a text editor:
      /opt/SecureSpan/Gateway/node/default/etc/conf/system.properties
    2. Add these lines to the properties file:
      com.ibm.mq.cfg.useIBMCipherMappings=false
      com.ibm.mq.cfg.preferTLS=true
    3. Save and exit the file.
  5. Restart the Gateway:
    # service ssg restart
Configuring the JMS Destinations
The JMS interface is enabled when the Gateway is restarted. You can now: