This sample explains the major steps required to build the MonitorAdapter
module, generate the monitor model, augment the monitor model, deploy the
monitor model, run test data through the adapter to be consumed by the monitor
model, and show monitoring results on a dashboard.
Here is a summary of the scenario used in this sample. When a new
customer record is added to a database table, a JDBC adapter becomes aware
of it and sends customer information to a mediation flow to process. In the
monitor model, you define metrics to be set from the data issued by the JDBC
adapter, and key performance indicators (KPIs) to be set using metric data.
You then build a monitor dashboard to display the metrics and KPIs calculated
by the monitor model processing.
- The MonitorAdapter module has two components: JDBCInboundInterface and
MediationFlow. After a customer record is added to the database table, the
JDBC inbound interface operation is activated to invoke the mediation flow
with the payload.
- Based on the SCA operation and mediation flow, a monitor model is generated.
In the Monitor Model Editor, you will add metrics to the generated monitor
model to monitor the data from the adapter and mediation flow.
- To see the resulting metrics and KPIs, use the Instances view and the
Dimensional view in the dashboard.
In this lab, you will create a J2EE application using
WebSphere Integration Developer. In the application, the JDBC adapter acts
as an event resource to fetch data from a database and then send that data
to the mediation flow which emits CBEs containing the business data from the
database.
Then you will create a monitor model and define the metrics.
After
that you will deploy the application and monitor model to WebSphere Business
Monitor test environment server.
You will then use db2 commands to
trigger the monitored application to submit events.
Finally, you will
configure dashboards in the WebSphere Integration Developer test environment
and view the monitored data in several different views.