Oracle Integration Cloud Service Reviews

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.

Coupa is a purchasing system that connects purchase invoices to our Oracle payables module. You may not know anything about Coupa, but if you have a Coupa adapter connection, you can drag and drop, and then you can simply get the Coupa connection. It will automatically connect to Coupa and pull data from it. 

Because it can easily connect to Oracle natively, it connects to Oracle and pushes data into Oracle. This is one of your use cases. You can also use Concur, which is an expensive product.

Another option is to transfer expense invoices from the Concur system to the Oracle payables model. It's the same thing back and forth; you can even push data from Oracle to Coupa if you need to send an acknowledgment.

The most valuable features of this solution are the SFTP adapters, file adapters, and risk adapters, that we use in everyday projects.

In terms of improvement, debugging and error handling, Oracle can be much more user-friendly on this, because clients must provide a much more error handling framework, which is a monitoring framework, that is much better. 

The current one has some level of monitoring, but then there are retrying mechanisms, automatically retrying mechanisms and error recovery mechanisms. Those things need to be greatly improved; they have something, but it is very basic.

The error retrying mechanism could be improved. If an error occurs, it can be retried automatically, it would be helpful.

Resilience can be enhanced.

The migration flow has to improve.

They have some kind of agent connecting with the on-premise systems. We need to simplify the process of connecting with non-cloud applications.

If you have to connect to some servers from this cloud to non-cloud, that is a bit of a hassle.

They now have something called an agent for those, but they can simplify it, and the error frameworks can be implemented much more effectively.

ICS is the correct solution but it is a bit old. The advanced version of ICS is called OIC Gen 2 (Oracle Integration Cloud Generation 2).

We probably used ICS a few years ago. Those are now out of date, and Oracle will not be releasing that product. It is probably supported, but Oracle has migrated away from that product at least two years ago. With ICS, you can't just publish that because it's out of date. You may be able to correct it if Oracle upgraded it to OIC.

I have been using Oracle Integration Cloud Service for two or three years. Not recently, but sometime in 2017 or 2018.

In the last 12 months we used it, but not the ICS version; instead, the most recent version was used.

OIC Gen 2 is the latest version.

Stability is, I believe, 90%. 10% is because the runtime system, at times, becomes unstable due to data center issues, or things that have gone wrong in productions. But that is probably only 2% of the problem; the remaining 8% will have intermittent problems.

There are some restrictions. That is something that bothers us because there are some service limitations. For example, the file size is limited to this amount; there are some restrictions. Oracle claims that it is being restricted internally due to performance issues. 

If you use a file larger than a GB or something, they offer very different adapters with different restrictions, that is all. 

According to the current situation, we will either split the file and then manage it internally. But it adds a lot of, sometimes unnecessary, overhead for us because the team implements; we need to improve that. There are some things they can work on to improve.

The solution is only used by the core IT team; no one else uses it.  It will be a five-person team from the client's side.

Not more than five, because the client's IT teams are limited to five people, and they only manage it. There are a maximum of five people.

We use it every day.

On a scale of one to five, I would rate technical support as four. 1 percent of the time, Oracle responses, support status, depending on the engineer, I believe 1 percent will be a good or bad experience.

Positive

On the technology side, we have something called Oracle Autonomous Database or Oracle Integration Cloud on the platform.

Google Cloud Platform I worked with a few years ago, but not recently. However, I am currently involved with Oracle Cloud.

We were using it for one of our Mexican clients. We probably used it for a year and a half. They are still using it, but I am not in contact with that client, but everything is going well for them.

I understand the fundamentals of Google Cloud SQL as well as other frameworks they provide, such as Spark. We also used their database.

Spark by Apache. That is something; that was used to handle all of the panel processing tasks and was something we didn't have in Oracle. We won't have as much leverage in Oracle, but we'll have many tools.

We use them primarily for performance handling. Heavy data can be easily processed in a memory partition, which they do in the memory, and then process in different pipelines concurrently, which is made efficient. That was really good, and they had a lot of leverage in terms of monitoring those files that were being loaded into the system. They had detailed logging and could monitor everything from their consoles. Which is good.

I am familiar with the Java Cloud and the Developer Cloud, but neither was used by us. Oracle Autonomous Transaction Processing, also known as ATP, is what we used. Not mobile Autonomous Transaction Processing Database It has nothing to do with mobile; it is simply Oracle or ATP.

The beauty of this Autonomous Transaction Processing is that it is nothing more than a database, but it is not the database cluster that Oracle provides. The main advantage of this is that, as you can see, everything is managed internally by artificial intelligence. You want to scale the processor's memory, but everything is already scaled.

There is no DVA to maintain that; it all happens automatically. When you submit a request, it is automatically adjusted and scalable.

Not Oracle Data Integration Cloud Service, which is designed specifically for data conversion, but rather a middleware, solution from Oracle, that is known as SOA Suite. Oracle has an SOA suite, but the thinner version of it is, and this is one Oracle is promoting, it is Oracle Integration Cloud.

Google is in Oracle because we are mostly all Oracle. Oracle, because we only tried the Google platform once because the client specifically requested it.

We normally recommend it because this Oracle product integrates with all Oracle products and we only implement Oracle products. This easily connects with all Oracle products in the ecosystem, the time you save is actually beneficial. 

Then this product is very specific to Oracle, it can be general, but it has very good features when trying to integrate with Oracle products.

The initial setup is easy.

I would rate the initial setup a four out of five.

This is where the deployment side comes into play. Oracle does not provide an out-of-the-box way to migrate or deploy from one environment to another. This needs to be improved. We can do it in a custom way, but Oracle should have some sort of migration flow.

This solution requires a developer, an administrator, and multiple developers to maintain it. I mean, depending on the size of your project, you can have a minimum of 2, 3 up to 10, depending on the complexity of your system.

As this is a cloud, I have seen a return on investment. It has reduced the number of administrators required to maintain the servers, but this is due to the fact that they are autonomous self-services.

I would rate it a five out of five.

Licensing costs vary from client to client, depending on the client's other products purchased. 

They look at discounts, and these are all based on a contract, not a flat rate. It specifies how much data you use and how much storage you require, among other things. 

Depending on the requirements. For example, it depends on the message, and how much data throughput will go through.

I would rate the price a three out of five. 

I know there are many other competing products, but Oracle can probably be a little bit cheaper than this.

There are no additional fees to the standard licensing fee.

We explored Google, as well as MuleSoft, and Dell has an integration solution.

In general, there are multiple platforms with the Oracle platform. For example, in Google Cloud, one of the services is a database. Oracle can also have multiple services, corresponding database service, that is an Oracle database service. But, to the best of my knowledge, that framework is not available in Oracle. Google is more Java-based, so they have a lot of Java frameworks that can be used.

We will recommend this to all of our clients because it is a feature that Oracle is promoting, and it is working well for us. 

We recommend that you use this product.

I strongly advise them to use this if they are using Oracle-related solutions, and they can definitely try it because, in addition to Oracle, it has other connectivities, such as I mentioned Concur, Coupa, and SAP. They have connectors for that as well, they should try it out.

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

The remaining two are due to pending items. It's a bit lightweight. When it comes to heavy volume data handling, they should improve something, but the rest is fine.

We are Oracle's golden partners. We implement Oracle products.

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.

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. 

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.

There was initially we had two products on-premises, with were BPEL and Oracle Service Bus. When stateless integrations were required, we used Oracle Service Bus, and when a large flow was required, as well as a long-running process, we used BPEL (Business Process Execution Language). Oracle has removed these two distinctions and has merged them into one. Oracle Integration Cloud Service can create two services: one that is simple request and response, and one that can run for an extended period of time which is a good thing. That is extremely valuable. As an organization, you do not have to buy a separate product or two separate products for it.

Furthermore, everything is now under Oracle's control, from an infrastructure standpoint. Initially, when we had an on-premise structure or the on-premise SOA Suite, we had to maintain the logs and server as an organization.

It was entirely the organization's fault if the server crashed. They needed to hire web logic administrators. There was another layer. There was an administrative layer and a development layer. There were a lot of node managers and admin managers. We no longer have to be concerned about infrastructure at all. If the server fails, Oracle will take care of it. We do not need to engage in web logic administration consultations to investigate this. The Oracle is in charge of everything. And if there is any maintenance, Oracle will take care of it as well.

