Creating the JMS target

Copy the bindings file created in Configuring the JMS-configuration directory to the directory where you want it to reside. If you want to preserve the JMS context, copy the subfolder (with the same name as the context) and the bindings file to the directory, so that the full path to the bindings file is as follows:

/parentDirectory/contextSubdirectory/.bindings

A sample path for the bindings file is:

/mydir/myctx/.bindings

From the Targets screen of the Community Console, create a target, specifying the following information shown in Table 115

Table 115. Information for Target Details screen of the Community Console

Field name Value Example
Transport JMS Same
JMS Provider URL

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 JMS Provider URL:

file://C:/filesender/config/jms
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 JMS Provider URL field:

  • If the JMS Provider URL includes the context name, you do not need to provide the context name as part of the JMS queue alias name.
  • If the JMS Provider URL does not include the context name, you must provide it in the JMS queue alias name, in the form:
    JMScontext/JMSqueueAlias
    
inQ
JMS Factory Name

The queue connection factory. You specified this name with the define qcf command when creating the bindings file. This factory name is relative to the path you specified in the JMS Provider URL field:

  • If the JMS Provider URL includes the context name, you do not need to provide the context name as part of the JMS factory name.
  • If the JMS Provider URL does not include the context name, you must provide it in the JMS factory name, in the form:
    JMScontext/JMSfactory
    
WBICHub
JNDI Factory Name
com.sun.jndi.fscontext.RefFSContextFactory
Same

Note:
The target must be able to access the directory where the subfolder and JMS bindings file are located.

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

Copyright IBM Corp. 2003, 2004