Table of Contents Previous Next PDF


Oracle TSAM Plus Console Users Guide

Oracle TSAM Plus Console Users Guide
This chapter contains the following topics:
Overview
The Oracle TSAM Plus monitoring console allows you to specify the Oracle Tuxedo components you want to monitor, as well as track events and alerts. The console has six major sections:
Note:
User Accessibility
User accessibility settings can be adjusted from the log-in screen and the console page.
In the upper left-hand corner of the log-in screen, click the Settings drop-down menu. You can select the following three options; the settings take effect immediately:
Accessibility-specific constructs are added to improve screen reader behavior.
Application display uses high-contrast instead of the default contrast.
Application display uses large fonts instead of the default size fonts.
In the upper right-hand corner of the Oracle TSAM Plus Console page, click Accessibility; the Accessibility Preferences page appears. It has the same three user accessibility options as the log-in screen.
When you have selected your options, click OK; the settings take effect immediately.
Top Menu Bar
The top menu bar contains the following Oracle TSAM Plus monitoring console functionality:
Policy: Define and manage system policies.
Tuxedo Metrics: Query Oracle Tuxedo monitoring metrics.
Tuxedo Application Runtime Metrics: Query Oracle Tuxedo Application Runtime monitoring metrics.
Management: Define user management, data management and global parameter settings.
Alert: Define and query alerts.
Help: On-line help page.
Component Tree
The component tree view displays Oracle Tuxedo, Oracle Tuxedo Application Runtime for CICS and JES hierarchy information.
By clicking the Type drop-down button in the upper right corner of the Oracle Tuxedo component tree panel, the tree panel can switch between three trees.
Each component tree gives you a different view of the back-end Oracle Tuxedo system.
Besides hierarchy information, other information is displayed (such as Oracle Tuxedo version, Domain model, server status, etc.). Certain tasks (for example, Create Policy) can be performed directly on the tree nodes.
Note:
Similar to the artjesadmin changeconcurrent command, the maximum concurrent job number can also be changed in TSAM Plus console. Right click ARTJESINITIATOR in the JES component tree, there is an menu item named Change Concurrent Jobs. If the server is active, the menu item is available. On this option is selected, a popup window appears with the current max concurrent job number displayed. Input a number between 1 and 32767, the concurrent job number is modified.
Search Panel
Search component tree elements.
Unread Alerts Panel
Displays severity-level unread alert count.
Work Area
Enter detailed monitoring information. For example, policy definition, metrics view and management etc.
Using Oracle TSAM Plus
This section contains the following topics:
Monitoring Policy
Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo infrastructure behavior. Policy Management allows you to do the following:
This section contains the following topics:
Tuxedo Monitoring Policy
On the menu bar, click Policy and select Tuxedo Monitoring Policy from the drop-down menu; the Monitoring Policy List page appears. It displays the existing defined policies and allows you to view, add, edit, or delete policies. This section contains the following topics:
Monitoring Policy List Page
The Monitoring Policy List page allows you to create and manage the Oracle Tuxedo component monitoring policies.
Button Bar
Table 1 lists the Monitoring Policy List button bar functions.
 
Exports selected policies in an .xml file to a user-specified location.
Policy List Table
The Policy List table displays the following columns:
Select: Allows you to select all or individual policies.
Name: Displays the current policy names.
Status: Displays the policy status.
enabled: The corresponding request is sent to Oracle Tuxedo.
disabled: The corresponding request is not sent to Oracle Tuxedo.
Note:
Domain ID: Displays the domain identifier attached to the policy as follows: DOMAINID:Master:IPCKEY.
Tuxedo Components: String that represents policy impact scope of Tuxedo resources in selected domain. It is FML32 boolean expression compliant. For example: (TA_PMID%%'.*BOXBANK*') indicates using an FML32 boolean expression for machine selection.
Create/Edit Policy Page
The Create/Edit Policy page contains the following sections:
Tuxedo Component Panel
The Tuxedo Component panel contains the following selections:
Domain: Required.
Machine: Optional.
Group: Optional.
Server: Optional.
Machine, Group, and Server can also accept FML32 boolean expressions. Click the radio button to select an input method (from the drop-down list or manually enter an FML32 boolean expression). The value of each level is determined by its parent level (except for Domain).One monitoring policy must be specified for one domain.
Monitoring Policy Panel
The Monitoring Panel contains the following tabs:
Call Path Tab
Service Tab
XA Transaction Tab
Domain Gateway Tab
BRIDGE Tab
GWWS Tab
To use the listed tab options, click the Enable check box. If enable is not selected, all tab options are disabled. One monitoring policy can contain multiple monitoring categories.
Call Path Tab
Table 2 lists the Call Path tab options.
 