They will provide you with a timeline stating that on this day, we will be performing upgrades or releasing some manuals or updates. Oracle has completely automated this process. You no longer need to be concerned about it. There is no web logic, nothing.

The dashboard provided by Oracle Integration Cloud for monitoring and error handling is very intuitive. For example, if I trigger the integration and can also schedule it within OIC, there is no need for a third-party scheduler to schedule the integration in the OIC integration cloud. 

We do have a good scheduler in place. We also have encryption and decryption systems in place. Which is good. 

With the dashboard for monitoring, you do not need a third-party dashboard or logging framework when you initiate the integration.

We can certainly create some logging framework, but for some of the lightweight integrations or logging where we do not want to retain the data for an extended period of time, the logging framework within the OIC is sufficient. The dashboard is excellent. You get a clear picture of how it works, where the flow is, logs, log management, and everything.

It is simple to incorporate into some of the best products. I can, for example, directly integrate with Workday and Oracle. There are many adapters directly available, as well as numerous inbuilt integrations shared by Oracle. We can use it as is with a little tweaking. 

There are a lot of adapters, which is what I like the most. This greatly simplifies the integration. There is no web service. You should not be concerned about it. You simply configure that after, and there will be direct connectivity, which you can use as it is. There are many options.

This is entirely web-based development. We lack an IDE for developing integrations. Back in the days of OSB and BEPL, we had to go into the code and not just drag and drop. We used to go into XML and modify it. We could, for example, edit some XSLT or XQuery documentation, but this is mostly a drag-and-drop. A person cannot directly enter the code or examine and modify so many variables. As a result, one had to rely solely on the drag and drop feature.

Oracle has implemented a few modifications. For example, you can now manually edit the XSLT by going into the code, but there are many things you cannot change. You cannot move from one location to another. UI-based controls still have room to improve, but migration can be made simple. If we are migrating integrations from one environment to another, such as development to testing, if it is a one-click migration, which is possible in some cases, that would have been good.

As of now, we simply export the IIR and import it into the new environment. Migration and the User Interface could be improved.

Make it more similar to the on-premises features. For example, if you can edit the code directly rather than just dragging and dropping, or if you can edit the examples by going into the background, and one-click migration, I'd like to see included in the next release.

I have been using Oracle Integration Cloud Service since 2016, nearly five or six years.

I am working with the most recent version, which is deployed on the Oracle infrastructure.

I find the performance to be really good, mostly, but it depends on the implementation, how the developer implements it, or what the design and patterns are, but I find the performance to be really, really good. Furthermore, Oracle is constantly improving the OCI infrastructure. 

We now have many features and options, such as buckets for Object Cloud Storage. You don't have to rely on the FTP server as much; if it's a file-based integration, you can use file buckets directly to access the files. 

In terms of performance, I think it's good. And the stability, it is stable. I haven't faced many issues. We do encounter slowness on occasion. For example, if there are other integrations, sometimes there is slowness, and we immediately raise an SR with Oracle, and they work on it.

It is easily scalable. For example, if you want to add servers to an existing set of servers to increase elasticity, it is easy. As demand changes, the elasticity can be reduced or increased.

It is also dynamic. It is dynamic in some of its features. It automatically enhances the server if it is needed more and reduces the servers if they are idle for an extended period of time.

We work for a variety of clients. I am sure there are a lot of clients who are currently using this Oracle Integration Cloud solution.

We do have an Oracle practice we call Oracle COE which stands for Center Of Excellence. For just OIC, I would estimate that we have a global team of over 500 developers.

Just for OIC, we have Fusion products separately, Oracle integration, ERP Cloud, and SIM cloud, that is the SaaS layer, but they can be more than 500 developers for the PaaS layer.

This solution is extensively being used by our organization.

I believe it will be used even more or remain stable, but I do not believe its demand will decrease. But, the usage will be more.

I would rate the technical support a four out of five. There is always room to improve.

Positive

I was previously working on the on-premise middleware solution, the Oracle SOA (Service Oriented Architecture) Suite, which included BPEL and Oracle Service Bus, but everything was later moved to the cloud.

Oracle Integration Cloud is now available. It was first introduced around 2014 or 2015.

I began working with the on-premises solution. Then there's the cloud. There was an Oracle server switch stack on-premise. I've been using the Oracle suite since the beginning of my career. Initially on-premise, but now in the cloud.

