Skip to main content
TrustRadius
TIBCO Integration (including BusinessWorks and Flogo)

TIBCO Integration (including BusinessWorks and Flogo)

Overview

What is TIBCO Integration (including BusinessWorks and Flogo)?

TIBCO Integration is used to connect diverse business solutions, data sources, and devices into a single, seamless system.

Read more
Recent Reviews

TIBCO user

8 out of 10
January 15, 2024
Incentivized
TIBCO BusinessWorks is being used by a department of the organization, in particular the integration team. TIBCO BusinessWorks addresses …
Continue reading

Trust My Review

7 out of 10
October 25, 2023
Incentivized
I use it as a middle layer to integrate two systems. we have various flows implemented. it addresses the problem we had with syncing data …
Continue reading

Reasons to use TCI

10 out of 10
July 25, 2023
Incentivized
TCI is used to integrate Business systems with SAP systems. Volume of transactions vary dynamically depending on time and day of business. …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 6 features
  • Pre-built connectors (121)
    7.5
    75%
  • Support for real-time and batch integration (118)
    7.0
    70%
  • Monitoring console (121)
    6.9
    69%
  • Connector modification (8)
    5.5
    55%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is TIBCO Integration (including BusinessWorks and Flogo)?

TIBCO Integration is used to connect diverse business solutions, data sources, and devices into a single, seamless system.

Entry-level set up fee?

  • Setup fee optional

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

Alternatives Pricing

What is SAP Integration Suite?

SAP Integration Suite is an integration platform-as-a-service (iPaaS) that helps quickly integrate on-premises and cloud-based processes, services, applications, events, and data. It is used to accelerate innovation, automate more processes, and realize a faster time to value.

What is Azure Logic Apps?

Microsoft offers the Azure Logic Apps as a cloud-based integration service, supporting data and application integration.

Return to navigation

Features

Cloud Data Integration

Cloud data integration software simplifies the task of integrating data from multiple different cloud applications

5.8
Avg 8.2
Return to navigation

Product Details

What is TIBCO Integration (including BusinessWorks and Flogo)?

TIBCO Integration is used to connect diverse business solutions, data sources, and devices into a single, seamless system. TIBCO accelerates connectivity initiatives with low and no-code experiences engineered to reduce development time and costs. Users can implement the best-fit style of integration to address any app, data, IoT, B2B and mobile/web integration use case. TIBCO Integration can connect to virtually any endpoint across the IT ecosystem with 200+ pre-built connectors for a wide variety of business suites, databases and legacy technologies.

TIBCO Integration (including BusinessWorks and Flogo) Features

Cloud Data Integration Features

  • Supported: Pre-built connectors
  • Supported: Support for real-time and batch integration
  • Supported: Monitoring console

Additional Features

  • Supported: No-code Business Process Automation
  • Supported: No-code Graphical Designer
  • Supported: Container and PaaS Support
  • Supported: Enterprise Scale

TIBCO Integration (including BusinessWorks and Flogo) Screenshots

Screenshot of TIBCO Control PlaneScreenshot of End-to-end ObservabilityScreenshot of TIBCO VSCode Development ExperienceScreenshot of Model-based Development ExperienceScreenshot of TIBCO Developer Hub

TIBCO Integration (including BusinessWorks and Flogo) Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Supported CountriesGlobal
Supported LanguagesEnglish

TIBCO Integration (including BusinessWorks and Flogo) Downloadables

Frequently Asked Questions

TIBCO Integration is used to connect diverse business solutions, data sources, and devices into a single, seamless system.

Boomi, Workato, and MuleSoft Anypoint Platform are common alternatives for TIBCO Integration (including BusinessWorks and Flogo).

Reviewers rate Pre-built connectors highest, with a score of 7.5.

The most common users of TIBCO Integration (including BusinessWorks and Flogo) are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(503)

Attribute Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Replicating data from cloud crm to internal database
  • data replication
  • data sync
  • API calls
  • JSON Normalization
I would recommend if you need a simple replication/sync from cloud data systems to local data storage. You should make sure that the connectors are supported, as the documentation is a bit generic. You also have to ensure that the settings are defined when making connections, as it's easily missed and not turnkey. In my opinion, feels like the UI is a bit unfriendly
Cloud Data Integration (3)
60%
6.0
Pre-built connectors
40%
4.0
Support for real-time and batch integration
70%
7.0
Monitoring console
70%
7.0
  • Operational agility
  • innovation and possibilities for reporting
No, but I feel the data synchronization opens alot of possibilities. If the integration options were a bit more robust, Tibco would have a much larger impact.
IT's ok, I think the UI is a bit unfriendly and the connections can take frustratingly long times to test and create. Sometimes it gets the job done, but alot of times you spend alot of time to do something, only to finally find out you can't do it. Various frustrating limitations that aren't clearly documented
I'd feel like it's not as user friendly as some other paid options and it could definitely improve. I also think that if they focused on improving the replication/synchonization function to create the niche market, it would be very beneficial.
  • TIBCO Cloud Integration
