ITCAM for SOA integration with TBSM
jwalczyk 100000GD5G Visits (14231)
This article will discuss the use of Discovery Library Adapter (DLA) technology to illustrate strategic integration capabilities between IBM Tivoli Composite Application Manager for Services Oriented Architecture (ITCAM for SOA) and IBM Tivoli Business Service Manager (TBSM). The integration of these types of monitoring components is critical to the success of an organizations’ Business Service Management (BSM) strategy.
ITCAM for SOA was designed to observe, monitor, track and apply controls to web services in an SOA environment. ITCAM for SOA graphically displays service information in a single, integrated console and generates events to monitor and enforce organizational SLA policies. The collection of service information is done through the deployment of agents which capture data in real time. Service definitions may be sent to TBSM using the ITCAM for SOA DLA. The status of these services (slow response times, missing responses, faults, etc.) may then be sent from ITCAM for SOA to TBSM using built-in ITM functionality (EIF).
What is the ITCAM for SOA DLA? A discovery library adapter (DLA) is common mechanism used by various IBM Tivoli products such as ITCAM for SOA, CCMDB, TADDM, etc. Using the DLA process, data is extracted from a specific source and an XML file is generated called a discovery library adapter book (a.k.a. IdML book). An IdML book may then be loaded into a DLA supported repository, for example, ITCAM for SOA's Tivoli Common Object Repository (TCORE) or as we’ll see later, into TBSM. ITCAM for SOA ships with three such DLA's; WSRR, BPEL and SOA - we'll only be talking about the SOA DLA. Once this data is loaded into TBSM, it may look something like the image below.
The images below are the TBSM GUI containing ITCAM for SOA services.
The TBSM Data server was designed to analyze IBM Netcool/OMNIbus ObjectServer events or SQL data for matches against the incoming-status rules you configured for your service models. This process can also be driven by ITM situations from ITCAM for SOA agents. Therefore, ITCAM for SOA events may change the service status and the status of the TBSM service model will change accordingly. When a services status changes, TBSM sends corresponding service events back to the ObjectServer.
The TBSM GUI is used as the primary dashboard for IT Operations. When a TBSM component status changes from green to yellow or red, the user may drill down into the ITCAM for SOA workspaces to gain more information and resolved the issues as depicted below...
...link from TBSM GUI to ITCAM for SOA workspaces....