Securing JMS connections and JNDI lookups

If you want additional security for JMS connectivity and the JMS nodes or SOAP nodes using JMS transport, two configuration options are supported.

About this task

When you include JMS nodes in your message flow, you can optionally secure JMS connection resources. You can secure one, both, or neither of these options, depending on the level of security and access that you want to enforce.

Procedure

  1. To secure a JMS connection:
    1. Specify the Connection Factory Name property on the node.
      You must set this property for every node using JMS transport.
    2. Use the mqsisetdbparms command to authorize the user ID and password for the specified connection factory.
      For example:
      mqsisetdbparms MyBroker1 -n jms::tcf1 -u myuserid -p secret
      where tcf1 is the name of the connection factory that matches the node property that you set.
  2. To secure JNDI bindings lookups:
    1. Specify the Initial Context Factory property on the node.
      You must set this property for every node using JMS transport.
    2. Use the mqsisetdbparms command to authorize the user ID and password for the specified context factory.
      For example:
      mqsisetdbparms MyBroker1 -n jndi::com.sun.jndi.fscontext.RefFSContextFactory 
     -u myuserid -p secret
      where com.sun.jndi.fscontext.RefFSContextFactory is the name of the initial context factory that you set.