Oracle Integration Cloud Service Reviews

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

We implemented this solution in an organization that was able to use OIC without having to procure any hardware. They bought the subscription and implemented quickly. It's the main advantage of the product. 

The solution has many valuable features including a large list of supported adapters and security. It provides various ways to secure services as well as providing extensive support.

I think this product is evolving and there are certain areas where there are still some limitations. The solution has a payload size limit and there are some legacy applications we'd like to integrate but can't. We can get what we need using our on-premise product, but not OIC. Our clients generally have on-premise servers and they have processes they'd like to convert to OIC but they're not supported and so our clients look for other solutions. I would like to see more flexibility regarding accessibility to files. 

I've been using this solution for a couple of years. 

The solution is generally stable. Sometimes changes come through that are not supported by OIC and we have to find a workaround and modify them manually. 

The solution is scalable but we haven't tested that yet. We tried to download a large file from a CM cloud but services were getting timed out because it took longer than five minutes.

Technical support is generally okay but some of the staff are not sufficiently experienced. 

For basic requirements, the initial setup is easy but when you start integrating more complex applications, it can become more complicated. We carried out a deployment that included the build, design, and development to production and it took about six months for around 10 processes. We have three developers who work on OIC and we maintain, develop and enhance the product. 

I'm unaware of licensing costs but I know that Oracle requires the purchase of two separate products, with separate billing. If I want one integration with API CS, I have to pay twice for the one call. It's one of the major factors for clients not choosing this product and it should be included in the API CS part of OIP.

We're always evaluating other tools like Microsoft Azure which might be more useful for some of our clients. 

It's worth evaluating all options including on-prem ones as well as other products in the market, like MuleSoft and Microsoft Azure, comparing features and cost. You might choose a product based on cost and then find there will be limitations in terms of the features it provides.

I rate this solution seven out of 10. 

Our typical use case is getting data, either real-time or bulk data. So, in the case of bulk data, we use Oracle Integration Cloud Service to get to an FTP location and read the file from the FTP location and do the necessary transforms in the solution and send it to the Oracle Cloud.

For real-time, we use Oracle Integration Cloud Service to expose the guest services to the consumers. We send data to the Oracle Integration Cloud Service from on-premise applications. After that, we send it to Oracle Cloud and other third-party application file sorts. For example, we integrated with a bank in the past. We sent data to HSBC bank and City Bank using the Oracle Integration Cloud Service.

The features I find the most valuable are the schedule and app-driven integrations. Some 90% of our use cases are covered by these two components. Sometimes we have to create a PaaS component. For that, we have to go for the DVCS screen in case the customer wants to have a screen where they can visualize their data. 

There is room for improvement with the Process Cloud Service (PCS) component. I would like to be able to implement a workflow in the PCS component because it is not as straightforward to use, even with help from the documentation. We are always having to take training if we want to implement a PCS component. The PCS component is the most complicated aspect of Oracle Integration Cloud Service. The PCS component should either be improved or Oracle should create some training documentation for this component specifically. I have not been able to find any training documentation for the PCS component. 

Oracle has parent and child integrations and once the parent submits a job to the child, it doesn't wait for a response. Some of our use cases are more complicated and there may be one parent integration and two child integrations. In this scenario, if one child finishes first, the parent may remove the second child's integration. This sort of scenario is difficult to resolve because the parent calls the child one integration and does not wait for the response.

In most of the scenarios we have, the child one integration should be completed before the child two integration is called, but the solution doesn't behave in that way. It parallel calls both child one integration and child two integration. What we often do is avoid the parent and child relationship and go for one big complex integration where you do everything for the parent. 

I have been working with Oracle Integration Cloud Service for three to four years, typically integrating on-premises applications with the cloud.

I find Oracle Integration Cloud Service pretty simple and stable. 

Oracle Integration Cloud Service is scalable. We have not had any performance issues with it. It behaves well. 

Sometimes, the tech support is slow to get back to us. We have had to wait up to two weeks for a response. However, if we follow up on a ticket, they do respond fast. 

Neutral

The Oracle Integration Cloud Service initial setup is easy. It is simple to understand and learn. However, we have run into a few problems on the Oracle SaaS cloud side. We have had to create a tech support ticket with Oracle to get our issue resolved.

We do deployments in-house. We usually have a small deployment team, in addition to an on-premises team, which takes care of the on-premise applications. We also have an Oracle ERP Cloud team, which takes care of the functional aspects of Oracle in Oracle ERP Cloud. 

Our deployment team usually consists of two to three people. How big the deployment team is depends on the number of integrations, but it is fairly simple in the OIC. 

