Integrate with Integrator

Activator can send messages to and pick up messages from the Integrator message translator via a JMS queue. This topic describes configuring Activator to integrate with Integrator, but does not include the Integrator tasks for integrating with Activator. Users of Integrator are advised to review the Integrator documentation.

Messages are moved between Activator and Integrator via a special JMS exchange named Axway Integrator. Setting up the Integrator application pickup or delivery exchange is almost like setting up any JMS application exchange. The difference is you must select Axway Integrator as the application pickup or delivery option in the exchange wizard. Integrator must be configured to use the same JMS queue as Activator.

JMS transport configuration describes the fields for configuring a JMS transport. However, for the Axway Integrator JMS transport, specific field values are recommended. The JMS provider used by Activator and Integrator is Axway Messaging. For this version of Activator, you must use Messaging 5.3.1.

When configuring integration with Integrator via the Axway Integrator transport, follow these guidelines when using the exchange wizard. The wizard already provides these as the default values.

Field

Recommended value

JMS type

Listener (integration pickup only).

JMS queue

For application delivery: queue/GI2IG

For application pickup: queue/IG2GI

If integrating with an Integrator earlier than 3.4.1:

For application delivery: queue/CI2XIB

For application pickup: queue/XIB2CI

This queue requires a user name and password

Do not select this option.

Use JNDI

Select this option.

JNDI URL

tcp://[host]:4569

The default value presumes Activator and Messaging are running on the same computer. If Messaging is on a different computer, substitute the fully qualified domain name or IP address of the computer.

JNDI factory

com.axway.xms.jms.XmsInitialContextFactory

This provider requires a user name and password

Do not select this option.

JMS connection factory

factory/QueueConnectionFactory

Use a custom Java implementation

Do not select this option.

Note: The Axway Integrator exchange only is for performing JMS integration with Integrator. If you do not want to integrate with Integrator, use a normal JMS exchange.

A special event router is created when adding an exchange for routing messages from partners to integration via the Integrator transport. The router moves metadata between Activator and Integrator. The metadata values allow each component to link messages exchanged between them. If Activator also is configured to integrate with Axway Sentinel, the metadata correlates the messages among all three components.

Related topics:

Message picked up from Integrator

Message sent to Integrator

Message picked up from Integrator

The following figure illustrates the flow when Activator picks up a message from Integrator.

 

 

 

The following steps describe the flow.

  1. Activator picks up a message from integration. Attached to the message as a string property are Integrator metadata elements. Activator changes the element names.

Integrator metadata

Activator changes to

TransferCorrelationId

ExternalCycleIdValue

SentinelTrackedObject

ExternalCycleIdTOName
  1. At the same time, Integrator can send events to Sentinel.
  2. Activator processes the message. If Sentinel integration is enabled, Activator sends events, but also sends information to link ExternalCycleIdValue to its newly generated SentinelCycleIdValue. Sentinel can use the information to link to the information received from Integrator in step 1.

Related topic:

Message sent to Integrator

Message sent to Integrator

The following figure illustrates the flow when Activator sends a message to Integrator.

 

 

The following steps describe the flow.

  1. Activator sends a message received from a partner to integration. Before doing so, Activator changes names of key metadata to Integrator-friendly names.

  2. Activator changes

    To Integrator-friendly metadata

    SentinelCycleIdValue

    TransferCorrelationId

    SentinelCycleIdTOName

    SentinelTrackedObject
  3.  
  4. If Sentinel integration is enabled, Activator sends events to Sentinel, but no transaction linking information is included.
  5. Integrator processes the message received from Activator. Integrator also can send events to Sentinel. The metadata Integrator sends links back to the metadata received from Activator.

Related topics:

Message picked up from Integrator