Ratio: Accepts a value range of 1-65535. It indicates that monitoring starts for a certain number of requests. The default value is “1” (indicating each request is monitored).
Interval: Accepts a value range of 1-65535. It indicates a period of time (in seconds) that monitoring can be started. It is exclusive of ratio settings. The default value is “1”. The ratio/interval control only applies to the call path initiator.
For single condition items by default, if one of the item evaluations is true, then the condition is true. This applies to other monitoring policy definitions unless there is a special comment.
Note:
"Domain Gateway" acts as a call path initiator for local service requests. For imported services, the initiator type is set to the original caller process. The "Web Service Client" initiator point is established from the Web service gateway process (GWWS).
TSAM Plus 12.1.1.1 rolling patch 020 (or later) Agent supports
GWSNAX ECID in call path metrics.
TSAM Plus 12.1.1.1 Manager does not support ECID. In order to display ECID in the console, the Manager version is required to be 12.1.3.0 or later.
To enable the call path monitoring for GWSNAX inbound request, you must select "Domain Gateway" when defining the policy.
The WTC module is not supported for call path monitoring.
Service Tab
Table 3 lists the Service tab options.
 
Ratio: Accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored).
Interval: Accepts a value range of 1-65535. It indicates a period of time (in seconds) that monitoring can be started and is exclusive of ratio settings. The default value is “1”.
XA Transaction Tab
Table 4 lists the XA Transaction tab options.
 
It accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored).
Domain Gateway Tab
Table 5 lists the Domain Gateway tab options.
 
BRIDGE Tab
Table 6 lists the Bridge tab options.
 
GWWS Tab
Table 7 lists the GWWS tab options.
 
Notes:
All polices are global configurations that are visible for all users and editable for users with policy management administrator privileges.
It possible for a policy to be to modified simultaneously by multiple users. The final changes may not be seen by other users depending on the console refresh interval.
Tuxedo Application Runtime Monitoring Policy
Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo Application Runtime infrastructure behavior.
This section contains the following topics:
Monitoring Policy List Page
On the menu bar, click Policy and select Tuxedo Application Runtime Monitoring Policy from the drop-down menu. The Monitoring Policy List page appears. It displays existing defined Tuxedo Application Runtime monitoring policies and allows you to view, add, edit, or delete policies.
Button Bar
Table 8 list the button bar functions.
 
Table 8 Button Bar
Exports selected policies in an .xml file to a user-specified location.
Policy List Table
The Policy List table displays the following columns:
Select: Allows you to select all or individual policies.
Name: Displays the current policy names.
Status: Displays the policy status.
enabled: The corresponding request is sent to Oracle Tuxedo.
disabled: The corresponding request is not sent to Oracle Tuxedo.
Note:
CICS Region ID: Displays the CICS region identifier (CICS region name) attached to the policy.
Create/Edit Policy Page
The Create/Edit Policy page contains the following sections:
Policy Property Panel
The Tuxedo Application Runtime Policy panel contains the following:
Name: Policy name input text box. Required.
CICS Region: Selection of region that the current policy attaches to. Required.
Tuxedo Application Runtime Monitoring Policy Panel
The Tuxedo Application Runtime Monitoring Panel contains the following tabs:
CICS Transaction Tab
CICS Terminals Tab
To use the options listed in each tab, click the Enable check box. If enable is not selected, all options in the tab are disabled.
CICS Transaction Tab
Table 9 lists the CICS Transaction tab options.
 
Ratio: Accepts a value range of 1-65535. It indicates that monitoring is started among how many requests. The default value is “1” (indicating each request is monitored).
CICS Terminals Tab
Table 10 lists the CICS Terminal tab options.
 
