What is your primary use case for Oracle Integration Cloud Service?

Use cases are integrating between SaaS and other applications, Oracle SaaS and other applications, predominantly for payment gateways and various other vendor-related applications, and connectivity between Oracle SaaS applications and the Oracle Cloud.

I use the solution in my company to integrate with different applications.

The tool is generally useful for system integrations between different applications, like Oracle and non-Oracle tools, including Oracle SFDC. It is also useful for ERP solutions like SAP, Workday, NetSuite, EBS, and Oracle Cloud ERP Platform.

We have hosted Oracle EBS applications on Oracle Integration Cloud Service.

My clients use the solution to integrate multiple systems, like ERP, SCM, EPM, and some ADP. Different integrations are there, like talent management, compensations and, AppSense OTL, time clock device integration.

I use the solution for system integration with different applications.

My use cases involve integrations and connecting to databases and REST services using REST adapters.

I am not well-versed in Oracle Integration Cloud Service. All I know is that it serves as a path or channel for us to transfer some files, but I am still unclear as to whether it is a cloud-based storage solution or a type of data communication tool. I am still trying to fully grasp the function and purpose of ICS.

My company implements this solution for our customers. The solution is typically used for any financial or supply chain implementation. We don't do it stand-alone; we typically do it with the Oracle ERP implementation. We use it to do all of the orchestration in and out of our ERP.

There are three major scenarios where we use the product. One is Oracle has applications integrated with other applications internal to the customers' organization. The second use case is having Oracle SaaS applications integrated with third-party suppliers or third-party integrator applications. For example, for a payment gateway of a bank. The third one is this OIC integration. Cloud services are used as a standardized integration platform, where they'll be used even for non-Oracle SaaS application purposes. In a hybrid model, they can use it for various applications. This becomes an integration platform to bring any other applications, whether upstream or downstream, connected to the product for services offering as well as consumption of the services.

We are vendors and implement this solution for our clients. I'm a senior Oracle SOA lead.

Whatever data is going in and out of Oracle, we are using Oracle Integration Cloud Service for any inbound or outbound integrations.

If I want to integrate with my on-premise application at the financial organization finance, I can do so. I can use the SAT finance and I have Oracle Fusion as my HR solution. I can send information from Oracle Fusion to Oracle SAP. Integration is required and I can use OICS for the dashboard. I can use two types of approaches - one is a real-time approach, and another is the best processing approach. I would always prefer to go with that best processing approach, and if we set a middle layer. It's good, however, to have options. In the middle layer, I can set up one type of integration - a Journey integration. With the Journey integration, are have personal-related information. It is already, readily, available.

Oracle ERP Fusion Cloud is used for enterprise resource planning. We have different ERP modules at HCM, such as human capital management, supply chain management, and asset work management. We use Oracle Integration Cloud to automate a large number of integrations. For example, if you want to load the employee file from, say, a boundary system or Workday, you are providing me with a file containing the employees' salaries, and designations. I need to import it into the Oracle ERP Fusion Cloud or the ERP cloud's human capital management module, but there is no simple or direct way to import that file into the ERP cloud or that CM. In Oracle Integration Cloud, we take the file, read it, and transform it to meet the MAT requirements of the ERP cloud or SIM cloud. For example, we create the HDL for a MAT file that contains HCM data, we also automate it. Basically, you provide the file, and we transform it. We will submit the job to ERP, where we will be able to encrypt, decrypt, and increase security. The Boundary system only needs to provide the file, and we will convert it to the required format and load it into the ERP cloud, sending notifications, logging, and monitoring.

This can be an Oracle-agnostic tool; it does not have to be Oracle-specific; it can integrate any other tools as well. However, it is very useful for integrating other Oracle applications. It can easily integrate Oracle Financial Suite, Oracle CPQ, and any other Oracle products, for example. When working with Oracle, this is the unmistakable integration tool we recommend. This is also an autonomous one, self-service, which is fantastic. If you need more messaging capacity, you can add it on a self-service page in the public cloud. It does a variety of market standard adapters, such as SAP, Google, and Facebook, as well as DocuSign.

