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 Analyzer.
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 Analyzer 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 Analyzer 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:
Note: The Sybase ASA database used for the Resource Management Repository must be created with the Ignore trailing blanks in string comparisons option (or the -b option in the dbinit command).
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.
The Resource Management Configuration pane has the following options:
The type of Resource Management that is being configured. Depending on your license key, this will show either Standard or Enterprise.
The name of the server configured with Resource Management.
The repository that is being used.
The data adapter connection of the current configuration. This is only seen with a Relational repository.
The owner/schema name for the relational adapter that Resource Analyzer will use to create the repository tables. This is only seen with a Relational repository.
Note: For MySQL, this is the database name from the URL specified on the MySQL adapter configuration page.
Indicates whether Data Request Monitoring is on or off. When Global Data Request Monitoring is enabled, or set to On, Resource Analyzer 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:
Indicates whether SQL Data Manipulation Language (DML) is enabled or disabled when monitoring is active. When SQL DML Monitoring is enabled or set to On, Resource Management will monitor SQL INSERT, UPDATE, DELETE, CREATE, ALTER, and DROP requests in addition to the standard data request commands. The default value is Off. This setting should be used to replace the use of SET SMARTMODE = DML, which is now a depreciated setting.
These settings allow for the customization of procedure data to be collected. The following options are available:
These settings allow for the customization of command data to be collected. The following options are available:
The following table shows the comparisons between the Monitoring settings in 7.6, and earlier releases, and the Command Log records settings in Release 7.7.
Release 7.6 |
Release 7.7 |
---|---|
Monitoring Settings |
Command Log Records |
All Data |
Select all |
Query, Froms, Relations, and Columns |
Commands, Request, Data Sources, WHERE/IF, and Fields |
Query, Froms, and Relations |
Commands, Request, Data Sources, and WHERE/IF |
Query and Froms |
Commands, Request, and Data Sources |
Query only |
Commands and Requests |
Note: The All Data option in Release 7.6 also collects SORT and Functions. In Release 7.7, SORT has been included in Fields, and Functions has its own select box.
The commands option in Release 7.7 will also collect information about Remote requests from a HUB-SUB configuration.
Resource Management will always collect session records and this feature cannot be turned off.
By default, command records (for example, a TABLE command being issued) will also be collected for a data resource that is not being monitored.
The Resource Management: Resource Analyzer page opens, and the navigation pane on the left appears, as shown in the following image.
WebFOCUS |