Notes:
All polices are global configurations that are visible for all users and editable for users with policy management administrator privileges.
It possible for a policy to be modified simultaneously by multiple users. The final changes may not be seen by other users depending on the console refresh interval.
If the UBBCONFIG group setting or the tuxgroups in the file Region-Group.mapping has been modified after the ART transaction policy is defined, the resource filter might be expired. In that case, policy should be redefined.
Tuxedo Application Runtime Monitoring IMS Policy
Oracle TSAM Plus provides comprehensive monitoring control of Oracle Tuxedo Application Runtime IMS infrastructure behavior.
This section contains the following topics:
Monitoring Policy List Page
On the menu bar, click Policy and select Tuxedo Application Runtime Monitoring IMS Policy from the drop-down menu. The Monitoring Policy List page appears. It displays existing defined Tuxedo Application Runtime monitoring IMS policies and allows you to view, add, edit, or delete policies.
Button Bar
Table 11 list the button bar functions.
 
Table 11 Button Bar
Exports selected policies in an .xml file to a user-specified location.
Policy List Table
The Policy List table displays the following columns:
Select: Allows you to select all or individual policies.
Name: Displays the current IMS policy names.
Status: Displays the IMS policy status.
Domian ID: Displays IMS policy Domain ID.
Create/Edit Policy Page
Click Add, Edit, or Clone, go to the Create/Edit Policy page. At the top of page, enter the name for IMS policy to be created and select a IMS Tuxedo domain.
The Create/Edit Policy page contains the following tabs:
IMS Transaction Tab
IMS Program Tab
To use the options listed in each tab, click the Enable check box. If enable is not selected, all options in the tab are disabled.
IMS Transaction Tab
This page is used to define policy to report IMS Transaction metric generated by MPP server. Table 12 lists the IMS Transaction tab options.
 
IMS Program Tab
This page is used to define policy to report IMS Program metric generated by BMP server. Table 4 lists the IMS Program tab options.
 
Tuxedo Metrics Monitoring
Oracle Tuxedo Metrics collection is driven by policy monitoring. Once metrics are collected, you can view them on the related metric pages. Click Tuxedo Metrics on the menu bar; the Tuxedo Metrics page appears. From the drop-down menu you can select the following:
Call Path
Call Path metrics monitoring provides a quick way for you to view the latest call path information. For long-running call path situations, Oracle TSAM Plus allows you to view runtime executions dynamically in real time.
The Call Path Metric window contains the following panels:
Call Path Query by Filter Panel
Table 14 lists the Call Path Query by Filter panel options. Results are displayed in the Call Path Results List panel.
 
Note:
"Application Failure" indicates tperrno is TPESVCFAIL. Other errors situations belong to "System Failure"
Tuxedo domain ID: <DOMAINID>:<master machine name>:<IPCKEY> in the UBBCONFIG *RESOURCE section.
Logical Machine ID: LMID in the UBBCONFIG *MACHINES section.
A counter in range of 1..99999999 (starting from 1)
Call Path Results Panel
This Call Path Results panel displays server-side call path queries.
There are two sub-panels:
Call Path Results List Panel
Table 15 lists the Call Path Results List panel options.
 
TPEXXX/tperrno
TPEXXX
is the error code string format and tperrno is the corresponding numeric value, for example, TPESVCFAIL/11.
Call Path Details Panel
Table 16 lists the Call Path Details panel options.
 
Message Flow: There are two Message Flow format:
ICON Server (
tpcall/tpacall/tpforward Root Service)
IMS Server (ARTIMS/DLI_OPERATION)

Where:
Note:
If an Oracle Tuxedo server has invoked tpcall/tpacall/tpforward, the content is displayed in parentheses. For example, BROKER (tpcall DEPOSIT).
Following DLI operations are supported: GU, GHU, GN, GHN, GNP, GHNP, ISRT, DLET, CHNG, PURG, REPL, FLD, OPEN, CLSE, INQY, POS, and PING.
Duration (microsecond): Time span T(n) - T(n-1) (in seconds)
Call Flag: The tpcall/tpacall call flags.
The Export to Excel button allows you to place the table contents into an MS Excel compatible file.
Notes:
If multiple async calls are made in one process (for example, in a service two tpacalls are made), the order is based on the service invocation sequence for the reply instead of the timestamp. This allows you to easily correlate requests and reply in an "ordered" manner.
For GWWTDOMAIN, both local domain and remote domain are displayed. LDOM/RDOM information is displayed in the domain gateway cell.
For BRIDGE, the message full stages are supported (same as GWTDOMAIN).
Call Pattern
Call Pattern monitoring provides a quick way for you to view the Call Pattern information. The Call Pattern Metric window contains the following panels:
Call Pattern Query by Filter
Table 17 lists the Call Pattern Query by Filter panel options.
 