I started out working with Informatica as well. That was a batch integration, such as for heavy-duty integrations or large files containing GBs of data. So I started with Informatica as well, but after that, I've only used Oracle products for online integrations and other integrations.

The initial setup is straightforward. It is not complex.

I would rate the implementation process a three and a half out of five because it is easy.

We are using Jenkins, and we have written some scripts to take integrations from one environment to another. We are logging everything, checking it into git, and then automating the processes in Jenkins. It starts with the IIR and then moves on to another environment. That doesn't take long. For example, if there are hundreds of integrations, Jenkins can deploy them in one or two hours. But, if you don't have Jenkins and you don't have automated scripts, it will be a lot of manual work. 

There are currently no one-click solutions. If we had a one-click migration feature, it would have been good. We're still using Jenkins script, it's not too difficult. It takes about one or two hours to deploy hundreds of integrations.

The deployment was done in-house. We are consultants and I am one of the consultants on my team.

We develop on our own. We raise an SR if there is a requirement. And if we have any questions about the product or suggestions for improvements, we do so as an Oracle SR.

I am not aware of the pricing.

Even if you have no prior experience with Oracle product integrations, it is easy to learn and use because it is mostly, drag and drop. If you are not familiar with coding or development or Java or JavaScript, you can easily learn Oracle Integration Cloud. This is mostly a configuration-based development, and you only need to use your mind and logic to implement it better in a performance-tuned way, but it's very simple. I would recommend that you use it. 

It makes integration so quick and simple.

I would rate Oracle Integration Cloud Service an eight out of ten. There is always room for improvement, but eight is definitely a good rating.

We are partners with Oracle.

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.

I am a Technology Architect. Our company is an IT service company. We develop integrated solutions for different clients.

Oracle Integration Cloud Service is part of enterprise-wide integrations. It integrates different applications from both inside and outside the organization.

The product improved our organization due to the available adapters, which are already provided with the product licenses. This helps us integrate with new cloud applications such as CRM, ERP, or any other cloud application. The proprietary adapters are already available, giving us the upper hand to integrate with different applications.

The most valuable feature of Oracle Integration Cloud Service is its ease of use. We do not depend on any tool to develop it. Everything is on the browser and is easy to integrate, even for someone who does not understand a lot about coding. 

Everything from development to deployment is seamless. It is a one-stop shop for all integration.

While most of the adapters are available through Oracle Integration Cloud Services, they do not have a lot of features. I would like to see some enrichment in this area and for the solution to go deeper into the applications and upgrade the adapters.

When comparing the solution to its on-premise solution which is also in the Oracle space, Oracle Suite, it is not as feature-rich as the on-premise solutions. It is still at a different level and will take some time to reach that level.

In future releases, Oracle could benefit from improvements to orchestration and level of monitoring. Some design aspects are not present in orchestration and there needs to be a more granular level of monitoring or more dashboards. 

I would like to see this product be more compatible and support the deployment on other clouds like AWS or Azure. 

I have been working with Oracle Integration Cloud for six years.

This is a very stable solution.

Oracle Integration Cloud Service is scalable. It's all configurations. We have approximately 500 people using this solution including IT developers, IT leads, IT designers, and IT architects.

Oracle takes care of the server maintenance and patching. Deployment is taken care of by the developers.

Support at Oracle is good, but not excellent. It takes time to resolve some issues.

In the past, we used Oracle Suite.

The initial setup of Oracle Integration Cloud Service is straightforward. Nothing needs to be done. Deployment takes minutes. I would rate the initial setup a five out of five.

We deploy in-house as we are using different DevOp tools for deployments. Oracle Integration Cloud Service supports all kinds of DevOps tools, so it is up to the client how they want to deploy the solution.

Our clients procure the licenses from Oracle and negotiate their own deals. The pricing varies. The solution is less expensive than other products.

This product only supports the deployment on Oracle's own cloud, it does not support AWS or Azure. This may deter other vendors who do not wish to deploy on Oracle Cloud.

Any organization that uses Oracle applications will find this solution very convenient to move into the proper cloud setup. If they require a cloud-to-cloud integration within a short timeframe, this would be an easy solution to use without issue. 

Overall, I would rate this solution an eight out of 10.

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.