Saturday, 4 February 2017

Oracle Integration Cloud Service (ICS) Coding Standards

Naming Convention for {Source/Target}-SOAP or SOAP-{Source/Target} based Integrations

·        Naming conventions for the Connections

Syntax:
<ProjectName>-SOAP-<Operation><BusinessEntity>-<AdapterName>

Example:
Sample-SOAP-ReceiveAccount-SFDC


·        Naming conventions for Integrations

Syntax:
<ProjectName>-< Operation><BusinessEntity>-<AdapterName>

Example:
Sample-ReceiveAccount-SFDC


·        Naming conventions for Identifier

Syntax:
<ProjectName>_<Operation><BusinessEntity>_<AdapterName>

Example:
SAMPLE_RECEIVEACCOUNT_SFDC when Target is SFDC


Naming Convention for {Source/Target}-{Source/Target} based Integrations  

·        Naming conventions for the Connections

Syntax:
<ProjectName>-<AdapterName>-Conn

Example:
Sample-Salesforce-Conn


·        Naming conventions for Integrations

Syntax:
<ProjectName>-Sync-<SourceAdapter>-<BusinessEntity>-<TargetAdapter>

Example:
Sample-Sync-OSC-Account-SFDC when source is OSC and Target is SFDC.


·        Naming conventions for Identifier

Syntax:
<ProjectName>_Sync_<SourceAdapter>_<BusinessEntity>_<TargetAdapter>

Example:
SAMPLE_SYNC_OSC_ACCOUNT_SFDC when source is OSC and Target is SFDC





·        Naming Convention for lookups

Must start with the Object Name / Business Entity Name.
Should be followed by the Element Name that needs domain value mapping.
Must be uppercase.

Syntax:
<BusinessEntity/ObjectName>_<ElementName>

Example:
ACCOUNT_THEATER.dvm



Description: Lookups created will be used inside the Integrations.

·        Better Readability

      Proper description to be present at each level of Integration, lookup's for better readability.
      
      
      
      Reason: Clear description prevent us from creating a duplicate integration and helpful in re-usability

Thank You!!!!


Happy Learning!!!!

No comments:

Post a comment