We are using Oracle Integration Cloud Service to enhance application features. We have only started and we are going to do it one by one.

We had a lot of integration between our On-Premise Systems and the Oracle ERP Cloud. We used it in that context.

The main use case is "systems integration" for my company's enterprise customers across many different industry sectors. One of our customer projects that use Oracle Integration Cloud or OIC iPaaS is ERP to e-commerce integration. Integration flows were developed for keeping product inventory, prices, addresses in sync between various end-systems. Additional non-functional goals were maintainability, stability, scalability, graceful error-handling, and "predictable performance". The predictability has been verified via repeatable testing and seamless operation in production. Additionally, we have implemented other use-cases like shipping integration (such as DHL, FedEx), order flows from e-commerce to ERP, & many more granular and custom use cases specific to customer needs (e.g. implementing internal APIs to support larger enterprise business processes or application user interfaces, bulk data reconciliation and many more). In general, a cloud-based product helps avoid the high lead-up times and maintenance overheads involved in setting up in-house infrastructure, and this is adequately achieved by OIC iPaaS. OIC, in particular, is also well integrated with Oracle SaaS ERP via "business events" and easy to integrate via Rest APIs (though other integration platforms also offer API-based integration, it makes a lot of sense to use OIC if a customer already uses Oracle SaaS). OIC offers a number of pre-built technology and SaaS adapters for high productivity for a wide range of target systems, both in-house via agents and cloud/SaaS, via a very flexible range of interfaces. These include APIs by way of Rest/SOAP over http/s, files like ZIP and CSV over filesystem or S/FTP, databases, and more. All of these interface types were utilized in our customer solutions to deliver a range of functionality in the form of "integration flows".

We are a system integrator, and Oracle Integration Cloud Service is one of the solutions we work with. We also work with other vendor solutions such as Apache Camel. We provide solutions depending on the environment and preferences of our customers. I am basically connecting a number of backend systems or creating the API backends for shipping, e-commerce, and ERP integrations. There are a number of use cases, such as product price updates to e-commerce, pricing and inventory information, ERP backend, and e-commerce front end.

Our use case is for its different modular compartments. We have different target integrations with different applications such as Ariba, Concur, Workday, where we're using the connectors to connect to those applications. We're using both mechanisms and lookups and the database systems that come with OIC. We've started our DVC simple config and have integrated that database. We pulled from Ariba and Concur and pushed it into the database and we've done some mappings and changes. We're exploring more features of OIC to see what else we can use. Right now it is in lookups connections and integration, we're planning to use ATP for our transactions in the future. We also use the Visual Studio Builder and embed some customizations into this app. We will be using the VPN that comes through the Oracle PaaS and that's the strategy right now. We need to complete a final evaluation before deciding in which direction to proceed. We're customers of Oracle and I'm a customer solutions architect.

We are a solution provider and we integrate Oracle solutions for our customers. The Oracle Cloud Integration Cloud Service is one of the platforms that we are now working with, in collaboration with a local company.

It is doing great. It has its own loopholes and that's where there is an opportunity for implementation partners like us. If the product was perfect, then probably there wouldn't be a place for implementation partners. So in fact, it's not the features that attract us, but the lack of features in something like Oracle Integration Cloud leaves some room for leads implementation partners like us, some room for custom implementation services. For example, the supply chain part of the solution is not completely available for the customer as a turnkey solution so we have a role to play in terms of integration into various solutions. But not all connectors are available. With Oracle Integration Cloud we have a role in terms of connecting to different applications. Also, not all features are there. Even if we are migrating Oracle on-premise, ERP, into Oracle ERP Cloud. So it's all Oracle, but still, there are holes that we need to plug in and that's where it leaves some opportunity for us.

We primarily use the solution for integration with SAP, for its specs and factors and for integration with Oracle applications.

Our primary use for this solution is enterprise integration.

The primary use case of the solution is integration for clients.

Integration of SaaS solutions that form systems of reference. Exposing simplified APIs to digital front ends. Integration of cloud & on-premises solutions (hybrid model) supporting secured remote access to on-premises data sources.