Oracle Integration Cloud Service (ICS) Best Practices

1. Proper Versioning of Integration should be maintained
 
 Example: 01.00.0000

 

Reason: Service versioning defines the strategy for having multiple versions of the same  service to be operational at same time so that changes and enhancements to service  interface do not affect existing consumers.

2. Integration should be inside Package.

 Syntax: <CompanyName>.<ProjectName>.ics.pkg

 Example: xyz.sample.ics.pkg

    

 

   

Reason: All Integration which are included in the package can be imported/exported in one shot from one environment to other environment.

  

Issue: If we won’t give the package name the integration will be created as normal integration without package and it will be a miss when we migrate integrations of project which are present in specific package from one environment to other and manually we have to move that particular integration.

3. Fault Mapping Should be done for every integration of map to data and Global Fault should be added for orchestrated integrations.

Reason: For proper debugging, get exact details of the error and to check where exactly integration has failed. If we don’t implement this, we are not aware where exactly the issue is and it will be time consuming.

4. All three Business Identifiers for tracking should be provided (Primary Id of Business Entity, Name, Cross Reference Id) and make one of them as primary according to the business functionality. 

Reason: It will be helpful for easy tracking, when issue comes immediately we can get into details and take necessary actions without time consuming.

5. Check for NULL values before assigning mandatory fields.

Reason: Checking the validation before sending the data to Target System which will reduce unnecessary calls with improper data.

6. Filter condition has to be implemented for events while configuring Adapter endpoint in integration to avoid same event firing continuously.

7. Copy-of in ICS Mapping:

Template:

Use when source and target has same WSDL (Including namespaces).

Reason: It will be helpful even if new elements have been added in the end systems, no need of mapping changes in integration and just what we need to do is a meta data refresh on connection and on the integration created.

Value-of in ICS Mapping:

 

Use when source and target has (Same/Diff) WSDL with different namespaces.

Reason: If we use copy of here, target won’t receive the data as both WSDL’s has different namespaces.

8. If the Service which is used in configuring the connection is deployed on managed servers try to use the load balancer WSDL URL.

Reason: Even if one managed server goes down this load balancer URL will automatically point to other running managed servers.

9. It would be preferred to login to ICS with their individual Id’s.

Reason: To avoid Session Conflict’s, Locked Draft state of integration and potential activation and deactivation issues of integrations.

Thank You!!!!

Happy Learning!!!!