The worksheets in this appendix are planning tools to help you organize the activities and information you must gather to perform an STA installation or upgrade. This appendix includes the following sections:
Table C-1is used only for upgrades from a previous version of STA. Use it to track the required and optional activities you perform to prepare for the upgrade. Use the "Comments" column to record any special planning information. See "Preparation Tasks for All Upgrades" for complete details about these activities.
Table C-1 Upgrade Preparation Activities
| Activity | Comments | Done |
|---|---|---|
|
Verify current STA version is a released version. Note: If you are upgrading from STA 1.0.x, you must also install a new version of Linux before installing the new version of STA. |
||
|
Choose single-server or two-server upgrade method. |
||
|
Verify site and target server meet requirements for the new version of STA. |
||
|
Determine whether you will need to temporarily increase the size of your /tmp file system for the upgrade. |
||
|
Review environment changes in the new version of STAor impact to your upgrade plan. |
||
|
Ensure all required RPM packages are installed (upgrades from STA 2.0.x only). |
||
|
Verify the current version of STA has recent, successful communication with the monitored libraries. |
||
|
Verify STA is processing exchanges across all monitored libraries. |
||
|
Move installation and database logs you want to retain to a safe place (optional). |
||
|
Perform service log snapshot on current STA installation (optional). |
||
|
Download service log bundles you want to retain (optional). |
||
|
Rename custom templates with "STA–" prefix (optional). |
||
|
Record current custom template settings you want to retain (optional). |
||
|
Record Executive Report policy settings you want to retain (optional). |
These worksheets include information required by the STA installer. See "Accounts Configured During STA Installation" for complete details about the requested information.
If you are upgrading from a previous version of STA, you can use the "Current Value" columns in the worksheets to record the values used in your current installation. Use the "New Value" columns to record the values you will use for the new version of STA.
Table C-2 includes user accounts and locations you need to run the STA installer.
Table C-2 Installation Users and Locations Worksheet
| Item | Description | Current Value | New Value |
|---|---|---|---|
|
Oracle group |
Linux group used for installing and upgrading Oracle products on the STA server. Introduced in STA 2.1.0. |
– |
|
|
Oracle user |
Linux user for installing, upgrading, and administering Oracle products on the STA server. Introduced in STA 2.1.0. |
– |
|
|
Oracle central inventory location |
Directory for tracking information about Oracle products installed on the STA server. Introduced in STA 2.1.0. |
– |
|
|
Oracle storage home location |
Directory where STA and associated Oracle software are installed. Introduced in STA 2.1.0. |
– |
|
|
STA installer location |
Location where the STA installer is downloaded. |
||
|
STA database data location |
Location of the STA database. |
||
|
STA database backup location |
Location of the STA database backups on the STA server. |
Table C-3 includes user accounts you will use to perform STA administration activities, and MySQL accounts used internally by the STA application to access and manage the STA database.
Note:
Password requirements have changed for STA 2.3.x. See "Username and Password Requirements" for details.Table C-3 User Accounts Worksheet
| Account | Description | Current Username and Password | New Username and Password |
|---|---|---|---|
|
WebLogic Administration |
Used to log in to the WebLogic Administration console. Caution: The username and password for this account are not retrievable. If these credentials are lost, STA must be re-installed. |
||
|
STA Administrator |
Used to log in to the STA application with full access privileges. |
||
|
STA Database Root User |
Owns the MySQL database. The predefined username of root cannot be changed. Caution: The password for this account is not retrievable. |
username = root |
username = root |
|
STA Database Application User |
STA uses this account to connect to the database. |
||
|
STA Database Reports User |
Non-STA and third-party applications use this account to connect to the database. |
||
|
STA Database Administrator User |
STA administration and monitoring utilities use this account to connect to the database, primarily to perform scheduled backups. |
Table C-4 includes external ports used by the STA application. These port numbers are predefined and cannot be changed. Use the "Verified" column to record that you have verified with your network administrator that these ports are open and available.
Table C-4 Unconfigurable External Ports
| Port Description | Protocol | STA Port | Verified |
|---|---|---|---|
|
Secure Shell. Used to log in from the STA server to the STA database backup and the monitored libraries. |
SSH |
22 |
|
|
Used for transmitting Simple Network Management Protocol (SNMP) requests to the monitored libraries. |
SNMP |
161 |
|
|
Used for receiving SNMP notifications (traps) from the monitored libraries. |
SNMPTRAP |
162 |
Table C-5 includes configurable external and internal ports used by the STA application. Use the "Verified" column to record that you have verified with your network administrator that these ports are open and available.
Note:
Changes to the default WebLogic Administration console port numbers were introduced in STA 2.1.0.Table C-5 Configurable Internal and External Ports
| Port Description | Type | Protocol | Default Port for STA 2.1.0 & Later | Current Port | New Port | Verified |
|---|---|---|---|---|---|---|
|
Unsecure port for the WebLogic Administration console (default for STA 1.0.x and 2.0.x was 7001) |
External |
HTTP |
7019 |
|||
|
Secure port for the WebLogic Administration console (default for STA 1.0.x and 2.0.x was 7002) |
External |
HTTPS |
7020 |
|||
|
Unsecure port for the staUi managed server, which manages the STA GUI |
External |
HTTP |
7021 |
|||
|
Secure port for the staUi managed server |
External |
HTTPS |
7022 |
|||
|
Unsecure port for the staEngine managed server, which manages basic STA internals |
Internal |
HTTP |
7023 |
|||
|
Secure port for the staEngine managed server |
Internal |
HTTPS |
7024 |
|||
|
Unsecure port for the staAdapter managed server, which manages SNMP communication with the monitored libraries |
Internal |
HTTP |
7025 |
|||
|
Secure port for the staAdapter managed server |
Internal |
HTTPS |
7026 |
Table C-6 includes your site's fully qualified domain name used by Oracle's Remote Diagnostic Agent (RDA) when generating STA service logs.
Table C-7 includes information you use to configure the SNMP connection between STA and the monitored libraries; the same SNMP v3 user must be configured on each monitored library and STA instance. See "Configuring the SNMP v3 Protocol on the Libraries" for complete details about the requested information.