Lexmark Tivoli Event Integration Supplementary Manual Download Page 8

Tivoli Event Integration

December 11, 2002

Tivoli Event Integration

Page 8

Once the installation has completed, the event adapter must be created and configured using
MarkVision Messenger.  The following section shows the steps necessary to configure the Tivoli
Event Adapter in MarkVision Messenger.

2.3 

Using MarkVision Messenger’s Integrated Tivoli Event Adapter

2.3.1 

Overview of MarkVision Messenger

MarkVision Messenger is a tool that provides a mechanism for automating responses to printer
conditions. The heart of MarkVision Messenger is a “service” that runs inside of the MarkVision
Server. To use this service, the user creates “actions” using a browser-based interface, either by
selecting “MarkVision Messenger Launch” from the actions menu, or utilizing the URL. If your
MVP web server is set as the default server on the machine, use

http://<yourserver>/messenger

 within your browser, otherwise you must include the port in the

URL, 

http://<yourserver>:9180/messenger.

  Once an action is created and enabled, the

browser can be closed because the action will be enforced by the messenger service running
inside the MarkVision Server.

An “action” created in MarkVision Messenger contains several key pieces of information. Using
MarkVision Messenger’s intuitive wizard based interface the action is defined according to the
following parameters:

  The printer conditions or folder changes for which the user would like notification

  The printers or folders in which the user is interested

  The function to perform when a printer event occurs

2.3.2 

Creating and Configuring a Tivoli Event Adapter in MarkVision Messenger

Open the MarkVision Messenger browser-based interface, either by selecting “MarkVision
Messenger Launch” from the actions menu in MarkVision Professional, or by utilizing the URL
described in the previous section.

Summary of Contents for Tivoli Event Integration

Page 1: ...Tivoli Event Integration Technology White Paper December 11 2002 Lexmark International Inc 740 New Circle Road Lexington KY 40550...

Page 2: ...of the information you supply in any way it believes appropriate without incurring any obligation to you You can purchase additional copies of publications related to this product by calling 1 800 55...

Page 3: ...Environments 4 2 Tivoli Event Integration 5 2 1 Technical Overview 5 2 1 1 Supported Printers 6 2 1 2 Supported Alerts 6 2 2 Installation 6 2 3 Using MarkVision Messenger s Integrated Tivoli Event Ada...

Page 4: ...ronment TME We have developed a custom event adapter which can feed Lexmark printer generated NPAP alerts into the Tivoli Event Console or T EC as it is more commonly known This custom event adapter h...

Page 5: ...nger converts printer generated NPAP alerts into events that are recognizable by the Tivoli Event Server A new event class MVP_Printer_Alert is derived from Tivoli s base event class so that printer s...

Page 6: ...tion for a list of supported alert conditions Alerts are converted using their severity Errors Warnings into Tivoli s Critical Warning classification 2 2 Installation Lexmark s event integration solut...

Page 7: ...Lexmark s custom event adapter for Tivoli The MarkVision Professional tab will reveal the optional MarkVision Professional components that can be installed Because the custom event adapter for Tivoli...

Page 8: ...ult server on the machine use http yourserver messenger within your browser otherwise you must include the port in the URL http yourserver 9180 messenger Once an action is created and enabled the brow...

Page 9: ...New to create a new action This action will be the basis of the Tivoli Event Adapter On the following screen enter a descriptive name for the new action You may also wish to enter a description and a...

Page 10: ...een where you will choose the type of event to monitor Note The Tivoli Event Adapter included in MarkVision Messenger will be available in a subsequent part of the wizard only if the type of event sel...

Page 11: ...n severity e g only those events that have a severity of Error or you may choose to monitor a set of devices for alerts of a certain type e g Input Alerts Output Alerts or Supplies Alerts To choose wh...

Page 12: ...kVision Server Monitor Devices in a Specified Folder Monitor Selected Devices The titles should be fairly self explanatory but it should be noted that Messenger does not provide a means of adding devi...

Page 13: ...or the MarkVision Web Client If the Monitor Selected Devices radio button is selected the next screen to appear will present a list of all the devices currently on the MarkVision Server From this lis...

Page 14: ...ted directly into Messenger is selected From the list of command types select the command entitled Send Device Status Alerts to a Tivoli Event Server and then click the right arrow icon to continue th...

Page 15: ...ly 0 zero which is the standard port for portmapper The TEC server registers itself with portmapper which then listens for incoming Tivoli socket requests redirecting the requests to the appropriate T...

Page 16: ...ver will accept from Messenger The predefined values from messenger that are included with each Tivoli alert are as follows action name action description action notes event severity event name source...

Page 17: ...ion screen appears as follows On the filter selection screen choose when your action should execute and then click the right arrow icon to finish the setup wizard The final screen will give you a summ...

Page 18: ...ration December 11 2002 Tivoli Event Integration Page 18 If the summary of the action is acceptable select the radio button for Yes and then click the right arrow icon to enable the action for the Tiv...

Page 19: ...Messenger is now configured to redirect device status alerts to a Tivoli Event Server However some additional steps must be performed on the Tivoli Server to complete the installation Refer to section...

Page 20: ...up of the Tivoli Event Adapter a Plus Module must be installed from the TME Desktop This Plus Module contains a task or script which is used to configure the Tivoli Event Server to recognize new types...

Page 21: ...002 Tivoli Event Integration Page 21 Use Select Media to open the File Browser dialog which is described below In this dialog navigate to the appropriate directory on the hard drive where the Plus Mod...

Page 22: ...Page 22 Select MarkVisionPlus Module for Tivoli Version 3 0a and then select Install Close to install the Plus Module as shown below Note The Plus Module Support Link binaries 3 2 d must be installed...

Page 23: ...ion Page 23 Once the MarkVision Plus Module is installed the user can run a script that will setup the Tivoli Event Server to handle Lexmark defined printer events as shown in the following screen cap...

Page 24: ...r_for_Markvision icon a dialog window will appear prompting for the following pieces of information Rule Base Name new or existing Rule Base to clone if new Path for Rule Base if new The value for the...

Page 25: ...e path where the rulebase should be created This can be any valid path but if you wish to create the rulebase in the same location as the default rulebase you will need to enter the following commands...

Page 26: ...n In previous versions the console was integrated directly into the TME Desktop for version 3 7 and later however the T EC became a separate application written in Java Please refer to your Tivoli doc...

Page 27: ...Tivoli Event Integration December 11 2002 Tivoli Event Integration Page 27 Once the filter has been properly configured change to Event Viewer mode by clicking Windows Event Viewer as shown below...

Page 28: ...December 11 2002 Tivoli Event Integration Page 28 In Event Viewer mode a bar graph representation of the MarkVision printer events are then displayed as follows Clicking the bar chart displays the Ma...

Page 29: ...Tivoli Event Integration December 11 2002 Tivoli Event Integration Page 29 A full description can be viewed by highlighting an event then clicking the Details button...

Reviews: