In this section: |
Resource Governor Usage Monitoring facility allows you to monitor requests as they are submitted by users, and logs information about request usage. This information includes the usage statistics associated only with data retrieval or data manipulation in the case of MODIFY or MAINTAIN. This request information is stored in Resource Governor Usage Monitoring tables. You can specify the Monitor Preference, which allows you to change what information is collected for monitored data sources.
The Web Console enables you to administer Resource Management.
You can:
Access to these tasks is provided by the Resource Management link on the toolbar.
The following image shows the hierarchical navigation menu that is available when the Resource Management link is selected.
|
|
In this section: |
The Resource Management ribbon provides options for configuring Resource Management, as shown in the following image.
The following sections provide detailed explanations for each option in the ribbon.
Note: You can also access these options by right-clicking Resource Management - Enabled/Disabled in the navigation pane.
|
|
How to: |
When you enable Resource Management, it automatically turns on monitoring. However, you can disable and re-enable monitoring at any time.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled and select Enable/Disable.
|
|
How to: |
The reporting server will write all information regarding monitored sources to a log file. This log file is then archived to the Resource Management repository at predetermined intervals or limits, while the server is running. The current log is also archived when the server starts or when the administrator submits a job from the Web Console of a running server.
The intervals or limits can be configured from the Logging Properties option in the Resource Management Web Console. When configured, the log file of an active server will be archived based on the maximum number of sessions or the days set, or based on a scheduled job configured by the administrator.
|
|
Logging properties can be configured in the Resource Management Web Console. When configured, the log files will be archived based on the maximum number of sessions and days set, or based on a scheduled job configured by the administrator.
or
From the navigation pane, right-click Resource Management - Enabled/Disabled and select Logging Properties.
The Resource Management Logging Properties window opens, as shown in the following image.
The following options are available:
The number of sessions recorded in the active log file before the log is archived and a new log is started. The default value is 10000.
The number of days an active log file is kept open before it is archived and a new log is started. The default value is 1.
When set to No, automatic archiving is active and based on the two settings above.
When set to Yes, only the Limit agent memory for interim log records is shown and the administrator has to configure the schedule archive settings. For more information, see How to Schedule an Archive.
Note: To use the scheduler feature for archiving of the log file, the server Scheduler process must be running. To check this, from the Web Console, click the Workspace option on the toolbar. Click the Special Services and Listeners folder, right-click SCHEDULER, and select Start. If the Start option is not available, the scheduler is already running.
This setting is used for a connection during which multiple procedures are run within the session. This type of connection can cause the Resource Management logging process to use a large amount of memory before the log records are written to the physical disk file (rmldata.log).
When set to Yes, enter a value between 5 and 99 (in megabytes). When this parameter is set to Yes and the specified amount of memory is reached, the connected users log records in memory are written to a temp disk file and the memory is freed.
At the point any new log records generated will be written to disk instead of memory until the end of the session disconnect. At this time, all the log records in the temporary disk file are written to the physical disk file (rmldata.log). This setting should only be used if excessive memory usage is observed and users are connected for long periods.
|
|
How to: |
When this option is selected, a context menu is shown with the following options:
Note: This option is only available when rmlog_schedule_archive is set to Y. For more information on logging properties, see How to Set Logging Properties.
These give the administrator the option to archive the current log file (a new log file is automatically started), as well as view previous archive jobs including any that were submitted due to server restart, and any of the intervals or limits mentioned above having been reached.
Note: After a successful archive, the log file is deleted. If the archive fails, the log file will remain available for archiving. The failure should be investigated and corrected. Once this is done, the List Unarchived Log Files option can be used to archive the data. For more information, see List Unarchived Log Files.
|
|
Note: Only one archive can be scheduled at a time.
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Archive, Schedule and E-Mail, and select Manage.
The Manage Schedule and E-Mail for procedure pane opens, as shown in the following image.
The Manage Schedule and E-Mail for procedure pane contains the following fields and options:
Determines if there is a schedule and if so, whether the schedule is active or inactive.
The email addresses where the messages will be sent. Place each email address (or user ID configured on the server with an associated email address) on a new line with no separators.
You can send the messages to email addresses defined in the procedure by either typing in the location of the procedure, or clicking the ellipses and manually selecting it from the Select Procedure dialog box.
Select this to enable when an email should be sent.
Select this option to get the following options:
The Manage Schedule and E-Mail for procedure pane contains the following additional fields and options:
Determines whether a process flow will execute once, on a recurring basis, on several specific days (multi-day), or when the server starts.
Specifies the interval in which a process flow will be executed. For example, if you select Month as your Interval Type, and select 2 as your Interval Number, the flow will execute every two months. This option is only available if the schedule type is set to Recurring.
Specifies the frequency at which a process flow will be executed. For example, if you select Week as your Interval Type, and select 2 as your Interval Value, the flow will execute every two weeks. This option is only available if the schedule type is set to Recurring.
Specifies the start date for the execution of the process flow.
Specifies the start time for the execution of the process flow.
Allows you to specify an end time for the execution of the process flow. This option is only available if the schedule type is set to Run Once or Multi-Day.
Specifies the end date for the execution of the process flow. This option is available if Specify End Date is selected.
Specifies the end time for the execution of the process flow. This option is available if Specify End Date is selected.
Specifies the day of the week on which the process flow will be executed. This option is only available if the schedule type is set to Recurring or Multi-Day.
Specifies the day of the month on which the process flow will be executed. This option is only available if the schedule type is set to Recurring or Multi-Day.
Specifies the beginning of the daily time span of the process flow. This option is only available if the schedule type is set to Recurring.
Specifies the end of the daily time span of the process flow. This option is only available if the schedule type is set to Recurring.
Specifies the option to execute the process flow on desired holidays.
The following options are available:
This option is only available if the schedule type is set to Recurring or Multi-Day.
This option controls where the log information from the Maintenance Job should be sent when the Job finishes.
The following options are available:
Multiple options can be selected. The default value for this option is ETLLOG and E-Mail.
Note: If the Job is Run from the DMC or Web Console, information will go to the console log regardless of this setting.
Note: Do not use the Set and Test Run or Save options.
A confirmation dialog box opens.
|
|
This report runs for the user whose ID value is stored in the sched_scan_id of a Scheduler. The Scheduler must be active to run the Scheduler Agents report.
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Archive, Schedule and E-Mail, and select Scheduler Agents.
The Scheduler Agents window opens, as shown in the following image.
The following options are available from the Procedure hyperlink:
|
|
Note: The Scheduler must be active to run the Scheduler Events report.
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Archive, Schedule and E-Mail, and select Scheduled Events.
The Scheduled Event window opens, as shown in the following image.
The report opens, as shown in the following image.
This report shows all flows and procedures scheduled to run during the time period you selected. The Run Date and Run Time columns show their scheduled run times. The User ID column shows the user ID used when running the flow or procedure.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Archive, and then select Submit Archive job.
The Select an Option dialog box opens, as shown in the following image.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Archive, and then select View Archive jobs.
The Deferred List opens showing the saved logs, as shown in the following image.
|
|
How to: |
Select this option to show a list, if any, of previous log files that have not been archived.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled and select List Unarchived.
The Resource Management unarchived logs list opens listing the non archived logs, as shown in the following image.
|
|
How to: |
Repository data can be deleted once it has been used or reported on. This deletion can be by date range or, if sufficient data has been stored, the data can be deleted if it is more than one, three, or six months old.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Maintenance, Schedule and E-Mail, and select Manage Jobs.
The Resource Management Schedule Repository Maintenance - Add pane opens, as shown in the following image.
The Manage Schedule and E-Mail for procedure pane opens, as shown in the following image.
The Manage Schedule and E-Mail for procedure pane contains the following fields and options:
Determines if there is a schedule and if so, whether the schedule is active or inactive.
The email addresses where the messages will be sent. Place each email address (or user ID configured on the server with an associated email address) on a new line with no separators.
You can send the messages to email addresses defined in the procedure by either typing in the location of the procedure, or clicking the ellipses and manually selecting it from the Select Procedure dialog box.
Select this to enable when an email should be sent.
Select this option to get the following options:
The Manage Schedule and E-Mail for procedure pane contains the following additional fields and options:
Determines whether a process flow will execute once, on a recurring basis, on several specific days (multi-day), or when the server starts.
Specifies the interval in which a process flow will be executed. For example, if you select Month as your Interval Type, and select 2 as your Interval Number, the flow will execute every two months. This option is only available if the schedule type is set to Recurring.
Specifies the frequency at which a process flow will be executed. For example, if you select Week as your Interval Type, and select 2 as your Interval Value, the flow will execute every two weeks. This option is only available if the schedule type is set to Recurring.
Specifies the start date for the execution of the process flow.
Specifies the start time for the execution of the process flow.
Allows you to specify an end time for the execution of the process flow. This option is only available if the schedule type is set to Run Once or Multi-Day.
Specifies the end date for the execution of the process flow. This option is available if Specify End Date is selected.
Specifies the end time for the execution of the process flow. This option is available if Specify End Date is selected.
Specifies the day of the week on which the process flow will be executed. This option is only available if the schedule type is set to Recurring or Multi-Day.
Specifies the day of the month on which the process flow will be executed. This option is only available if the schedule type is set to Recurring or Multi-Day.
Specifies the beginning of the daily time span of the process flow. This option is only available if the schedule type is set to Recurring.
Specifies the end of the daily time span of the process flow. This option is only available if the schedule type is set to Recurring.
Specifies the option to execute the process flow on desired holidays.
The following options are available:
This option is only available if the schedule type is set to Recurring or Multi-Day.
This option controls where the log information from the Maintenance Job should be sent when the Job finishes.
The following options are available:
Multiple options can be selected. The default value for this option is ETLLOG and E-Mail.
Note: If the Job is Run from the DMC or Web Console, information will go to the console log regardless of this setting.
The Save As dialog box opens.
Note: To create a new application, click the New button and enter a new application name in the dialog box.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Maintenance, then Schedule and E-Mail, and select Show jobs.
The Resource Management Repository Maintenance - Update pane opens, as shown in the following image.
The columns shown have the following drill-down options available:
Log and Statistics. Opens the Log and Statistics pane that enables you to view a log or statistics report.
The following options are available:
The Scheduler must be active to run the Scheduler Events report.
This report shows all flows and procedures scheduled to run during the time period you selected. The Run Date and Run Time columns show their scheduled run times.
The User ID column shows the user ID used when running the flow or procedure:
Older than. Opens the Resource Management Schedule Repository Maintenance - Change pane. Select the new time range of data that you want to delete and click Save.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Maintenance, then Schedule and E-Mail, and select Delete jobs.
The Resource Management Repository Maintenance - Delete pane opens.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Maintenance, and select Submit Maintenance job.
The Resource Management Repository Maintenance pane opens, as shown in the following image.
Note: If you select Delete data older than 1 month, the options on the Repository Maintenance pane will be slightly different than shown in the above image.
Note: Caution should be used when using this utility. Make sure you have a backup of the data before you proceed.
The Submit Repository Maintenance Job window opens.
A Deferred Execution pane opens confirming your request.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Maintenance, and select View Maintenance jobs.
The Deferred List pane opens, as shown in the following image.
|
|
In this section: |
The Configuration command has the following options:
These give the administrator the option to see current configuration settings, as well as change the viewable application directories, perform migration, change a license key, and remove the current Resource Management configuration.
|
|
How to: |
Setting monitor properties enables you to select global settings and the component levels to be monitored. Components are split into two categories, Procedure and Command. The information that Resource Governor monitors is stored in the Usage Monitoring tables. The default settings are: Global Data request Monitoring set to off and component level set to Command. Session records are always captured.
|
|
To view Resource Management Properties:
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration, select Properties, and then select General.
The Resource Management Properties page opens, as shown in the following image.
The Resource Management Properties pane shows the following fields:
The date that Resource Management was configured or reconfigured.
The repository that is being used.
The data adapter connection of the current configuration.
The owner/schema name for the relational adapter that Resource Governor will use to create the repository tables.
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 number of application data sources and relational pass-thru data sources that have been enabled for monitoring. This will show Global monitor enabled if Data Request Monitoring is On. See the Global Settings section below for more information.
The number of application data sources and relational pass-thru data sources that have been disabled by setting the monitoring setting to OFF.
The number of procedures that have been excluded from monitoring.
The date the repository was modified using the Repository Maintenance page.
The last time the repository updated to include data from a log file.
|
|
To set Resource Management Properties:
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration, select Properties, and then select Monitoring.
The Resource Management Monitoring Properties page opens, as shown in the following image.
The Resource Management Monitoring Properties page has the following options:
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 amount of data stored in the repository can be controlled by selecting the record types logged for each connected session. Collecting all of the records can give a complete overview of what each connected user is doing and is a good first step in determining what resources are being consumed and which procedures, data sources, and fields are being used and by whom. But collecting everything can stress the data repository, whether a FOCUS or Relational Database Management system is being used. Some of the tables are more geared towards the Resource Governor feature and others are used just for the Resource Analyzer feature. The Functions and WHERE/IF records are mainly used by the Resource Governor, but there are several reports in Resource Analyzer that will report on that data as well. From the Web Console's Resource Management tab you have the option to add or remove any record type from the logging process using the Configuration/Properties/Repository menu in the Web Consoles ribbon or the Resource Management node on the tree.
To set Resource Management Repository Properties:
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration, select Properties, and then select Repository.
The Resource Management Repository Properties page opens. The page, as shown in the image below, shows the default record types collected. You can enable or disable any items on the page to control when they are to be collected. Some records are required for others to be collected so by selecting one record, it may cause dependent records to be selected automatically.
By default all procedures (focexec or SQL Stored Procedure) are monitored unless the Procedure requests log record has been disabled or the procedure has be removed from monitoring using the Manage Monitoring/Remove Procedures from Monitor page. By default, no data requests are collected unless one or more Data Requests log record types are selected and either Global Monitoring is enabled or at least one Data Source has been enabled for monitoring using the Manage Monitoring/Add Data Sources to monitor page for each Application folder. Also, the properties for the Application must have Monitoring enabled in the Applications properties page.
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 and, if active, Resource Governor records.
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 following table shows the relationship between the Repository Properties and the log record types, as well as the corresponding Repository entries.
Repository Property |
Record Type |
Repository Location |
Comments |
---|---|---|---|
Messages |
RLAU |
SMAUDIT |
Messages that are issued during the processing of a request will be monitored. |
Procedure Requests |
|||
Procedure |
RLFX |
SMRPCS |
Each Procedure (for example, FOCEXEC or SQL Stored Procedure) executed will cause a RLFX record to be collected. |
RLFW |
SMRPCWF |
The RLFW record will only be collected if the session was started by a connection from the WebFOCUS client or WebFOCUS self service application. The RLFW record is added to the SMRPCWF table or segment. Only one RLFW record will be collected for the primary procedure but several RLFX may be collected for a session |
|
Procedure statements and parameters |
RLFC |
SMRPCREQUESTS (table) SMRPCSCMD (segment) |
Contains the EX statement and it parameters or the -INCLUDE record. The actual command as executed. The RLFC records are collected if enabled and the Procedures are being collected. |
Data Requests |
|||
RLCD |
SMQUERY |
These settings allow for the customization of command data to be collected. The RLCD record is collected and added to the SMQUERY table or segment.. Each data request (for example, TABLE FILE… or SQL SELECT…) executed will cause a RLCD record to be collected. The RLCD can generate two additional child records, RLDG (Governor) and RLDE (request using SUFFIX=EDA data source). These two records cannot be disabled and will always be collected if generated. |
|
RLDG |
SMGOVERN (table) SMGOVEND (segment) |
||
RLDE |
SMREMOTES (table) SMRMTS (segment) |
||
Data Request Details |
|||
Data Request Statements |
RLCC |
SMRPCREQUESTS (table) SMCMDLN (segment) |
Contains the complete request. For example, TABLE FILE CAR PRINT CAR END. |
Translations |
RLAU |
SMAUDIT |
Contains the translated request if translation is required. If a WebFOCUS TABLE request is for a relational data source, the translated SQL, which is sent to the RDBMS, will be monitored. The RLAU records are collected if enabled and the Data requests statements are being collected. |
Functions |
RLDU |
SMFUNCTIONS (table) SMFNCTNS (segment) |
Data about aggregate functions used on fields. There is one record for each function used and contains the aggregation function used and the field it was used on. |
WHERE/IF |
RLDR |
SMRELATIONS (table) SMRELTNS (segment) |
Data on the Relational tests used in a request, such as the operator, literals, or date and time values used. There is one record for each WHERE/IF/AND/OR and contains the right and/or left data source and field used. It also has the literal if one was used on the left or right hand side of the clause other information pertinent to a relational test clause. |
Data Sources |
RLDS |
SMFROMS |
The Master File Description/Synonym name or RDBMS table or tables used in a request. There is one record for each data source used in a request. This includes cross referenced data sources or data sources joined using the JOIN or COMBINE command. |
Field |
RLDF |
SMCOLUMNS (table) SMCOLMNS (segment) |
The fields used, the type of field, and whether it was used in a sort or group in a request. There is one record for each field selected to return data in the request or in a BY or ORDER BY/GROUP BY statement. This record is not collected for fields used in functions or relational tests. |
Fields used by Reference |
RLDF |
SMCOLUMNS (table) SMCOLMNS (segment) |
Information about any DEFINE fields used or referenced in a request. The Fields used by Reference are indicated when the SMDEFINE field is set to 5 (Referenced). Referenced fields are fields that are used in a DEFINE in the MFD, DEFINE FILE or COMPUTE statement to create a virtual field and the virtual field is use in the request. |
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 |
|
|
How to: |
You can configure the application path to set the viewable directories for Resource Governor.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration and select Configure Application Path.
The Application Path pane opens, as shown in the following image.
|
|
For more information on how to migrate Resource Management, see Migrating the Resource Management Repository.
|
|
How to: |
A license key is required to run Resource Governor. You can change the license key you are using from within Resource Management at any time.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration, and select Change License Key.
The Resource Management Configuration pane opens showing your current license.
|
|
How to: |
You can remove Resource Management from the server from the Resource Management Configuration pane. This is required if you want to change the repository type from FOCUS to relational, or relational to FOCUS.
|
|
or
From the navigation pane, right-click Resource Management - Enabled/Disabled, select Configuration, and select Remove.
The Resource Management Confirmation pane opens.
|
|
In this section: |
When you right-click an application directory, a context menu is available, as shown in the following image.
The following sections provide detailed explanations for each option in this context menu.
|
|
How to: |
Monitoring Data Sources can be set at the Application level to monitor all Data Sources or at the individual level.
Note: Monitoring at the individual data source level will take precedence over the application level. For more information, see Monitoring Individual Data Sources.
|
|
The Application pane opens.
The Application pane has the following fields/options:
Is the date the synonym was first accessed.
Is the date the synonym was last accessed.
The number of data sources with monitoring on.
The number of data sources with monitoring off.
The number of data sources not being monitored.
The total number of data sources in the selected application directory.
The number of procedures with monitoring on.
The number of procedures with monitoring off.
The total number of procedures in the selected application directory.
For more information on setting monitor status, see How to Set Monitor Status at the Application Level.
Note: The samples application directory ibisamp, created at product installation, has monitoring turned off, by default.
|
|
Data sources in an application can have monitoring turned on or off at the application level. When On is selected, the Usage Monitor will collect information about all requests for all data sources in the application. When Off is selected, no monitored data for data sources in the Application is collected.
If Application monitoring has never been used, the Monitor Status will be Not Set. This is the default value.
To set monitor status for an application:
The Application pane opens.
|
|
How to: |
When you right-click an application directory and select Manage Monitoring, a context menu is available, as shown in the following image.
|
|
Data sources must be monitored to provide monitor data, which can then be used to analyze performance.
The Add Data Sources to Monitor pane opens to display all synonyms in the selected application directory, as shown in the following image.
The Add Data Sources to Monitor - Status pane opens displaying the selected data sources with monitoring enabled, as shown in the following image.
The data sources you selected now appear in the tree, as shown in the following image.
|
|
You can remove a data source from being monitored as follows.
A list of available data sources opens.
The Remove data Sources from Monitor - Status pane opens, confirming that the selected data source was removed.
|
|
By default, all Application Data Source procedures are monitored. You can remove a procedure from being monitored as follows.
A list of available procedures opens.
The Remove Procedures from Monitor - Status pane opens, confirming that the selected procedure was removed.
|
|
To have the ability to add procedures, they will need to be removed from monitoring first. For more details, see How to Remove a Procedure from Being Monitored.
The Add Procedures to Monitor pane opens to display all procedures in the selected application directory, as shown in the following image.
The Add Procedures to Monitor - Status pane opens displaying the selected procedures with monitoring enabled, as shown in the following image.
The procedures you selected now appear in the tree under the selected application directory.
|
|
In this section: |
When you right-click a relational adapter folder, a context menu is available, as shown in the following image.
The following sections provide detailed explanations for each option in this context menu.
|
|
|
|
Note: If there is only one connection name available, the properties for that connection will be shown immediately.
The Properties for Relational Adapter for the selected connection pane opens, as shown in the following image.
The Properties for Relational Adapter pane has the following fields/options:
Allows you to select the connection name from the drop-down menu.
Is the date the relational adapter was first accessed.
Is the date the relational adapter was last accessed.
The number of data sources with monitoring on.
The number of data sources with monitoring off.
The number of data sources not being monitored.
The total number of data sources in the selected application directory.
The number of procedures with monitoring on.
The number of procedures with monitoring off.
The total number of procedures in the selected application directory.
|
|
How to: |
When you right-click a relational adapter and select Manage Monitoring, a context menu is available, as shown in the following image.
In the example shown, the MS SQL Server is the adapter selected for relational source monitoring.
|
|
Monitoring relational data adapter sources means monitoring SQL direct passthru requests to relational sources that do not use synonyms. Relational sources must be monitored to provide monitor data, which can then be used to analyze performance or govern usage.
Note: The following procedure can only be done if a relational adapter has been configured.
To monitor relational sources:
The Add Data Sources to Monitor pane opens, as shown in the following image.
The Add Data Sources pane opens, as shown in the following image.
The Add Data Sources pane reopens displaying the selected data sources with monitoring enabled.
|
|
You can remove a data source from being monitored as follows.
The Remove Data Sources from Monitor pane opens.
The Remove Data Sources pane opens.
The Remove Data Sources pane reopens displaying the data sources that were removed.
|
|
By default, all relational procedures are monitored. You can remove a procedure from being monitored as follows.
The Remove Procedures from Monitor pane opens, as shown in the following image.
The Remove Procedures from Monitor pane opens, showing the list of available procedures.
The Remove Procedures from Monitor - Status pane opens, confirming that the selected procedure was removed.
|
|
To have the ability to add procedures, they will need to be removed from monitoring first. For more details, see How to Remove a Procedure for a Relational Adapter from Being Monitored.
The Add Procedures to Monitor pane opens.
The Add Procedures Status pane opens displaying the selected procedures with monitoring enabled, as shown in the following image.
|
WebFOCUS |