Click the Query button; the Call Pattern Result List panel appears.
Call Pattern Results Panel
The Call Pattern Results panel displays server-side Call Pattern queries. There are two sub-panels:
Call Pattern Results List Panel
Table 18 lists the Call Pattern Results List panel options.
 
Total call pattern in this collection. The Export to Excel button allows you to place the table contents into an MS Excel compatible file.
Call Pattern Details Panel
Click any row in the Call Pattern list, the selected Call Pattern details are displayed. Table 19 lists the Call Pattern Details panel options.
 
The Export to Excel button allows you to place the table contents into an MS Excel compatible file.
Service
Service Monitoring allows you to monitor Oracle Tuxedo services. Click Tuxedo Metrics and select Service from the drop-down menu; the Service page appears.
The filtering options panel allows you to specify supply information to the services you want monitored. On the left, there are drop-down lists of Domain, Machine, Group and Server. There are two modes for the service selection, select the most active services or particular services on the right. Table 20 lists the Service Selection options.
 
Click Query; the query results are displayed in the Service Monitoring Results panel. Table 21 lists the Service Monitoring Results panel options.
 
The Pause/Resume button allows you to stop the data refresh temporarily. The default is Pause (which indicates that a current refresh is in progress). Clicking it will Resume and refresh stops. Clicking it again restores the status.
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
XA Transaction
There are two ways to initiate XA Transaction queries: you can specify an XA Transaction identifier, or you can query using filtering parameters. These two ways are exclusive. Table 22 lists the XA Transaction Query by Scope filtering options.
 
 
The default value is "All" and the second monitoring scenario must use the default setting.
The Exact Match checkbox is under the text field. If checked, the whole identifier string must be matched, otherwise all the XA transaction IDs that contain the specified string are listed.
Click Submit; the XA Transaction results appears in the XA Transaction Result List panel.
Table 23 lists the XA Transaction Results List panel options.
 
When you click on a transaction item in the list, the transaction path, related call path ID and transaction details are displayed in the XA Transaction Path, Corresponding Call Path Correlation ID and XA Transaction Detail panels respectively.
The XA Transaction Path shows the XA Transaction network in a tree structure similar to the Component Tree. In the XA Transaction Path tree, each node represents one domain XA Transaction. If multiple /T domains are involved in the XA Transaction, the XA transaction spread path can be easily observed.
In the Corresponding Call Path Correlation ID panel, the call path(s) related to the XA transaction are listed. You can include multiple call path correlation IDs in an XA Transaction. To do so, you must define an XA Transaction policy element and a call boundary call path policy element. If the two elements are applied to one process, one XA Transaction monitoring process includes multiple call paths. Clicking on the call path ID displays the call path detail in the Call Path Metric.
Table 24 lists the XA Transaction Detail panel options.
 
tms_msg_xxx (for GWTDOMAIN XA Transaction activities)
xa_msg_xxx (for GWTDOMAIN XA Transaction activities)
Domain Gateway
A monitoring project may contain multiple domain gateways; however, one monitoring chart can only monitor one local domain gateway (due to data source consistency). Click Tuxedo Metrics and select Domain Gateway from the drop-down menu; the Domain Gateway Metrics page appears. The Domain Gateway page contains two panels:
Domain Gateway Selection
Table 25 lists the Domain Gateway Selection panel options.
Note:
 
 
Domain Gateway Monitoring
Table 26 lists the Domain Gateway Monitoring panel options.
 
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
BRIDGE
Similar to Domain Gateway.
Note:
GWWS
Click Tuxedo Metrics and select GWWS from the drop-down menu; the GWWS Metric page appears. The GWWS Metric page contains two panels:
GWWS Query by Filter
Table 26 lists the GWWS Query by Filter options.
 