The development team will usually include 10 people, however, we ramp it down to six people for maintenance. 

Oracle Integration Cloud Service is a really good product and the ROI is very good with it. It lowers development time. A development cycle that may have taken a year without Oracle Integration Cloud Service can drop down to three or four months with it. 

I do not deal with the licensing costs directly but I have seen the numbers. Whenever we have to get a license for the OIC, we have to get at least three environments: production, development, and UI test instance. The cost for these three instances is about $100,000 per year. 

I find the licensing a little expensive. If customers are already using Oracle products, they can often get deals and bring down their costs.

We do have trouble with a lack of knowledge about Oracle Integration Cloud Service. Sometimes, customers want us to achieve certain things with integrations that are not so simple. Those use cases are tricky and OIC is not the right solution for all use cases. 

My advice to those looking to implement Oracle Integration Cloud Service is this: you have to have experience with hand-on integration and developing integrations before you can work in a live scenario. 

On a scale of one to 10, with one being the worst and 10 being the best, I would rate Oracle Integration Cloud Service with an eight for overall performance. 

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

Oracle Integration Cloud Service can improve file handling. Currently, our real-time file polling limitation is 10 MB, if that size can be increased it would be helpful. For example, increasing the size from 10 MB to 1 GB.

I have been using Oracle Integration Cloud Service for approximately 

We have been satisfied with the performance of Oracle Integration Cloud Service.

Oracle Integration Cloud Service is scalable.

We have approximately 30 IT experts in my small organization. We have plans to increase the usage of the solution in the future.

Oracle has a support portal where we can raise a service request and we can have our issues addressed. They provide an average level of support.

I have not used another similar solution prior to Oracle Integration Cloud Service.

The initial setup of Oracle Integration Cloud Service was easy.

The deployment is very easy to export from one and import from another, it only requires a simple one-button click. For 100 integrations it can take 30 minutes. We usually use microservice for very small integrations and then connect them together.

The deployment of Oracle Integration Cloud Service was done in-house.

We have one person who does the deployment and maintenance of Oracle Integration Cloud Service.

My advice to others is if you are looking for integrations with other Oracle solutions, then this is a great choice. Otherwise, you can explore other middleware platforms.

I rate Oracle Integration Cloud Service an eight out of ten.

The most valuable features of Oracle Integration Cloud Service are the seeded integrations with many communication platforms, such as Slack and emails. It works best for the historical communication methods. Those are still prevalent with all the other clients. When we are doing the integrations, it makes it a little bit easier for us to communicate the same output over Slack, rather than sending out an email and downloading the report. The number of seeded functionalities within the Oracle Integration Cloud Service platform is better. 

Oracle Integration Cloud Service can improve the downloading and uploading of files. I've submitted this issue to the Oracle Idea Labs. The issue is from the front end of Oracle Integration Cloud, we cannot download or upload a file directly or drag and drop it.

I have been using Oracle Integration Cloud Service for approximately three years.

Oracle Integration Cloud Service is highly stable.

The stability of Oracle Integration Cloud Service is great.

We have approximately 100 people using this solution in my company. In my client's company, there are approximately 50 users using it with plans to increase usage.

I have not used the technical support from Oracle. However, I did have contact with the support regarding the package cost of the solution and the response I received was good.

I have not used another solution in the same category as Oracle Integration Cloud Service.

The initial setup of Oracle Integration Cloud Service is very simple and easy to navigate around. For a user to be created and set up, takes approximately five minutes.

We have a technical team of 10. Five of them deal with the implementation, and the other five are handling other aspects, such as maintaining the schedule and any kind of changes requested on an ad-hoc basis

We have seen a return on investment, our client always renews their license.

The price of Oracle Integration Cloud Service is good. It is reasonable and is priced well for the market segment. The model they use is on a per-package unit and we have a two-year subscription.

Others looking into implementing Oracle Integration Cloud Service should explore more as and when new updates and patches are coming out and if their business would fit well with Oracle Integration Cloud Service.

I rate Oracle Integration Cloud Service an eight out of ten.

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. 

Overall, it's a very good product.

It offers a lot of stability and flexibility. 

The initial setup is easy.

The solution did use to have stability issues, however, that is now dealt with.

The solution is expensive. 

We would always prefer any solution to be more secure. 

I'd rate the solution for three to four years now. I've used it for a while. 

For the first few years, the solution was not stable. It is much more stable now in this instance. It's been stable for about two years or so now. 

We have seven or eight clients using this solution currently. They use a variety of other Oracle products as well that we have helped arrange. 

Oracle has a great dedicated service team. If you have to make a service request, you will get the solution. A forum is also available as are landing guides, which are quite helpful. Based on my experience, they are readily available to assist in multiple ways.

The initial setup is easy. However, the provisioning is employee-based. The provisioning is based on the message list, that we have purchased. 

It did not take that long especially if you have already worked with or had Oracle. Some pre-setup is required, from an organizational perspective. For us, we took data from our on-premises system and installed the OIC agent. 

Our middle layer isn't accessible from anywhere purposefully. That integration was via the internet only. 

In general, the setup and other requirements surrounding the implementation will take time. We had to arrange policies, et cetera, before even beginning the setup process. 

The price could be better and they need to work on their licensing model to make it easier for users. 

We are an implementor. I'm also an Oracle Prime customer. I'm currently using that Oracle for many years and I have a complete ecosystem in Oracle.

Earlier, due to instability, at that time I would never suggest that anyone go with that OICS, integration cloud service. However, now that Oracle has improved a lot in the OIC part, I would recommend it. However, it depends on that ecosystem. If the surrounding technology is related to Oracle, it's a great integration tool. I would always prefer that OICS. However, some SAP or some other tools might not be as available and we would have to build some custom solution. Of course, rather than the customized adapter, we would prefer to go with a standardized one. It really just depends on the environment.

I'd rate the solution nine out of ten.

The out-of-the-box adapters are the most valuable aspect of the solution.

It was easy to set up.

The solution is robust.

You can scale it as needed.

Technical support responds quickly.

The bulk processing needs improvement. When the data it needs to process is huge, then it does not work well, for example, when we're talking about gigabytes or terabytes. If data is received in this way, then this middleware doesn't work properly.

We would like to see more out-of-the-box adapters with different boundary applications.

The solution needs the support of more EDI protocols, like RosettaNet.

I have joined this organization recently. I joined eight months ago, and have used the solution since then. However, I'm not sure for how long the company has used it. 

The solution is robust and the stability is good. There are no bugs or glitches. 

The solution can scale quite well.

Technical support is quite fast. We are happy with their level of response.

The initial setup is not difficult or complex. It's quite straightforward. 

How much maintenance is required after implementation depends on the number of integrations. For example, if there are 100 integrations, then around five people will be required to maintain everything.

We are implementors. We are able to deploy this product for our clients. 

The licensing costs need to be checked from the Oracle portal.

Typically, there is just a standard licensing fee.

We are the implementers of the product.

We are using the latest version of the product.

If a company is integrating this product with file-based integration, then it is very good. It provides good monitoring and tracking as well. B2B capabilities earlier were not there, however, now they are coming up with the B2B capabilities where EDI-related interfaces can be handled well. That said, bulk processing is still a challenge

I'd rate the product an eight out of ten.

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

As a technical person, I find most of the features valuable, but I particularly like the drag-and-drop feature for designing integrations and processes.

In designer mode, sometimes the browser closure or other unknown issues can cause strange behavior, which requires a restart. I've also experienced issues with caching.

It's been around four years since I started working with it. I am using the latest version because cloud versions get updated in the background frequently.

I have never seen any issue with stability.

Scalability is a complex thing, as when we scale with more instances and requests, there will be costs attached to it. However, OIC can be scaled and it scales automatically.

The customer service and support team is good. Sometimes we had issues achieving certain functionalities, and we contacted support for assistance.

Positive

The initial setup is super easy. Most of the setup is super easy nowadays, with just a few clicks. Whether it's in space creation or configuration, I find it's a nice feature.

The deployment process is all CICD and it doesn't take much time, maybe within half an hour, we can deploy one application or promote from one environment to another environment.

The pricing models vary, and they can be per-message, fact-based, or incident-based. So, there are different pricing models available for users. 

I would definitely recommend using the solution. 

Based on my understanding, I would rate it eight out of ten. There are still features that could or should be added, and I believe it is still evolving.

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.

Oracle Integration Cloud Service integrates well and is user-friendly. If you are not a developer or ops engineer you can still use the solution with ease. You do not need to have developers' knowledge, you can easily adapt and learn quickly to integrate the services. They have good documentation.  

There are a few features that we noticed are not in the cloud. There are some improvements needed. One example is the graphical user interface that needs to improve, it could be easier to use.

I have been using Oracle Integration Cloud Service for approximately two years.

Since we have been using Oracle Integration Cloud Service we have not had any problems. I am not sure what the future will bring, but it has been great. AWS was down for a period of time and no one expected it. There were outages for Azure and Oracle cloud. We cannot predict the future, no one can be certain about the stability of these solutions.

