Integration with new Oracle Integration Cloud Service (ICS) by ec4u
July 26, 2016 Leave a comment
Since a few years cloud computing has become more and more popular. The main types of cloud computing are Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS). In the past, several subareas have been established in the market and pushed by research companies. One subarea is Integration PaaS (IPaaS) and a variety of vendors have provided solutions. One advantage of IPaaS solutions is the simplified integration. Furthermore, IPaaS provides the capability to integrate cloud- and on-premise applications. Oracle announced Integration Cloud Service (ICS) as an IPaaS solution in June.
This article describes a first impression and the key components of ICS.
First experience with ICS
After the login to ICS, you will get greated with an organized and clean overview. The page provides an overview on the three main functional areas. Figure 1 shows the areas and the simple and tablet-friendly user interface. The functional areas are divided into Connections, Integrations and Dashboard.
Figure 1: ICS Start Page (click on the picture to see an enlarged version of the picture)
The Connections-area provides the capabilities to define configurations to specific application endpoints. These configurations are based on technology adapters such as SOAP, application adapters for on premise application e.g. eBusiness Suite and cloud adapters for cloud applications e.g. Oracle Sales Cloud. The connection could be used for several integrations and one of the main benefits is the reusability of the configuration. In addition, the integration developer does not need to know details about the service or application when using the preconfigured adapter.
The most important functional area is Integrations. It provides the functions to develop the integration flows and lookups. The overview page shows all integrations with the possibility to filter by status. The user interface to develop the integration is kept as simple as possible.
Figure 2 shows the integration development and the clean interface you will already know from the overview. Target, source and transformation are the key elements of an integration scenario. The source and target can be defined with preconfigured connections or technology adapters such as Rest or SOAP. The transformation for request and response messages is placed in the middle of the screen. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog 
Twitter 
LinkedIn ![image[7][2][2][2]](https://paascommunity.com/wp-content/uploads/2013/04/image7222.png?w=20&h=20 "image[7][2][2][2]"){kind=small}
Facebook ![clip_image002[8][4][2][2][2]](https://paascommunity.com/wp-content/uploads/2013/04/clip_image00284222.jpg?w=26&h=23 "clip_image002[8][4][2][2][2]"){kind=small}
Wiki
Sympany, with its head office in Basel, grew out of the ÖKK Basel and other health insurers. In 2012, Sympany earned premiums of CHF 994 million and had a profit of CHF 16.3 million. Sympany’s roughly 550 employees serve over 227,000 private customers, of which about 189,000 have basic insurance policies. Its corporate clientele comprises approximately 12,200 companies.
PaaS Community Blog 