In our previous post we showed the main characteristics of Oracle ICS, now we will learn how to publish a cloud integration service.
In our next post we will learn the integration of Taleo and PSFT. I am preparing this and I will publish it as soon as it is ready. Right now, lets do a simple example.
Lets consider that we have a need to call a service in the cloud and that we want to do it through Oracle ICS.
The first thing we need to do, is to identify the type of service / application that we need, since Oracle ICS offers a series of adapters that simplify the integration. Such adapters available as of today are the following:
Oracle Sales Cloud
Oracle Messaging Cloud Service
Oracle Eloqua Cloud
Oracle HCM Cloud
Oracle ERP Cloud
Oracle CPQ Cloud
Oracle SOAP Adapter
Oracle REST Adapter
Oracle NetSuite Cloud Adapter
Integration Cloud Service Messaging
Oracle FTP Cloud (in Using Oracle FTP Cloud Adapter)
From the date in which the Oracle Integration Cloud Service was released, my colleague and friend Arturo Viveros and I started writing about the use and application in which it can be applied taking into consideration different integration scenarios and we decided to write the article “Integration Cloud Service (ICS) Preview” that you will see by clicking in the link.
We also make the next video:
Now I am writing this article that shows its use. This will be a series of articles that I will be writing during the following days.
The images below can be seen in a bigger size if you click over them.
The first thing to highlight is how easy is to use Oracle ICS.
Like other cloud applications, Oracle ICS is based in the UX principles that Oracle has been refining over the years.
Somebody used Oracle EBS at the beginning of the 2000’s?, How many options are there in[...]
How to make the installation of Oracle API Manager 12c? We will tell you in this article.
Oracle API Manager 12c is a component of the new Governance SOA Oracle stack. It is a brand new product since there are no previous versions of it.
Some of the points that call my attention were the following:
· Its installer is too small. Actually they are a couple of patches. I will explain this below.
· It is a component that is adhered to the service bus and can reside in the same OSB managed server.
· In relation to the last point, the API Manager does not have a managed server for him
· The API Manager Portal stays open over the Admin Server
· Its graphic interface is very similar, in aspect and utilization, to the one of the Catalog 12c
· Without any problem, it can be installed in the extended domain mode. This means that[...]