LexiCom Translator Integration Guide

Transcription

1 LexiCom Translator Integration Guide For Emanio Trading Partner Document Version 2.3 February, 2005 Copyright Cleo Communications LexiCom Translator Integration Guide This translator guide describes how to configure LexiCom with Emanio TP to transfer files with a trading partner. To begin, first confirm that you have completed the Before You Begin steps below. Then, complete the Integration Steps within LexiCom and Emanio TP. If you have questions related to performing a task in LexiCom, refer to the LexiCom User s Guide located at Before You Begin Confirm that the following steps are complete before continuing. If a step is incomplete, refer to the Getting Started Guide (and LexiCom User s Guide as necessary). I have read the Cleo LexiCom Getting Started Guide. I have been given a Username and Password for my host logon account (e.g., from my VAN or trading partner). I have installed LexiCom. I am able to launch LexiCom. (LexiCom is activated with a temporary or permanent key.) I have activated and configured the host that I wish to connect to with LexiCom. I have tested with a Cleo system test host (if applicable). I have an existing trading partner relationship setup within Emanio. Integration Steps Follow these steps to ensure the Emanio TP integration goes smoothly. LexiCom Configuration: Generate Files for Emanio TP (page 3) Emanio TP Configuration: Create a Custom Network (page 5) Create a Custom Receive Task (page 8) Create a Custom Send Task (page 11) Assign Network to Trading Partner (page 13)

2 LexiCom Configuration Generate Files for Emanio TP NOTES: The translator file generation assumes that incoming files to Emanio TP will be called recvfile.edi and outgoing files will be called sendfile.edi. If the input/output file names differ from these from within Emanio TP, the user must manually update the generated files. If host, mailbox, or action alias names are changed, the user will have to re-generate the translator files. Generating translator files deletes the last set of files generated. 1. Select Configure > Integration in the menu bar. 2. Select the Emanio TP from the Translator pull-down. 3. The Platform will be forced to Windows. 4. Enter the local directory path for Emanio TP. You may also use the < > button to browse to that directory. 5. Select <Generate Translator Files > to begin the process of selecting actions for which you wish to generate translator files.

3 6. Select the actions for which you wish to generate script files. Note: (a) Only active hosts will be listed (b) All selected files will be re-generated (c) Files previously generated and not selected will be deleted. 7. Enter the Script Location where the scripts should be generated. (Note: For certain translators, additional files are generated into the Translator Location or one of its sub-directories). By default, the script location is Translator, a subfolder of the LexiCom folder (e.g., C:\Program Files\LexiCom\Translator.) 8. Select the <Generate> button to generate the translator files. Emanio TP Configuration Overview The Trading Partner EDI software can be configured to support multiple VANs that require LexiCom to perform file transfers. Each VAN can be represented by a Trading Partner Custom Network. The user will create these Custom Networks and add tasks for launching LexiCom and perform file transfers between the desired VAN and Trading Partner. Trading Partner can be configured to receive and send EDI files at the Network (VAN) level by creating custom tasks. The user will be responsible for configuring Trading Partners & Transaction Sets by referencing the Trading Partner User s Guide. The Trading Partner can then be attached to the desired Network (VAN). Outbound Processing: By associating a trading partner with a network, outgoing EDI files for that trading partner will be placed in the corresponding network s directory to be sent by LexiCom (Example C:\Program Files\TradingPartner\Edata\GXS ICS). A single file called mail_out.new is created in the network s directory. This file contains all EDI interchanges for all trading partners associated with the network. Inbound Processing: When the Receive EDI task is executed for a particular network, all EDI data for all trading partners on that network will be pulled from the VAN and stored as a single file (mail_in.new) in the directory corresponding to the network (Example:

4 C:\Program Files\TradingPartner\Edata\GXS ICS ). Create a Custom Network 1. Double-click on Add New Network in the Networks & the Internet window 2. Select Create a custom Network and click Next. 3. Type a name for the new custom network and click Next. For example, GXS ICS might be used.

5 4. Click the Finish. Ignore any warnings about the network not being completely configured. 5. The new network will appear in the Networks & the Internet window.

6 Create a Custom Receive Task 1. Open the new network by double-clicking on the icon (in this example, GXS ICS.). 2. Right-click in the network window and select New to create a new task 3. Select Create a custom Task.

7 4. Type in a name for the new task and select the User Tracked Task type. 5. Enter the path to the batch file used to receive EDI data using LexiCom. Note: This is the batch file generated by LexiCom. The naming convention is as follows: Host Name+Mailbox Name+Action Name.bat, where

8 a. Host Name is the host alias within LexiCom, b. Mailbox Name is the mailbox alias within LexiCom, and c. Action Name is the action alias within LexiCom. Most likely the path will include spaces and double-quotes will be necessary. Also, the batch file requires one parameter, the network name. If the network name contains spaces, double-quotes are necessary. For example, C:\Program Files\LexiCom\Translators\GXS ICS FTPsMyMailboxReceive.bat GXS ICS. 6. The receive task will appear in the network window. In this example, the GXS ICS FTPsMyMailboxReceive.bat file will launch LexiCom in command line mode and retrieve all EDI files from that specified host into a single EDI file called mail_in.new. When the EDI data has been retrieved, a flag will be raised on the

9 New Mail In icon located in the right side of the TP network window. Create a Custom Send Task 1. Create another task to send EDI data to the VAN. 2. Enter the path to the batch file used to send EDI data using LexiCom. Note: This is the batch file generated by LexiCom. The naming convention is as follows: Host Name+Mailbox Name+Action Name.bat, where a. Host Name is the host alias within LexiCom, b. Mailbox Name is the mailbox alias within LexiCom, and c. Action Name is the action alias within LexiCom. Most likely the path will include spaces and double-quotes will be necessary. Also, the batch file requires one parameter, the network name. If the network name contains spaces, double-quotes are necessary. For example, C:\Program Files\LexiCom\Translators\GXS ICS FTPsMyMailboxSend.bat GXS ICS.

10 3. The send task will appear in the network windows. In this example, the GXS ICS FTPsMyMailboxSend.bat file will launch LexiCom in command line mode and send the mail_out.new file to the associated VAN. When the EDI data has been sent, the mail_out.new file is deleted and the flag will be removed on the Mail Out Ready icon located in the right side of the TP network window. 4. Optionally, add your custom tasks to the existing Inbound and Outbound task lists. You may also add the Send custom task to your Process Outbound Data task list, and the Receive custom task to your Process Inbound Data task list. Assign Network to Trading Partner 1. Right-click the desired trading partner icon (in the Trading Partners window)

11 and select Properties. The Trading Partner Wizard is displayed. 2. Click the down arrow to the right of the Network field and select the desired network then click Finish.