Used to replicate data from CRM to SQL Server
This is an older solution to replicate the data, and so far it works fine. We need the data replicated because we feel the CRM reports aren't robust enough and cannot generate calculations well
We deployed an agent On prem...relatively easy to deploy
For this particular use case. It was this one product I was interested in. There is a big impact for business for a relatively simple solution.
It's not realtime as the agent has to update in batches. the agent takes a good 30 secs to update and I think it's sufficient but I have seen some sync errors.
  • MS SQL Server
It was pretty easy
Compatibility. I did fine tibco's tech stack a bit lacking in terms of connectors and writeback
They didn't invest in their replication service so I didn't see any impact. They only invested in the ETL portion, and honestly that was a bit flawed
Deployment was smooth and easy
Migration was well done. No negative impact, and it was well commended. Support was pretty good and responsive too
No, they have not. Particularly if I wanted to use any API calls. I found the documentation and support of it lacking, and the interface is a frustrating experience as it is not super responsive. I abandoned my attempts to use it and went with something else
  • None
They reviewed the logs I gave them, took over as temp admins, and resolved my issue fairly quickly. The point is that the log reviews are quick and easy to share/review. Would be great if it were a bit more automated so I wouldn't have to send logs through the case and the agents could just see
I think I wrote that I wanted more robust documentation...it was a bit lacking to be honest.
  • None
Ease of use, and sync with dunamics CRM. Tibco has a competitive advantage with this connector, but I don't think it utilizes the connector or invests in it very well
Kingswaysoft, ease of use made it a better purchase
No, not at the moment until i see improvements in the API calls
No
  • Cloud Solutions
  • Ease of Use
Needed something up and running to respond to deadlines
Id be evaluating the same set of criteria
I don't use these tools
Sync data with MS SqL to use SSRS
manage user expectations to not expect realtime sync
I haven't used it, it's a clunky interface with slow response times
Just manage user expectations on sync times
I wouldn't change the criteria
Replication, and that's it. Data syncing to SQL Server
I don't have any
Ease of use. and the CRM Connector
  • data replication
8
Data entry and reporting
1
sQL Server
  • None
Business need
  • Implemented in-house
No
Change management was minimal
I was the only admin...and it's easy to use
  • None, was easy to imple ment
No, I use it as a backend solution. No visilbility to regular users
  • No Training
Yes
too limited, but more or less to clunky
No, not really
No - we have not done any customization to the interface
No - we have not done any custom code
Not at the moment
Money, not value to us
Fairly fast resolution of issues. some folks are knowledgeable
No
  • data replication
  • API Calls
  • ETL in FLogo
  • Connector testing connections
  • Iteriation in the ETL
  • Upserts in ETL
ITs a clunky interface, but the replication works fine
haven't seend outages at all
The ETL is clunky. and confusing. Flogo I think is what's it called
  • Dynamics cRM
  • Salesforce
  • ETL tools
Replication easy to use
Try the ETL and flogo app, but after 1 day if you can't get what you want...use something else
fine no complaints
fine, no complaints
Cost
No they are fine
No
  • none
No
No
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use TIBCO Cloud Integration to synchronize our ERP data with the CRM. It is used for six companies in Europe. As the ERP is the leading system, the source data always comes from Infor LN and Sage B7 ERP. This data is integrated into three different On-Premise Microsoft Dynamics CRMs. Most of the data is synchronized daily and partly every few minutes to keep the CRM data up to date.
  • Easy integration, even for non-programmers
  • It can connect to a lot of different systems/databases easily
  • The support is helpful and questions are answered fast and professionally. And if nothing helps, you get remote live-support
  • Good on-site training available
  • It is fast and (the CRM module) has the ability to cache query results
  • Export and import of mappings are very easy
  • Easy change of connections in (imported) mappings
  • The debugger is a pain. Sometimes it is hard to find an issue
  • It is not possible to split the integrations into steps. You need to copy/paste (and maintain) integration-steps that are used in multiple integrations
  • You cannot call a flow from another flow
I would recommend TIBCO Cloud Integration for most standard tasks, especially for integrating data to Microsoft Dynamics CRM. The integration is fast and stable. But in some cases, I would think about a data warehouse solutions, especially when data needs to be calculated for business reports and dashboards. The calculation-abilities of TIBCO Cloud Integration are limited in these cases.
Cloud Data Integration (3)
76.66666666666667%
7.7
Pre-built connectors
100%
10.0
Support for real-time and batch integration
80%
8.0
Monitoring console
50%
5.0
  • It saves a lot of time so it had a huge positive effect on our daily business.
  • Mappings are cancelled when too many records fail, sometimes this is an unwanted behaviour
  • Sometimes the whole integration is cancelled and nothing is in the execution history. You can only see a small message in a mouse-over hover tooltip