GWWS Live/History Monitoring
Table 28 lists the GWWS Live/History Monitoring options:
 
Tuxedo Application Runtime Metrics Monitoring
Metrics collection is driven by policy monitoring. Once metrics are collected, you can view them on the related metric pages.The Tuxedo Application Runtime Metrics page includes four panels:
To access the Tuxedo Application Runtime Metrics page, click Tuxedo Application Runtime Metrics on the menu bar. From the drop-down menu you can select the following:
CICS Resources
Oracle TSAM Plus allows you to query and edit CICS resource configuration files on the Oracle Tuxedo master node
Note:
To enable this function, you must make sure the ARTADM server runs on each node and the KIXCONFIG environment variable is set to the CICS resource files directory.
Querying CICS Resources
You can query CICS resources by region. All of the CICS Resource configuration files are listed after you select a CICS region and click the Query button.You can also the click Refresh button to refresh the CICS Resource list for the selected CICS region.
Editing/Viewing CICS Resources
You can edit or view the CICS resource depending on the authority configured in User Management.
To edit the CICS Resource configuration file, you must do the following steps:
1.
Select one CICS region from region dropbox, then click the Query button. All of the CICS configuration files belonging to the selected region are listed.
2.
Note:
The Edit button is enabled when the number of selected configuration file is 1.
3.
Click the Update button to save the modification. You can also click the Back button to return to the list of CICS Resources without modifying the file.
Note:
For more information, see Oracle Tuxedo Application Runtime for CICS and Batch documentation.
CICS Transaction
CICS Transaction monitoring provides a quick way for viewing the latest CICS Transaction information.
The CICS Transaction page contains the following panels:
CICS Transaction Query by Filter Panel
Table 29 lists the CICS Transaction Query by Filter options.
 
CICS Transaction Live/History Monitoring Panel
Table 30 lists the CICS Transaction Live/History Monitoring Graph tab metrics.
 
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
 
CICS Terminals
CICS Terminals metrics provides a quick way for you to view the latest CICS Terminals information.
The CICS Terminals window contains the following panels:
CICS Terminals Query by Filter Panel
Table 31 lists the CICS Terminals Query by Filter options.
 
 
CICS Terminals Live/History Monitoring Panel
Table 32 lists the CICS Terminals Live/History Monitoring panel options.
 
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
JES Job Submit
JES Job submit provides a quick way for you to submit a job through the TSAM Plus console. For more information, see Oracle ART Runtime documentation.
Notes:
To enable JES job submit and monitoring, you must set the JESMONITOR environment variable to yes before you start the LMS server and set the "JOBREPOSITORY" value in the JES configuration file to specify the path of the job repository.
If the "JOBREPOSITORY" value is not in the JES configuration file, the list panel lists the JOB in the APPDIR.
The JES job submit window contains the following panels:
JES Application Selection Panel
Click List Available Jobs, all available job script files are listed in the Job File Information List Panel" if the selected JES application is alive.
Job File Information List Panel
Table 33 lists the JES Job File Information List Panel options.
 
Select an item, and click Submit. If the job is submitted successfully, the display message appears as follows:
"Submit of Job xxxx was successful", where "xxxx" is the job id. Click View Job to see a detailed message. If it fails, an error message is displayed.
JES Jobs
JES Jobs metrics provides a quick way for you to view the latest JES jobs information.
The JES jobs window contains the following panels:
JES Jobs Query by Filter Panel
Table 34 lists the JES Jobs Query by Filter options.
 
You can also query the exact job ID by using 'Query by Job ID' subform. Fill in 'Job ID' and click Query; if found, the corresponding job is listed in the result.
Jobs Query Results List Panel
Table 35 lists the JES Jobs Query Results List table columns.
 
