Untitled

The Cleo Harmony and Cleo EDI Integrator integration piece allows existing Harmony and EDI Integrator to easily ‘talk’ between the 2 solutions

Below are the notes from Cleo Harmony

Cleo Harmony Notes:

This connector is used to integrate inbound and outbound file transfers with Cleo EEI.  The inbox and outbox of each Cleo Harmony/VLTrader host to be integrated with Cleo EEI must point to an instance of this connector.

Only one Cleo EEI connector is needed for an integration with Cleo EEI.  Consider giving the EEI connector a meaningful name such as 'Prod' or 'Test'.  To use the Cleo EEI connector, set the host inbox to EEI:Prod/ and the host outbox to EEI:Prod/partner1, where 'Prod' is the alias of the connector and 'partner1' is the trading partner name configured in Cleo EEI.  Harmony/VLTrader allows you to map many EEI partners to one host connection by entering them as a comma-separated list in the Harmony/VLTrader host outbox, for example, EEI:Prod/partner1,partner2,partner3,partner4.  All outbound trading partner files are placed in the same outbound directory identified by the first partner in the list.  The first name in the list can actually correspond to what is referred to as a 'port' in EEI.  If the trading partner is defined in more than one enabled host outbox, the file is not sent and EEI is sent an error notification.

When an integrated host receives an inbound file, Harmony/VLTrader attempts to connect with the Cleo EEI server.  If the server is unavailable, the transfer fails.  When a connection has been established, the data is streamed to the Cleo EEI inbound data queue.  For more information on how Cleo EEI processes the data, see the Cleo EEI User Guide.

For outbound data flow, Cleo EEI places data on its outbound data queue.  The integrated host's <send> action can then be scheduled to run either periodically or automatically by polling Cleo EEI.  All data for the trading partner name specified in the Cleo EEI connector is then streamed to the trading partner.  For more information on how data is sent from Cleo EEI, see the Cleo EEI User Guide.  

NOTES:

When migrating a large number of trading partners from ESX, you can transition trading partners in batches either by migrating the associated hosts to Harmony/VLTrader in sets or by initially disabling all of the imported hosts and enabling a set of hosts at a time.  When a host is not found or is disabled in Harmony/VLTrader:

- Outbound messages in Cleo EEI will be placed on a secondary outbound data queue (EXTESXOUT2) that will be processed by ESX.  The secondary EXTESXOUT2 outbound data queue should be manually created in the same library as the EXTESXOUT data queue at the beginning of the migration phase and set as the outbound data queue in ESX.  The AS/400 command to create the EXTESXOUT2 outbound data queue is:     CRTDTAQ DTAQ(&DTAQLIB/EXTESXOUT2) MAXLEN(325) AUTORCL(*YES) TEXT('EEI to ESX actions (Outbound data)')

 After migration is complete, the command to remove the secondary outbound data queue is:

    DLTDTAQ DTAQ(&DTAQLIB/EXTESXOUT2)

After creating a new partnership, some additional configuration is required.

Select the Partnership

Find the partnership under the ACTIVE tab of the TREE view, and highlight it.

The details of the partnership will be displayed on the right in the CONTENT window.

In the CONTENT window for the partnership level, there are 2 tabs that need to be edited:

General

HTTP

The HTTP tab needs to be added by performing a one-time change via the following steps:

Click CONFIGURE > OPTIONS

Select the OPTIONS tab

Click Show Hidden Panel

General Tab

The GENERAL tab contains the Server Address and Port as well as the directories used for inbound and outbound communication.

Server Address – URL or IP Address of the partner's AS2 server.

Port # - The Port on the server through which data will pass.

Inbox – Directory where inbound data will write.

Outbound – Directory from which data will be sent.

Sentbox – Directory where outbound data will be archived.

Receivedbox – Directory where inbound data will be archived.

HTTP Tab

The HTTP tab contains instructions for the transfer of data. Most of the tab is defined by default, but when communicating with the server, via AS2/HTTP, the Path where the data will be written must be specified.

Open HTTP Tab.

Double click the PATH field on the PUT command.

Enter the Directory Path on the target server.

Click Apply.

Select and Configure Mailbox

Each partnership can contain multiple mailboxes.

To define how each mailbox functions, select the mailbox and edit the tabs in the CONTENT window. The tabs that must be edited are:

AS2

Certificates

HTTP

Define AS2 Tab

The AS2 tab defines the type of security used during communication and how receipts will be delivered.

Click the AS2 tab in the CONTENT window.

Select the request options: Encrypted, Signed, and Receipt

Select Encryption Method.

Select MDN Receipt options: Signed, MIC type, and Synchronous/Asynchronous.

Optional: Select Forced Message Security options.

Select Certificates

Signed and Secured AS2 communication requires Certificates. Define the certificates for the mailbox via the Certificates Tab.

Click the Certificates Tab in the CONTENT window.

Click Browse... on the Encryption Certificate entry.

Select the Certificate provided by the partner

Check the Signing Certificate box to use the same certificate during the signing process.

Check the Use Encryption Certificate box.

Click Apply.

HTTP Tab

The HTTP tab contains the AS2-From and AS2-To header information and must be configured for each partner.

Click the HTTP Tab.

Double click in the “Default Value” field of the AS2-From.

Enter YOUR AS ID.

Double click in the “Default Value” field of the AS2-To.

Enter PARTNER AS ID.

Click Apply.

Select and Define Actions

Each partnership mailbox can be configured for multiple actions to Receive, Send, etc. These actions must be defined before communication can take place.

Click one of the preset actions.

If a new action is required, right-click the mailbox and select New Action.

      2.In the CONTENT window, double click the preset command, or click the New Action Wizard button.

Header values are captured from the HTTP Tab on the Mailbox.

Define the Source name; this can be a wildcard value of * or a specific file name.

Define the options: Multi File Payload and/or Delete Source After Put

Click OK.

Click Apply.

1. Accessing VL Trader

Once users gain access to the VL Trader system, click on the VL Trader icon on the desktop.

This opens up the VL Trader application. Inside the application is where we can see all the information that is being passed.  

2. Local Listener

On the left side of the application will be a list of the active trading partners, as well as the Local Listener .

The local listener is the program that finds and picks up all the trader messages and information that gets sent.  

In this instance we are monitoring AS2 information, so that is what the local listener is monitoring.  

The log in VL Trader is where you can see all the AS2 information being passed.  Here is where we can see if the information is passed successfully or if there are any errors.

Some errors may include:

Below are the instructions on how to exchange public certs based on the self-signed cert we just created HERE

STEP 1:

After exporting the certificate, it must now be shared with the partners that will use it. To do so, unfold the Partnership in the Active tab and click Mailbox.

STEP 2:

In the Comment Pane on the right, select the Certificates tab and click Exchange Certificates.

STEP 3:

On the Certificate Exchange panel, highlight the partner whom is receiving the certificate, select Send New Certificate in the drop down, and click Proceed.

If you receive a prompt and you are sure you wish to proceed, click Yes.

STEP 4:

Specify the certificate to be used and it's password. You can browse to the certificate that you exported in Step 7.

STEP 5:

Click Email to send the certificate in .zip form.

STEP 6:

On the confirmation prompt, ensure that you want to send this certificate at this time by clicking Yes.

Below are the steps to create a new self-signed user certificate.

STEP 1:

Launch VLTrader

STEP 2:

Click on CERTIFICATES to access the Certificate Manager

STEP 3:.

In the Certificate Manager window, click Certificates and select Generate > Self-Signed User Certificate.

STEP 4:

Define the Alias, Algorithm, Key Size, Private Key Password, etc on the Generate User X.509 Certificate window.

STEP 5:

Click OK to generate the Certificate. 

Generation time will vary depending on key size

STEP 6:

After the certificate is generated, it will be visible in the Certificate Manager.

STEP 7:

Once the Certificate exists in the Certificate Manager, Right-click the certificate. Export the Certificate and/or Key for local storage and sharing with partners (only share Certificates with partners; never share Keys.)

Below are the instructions to create a new AS2 partnership in VLTrader

STEP 1:

Launch VLTrader

STEP 2:

From the TREE PANEL, click the TEMPLATES tab.

STEP 3:

Select the type of template you want to use; Generic or Pre-configured.

If the Partner is a big company like Amazon or Walmart, you can find them in the Pre-configured folders.

If the Partner is a smaller company, or if you prefer to create your own, use the Generic folder.

STEP 4:

Select the type of communication you will be using with the partner.

Example: AS2

STEP 5: 

Right-click the selection and click Clone and Activate.

When trying to access the VLTrader Application, for the first time, we receive the following error: java.io.FileNotFoundException VLTrader license file (Access is denied)