Beginning Operations

This section explains basic information you need to begin using the sample implementation scenario.

See the eXchange User’s Guide for more information on the subject matter covered by this section.

Before Starting Enterprise Designer

Before you start using Enterprise Designer, ensure you have completed the following tasks:

• Make sure you have completed all necessary phases of the product installation.

• Make sure your LDAP and Oracle systems are installed, configured, and operating correctly.

• Your Repository must be running.

• You must have two Logical Host domains installed and running, one for Atlanta (dmnA) and one for Berlin (dmnB).

• Using Enterprise Manager (port 15000), you must add two Integration Servers for the domains, dmnA on 18000 for Atlanta and dmnB on 28000 for Berlin (Host Name: localhost, User Name: Administrator, Password: STC).

• Also for dmnA, add a user with the following parameters:

• username: userA

• password: userA

• Group List: PartnerManager, MessageTracking

• For dmnB, add a user with the following parameters:

• username: userB

• password: userB

• Group List: PartnerManager, MessageTracking

  ---

  Note –

  If your Repository already has a Project at the root level whose name is identical to any of the Projects you are importing, you must delete or rename such Projects before you start.

  ---

After you have completed the tasks in the previous list, you must then log in to Enterprise Designer.

Exporting Sample Files

Files are supplied with the sample scenario, which support the general operation of the sample. These files are for the transport of data and ePM operation. You must export these files using Project Explorer in Enterprise Designer.

For a list of the sample scenario’s Projects, see Sample Scenario Project Folders.

These files are:

• Data

• ePM

Exporting Data Files

The data files are:

• For Atlanta under eXchange > Samples > AS2 > RecvFromInt > Files:

• InputAS2.xml.~in

• X12-Payload.edi.

It is recommended that you set up an export folder structure to contain these files, for example:

C:\temp\eXchange\Sample\AS2\Data\Atlanta

Exporting ePM Files

The ePM export files are located in Project Explorer under eXchange, as follows:

• ePMImport > AS2 > Hosts > envA_AS2.exp and envB_AS2.exp

• ePMImport > AS2 > SecurityKeys > CompanyA-Cert.der and CompanyA-Key.p12

• ePMImport > AS2 > TP_Profiles > envA_AS2_TP_Berlin.exp and envB_AS2_TP_Atlanta.exp

The Atlanta ePM file are:

• envA_AS2.exp: For the B2B Host.

• CompanyA-Key.p12: For SME/KS (used by B2B Host).

• envA_AS2_TP_Berlin.exp: For the Berlin TP.

The Berlin ePM files are:

• envB_AS2.exp: For the B2B Host.

• CompanyA-Cert.der For SME/KS (used by TP).

• envB_AS2_TP_Atlanta.exp: For the Atlanta TP.

It is recommended that you set up an export folder structure to contain these files, for example:

C:\temp\eXchange\Sample\AS2\TP_Profiles or B2B Hosts or SecurityKeys

Editing the Sample XML File

An .xml data file is supplied with the sample scenario, for Atlanta, which reference path locations enclosed between the XML tags: <dir> </dir>. You must edit this file to reflect the location where the data file is to be used by the Atlanta system.

The file you need to edit is:

• For Atlanta: InputAS2.xml.~in

The previous section lists the locations of where to find these files, if you have not already exported them. If you need information on exactly how to edit these files, see Editing the Sample Data XML File.

If you have already run the sample and you want to experiment with other differences from the sample (such as using a payload data file with a different file name, or using a TP with a different name), be sure these differences are also reflected in these files, as necessary.