We might see some interruptions in the future. They're doing a very good job because they're expanding their regions. Recently they opened three to four regions, Italy, India, and a few in the Middle East. I don't think there will be any scaling problems or availability problems in the future for Oracle. 

The solution is scalable.

For those who have Oracle on-premise, Oracle Cloud is the best solution because when we tried to migrate to Azure and Google cloud, we could not meet their expectations.

The native Oracle application can easily migrate to Oracle Cloud. If you're trying to migrate to AWS, Google, or Azure, we need a lot of effort and there are is a challenge to redesign everything. If it is a popular application, it is a bit tough to redesign applications to be compatible with Azure, Google, or AWS.  

I rate Oracle Integration Cloud Service a seven out of ten.

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

The adapter was pretty useful. The visualization tool was pretty useful, too. Drag and drop features — those are pretty good. In general, there were a lot of great utilities for working with files. 

We were using this solution, but we recently stopped using it four months ago. 

This solution was fairly stable. We never had any issues with it.

We used to face some issues when we tried to connect to the Oracle ERP Cloud. When we were trying to run a job on the ERP Cloud site, when the integration was complete, the job on the Cloud would still be running. We couldn't completely monitor the execution of that integration. There were instances when the integration finished, and at the end of the retry count, the thing was still running — the job on the ERP Cloud site was still running. 

Because of this, we had to keep pulling the job on the ERP Cloud site to find out if it was finished or not; but you can't keep doing that forever. We would retry and after five attempts, we would find out that the job was still running. We just had to report back saying that the job was still running on the ERP Cloud site. There was no way of knowing whether a job was completed successfully or not — unless we logged into the Oracle ERP Cloud and checked the status of a particular job.

The support and resources were lacking — they weren't there. Coming from an AWS background, the difference between Oracle Support and the resources and support of AWS was like night and day. 

Although I wasn't involved in the initial setup, I know it's fairly straightforward. I've done it in one of the classes that I've taken, but when I came to this company, it was already set up. It's quite straightforward; you just need to specify the compartment and where you would like to install it. 

When comparing AWS to the Oracle Cloud, I don't see an equivalent platform. There is no ESB as such currently on AWS. AWS has a lot of other services like a queuing service, national servers, SQL Servers, etc. If you want to integrate with Oracle and SAS applications, then this is a pretty good solution. On the flip side, OIC has a limited number of resources, including support — there are just one or two courses to go by. I wasn't happy with the instructions that we received and the number of materials and resources; it made it hard for us to learn how to properly use it. 

All things considered, it's a fairly good platform. Overall, on a scale from one to ten, I would give Oracle Integration Cloud Service a rating of seven. If they improved the amount of support and resources available, I would give them a higher rating. 

Integration of SaaS solutions that form systems of reference. Exposing simplified APIs to digital front ends.

Expoit its deep integration to Oracle apps and SaaS so we can have event driven integration.

Take advantage of the rich catalogue of prebuilt integration adaptors covering RPA, SAP, Salesforce, ServiceNow etc etc

Integration of cloud & on-premises solutions  (hybrid model) supporting secured remote access to on-premises data sources.

The integration of cloud solutions and realizing Hybrid intergrations with existing on-premises solutions has become far easier (compared to SOA suite).

The movement from ICS to Oracle Integration Cloud (OIC) has meant the introduction of additional capabilities which will be of positiver value such as Visual Cloud builder, scaling restrictictions of ICS removed.

• The simplicity and ease of creating SOAP and REST endpoints and integrating with them. New features being added regularly to make it a significant integration platform.

Some of the adapters could be enhanced to make integration even simpler.

The example I would use is the GMail interface - it requires Base64 encoded content. But to make the interface simpler, the API should provide the encoding and the adapter simply accept plain text.

Depending on our customer upto 4 years

No stability issues.

There are volumetric constraints today driven by licensing, but we haven't encountered an issue with this. However, people should consider them before signing up.

Customer Service:

The solution is self-serve, so little contact is necessary. When we have spoken to Oracle (more to ask questions about future features), we have had friendly, helpful engagement.

Technical Support:

Technical support is good

SOA. Adopting ICS with JCS offers a cost effective and flexible platform

Initial setup was a piece of pie.

Own team

Agility, now middleware deployment challenges (excluding agents - but they are pretty simple)

Look at volumetric and the number of different connections

Other Oracle integration options that can help with hybrid use cases

Look carefully at the adaptors, they aren't always fully featured when announced.