As we don't use other Tibco products I cannot tell you anything about this. But the Tibco cloud environment has been obviouslly enhanced so it should work well.
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.
Scribe has been the first big integration solution we used. After the test period we knew that it fits our needs. We thought about programming own solutions but in most cases that would be too much work.
We set up the integration and did not need to change it for more than a year now. It's stable and fast. I can focus on other work now. We could hire a new colleague who is not a programmer and he was able to work with Scribe within days.
Microsoft Visual Studio, Adobe Acrobat, Navisite Productivity and Collaboration (Microsoft Office 365 and MDM)
We did integrations for 4 different sub-companies. Mostly the data was pushed to the CRM system. As all were using MS Dynamics this was really easy with the connector. Sometimes you have small issues with non-standard systems.
The cloud integration works well with other standard cloud systems. We use it mostly with Microsoft Dynamics CRM. It's fast and reliable. Although it is expensive it reduced our costs because we need less people working on integrations
We migrated from the previous Scribe cloud solution. The migration was easy and the Tibco support helped to manage the migration within minutes. I've never seen something easier. But I am sure migrations from other tools will not go that smooth.
Yes the migration of the existing applications were very easy. The integration on the new environment worked the next day, so we had no impact. Nobody even noticed that anything changed in the background. That's how a migration (in the same ecosystem) should work. I'm really impressed.
I did not notice real big changes in the integration capabilities. Some things I would like to see (like calling flows from a flow, better debugging) are still missing. I also did not notice any speed increase. They often update some connectors but mostly this does not affect ours, because we only use 3 or 4 connectors.
  • Stability
  • Speed
I had problems moving a solution between organizations. I was called (they considered my local time) and solved it whithin minutes. The migration from Scribe to Tibco cloud was done within minutes also and without any real issues. The support is really superiour.
I made some feeback which was ignored by Tibco. Some small annoying things: The login screen shows only an email field and after entering it the password field appears. Because of this behaviour the saved password cannot be autofilled by the browser.
Another really annoying thing: The mappings open in a new browser window and this window is resized to the whole screen size - I have a 49 inch monitor.
I asked Tibco to change this. But it was ignored.
  • We used it straight forward for ERP and CRM
Fast and reliable integration to and between CRM systems in our company. That is what Tibco integration is exactly doing. We booked 2 days on-site training and were able to create the integrations. No weeks of learning needed, it just worked out of the box.
We did not consider other systems, Tibco convinced us at once.
We will use it to migration a on-premise CRM to a cloud CRM. We will not use the Microsoft tools because this is the chance to clean the data. So we will set up a really huge integration and copy only the relevant data.
No
  • Product Features
  • Product Usability
The product features
The most important factor was the flexibility of Tibco Scribe. We needed to integrate data from a lot of different sources for example MSSQL, CSV files, and after splitting CRM (each company now has its own) from other CRMs. We are also able to work with different agents, which speeds up the integration a lot. You can install agents on different VMs and run jobs simulanously.
Connecting to several web-APIs becomes more and more important. Especially if you need data from self-written software in other tools. So the possibilities connecting to any APIs would be a bigger factor than some years ago. But Tibco Scribe is able to connect to every service we need, so we would have bought it (again).
Tibco Scibe itself runs in the cloud, so the deployment is very easy. We installed seven connector agents on several machines (one for each company which needs integration). The jobs can be run simultaneously overnight. We installed an additional cloud agent for integration data from some online services (Microsoft Azure).
Some self-written tools generate data which needs to be available in the CRM system. These data is usually delivered by an XML- or JSON-API. We do not integrate data from other popular tools. But it is planned to integrate data from a quality-testing-software where barcodes need to be tracked. So mostly other data comes from self-written tools.
To speed up initial integration you can install 10 agents and run 10 solutions simultaneously.
My advice is to book an onsite training first.
I asked several questions and they all were answered quickly and always helped solving my issues.
To have a bit of configuration I added some variables in a configuration lookup table. There I can control things like "read data of the last X days"...
We did the correct choice. Nothing to change here.
1. Debugging: This is really helpful finding errors.
2. Multiple agents: My solutions can connect to different agents on different on-premise systems. This speeds up the integration a lot
3. Lots of connectors: These are really helpful with most of the common data sources
As I first had an onsite training I knew the best practice. This is what I recommend everyone who starts with Scribe.
The different connectors are amazing. They connect to all data sources we have in our companies. The mappings are absolutely easy to use and the community (and staff) is helpful and extensive.
  • Dynamics CRM
  • Infor ERP
