In this section: |
How to: |
At run time, Resource Management collects usage monitoring data in a log file. At predetermined times, such as during server startup or a user request, the log data collected is archived to a permanent repository. Before collecting the data, Resource Management must be configured.
To configure Resource Management, after the server is installed, you must:
There are two levels of security to consider:
|
|
To enable Resource Management, you must have a valid license key. After typing the key, you can specify the type of repository to be used for Usage Monitoring. The Usage Monitoring tables are then created. This procedure shows how to create Usage Monitoring tables in a FOCUS or relational repository using a license code for Resource Governor.
Before performing the following steps, make sure the server is running.
If you are using an operating system other than Windows, enter
http://ipaddress:port
where:
Identifies the server where Resource Governor is to be configured.
Is the port number for that server.
Note: On the Program Menu under iWay Software, the server types can include iWay Full-Function Server, or iWay DataMigrator Server. On the Program Menu under Information Builders, the server type can include a WebFOCUS Server. Resource Governor can be configured on any of these servers.
The Web Console opens, as shown in the following image.
The Resource Management page opens, as shown in the following image.
The Resource Management Configuration pane opens.
Note: If no certified Resource Management adapter has been configured, the only option in the drop-down menu will be FOCUS.
The current list of certified relational engines is:
The limit on the number of locks has been exceeded for the tablespace within DB2.
If the DDL Only option is used at configuration time, then this parameter can be added to the DDL that is generated otherwise the sites DBA can add it to the existing Resource Management environment.
When No is selected, the configuration process will not issue DROP TABLE, DROP INDEX, CREATE FILE, and CREATE INDEX commands. Because the configuration process will always initialize the repository with default data and issue the default GRANTS, the repository must exist when the commands are executed or the configuration will fail. Yes is the default value.
For more information, see Using DDL Statements to Create the Internal Tables. For more information on Many-to-one, see Configuring Many-to-One Monitoring.
If the tables are to be created in an alternate database that the owner has rights to, and the technique is supported by the RDBMS, the database name must be specified as well (for example, database.owner). Consult the appropriate RDBMS documentation for the appropriate syntax. On the System I platform, the Owner Name will be shown as Library.
Indicates whether Data Request Monitoring is on or off. When Global Data Request Monitoring is enabled, or set to On, Resource Governor collects information on all SQL SELECT and FOCUS TABLE, TABLEF, MATCH, GRAPH, MODIFY, and MAINTAIN requests. The default value is Off. Monitoring will be by individually selected data sources.
Indicates the level of Procedure Request Monitoring. The following options are available:
The Repository Statistics page opens, and the navigation pane on the left appears, as shown in the following image.
You can now select monitoring levels for Resource Governor. For more information, see How to Set Repository Properties.
|
|
In this section: |
Several considerations and steps must be taken in order to configure Resource Management to gather monitor data for multiple servers into a single repository. This feature can only be done using relational adapters. Access must be available from each server machine to the selected relational engine and a license will be needed for each individual adapter.
All servers in a cluster environment, or multiple servers on UNIX, AS/400.MVS/PDS, and Windows platforms, can collect monitor data into a single repository. If you have environments with multiple WebFOCUS or iWay servers configured for Resource Management and want to collect monitor data from those servers into a single repository, the steps in the following procedure show how to configure Resource Management using the Web Console of the servers.
|
|
How to: |
If you have not used the Resource Management DDL to create the repository tables, then you need to pick a server to do the initial configuration that will create the repository tables. Using the Web Console of the server you will need to perform the steps in How to Configure the First Server. If the Resource Management DDL was used to create the repository tables then go to the How to Configure Additional Servers.
|
|
For the first server, configure Resource Management from the Web Console of the server using the following steps:
After configuration is complete, select the monitoring level for Resource Governor. For more information, see How to Set Repository Properties.
|
|
For additional servers that will use the same repository, configure the Resource Management from the Web Console of the server using the following steps:
Note: Create Repository must be set to No on each additional server so that the configuration process does not drop and recreate the repository tables. This will cause the loss of data for any of the reporting servers using the same repository tables.
If the relational repository tables were created by the DBA using the DDLs provided with the product, then all servers have to be configured using Create Repository No.
After configuration is complete, select the monitoring level for Resource Governor. For more information, see How to Set Repository Properties.
Note: All administration for Resource Governor must be done on each of the servers configured to use the same repository tables.
|
|
If Governing is being used, administration for Resource Governor must be done on each server. Knowledge base rule files cannot be shared or copied from one server to another.
When rules are built for Governing, there is a knowledge base rule file built on the server. These knowledge base files can only be used on the server that they were built on. For example, if rules to govern databases are built on a UNIX server, these rules can only be used on that specific UNIX server. The same rule applies for Windows, z/OS, PDS server, and other platforms.
|
WebFOCUS |