306 Problem Determination Using Self-Managing Autonomic Technology
9.1 Scenario description
In a distributed environment, enterprise software applications are multi-tiered
and their components run on multiple nodes. Very often, these applications
establish database connections to insert, modify, and update database records.
In this chapter, we show an example scenario using a two-tier application. The
sample Java application runs on the application node and accesses a database
hosted by an IBM DB2 server running on the database node. The sample Java
application generates Common Base Events (CBEs) natively and logs them into
a log file. Figure 9-1 depicts the sample Java application used in this case study
scenario chapter.
Figure 9-1 Application scenario environment
In order to make this application scenario autonomic, the following actions need
to be performed:
On the database node:
– Develop a Generic Log Adapter (GLA) context to convert the log
information created by DB2 into a CBE format. Common Base Events will
be stored in a log file by the GLA outputter.
– Develop resource models to monitor and take corrective actions based on
events created by DB2 and translated by the GLA.
Scenario2
Application
DB2
DB2 Log
File
CBE Event
CBE
Log File
Application Node
Database Node
Chapter 9. Problem Determination scenario two 307
– Develop a second GLA context to convert log information created by DB2
into a CBE format. This GLA context’s outputter will use Web services to
send the Common Base Events to the application node. A custom
outputter for this GLA context, named ITSO-SHIM outputter, will be also
developed.
On the application node:
– Create resource models to monitor and take corrective actions based on
events created by the sample Java application.
– Develop a simple Web services application to receive Common Base
Events from the second GLA context running on the database node. This
Web services application, named ITSO-SHIM Web service, will be running
on the application node on top of IBM WebSphere Application Server. The
ITSO-SHIM Web service will receive CBEs from the second GLA context
and store them into a log file in the application node.
– Create resource models to monitor and take corrective actions based on
created events stored in the ITSO-SHIM CBE log file.
Figure 9-2 on page 308 shows the application scenario environment with the
autonomic computing elements in place.
308 Problem Determination Using Self-Managing Autonomic Technology
Figure 9-2 Autonomic application scenario environment
Using the IBM Autonomic Computing Toolkit and other development tools, we will
create, develop, and configure self-managed autonomic technology. After all the
components are developed and deployed on both the application and database
nodes shown in Figure 9-2, the following sequence of events will be performed to
demonstrate the automation and self-healing capabilities of the autonomic
environment. The following steps refer to Figure 9-2:
1. All components of the application are operational, up, and running on their
respective nodes.
Scenario2
Application
CBE Event
CBE
Log File
ITSO-SHIM
CBE Log file
WebSphere
ITSO
SHIM
Redbook
AME
Runtime
AME
RM
Action
Action:
Restart
connection
to DB2
ILT
ILT
DB2 Log File
CBE DB2
Log File
GLA
Context 2
AME
Environment
(SARA)
AME
RM
Action
ILT
GLA
context1
Restart
DB
ITSO-SHIM
GLA outputter
DB2
Application Node
Database Node
Get Problem Determination Using Self-Managing Autonomic Technology now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
