Data Management
Data Management purges TSAM monitoring database. Data purge options are as follows:
Purge Tuxedo Component/Server/Service Data
Purge Tuxedo Component/Server/Service Data purges data based on the Tuxedo Component.
Table 1-13 lists the Purge Tuxedo Component/Server/Service Data properties.
Table 1-13 Purge Tuxedo Component/Server/Service Data
|
Name
|
Description
|
|
From
|
Start time [DD MM YYYY HH MM]
|
|
To
|
End time [DD MM YYYY HH MM]
|
|
Scope
|
Purge Scope:
- Tuxedo Component: Purges Tuxedo component and all relative data
- Server Monitor: Purges Server Monitor data
- Service Monitor: Purges Service Monitor Data
|
|
Domain
|
Domain name
|
|
Machine
|
Machine name
|
|
Group
|
Group name
|
|
Server
|
Server
- Server Available: Lists all available servers
- Server Selected: Lists server(s) selected for purge
- Fast Search (Left/Right): Input partial server name, the cursor highlights the first matched server name
|
|
Service
|
Service
- Service Available: Lists all available services
- Service Selected: Lists service(s) selected for purge
- Fast Search (Left/Right): Input partial service name, the cursor highlights the first matched service name
|
Purge Tuxedo Component/Server/Service Data
To Purge Tuxedo Component/Server/Service Data, do the following steps:
- Select From and To for purge time period
- Click the Scope check box. If a scope is not selected, data cannot be purged.
- Tuxedo Component: Purge the Tuxedo Component data and its database data
| Note: |
When Tuxedo Component is selected, From and To are ignored. |
- Server Monitor Data: Purge Server Monitor data from database, but not the Tuxedo Component
- Service Monitor Data: Purge Service Monitor data from database, but not the Tuxedo Component
- Select any of the following and click Purge.
- Domain: Select a domain and click purge. If Tuxedo Component scope is selected, the purge deletes the domain from the database and all the Machine, Group, Server, Service data under this domain.
If Tuxedo Component scope is not selected, the Server Monitor Data is automatically selected, all the Server Monitor Data under the domain is deleted. If Service Monitor data is selected, all the Service Monitor data under the domain is deleted.
- Machine: Select a machine for the domain
- Group: Select a group for the domain
- Server: Select a server for the domain
- Service: Select a service for the domain
| Notes: |
If a Domain is selected, all the servers and services are populated to the Server Available list and Service Available list respectively. Use the > (single selection) or >> (all) button to add to the selected list. The Purge button only applies to the servers or services in the selected list. |
| Note: |
Fast Search (Left/Right) helps to quickly locate a server or service. |
Purge Call Path/ Transaction Data
Purge Call Path/ Transaction Data purges Call Path/ Transaction monitoring data.
Table 1-14 lists the Purge Call Path/ Transaction Data properties.
Table 1-14 Purge Call Path/ Transaction Data
|
Name
|
Description
|
|
From
|
Start time [DD MM YYYY HH MM] of time period
|
|
To
|
End time [DD MM YYYY HH MM] of time period
|
|
Call Path/ Transaction
|
Call Path/ Transaction purges the following monitoring data:
|
Purge Call Path/ Transaction Data
Call Path and Transaction monitoring data is independent of the Tuxedo Component.
To purge Call Path/ Transaction data, do the following steps:
- Select purge time period by From and To
- Click the check box for Call Path or Transaction
- Click the Purge button to delete the monitoring data for Call Path/ Transaction from the database
Purge All Data
Purge All Data purges all monitoring data in Purge Tuxedo Component/Server/Service Data and Purge Call Path/ Transaction Data.
Purge All Data
Click Purge All to clean all the monitoring data from database, include Tuxedo Component and Call Path/ Transaction.
| Notes: |
Only the super-user admin can purge the monitoring data. |
| Note: |
Using any of the purge options removes monitoring data from the database. Sessions that are already logged-in are reminded to logout and re-log on to avoid data inconsistencies. |
See Also