Setting up a JMS target

A JMS target polls a JMS queue (according to the schedule you specify) to look for new documents.

The following steps describe what you need to specify for a JMS target.

  1. Click Hub Admin > Hub Configuration > Targets to display the Targets List page.
  2. From the Target List page, click Create Target.

Target Details

In the Target Details section, perform the following steps:

  1. Type a name for the target. For example, you might call the target JMSTarget1. This is a required field. The name you enter here will be displayed on the Targets list.
  2. Optionally indicate the status of the target. Enabled is the default. A target that is enabled is ready to accept documents. A target that is disabled cannot accept documents.
  3. Optionally enter a description of the target.
  4. Select JMS from the Transport list.

Target Configuration

In the Target Configuration section of the page, perform the following steps:

  1. Optionally indicate the gateway type. The gateway type defines the nature of the transmission. For example, if you want to test a document exchange before putting it into production, you would enter Test. The default is Production.
  2. Enter the JMS provider URL. This should match the value you entered (the file system path to the bindings file) when you configured WebSphere Partner Gateway for JMS (step 5). You can also specify the subfolder for the JMS context as part of the JMS provider URL.

    For example, without the JMS context, you would enter c:/temp/JMS. With the JMS context, you would enter c:/temp/JMS/JMS.

  3. Enter the user ID and password required to access the JMS queue, if a user ID and password are required.
  4. Enter a value for JMS queue name. This is a required field. This name should match the one you specified with the define q command when you created the bindings file (step 4).

    If you entered the subfolder for the JMS context in step 2, enter only the queue name here (for example, inQ). If you did not enter the subfolder for the JMS context in the JMS provider URL, specify the subfolder before the factory name (for example, JMS/inQ).

  5. Enter a value for the JMS factory name. This is a required field. This name should match the one you specified with the define qcf command when you created the bindings file (step 4).

    If you entered the subfolder for the JMS context in step 2, enter only the factory name here (for example, Hub). If you did not enter the subfolder for the JMS context in the JMS provider URL, specify the subfolder before the factory name (for example, JMS/Hub).

  6. Optionally enter the Provider URL package.
  7. Enter the JNDI factory name. If you do not enter anything, the value com.sun.jndi.fscontext.RefFSContextFactory is used. This is a required field.
  8. Optionally enter a value for Time Out, to indicate the number of seconds the target will monitor the JMS queue for documents. This field is optional.
  9. Optionally enter a value for Thread Nbr, to indicate the number of documents the Document Manager will process simultaneously. The default value of 1 is recommended.

For example, if you wanted to set up a JMS target to match the JMS configuration example in Configuring the hub for the JMS transport protocol, you would:

  1. Enter the value JMSTarget in the Target Name box.
  2. Enter the value file:/C:/TEMP/JMS/JMS in the JMS Provider URL box.
  3. Enter the value inQ in the JMS Queue Name box.
  4. Enter the value Hub in the JMS Factory Name box.

Handlers

If you will be receiving files containing multiple EDI interchanges or XML or ROD documents that need to be split, configure the appropriate splitter handler in the Preprocess configuration point.

To modify configuration points for this target, go to Modifying configuration points. Otherwise, click Save.

Copyright IBM Corp. 2003, 2005