ReakTor Labz | ProaKtor

> > > Best Practices – Core Project

Best Practices – Core Project

14th June 2016

Sean Hoppe Consulting Group

As you may know, there are many different ways you can accomplish something in EXTOL Business Integrator (EBI), or Cleo Clarify.  How you create your Rulesets, Business Processes, configure your SVN Repository, Projects and Packages, and even how you name your resources depends on what you, or your company may decide.  With the many ways of doing something, you want to do it right the first time in the most efficient way possible to reduce time, and provide adequate usability.

In this next series, we’re going to focus on Best Practices.  These are our recommendations, and methodologies, on how we configure our environments.

Project Structure

Whether you’re brand new to creating resources, or an experienced user, one of the most challenging and daunting tasks is to properly configure your Projects and Packages to a uniform standard that meets requirements.  Sure, you can create all objects and place them beneath the same Project and Package, but there are many reasons why we strongly recommend a proper structure for your Project Explorer.


Core Project

The use of a Core Project will help contain resources that can be used by multiple trading partners, and multiple Projects and their resources.

Core Project Explorer Clarify Studio

With dependencies properly configured, the Core Project allows its resources to be used in multiple partner-specific objects.  For example, a Ruleset in your trading partner-specific Project, specially designed for your trading partner, can use Schemas available in the Core Project. Generic objects that can be used in many other objects should be created here.

Core Dependencies

Make your Core Packages available to other Projects by configuring the dependencies in the MANIFEST.MF file located within the Project beneath the META-INF folder.

MANIFEST File Core Project Clarify Studio

In the Runtime tab in the MANIFEST.MF file, add the desired Package whose contents you’d like to share with other Projects.

Runtime Dependencies MANIFEST file Clarify Project Explorer Studio

Trading Partner Project Dependencies

Now that the Core Package is available, you must configure the proper dependencies from your Trading Partner-specific Projects.

In that Project’s MANIFEST.MF file, navigate to the Dependencies tab and click Add in the Required Plug-ins section to add the Core Package that was previously shared.

Trading Partner Project Dependencies Clarify Studio Project Explorer

Now, your dependencies are properly configured.  You can use the Core’s resources, from the Core Project/Package, for resources in your trading partner Project.

Note:  This must be configured for all Trading Partner-specific Projects, and you must configure each MANIFEST.MF file accordingly.  However, Core’s MANIFEST.MF file only needs to be modified once to include the Package for sharing.  

If additional Packages are available, and you’d like to make those resources available, follow the same steps and include your additional Packages.

By: on