What is ICS integration
Integrations are the main ingredient of Oracle Integration Cloud Service. An integration includes at the least a trigger (source) connection (for requests sent to Oracle Integration Cloud Service) and invoke (target) connection (for requests sent from Oracle Integration Cloud Service to the target) and the field mapping between those two connections.
When we create the integrations, we build on the connections we have already created by defining how to process the data for the trigger (source) and invoke (target) connections.
Once our trigger (source) and invoke (target) connections are configured, the mappers between the two are enabled so we can define how the information is transferred between the trigger (source) and invoke (target) data structures for both the request and response messages.
Types of Integration
ICS allows us to create four types of integration. Here is the list if supported types of integration:
1) Basic Map Data: Such type of integration is very simple and allows us to flow data between two systems with the ability to add one additional enrcihment call during requsest and response. For example, if you want send data from system A to B where the transformation is very straighforward then such type of integraton would be very useful.
2) Orchestration: This type of integration allows us to create more complicated flows i.e invoking call to multiple systems, aggregating data and making some if/else flows decision based on the data we receive. Like Oracle Service Bus, these integrations are stateless.
This pattern allows us the following activities:
Combining these allows us to create more complicated integrations.
3) Basic Publish To ICS: This is very fairly straightforward integration. It is like we are sending data in JMS queue.
4) Basic Subscribe To ICS: This is very fairly straightforward integration. It is like we are reading data from JMS queue.
Integrations are the main ingredient of Oracle Integration Cloud Service. An integration includes at the least a trigger (source) connection (for requests sent to Oracle Integration Cloud Service) and invoke (target) connection (for requests sent from Oracle Integration Cloud Service to the target) and the field mapping between those two connections.
When we create the integrations, we build on the connections we have already created by defining how to process the data for the trigger (source) and invoke (target) connections.
Once our trigger (source) and invoke (target) connections are configured, the mappers between the two are enabled so we can define how the information is transferred between the trigger (source) and invoke (target) data structures for both the request and response messages.
Types of Integration
ICS allows us to create four types of integration. Here is the list if supported types of integration:
1) Basic Map Data: Such type of integration is very simple and allows us to flow data between two systems with the ability to add one additional enrcihment call during requsest and response. For example, if you want send data from system A to B where the transformation is very straighforward then such type of integraton would be very useful.
 |
| Basic Map Data |
2) Orchestration: This type of integration allows us to create more complicated flows i.e invoking call to multiple systems, aggregating data and making some if/else flows decision based on the data we receive. Like Oracle Service Bus, these integrations are stateless.
This pattern allows us the following activities:
- Assign
- Map
- Callback
- Stop
- Swith
- Notification
- For loop
- While loop
Combining these allows us to create more complicated integrations.
3) Basic Publish To ICS: This is very fairly straightforward integration. It is like we are sending data in JMS queue.
4) Basic Subscribe To ICS: This is very fairly straightforward integration. It is like we are reading data from JMS queue.
Tidak ada komentar:
Posting Komentar