Chapter 9. Integrating Tivoli Monitoring 549
Best practice calls for small (up to 50 processors) scheduling networks for
automatically and periodically refreshing the resource model distributions to
ensure all processors have a current and up to date set of resource models. Use
the wdmdistrib command to distribute profiles, and the periodic runs can be
scheduled from TWS. See IBM Tivoli Monitoring User’s Guide Version 5.1.2,
SH19-4569 for details on the wdmdistrib command.
Larger (50 or more processors) scheduling networks may not want to refresh the
profiles on all systems, and may opt to instead report on all configured resource
models. The wdmlseng command can help in creating reports to address this
requirement.
This book does not discuss enabling and configuring the heartbeat function of
Tivoli Monitoring because it is not directly related to the integration with TWS.
However, in an actual production environment this function would be used to
ensure the basic health of endpoints and their connection to their gateways.
These are only some of the basic uses of the integration. More advanced usage
involves feeding the data collected by Tivoli Monitoring into additional
integrations with help desk ticketing systems for automatically creating tickets
when system conditions first start to deteriorate, data warehouses for correlating
overall server hardware performance and job processing performance, and so
on.
9.10 Possible enhancements
This section shows the power of integrating across other Tivoli products with
TWS, using the integration with Tivoli Monitoring as a starting point. These are
ideas that can help you identify other needs in your environment that can be
addressed by deploying Tivoli solutions.
The base Tivoli Monitoring product has many complementary monitoring
products in the Tivoli Monitoring family. Each product incorporates resource
models implementing best practice monitoring for specific application servers,
and includes the following products:
򐂰 Tivoli Monitoring for Applications
For mySAP.com and Siebel e-business applications.
򐂰 Tivoli Monitoring for Business Integration
For WebSphere MQ, WebSphere MQ Integrator, WebSphere MQ Workflow,
and WebSphere Interchange Server.
550 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
򐂰 Tivoli Monitoring for Databases
For IBM DB2, IBM Informix®, Oracle, Microsoft SQL Server and Sybase
database servers.
򐂰 Tivoli Monitoring for Messaging and Collaboration for Lotus® Domino®
Servers
For IBM Lotus Notes® Domino servers.
򐂰 Tivoli Monitoring for Messaging and Collaboration for Microsoft Exchange
Servers
For Microsoft Exchange servers.
򐂰 Tivoli Monitoring for Microsoft .NET
For the Microsoft .NET environment’s components: Biz Talk Server,
Commerce Server, Content Management Server, Host Integration Server,
Internet Security and Acceleration Server, Sharepoint Portal Server, and
UDDI Services.
򐂰 Tivoli Monitoring for Web Infrastructure
For Apache HTTP Server, Microsoft Internet Information Server, iPlanet Web
Server, WebSphere Application Server, and BEA WebLogic Server.
These products represent the easiest way to rapidly install and configure
availability management of specific application servers. The extensive line of
Tivoli OMEGAMON products can also be integrated into Tivoli Monitoring as
well. This provides the enterprise with a broad suite of options from which to
select ready-made monitoring solutions.
Comprehensive proactive monitoring of a TWS scheduling network would
encompass not only the system level monitoring of computing resources such as
processor, disk, file systems, and so forth., but also application level monitoring
like databases. This helps ensure that potential problems that might impact the
production plan are identified as soon as possible, ideally long before a job
launches with dependencies on the application level resources.
Integrating comprehensive monitoring across an enterprise’s technology “stack”
leads to a lot of data returned by all the monitoring points. Also, even with the
local event correlation facility offered by Tivoli Monitoring, there are still many
scenarios where the correlation has to cross system boundaries. Tivoli
Monitoring’s Web Health Console delivers a “micro” view of the managed
resources, but in larger or more complex environments a higher level
management solution is necessary for effective systems management.
Tivoli Enterprise Console and Tivoli Business Systems Manager provide these
higher level views. Tivoli Enterprise Console enables sophisticated dynamic
analysis, correlation and root cause analysis of events across all systems. This
Chapter 9. Integrating Tivoli Monitoring 551
allows enterprises to reduce cascades of events to one or a few root cause
events.
Tivoli Business Systems Manager enables management of the dependencies
between business components and their underlying infrastructure. It organizes
events into line of business views, letting enterprises plan, define, and control
their business systems (as contrasted with a technical view of the systems).
552 Integrating IBM Tivoli Workload Scheduler with Tivoli Products

Get Integrating IBM Tivoli Workload Scheduler with Tivoli Products now with O’Reilly online learning.

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