5
Software developers, IT managers and consultants
3
Software developers: These are doing the debugging and tricky things
IT managers: Doing the planning
Consultants: Sometimes help when there is no time
  • Maybe adding triggered integrations
It's stable and you can quickly setup new mappings with ease
  • Implemented in-house
  • Third-party professional services
aXon GmbH Paderborn
Change management was minimal
  • Setting up the correct permissions for the SQL database user
Buy a training and ask the community. This will both help a lot
  • In-person training
  • Self-taught
We have had an 2-day on-site basic training before we started building our integrations. After that we were able to build the first integrations very fast. I would strongly recommend a personal training to get a basic understanding how it works and what are common mistakes.
The onsite training has been very helpful to learn the best practices and start with clean mappings .
It is possible, but to get started fast I recommend a training. The trainer will answer specific questions directly which you would otherwise search in the internet spending a lot of time for it.
We almost did not configure anything. It works out of the box!
Install it, run it
No - there is no facility to customize the interface
No - we have not done any custom code
We did not customize anything.
Not Available
They helped a lot with moving solutions between organizations. Got a call and it was done quickly.
No
  • The mappings
  • There are no variables in the mappings
Most of the features work out of the box and stable. The mappings are done by drag'n'drop
No
In the last weeks they had several issues with the login and we could not add users. But the integration did not stop, only the frontend has not been available.
It depends on the mappings, mostly it does about 2-3 records a second. But this is a limitation of the CRM API. Lets see what happens when we move to the cloud.
  • Dynamics CRM
  • Infor ERP
As there is a CRM connector this was absolutely easy. The ERP integration is done by direct reading of the SQL database.
  • Some self-written tools
Yes, this will be done on SQL server
---
All done by drag and drop
Get a training before you begin
We already knew what we need. So no advice needed.
We had no complains
nothing
---
Yes
We did not register any downtime
  • not sure
No
No
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use Tibco Cloud Integration in syncing our data to Salesforce.
  • Easily maps data.
  • Provides the ability to use logic with data.
  • Quick response when syncing data.
  • Could provide simpler connector requirements.
  • We've had difficulty troubleshooting issues without involving support.
  • Provide templates to follow as a guide.
Well suited with data housed in a data store, but would probably not be as well suited if you're wanting to use real-time data from multiple different sources, from what we know of.
Cloud Data Integration (3)
53.33333333333333%
5.3
Pre-built connectors
60%
6.0
Support for real-time and batch integration
50%
5.0
Monitoring console
50%
5.0
  • Provides the ability to gather data from multiple sources to map into a CRM solution using TIBCO.
  • Allows our organization to become more data-driven.
  • Provides the ability for the staff to see a snapshot of customer data from multiple systems in our CRM solution.
  • Mapping data from data store to Salesforce CRM
  • Ability to retrieve data from multiple sources to import into Salesforce CRM
  • Data is able to be imported on a schedule
1
IT
We have not implemented any other integration solution other than TIBCO. TIBCO provides what we needed to map data from our multiple sources into our CRM solution for a reasonable price and usability.
  • Product Usability
We wanted to verify the usability of the product to ensure we could successfully upload our data to Salesforce with limited interaction on our part and without any need for continued attention by us once we set up the integration.
  • In-person training
My only training was from another colleague who learned from a TIBCO/Scribe technician using a remote training session.
Using TIBCO has made the integration of our data into Salesforce very streamlined. It has saved us time and allows the data to be uploaded into Salesforce efficiently.
Can add some logic to the solutions in TIBCO so the data is accurate. Previewing the data to confirm the logic has been an important lesson.
We noticed faster syncing which had a reduction in operating costs and improved operations and customer satisfaction.
We did not encounter any issues with the cloud based adoption. We migrated from the on-premise tool to the cloud-based product provided by TIBCO.
We used our existing applications built using TIBCO. This allowed us to seamlessly move to TIBCO's cloud without hassle or downtime.
Our organization's needs continue to be met by TIBCO. Even though our needs haven't significantly changed since we first adopted TIBCO, we feel that TIBCO's solution would successfully meet what we required.
  • NA
The few times I have contacted TIBCO Scribe for support, the technicians have always been helpful and quick to respond. I have have never had issues so far where the support was not exceptional.
Yes, the feedback has been taken into consideration. The feedback given was receptive and seems to have been relayed to the appropriate areas.
  • Integration with Salesforce CRM
  • Add logic to field mappings
