Importing Sample Projects and Environments

This section explains how to import the ebXML Protocol Manager sample Project, Environment, and related files. It also lists these files.

Importing the sample’s files requires the following steps:

• Extracting Sample Files

• Importing Sample Projects

• Importing Sample Environments

Extracting Sample Files

This section explains how to extract the ebXML Protocol Manager sample files from the file ebXML_Manager_Sample.zip that contains them. You must perform this operation before you can import an ebXML Protocol Manager sample Project or Environment.

ebXML_Manager_Sample.zip is provided on the CD-ROM with ebXML Protocol Manager. See Chapter 2, Installing ebXML Protocol Managerfor instructions on how to obtain (download) this file.

To extract the sample files

1. Extract the contents of the ebXML_Manager_Sample.zip file to a temporary directory, for example, C:\temp\eXchange. Make sure you preserve the extracted file paths.

   ---

   Note –

   It is recommended that you first create a temporary eXchange directory for the sample files and extract these files to this directory for your convenience. This action allows you to easily access the files while performing procedures provided later in this chapter.

   ---

Extracted Files and Directories

If you use the C:\temp\eXchange top-level directories, the following directories and files are created:

 C:\temp\eXchange\Sample\Certificates\CompanyA-Cert.der
C:\temp\eXchange\Sample\Certificates\CompanyB-Cert.der
C:\temp\eXchange\Sample\Data\Atlanta\payload\Blue hills.jpg
C:\temp\eXchange\Sample\Data\Atlanta\payload\payload.xml
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_NoPayload.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_Ping.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_PO_AckReq.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_PO_Binary.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_PO_DupCheck.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_PO_NoAckReq.txt
C:\temp\eXchange\Sample\Data\Atlanta\Outbound_StatusRequest.txt
C:\temp\eXchange\Sample\Data\Berlin\payload\payload.xml
C:\temp\eXchange\Sample\Data\Berlin\payload\Blue hills.jpg
C:\temp\eXchange\Sample\Data\Berlin\Outbound_NoPayload.txt
C:\temp\eXchange\Sample\Data\Berlin\Outbound_Ping.txt
C:\temp\eXchange\Sample\Data\Berlin\Outbound_POAccep_Binary.txt
C:\temp\eXchange\Sample\Data\Berlin\Outbound_POAccep_NoAckReq.txt
C:\temp\eXchange\Sample\Data\Berlin\Outbound_POAcceptance.txt
C:\temp\eXchange\Sample\Data\Berlin\Outbound_StatusRequest.txt
C:\temp\eXchange\Sample\Environments\CommonEnvironments.zip
C:\temp\eXchange\Sample\Keys\CompanyA-Key.p12
C:\temp\eXchange\Sample\Keys\CompanyB-Key.p12
C:\temp\eXchange\Sample\Projects\SampleProjects.zip
C:\temp\eXchange\Sample\TradingPartners\envBerlin_AtlantaSME.xml
C:\temp\eXchange\Sample\TradingPartners\envAtlanta_BerlinSME.xml

If you use the \temp directory, and your system does any kind of auto-delete operation on any directory with this name, you must disable this function.

As shown in the previous list, in addition to files for the Projects and Environments, ebXML_Manager_Sample.zip also contains key, certificate, TP, and data files.

Before you import the Environments, you must first extract them from the CommonEnvironments.zip file.

If You Use Different Path Locations

If you extract the data files to different locations, modifications are necessary in the appropriate Enterprise Designer configurations. You must also modify the appropriate eXchange ePM fields under the ToPartner and FromPartner tabs.

Importing Sample Projects

Before you import the sample Projects, your Repository must be running, and you must be logged on to Enterprise Designer. 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.

To import sample Projects

1. In Project Explorer, right-click the Repository and, on the context menu, click Import.

2. In the Import Manager dialog box, browse to the directories where you installed the sample files (such as C:\temp\eXchange\Sample\ebXML\Projects).

   The name of the Project file you must import is SampleProjects.zip.

3. Select this file and click Import.

   A message appears saying the import operation was successful.

4. Click OK.

5. Close the Import Manager dialog box.

   The Project Explorer tree now displays the following Projects under ClientProjects:

   • ClientInebXML

   • ClientOutebXMLAtlanta

   • ClientOutebXMLBerlin

   • HostAtlanta

   • HostBerlin

   • JmsToFile

   • ToInternal

Using Deployment Profiles

To run an ebXML Protocol Manager Project, you must create and activate at least one Deployment Profile for the Project. The general types of Projects are:

• B2B host Projects

• Main Projects

• Outbound and inbound Projects

• Error-handler Projects

Importing Sample Environments

Before you import the sample Environments, your Repository must be running, and you must be logged on to Enterprise Designer. If your Repository already has an Environment at the root level whose name is identical to any of the Environments you are importing, you must delete or rename such Environments before you start.

To Import Sample Environments

1. In Environment Explorer, right-click the Repository and, on the context menu, click Import.

2. In the Import Manager dialog box, browse to the directories where you installed the sample files (such as C:\temp\eXchange\Sample\ebXML\Environments).

   The name of the Environment file you must import is CommonEnvironment.zip.

3. Select this file and click Import.

   A message appears saying the import operation was successful.

4. Click OK.

5. Close the Import Manager dialog box.

   The Environment Explorer tree now displays the following Environments:

   • envAtlanta

   • envBerlin