A Connection identifies a unique Application endpoint that is accessed using Integration Cloud Service. For instance, a sandbox instance of Salesforce.com or your production instance of Oracle Sales Cloud are each considered individual connections. There is a minimum of 6 connections for non-metered ICS and a minimum of 2 connections per month for metered ICS. There is no maximum limit on the # of connections you can place in an order. After you place an order for a specific number of connections, you will be led to a UI wherein you can decide on the allocation of connections to one or more ICS instances. Each ICS instance can accommodate up to 10 connections.
For example: if you place an order for 20 connections, you would be able to allocate 10 to one instance and 10 to another instance. If you place an order for 7 connections, you could allocate 5 to one instance and 2 to another. You can process upto a a maximum of one hundred thousand (100,000) messages per connection per day, across all connections. If your ICS instance had 8 connections, you could process upto 800,000 messages per day across all connections. Since once ICS instance can be configured with a max of 10 connections, you can process upto 1 million messages across all connections per day on that instance. Note that the size of the message may not exceed 5 MB.
Run your data integration workloads as the oracle user. Use the command sudo su - oracle after you log into the VM of your service.
Whenever a patch for a service instances becomes available, a message appears next to its name in the Services page. Click the service name to go to the detail page and then click the Administration tile. The Administration page has a tab called patching. In this page, you'll find a list of all available patches. Each patch has a Precheck and a Patch menu option. First click Precheck to ensure that your service needs a patch. Then click Patch, to apply the patch to your service. Each patch also has a Readme file for your information.
Yes – you can define tracking identifiers for each integration flow and use them to search and find executed tractions from the monitoring dashboard. The dashboard allows drill-down capabilities and insight into errors. Users can act on these errors by submitting or aborting those errors.
Integration Cloud Service addresses literally all SaaS to SaaS and SaaS to On-premises integration use-cases including ranging from simple Customer data synchronization across applications, to more advanced integration flows for processing opportunities, quotes, orders etc. The integration patterns range from real-time synchronous message exchanges between 2 applications to publish/subscribe message exchanges between multiple applications. Depending on the application, ICS also enables submission of a batch of requests to process a set of data objects (such as Incidents, Accounts etc) in one single interaction. When operating in a hybrid model, the set of possibilities expand to even larger number of business use-cases.
Yes. This is on our roadmap. We have upcoming capabilities to build long running processes in the cloud. However, the use-cases will be tailored to ensure they do not bring in elements of complexity into the design experience. You can also integrate with an existing SOA BPEL based Web service built using SOA Suite on-premises or SOA Suite Cloud Service instead.
Integration Cloud Service provides rich and native connectivity to a wide variety of applications including but not limited to Salesforce.com, Oracle Sales Cloud, Oracle HCM Cloud, RightNow, Eloqua, CPQ. This list will grow to a broad portfolio of Oracle and third party SaaS applications over the next few releases. However, you do not need an adapter to get your integrations off the ground. The product does support native Web Services – so any one of the 2300+ SaaS applications in the market today can be integrated with ICS. The same applies to on-premises Applications as well. Native rich adapters for on-premises applications such as E-Business Suite, S.P, Siebel, JD Edwards, Peoplesoft etc will also be available on ICS in future releases.
There are no prerequisites for subscribing to any cloud services while subscribing to Integration Cloud Service.
You connect to many heterogeneous on-premises and cloud data sources from a single platform and do all sorts of integration on your data entities. Data in any shape and format can be loaded and trformed on this platform. Data integration and synchronization happen in real time. Data will not get lost and data sources are highly available, even with large volumes of data. You have a choice for the type and number of sources and targets for data replication. All your unstructured data is handled well and data from this platform can be streamed into big data technologies for further ingestion and analytics. Because this is an Oracle Cloud product, you can easily integrate other Oracle cloud and non-cloud products such as Storage, Database, Exadata and Big Data Cloud with it.
For someone who is looking to master the service and offering in a greater detail, or for someone who is very new to the integration space, we are planning to offer a full-service training from Oracle University.
Data Integration Platform Cloud (DIPC) is an Oracle Cloud service that offers a single platform to connect to hundreds of on-premises and cloud data sources. From this platform you extract, load and trform (ELT) data entities of any shape and format, synchronize or replicate selected data sources, integrate with big data technologies, perform data analytics and maintain data quality.
There are several dimensions of security that Integration Cloud Service supports:
As per Gartner, Integration Platform as a Service (iPaaS) is a suite of cloud services enabling development, execution and governance of integration flows connecting any combination of on premises and cloud-based processes, services, applications and data within individual or across multiple organizations.
Yes. However we are working on a plan to deliver the same capability on-premises and in the private cloud.
Oracle Integration Cloud Service (ICS) is a simple and powerful integration platform in the cloud to maximize the value of your investments in SaaS and on-premises applications. Oracle Integration Cloud Service is Oracle's integration platform as a service (iPaas) and includes an intuitive web based integration designer for point and click integration between applications, a rich monitoring dashboard that provides real-time insight into the tractions, all of it running on a mature runtime platform on Oracle Cloud. ICS will help customers accelerate their integration projects by pre-integrating with several SaaS Applications and will significantly shorten their time-to-market through a highly intuitive user interface and a large library of SaaS Adapters.
Yes. Oracle and its partner SIs can further accelerate your time to market by designing and providing pre-built solutions on the Integration Cloud Service Platform.
Yes, starting with release 17.4.5 with the following caveats:
If your use case can be satisfied with all the conditions mentioned above, then you can create your Oracle GoldenGate artifacts — extract, data pump, and replicat, directly from within your on-premises Data Integration Platform Cloud remote agent installations and the data is routed accordingly. Connections must be defined within the Data Integration Platform Cloud Catalog for the replication source and targets.
The Data Integration Platform Cloud application in Oracle Cloud is not aware of these custom artifacts, as they are monitored outside of Data Integration Platform Cloud. Future releases will add support for monitoring these custom processes within Data Integration Platform Cloud.
Load balancers control the traffic to the applications that come with your service instances. They receive the client requests to the applications for a service and then, they distribute them among the VMs in a service instance. The overhead of encrypting and decrypting HTTPS traffic is also trferred to the load balancer. Load balancers can temporarily suspend traffic access to the service instance in order to perform routine maintenance. Each load balancer node is assigned a separate public IP address.
During initial product releases it would require a planned down-time once every month for a short duration. The patching window would be announced in advance for your information. We are looking to alleviate this in a future release.
The most relevant use cases are: