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
TIBCO Cloud Integration
Score 8.1 out of 10
N/A
TIBCO Cloud™ Integration is an enterprise iPaaS platform. It offers a drag-and-drop and API-
led design approach for user-friendliness.
$400
number of iPaaS apps
Pricing
Oracle Integration (OIC)
TIBCO Cloud Integration (including BusinessWorks and Scribe)
Editions & Modules
No answers on this topic
Basic
Starting from $400 per month, billed annually
number of iPaaS apps
Premium
Starting from $1,500 per month, billed annually
number of iPaaS apps; includes additional functionality
Hybrid
contact us for pricing
number of iPaaS apps; includes additional functionality and hybrid deployment options
Offerings
Pricing Offerings
Oracle Integration (OIC)
TIBCO Cloud Integration
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
Optional
Additional Details
Try for free: https://cloud.oracle.com/tryit
Pay-as-you-go/hour pricing https://cloud.oracle.com/en_US/OIC/pricing
Oracle's solutions play well with their own software and other systems. Their cloud products are familiar if you have used one and the UI is easy to use. Uptime and reliability are also always a factor.
TIBCO Cloud Integration (including BusinessWorks and Scribe)
Likelihood to Recommend
Oracle
For all type of integration except those with a huge volume. It can deal with 20MB of transactions and processing of 1GB file when a file is being read using file or FTP adapters. It cannot be used for EDI as this support is not there. OICS is a perfect fit for other integration and is best when a customer has Oracle applications in the landscape. It is even greater if you have a requirement to create a custom form and make use of Process Cloud. All of these work very well together seamlessly. API needs can be handled by APIary.
Used TIBCO for migration of our data for our learning management system.TIBCO, succesful Content ,data migration(courses, classes, registrations, transcripts etc.) ,User migration(Internal users and Partner migration)and Report migrationIntegrations with different applications Workday,Single Sign-On,CertTracker,Okta,Partner contact sync and Questionmark is succesful.LOD: Learn on demand is a third party vendor application where all Virtual classes are delivered by the vendor application. Learning management system sends the class and registration events to learn on demand via real time web service call through TIBCO
Auto-association of Oracle applications prepopulates the application connector select box and preconfigures Oracle Integration (OIC) using secure credential access for faster integration.
Various other system connectors are available to use readily.
User-intuitive experience--Connectors, integrators, and dashboard can be seen on one page.
Scribe can dependably map or sync data between systems. When you have different systems being used by many departments, this is the tool to keep the data in-sync!
API's are widely used by many applications and companies. Tibco Cloud Integration allows companies to integrate data from an older ERP system with a newer system using an API.
Tibco provides the flexibility for business users, developers and anyone in-between to understand where data is moving within their organization.
One example of flexibility of the solution is easily manipulating data on the fly.
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.
Missing functionality: We like to run all the files available in the FTP when clicking the run button. Right now, we have to click the run button several times (or have multiple solutions) in order to run files from our FTP site one at a time.
Generating column fields every time a file changes from the source in the FTP is very tedious. Working in integrations makes me have to go back and forth a lot of the time, and doing this is incredibly annoying.
The security is horrendous. We installed an on-premise agent on the customer side, but we don't want them even touching the ETL tool at all. The only knowledge we are fine with knowing and being able to see is that they installed the agent, not the solutions themselves.
Our company's connector would have to point to the dataset name rather than dataset ID. It was very frustrating because we change the dataset name a lot, and then we'd have to repoint it.
It's very difficult to monitor the different integrations that go on because there isn't a consolidated dashboard.
We are deeply entrenched in using Tibco Scribe capabilities, and we are only expanding our usage. It would be one thing if we used it only for a one-time data load, but we have several Scribe maps running constantly, keeping business-critical data up to date. And the ease of use for the occasional, mass data update or upload is simply icing on the cake. I'm a big Microsoft fan, so there is potential down the road to convert our Scribe data integrations to Microsoft Flow (or Power Automate as it is now called). But for now, the functionality just isn't there with Flow (Power Automate), plus the work involved to change all our current integrations would be a large undertaking. So for now and the foreseeable future, Scribe will remain our data integration tool of choice.
As mentioned in the previous sections, setup and maintenance is extremely easy. We don't have many issues for which we need support and there is no need for deep technical skills to use Tibco Cloud Integration platform. The solution provides everything we need for our specific use case, being the replication of our Microsoft Dynamics 365 CRM data to our on premise database for reporting.
We have not had any issues with TIBCO not being available when needed. I have only had to contact support less than 5 times in about 5 year time frame due to syncing issues or a problem with the agent. Support is very quick to respond as well as very helpful.
TIBCO Cloud Integration (including BusinessWorks and Scribe)'s performance of the user interface are not to be complained about. The user interface is swift and is a pleasant user experience. The replication jobs take some time to finish but that is because the number of records to be updated/created on a daily basis is quite big. I did split up the jobs between highrunners (entities with a lot of changes) I update on a daily basis and quite stable entities that I update weekly. That solved my issue of a way to long replication.
For creating new process, you have lots of palettes to do every develop you need. For created process it is easy to understand even if you have ever seen before it. You can analyze your process in all their detail. User Experience is positive for beginner and expertise people. Just debug mode is still raw, but better in TIBCO BusinessWorks 6.x than TIBCO BusinessWorks 5.x .
Before using TIBCO Businessworks, I participated an official training with a specialized instructor. In this training, I learned what I needed to know to build some applications or web services and how to manage its. It was been very important to me. I understood many technical stuff to familiarize with this powerful platform. I can advice TIBCO Educational Services.
If we don't design the process correctly, it can do lot of damage (like deleting files or data etc.,) and might assume product issue rather than a design flaw. So it is always recommended to do thorough unit testing , QA and a design review even for a small process to avoid major problems.
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.
We have used Microsoft SQL Server Integration Services previously for various projects including data migration and integration, although the product is free and has very high flexibility it doesnt have the usability and connectors of scribe that allow you to quickly create basic integrations and have normal users manage and review these setups
We could easily add multiple agents and new systems. This had no impact on the performance. We had some issues because flows cannot be splitted and called by each other. So you have lots of flows which are the same. It would be great if this was improved. Also transferring values via variables between flows seems to be impossible. You can only use global lists with dictionaries.
Created a solution for unique business integration with minimal processing times
Saves my team about 7 hours per week because of how it communicates with all the information. Because it communicates faster, and because there's a lot of information to communicate with, another solution might not work.
The data migration has been extremely slow. Things that should have taken a short amount of time have gone way past where any of us though.
Job monitoring has been more resource intensive and time consuming that planned for.
Researching and searching for things is time consuming.
There is no way to easily organize solutions. So there are hundreds of solutions in the list with no easy way to put them in folders or something like that. The only thing you can do is name them specifically so that you can filter them. But filtering is not very good in Scribe.
The concept of Scribe is good. I like the graphical flow builds in the maps. It just doesn't work very well yet. maybe as they improve it.
