Live fast with BusinessWorks
Anonymous | TrustRadius Reviewer
Updated December 10, 2019

Live fast with BusinessWorks

Score 5 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with TIBCO Cloud Integration (including BusinessWorks and Scribe)

It is used by a department for manufacturing electronic system. It keeps separate logic from implementation, making it easy for application to call services. Logging and centralization let us easily detect problems.

We use TIBCO Rendezvous protocol behind BusinessWorks

For example, we use a service to retrieve data between different systems and though different protocols (FTP, shell script...) making all transparent to clients.


  • Abstraction of logic
  • Robustness (very high)
  • Good maintainance
  • Versatility
  • Usability of GUI (too many settings in too many places)
  • Slow management interface
  • Difficult to learn
  • Robustness of the product helped keeping business running 24/7
  • Good code reuse
  • Big initial cost
TIBCO BusinessWorks is a more high level application. You do not have to know how to code, it has a very high flexibility and robustness. Logging is very detailed and verbose.
  • We were able to integrate old systems with new frontend thanks to webservices
  • Be robust thanks to fault tolerance
  • In-person training
The training was good to understand all the environment, but the exercises where too easy and banal, not really a real world cases.

Appropriate when you need to highly monitor the service you do, or when you do not have rights or code for some parts of the service.

Good for big applications and for selling your service to customers, not to use for small web applications, the effort is not worth it. Now there are plenty of cheaper alternatives.

Using TIBCO Cloud Integration core features

Database connectors: we are plenty of legacy systems. Dozens of databases are now accessible with the APIs.
Portability: because our business runs on a mix of on-premises systems and cloud applications, we can easily work in "local", design and testing and then deploying continously in an "agile" way.
Flogo: we use realtime event driven features, to enrich static data with dynamic items.
REST APIs are around since many years but in a static manufacturing environment like ours, where management is very very reluctant to invest in new technologies, were diffucult to use. With new BusinessWorks releases, we now do everything with them, in many times faster.Again, even non IT people are able to work with data with their own favourite clients.
TIBCO is a real warranty in terms of support and robustness. We rely on them for many years, their infrastructure is fast and reliable. The possibility to speak with a single interlocutor is fundamental for the continuity of the business. critical applications can thus be moved to the cloud without hesitation. infrastructure savings allow us to work as hard as possible on the cloud.

Using TIBCO Cloud Integration (including BusinessWorks and Scribe)

  • Removing all old interfaces, unix scripts, power off old servers.
  • centralization of processes
  • Monitoring of calls, to ensure requests are used.

TIBCO Cloud Integration (including BusinessWorks and Scribe) Support

the support for tibco businessworks is of different types: for the day by day work I can work well
with standard documentation. palettes and buttons are well documented too.
With our contract we can call for support from tibco itself, which can be
defined case by case. tibco consultant I met are all very competent

Using TIBCO Cloud Integration (including BusinessWorks and Scribe)

- Things are not placed in intuitive places.
- XPath code is hidden many windows, too many click before getting a main part on the process flow. Data mapping is without doubt the best feature of businessworks, so it should be improved.
- The administration website could be more user-friendly, for example a better console of what and where is running.
ProsCons
Like to use
Easy to use
Well integrated
Consistent
Quick to learn
Familiar
Unnecessarily complex
Requires technical support
Cumbersome
  • Data mapping , database accessing is very performing and easy to maintain
  • Fault tolerance / Load balancing is very robust, thanks to lower layer based on Rendezvous (or EMS)
  • Thanks to the graphical flow of processes, everyone can easily understand what a given process do. Even if she is not the author and there is no documentation.
  • The domain part. Joining multiple machines in a single environment. Primary/Secondary instances on BW. Too cumbersome, need to be trained.
  • Installation. too many packages with similar but not configurations.
  • Deployment of EAR files is still very manual.

Integrating TIBCO Cloud Integration (including BusinessWorks and Scribe)

At the end, despite the not so good usability of the tool itself, the integration you achieve is very
powerful.
In few minutes (yes, minutes after some months of use) we can design a new integration tool.
The power of rendezvous plus the power of webservices, in addition the use of json made us doing great things
  • Oracle DB
  • rendezvous messaging
  • webservices call
The integration was done in different phases. First, we tried on developing systems, then thanks to rendezvous we could stay in listening on the same subjects of the old system (a homemade script). The big effort was to certify that the new BusinessWorks process did the same things the old one did. The built-in test system is ok for testing the process but lacks some TIBCO Rendezvous simulation parts.