Difference Between TIBCO BW5 Administrator and BW6 TEA

After a great success of TIBCO BW5 in the market; with worldwide acceptance and a rapid growth and enabling a huge number of customers to achieve their business goals in an efficient manner by utilizing the powers of BusinessWorks 5.xx; TIBCO has introduced BW6 with major advancements and changes to meet the market demands. New product has many differences in terms of architecture, functionalities, look & feel and product features.

From design & development perspective, TIBCO Designer has been replaced by Eclipse based BusinessStudio which appears to be a more familiar IDE for those developers who have worked before with Eclipse IDE for any Java projects.

For administrator, TEA (TIBCO Enterprise Administrator) has been introduced replacing the classic TIBCO administrator.

While I will cover the differences observed by me from development point of view, in a separate post, here I will briefly talk about some of the major differences I observed for administrator in BW6 compared to my experience with BW5 administrator.

Please note that these are just my observations and may not necessarily reflect in-depth details and power of the product itself.

Differences observed in TIBCO BW6 TEA Compared to BW5

1. In BW 5 we use Domain Utility for domain creation and domain management, in BW 6, we can do domain management directly from TEA or else can use Bwadmin utility to create Domain, AppSpace and AppNode.
2. In Bw5 each machine should have TRA install in 5.x but in 6.x each machine should have one bwagent running to communicate with TEA.
3. In BW6, we can install directly from Eclipse based Business Studio by adding Deployment Servers directly from BusinessStudio.
4. In BW6, We can see Process diagram directly in TEA which is helpful in understanding process structuring for debugging purposes.
5. In BW6, a running AppNode can be enabled for remote debugging from either Bwadmin or the Admin UI. Once enabled, use TIBCO Business Studio to debug the application running on the AppNode.
6. When an application is deployed to an app space in BW6, it gets deployed to all the machines which are part of that space.
7. In BW6, For deployed application properties, multiple profiles can be created and we can choose profile for a deployed solution.
8. We can view endpoints, components, and processes (including process diagram) for a running application from the Admin UI.
9. BW6 Provides option of registering URL Agent through which it is possible to add non-BW (e.g. Java) products as well to TEA.
10. Earlier versions of TIBCO Enterprise Administrator supported only one-way authentication. TIBCO Enterprise Administrator 1.3.0 and above supports two-way authentication as well.
11. Method of deploying solutions in FT/LB mode has changed considerably with introduction of managed and unmanaged fault tolerance and setting up of persistence modes (memory, group, datastore).

Ajmal Abbasi

Ajmal Hussain Abbasi is Integration Consultant By Profession with 13+ years experience in Integration domain mainly with TIBCO products. He has extensive practical knowledge of TIBCO Business Works, TIBCO Cloud, TIBCO Flogo, TIBCO Mashery, TIBCO Spotfire, EMS and TIBCO ActiveSpaces. He has worked on a number of highly critical integration projects in various sectors by using his skills in TIBCO Flogo, TIBCO API Management (Mashery), TCI, Tibco Designer, TIBCO Business Studio, Adapters, TIBCO EMS, RV, Administrator, TIBCO BE, TIBCO ActiveSpaces etc. Ajmal Abbasi has experience with MuleSoft ESB as well. Ajmal Abbasi is also experienced in the area of API Management particularly with WSO2 API management platforms. Ajmal Abbasi is also experienced in developing solutions using Core Java and J2EE Technologies. You can contact Ajmal Abbasi for Consultancy, Technical Assistance and Technical Discussions.

More Posts - Website - Facebook - LinkedIn - YouTube