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.

To extract the sample files

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:

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.

Note –

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

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

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.

Select this file and click Import.

A message
appears saying the import operation was successful.

Click OK.

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

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

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.

Select this file and click Import.

A message
appears saying the import operation was successful.

Click OK.

Close the Import Manager dialog
box.

The Environment Explorer tree
now displays the following Environments: