Adding an Integrator Sentinel CommAdapter

About the Integrator Sentinel CommAdapter

Prerequisites

Procedure

About the Integrator Sentinel CommAdapter

The Integrator Sentinel CommAdapter provides the services that enable Integrator to send Tracked Object messages to Sentinel.

This CommAdapter uses a dedicated processing task on the Integrator Server which we create as part of the procedure. This configuration step is optional, but it is recommended because it improves the performance of the Sentinel connector by reserving dedicated processes.

Prerequisites

The Integrator Axway Server object and CommNetwork must exist in Composer.

To monitor custom Tracked Object messages when using an overflow file, define a separate overflow file for each processing task running the DML activity . To do this, edit $CORE_LOCAL/config/environment.dat and set a SENTINEL_OVERFLOWFILE environment variable for each processing task.

Procedure

1. In the Composer Topography workbench, open the Integrator Axway Server object.
2. On the Core Tasks tab of the Axway Server properties window, create a processing task dedicated to Sentinel.
   This step is mandatory. By creating a dedicated processing task for the Sentinel CommAdapter you improve the performance of the Sentinel connector by reserving dedicated processes.
3. On the Communication tab, right-click the CommNetwork and select add a CommAdapter. Select Sentinel QLT-XML for the CommAdapter type.
4. Complete the Communication / Configuration sub-tab
   • Select the Enable check box
   • Leave the default values for the other parameters
   • To configure an overflow file, select a mode (direct or batch):
     • Select Use overflow file
     • Select a mode: Direct In Direct mode, Integrator sends notifications directly to Sentinel. Integrator uses the overflow file to store notifications only if the Sentinel Server is not available. or BatchIn batch mode, Integrator stores notifications in the overflow file, even if the Sentinel Server is available. Those notifications are then sent to the Sentinel Server when the overflow file reaches its limit, or during periods of system inactivity
     • Set an overload file maximum size limit
5. Note: To use an overflow file with custom Tracked Objects, you must first define a separate overflow file for each processing task running the DML activity . See the "Prerequisites" section, above.
5. On the Task references sub-tab, select the processing task you created in step 2 of this procedure.
6. Check, save and close the Axway Server object.
7. Send the Axway Server object to the execution server via the Send to Server command. The status of the Axway Server is set to "committed".
8. Note: Since the Integrator Sentinel CommAdapter is a client CommAdapter, there is no need to create a CommPoint.