Configuring Many-to-One Monitoring

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.


Top of page

x
Configuring Resource Governor

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.



x
Procedure: How to Configure the First Server

For the first server, configure Resource Management from the Web Console of the server using the following steps:

  1. Configure the relational data adapter for the repository, if it does not yet exist.
  2. Configure Resource Governor from the Resource Management Configuration pane.
  3. Enter the Resource Management license key. Click Continue.
  4. Select Relational from the Repository Type drop-down menu.
  5. Enter a unique name in the Server Name field, or accept the default.
  6. Select a Data Adapter and the appropriate connection name from the drop-down menu.
  7. Set Create Repository to Yes.
  8. Provide an Owner/Schema name for the relational adapter that Resource Governor will use to create the repository tables.
  9. Click Configure.

After configuration is complete, select the monitoring level as per the Resource Governor manual.



x
Procedure: How to Configure Additional Servers

For additional servers that will use the same repository, configure the Resource Management from the Web Console of the server using the following steps:

  1. Configure the relational data adapter for the repository, if it does not yet exist, that connects to the same database used in step 1 in How to Configure the First Server.
  2. Configure Resource Governor from the Resource Management Configuration pane.
  3. Enter the Resource Management license key. Click Continue.
  4. Select Relational from the Repository Type drop-down menu.
  5. Enter a unique name in the Server Name field, or accept the default.
  6. Select a Data Adapter and the appropriate connection name from the drop-down menu.
  7. Set Create Repository to No.

    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.

  8. Provide an Owner/Schema name for the relational adapter that Resource Governor will use to create the repository tables.
  9. Click Configure.

After configuration is complete, select the monitoring level as per the Resource Governor manual.

Note: All administration for Resource Governor must be done on each of the servers configured to use the same repository tables.



x
Reference: Repository Tables Sizing

There is a sizing document available with suggestions on how to determine the size for the Resource Governor repository tables for the different releases. This documentation is available by contacting Customer Support.



x
Reference: Governing

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