If only specific Systemwalker Operation Manager subsystems, queues and projects are to be analyzed or under a cluster system, prepare the definition file referred to below.
Also prepare this definition file if Systemwalker Operation Manager is not running at the moment but will be running at some time in the future.
Point
By using this definition file to restrict the subsystems, projects and queues that will be analyzed, the amount of data stored in the PDB can be kept down and the load on the management server can also be reduced.
Note
If this definition file is set up, data that is not related to the subsystems, queues and projects that have been specified will not be stored in the PDB.
If this definition file is not set up, all the subsystems, queues and projects specified by Systemwalker Operation Manager will be subject to analysis.
For this reason there is no need to set up this definition file if the subsystems, queues and projects are not to be filtered in any way.
This definition file does not exist at installation time.
If a server is subject to monitoring but is not running for some reason (Systemwalker Operation Manager is stopped or on standby, etc.), it will not be possible to obtain information about subsystem names, project names and queue names, and this definition file should be set up.
If it is not set up, it will not be possible to collect correct data when Systemwalker Operation Manager restarts.
Definition location
The definition file is a text file. Use a text editor, such as Notepad, to create and edit this file. The path to the file is as follows:
[Windows]
<Variable file storage directory>\control\jla.ini |
[UNIX]
/opt/FJSVssqc/control/jla.ini |
Format
[subsystem] subsystem = LL [project] subsystemMM = project_name [queue] subsystemNN = queue_name |
Explanation
This section indicates the start of the definition block of a subsystem that will be subject to collection.
Use the following definition statement to specify the target subsystem:
subsystem = LL |
LL: A two-digit integer between 00 and 09. It specifies the number of a target subsystem.
Note
Systemwalker Service Quality Coordinator sets subsystems, queues and projects as resource IDs so that resource IDs can be filtered in the Report view according to the first matching part of the resource ID. To ensure that subsystem numbers are unique, they are represented using a two-digit integer. If Systemwalker Operation Manager subsystems use one-digit numbers, add a zero to the beginning of each number and read them as two-digit numbers.
Example: Change "2" to "02"
To specify more than one subsystem, enter the relevant settings on multiple lines.
Lines that do not have the "LL" component are ignored.
If there are no definition statements in this block and this section is omitted, all subsystems will be analyzed.
Indicates the beginning of a definition block of the target project. It also indicates the end of the previous definition block.
Projects to be analyzed are specified using the following definition statement:
subsystemMM = project_name |
MM: Here, 00 to 99 is a two-digit integer that specifies the subsystem number of the target project.
project_name: Specifies the name of a single target project.
Note
Multiple projects and subsystems can be specified in the same way over multiple lines.
Lines that do not have a project_name component are ignored.
For subsystems that are not specified within the [project] section, all projects within those subsystems will be subject to analysis.
No problems will arise if the same specification is entered more than once.
This block can be omitted if there are no definition statements contained within it.
If characters that are not permitted by Systemwalker Service Quality Coordinator (\ : < > " , $ ' [ ] & =) are used as part of a project name, those characters will be converted to hexadecimal format before being displayed, as follows:
"|hexadecimal code of forbidden character|" |
Example
"&" -> "|26|" |
Indicates the beginning of a definition block of the target queue. It also indicates the end of the previous definition block.
Queues to be analyzed are specified using the following definition statement:
subsystemNN = queue_name |
NN: Here, 00 to 99 is a two-digit integer that specifies the subsystem number of the target queue.
queue_name: Specifies the name of a single target queue.
Note
Multiple queues and subsystems can be specified in the same way over multiple lines
Lines that do not have a queue_name component are ignored.
For subsystems that are not specified within the [queue] section, all queues within those subsystems will be subject to analysis.
No problems will arise if the same specification is entered more than once.
This block can be omitted if there are no definition statements contained within it.
[subsystem], [project] and [queue] blocks can be specified in any order.
Lines that begin with a hash character (#) are treated as comments and ignored.
Sample definition
The following is an example of a definition:
[subsystem] subsystem = 00 subsystem = 01 [project] subsystem00 = eigyo subsystem00 = keiri subsystem01 = soumu [queue] subsystem00 = queue0 subsystem00 = queue1 subsystem01 = queue0 subsystem01 = queue1 |
Performing cluster system operation
In the case of an active/standby server configuration:
Use the same settings in the definition file on both the active and standby servers.
In the case of a mutual standby server configuration:
Set up definition files that contain the subsystems, projects and queues that are to be analyzed on both servers.
The same settings should be specified in both definition files.