Certain actions can be made to the queried out job list entries. Besides the Refresh button, Cancel, Purge, Hold, and Release actions can be used on selected jobs. The job cancel and purge behavior is the same same as the artjesadmin command. The command return status is displayed in a popup window.
Notes:
A job can be released only when the job status is HOLD_WAITING.
A job can be purged only when the job is not in the PURGE queue.
Two additional actions/buttons (Job Logs and Job Sysouts) are located on the button bar that provide job log and job sysout information.
Notes:
Purged jobs do not have Job Logs and Sysouts to view
All records in the job list table can be exported to a .xls file by clicking the Export to Excel button below the list table.
Note:
Choosing Monitoring Mode
You can change monitoring to auto refresh mode by specifying the Refresh Interval in the query result list panel toolbar; auto refresh is disabled by default. The refresh rate can be set as follows:
Job Detail Information Panel
When you select a Job in the Job Query Results List table, detailed information for the selected job is displayed in the Job Detail Information panel. The job detailed information is self-explanatory and includes the following:
Note:
JES Metrics
JES Metrics allows you to monitor the running status of the JES system. It contains two panels: Query by filter and Monitor view.
JES Metrics Query by Filter Panel
The filtering condition panel let user supply information to specify the jobs to be observed in the JES system. On the left, there are dropdown lists for JES application name, Job classes, Job priorities and Job owners, and one edit box for Job name.
There are two modes for the JES metrics monitoring, live monitoring and history monitoring.
Table 36 lists the UI components and their relationships.
 
When the conditions filing is complete, click Submit; the monitoring results page appears on the right.
JES Monitor View
 
The Export button allows you to save the table contents to an EXCEL compatible file.
IMS Transaction
IMS Transaction monitoring provides a quick way for viewing the latest IMS Transaction information and shows IMS transaction metrics generated by MPP server.
The IMS Transaction page contains the following panels:
IMS Transaction Query by Filter Panel
Table 38 lists the IMS Transaction Query by Filter options.
 
IMS Transaction Live/History Monitoring Panel
Table 39 lists the IMS Transaction Live/History Monitoring Graph tab metrics.
 
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
IMS Program
IMS Transaction monitoring provides a quick way for viewing the latest IMS Program information and shows IMS program metrics generated by BMP server.
The IMS Transaction page contains the following panels:
IMS Program Query by Filter Panel
Table 40 lists the IMS Program Query by Filter options.
 
Lists all programs. The default value is empty.
IMS Program Live/History Monitoring Panel
Table 41 lists the IMS Program Live/History Monitoring tab metrics.
 
In table view, the Export to Excel button allows you to place the table contents into an MS Excel compatible file.
IMS Detailed Monitoring
The IMS Transaction page contains the following panels:
Search Panel
Table 42 lists the query filters on the Search panel.
 
Table 42 Query Filters
Clicking on the Reset button resets all the query filters (except Max Queried Out Record) to the initial status.
Query Result List Table
When clicking the Query button, all the Transaction/Program collect instances met the search criteria are listed in the Query Result List table. Click any of the entries listed in the Query Result List table to display the detailed information in the Detailed Information panel.
Clicking on the Refresh button executes the last query once more and loads the latest DB data in the list table.
Detailed Information Panel
This panel displays the detailed information of the entry selected in the Query Result List Table. Table 43 lists the detailed information.
 
User/Data Management
Click Management and select the following from the drop-down list:
User Management
The User List page allows you to add, edit and delete users and groups. An Oracle TSAM Plus group is a set of privileges. The default groups are "administrator" and "viewer". They cannot be deleted.
An Oracle TSAM Plus user may belong to one or more groups. When Oracle TSAM Plus is installed, the default user is “admin” (configured during installation), and cannot be deleted.
You can enter the Group List menu bar by clicking the Group List button, and return to the User List menu bar by clicking the User List button. Table 44 lists the User List Menu Bar options.
 
Click Change Password to change the password. Click Back to cancel the operation and return to the User Management window.
Note:
The Create User button is enabled only when the current logged-in user has User Management administrator privileges.
The information of all online users is displayed in Online Users window. The available information of users includes Name, IP Address, Login Time and Session ID.
Table 45 lists the Group List button bar options.
 
The "Modify" button is enabled when the current login user has the administrator privilege of group management. Select the group you want to edit and click the Modify button.
Oracle TSAM Plus Group/User Privileges
Table 46 lists the Oracle TSAM Plus Group/User privilege options.
 
