- It provides a palette which makes it very easy to map data from one format to another and do calculations or transformations as part of the mapping.
- The pallets make it easy to get different listeners and publishers stood up very quickly.
- It is easy to deploy and manage on application across multiple machines.
- It provides consistent code across multiple development teams, as there are code is presented as an activity which is simple dragged and dropped.
- In BW 5, there is no native JSON parsing, it must first be converted to XML which adds overhead. Native parsing was just added to BW6.
- Some settings must be editors in a tea text file, and are not editable as a part of the deployment.
This is useful if you need to test why something in a deployed environment is failing. You can turn on logging there to capture the input message and then run that through the debugger in your local environment.
- Solutions built with BusinessWorks are flexible
- Learning curve is not too steep
- Seamless integration, development, testing and deployment
- Reduce time to market for any deliverable
- I would like the design time to improve and match that of the designer. The newer versions are getting better.
- Would like to have web app development and deployment possible through BusinessWorks design time like we had with AMSG.
So complete ordering system is using Business works and 75 % of Ingram Micro revenue goes through our integration platform using BW.
- B2B integration.
- Micro service and also SOA enabled implementation.
- Migration of 5.x to 6.x should be easy. It is currently like doing complete new projects.
- There should be more in built plugins rather having to buy each and every plugin separately.
- Very strong in messaging
- Unique platform which supports Microservices and Cloud with enterprise integration
- Extended support and OOTB integration with APIM platforms and Event processing
- OOTB Analytics support on integration BW
- Upgrade from BW 5 to 6 is difficult for customers, which requires redesigning and sometimes re-coding the Integrations to support containers. Need to make it easy
- Nice graphical user interface and works on any platform. Easy to develop/deploy for a programmer.
- BusinessWorks is forward and backward compatible.
- It would be helpful to get more plugins (e.g SFTP/REST Plugin) out of the box.
- BW is a great engine to use along with other TIBCO softwares to make proper use of business flows to get data from point A to point B throughout the lifecycle
- BW upgrade paths are typically cumbersome and quite frankly much easier to do a complete parallel build and cutover which can be time consuming and costly
TIBCO BusinessWorks Review: "Tibco BW5 is a great productivity tool, but the new version, BW6, is not."
- TIBCO Business Works does field mapping well. I often have projects that include ERPs like SAP, which can often use large and complex XML schema. BW makes it easy to map fields between these cumbersome documents, loop over repeating nodes, apply xpath... I think this is where BW has the biggest advantage over other tools.
- BW also makes it easy to establish logical flow. When it's just code on a page, you have to rely on UML diagrams. BW offers an icon based designer to design the logical flow, which is pretty nice and intuitive.
- TIBCO BW runs very efficiently. People are often surprised at how quickly our systems move, especially when components like the database adapter are used. We have many integrations quickly moving large amount of data.
- Training developers new to Tibco BW5 easy. This might be my favorite thing about it these days. If someone already has experience with app development, or is otherwise familiar with business processes, sql, xml, ems, etc., BW5 is very easy to be productive on.
- General development time on BW5 is quick. From a business perspective, I would say this is the strongest advantage. Creating new processes and making adjustments is fast and reliable -- not prone to creating new issues.
- When discussing needed improvements to BW, we have to make a clear discrepancy between BW5 and BW6. BW5 is stable, tried-and-true, and easy to train people on. BW6 is the total opposite. Also, BW6 offers no significant advantage over BW5. I began using BW6 almost two years ago now. Our original intention was to make use of its REST activities first thing, then transition all our processes to BW6. Today I still only use it for REST, but I don't use the REST activities because they can't do complex queries. I have to use HTTP activities... We also have NO plans to move anything other than REST interfaces to BW6.
- The main issue with BW6 is the dreadful bugs. It's a sophisticated system but very immature, so it's loaded with dangerous surprises. I even took the BW6 bootcamp class, intending to get a good start. But the class was mostly worthless because the instructor couldn't even run the example solutions. We just fumbled though numerous introductions to features. The best advice I can give is, first learn BW5. Then, if you really want to learn BW6, go ahead, but don't use it for any projects with critical deadlines. Also, push to the repo often, and understand that your workspaces are basically disposable. Things go wrong that just aren't worth all the XML editing to fix, so it's better to just backup an hour or two and start again. Also, delete and recreate if anything starts to act funny. When the designer crashes, start it up, shut it down, then start it up again. Also, you're not alone. Everyone knows this thing is buggy.
- The BW6 designer is built on Eclipse. I was optimistic about this, and anticipated a more efficient interface compared to BW5's designer, which is clunky. BW6 designer looks more slick, but it offers no real advantages over BW5, and is heavy and unstable. It crashes often, is painfully slow, corrupts project files, and otherwise requires a lot more time than BW5 for even simple tasks.
- Testing is more difficult on BW6 than on BW5. Setting up a whole integration and running it locally is an easy task with BW5. Things run quickly. It's easy to see the input and out put data from each process. Errors are quickly evident. BW6 -- just getting it to build and run can be difficult. The big issue is that there are numerous run time hazards that BW6 will not indicate after compilation. You just have to run the thing and sift through terminal output. Here's a tip. It always say every process is imparted. The gobs of red text that poor out, that's normal and OK. Neither of these sections are describing your error. Your error will be in black text somewhere.
- Once you get your integration running, examining the input and output is challenging. The designer will take your focus for various reasons. For example, if you have http debugging enabled, you simply can't look at anything else. The focus is repeatedly returned to the standard output terminal. Or, even with minimal debugging and nothing trying to grab focus, just digging up the data can be difficult, especially if you're dealing with large objects. You can't click on an activity to see its output, as with BW5. You have to sift through the nested lists of processes and down into activities. It's actually hard to even explain how to see input/output without an image.... But you can't really even see the data from within the designer itself. You have to copy it out and paste it into a text editor.
With BW6 it's a more cumbersome process and you'd better have plenty of memory on your machine and a lot of patience waiting for everything to start up. Good eyes is also essential because BW6 dumps a huge amount of standard output, which often includes run-time errors that may or may not be actual issues.
- Reduces the number of trivial tasks that are often associated with other programming languages.
- Enterprise friendly for both multi user development and deployment solutions. Also fully capable of running a highly available infrastructure.
- Extensible out-of-the-box and through plug-ins.
- BW 5.x and the run-time agent both feel very dated, though this has been addressed with BW 6.x.
- BW 5.x is not as friendly to CI, though this has been addressed with BW 6.x.
- While the tool doesn't require specific programming language knowledge, it is still necessary to become familiar with BusinessWorks which is most effective with training. This does require that developers to have knowledge of the tool and has lead to some difficulties finding skilled software developers.
- Ease of use—Integration activities
- Short deployment Processes
- Scalability and extensibility of Projects
- Drag-and-drop graphical development environment
- Energy and Utilities area: we faced situations to respond an increasing demand, and through TIBCO BusinessWorks we reduced costs and job time.
- Bank Area: through TIBCO BusinessWorks we connected and unified banking business processes across applications and data sources.
- Finance Area: The integration project was ready to go to production within a realistic timeframe and deploying from development to a running project went smoothly.
- Good support for various modes of communications, Java JMS, Tibco EMS, HTTP, Restful, SOAP etc. With easy to develop interfaces.
- Acts as a good data transformation layer with excellent interfaces for cross mapping the data with easy to implement new custom x-path functions and complex data mapping between the complex XML structures.
- Easily Scalable
- Needs more support to customize SOAP interfaces. Although the SOAP based interfaces are very easy to implement, they are not Java like. It is hard to add any custom headers, need to define new port to allow the SOAP clients to download and the wsdl etc.
- I am using BW 5.13, Restful support is not available out of the box in this version. Although the parallel version BW 6.x has the support for restful interfaces, BW 5,13 needs a new plugin. Which is annoying and expensive.
- Most databases and SQLs has been supported by TIBCO. But still they cannot support a prepared statements with "in" clauses like "select * from employee where workplace in ( ?, ?, ? ... )". TIBCO needs to implement the in clause more cleverly where the developers can have any number for values in the "in" clause.
- I have to either write a database stored procedure or use SQL direct for this purpose. I have SQL direct as this is tagged as a security vulnerability and we have no track of what sql is been executed ?
On the other hand I have had multiple requests from other application owners like Pega requesting me and team to build triggers and stubs using tibco BW, so they can test their stuff !!
- REST/JSON and SOAP support
- JMS compliance is excellent
- Less development time if design is well thought out and addressed well for use case
- Better integrated testing support
- CI support is progressing well and needs to be made more flexible and easy to integrate
- TIBCO does well on data manipulation and on heterogeneous systems integration. We were able to perform messaging between several different systems, without developing custom APIs. With TIBCO BusinessWorks it's easier transform and analyze data, including managing of error cases.
- It would be great to have dedicated regex functions, such as search and replace, match and so on. For data or strings manipulation it's strongly recommended.
TIBCO BusinessWorks is a powerful solution for homogeneous integration with a large choice of connectors and the possibility of developing custom ones.
- Develop and deploy fast. The drag and drop approach allows experts and beginners to develop consistent services, based on common practices. The latest version of BW offers the possibility of easily integrating DevOps standards (CI/CD)
- BW contains a lot of standard connectors that enable connection to the majority of applications or services. It's very easy to develop custom adapters that will fit our ad-hoc requirements.
- With a Java backend and XML knowledge, everyone can quickly ramp up in a BW team.
- Better Integration with the Big Data world
- More visibility into features planned for release in future versions
- Extend the possibility of developing customer adapters in every language running within the JVM (e.g. Scala)
- Development of REST services (TIBCO is following open API standards).
- Integration of legacy systems (not too old such as mainframe)
- Short time to market
- Developing batch jobs is out of scope of BW
- Cost might be a blocker for companies thart don't want to invest too much
- High volumes of data (big data)
Mainly used in the MES department for system integration. Limited use on business system level as yet, with the exception of some business systems being integrated with SAP.
Mainly used for process orchestration during integration. It allows us to use a standardized platform for building, deploying and monitoring our integration solutions.
- Platform independence, although we are using just MS Windows
- Powerful, with a great set of components (activities) available, yet also being able to customize and extend according to our needs
- Runs quite stable within deployment
- Deployed process can become quite resource intensive, with each deployment running within its own JVM
- Licensing cost is quite high
- The version we are using does not yet support newer technologies like REST and JSON natively
We find it is well suited for integration solutions using messaging with XML as protocol.
A possible issue could that it may be used for solutions where BW is not really needed and its power does not come through. We have seen it being used as a tool for moving files around, which it can do but is a waste of the tool's power. It is too expensive to use for such trivial actions.
TIBCO BW is used across the whole organization. It is an efficient software to ease the integration process of backend and front-end systems. It supports a wide variety of technology like SAP,Siebel,PeopleSoft,Facebook etc etc. Someone using TIBCO BW does not have to worry about data conversion issues between front-end and back-end systems or incompatible software products. It seamlessly converts the data via the use of XML as a standard.
It is a highly scalable and reliable software that has many supporting technologies like JDBC, JMS, different databases, messaging systems, data conversion system. It is extremely user friendly using the Eclipse UI as a standard and is highly customizable.
It is certainly a leader in the integration software industry.
- Process large volume of data in real time
- Suited for data conversion for systems that follow different data conventions
- Suited for cloud deployment
- Not suited for low processing capability systems
Also, stability and concurrent testing has to be extensively done hence is time consuming.
The software used is TIBCO BusinessWorks and more precisely streams are integrated with EMS, Web Services and Files, for customers in the energy and banking sectors.
- Flexibility as it is possible to customize flows for any need
- Compatibility with a large number of drivers
- Highly customizable
- SFTP - currently TIBCO has no palette for performing SFTP operations. We have to write custom Java code which does the SFTP operations and then call the Java code from TIBCO.
- Cloud interaction is not that well explored while using TIBCO BusinessWorks, BC and adapters etc.
- The RESTful + JSON support is still not too perfect.
TIBCO BusinessWorks 5 has a very simple and useful testing phase unlike the BW 6 where the testing is very tricky. Logging using breakpoints is still very useful as each palette allows you to see in real time the data transmitted in input or output of the palettes to the designer. The testing phase on IBM Sterling for example does not allow you to see all the steps of file transfer and this results in a more complicated debugging phase
My company uses BusinessWorks most to develop finance or energy-related processes, but another group deals with the systémistic part (Installation, Maintenance and Configuration of Environments).
The issues faced for the infrastructure section are property configurations that block the start of the process, and on the development side the issues encountered are on the REST processes.
- You do not have to learn a new language to be able to develop it.
- The ability to have a container that can meet my project needs (see Cloud option).
- Creating services and integrating the visual applications used, developing the "model-driven" environment, then releasing with TIBCO BusinessWorks in runtime.
- The ability to add a new machine to the domain without having to run commands so you can decide if you want to deploy everything on the new added node
- You can improve the management of property modules on BusinessStudio
- You could also improve the part of drag and drop activity on BusinessWorks since in order to add an activity, you must first click and then move inside the process, I find it a very tricky passage.
BusinessWorks can be used to integrate different systems and communicate with each other through processes, as well as simplify process development.
Testing of BusinessWorks processes, the fantastic thing is the ability to directly test the newly developed flow, as well as decide to debug and control the values present in each single activity present in the flow of the process. There are other tools that can be used to test BusinessWorks processes (eg Soap UI, etc ..) but make direct calls to the service without having access to the entire flow of the process.
Main scenario: Integrate internal source systems based on different technologies with SAP C4C CRM. An event based architecture was built using an In-Only pattern based on XML over JMS. Soap over http services exposed by SAP were easily consumed using the out of the box functionality of the product.
The integration layer was built defining a Canonical Data Model to reduce the number of transformations and simplify the code maintenance.
1) Event based architectures based on XML over JMS
2) Synchronus services implementation based on SOA with SOAP
3) REST stateless rest services
4)Implementation of transformations patterns
Debugging info for each transformation, mapping, service invoked is available from the debug tab.
OSGI console is available to debug different issues and get low level informations on applications developed, like bundle,dependencies,etc...
OSGI console can be used also a runtime to debug issues with deployed applications.
Tibco enterprise administrator allow to manage runtime entities in a very simple way.
- It is a product that allows distributed solutions that complies with SOA principles
- With the principle of non-code, it helps companies have more agility and better understand their processes and fulfill the business objectives.
- Manage real-time information for new business decision-making strategies
- There are few customers with the product in my country Colombia. So the potential of the platform is not known.
- Not much documentation for independent developers.
- It is a very good integration platform. Easily used to model a business process and integrate data sources and services.
- It is easy to learn and one does not have to learn a different programming language. It provides loads of built-in services that are dragged and dropped to build processes.
- Deployment of its services are very simple and well managed my the administrator.
- It integrates very well with other TIBCO software to build more robust development platform.
- Extension of build-in services/APIs.
- Improvement could made in its integration with iProcess.
- Improvement is the information logged by the inbuilt-services in cases of errors.
TIBCO BusinessWorks Scorecard Summary
About TIBCO BusinessWorks
TIBCO BusinessWorks Screenshots
TIBCO BusinessWorks Video
TIBCO BusinessWorks Downloadables
- TIBCO BusinessWorks 6 Datasheet: TIBCO’s flagship integration platform provides next- generation enterprise integration capabilities.
- TIBCO Connectors Datasheet: TIBCO universal connectors help IT organizations integrate on-premise applications, databases, and other technologies with SaaS and mobile solutions.
- White Paper: Why "Good Enough" Doesn't Cut It, 13 Ways to mess with success. This paper explains why mastery will not be possible with merely adequate (“just good enough”) integration technology. “Good enough” will produce a massive negative impact and prevent you from maximizing success (digitalization) in all areas.
TIBCO BusinessWorks Integrations
TIBCO BusinessWorks Competitors
TIBCO BusinessWorks Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
TIBCO BusinessWorks Technical Details
|Operating Systems:||Windows, Linux, Mac|