• 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:In the upper right-hand corner of the Oracle TSAM 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.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.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.
Note: Similar to the artjesadmin changeconcurrent command, the maximum concurrent job number can also be changed in TSAM 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.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:Table 1 lists the Monitoring Policy List button bar functions.
Exports selected policies in an .xml file to a user-specified location.
• 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.
• Domain: Required.
• Machine: Optional.
• Group: Optional.
• Server: Optional.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.Table 2 lists the Call Path tab options.
Table 2 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. Dynamic filter conditions are independent of each other. If multiple conditions are configured, the evaluation is true for all conditions and the monitoring can be initiated.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. Table 3 lists the Service tab options.
Table 3 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”. Table 4 lists the XA Transaction tab options.
Table 4 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). Table 5 lists the Domain Gateway tab options.
Table 5 Domain Gateway Tab Options It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is 300. Table 6 lists the Bridge tab options.
Table 6 Sub Controls of BRIDGE Panel It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is “300”. Table 7 lists the GWWS tab options.
Table 7 GWWS Panel Tab Options It indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is “300”. 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.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.Table 8 list the button bar functions.
Table 8 Button Bar Exports selected policies in an .xml file to a user-specified location.
• 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:
• Region ID: Displays the region identifier (region name) attached to the policy.
• Name: Policy name input text box. Required.
• Region: Selection of region that the current policy attaches to. Required.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.Table 9 lists the CICS Transaction tab options.
Table 9 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).
• Table 4 lists the CICS Terminal tab options.
Table 10 CICS Terminals Tab Options Indicates a period of time (in seconds) that monitoring can be started. It accepts a value range of 1-65535. The default value is 300. 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.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:
•
•
• Table 11 lists the Call Path Query by Filter panel options. Results are displayed in the Call Path Results List panel.
Table 11 Call Path Query By Filter Options
•
–
•
•
•
Note: "Application Failure" indicates tperrno is TPESVCFAIL. Other errors situations belong to "System Failure"
•
•
•
• A counter in range of 1..99999999 (starting from 1)Table 12 lists the Call Path Results List panel options.
Table 12 Call Path Results List Panel
• Start Time
The time stamp for the start of the call path query in the following format: mmmdd,yyyy,hh:mm:ss:ms GMT
•
•
•
• TPEXXX/tperrno
TPEXXX is the error code string format and tperrno is the corresponding numeric value, for example, TPESVCFAIL/11.
• Table 13 lists the Call Path Details panel options.
Table 13 Call Path Details Panel Options
•
–
Note: If an Oracle Tuxedo server has invoked tpcall/tpacall/tpforward, the content is displayed in parentheses. For example, BROKER (tpcall DEPOSIT).
• Duration: 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.Table 14 lists the Call Pattern Query by Filter panel options.
Table 14 Call Pattern Filter Panel Table 15 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.Click any row in the Call Pattern list, the selected Call Pattern details are displayed. Table 16 lists the Call Pattern Details panel options.
Table 16 Call Pattern Details Panel
– The Export to Excel button allows you to place the table contents into an MS Excel compatible file.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 17 lists the Service Selection options.
Table 17 Service Selection Options
• Click Query; the query results are displayed in the Service Monitoring Results panel. Table 18 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.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 19 lists the XA Transaction Query by Scope filtering options.
– The default value is "All" and the second monitoring scenario must use the default setting.
•
• Query an XA transaction by using an XA transaction identifier. For example x0 x46524a28 x1. For more information, see How the System Tracks Distributed Transaction Processing in the Oracle Tuxedo User Documentation.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.Table 20 lists the XA Transaction Results List panel options.
Table 21 lists the XA Transaction Detail panel options.
Table 21 XA Transaction Detail Panel Options
•
•
•
•
•
• tms_msg_xxx (for GWTDOMAIN XA Transaction activities)
• xa_msg_xxx (for GWTDOMAIN XA Transaction activities) 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:Table 22 lists the Domain Gateway Selection panel options.
• Table 23 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.Click Tuxedo Metrics and select GWWS from the drop-down menu; the GWWS Metric page appears. The GWWS Metric page contains two panels:Table 23 lists the GWWS Query by Filter options.
Table 24 GWWS Query by Filter Panel Options
• Table 25 lists the GWWS Live/History Monitoring options:
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:
•
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.You can query CICS resources by region. All of the CICS Resource configuration files are listed after you select a region and click the Query button.You can also the click Refresh button to refresh the CICS Resource list for the selected region.
1. Select one region from region dropbox, then click the Query button. All of the CICS configuration files belonging to the selected region are listed.
2. Select a configuration file then click the Edit button.
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.Table 26 lists the CICS Transaction Query by Filter options.
• Table 27 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.Table 28 lists the CICS Terminals Query by Filter options.
• Table 29 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.
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.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.Table 30 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.Table 31 lists the JES Jobs Query by Filter options.
Table 31 JES Jobs Query By Filter Options Specifies one or more owners separated by a semi-colon (;) or a coma (,).
•
•
•
•
•
• 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.Table 32 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.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: If you are using Internet Explorer, and IE security is set above medium, a warning message pops up when you click the Export to Excel button. Click the export button again to ignore the warning.
•
•
•
• Table 33 lists the UI components and their relationships.
Table 33 JES Metrics Query by Filter Panel When the conditions filing is complete, click Submit; the monitoring results page appears on the right.
Table 34 JES Monitor View The Export button allows you to save the table contents to an EXCEL compatible file.Click Management and select the following from the drop-down list: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 35 lists the User List Menu Bar options.
Table 35 User List Menu Bar You can change all user properties from the User Management window if you have User Management administrator privileges. Select the user you want to edit and click the Change Properties button. If you are the selected user, you can change your own properties.
• You can change all user passwords from the User Management window if you have User Management administrator privileges. Select the user whose password you want to change and click the Change Password button. If you are the selected user, you can change your own password.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 36 lists the Group List button bar options.
Table 36 Group List Button Bar 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.
•
• Table 37 lists the Oracle TSAM Group/User privilege options.
Table 37 Oracle TSAM Group/User Privileges
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.
•
•
•
•
•
•
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.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.
• Table 38 lists the Global Parameter properties for each panel.
Table 38 Global Parameter Properties Note: If you check or unchecked Tuxedo Application Runtime Feature Enabled, you must restart the Oracle TSAM application for the change to take effect. Denotes the sleep interval (in milliseconds) in case the MAX_INQUEUE_RUNNER_NUM value is crossed. The default value is 5000. Log level control. The default value is Info. (Trace, Debug, Info, Warn, Error). Click Alert and select one of the following: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 39 and Table 40 list the Tuxedo Alert Definition Menu Bar and Tuxedo Alert Column options respectively.
Table 40 Tuxedo Alert Columns
•
•
• 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.Table 41 lists the Alert Properties options.
Table 41 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.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.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.Table 42 and Table 43 list the Tuxedo Application Runtime CICS Alert Definition List menu bar options and columns respectively.
Table 43 Alert Definition List Columns 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.Table 44 lists the Alert Properties options.
Table 44 Alert Properties Options
•
•
• You can select the metric, operator and threshold to compose one expression. The logic for the expression can be "and" or "or".You can also input FML Boolean expressions directly. For more information, see Alert Metrics Tables.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.Table 45 and Table 46 list the Tuxedo Application Runtime JES Alert Definition List menu bar options and columns respectively.
Table 46 Alert Properties Options
•
•
•
• Table 47 lists the JES Alert Definition Filter Conditions options.
Table 47 JES Alert By Filter Options If the Type is JES Job, the JES metric detail panel provides the information shown in Table 48. Three levels of metric details can be selected and displayed: Job Status, Job Execution Time, and Job.
Table 48 JES Job Type Detailed Information
•
•
•
•
•
• If the Job Type is JES Metrics, the JES metric detail panel provides the information shown in Table 49
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.Table 50 lists the Alert Query filtering condition options.
Table 50 Alert Query Filtering Conditions
•
•
•
•
•
•
•
•
• Table 51 lists the Alert Query columns.
Table 51 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:Click the Reset button to reset filter conditions and list all "unread" alerts.Table 52 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.Table 53 lists the supported system alerts.
Table 53 System Alerts Supported
Table 54 Call Path Alert Metrics Table >, >= ==, != ==, != >, >=
Table 55 Service Alert Metrics Table >, >= ==, != >, >= >, >= ==, != >, >= >, >=
Table 56 GWTDOMAIN/BRIDGE Alert Metrics Table Lost, Reconnect >, >=
Table 57 GWWS Alert Metrics Table >, >= >, >= >, >= >, >= >, >= >, >=
Table 58 XA Transaction Alert Metrics Table
Table 59 CICS Transaction Alert Metrics Table >, >= >, >=
Table 60 CICS Terminals Alert Metrics Table >, >= >, >=