How to Monitoring TIBCO ESB


Monitoring and Reporting

TIBCO Enterprise Service Bus provides a complete set of ESB products, these products need to be combined into a solution architecture. For my current customer I designed and implemented the following monitoring and reporting solution that resulted in a significant reduction of business process exceptions.

The solution includes the following products
  • OpsView (Enterprise IT Monitoring)
  • TIBCO Hawk (monitor infrastructure behavior, metrics and failures)
  • TIBCO Clever (monitor functional and technical errors)
  • TIBCO Spotfire (reporting)
  • Pentaho Data Integration (ETL)
  • Esper (Complex Event Processing)
  • Confluence (Wiki based knowlegde base)

Continue reading


TKP Pensioen BV

TKP Pensioen BV provides services to pension funds such as administration, asset management and many others. TKP is optimising its business processes and integrating Oracle applications with its document management system (Documentum). Integration will be done by introducing a service oriented architecture supported by Oracle integration products, workflow en MQSeries messaging.

Mr Ritter was asked as an EAI consultant to help with this process and to start setting up the Oracle Interconnect and MQSeries middleware. He designed and implemented the MQSeries middleware, solved problems with the Oracle middleware and helped to set up a first working version.

When testing he quickly revealed a problem with the Oracle InterConnect middleware, it was unable to execute a proper request/reply sequence. It could not send an answer (reply) to the originator because it lost the originator address (messageId). Mr Ritter managed to fix the problem by reverse engineering of the Oracle software that was written in Java. When this fix proved to be working he informed Oracle support and asked them for a more definite fix.

IB-Groep “Troubleshoot E-Service”


DUO / IB-groep

The IB-groep is a governmental organisation for student administration. The IB-Groep E-service offers direct web access to student information via the internet.  The end users on the website complained about problems getting to their data. Mr Ritter was asked to find the root cause of these problems.

The website directly connects via an MQSeries based middleware infrastructure to their back office systems running on IBM mainframeAS400 and Windows 2000. IB-Groep experienced a wide range of errors, from lost messages to timeout situations and lost connections. Mr Ritter was asked to determine the cause of all these problems, find solutions and to give advice for improving the infrastructure.

Mr Ritter first setup a measurement system to collect information on current system behaviour. This included network- , computer system traces and response time overviews. This information was presented in spreadsheet format to management on a daily basis showing availability and periods of system outage. This proved to be a very fruitfull approach. Mr Ritter concluded from all collected data that there was a serious network problem, some internal systems had performance problems and the Service Level Agreement with its external mainframe supplier was not met.

Meetings were arranged with the external mainframe supplier to improve performance to aggreed SLA levels. Also network and system specialists where involved to find the bottlenecks and improve system performance. Mr Ritter coordinated work between these specialists and conducted further tests. All problems were identified and solved. Mr Ritter compiled a final report on the current state of the infrastructure and improvements to be made.

Philips Semiconductors “SPEED”

Philps-SemiConductorsIn 2000, Philips decided to phase in an SAP-ERP system for all its manufacturing sites worldwide. A program, SPEED (Superior Production
Execution through ERP Deployment), was launched. The first phase that enabled worldwide integration of SAP ERP and legacy systems in the Netherlands, France, Thailand, Hongkong and China.

Mr Ritter worked in close cooperation with the main architect responsible for designing the messaging architecture and system management environment for the world-wide SAP implementation. The resulting architecture is based on a TIBCO Rendezvous publish/subscribe implementation.

  1. In order to full fill the project requirements the standard TIBCO Message Broker was enhanced by Mr Ritter with extra functionality for message integrity checking based on XML schemas.
  2. Mr Ritter setup a system monitoring system based on TIBCO Hawk
  3. Mr Ritter also fixed a blocking problem with the Message Broker software by patching the TIBCO source code and donated the code to the TIBCO support group.

The initial rollout was successful and the project continued to its next planned phase. Press release: ss_Philips_SPEED__Accelerating_Global_Integration