Oracle Integration Cloud Service Reviews

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.

The solution's most valuable feature is its integration capabilities, and we don't use Oracle PCS too much. To some extent, we use Oracle VBCS for extensions. I think we use the integrated SFTP server sometimes. From OIC, we mostly use the above-mentioned components.

In terms of the area of improvement in the product, I would say that the way we design the services is very limited. The kind of architectural design we can have is an area that is pretty limited if I compare it with a tool named Boomi. We could not expect everything to be done like what we have done in Oracle, SOA Suite, or MuleSoft. The design is limited to five or six design approaches, and within that, the number of activities is limited. The debugging part is sometimes difficult in the tool.

There have been situations where the drag-and-drop features might not work, so you need to include some coding, but it may not be that user-friendly. If I compare it with Boomi, you can put Groovy and some other scripting languages, which might help you navigate tricky situations where your drag-and-drop feature doesn't work.

I would not say the tool is lacking in something. There might be different ways to do it. If somebody has to choose between a couple of products, they can choose Oracle Integration Cloud Service as one part, and the other part is the deployment environment. We are still in Oracle Cloud, and if the things in it can be moved to AWS or Azure and made compatible with other tools, then it would be good.

I have been using Oracle Integration Cloud Service for seven years.

It is a good and stable solution. Stability-wise, I rate the solution a seven to eight out of ten. Considering that Oracle's stability is not the best, I would say that I rate Boomi's stability as higher if I look at the runtime environment.

The tool's load-bearing capacity is a little bit lower compared with Oracle products like Oracle SOA. If there is a long-running process with a lot of data, it crashes. In normal scenarios, you can keep on adding new servers or you can just ask for an extension, but with Oracle Integration Cloud Service, it is difficult. The flexibility is not available to the client.

Considering the product's pricing model, I think the tool is more suitable for medium to large-sized enterprises. I don't think smaller businesses would actually benefit from the use of the tool unless Oracle comes up with a pricing plan that is beneficial for them. With the tool, we do not have different levels of runtime. Runtime is something that consumes a lot of money, and that is why it may not support smaller teams where the user base is smaller.

The tool's technical support is lacking. Unless one goes to advanced support, like connecting to the product team, then they are good, but the frontline team handling the initial stages of your issues is where the delay is happening. They are not very capable of understanding the tool per se. Overall, they understand, but if I am raising a ticket for Oracle Integration Cloud, they should be well-equipped to handle or at least debug certain things.

I have experience with Boomi and Oracle Integration Cloud Service. Both products have their own pros and cons. Oracle works well with activities and mapping. The mapping thing is very good in Oracle. Oracle lacks interoperability, the runtime environment, and the flexibility within the product. Oracle's processing power is not what we have seen with WebLogic. With Oracle SOA and WebLogic, the processing power speed was lightning-fast. The processing power is a little bit slower in Oracle than in Boomi. The price of Oracle Integration Cloud Service is much better than what Boomi offers.

The product's initial setup phase is the best since we don't have to do anything. There is nothing like where you need to do some kind of scaling or capacity planning. We don't have different tiers for it. If somebody wants to have a higher capacity, and if that is available, then it is an addition to your arsenal. As of now, it is good.

If I consider the automation options, code importing and code porting to different environments were the reasons we used it in our company. We used OIC REST API services for automation.

I only work with Oracle Cloud deployment.

I think that considering the features, most of the clients move from a legacy integration tool to a cloud, so they always expect more of a seamless approach. Suppose Oracle can jump into a scene and provide assistance in the capacity of helping users navigate from on-premises to the cloud. My company, as a partner, can do our bit, but there is always a gap. If I compare Oracle Integration Cloud Service with other tools, I see that they are pushing it and always trying to sell it using different approaches.

I recommend the tool to others. Customers who are familiar with Oracle SOA might find Oracle Integration Cloud Service to be 70 to 80 percent similar.

I rate the overall tool an eight out of ten.

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

The product provides an easy and low-code integration process. We can quickly build web applications using it.

Oracle Integration Cloud Service offers a lot of adaptors.

Oracle Integration Cloud Service could have better intuitiveness compared to Microsoft products. It has lengthy documentation, making the process of building applications more time-consuming. These particular areas need improvement.

We have been using Oracle Integration Cloud Service for four years.

I rate the platform's stability a nine out of ten.

I rate the product's scalability an eight out of ten.