Import data from multiple sources into Salesforce. TIBCO was able to meet that need for us.
We did not look at others since TIBCO was a recommendation.
No, we will not expand our use of TIBCO in the future.
No
Did it meet our needs and was it within budget. Once we determined TIBCO was within our budget and could successfully meet our needs, we implemented TIBCO.
I would wonder if TIBCO could provide real time API calls from multiple data sources without much complex configuration?
We use TIBCO's on-premises agent installed on a server for use with syncing our data to Salesforce. Solutions configuration and syncing is performed using TIBCO online/Scribe.
We only use TIBCO/Scribe to sync data to Salesforce. We don't use any other tools integrated with TIBCO.
We use TIBCO to sync data into Salesforce to see what services our customers use which allows us to promote other services to them. We use logic when syncing in the data so the data has relevance.
Work with the company for a tutorial and help out with the initial setup. We have both a Test and Prod environment. TIBCO assisted us with setting up the Test environment and we created the Prod environment configuration ourselves.
I haven't used the TIBCO Community as of yet.
Using the scheduler to sync the data is a nice feature so there isn't a need to manually sync the data.
Research if there is a utility that could pull our data real time without the need for us to upload the data into a data store on a periodic basis to then integrate into Salesforce.
Automatic scheduling.
Entering logic and viewing results to verify data.
Fast response from support when needing assistance.

Automatic scheduling.
I didn't implement the auto scheduling right away and wish I would have.
I have not used any other cloud integrations so I cannot answer this question.
1
The person that uses TIBCO Scribe has an IT background.
  • Potentially map from various data sources in various locations to Salesforce rather than just one data store
  • Use in creation of data lake which encompasses all our data from various systems into one location
TIBCO Scribe works well for us. It has a fast response time and meets our needs to map our data to Salesforce.
  • Implemented in-house
No
  • Understanding how to implement logic into the data mapping
  • Understanding how to map our data from multiple sources to what we wanted in Salesforce using Scribe
We should have requested documentation from the vendor when we implemented TIBCO Scribe so all of us understood the logic of the data mapping.
The training was done remotely rather than in person.
I would recommend someone at TIBCO to provide training unless you are familiar with data integration like this.
I would like more flexibility in the scheduling to include holidays and weekends. We sync data on the 10th of the month and there are issues when it falls on a holiday or over a weekend then the syncing process has to be manually done during the next business day to resolve any issues.
Not that comes to mind.
Some - we have done small customizations to the interface
It required some knowledge to customize the interface.
Some - we have added small pieces of custom code
We added some logic to the code in order to map the fields correctly.
No.
Yes
We do pay for premium support as we want to make sure our needs are met in a timely manner.
TIBCO Scribe support is fast to respond and courteous. They are knowledgeable, helpful, and pleasing to work with.
No
  • Figuring out which fields in the data store to map correctly
  • Including logic with the data mapping
  • Having to dig around for why syncing may have failed (was it an expired password, a new record that was added to the data but not yet mapped, etc)
It is the first and only cloud integration system we have used with Salesforce so we cannot compare to other solutions that are out there. However, TIBCO Scribe does meet our needs.
We use TIBCO only for syncing data into one Salesforce solution. We have not implemented TIBCO for any other solutions.
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.
Response time is very quick and we have not seen any issues with slowness re. other systems or software.
  • Salesforce CRM
We had never worked with an integration utility prior to using TIBCO Scribe so it did require assistance from the vendor but once we were given guidance on the process, we were able to successfully integrate our data using Scribe without very many issues.
  • No
NA
  • File import/export
The interface is fairly easy to understand and use. We were provided guidance from TIBCO Scribe initially and were then able to continue the setup of the integration on our own without issue.
Contact TIBCO with your questions and any assistance. They have been very helpful.
I was not involved with the sales process.
TIBCO has been very responsive when I have needed to work with them.
I was not involved with any negotiations.
Ask questions and ask for assistance if needed to help guide you through the process.
No
We have upgraded the agent only which is a streamlined process. No other upgrades have been implemented.
  • Unsure