Notes:
For lower left Unread Alert notification panel:
For example, you have Tuxedo alert, ART alert and Tuxedo alert administrate privileges. When you select all the queried out alerts (including both Tuxedo alert and ART alert type), the Clear and Delete button above the query result table is disabled.
Data Management
Data Management allows you to purge the Oracle TSAM Plus database data (including the monitoring data in the database and the invalid Oracle Tuxedo components in the database).
Purging Monitoring Metrics Data
You can purge all monitoring data including Server/Service data and Call Path/ XA Transaction data. To purge Monitoring data, do the following steps:
1.
Note:
2.
You can select "Any", "Time Period", "Weeks" or "Months" to enter purge time period.
Note:
The Purge button is enabled when the logged-in user has Data Management privileges.
3.
Click the Purge button to delete monitoring data from the database.
Purging Invalid Tuxedo Components Nodes
Tuxedo components can be changed to "INValid" status due to management operations at Tuxedo application side. By default, the "INValid" Tuxedo components are not deleted from the database.Customers can purge all "INValid" Tuxedo components in the Data management window.
Note:
Currently, only the purging all "INValid" Tuxedo components on the data management page is supported. Invalid components can be purged in the component tree.
Global Parameters
The Global Parameters page contains four panels:
Table 47 lists the Global Parameter properties for each panel.
 
Note: If you check or unchecked Tuxedo Application Runtime Feature Enabled, you must restart the Oracle TSAM Plus application for the change to take effect.
Note: To back up configuration files successfully, properly set the file permission of the backup directory, or start up TSAM Plus Manager web server using the same account as the backup directory file owner.
Denotes the sleep interval (in milliseconds) in case the MAX_INQUEUE_RUNNER_NUM value is crossed. The default value is 500.
Log level control. The default value is Info. (Trace, Debug, Info, Warn, Error).
Alert Monitoring
Click Alert and select one of the following:
Tuxedo Alert Definition
Click Alert and select Tuxedo Alert Definition from the drop-down list; the Tuxedo Alert Definition List Panel appears. This panel lists available alert definitions and allows you to create, edit, and manage alert definitions.
Table 48 and Table 49 list the Tuxedo Alert Definition Menu Bar and Tuxedo Alert Column options respectively.
 
 
Define New Alert Page
Click the Add, Edit or Clone button on the Alert Definition List Menu bar; the Define New Alert page appears. It allows you to define a concrete Oracle Tuxedo alert definition.
The Define New Alert page is divided into four sections:
Alert Properties
Table 50 lists the Alert Properties options.
 
If this alert evaluation is true, the request message is dropped and the call fails (TPESYSTEM). This only applies to Call Path and Service type alerts.
Tuxedo Components
The Component Scope panel contains the following selections:
Note:
Click the radio button to select input method (use the drop-down list or manually enter an FML32 boolean expression). The values of each level is determined by its parent level, except for Domain.
Metrics Evaluation Expression(s)
You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "and" or "or".
FML Boolean Expression(s)
You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables. For call path alerts, if the elapsed time only is evaluated in the evaluation expression, the alert is triggered once along the entire call path. Other metrics combined with elapse time do not have this effect.
Note:
Tuxedo Application Runtime CICS Alert Definition
Click Alert and select Tuxedo Application Runtime CICS Alert Definition from the drop-down list; the Tuxedo Application Runtime Alert Definition List panel appears. This panel lists available Tuxedo Application Runtime alert definitions and allows you to create, edit, and manage alert definitions.
Tuxedo Application Runtime CICS Alert Definition List Panel
Table 51 and Table 52 list the Tuxedo Application Runtime CICS Alert Definition List menu bar options and columns respectively.
 
 
Define New Alert Panel
Click Add or Clone on the menu bar; the Define New Alert panel appears. This panel allows you to define concrete Tuxedo Application Runtime alert definitions.
The Define New Alert panel is divided into three sections:
Alert Properties
Table 53 lists the Alert Properties options.
 
