Manage Resources with Core and Trading Partner Projects

How you create and name Projects and packages in your CIC Studio workspace is important for general organization and easy identification of your integration resources, but also a good practice when onboarding new customers. The use of CORE Projects and Projects that apply to your specific trading partner, along with good naming conventions, are key for good resource organization and maintenance. 

Recommended Projects

Here are some recommended Projects that can be used in your integration solutions:

Core EDI 

Create this core base Project to contain all the EDI schemas, base EDI Rulesets, Inbound and Outbound Route Business Process, etc. to be used in EDI integrations at an environment level.
For example, com.<customer>.core.edi

Core Non-EDI

Create this core base Project to contain all non-EDI Schemas (XML, flat file, etc), base non-EDI Rulesets, Application Routes Business process, etc. to be used in non-EDI integrations.
For example, com.<customer>.core.nonedi

Core System

Create this core base Project that contains all the customer Schemas, Adapters,  Data Sources, SQL Access used globally, DB Adapters, etc.
For example com.<customer>.core.system

Trading partner-specific Project

Create a Project that is specific to a trading partner; this can contain partner Rulesets, inbound and outbound Routes, Envelopes, etc.
For example com.<customer>.core.<tradingpartner>

Notes:

• The packages should then be further qualified for inbound/outbound, and document type (850, 810, etc.) For example com.<customer>.core.edi.inbound.n850
• A number should not be present after (.) in any case.

Related Topics

• Projects, Packages, and Objects
• Naming Conventions