No
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Tibco Scribe to bring the data from our Dynamics 365 CRM Cloud environment to our on-premise data warehouse. We use this data in our BI environment, where our business users use it to create dashboards and reports. The sync is done on a daily basis using a manually selected set of Dynamics 365 CRM entities.
  • The setup of both the sending as the receiving side is easy, you don't really need expert skills to set up the "technical" part.
  • We don't need a complicated ETL tool to extract the data from the Cloud environment.
  • The overall management of what needs to be synchronized is straight forward.
  • Thanks to the specific SCRIBE fields in the receiving database we have a track of deleted records (for which we don't have anything in the CRM database).
  • The synchronization is not fast and seems to do some unnecessary work.
  • Selecting the entities to synchronize is quite tedious, you need to scroll through quite a big list (especially when you have a lot of custom entities) a filter would be welcome.
  • You need to manually update the metadata of the sending connection to see newly created entities, it would be nice if you could schedule those tasks too.
  • We already had quite some situations where MS changed things in the data model of CRM that caused issues in the sync tasks.
It is a great tool to quickly set up synchronization between an on-premise data warehouse and a cloud solution as MS Dynamics 365 Customer engagement (CRM), which was our specific use case. Most of the issues we ran into could be worked around without any special technical skills.

When you need more specific control (field level) of what needs to be synchronized, you need to look to a more specialized tool to do the data integration.
Cloud Data Integration (3)
70%
7.0
Pre-built connectors
80%
8.0
Support for real-time and batch integration
50%
5.0
Monitoring console
80%
8.0
  • We didn't need to invest resources in setting up something similar in a more complicated ETL tool.
  • We don't need to worry about keeping this environment up to date, very little maintenance from our end.
  • Sync the data of our Dynamics 365 CRM data to on premise database for reporting
  • batch migrate data from legacy systems after go-live
1
I'm the only user and as the IT application engineer, I'm responsible to keep our production applications up and running. And Scribe is one of the applications in our BI environment. Together with the SQL databases and Qlik Sense, which we use for reporting and dashboarding of our KPI's.
Both for our management and our Sales team.
Scribe was proposed by our partner assisting us in the migration from Siebel CRM to Microsoft Dynamics 365 CRM, to do the database sync of the information stored in our Cloud CRM system. Talend we use for our internal ETL and API development, the tools are complementary.
They both have their strengths and weaknesses.
  • Existing Relationship with the Vendor
We we're unfamiliar with software to integerate cloud environments with our on premise environments, so we trusted our migration partner to help us with finding the best solution for the case at hand. They had experience with Tibco Scribe so we went for their proposal to use this solution to get the Dynamics 365 data in our on premise database for reporting.
  • migrate Salesforce data into a live production MS dynamics 365 environment
  • Self-taught
As mentioned earlier, setting up a SCRIBE environment is extremely easy, you don't need any technical skills to setup the "technical" part of the setup. You do need some knowledge of the source environment to determine which tables or enities you need to select for the integration purpose you have in mind. But is not related to the Tibco tool.
We started using Tibco Scribe when we moved to Microsoft Dynamcis 365 CRM, we previously had no need for such a tool. But we found it extremely easy to use and setup synchronization jobs. It was a no-brainer to create and maintain the jobs and schedules to keep our on premise database in sync the our CRM production environment.
My current experience with the support for Tibco Cloud Integration has been very positive. I always worked with skilled support engineers who knew the product well and most of the time understood my problem from the start. They also needed little time to resolve my cases and until now I have not needed to escalate tickets to second level support.
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.
Our reporting is dependent on the correct synchronization of the Microsoft Dynamics 365 data to our on premise database.
We learned that sometimes Tibco Scribe is not up to date when it comes to changes in the REST api or changes Microsoft implements on the database, which caused the synchronization to fail. And it is not always easy to figure out what is the exact cause of the failure.
But Tibco Support was of great help in those cases.
No
The integrator we worked with proposed this tool to fulfill a need we had on getting the data from our Dynamics 365 CRM environment on premisse for our reporting needs.What I like the most about the product is that it mitigates the need for us to develop the logic to do updates or inserts of data. We have an ETL tool in house, but it would cost us quite some time and money to develop and maintain the stuff that Tibco's product does out of the box.
The market and the needs change over time, we might focus a little more on user friendlyness of the product. Some things take quite some time specially if one wants to make a selection of which fields someone wants to synchronize from a very large table for instance.
And the relationship the supplier has with the products it connects to, will also have a bigger role. This last aspect to prevent there arise problems with synchs because of changes on the source application (in our case MS Dynamics 365 CRM)
We use the cloud solution of Tibco scribe to synchronize our Microsoft Dynamics 365 environment to our on premise Microsoft SQL server for business reporting purposes. The only on premise component we had to install was the agent on the Microsoft SQL server machine that is the destination of the synchronization jobs we created. It's zero effort once it is installed, it updates itself when a new version is released.
We don't have any further integrations with Tibco Cloud integration (Scribe). We purely use it to have a local copy of ourt Dynamics Customer Relationship Management tool which also runs in the Cloud. The copy of the data is stored in our Microsoft SQL server and consumed using our reporting tool (Qlik Sense).
We recently used it, with help of our current Microsoft Dynamics 365 partner, to migrate data from the Salesforce environment from one of our subsidiaries. Our partner took care of the complete setup and execution of the job. But the end result was what we expected and the leadtime from analyzing to final migration was short (a little more than a month).
Tibco Scribe is a very user-friendly solution to integrate and replicate your cloud data. Both for cloud-to-cloud as for cloud-to-on premise integrations or replication. It's extremely easy to setup and configure, and it can be managed by users with very little IT skills.
But also be prepared to accept that it not always is up to date when it comes to API or database model of the source application and that it can take some time to resolve that kind of issues.
I have not used the community that often to find resolutions for my problem, but they often pointed me in the right direction to formulate the problem in the right wording to pass on a ticket to Tibco Support.
So to be honest I've got very little experience with the Tibco Community, on the other hand we haven't had that much issues with the solution either.
As probably mentioned earlier, we have had some issues with the API not being up-to-date and causing our synchronization of our Microsoft Dynamics 365 CRM to fail. Which in turn caused our management dashboards and KPI's to not refresh with the most recent data.
This is one aspect users of the Tibco Cloud integration solution need to keep in the back of their head.
We started using Tibco Cloud Integration (more specifically Scribe) on the proposal of our partner that assisted us in the migration from Siebel CRM to Microsoft Dynamics 365 CRM at the time. And since then we also did the exercise to map our application landscape and enterprise architecture. So we probably would check if we can consolidate on one integration solution to do the kind of work that Tibco Scribe does, which in the end could be to stick to Scribe or move to another solution we might already have.
We only use it to replicate our Microsoft Dynamics 365 CRM data to our on premise Microsoft SQL server database. We currently don't have other use cases for the tool. And I don't think this will change in the near future, for internal replication and integration jobs we have another tool that we use extensively.
None
No real opninion
1
I'm the only user and as the IT application engineer, I'm responsible to keep our production applications up and running. And Scribe is one of the applications in our BI environment. Together with the SQL databases and Qlik Sense, which we use for reporting and dashboarding of our KPI's.
Both for our management and our Sales team.
Even though I have an IT background, I don't find it a pre-requisite to use Scribe.
  • other replications
Since everything is running as it should be, we currently don't have plans to change the application used to do the kind of work we use Tibco Cloud integration for the moment. It does what it needs to do in a way that currently asks very little maintenance and management from our end. So you could say the TCO of this solution is at an acceptable level.
  • Implemented in-house
No
Change management was minimal
None, we had no prior use case. So this was the initial setup for what we needed to do. And also for us this a backend solution it is hidden from the end users. They only want to see the most recent data in their dashboards and KPI's and how the data is fetched from the source system is not their concern.
  • Setting up the list of entities to sync
Implementation is a no-brainer, it's just installing the agent on our Microsoft SQL server environment. Linking it to the Tibco Cloud Integration platform and then setting up the connections to the source and destination systems. Once those steps have been done, it's just setting up the jobs using the connections and selecting the data we needed to be replicated.
We have not needed any training. The User interface is self explanatory and makes training unnecessary.
Mainly because there's a small number of steps needed to create a replication job in Tibco Cloud Integration (Scribe). Manually selecting the entities to be replicated from our Microsoft Dynamics 365 CRM was the most labour intensive part.
We have not needed any training. The User interface is self explanatory and makes training unnecessary.
Mainly because there's a small number of steps needed to create a replication job in Tibco Cloud Integration (Scribe). Manually selecting the entities to be replicated from our Microsoft Dynamics 365 CRM was the most labour intensive part.
As mentioned already a few times in the previous sections. The user interface is self explanatory and very easy to use to setup the environment, and prepare for first use. The configurability is just right for this type of product and absolutely not too limited or too complex to prepare for use.
No, no specific recommendations. Just set up the basic components like connections to your source and destination systems and create a job. Then select the entities you need to replicate or integrate. Save the job and schedule it to do it's thing. Nothing more, nothing less.
It really is that easy to setup and get started.
No - we have not done any customization to the interface
No - we have not done any custom code
No, we did no customization
No
My most recent ticket was one such situation. It initially was picked up by a first level support engineer but because of holidays it was put on hold. Then "out of the blue" a French second level support engineer took over the case and we had a screen sharing session to have look to our on premise agent installation. There he immediately a possible cause for the issue we had, and he was spot on.
He was an extremely friendly person who really helped me out at that time and resolved my case in a very short time. I was very pleased with the way this case was handled.
  • Basic setup of jobs
  • selecting the MS Dynamics entities we needed synhronization for to on-prem
  • Debugging when something goes wrong
We have not yet needed to scale the solution for which we use Tibco Cloud Integration. As mentioned earlier, we only use it to replicate our cloud hosted Microsoft Dynamics 365 CRM environment. We don't have any plans to use the tool more extensively in the future.
In the three years we use Tibco Cloud Integration platform Scribe, we have not yet experienced any outages. The only issues we had were with Microsoft changing the Microsoft Dynamics 365 REST API which caused our replication jobs to fail.But for the time being we have not yet had any real downtime impacting our scheduled replication jobs.
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.
  • Microsoft Dynamics 365 CRM
It was a very simple data replication we needed for internal reporting on the Microsoft Dynamics 365 CRM data.
  • none
I have no idea
  • ETL tools
The User interface is self explanatory and makes training unnecessary.
Mainly because there's a small number of steps needed to create a replication job in Tibco Cloud Integration (Scribe). Manually selecting the entities to be replicated from our Microsoft Dynamics 365 CRM was the most labour intensive part.
We only used it for replication
Our partner that assisted us in our migration to Microsoft Dynamics 365 CRM took care of the purchase process. We were not involved in it so I can not rate this part.
Our renewals are done by ourselves (more specific our purchasing department) and so far we have not had any issues related to that either. Transferring the administration to us after we stopped the collaboration with the initial partner was also very easy and went without any hassle.
We did not negotiate with Tibco directly
No, since we did not negotiate with Tibco directly
  • none
  • that everything keeps working
No
No
October 27, 2020

Scribe Online: Use it

Score 7 out of 10
Vetted Review
Verified User
Incentivized
We offer Scribe to multiple customers as a Microsoft partner. Our most common uses are one-off migrations from legacy systems to dynamics 365 or ongoing integrations between dynamics 365 and another system.
  • Point and click design for integration maps
  • Simple scheduling of integrations
  • Useful error reporting
  • Since moving to Scribe online: no publisher
  • Online editor can be sluggish: lagging
  • Debug should mimic a commit not actually commit
  • Improve having live and testing integrations in one tenancy
Dynamics on-prem to online upgrade. Dynamics to NAV. Dynamics to SQL.
Cloud Data Integration (3)
56.66666666666667%
5.7
Pre-built connectors
70%
7.0
Support for real-time and batch integration
40%
4.0
Monitoring console
60%
6.0
  • Using Scribe for integrations, especially with NAV has helped us win business against competitors as we can build quickly and have full control over integration logic compared to the nav adapter, for example.
  • It is a known system and our customers respect that.
Flow has far more connectors but is more clunky to use. Although I see that this could rival Scribe in the future as people look to stay in the MS stack and avoid additional license fees.
  • Online training
  • In-person training
  • Self-taught
I initially self taught using an earlier iteration of Scribe online. Subsequently i have had in person training.
I think the online materials are sufficient for you to pick up the basics and work from there
The ability to copy and paste block between integrations has saved time.
The revisions functionality has also made rolling back really good.
THe support is really good, would be useful if it was single sign on between the platform and the support.

The cases are updated in a timely fashion and prompts when an update is needed.
The UI has improved dramatically over the years of using scribe.

the drag and drop with the connectors means building integrations can be super fast.

THe debug tools is also rally useful
No
Price and reputation.

Needs to be competitive for our customers when going up against other products.
Partner discount/kickback always helps.
Most of our integrations are with Microsoft Dynamics, some of our customers have legacy on prem systems having htat flexibility with the connectors is great.
Dynamics 365
SQL
NAV
Business Central
Recently used it so that field engineers can submit transfer orders or stock requests from their mobile device, that creates a record in D365. We then transform that and ass it into Nav to perform a transfer order and ship goods to them. Pretty cool
Dive in, watch some of the videos and training materials but you learn from doing.

Know your scenarios, know your systems data structure and you will pick it up
What a great resource, likeminded people trying to solve similar problems.
Use the community and get on the partner calls.
No
Drag and drop
Copy and pate
Native connectors
Copy and paste
The user interface really sets it apart from its competitors.
And its reliability
3
We have a dedicated Dynamics support team - these guys are capable of supporting TIBCO scribe as well. Most of our customer integrations are from bespoke in-house systems, or Dynamics NAV/Business Central to Dynamics 365
  • Templates for BC to Dynamics 365
  • Dynamics on prem to Dynamics online
  • Bespoke to Dynamics 365
If you need control over your integrations between a finance application and D365 then TIBCO scribe gives you that capability.

We build in specific error handling and write those errors back into the application so that the user can self serve with issues.
  • Implemented in-house
No
Change management was a major issue with the implementation
Moving away from historic systems
  • Old systems
  • Data quality
  • Connectors
successful implementation
N/A not needed
really good resources
Yeah it is really intuitive
Meets our needs
Use the documentation provided by TIBCO
No - we have not done any customization to the interface
No - we have not done any custom code
N/A
No
Immediate response and connection to env.
  • Copy Nad paste
  • revisions
  • Export
  • Import
No
Scalable dealing with arge volume of data
always on
No performance issues with updated interface
  • Dynamics 365
  • SQL
  • Txt
  • xERO
  • File import/export
Extremely easy with connectors and drag and drop
Use it you won't be disappointed
Really knowledgeable and good guys, always willing to help
Plain sailing
Absolutely
NOt really, really good engagement
Yes
Very little downtime - migration from US to EU datacenter
  • Solutions
  • Apps
  • Flows
  • Not sure what is on the road map
No
No
Return to navigation