The Oracle Integration Cloud Service is an iPaaS providing prebuilt integration flows between applications, including other Oracle products. The Integration Cloud Service is scaled for enterprises, with prebuilt codeless adapters for on-premises and SaaS systems and low-code automation capabilities.
N/A
WSO2 API Manager
Score 9.4 out of 10
Enterprise companies (1,001+ employees)
WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…
$0
per month
Pricing
Oracle Integration (OIC)
WSO2 API Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Oracle Integration (OIC)
WSO2 API Manager
Free Trial
Yes
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Oracle Integration (OIC)
WSO2 API Manager
Features
Oracle Integration (OIC)
WSO2 API Manager
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Oracle Integration (OIC)
7.4
22 Ratings
8% below category average
WSO2 API Manager
-
Ratings
Pre-built connectors
7.821 Ratings
00 Ratings
Connector modification
7.821 Ratings
00 Ratings
Support for real-time and batch integration
5.822 Ratings
00 Ratings
Data quality services
6.120 Ratings
00 Ratings
Data security features
8.021 Ratings
00 Ratings
Monitoring console
9.222 Ratings
00 Ratings
API Management
Comparison of API Management features of Product A and Product B
Oracle Process Cloud is suited for medium-sized companies and up who want to create applications that can automate tasks without the need of recruiting more software developers. With a couple hours of training, any member of the organization's business team will be well-equipped with all of the knowledge that is needed to use Oracle Process Cloud effectively. If your IT team is large and able to take upon the task of making the given application, then something like Oracle BPM is a better solution.
It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
New enhanced activities that are targeted to reduce the integration pain. For example, file stage activity reduces the pain of chunking the input file while sending and mapping the data to the target application. Stage activity takes care of it automatically for the customer. Similarly, recommendation on the mapper is a huge plus for people looking for common integration.
There are around 50 adapters available including dedicated out of the box application adapters and generic technologies adapters on OICS. The best part of these application adapters is that they are designed considering LOB users. Most of the time integration implementor does not require, application knowledge to perform the integration. OICS has some of Oracle Cloud applications adapters which make integration much easier may not be available in other integration platforms.
Inbuilt diagnostic dashboard and error hospital makes this product lucrative. OICS also comes with integrated Process Cloud and Visual Builder at the same cost. the customer can have seamless integration with Apiary and SSI on demand.
Currently, it is not retaining the logs for more than 3 days, which it needs to address.
We also need some functionality inside the interface to re-push the same transaction again so that it will be helpful while testing and fixing the issue.
Also, some log errors are not giving the correct details. Oracle needs to rectify those.
The nearest thing I have used to OIC is UiPath, as it is often used as a tool to integrate software together. However, it is much more suited to legacy software which have little to no API endpoints. If the infrastructure already exists I understand why people use RPA for integration, however for when API's are easily accessible and you're using Oracle tools, OIC is better.
Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
The modern and advanced analytical abilities in Oracle Process Cloud are also a missing element that should be catered to.
This tool is used greatly for IT departments at a lower level with some very basic and limited access for general employees only.
Oracle Process Cloud has many advantages like it offers some very great and scalable solutions.
I find Oracle Process Cloud pretty straightforward and easy as compared to the different options available. Lastly, I think that as it is just one platform, managing the Oracle Process Cloud is pretty easy too.
We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.