XML Trading Partner Event Configuration
An XML Event relates to a trading relationship linking a single Trading Partner and Business Transaction to form an Event. XML Event Configuration is required to link a Trading Partner with Transaction to configure the communications method, Source/Destination folders, communication/application identifiers, trigger programs, Event owner and Trading Partner information.
The set up and configuration of XML Events is required before Inbound or Outbound XML transactions can be processed using the ECS/XML Processor integrated with ECS/integrated email.
To configure an XML Event, perform the following:
Inbound XML Event
The following describes the requirements of adding a definition for an Inbound XML Event:
The ECS/XML Processor can be configured to execute a Trigger Program following the successful parsing and conversion of an inbound XML Document. The Trigger Program is a user developed AS/400 based program, not supplied with ECS/integrated email. The Trigger Program could reference an application mapping program designed to map the data from the ECS/XML Transaction database to the Business Application system.
The ECS/XML Processor can be configured to execute a Trigger Program on Error following the unsuccessful parsing of an inbound XML Document. The Trigger Program on Error is a user developed AS/400 based program designed for remedial action to be taken in the event of a failure.
The Input Folder must contain the full path details of where the ECS/XML Processor retrieves the inbound XML Documents from. This could be the same path that was used as the destination folder for Inbound e-folders if the XML Document was received by email. Example of an Input Path path is: C:\XML\IN\
The Error Folder must contain the full path details of where the ECS/XML Processor places inbound XML Documents if they fail the validation. Example of an Error Folder path is: C:\XML\IN\ERROR\ .
The Processed Folder must contain the full path details of where the ECS/XML Processor places inbound XML Documents when they have been successfully processed. Example of a Processed Folder path is: C:\XML\IN\PROCESSED\ .
Every XML Event should have an administrator that is responsible for dealing with any errors caused while processing Inbound XML Documents relating to this Event. All error reports will be automatically emailed to the email address stored within the Administrators email address entry and the emails will be sent with the subject text entered in Error email subject text text box.
The Element Translation command button enables the maintenance of the element translation table relating to this XML Event.
Click OK to add the Event or Cancel to return to the XML Event list without updating the record.
The following window displays an example of a completed XML record for Inbound processing:
Outbound XML Event
The following describes the requirements of adding a definition for an Outbound XML Event:
The ECS/XML Processor can be configured to execute a Trigger Program following the successful creation and parsing of an outbound XML Document. The Trigger Program is a user developed AS/400 based program, not supplied with ECS/integrated email. The Trigger Program could reference an application mapping program designed to map the data from the ECS/XML Transaction database to the Business Application system.
The ECS/XML Processor can be configured to execute a Trigger Program on Error following the unsuccessful parsing of an outbound XML Document. The Trigger Program on Error is a user developed AS/400 based program designed for remedial action to be taken in the event of a failure.
The Output Folder must contain the full path details of where the ECS/XML Processor places Outbound XML Documents when they have been successfully processed. This path can be the same as the source folder used within Outbound e-folders if it is intended that the XML document is sent to the Trading Partner as an email attachment. Example of an Output Folder path is: C:\XML\OUT\ .
The Error Folder must contain the full path details of where the ECS/XML Processor places Outbound XML Documents if they fail the XML Parser validation. Example of an Error Folder path is: C:\XML\OUT\ERROR\ .
Every XML Event should have an administrator that is responsible for dealing with any errors caused while processing Outbound XML Documents relating to this Event. All error reports will be automatically emailed to the email address stored within the Administrators email address entry and the emails will be sent with the subject text entered in Error email subject text text box.
The Element Translation command button enables the maintenance of the element translation table relating to this XML Event.
The Header and Footer command buttons enables the maintenance of the fixed Header and Footer text relating to this Outbound XML Event.
Click OK to add the Event or Cancel to return to the XML Event list without updating the record.
The following window displays an example of a completed XML record for Outbound processing:
<<<<< Back to ECS/XML Menu <<<<<
Copyright © 1998-2003 Electronic Commerce Solutions All rights reserved.
ECS/integrated email & ECS/ie are trademarks of Electronic Commerce Solutions, Ltd. Other brand names and product names used in this document are the trademarks and trade names of their respective holders and may be registered.