Below we walk through the steps of running the Cleo/EXTOL Conversion Manager with a EBI 2.6 Windows instance.

Step 1 - Conversion Archiver

The first step to migrating the EBI user’s EBI 2.6 environment to Cleo Clarify is the Conversion Archiver. This is located in the Clarify /runtime/utils directory.


The ConversionArchiver.zip file needs to unzip to the root directory of the EBI 2.6 installation.

Step 2 - Executing the Conversion Archiver

The next step is making sure the EBI 2.6 server is started. Once started, the EBI user wants to open a command window and change the directory to where the conversion folder was just unzipped. From the command line, run the command ExecuteConversionArchiver “EXTOL_ENTIRE_DATABASE”.


When the command finishes running a .jar file will be created in the conversion folder directory.

Step 3 - New EBI Project

The EBI user will want to create a new Clarify workspace to bring their EBI 2.6 environment into. Once created they will want to create an Clarify Project. A good practice is a zzz prefix for the project containing the projectutil file and Conversion Manager object.
Click File > New > Clarify Project

Step 4 - Create Project Util File

In the EBI Project, the EBI user will want to create a .projectutil file. In this file is where the EBI user will specify the name of their projects and trading partners like the following example.



This example will create the following projects in the EBI user’s workspace when the EBI user right clicks the .projectutil file and clicks Create Projects.

Step 5 - Creating the Conversion Manager

Once the Clarify user has their projects created, they can create their Conversion Manager.
Click File > New > Conversion Manager

Click Next
Below the Clarify user browses and identifies for the .jar file that was created by the ExecuteConversionArchiver, in the conversion folder.

Click Finish.

Step 6 - The Conversion Manager

Once the Conversion Manager is created it will appear in the package of the zzz project as in the following example.


From here the EBI user can see all the objects that were brought in with the Conversion Manager. It lists all the info for the objects and what they will be named in EBI 3.1.
This is where the EBI user wants to sort out what objects can be placed in the base and used by multiple trading partners. Also which objects are trading partner specific and placed in their own EBI Projects.

Conversion Manager Example 1

For example, objects going into the base project would be Actions and EDI Schemas because they can be used by multiple trading partners.

Conversion Manager Example 2

For objects going to myPartner project, EBI users would want objects such as Rulesets and Routes.

When complete, click Start Conversion and all of the objects will be split up into their EBI projects and packages that the EBI user specified.