This is the beginning of a new era for all the TIBCO community. It is the moment to look to the future and leave all the things we know, to embrace the things that are waiting for us. This is the birth of TIBCO BusinessWorks 6.
The announce of this new version of the main integration suite of the Californian company is more than that. After so many failed tries such as TIBCO AMX Service Grid suite, TIBCO BusinessWorks Express, this is the moment to face the future.
BusinessWorks 6.0 is here, and the change will be general and complete. The BusinessWorks we know is already dead, but this is not a bad thing. This could be a good thing for all of us. After previous failed tests, the company learnt many things that we can see in this new release.
1.- The IDE – TIBCO Business Studio
As all of us we could guess, we have to say goodbye to our loved TIBCO Designer as we did like TIBCO BE developers. We now have to face the change to another TIBCO Business Studio based on the Eclipse IDE. This TIBCO Business Studio is already prepared to face all our TIBCO BW developments (better not remember the TIBCO Designer plugin for Eclipse. This is not the same thing… :))
2.- The Administrator: TIBCO Enterprise Administrator
Another goodbye we have to face. Goodbye to our old TIBCO Administrator. Our new developments we have to be deployed in the new bet of TIBCO. The unified enterprise administrator, known as TIBCO Enterprise Adminsitrator or TEA. This will be a new administrator that have the goal to embrace all the TIBCO developments independently of its nature: TIBCO BE developments, TIBCO AMX BPM developments, TIBCO BW developments as so on.
Based on a logical division similar to TIBCO AMX suite, but technology based on one of the best TIBCO products: TIBCO Active Spaces. We have our environments, hosts and nodes but with another naming. We have to get ready to use all these new terms: AppSpace, AppNodes. On our next posts we will deep into all these changes so don’t worry about it for now.
3.- SCA View
As we could suffer as TIBCO AMX Service Bus and TIBCO AMX Service Grid developers the SCA vision is a feature we have to get ready to face it, because it is here and we think it’s for the future. The Service Component Architecture is a common technology embraced and developed by all the import integration vendors such as TIBCO, Oracle or IBM.
In our new developments we have to get used to define service interfaces, binding when we are going to specify transport specific configurations, references to define the dependencies of our services with the external world and so on. If you come from the TIBCO AMX world or from another vendor we have no problem to face it, but if you come from TIBCO BW 5.x world you have to suffer and adoption time to be able to think in a SCA way, but don’t worry all of use passed it and we are here, alive and wiser than before.
In our next posts we are going to breach and go deep in all the changes and all the new features TIBCO BW 6.0 gives us, so you can face your developments and designs without worry about this changes. We are here to suffer for all of you 🙂