74 Smart SOA Solutions with WebSphere Enterprise Service Bus Registry Edition V7.5
3.5.1 IBM Tivoli Composite Application Manager
IBM Tivoli Composite Application Manager (ITCAM for SOA) interacts in many
different ways with WebSphere ESB Registry Edition. It can read events from the
components and can send events to the WSRR to update service metadata.
Figure 3-17 illustrates the integration of ITCAM for SOA and WebSphere ESB
Registry Edition.
Figure 3-17 ITCAM for SOA and WebSphere ESB Registry Edition
WSRR settings
The ITCAM for SOA Event Handler for WSRR, shown in Figure 3-17 on page 74,
runs in the WSRR instance that resides between WSRR and IBM Tivoli
Monitoring. Those events that are detected by Tivoli Monitoring (for example, a
new runtime service interface is down and no longer accessible) are used to
send another event to the Event Handler (optionally using IBM Tivoli Enterprise
Console® or Netcool/OMNIbus). The registry metadata is updated and the Event
WESB (Instance)
WSRR (Instance)
Mediation Flows
Web Service handler
or extension for WAS
Consumers Providers
ITCAM Event Manager
ESB runtime
information
Registry & Repository
statistics and service
metadata information
(Tivoli Event
Integration Facility
Events)
LOOKUP
Tivoli Enterprise
Management Server
ITCAM for SOA
Monitoring Agent
Tivoli Enterprise
Portal Server
Chapter 3. Topology overview 75
Handler then creates, updates, or removes properties on the WSDLPort or SCA
Export logical objects in the registry.
The ITCAM for SOA Event Handler is integrated with WSRR V7.5 (a Support
Pack is required to add this capability for WSRR versions prior to V7.5). You can
configure which objects (such as ServiceEndpoint, SOAPServiceEndpoint, and
SCAServiceEndpoint) the metadata is stored on, and support is provided for both
consumer and provider events.
The ITCAM Integration Editor is shown in Figure 3-18.
Figure 3-18 ITCAM Integration Editor
You can find details about ITCAM for SOA and the ITCAM family of products in
IBM Tivoli Composite Application Manager Family Installation, Configuration,
and Basic Usage, SG24-7151.
Sample events to be monitored
Many SLAs can be defined for a service regarding performance, availability,
security, and so forth. Example 3-1 provides one sample an SLA definition.
76 Smart SOA Solutions with WebSphere Enterprise Service Bus Registry Edition V7.5
Example 3-1 Sample SLA definition
The consumer “Supply Company” will have an average response time of
less than 1.5 second as long as there are no more than 20 request per
minute, and the concurrency is not bigger than 2 requests at a time.
For this SLA (defined in WSRR), we must monitor the invocation to the service in
WebSphere ESB. While collecting this information, ITCAM for SOA is processing
(for example, every 5 minutes) if an issue occurs as described in the following
examples:
The time response of the service took more than 1.5 seconds.
WebSphere ESB is receiving more than 20 request per minute.
Three or more requests at the same moment were processed.
When an issue occurs that violates the SLA, ITCAM for SOA raises an alert.
However, the SLA can change. Thus, ITCAM for SOA must also check WSRR to
get the SLA information and then determine whether to raise an alarm. This alert
system must be designed in the ITCAM for SOA monitoring model. Other events
might generate changes in WSRR, and these changes are also triggered by
ITCAM for SOA.

Get Smart SOA Solutions with WebSphere Enterprise Service Bus Registry Edition V7.5 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.