Read me to emphasis TIBCO.
Overall Satisfaction with TIBCO BusinessWorks
I work for TCSL where we provides services for various clients irrespective of various domains (telecom, banking, insurance, transport, health). I am working for TalkTalk group client, basically TTG provides the telecom service across UK market.
We use BusinessWorks for integrating applications (internal and external applications) and recently we have migrated the java legacy applications into BW. We mainly use BW for integrating and order management layer.
We have been using BW for the last five years. In that long span, the main issue we've faced is that BW engines go to a hung state for various reasons (like when we kill the hawk & rvd, BW engines also get hung and will not take any load). Another thing is even if we set the timeout value in the services, BW engines will not free the thread. It will keep on retaining the jobs in the service even though downstream engines are not responding within the time limit which creates the hung jobs and potential business loss.
Pros
- It's easy to develop the code for various business cases.
- BW is more adoptable for all the projects because it has all features to implement in it.
- BW performance is faster than the other applications.
- Easy to make the changes in runtime.
Cons
- Coercions for repeating nodes are sometimes hard to retrieve while mapping the fields.
- Optional fields are automatically converting to mandatory if string-length check is not provided.
- Simple archive is taking more time for deployment.
- Effective response time for processes the journeys.
- Since it has all predefined functions, took less time to deliver the requirements.
- When more jobs/threads are running hung threads are frequently created , so in some scenarios business is getting impacted while sorting of the issue.
- TIBCO BE, iProcess, EMS and TIBCO Administrator
Comments
Please log in to join the conversation