Operations Guide

10.5
- 10.5 HotFix 2
- 10.5 HotFix 1
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Server Statistics

Progress information can be retrieved for the servers, which are themselves jobs started by the Console. See Console Client
below for details about progress information. The slider can be used to slow the refresh rate from once per second (the default) to up to 30 seconds.

Because this has the potential to impact performance, it is not switched on by default. Some environment variables are required to be set in order for this feature to become available.

In the

<MDM Registry Edition Installation Directory>/env/mdmres

script, set the SSA_SERVER_STATS environment variable to YES, and set the SSA_RBNAME environment variable to the rulebase connection string with the rulebase number that you currently use.

For example:

On Windows:

set SSARB_NAME=odb:0:userid/password@service

set SSARB_NAME=iir:rb

On UNIX:

export SSARB_NAME="odb:0:userid/password@service"

export SSARB_NAME="iir:rb"

To keep your password secure, Informatica recommends that you use a Dictionary Alias.

When you start the servers, issue a refresh. The jobs window displays the search server progress information.

If the rulebase has only just been created, first use the console client to stop and restart the servers.

There will be two entries. One will be an overview job whose function is to restart the servers if one fails. It will state how long it has been running and what servers are active. Its logs are often interesting though.

The other will have the progress details of the search servers, if

SSA_SERVER_STATS=YES

. Otherwise it will merely list the individual servers and their start times.

The progress will look something like this:

ssasrsv: server 0:28:14.000
rulebase server: active
clients 4
rulebases 1
status available
search server: active
== Search clients ====
formerly active clients: 6
currently active clients: 1
maximum concurrent clients: 2
minimum duration: 0.000 seconds
maximum duration: 30 minutes 28.979 seconds
total duration: 37 minutes 21.435 seconds
average duration: 320.205 seconds
==== Searches ====
formerly active clients: 53558
currently active clients: 0
maximum concurrent clients: 1
minimum duration: 0.004 seconds
maximum duration: 1.692 seconds
total duration: 3 minutes 58.877 seconds
average duration: 0.004 seconds
==== Name3 clients ====
formerly active clients: 2
currently active clients: 0
maximum concurrent clients: 2
minimum duration: 6 minutes 37.422 seconds
maximum duration: 6 minutes 37.532 seconds
total duration: 13 minutes 14.954 seconds
average duration: 397.477 seconds

A particular job may run a series of searches, some in parallel. The maximum and minimum duration are recorded rather than the average. Generally speaking, a large maximum that continues getting larger indicates a client that has failed to disconnect. It can be seen that a small number of search clients can carry out a large number of searches. The average can be found by dividing the total duration by the total number of searches. Here

Rename Saved Search

Table of Contents

Operations Guide

Operations Guide

Server Statistics

Server Statistics