Metrics Evaluation Expression(s)
You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "and" or "or".
FML Boolean Expression(s)
You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables.
Note:
Tuxedo Application Runtime IMS Alert Definition
Click Alert and select Tuxedo Application Runtime IMS Alert Definition from the drop-down list; the Tuxedo Application Runtime Alert Definition List panel appears. This panel lists available Tuxedo Application Runtime IMS alert definitions and allows you to create, edit, and manage alert definitions.
Tuxedo Application Runtime IMS Alert Definition List Panel
Table 54 and Table 55 list the Tuxedo Application Runtime IMS Alert Definition List menu bar options and columns respectively.
 
 
Define New Alert Panel
Click Add or Clone on the menu bar; the Define New Alert panel appears. This panel allows you to define concrete Tuxedo Application Runtime IMS alert definitions.
The Define New Alert panel is divided into three sections:
Alert Properties
Table 56 lists the Alert Properties options.
 
Metrics Evaluation Expression(s)
You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "And" or "Or".
FML Boolean Expression(s)
You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables.
Tuxedo Application Runtime JES Alert Definition
You can view, add, edit and delete JES Alert Definitions through Alert Definition
Click Alert and select Tuxedo Application Runtime JES Alert Definition from the drop-down list; the Tuxedo Application Runtime JES Alert Definition List panel appears. This panel lists available Tuxedo Application Runtime JES alert definitions and allows you to create, edit, and manage alert definitions.
Tuxedo Application Runtime JES Alert Definition List Panel
Table 57 and Table 58 list the Tuxedo Application Runtime JES Alert Definition List menu bar options and columns respectively.
 
Click Add or Edit; the JES Alert Definition panel appears.
 
JES Alert Definition Filter Conditions
Table 59 lists the JES Alert Definition Filter Conditions options.
 
JES Alert Definition Details
If the Type is JES Job, the JES metric detail panel provides the information shown in Table 60. Three levels of metric details can be selected and displayed: Job Status, Job Execution Time, and Job.
 
If the Job Type is JES Metrics, the JES metric detail panel provides the information shown in Table 61
 
Alert Query
Alert Query view displays the alerts that have transpired. It includes metric alerts and system alerts. Metrics alert are the events generated against the defined metrics alert. System alerts represent system events.
Click Alerts and select Alert Query from the drop-down menu; the Alert Query page appears.The Alert Query page contains two tabs:
Unread Alerts Tab: Displays all unread alerts.
Historical Alerts Tab Provides historical alert query information.
Unread Alerts Tab
"Unread" alerts are most important for administrators because they represent events that they may not be aware of. The Unread Alerts tab contains two sections:
Table 62 lists the Alert Query filtering condition options.
 
Table 63 lists the Alert Query columns.
 
"Process [%s:%d] evaluates alert [%s] with true, metrics[key=value,key=value...]"
Click Clear to clear all the selected alerts on current page.
Click Delete to delete all the selected events on current page.
Click Detail, a popup window with the following detailed Alert information appears:
Once an alert is cleared as "Unread" status and not deleted, it still can be queried in the historical alert page, but not in the active alert page. The following filter conditions can be set:
The search operation finds matched records from all current filtered "unread" alert results, no limited to the "unread" alerts shown on the current page. Matched record means any alert that is matching the specified alert category condition, alert severity condition and having the given "search" text string within any of the following value fields: "Alert Name", "Alert Reason String (Description)".
Click the Reset button to reset filter conditions and list all "unread" alerts.
Historical Alerts Tab
The Historical Alerts Tab allows you to query historical alerts with supplied filtering conditions. It contains two panels:
Table 64 lists the Historical Alert Query Conditions panel options.
 
"Any" and supported severity levels. If Include Lower Level is checked, all alerts at this level or below are queried. The sequence is Fatal, Critical, Warn and Info.
The exact time of the previous day to the exact same time of the current day. For example: 7:45 Wednesday-to-7:45 Thursday.
Click Submit; the results are displayed in the Alert Query Result panel.
System Alerts Supported
Users cannot define System Alerts; they are generated automatically (for example, an invalid alert definition is encountered, or the database purging process is completed).
Table 65 lists the supported system alerts.
 
 
Data purging(sequence:?) filed at [%DATE_TIME] by admin is done.
Alert Metrics Tables
The Alert Metrics tables contain the alert metrics for all alert types. Each metric has the corresponding FML32 field name and applicable operators. Referencing these tables will help you write the alert metric FML boolean expression directly when defining a new alert.
Call Path Alert Metrics Table
 
>, >=