![]() |
![]() |
This section contains updated information and new items that will be inserted into the product documentation in the next release.
The following table shows two new naming conventions for the server types
that Tivoli Manager for Domino implements and briefly describes all server
types:
Table 5. Server Types in Tivoli Manager for Domino
Original Name | New Name | Description of Server Type |
---|---|---|
Mail server | Mail Database server | Hosts user mail databases. |
Mail Router server | -- | Routes mail between servers. |
Database server | Application server | Hosts Lotus Notes database applications. |
Web server | -- | Hosts Web services. |
News server | -- | Hosts news group services. |
The new naming conventions ("Mail Database server" and "Application server") must be applied to following sections of the documentation:
Location: Chapter 4, Setting Up Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide and in the management console help
Location: Chapter 5, Working with Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide and in the management console help
Location: Chapter 6, Setting Up Monitoring, of the Tivoli Manager for Domino User's Guide
Location: Chapter 7, Domino Server Commands, of the Tivoli Manager for Domino Reference Guide and in the ASCII-based help for the command line interface
The following information supplements Chapter 1, Overview, of the Tivoli Manager for Domino User's Guide in Authorization Roles:
The following administrator roles are the minimum requirements for logging
onto the management console:
Table 6. Authorization Roles for Management Console
Role | Level |
---|---|
User | Tivoli management region |
Domino_User | Manager For Domino 3.1 policy region |
To work with Distributed Monitoring profiles, an administrator must have either an admin, senior, or super role for the policy region that contains the profile manager of the Distributed Monitoring profile. At least one administrator must have one of the listed roles for the Manager For Domino 3.1 policy region to work with the default set of profile managers and profiles.
By default, the management console displays all objects associated with Tivoli Manager for Domino. Depending on an administrator's assigned roles, an administrator may or may not be able to interact with the displayed objects. Any attempt to operate with an object for which the required Tivoli management region role has not been assigned results in an error message stating that the administrator does not have sufficient roles to perform the operation.
The following information supplements Chapter 1, Overview, of the Tivoli Manager for Domino User's Guide in User Interface Options:
Each of the tabs in the management console contains one or more methods for refreshing the data displayed in that tab. Each table contains a Refresh button in the action bar above the table. This button refreshes the data in the table.
The selection trees along the left side of the tabbed views contain a right-click Refresh menu option that forces the contents of the tree data to refresh. The refresh option for the server trees in the Status and Operations, Backup, Restore, and Activate views invoke the refresh option for the Server Configuration table. When you use this refresh option in any of these server trees or in the Server Configuration table, all these components refresh.
The following information supplements Chapter 3, Installing Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide in Preparing for Installation:
The following information supplements Chapter 3, Installing Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide in Creating the Database and the RIM Object:
When you run the tmd_cr_db.sh script that creates the Tivoli Manager for Domino RIM database, you might see a warning message from the RDBMS application that says the user name for the RIM database was not created. In this case, the database and its tables are created, but not the user name. This warning appears when you run the script and specify a user name that already exists in the RDBMS application.
The following information supplements Chapter 5, Working with Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide:
The Status and Operations view displays a status icon for the monitors on each Domino server. The data from the Server Availability monitor updates the status icon every time this monitor runs. By default the monitor runs every five minutes.
The management console checks the monitor status on a Domino server regularly. The console also checks the timestamp of the latest monitor status update that the Server Availability monitor has triggered. If the timestamp is over 15 minutes old, the monitor status icon becomes a yellow warning triangle, indicating possible problems with the Domino server. When you use the Refresh command to refresh the console display or click on a server to display its list of monitors, the yellow warning triangle is displayed immediately if problems exist.
The following information supplements Chapter 6, Setting Up Monitors, of the Tivoli Manager for Domino User's Guide in the Overview section:
All of the monitors for each profile manager that are associated with a particular server work together to provide a complete set of monitors for that defined server's role. This customized set of monitors is important when you are managing real-time servers. All of the real-time monitors from the real-time profiles run on a single schedule that you define in the Real Time profile. The Real Time profile is located in the Basic profile manager that corresponds to the version of Domino that the server runs (the Domino 5.0 Basic Server profile manager or Domino 4.6 Basic Server profile manager). When you add or work with real-time monitors, make sure you schedule only one monitor and, at most, one instance of any unique real-time monitor located in any of the combined sets of profiles that are associated with a server. See the first bulleted item in the following note for an explanation of a unique real-time monitor.
Consider the following key points as you work with real-time monitors:
This section contains updated information and new items regarding Domino Performance Stations. The items in this section supplement Chapter 8, Working with Domino Performance Stations, of the Tivoli Manager for Domino User's Guide, with one exception. The last item in this section supplements Appendix G, Troubleshooting, of the Tivoli Manager for Domino User's Guide.
Do not configure (create) a Domino Performance Station on an endpoint that you already have configured with a Domino Performance Station or with a Lotus Domino Server object. Such a configuration can generate invalid performance data and can cause resource conflicts and contention.
To manage Domino Performance Stations in the management console, you must leave station objects in their original policy regions. Also, you must leave profiles for station objects in their original Domino Performance Station Monitors profile manager.
To access Domino Performance Station functionality, users must have the following roles either globally or in the Manager for Domino 3.1 policy region:
After you add or edit a probe in the management console, click Reset All Probes to activate the changes. This action is equivalent to distributing the station's monitoring profile from the Tivoli desktop or using wdistrib in the command line interface.
The following information supplements Appendix G, Troubleshooting, of the Tivoli Manager for Domino User's Guide:
Domino Performance Station endpoints on which other Java-based applications are running occasionally produce contention problems because the station controller relies on a dedicated Java run-time instance. You can avoid this problem by disabling all other Java-based applications or services running on the system that is host for the performance station.
In versions of the Lotus Notes R5 client earlier than release 5.0.3b, the station controller can occasionally terminate unexpectedly with a pop-up message indicating a Java memory access violation. To avoid this error, periodically restart the Domino Performance Station object using a Tivoli scheduled job or upgrade the Lotus Notes client to version 5.0.3b or later.
This section contains updated information and new items regarding use of the Reports tab of the management console. The items in this section supplement Chapter 9, Graphing and Reporting, of the Tivoli Manager for Domino User's Guide.
The tmd_cr_db.sh script that you run to create the tmd database also adds several report templates for tables and graphs. Creating the Database and the RIM Object in Chapter 3 of Tivoli Manager for Domino User's Guide describes how to run this script. After you run the script, you access the templates in the tree view on the left side of the console in the Reports tab.
Consider the following points regarding the use of report templates:
A Refresh button was added to the action bar of the Reports tab for refreshing the report definition tree. Report definitions are shared by all Tivoli Manager for Domino users and might be updated frequently. The Refresh button on the Reports tab of the management console has the following effects:
The Probe selection dialog box now contains an Async Attribute option to permit reporting of a specific asynchronous attribute (monitor) from a sync/async monitor group.
To access report generation functionality, users must have the following roles either globally or in the Manager for Domino 3.1 policy region:
When you access the Probe selection dialog box (for both graphs and tables) and you select a monitor (probe) to be reported on, a percent sign (%) might appear in the formatted monitor argument value. This symbol represents a wildcard character that allows the report to return data that matches a pattern instead of returning static text. For asynchronous and sync/async monitor types, the first argument (channel identifier) is almost always a wildcard character indicating that data should be returned for all monitor values, regardless of the channel identifier. To view data for a specific monitor instance, modify this value by replacing the wildcard with the channel name that appears in the Status and Operations view of the management console.
This section contains updated information and new items about configuring Tivoli Enterprise Console to work with Tivoli Manager for Domino. The items in this section supplement Appendix E, Setting Up the Tivoli Enterprise Console, of the Tivoli Manager for Domino User's Guide, with one exception. The last item in this section supplements Appendix G, Troubleshooting, of the Tivoli Manager for Domino User's Guide.
When a Tivoli Enterprise Console is installed on a Domino server managed with Tivoli Manager for Domino, the Tivoli Enterprise Console's rule engine performs all necessary event processing. You never need to start the standalone Tivoli Enterprise Console engine that comes with Tivoli Manager for Domino. If you start the Tivoli Enterprise Console engine that comes with Tivoli Manager for Domino in these circumstances, the two engines might conflict and produce unpredictable results.
Tivoli Manager for Domino can capture Domino-generated events, which Lotus Domino lists in the events4.nsf file, and forward them to the local event correlation engine. Using the rule-building guidelines for the Tivoli Enterprise Console, you can create rules for the local correlation engine to process the events. The local correlation engine implements the following rules by default:
The rule file is called tmd_sa.rls, and the baroc file is called tecad_tmd.baroc.
Use one of the following methods to configure default rules for local event correlation in Tivoli Manager for Domino:
With this method, you set rules for local event correlation on the managed node before you create Domino server objects. Use this method to create rules that apply for all Domino servers.
$install_dir = 'objcall oserv_OID query install_dir'; $install_dir/lcf_bundle/bin/w32-ix86/TME/DominoManager/TEC/rule_base \ /TEC_RULES/tmd_sa.rls $install_dir/lcf_bundle/bin/w32-ix86/TME/DominoManager/TEC/rule_base \ /TEC_CLASSES/tecad_tmd.baroc
With this method, you set rules for local event correlation at the endpoint after you create a Domino server object. Use this method to create rules for a specific Domino server.
$LCF_BINDIR/mrt/TMDTEC/rule_base/TEC_RULES/tmd_sa.rls $LCF_BINDIR/mrt/TMDTEC/rule_base/TEC_CLASSES/tecad_tmd.baroc
$LCF_BINDIR/mrt/TMDTEC
For Solaris:
SHLIB_PATH=./lib:$SHLIB_PATH LIBPATH=./lib:$LIBPATH LD_LIBRARY_PATH=./lib:$LD_LIBRARY_PATH% TEC_BIN_DIR=. TEC_KB_DIR=$TEC_BIN_DIR/rule_base BIM_PROLOG_DIR=$TEC_BIN_DIR INTERP=solaris2
For AIX:
SHLIB_PATH=./lib:$SHLIB_PATH LIBPATH=./lib:$LIBPATH LD_LIBRARY_PATH=./lib:$LD_LIBRARY_PATH% TEC_BIN_DIR=. TEC_KB_DIR=$TEC_BIN_DIR/rule_base BIM_PROLOG_DIR=$TEC_BIN_DIR INTERP=aix4-r1
For Windows NT:
PATH=.;.\lib;.\bin;%PATH% TEC_BIN_DIR=. TEC_KB_DIR=%TEC_BIN_DIR%\rule_base BIM_PROLOG_DIR=%TEC_BIN_DIR% INTERP=w32-ix86
tec_compile_rules [-notrace] rule_base
To configure Tivoli Enterprise Console for Tivoli Manager for Domino, run the Tivoli task Configure TEC for TMD in the Tivoli desktop. You also can use wruntask to run this task in the command line interface. For more information on Configure TEC for TMD, see the Tivoli Manager for Domino Reference Guide.
The following information supplements Appendix G, Troubleshooting, of the Tivoli Manager for Domino User's Guide:
Tivoli: Could not initialize TEC Agent
This message is displayed in the Domino server console or is logged in log.nsf because the standalone Tivoli Enterprise Console engine at the endpoint is not started and you must start it with one of the following methods:
where <object_name> is the name of the server object on which the engine is located.
Tivoli: Could not Send events to TEC. Please make sure TEC is running.
This message is displayed in the Domino server console or is logged in log.nsf because the standalone Tivoli Enterprise Console engine at the endpoint has stopped and cannot send Tivoli Enterprise Console events to the engine. You must start the engine with one of the following methods:
where <object_name> is the name of the server object on which the engine is located.
When the engine starts, the following message is displayed:
Tivoli: TEC is running. Sending events to TEC.
This section contains updated information and new items regarding troubleshooting your system. The items in this section supplement Appendix G, Troubleshooting, of the Tivoli Manager for Domino User's Guide.
Consider the following points when you run the DbSetup scripts that create or remove the database and RIM (RDBMS interface module) object. You run these scripts when you install or uninstall Tivoli Manager for Domino.
Ask the your company's administrator for Tivoli Data Protection to perform the following steps. These actions can resolve problems you might have using Tivoli Data Protection to back up and restore databases in Tivoli Manager for Domino.
When you install the Tivoli management region, you can choose an administrator name other than root or Administrator, the names that Tivoli highly recommends. If you choose a different name, you cannot immediately use standard procedures to configure a Domino Performance Station on an endpoint. Instead, you must first complete the procedure in this section to ensure that the administrator name you created exists on the endpoint with the necessary Windows group assignments.
Additional Information: This action creates the user on the endpoint that enables Domino Performance Station functionality.
The following information supplements Appendix H, Uninstalling Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide:
When you run the tmd_rm_db.sh script to remove the Tivoli Manager for Domino RIM database, you might see a warning message from the RDBMS application. The message states that the user name for the RIM database was not removed. In this case, the database and its tables are removed and only the user name remains. This warning appears when you have created a RIM database with a user name other than the default user name, tmd. Tivoli Manager for Domino does not remove a custom user name because the name might be valid for other databases in your RDBMS. If necessary, you can remove the user name through the user interface of the RDBMS application. See the documentation for your RDBMS application for instructions on this process.