WebGUI launch to IBM Tivoli Monitoring
This chapter describes an integration that can be provided by using the WebGUI component of IBM Tivoli Netcool/OMNIbus with other Tivoli products in your environment. After adding this customization, WebGUI users can drill down for additional details to uncover the root cause of the events shown in the WebGUI. WebGUI users will be able to more quickly determine and resolve issues in their IT environments. This integration requires the development of several custom scripts and additional setup, as outlined in other sections of this book.
This chapter contains the following topics:
11.1 Scenario description
This scenario demonstrates the launch-in-context integration between the IBM Tivoli Monitoring 6.2.2 and IBM Tivoli Netcool/OMNIbus Web GUI 7.3 products.
This chapter accomplishes the following tasks for this scenario:
•Install the products used in Integration.
•Outline the steps involved in the setup of Event Forwarding.
•Confirm through the IBM Tivoli Netcool/OMNIbus Web GUI 7.3’s Active Event List (AEL) portlet that our new event fields are being populated and accessible through AEL scripts.
IBM Tivoli Netcool/OMNIbus alerts.status fields and EIF Probe rules are updated to allow the communication between IBM Tivoli Monitoring 6.2.2 and IBM Tivoli Netcool/OMNIbus Web GUI 7.3.
•Define a new AEL tool to use to launch into the Tivoli Enterprise Portal server UI, which is associated with the IBM Tivoli Monitoring 6.2.2 that sends the event, passing to the script the parameters that open the workspace that is associated with the resource in the event.
11.2 Products involved
The products and product components involved in this scenario are as follows:
•IBM Tivoli Monitoring 6.2.2
•IBM Tivoli Netcool/OMNIbus Web GUI 7.3
•IBM Tivoli Netcool/OMNIbus 7.3
•IBM Tivoli Netcool EIF Probe 9.0
•IBM Tivoli Monitoring Situation Update Forwarder (SUF) Component
•LDAP server on Microsoft Active Directory
11.3 Benefits
Benefits of this integration are as follows:
•Ability to drill down for additional details to uncover the root cause of the events.
•More quickly determine and resolve issues in the IT environment.
•Visualize event data efficiently with the capabilities of consoles.
11.4 Architectural diagram of the integration
Figure 11-1 shows the architectural diagram of the integration.
Figure 11-1 Overview of IBM Tivoli Netcool/OMNIbus Web GUI integration with Tivoli Enterprise Portal
11.5 Implementation steps
This section describes the implementation steps of this scenario.
11.5.1 Product installations
A description of the products that are involved in this scenario are provided in this section. Web addresses for information about installing the products are also provided.
IBM Tivoli Monitoring 6.2.2
IBM Tivoli Monitoring monitors and manages system and network applications for a variety of operating systems, tracks the availability and performance of your enterprise system, and provides reports to track trends and troubleshoot problems. IBM Tivoli Monitoring is the launch-into product from the IBM Tivoli Netcool/OMNIbus Web GUI 7.3 used to provide additional details.
Instructions for installing and configuring the IBM Tivoli Monitoring environment are in the IBM Tivoli Monitoring Installation and Setup Guide:
IBM Tivoli Netcool/OMNIbus 7.3
Tivoli Netcool/OMNIbus is a service level management (SLM) system that delivers real-time, centralized monitoring of complex networks and IT domains. Tivoli Netcool/OMNIbus can consolidate information from different domain-limited network management platforms in remote locations. Tivoli Netcool/OMNIbus tracks alert information in a high-performance, in-memory database, and presents information of interest to specific users through filters and views that can be configured individually. Tivoli Netcool/OMNIbus has automation functions that can perform intelligent processing on managed alerts.
IBM Tivoli Netcool/OMNIbus integrates with IBM Tivoli Monitoring solution by using its probe component. Tivoli Enterprise Monitoring Server component of IBM Tivoli Monitoring sends the alarms that are created by situations and Tivoli Netcool/OMNIbus EIF Probe receives them as the integration and creates events in Object Server.
The scenario, described in this chapter, can help improve the IBM Tivoli Netcool/OMNIbus, IBM Tivoli Monitoring integration by enabling communication between both web consoles. It is possible to open Tivoli Enterprise Console from IBM Tivoli Netcool/OMNIbus Web GUI by using a customized script within the context of the event.
Installation and configuration details are at the following web address:
IBM Tivoli Netcool/OMNIbus Web GUI 7.3
IBM Tivoli Netcool/OMNIbus Web GUI is the user console of Tivoli Netcool/OMNIbus product. It is the web-based user interface that lists and operates on the events that are stored in Object Server.
An important entity of the Web GUI product is the Active Event List (AEL), which is a list of events that the user can configure to monitor the environment. With the help of tools, the user can work on the stored events and take actions.
This scenario adds a new action option to the alerts menu for Active Event Lists. The user can then open the Tivoli Enterprise Portal console that is associated with the event from the IBM Tivoli Netcool/OMNIbus Web GUI.
Installation and configuration details are at the following web address:
IBM Tivoli Netcool EIF Probe 9.0
To integrate IBM Tivoli Monitoring and IBM Tivoli Netcool/OMNIbus, Tivoli Netcool/OMNIbus EIF Probe is needed. EIF Probe is a component of Tivoli Netcool/OMNIbus.
|
Note: Starting with Tivoli Netcool/OMNIbus V7.3, Tivoli Netcool EIF Probe is installed with the same installer as the core Tivoli Netcool/OMNIbus product. In previous versions of Tivoli Netcool/OMNIbus, the EIF Probe had a different installation package and was installed on Tivoli Netcool/OMNIbus as a patch.
|
You configure IBM Tivoli Monitoring Tivoli Enterprise Monitoring Server to send situation alarms to the EIF Probe, and the EIF Probe receives and processes those alarms. Tivoli EIF Probe can do the event field matching with the help of rule files, and create an event for each of them in Object Server.
You can install Tivoli Netcool/OMNIbus EIF Probe on the same server with Tivoli Netcool/OMNIbus, and on a separate server.
Installation and configuration details are at the following web address:
IBM Tivoli Monitoring: Situation Update Forwarder
Situation Update Forwarder, known as SUF, is a tool of IBM Tivoli Monitoring that is used to send the updates back to IBM Tivoli Monitoring from Tivoli Netcool/OMNIbus. Acknowledgement and status change operations are the possible operations performed on the stored events at WebGUI.
SUF is installed between IBM Tivoli Monitoring and Tivoli Netcool/OMNIbus, waits for the updates coming from Object Server, and sends them back to IBM Tivoli Monitoring. With the help of Tivoli Netcool/OMNIbus EIF Probe, Situation Update Forwarder supports the bidirectional event and data flow between IBM Tivoli Monitoring and IBM Tivoli Netcool/OMNIbus.
SUF installation package is included with the IBM Tivoli Monitoring v6.2.2 Tools package. SUF must be installed on the same server as the IBM Tivoli Netcool/OMNIbus ObjectServer. To perform the installation and configuration, follow the instructions at the following address:
11.5.2 Event integration
To integrate IBM Tivoli Netcool/OMNIbus with IBM Tivoli Monitoring bidirectionally, implement the following flows:
•Events from IBM Tivoli Monitoring to IBM Tivoli Netcool/OMNIbus (with the help of the Tivoli EIF Probe)
•Event updates from IBM Tivoli Netcool/OMNIbus to IBM Tivoli Monitoring (with the help of Situation Update Forwarder)
Event flow from IBM Tivoli Monitoring to IBM Tivoli Netcool/OMNIbus
Tivoli Netcool/OMNIbus is the main event destination for various event sources. Sources such as IBM Tivoli Monitoring can send alarms they produce to OMNIbus Object Server. This event integration enhances the event management capability of the users.
For the integration of IBM Tivoli Monitoring and OMNIbus, the events that are created in IBM Tivoli Monitoring should be forwarded to the Tivoli Netcool/OMNIbus.
On the Tivoli Netcool/OMNIbus side, the forwarded events are received and processed by Tivoli Netcool/OMNIbus EIF Probe. The probe performs field matching to create new events in the Object Server for the coming IBM Tivoli Monitoring alarms.
To implement the event flow from IBM Tivoli Monitoring to IBM Tivoli Netcool/OMNIbus, use the following steps:
•Configure the IBM Tivoli Monitoring to forward events.
•Install and configure the Tivoli Netcool/OMNIbus EIF Probe to receive and process the events.
Configuring Tivoli Enterprise Monitoring Server is located at the following address:
Configuring the Tivoli Netcool/OMNIbus EIF Probe is located at the following address:
Event updates flow from IBM Tivoli Netcool/OMNIbus to IBM Tivoli Monitoring
When the alarms in Tivoli Enterprise Monitoring Server are sent to IBM Tivoli Netcool/OMNIbus, the operators can check and work on them by using Tivoli Netcool/OMNIbus Web GUI product. They can use the tools in the Alerts menu on the console to operate on those alarms. To send updates on events back to the IBM Tivoli Monitoring, you need the Situation Update Forwarder (SUF) tool.
SUF is included with the IBM Tivoli Monitoring 6.2.2 Tools package and must be installed on the server where Tivoli Netcool/OMNIbus resides.
During implementation of the SUF, Tivoli Netcool/OMNIbus EIF Probe and Object Server components are updated with the SQL and rules files from the installation package of SUF.
To update Object Server to create the required fields, triggers, and procedures, run the SQL files that are included with the SUF package.
To configure the Tivoli Netcool/OMNIbus EIF Probe to collect and match correct information, update the rules file with the one that is included with the SUF installation package.
Installation and configuration details are at the following address:
11.5.3 Event flow check
After implementing the bidirectional integration of IBM Tivoli Monitoring and Tivoli Netcool/OMNIbus, a good practice is to check the event and data flow between them before implementing the launch-in-context integration of Tivoli Netcool/OMNIbus Web GUI and Tivoli Enterprise Portal console of IBM Tivoli Monitoring.
Perform the following steps:
1. Open the Tivoli Enterprise Portal console of IBM Tivoli Monitoring to see whether agents are collecting alarms or not, as shown in Figure 11-2.
Figure 11-2 Events listed in Tivoli Enterprise Portal console of IBM Tivoli Monitoring
2. If you have correctly configured the IBM Tivoli Monitoring to forward alarms to Tivoli Netcool/OMNIbus EIF Probe, and Tivoli Netcool/OMNIbus EIF Probe to process the incoming alarms, you see the events in Tivoli Netcool/OMNIbus Web GUI also.
Figure 11-3 Events from IBM Tivoli Monitoring are listed in Tivoli Netcool/OMNIbus Web GUI
To apply the script that is described in this scenario, the Node and ITMHostname fields must be populated with the correct information. To do make sure the fields are correct, apply the Situation Update Forwarder configuration steps as described in 11.5.2, “Event integration” on page 307. The important step is to run the SQL files of the SUF package correctly and replace the tivoli_eif.rules file of the probe with the one that is included with the SUF package, and run the probe with the new rules file. The EIF Probe working with the updated rule file is able to populate the Node and ITMHostname fields correctly.
You can check the information details of an event by double-clicking it. Check the information in the Node and ITMHostname fields. Node is the name of the managed system affected by the event. ITMHostname is the host name of the Hub TEMS (Figure 11-4 on page 311).
Figure 11-4 Information Details of an event in Web GUI
11.5.4 Implementing launch-in-context integration between user consoles
In this scenario, we implement launch-in-context integration of Tivoli Netcool/OMNIbus Web GUI and Tivoli Enterprise Portal console of IBM Tivoli Monitoring. In 11.5.1, “Product installations” on page 305 and 11.5.2, “Event integration” on page 307 we have described the basic steps including installation, configuration and event synchronization of the products. In this topic, the main purpose of the scenario will be described.
In Tivoli Enterprise Portal console, all monitored systems have workspaces. Operators can see detailed information for the alarms that occurred with the help of available charts and data configurations. However, Tivoli Netcool/OMNIbus stores only the event data sent by the source; sometimes, to diagnose a problem, operators must launch the Tivoli Enterprise Portal console to see more details related to the event.
By using launch-in-context integration between IBM Tivoli Netcool/OMNIbus Web GUI and IBM Tivoli Monitoring Tivoli Enterprise Portal console, you can launch into the Tivoli Enterprise Portal console in context of the managed system that is affected by the event. This new option is added to the Alerts menu that the operator can use from Tivoli Netcool/OMNIbus Web GUI console to open the workspace that is associated with the managed system name of the event in IBM Tivoli Monitoring Tivoli Enterprise Portal console. The integration increases the ease of use of the monitoring products for the operators.
To implement the launch-in-context integration of consoles, perform the following steps:
1. Log in to the Tivoli Netcool/OMNIbus WebGUI console as a user that has ncw_admin role.
You may check the user and role management of the Web GUI at the following address:
2. In the left navigation menu, click Administration → Event Management Tools → Tool Creation (Figure 11-5).
Figure 11-5 Tool Creation page at WebGUI console
|
Note: If you do not see this page at the left navigation menu, check the roles of the user you have logged in with.
|
Figure 11-6 Adding new Script Tool for launch-in-context integration of the console
4. Select type Script and enter a meaningful name such as Open_TEP.
5. For the Script Commands area, use the script that is suitable for your environment, single or multiple Tivoli Enterprise Portal Server:
– Single Tivoli Enterprise Portal Server
If you have a single Tivoli Enterprise Portal Server in the environment and Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server components of IBM Tivoli Monitoring are running on the same server, add the script command that is shown in Example 11-1.
|
Important: In the examples, we use HTTP and port number 1920. If, in your environment, you use HTTPS and a different port number, you must customize the scripts to reflect that environment.
|
Example 11-1 Single Tivoli Enterprise Portal Server: TEPS and TEMS on the same server
var strsystem={@Node};
var ustrsystem = strsystem.replace(/'/g, "");
var strtems={@ITMHostname};
var ustrtems = strtems.replace(/'/g, "");
window.open("http://"+ ustrtems+":1920///cnp/kdh/lib/cnp.html?managed_system_name=" +ustrsystem);
If you have single Tivoli Enterprise Portal Server in the environment, but Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server components of IBM Tivoli Monitoring are running on separate servers, add the script command, shown in Example 11-2.
Example 11-2 Single Tivoli Enterprise Portal Server: TEPS and TEMS on separate servers
var strsystem={@Node};
var ustrsystem = strsystem.replace(/'/g, "");
window.open("http://ithilien.tivlab.austin.ibm.com:1920///cnp/kdh/lib/cnp.html?managed_system_name=" +ustrsystem);
In the script, <tep_host > is the IP address or the host name of the system where IBM Tivoli Monitoring Tivoli Enterprise Portal Server is running.
|
Important: In IBM Tivoli Monitoring 6.2.2 FP1, IBM Tivoli Monitoring added the capability to send private situation events directly from an agent to IBM Tivoli Netcool/OMNIbus. For these types of events, you cannot launch back to the Tivoli Enterprise Portal because the Tivoli Enterprise Portal might have no knowledge of the agent (for example, the agent might be autonomous and not connected to a Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server). To ignore events from an agent for launch-in-context, the script command would need to check the @ITMApplLabel OMNIbus variable (which only exists if you are using Tivoli Monitoring 6.2.2 FP1 or later) and skip the launch-in-context if this label is set to "A:P:S" or "A:P:L".
|
– Multiple Tivoli Enterprise Portal Servers
If you have multiple Tivoli Enterprise Portal Servers in the environment that is connected to separate Tivoli Enterprise Monitoring Server, add the script commands, shown in Example 11-3.
|
Important: In the example, we use HTTP and port number 1920. If, in your environment, you use HTTPS and a different port number, you must customize the scripts to reflect that environment.
Also, make sure that all monitoring servers are sending the alarms to the same Object Server.
|
Example 11-3 Multiple Tivoli Enterprise Portal Server servers
var strsystem={@Node};
var ustrsystem = strsystem.replace(/'/g, "");
var strtems={@ITMHostname};
if( strtems == "reg-10.tivlab.austin.ibm.com" )
{ window.open("http://ithilien.tivlab.austin.ibm.com:1920///cnp/kdh/lib/cnp.html?managed_system_name=" +ustrsystem);}
else if( strtems == "nc185071.tivlab.austin.ibm.com")
{ window.open("http://nc185071.tivlab.austin.ibm.com:1920///cnp/kdh/lib/cnp.html?managed_system_name=" +ustrsystem);}
This script uses the following definitions:
<tems_host1> This is the IP address or the host name of the server where first Tivoli Enterprise Monitoring Server exists. Make sure to use the host name or IP address in the @ITMHostname field of the event.
<tep_host1> This is the IP address or the host name of the server where first Tivoli Enterprise Portal Server exists.
<tems_host2> This is the IP address or the host name of the server where second Tivoli Enterprise Monitoring Server exists. Be sure whether host name or IP address is used in @ITMHostname field of the event and use the same.
<tep_host2> This is the IP address or the host name of the server where the second Tivoli Enterprise Portal Server exists.
6. After writing the script command that matches your environment, click Save to save the new tool (Figure 11-7).
Figure 11-7 Script to open Tivoli Enterprise Portal console from WebGUI of Tivoli Netcool/OMNIbus
7. In the left navigation menu, click Administration → Event Management Tools → Menu Configuration. See Figure 11-8.
Figure 11-8 Menu Configuration page of Web GUI
8. Add the newly created Open_TEP tool in the Alerts menu as a new option. At the Available menus table, you see that the tool lists that were created before. Select Alerts and click Modify to update it. See Figure 11-9 on page 317.
Figure 11-9 Update alerts menu to add new tool as new option
9. The available tools are listed in the table on the left. Select the Open_TEP tool and click the right arrow button to add it to the list at the right.
10. The tools that are listed in the table on the right are options that will be available when a user right-clicks an event in Active Event Lists. After adding the new tool to the Alerts menu, click Save to save it. See Figure 11-10 on page 318.
Figure 11-10 Adding new tool Open_TEP to Alerts menu
By following these steps, a new tool with the name Open_TEP is created and added in the Alerts menu as an option. By using this new option, users can use the launch-in-context integration easily by just selecting this new tool from the options list.
The launch-in-context integration of the consoles will be shown in detail in the following sections.
11.5.5 Single sign-on option for the products
Both Tivoli Netcool/OMNIbus WebGUI and IBM Tivoli Monitoring Tivoli Enterprise Portal console run on Tivoli Integrated Portal. You can configure both consoles to authenticate users from an external LDAP repository.
If you do this configuration and add the single sign-on (SSO) capability between both servers (WebGUI of IBM Tivoli Netcool/OMNIbus and Tivoli Enterprise Portal console of IBM Tivoli Monitoring), you can open and work on both consoles with same user credentials (authenticated by LDAP server). You do not need to log in separately to each console.
If you do not enable SSO option for the consoles, you must log in to each server with authorized local users.
To configure Tivoli Enterprise Portal console for the SSO option, go to the following address:
The LDAP configuration of Tivoli Enterprise Portal console is also defined in section 4.7 of Integrating Tivoli Products, SG24-7757.
To configure the WebGUI console for single sign-on option, go to the following address:
The LDAP configuration of IBM Tivoli Netcool/OMNIbus console is also defined in section 4.6 of Integrating Tivoli Products, SG24-7757.
The Single Sign-On implementation of the user console is also defined in section 4.3.2 of Integrating Tivoli Products, SG24-7757.
11.6 Scenario walk-through
In this section, we demonstrate how this integration works in a typical real-life scenario.
To use the launch-in-context solution for both consoles, perform the following steps:
1. Log in to WebGUI console of Tivoli Netcool/OMNIbus, open an Active Event List, select an event and right-click it to see the options in Alerts menu. (Figure 11-11).
Figure 11-11 Using created tool to open Tivoli Enterprise Portal console for selected event
You see the newly created Open_TEP script tool in the list.
2. Select the Open_TEP from the list. A window opens showing the Tivoli Enterprise Portal address of the managed system name (Figure 11-12).
Figure 11-12 Workspace in Tivoli Enterprise Portal for system related to event in IBM Tivoli Netcool/OMNIbus
3. If you have not configured the single sign-on capability between both consoles, log in to the opened Tivoli Enterprise Portal console as an authorized user. Before the Tivoli Enterprise Portal console opens, a window opens, as shown in Figure 11-13.
Figure 11-13 Log in to Tivoli Enterprise Portal console if SSO is not enabled
11.7 Summary
Figure 11-14 shows the quick summary of this integration.
Figure 11-14 Quick summary
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.