Integrating Content Manager in a Tivoli Environment

 

Overview

IBM® Content Manager™ for Multiplatforms Version 82 is Tivoli-Ready for event log adapter monitoring. These resource models have been created so that you can monitor the status of Content Manager components from a Tivoli Event Console.By reporting this information, the administrator can then determine whether or not an action needs to be taken.
When Content Manager Library Server or Resource Manager starts or fails, an event will be generated and an the event forwarded to the Enterprise Console's event server.  New to CMv82 fixpack7, the Content Manager Library Server Monitor now logs detail status on each Resource Manager.   This new functions allows you to quickly determine whether a Resource Manager is AVAILBLE or UNAVAILABLE.  The administrator will be able to determine when a component has stopped by checking its status on the Tivoli Event Console.
The Content Manager log files that will be monitored on UNIX and Windows include the following:

UNIX/Windows

Logfile
Description
ICMSERVER.LOG
Library Server 
icmrm.logfile
Resource Manager Servlet
icmrm.migrator.logfile
Resource Manager Migrator
icmrm.stager.logfile
Resource Manager Stager 
icmrm.destager.logfile
Resource Manager Destager

Prerequisite

These instructions assume that the administrator has had experience working in a Tivoli environment and is familiar with the Tivoli products Framework and Tivoli Event Console.Before beginning, the following products need to be installed and functioning within the network.

Installation

The integration of Content Manager into a Tivoli environment can be achieved by performing the following instructions. Please do not skip through any steps, the order in which they are performed is important in getting the entire setup to work.
  1. Locating the adapter files on the Content Manager CD. The adapter files can be found in the /Tivoli directory on the Content Manager CD
File
Description
icm.baroc
Content Manager BAROC file
tecad_icm.fmt
Content Manager format file
tecad_icm.conf
Content Manager configuration file
  1. Add the contents of the adapter files tecad_icm.fmt and tecad_icm.conf to the format and configuration files located on the Tivoli management region server or managed node/gateway.On Windows this would be the tecad_win.fmt and tecad_win.conf files respectively. On UNIX, this would be he tecad_logfile.fmt and tecad_logfile.fmt.
  1. Rebuild the *cds file

    2. On Windows, you would need to stop the log Adapater, generate the cds file (e.g. tecad_win.cds), then start the log Adapter.
  1. Create/Configure the ICM Rule Base on the Event Server (see Tivoli Event Console Rule builder guide)
  1. Creating a rule base. Open up the TME Desktop and click on EventServer. This will open up a window showing the Event Server Rule Bases. Click on Create from the menu bar and select Rule Base… A window will pop up. Insert a name (i.e. ICM_Base_SQLError, ICM_BASE_RMError) and directory (i.e. C:\Tivoli). Push Create & Close.
  1. Configuring the rule base. Right-click on the Default rule base and select Copy… Select the rule base you have just created (i.e. ICM_Base_....) and put a check mark for Copy rules and Copy classes. Close the window.
Right-click on your rule base and select Import…You will now be adding the BAROC files into your rule base.For convenience, we will go ahead and add the BAROC file for both AIX and Windows.If you look under Position to insert imported class file, you will see a list of BAROC files already defined in this rule base.You will need to import the following file so that it appears on the bottom of the list:
ICM.baroc
If these files are not in this order, you will receive an error when you compile the rule base.

To import these files, check the Import Class Definitions option.Under the Directory Path, click file and locate the icm.baroc file.In the bottom section, click Insert After and highlight the last *.baroc file in the list.Hit the Import button.This will place the icm.baroc file at the very end. When completed, hit Import & Close.

  1. Compiling the Rule Base. Right-click on the rule base you have created and select Compile… When the window pops up, select Compile. Be sure that there are no errors in the compiler output.
  1. Loading the Rule Base. Right-click on the rule base you have created and select Load… When the window pops up, put a check mark for Load and activate the rule base and hit Load & Close.
  1. Restarting the Tivoli Event Console. Open up a bash shell. Shutdown and restart the Tivoli Event Console (TEC).
wstopesvr- stops the TEC
wstartesvr - restarts the TEC
wstatesvr- displays the status of the event server
wrb –lscurrb- shows that the new rule base has been loaded
  1. Configuring Management Region. By completing Step 2, the ICM resource model should have been added to existing regions in the Tivoli environment. Right-click on your managed region and select Managed Resources. In the field under Current Resources, you should see a list of resources that includes icmProfile. If not, select the item from the list of Available Resources and add it by pushing the left arrow button. Hit Set & Close.
  1. Creating Profiles. If you already have a Distributed Monitoring Profile, jump to the next step. Double click on your region in the Tivoli Desktop and open up one of your defined policy regions. Go to Create on the menu bar and select Profile… A window will open up. Insert a name and highlight the icmProfile type. Hit Create & Close.
  1. Configuring Profiles. Open up your profile in Profile Manager. Insert a profile name. Click on Add with Defaults… located at the bottom of the panel.
If this is a Windows profile, select Windows from the Category pull-down menu.In the list of resource models, select VCProcess.Hit Add & Close.Back in the Distributed Monitoring Profile window, go to Edit on the menu bar and select Properties…In the window that pops up, put a check beside Send TEC Events.Select TME (Secure) delivery and choose EventServer from the pull-down menu when asked to choose a TEC Server.Click OK and select Close in the Distributed Monitoring Profile window.
If this is an AIX profile, select UNIX - LINUX from the Category pull-down menu.In the list of resource models, select DMXVCProcess.Hit Add & Close.Back in the Distributed Monitoring Profile window, go to Edit on the menu bar and select Properties…In the window that pops up, put a check beside Send TEC Events.Select TME (Secure) delivery and choose EventServer from the pull-down menu when asked to choose a TEC Server.Click OK and select Close in the Distributed Monitoring Profile window.
  1. Distributing Profile. From the Profile Manager window, click on the profile you have just modified and select the endpoint containing the VideoCharger server. Go to Profile Manager on the menu bar and select Distribute… Select Distribute Now to send the profile to you endpoint.
  1. Checking Profile. You can check whether or not the profile was distributed successfully to the endpoint by running the following command from a bash shell.
wdmlseng –e <endpoint>
If the results show that the profile is currently stopped, start up the engine with this follow up command:
wdmeng –e <endpoint> -p <profile#region> -start

Testing the Installation

    1. Check that Systems are Up and Running. Start up the Tivoli Event Console (TEC) and the Content Manager Resource Manager Websphere application and associated resources.
    1. Pull Up the Appropriate Views.
TEC: Go into the Event Viewer so that you can monitor events in detail.
Content Manager:  Bring up the Content Manager Windows application. Logon and view data.
 
    1. Stop the Content Manager Resource Websphere application. Use either the WebSphere Administrator console or the Command line interface.
    1. Observe the results. Depending on the refresh rate that you may have set for the TEC  each logfile will begin to report that the server has been stopped. If you do see anything after a while, select Retrieve Events in the TEC Event Viewer.