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 on-boarding 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 Routes, Envelopers, Cloud Monitors, etc. to be used in EDI integrations.
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, Cloud Monitors, 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, Cloud Monitors, Data Sources, SQL Access, 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 - You may wish to add
prod or stageto your Project and package names if using different environments to differentiate, although not required. For example:
com.<customer>.core.edi.prod
com.<customer>.core.edi.prod.inbound.n810
com.<customer>.core.edi.stage
com.<customer>.core.edi.stage.inbound.n810
Related Topics