Integration Components
136
Integration Guide
T
File split - Multi-noun files that are processed by the
FLATFILECONSUMER cron task are split before they are written to the
queue. The cron task identifies if the file that is loaded is a multi-noun
XML file. If the XML file is a multi-noun file, the integration framework
uses the enterprise service key columns to identify where the file split
occurs. For example, PONUM and SITE in the MXPOInterface enterprise
service.
T Queue processing - The FLATFILECONSUMER cron task identifies the
queue in which the flat file is loaded. The location is based on the queue
(continuous or sequential) specified at the external system and enterprise
service level.
The cron task creates an index file (recovery_filename.txt) that contains a
reference to the last successfully processed noun when you process a multi-noun
file. The entry in the index file is updated when the noun is successfully
committed to the queue. Index files are available in the RECOVERY folder which
is created in the cron task source directory.
The FLATFILECONSUMER cron task uses the index file name to identify the file
that was processed before the server or queue problem was encountered. The
cron task continues to process the XML file starting at the last successfully
committed noun in the index file. Errors that are identified after a message is
successfully written to an inbound queue must be resolved in the Message
Reprocessing application.
Integration Components
To configure the integration framework.
Configuring External Systems
Use the System tab in the External Systems application to perform the following
configuration activities:
1 Create an external system.
2 Identify the queues to the external system.
3 Assign an endpoint to the external system.
Use the Enterprise Services and Publish Channels tabs in the External Systems
application to perform the following configuration activities:
1 Add enterprise services and publish channels to the external system.
2 Disable unused enterprise services and publish channels.
3 Specify the inbound JMS queue the enterprise services use.
4 Optional: Specify the endpoint that the publish channel uses to override the
external system endpoint.
To Next Page
Loading...