Are you Oracle SOA (Service Oriented Architecture) developer trying to understand OIC (Oracle Integration Cloud) from development perspective?
If you are already a pro in SOA, then OIC is a cake walk for you. But, if you are just acquainted with SOA and want to relate/compare it with OIC, well, you are at the right place.
This post will help SOA developers to understand OIC easily in SOA terminology.
1. Connection - A connection in OIC has multiple references in SOA.
If you are already a pro in SOA, then OIC is a cake walk for you. But, if you are just acquainted with SOA and want to relate/compare it with OIC, well, you are at the right place.
This post will help SOA developers to understand OIC easily in SOA terminology.
1. Connection - A connection in OIC has multiple references in SOA.
- DB Connection - It can be referred to datasource created in weblogic. DB based Connection will have the connection details to connect to DB like host name, port, service name/SID, username, password, etc.
- REST Connection - Can be related to an empty REST adapter created in SOA without any service or schema related details associated.
- SOAP Connection - a SOAP/Webservice adapter in SOA with WSDL associated.
- FTP Connection - Similar to FTP outbound connection pool created in SOA's weblogic server. This will contain FTP server's host address, port, username, password, security policy etc
- Oracle ERP Cloud Connection - ERP Cloud adapter in SOA with ERP services catalog url, username and password defined.
Similarly, there are different other types of Connections which can be created.
2. Trigger and Invoke - These are the roles that can be assigned to a connection. Trigger role means that the Connection can be exposed as a "Service" in SOA terms and accept input like "Receive" activity. An Invoke role means that the Connection can be invoked as a "Reference" partner link in SOA and sent input through "Invoke" activity.
3. Integrations - These can be compared to "Composites" in SOA. Like each composite can be designed as Empty Composite, Composite with BPEL, etc, integrations also be designed as Basic Routing, App Driven Orchestration, Scheduled Orchestration, etc.
4. Packages - Packages are like Applications in SOA. All integrations in a package can be bundled together and moved to different environments.
5. Libraries - Unlike SOA where custom java classes can be written and imported into the component, OIC does not support Java libraries. OIC only supports Java Script libraries. You can write all your functions in java script, add them as a library and use in OIC integrations.
OIC is much more simpler product than SOA in terms of the richness of components.
OIC is can be used in scenarios where you want to do simple integrations with services or APIs already present in cloud or on-premise. Where message size is not too huge and there is not lot of orchestration needed.
3. Integrations - These can be compared to "Composites" in SOA. Like each composite can be designed as Empty Composite, Composite with BPEL, etc, integrations also be designed as Basic Routing, App Driven Orchestration, Scheduled Orchestration, etc.
4. Packages - Packages are like Applications in SOA. All integrations in a package can be bundled together and moved to different environments.
5. Libraries - Unlike SOA where custom java classes can be written and imported into the component, OIC does not support Java libraries. OIC only supports Java Script libraries. You can write all your functions in java script, add them as a library and use in OIC integrations.
OIC is much more simpler product than SOA in terms of the richness of components.
OIC is can be used in scenarios where you want to do simple integrations with services or APIs already present in cloud or on-premise. Where message size is not too huge and there is not lot of orchestration needed.
No comments:
Post a Comment