Creating the JMS gateway

From the Gateways screen of the Community Console, create a gateway, specifying the information in Table 116

Table 116. Information for Gateway Details screen of the Community Console

Field name Value Example
Transport JMS Same
Target URI

The file-system path to the JMS-configuration directory, where the context subfolder (if there is a context) and the bindings file are located, in the following form:

file://JMSConfigDirectory

where JMSConfigDirectory is the full pathname. Optionally, this JMSConfigDirectory can contain the context subdirectory, where the .bindings file resides.

This value includes the JMS context in the Target URI:

file://C:/filesender/config/jms
JMS Factory Name

The JMS factory name that you specified when creating the JMS bindings file. This factory name is relative to the path you specified in the Target URI field:

  • If the Target URI includes the context name, you do not need to provide the context name as part of the JMS factory name.
  • If the Target URI does not include the context name, you must provide it in the JMS factory name, in the form:
    JMScontext/JMSfactory
    
WBICHub
JMS Message Class

One of the following JMS message classes:

  • StreamMessage
  • BytesMessage
  • TextMessage

Depends on message class supported by back-end system

JMS Queue Name

The JMS queue alias name that you specified when creating the JMS bindings file. This queue alias name is relative to the path you specified in the Target URI field:

  • If the Target URI includes the context name, you do not need to provide the context name as part of the JMS queue alias name.
  • If the Target URI does not include the context name, you must provide it in the JMS queue alias name, in the form:
    JMScontext/JMSqueueAlias
    
outQ
JNDI Factory Name
com.sun.jndi.fscontext.RefFSContextFactory
Same

In Table 116, the Example column lists the gateway values for the JMS configuration defined by Figure 31 and Figure 32.

Copyright IBM Corp. 2003, 2004