We follow Oracle SR links. They respond faster if the question is properly routed to their technical team. If insufficient information is provided while raising queries, they take a few weeks to answer.

The initial setup process is straightforward.

The product generates a return on investment by reducing the development time.

I rate Oracle Integration Cloud Service an eight out of ten. The product's tutorial video helps us understand the technology and quickly work on it.

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.

The OIC is very good. It comes with a lot of pre-built integration APIs. It's already there, so it's very helpful for integrations and they can serve very specific purposes also. The actual good old days of programming or coding to make the integration work at a precise level of expertise or work is not needed. That's the advantage here. It's user-friendly.

The job of Oracle is to offer us a total service, including licenses, support fees, postings, visas, et cetera. Everything is bundled. That makes everything easier.

From a security perspective, a connectivity perspective, and the ability to set it up as a hybrid, the solution is very good.

It is easy to set up the product.

The solution is stable. 

We can scale the solution. 

We would love to have more and more ready-to-use interfaces from Oracle. We'd like to download the marketplace right away. We'd like it, so we don't have to put in so much effort with integration. Therefore, I'm still keen to see a continuation in the addition of ready-to-use interfaces. 

This solution is recent, however, we have been partners with Oracle for the last about 20 or 25 years. This solution is more recent. We've only used it for about four or five years if you include the previous version of the cloud product.

The solution is very stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. The performance is good. 

It can scale. You can just keep provisioning it. Of course, you need additional computing power, however, you can always add it. It comes with a certain cost, which needs to be considered. That said, the scalability is there; you can increase, optimize, or decrease it also.

Technical support is really good, actually. There are no issues as such in terms of product support or anything like that. Everything is done from the Oracle side itself.

The solution is very straightforward and simple to set up. 

It is relatively easy and not that difficult. At the moment, you just provision and subscribe to it, you just need to provision it. We can do it on our own; it's not a big task.

Just to set it up, you don't need too many people. One person is enough to do the deployment. However, if you want to deploy various integrations, then it depends on the number of applications, and the number of integrations you need to deploy and set it up. If there are maybe ten to 15 integrations, you can do it in less than six weeks or so.

Still, if there are a lot of complexities and too many products are there, and you want to do it very quickly, then you need to add manpower to load it. Otherwise, it is relatively straightforward. Typically, you will need engineers to handle the deployment. 

We were able to handle the deployment ourselves. 

The return on investment is there, especially in terms of operations part. From a licensing perspective or management perspective, the patching, and all these other things are taken care of straight away by Oracle. We don't have to allocate time.

Therefore, maintenance administration or around 40% of the activities or efforts now happens automatically. Since it is ready to use and the majority of the services are available, there is a significant amount of time and labor savings in terms of effort reduction.

I'm an Oracle partner. 

We deal with the most up-to-date version of the product.

One has to understand their requirements before deploying the solution. You need to analyze it and see whether it is available for them to leverage its capabilities. Most of the interfaces are already in place. You just need to provision it and configure it. That's it.

This is a relatively new product. It may still need maturing, however, it is already quite good.

I'd rate it eight out of ten.

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.

We use the solution for inbound and outbound integrations.

Integration Cloud and Visual Builder Cloud Service (VBCS) are the solution's most valuable features.

We encounter challenges with the solution's REST service while exporting demographic data from Oracle Time and Labor to a third-party application. It is challenging to produce reports for larger data sets.

We have been using the solution for five years.

It is a highly stable solution. I rate its stability a ten out of ten.

I rate the solution's scalability a nine out of ten. We have more than 100 solution users in our organization.

We encounter issues while raising the change request. It is complicated to follow multiple steps to identify the correct incident category. This area needs improvement. Also, it would be helpful if the same representative addresses multiple service requests of the same issue for better coordination.

Positive

We have used Azure Logic Apps before. It provides advanced customization and integration with multiple third-party systems. In comparison, Oracle is easy to use and understand.

The solution's initial setup process is straightforward. It provides easy-to-understand documents to refer to for implementation. Depending on the business requirements, it takes around five minutes to one or two days to complete.

I rate the process a nine out of ten.

The solution's pricing is relatively lower than other vendors.

If you already use the Oracle ERP system, you should opt for OIC. It is a stable and low-cost solution. It has user-friendly features and impressive integration capabilities. Also, it provides regular updates.

I rate it a ten out of ten.

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. 

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.