Mule ESB vs. TIBCO Integration (including BusinessWorks and Flogo)

If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.

Incentivized

In BusinessWorks it is quite easy to develop applications and monitor where as it is not similar with Scribe. The data which successfully processed in Scribe is quite difficult to view. I think the Scribe console tool should have better view for the data it has processed.At times we founds some of our sales orders are missing which are unable to update/insert in the DB, after investigation found the issue is in Scribe tool. A case has been raised 02129657 for the same and as per the guidelines from the Scribe support engineer we did changes in the shutdown interval to zero. ''update SCRIBEINTERNAL.SCRIBE.KSYNC
set keyvalue= 0 where KEYNAME = 'SETTINGS.SHUTDOWNINTERVAL''. Later this change we started getting alert emails like ''Fatal error 325 occurred: Message processor shutting down
- defined maximum memory usage (900MB) exceeded. Please contact Scribe support
at support@scribesoft.com if this
problem persists''. We found this issue is a critical one as the occurrences of it is decreased but still it is persist.

Incentivized

• It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
• Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
• Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
• Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.

Incentivized

• The UI is easy to navigate and map flows are intuitive and easy to build upon after some basic training. However, a user should have some basic knowledge of writing nested statements.
• Very responsive customer support.
• The debug feature is a great tool for troubleshooting. You can easily identify where the issue is in your flow. At each debug step, it returns the expected value, and when there isn't the expected value, you know when to modify your flow.

Incentivized

• Make sure to not over-engineer shared components. It can complicate development
• Create a roadmap for where you are going - if not, you may miss components
• I suggest getting support, otherwise it could be a difficult learning curve

Incentivized

• 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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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 .

Incentivized

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.

Incentivized

really good resources

Incentivized

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.

Incentivized

It doesn't have API . We have to go for another API manager. But in Mule, it has both API manager and ESB

Incentivized

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

Incentivized

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.

Incentivized

• Overall a great tool for complex integrations

Incentivized

• Startup time - the quick time in which we can provision integrations means we can deliver requirements quickly, which is what our departments need
• The online training means we can easily get users up and running without the need for the internal cost of training
• Development time - The development that was needed to create connectors for our custom application was large

Incentivized