This chapter describes the steps required to install and configure the Axway Synchrony EDI (Electronic Data Interchange) Gateway so it can operate correctly with Argus Interchange.
Note:
Either B2B or Axway Synchrony is required for E2B reports exchange. You can choose any one of the software, as required.You may install EDI Gateway and Interchange Service in any order.
Log in to the database server as an Admin user.
Create a blank Axway Synchrony instance, if it does not already exist.
Connect to the Axway Synchrony Instance created in Step 2.
Create an Axway Synchrony DB User identified by the Axway Synchrony DB password.
Provide the following grants to the Axway Synchrony DB user:
Grant CREATE PROCEDURE
Grant CREATE SESSION
Grant CREATE TABLE
Grant CREATE VIEW
Grant UNLIMITED TABLESPACE (Optional)
Grant CREATE SEQUENCE
Alter user Axway Synchrony DB User default tablespace USERS.
Grant CONNECT
Grant RESOURCE
Log in to Axway Synchrony schema and create the following indexes to improve the interface performance between Argus Interchange and Axway Synchrony:
create index fbi_mes_confilename on messageeventsnapshots (direction, upper(consumptionfilename));
create index fbi_mes_coreid on messageeventsnapshots (upper(coreid), messageid)
Before starting and configuring Axway Synchrony Interchange, you must install Axway Interchange. For more information, see the Axway Interchange installation documentation.
Log in to the computer as an Admin user.
Go to Start > Applications > Services.
Double-click the GatewayInterchageService.
The GatewayInterchangeService Properties dialog box appears.
To start the Service Status, click Start and click OK.
You may also start the Axway Synchrony Server from the command prompt.
To start the Axway Synchrony Server from the command prompt, select Start > Programs > Axway Synchrony > Start Server.
The Start Server dialog box appears.
Note:
The first time you perform this task, the system creates tables in the database. This dialog box is different on subsequent executions. Do not close this dialog box until the Server Startup Complete status appears.Log in to a client computer.
From the browser, go to (Sender or Receiver) http://<Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting Started screen, hover the Trading Configuration icon and select Recent Communities > Manage Trading Configuration from the menu.
In the Pick a community screen, click Add a community.
In the Choose the source screen:
Click Next >> to continue.
Click the Manually create a new community profile option button.
Enter the parameters.
Click Yes to add a certificate.
Note:
This information is entered for both the sender and the receiver, but initially for the sender.Click Finish.
In the Add a certificate screen, click Create a self-signed certificate and click Next >>.
In the Enter the certificate information screen, click Next >>.
In the Review request screen, click Next >>.
In the View certificate details screen:
Check Make this the default encryption certificate.
Check Make this the default signing certificate.
Click Finish.
Hover the Trading Configuration icon, from the drop-down menu, select the recent Communities > <community>.
In the Summary screen, click the Setup up a pickup for receiving messages from partners.
In the Choose message protocol screen, select the EDIINT AS2 (HTTP) option and click Next >>.
In the Choose HTTP transport type screen, click Next >>.
In the Configure URL screen, click Next.
In the Exchange Name screen, enter the Exchange Name and click Finish.
In the Summary screen, click Application Delivery and add an application delivery.
In the Choose transport protocol screen, select the File system option and click Next >>.
In the Configure the file system settings screen, click Next.
In the Exchange Name screen, enter the Exchange Name and click Finish.
Go to the Summary Page and click Configure the settings for application delivery.
In the Select application delivery screen, select Name and click Finish.
You can configure transmission for binary files such as PMDA zip files and E2B attachments.
To configure Axway Synchrony for binary file transmission:
Log in to a client computer.
From the browser, go to (Sender or Receiver): http://<Axway SynchronyServer>:6080/ui.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting Started screen, hover the Trading Configuration icon and from the drop-down menu, select Recent Communities > <community>.
In the Summary screen, click the Application Pickup icon and add an application pickup.
In the Choose transport protocol screen, click File system option and click Next >>.
In the From address and To address screens, click Next >>.
Address must be determined by either message attribute configuration or by protocol address only.
In the Configure the file system settings screen, on the Sender's Axway Synchrony Server, locate Common/Out folder and create the following folder structure:
Common\Out\Sender's Routing ID\Receiver's Routing ID
In the Exchange Name screen, enter the Exchange Name and click Finish.
In the Change this application pickup exchange screen, click the Message attributes tab.
In the Message attribute directory mapping tab:
The system moves them to the Selected attributes list.
Select From routing ID and To routing ID and click Add.
Locate the Available Attributes list.
Click the From address tab.
Click To address tab, select the Address determined by message attribute configuration option or by protocol address only and click Save Changes.
On the Sender's Axway Synchrony Server, locate Common/Out folder and create the following folder structure:
Common\Out\Sender's Routing ID\Receiver's Routing ID
Note:
This completes the folder configuration for outgoing binary transmissions. Since binary file transmission configuration is based on these folder names, each combination of Sender and Receiver Routing ID must be unique for binary file transmission to different trading partners.The Binary file should be dropped in the RECEIVER's Routing ID Folder which is the last folder. Although in the Axway Synchrony GUI the Integration Pickup folder will show up only ..\common\out.
For incoming binary transmissions, repeat steps 5 - 8 for Integration Delivery.
Repeat steps 1 - 12 for setting up the Receiver Axway Synchrony.
From the browser, go to http://<Receiver Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter Axway Synchrony User ID and Password, and click Login.
In the Getting started screen, hover the Trading Configuration icon and from the drop-down menu, select Recent Communities > <community>.
In the Summary screen, click Export this community as a partner profile at the bottom of the page.
Save the file to your local hard drive and close the Save dialog box.
Click Logout in the upper right corner of the page.
From the browser, go to http://<Sender Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting Started screen, hover the Trading Configuration icon and select Recent Communities > <community> from the menu.
In the Summary screen, click the Add a Partner to this community link.
In the Choose the source screen, select the Import the profile information from a file option and click Next >>.
In the Enter profile path screen, click Browse to navigate to the saved file and click Finish.
In the Successful profile import screen, click Close.
Note:
If you receive a summary where the Routing ID is not displayed, you must add the sender's Routing ID manually, as listed from Steps 9 - 12.In the Summary screen:
Click the Partners menu item and select the newly imported partner.
Hover the Trading Configuration icon.
From the drop-down menu, click Set up a routing ID.
In the Routing IDs screen:
Click Add.
Type the partner (sender) routing ID in the Routing ID field.
Verify that the partner does not have a routing ID.
The new routing ID is added to the page.
Hover the Trading Configuration icon.
Select Recent Communities > <community> from the menu.
In the Summary screen, select the sender partner.
In the Summary: Sender screen, click the Default delivery exchange link.
In the Change this delivery exchange screen, click the HTTP Settings tab, and verify that the URL is correct and that the correct routing ID for the send is appended to the end of the URL
From the browser, go to http://<Sender Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting started screen, click the System Management icon.
In the System Management screen, click Add a node.
In the Add a node screen:
Click Add.
Select the machine to add the node to from the Computer name drop-down list.
Click the Trading Engine option.
When the System management page opens with the newly created node:
Click Start to start the node.
The system updates System management page.
The status of the node changes to Starting.
The system updates the System management page.
The status of the node changes to Running.
Click Home and verify that the node status is Running.
Repeat the procedure to set up the Receiver Axway Synchrony.
From the browser, go to http://<Receiver Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting Started screen, hover the Trading Configuration icon and select Manage trading configurations from the menu.
In the Community screen, click the Community name.
In the Summary screen, click the Certificates link.
In the Certificate screen, click the Certificate listed on the Personal certificates tab.
Note:
Click the Trusted root certificates tab to verify that no certificates exist for the Sender or Receiver Axway Synchrony.Skip this section if a valid trusted root certificate already exists in the Name section on the Trusted root certificates tab.
In the View certificate screen, in the General tab, locate the Related task section and click Export this certificate.
In the Choose the format you want to use for the certificate export screen, retain the default configurations.
Click Export certificate.
Click the Cryptographic Message Syntax Standard PKCS #7 option button.
Select the Include all certificates in the certification path if possible checkbox.
Save the file to the Sender's local hard drive and click Logout in the upper right corner of the page.
From the browser, go to http://<Sender Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting Started screen, hover the Trading Configuration icon and select Manage trading configurations from the menu.
In the Community screen, click the Community name.
In the Summary screen, click the Certificates link.
In the Certificate screen, click the Trusted root certificates tab and click the Add a trusted root certificate link.
Note:
It is possible that the Trusted Root Certificates for the Receiver Axway Synchrony Server may already be on the Sender Axway Synchrony Server.In the Add a certificate screen, click Next >>.
In the Locate the certificate file screen, click Browse to locate the P7B certificate file saved for the Receiver Axway Synchrony Server and click Next >>.
In the View certificate details screen, click Finish.
In the Pick a certificate screen, click the Trusted root certificates tab.
Verify that the certificate you added appears on the list.
Log out of the Sender Server.
Repeat the procedure to register the Sender's certificate on the Receiver Server as a Trusted Root Certificate.
Note:
JVM argument is not applicable in version 5.12. Hence, only edit the Event.xml.To configure Event.xml on Client machine:
Log in to a client computer.
Using Windows Explorer, go to the local directory containing the Argus Safety installation files and navigate to ..\DBInstaller\Utilities\Cyclone.
Locate and double-click the cyclone_setup.bat file to open a DOS command prompt window.
In the Oracle SQL+ screen:
Enter the Axway Synchrony instance in the TSNAMES entry.
Enter the Axway Synchrony DB User Name in the Axway Synchrony User Name.
Enter the Axway Synchrony Schema User in the [USERS].
Enter the Axway Synchrony User Password in the Password for User Axway Synchrony_USER.
When SQL+ connects to the specified database, enter the log file name and the Directory name.
When the process is complete, the SQL+ window and DOS command prompt window close.
To configure Event.xml on Receiver machine:
Log in to the Receiver Server.
Using Windows Explorer, navigate to <Axway Synchrony Install Folder>\conf folder\.
Take a backup of the Events.xml file and rename it Events.xml.bak.
Right-click the Events.xml file and select Edit to display it in Notepad.
Locate the <EventRouters> section and add the following code:
<EventRouter id="ARGUS Events" class = "com.cyclonecommerce.relsys.router.GetEventInfo" active="true"> <Parameters file="../logs/ARGUS.log" rollOnStart= "true" autoFlush="true" maxFileSize="2M" maxBackupFiles="5"/> <MetadataProcessorListRef ref="Messaging"/> <EventFilterRef ref="ARGUS"/> </EventRouter>
Add the following section in the Events.xml file in the <EventFilters> section:
<EventFilter id="ARGUS"> <OrFilter> <EventFilterRef ref="Message Milestones"/> <EventLevelFilter level="Warning"/> <EventLevelFilter level="Error"/> <EventLevelFilter level="High"/> </OrFilter> </EventFilter>
To re-enable logging into the MESSAGEEVENTSNAPHOTS table, uncomment the following event filter in the events.xml. This was enabled, by default, in Axway Synchrony versions prior to Axway Synchrony 5.4.
<EventRouter id="Message Events to Database" class="com.cyclonecommerce.events2.router.PersistenceRouter" active="true" priority="2147483647"> <EventFilterRef ref="Messaging To Database"/> </EventRouter> <EventFilterRef ref ="MessgeingToDatabase"/></EventRouter>
Copy the ArgusRouter.jar file from Argus local directory: \SUPPORT\Axway Synchrony\Axway Synchrony 5x to Axway Synchrony directory: <Axway Synchrony Install Folder>\site\jars\.
From the browser, go to http://<Receiver Axway SynchronyServer>:6080/ui/.
In the Getting Started screen, hover the Trading Configuration icon and from the drop-down menu select Recent Communities > Community.
In the Summary screen and click the Application Pickup icon.
In the Application pickup exchange screen, click the link in the Name column.
Click the Inline Processing tab.
In the Inline processing rules screen:
In the Class name field, enter com.cyclonecommerce.relsys.router.GetMessageInfo.
In the Parameter field, enter Relsys Argus.
In the Description field, enter GetMessagesInformation.
Click Save changes.
When the Pick an integration pickup exchange screen appears, click Logout.
Repeat the preceding steps for the Sender Server.
From the Sender Axway Synchrony Server, configure an XML file to transmit from the Sender server to the Receiver server.
Note:
The file must be an E2B file that contains the correct routing IDs for the sender and the receiver.Make sure that the Axway Synchrony servers on both sender and receiver are running.
Drop the E2B XML file into the out bound folder of the Axway Synchrony Sender server.
Log in to a machine where Axway Synchrony is installed.
From the browser, go to http://<Sender Axway SynchronyServer>:6080/ui/.
In the Axway Synchrony Login screen, enter the Axway Synchrony User ID and Password, and click Login.
In the Getting started screen, hover the Message Tracker icon and select the Message Searches > All Messages from the menu.
From the Search results screen, verify that the transmission is in progress by locating the Custom Search section and click Find until Delivered appears on the screen.
Note:
The system does not display this screen if it has already transmitted the file.When the file is transmitted successfully, click Logout.
Go to the Axway Synchrony Receiver server and verify that the E2B file has been received.
To verify that the file has been transmitted:
Log in to the receiver Axway Synchrony server.
Select the All Messages option.
View the message payload.
Compare the E2B file on the receiving machine (payload version displayed) with the file from the sending machine.
These files should be identical.
To verify delivery on the Receiver Server, repeat the procedure.
Verify that the E2B XML file is configured with proper routing IDs for both the send and the receiver before dropping the file into the Axway Synchrony outbound folder.