TLP Software Installation (Task Map)
This task map includes all of the installation tasks that must be completed before you can use the TLP tool. Note that some of the installation procedures must be completed in sequential order. The order in which these procedures should be performed is indicated in this task map.
|
Tasks |
Description |
For Instructions |
|---|---|---|
|
1. Install the TLP server software on target systems. |
The TLP server software is installed on a dedicated system in the data center. The software package name is SUNWtlp-2.3. | |
|
2. Modify the TLP default configuration file. |
After you install the TLP server software, you need to manually configure some of the parameters in the tlp.cfg file. | |
|
3. Configure the CGI web server script configuration. |
The web server script is used to retrieve the data from the clients. By default, the script is located in the /opt/SUNWtlp/cgi directory. The script responds to requests from the client systems and then uploads the data to the server. The script then stores the Explorer dumps in the TLP directory. | |
|
Upgrade the TLP server software to the most recent version. |
If you are running an older version of the TLP software, you need to upgrade to the 2.3 version of the software. | |
|
Update the TLP configuration, snapshots, and the metafiles. |
When you upgrade to the latest version of the TLP software, you also need to update the TLP configuration, the snapshots, and the metafiles. |
How to Update the TLP Configuration, Snapshots and Metafiles After Upgrading the TLP Software |
|
Install the TLP client software on each client system. |
Before you can run the TLP client, you must install the TLP client software on each client system in the data center. The package name is SUNWtlpc-1.0. | |
|
Install TLP baselines. |
TLP uses patch baselines to allow standardized patching in the data centers. The baselines are consistent and complete, and they do not have any external dependencies. When installing a baseline, TLP will check and resolve any external dependencies. |
- © 2010, Oracle Corporation and/or its affiliates