Oracle Integration Cloud Service Reviews

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. 

In our customers' organizations, Oracle Integration Cloud Service mainly integrates their other applications with the Oracle Fusion stack. It's very handy in scenarios where they want to seamlessly maintain data flow between applications, with business tools and logic validations in place.

One of the most valuable features in our integration projects is the wide range of connectivity options. OIC has built-in adapters for almost every important product in the marketplace, allowing easy connections to various applications with minimal technical interference. It also connects well with databases, file services, and object storage. The error handling capabilities are good, with rich logging features and logging analytics, allowing proactive error monitoring and notifications.

In terms of measurable benefits, we've helped clients integrate about 50 applications from different geographies using OIC Service as an enterprise integration platform.

It isn't specifically for AI-driven projects; it does provide Integration Insights, which gives some predictive measures about the integrations that have run.

The solution should improve its support. 

I've worked with Oracle Integration Cloud Service for three to four years. I'm OIC certified and have been generally satisfied with the product. 

Apart from the initial learning curve, we didn't face major challenges during implementation. Once the team got familiar with the product, it was quite easy to use thanks to its drag-and-drop interface and low-code/no-code principles.

Oracle uses a universal credit model for OCI. Clients commit to an annual budget and can choose which products to use and build during their contract period. Billing is based on consumption - you're only billed for the products you use.

I would recommend the product to others, especially companies already using Oracle as their ERP and application platform. However, companies with established integration platforms might prefer to stick with those. It has improved much with recent releases and versions, much better than three to four years back.

I would rate Oracle Integration Cloud Service between eight and nine on a scale of one to ten. They've improved performance and scalability greatly over the past few years. The main area they still need to work on is technical support, not just for the tool but across their entire product line. That's the only area where I feel they're a bit behind.

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. 

In the past, connectors were pretty much the same in all environments. In this instance, the out-of-box integration between Oracle and SAP is really beneficial for us because we have a lot of business events in Oracle cloud and we need to subscribe to them from within the PaaS. It's a very helpful feature for us. The database is also great because it's using tech cloud and we can do a traditional database like securities, which is why we're using the DB system. So there are a few good features, and of course the lookups is also good. That's a cool feature. These features are helpful to us. 

IDCS doesn't currently have a fully fledged workflow feature like they have in OIM for provisioning lifecycle management of the user, which means having to create a user in IDCS, getting approval for the financials and security before pushing into the Oracle Financial Cloud setup. They have a light version for now and that should be improved. If you want to provision a user with IDCS, you need to kick an approval process and rely on PCS for that, which is risky. We are currently using OIM as an on premise application, where you get the full suite of approval and don't have to go to other cloud applications. That's lacking in ICS. 

There's no out-of-the-box solution like OIM in IDC. There's also no in-built hierarchy for approval. You can't directly use your HR hierarchy for the approval process. It requires writing custom approval policies and maintaining the provision to do that. More approvals features would be good.

Finally, there are two options of database. You can bring your own license, or take the enterprise license and use it as a loan license which unfortunately costs. Given that we're already paying for the database enterprise, why should we go and pay again for the PaaS. We've asked about that but haven't had a good response. 

We've been using this solution for the last five months. 

I believe the solution is stable. 

We're not in production, but they've said that as long as we're not using the VM for any services, they will automatically scale it. There are a few from my team using the solution and also some developers. It will be extended as we move forward to our development and QA, UAT stage. We currently have up to 25 users but we know we can have 300 or 400. 

We're already talking to technical support and they are investigating some of our issues. They've been able to solve some things but not others. 

The initial setup was tricky. When we integrate with Concur, there were some errors and nobody knew why. Eventually we found the solution but it took some time - the solution doesn't handle all the characters that a password could have, which is a small thing. Sometimes we also need to manually restart the virtual machine because some script can run through and doesn't automatically come up. That's a problem. We're struggling with the small virtual machines. We have a system integrator in our team, but we're not quite at that stage yet. 

In general, the solution is functioning well. We already have Informatica Cloud established and we've been using it for a few years as our integration tool. We bought PaaS specificlaly for this project. Our challenge now is to test the comparison between Informative Cloud and PaaS. Informatica is a set price whereas PaaS has the meter running every time the database is extended in the virtual machine. On the other hand PaaS has the front client, the workflow, Ariba, everything. We're still evaluating.

I would rate this solution a seven out of 10. 

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. 

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

The most valuable feature of the solution is that the tool has out-of-the-box adapters. It has a list of adapters, like pre-built adapters, that can be used. The adapters are used for most of the renowned applications, and Oracle has built-in adapters, which can help to quickly connect with the services just like how Salesforce has adapters for some services that helps with quickly integration.

In Oracle, most of the things are based on XML and SOAP Messages. Nowadays, JSON is also very much in use. Most of the integrations are JSON-based with mobile phones, and all are coming into the picture. Most of the digital integrations are based on JSON. If I use Oracle Service Bus, I know it mostly uses XML and Java-based or JSON objects. Oracle has most of the message exchanges between XML, and it supports SOAP Messages. The support for JSON should be more in Oracle Integration Cloud Service.

The tool offers very good capabilities for transforming XML and objects. With JSON, if the tool provides support similar to XML, then it would be helpful. Nowadays, most things are on JSON, both digital and mobile.

The pricing model could be more flexible for clients.

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

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

The tool is more suitable for enterprise businesses.

I have contacted the solution's technical support team, and they are good since they are readily available. Based on the priority, they respond. If we have raised P1 or P2 tickets, they are readily available. It depends on the priority of the ticket. For P1 tickets, they work twenty-four hours and seven days. The support is good, and we get it on time. I rate the technical support an eight out of ten.

Positive

The product's initial setup phase is simple. It is not very complex, like moving something to the cloud.

The solution is deployed on the cloud.

The solution can be deployed in a couple of hours.

Pricing is not on the economic side since it is a tool for enterprise-sized companies.

I don't use much of the automation capabilities offered by the product.

I have not integrated Oracle Integration Cloud Services with AI tools.

Most of my technical experience is with Oracle only.

I recommend the tool to others.

I rate the tool a seven to 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.

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.

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.