But one can choose to show the average delivery time of one system hosting one or more domino servers as well.

One can create groups of systems to show the avg delivery time of an OU.

Maybe useful in case of issues in certain subnets or with certain configurations.

Starting with 5.61 (or 5.60 patch 01) and after making some necessary changes for the following defect (documented in release notes):

“NOTES_SPI_METRIC does not handle multiple partitions out of the box (ID:  3703)”, the report uses each partition as sample. Before solving this defect, only the first partition on a system was used as sample.

Note: You will still not see the domino hierarchical name in this report but the host name only.

Applicable for all Domino SPI Versions

The SPI Data Collector needs to be deployed to the Domino Server in order to store the Domino SPI performance data (see “Getting the SPI Data Collector to the Domino Server is a bit different in every environment”)

To start Domino SPI performance data collection run the tools from Domino SPI tool group “Performance” and afterwards deploy collection policies:

• Execute tool “Report Data Setup”
• Execute tool “Report Data Store Start”
• Deploy policy group “Domino Report Data Collection”

At least one full day needs to go by before enough data is collected to fill the reports.

Once a day the performance data stores are gathered by the Reporter system which afterwards generates the reports based on the performance data.

Getting the SPI Data Collector to the Domino Server is a bit different in every environment:

In HP OMW environments SPI Data Collector is automatically installed by the SPI DVD. It is listed in the instrumentation and should be deployed to the Domino servers together with the Domino SPI instrumentation.

In HP OMU 8 environments DSI2DDF needs to be installed explicitely from SPI DVD and is deployed together with Domino SPI templates, actions, cmds and monitors.

In HP OMU 9 environments SPI Data Collector is installed automatically by the SPI DVD. It is listed in the categories as “SPIDataCollector”and should be assigned to the Domino servers along with the Domino SPI category (contains policies) and either DominoSPI-Native or DominoSPI-3264 (containing the correct instrumentation for either native Domino servers or Domino Servers with mixed bitness). All assigned categories may then be sent to the Domino Server with the command “Deploy configuration”.

Applicable for all Domino SPI Versions 6.0x.

The SPI Data Collector needs to be deployed to the Domino Server in order to store the Domino SPI performance data (see “Getting the SPI Data Collector to the Domino Server is a bit different in every environment”)

To execute Domino SPI performance data collection run the tools from Domino SPI tool group “Performance”:

• Run Availability Collection
• Run DB Collection
• Run SMTP Collection
• Run Stat Collection
• Run Web Availability Collection

Or deploy the policy group “Report Data Collection” for a scheduled execution of performance data collection.

At least one full day needs to go by before enough data is collected to fill the reports.

Once a day the performance data stores are gathered by the Reporter system which afterwards generates the reports based on the performance data.

Getting the SPI Data Collector to the Domino Server is a bit different in every environment:

In HP OMW environments SPI Data Collector is automatically installed by the SPI DVD. It is listed in the instrumentation and should be deployed to the Domino servers together with the Domino SPI instrumentation.

In HP OMU 8 environments DSI2DDF needs to be installed explicitely from SPI DVD and is deployed together with Domino SPI templates, actions, cmds and monitors.

In HP OMU 9 environments SPI Data Collector is installed automatically by the SPI DVD. It is listed in the categories as “SPIDataCollector”and should be assigned to the Domino servers along with the Domino SPI category (contains policies) and either DominoSPI-Native or DominoSPI-3264 (containing the correct instrumentation for either native Domino servers or Domino Servers with mixed bitness). All assigned categories may then be sent to the Domino Server with the command “Deploy configuration”.

Applicable for all Domino SPI Versions 5.5x and 5.6x.

Applicable for all Domino SPI Versions 5.5x and 5.6x.

OMU 8 detects the bitness of the Windows platform, which is 64bit and logically deploys 64bit binaries. But since this is a 32bit Domino Server application the 32bit binaries are required. There is a workaround described in the Lotus Domino SPI Release Notes and Admin Guide.

To make a long story short, the workaround requires copying the 32bit binaries from

/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/x86/winnt/cmds and monitors

to the Domino server’s instrumentation directory.

This is a fundamental issue with OMU 8 which has been solved for OMW, OMU 9 and OML 9.

Applicable for all Domino SPI Versions 5.5x and 5.6x.

Send this information to SPI support along with a detailed description or the problem that you are experiencing.

Domino Server

1. 1. Domino version and bitness (Registry)
   2. Domino SPI AddIn task version (C:\Lotus\Domino\nwcstat -v)
   3. Operating System version and bitness (uname -a, My Computer-View System Information)
   4. HP OM agent version and type (opcagt -type -verbose)
   5. nwcstat.log
   6. npi.log

HP OM Management Server

1. 1. Lotus Domino SPI version (swlist, pkginfo -l, rpm -qa, “Add / Remove Programs”)
   2. HP OM Manangement Server version (swlist, vpstat -9)
   3. Operating System version and bitness (uname -a, My Computer-View System Information)
   4. SPI Data Collector version (DSI2DDF, version) (swlist, vpstat -9)

Applicable for all Domino SPI Versions

Warning messages from AT policies may be safely ignored for one day after deployment of the policies. Lotus Domino SPI CODA data sources are created by scheduled task policies/templates and are not immediately available for the AT policies when executed right after policy deployment.

To avoid this issue and to ensure that the AT policies have enough performance data to work with, deploy the AT policies at least two weeks after the performance data collection has been started.

Applicable for all Domino SPI Versions

All Lotus Domino SPI policies should be disabled during maintenance when the Domino SPI AddIn task or the Domino server is not running for a particular reason. In the same way, the AddIn has to be running for all servers or partitions which are to be monitored by the Lotus Domino SPI policies.

Otherwise the Domino SPI monitoring policies will complain vocally about missing resources which is true, but inevitable during maintenance.

To avoid these irritating messages, disable all Domino SPI 5.xx policies before stopping the AddIn or the Domino server by purpose. The same issue arises with Lotus Domino SPI 6.00, even if it has no AddIn. When the Domino Server is stopped by purpose, all Domino SPI policies should be disabled as well.

If you are unsure how to go about doing it, consult HP documentation to see how certain policies/templates can be disabled.

Applicable for all Domino SPI Versions.

The new files can be downloaded via the NiCE Customer Portal.

For details please check the Support Matrix as well as the Whitepaper, both available via the Portal.
You may also request a copy at products@nice.de.