Before installing STA, understand what the STA installation configures.
The STA installation configures specific users, groups, and directories. Understand how these are used by STA so that you will know how best to configure them during installation.
Pay close attention to the ownership and permissions required for each location. Make sure that the locations do not have SELinux permissions. See Remove SELinux Permissions.
A Linux group used for installing and upgrading Oracle products on the STA server. Oracle recommends creating a separate group dedicated for this purpose. To perform STA installation and administration, you must log in as a user that is a member of this group. You cannot install STA as the Linux root user nor any other user with superuser privileges
The instructions and examples in this guide use the name oinstall for this group.
The Linux user used to install Oracle products on the STA server and run STA utilities and the STA application. This can be any user that is a member of the Oracle group.
Depending on your site's configuration, some of the activities performed by this user may require system root privileges. The administrator should add the Oracle user to the system sudoers file if this is the case.
The instructions and examples in this guide use the name oracle for this user.
The directory used for tracking information about Oracle products installed on the STA server. STA installer and deinstaller logs are kept in the logs subdirectory within this location.
The Oracle user must own this directory and have full permissions to it. To ensure other users in the Oracle group have proper access so they can install Oracle products, you should not use the Oracle user's home directory. Additionally, there should not be any system links created in this directory, as these can interfere with an STA installation or upgrade.
This location should be separate from the other directories described in this section. Oracle recommends registering this location after STA installation is complete so all Oracle installers use the same central inventory location on this server. See Register the Oracle Central Inventory Location for details.
The instructions and examples in this guide use /opt/oracle/oraInventory for this location.
The directory where STA and associated Oracle software is installed. STA is automatically installed in the StorageTek_Tape_Analytics subdirectory within this location. This location should be separate from the other directories described in this section.
If an earlier version of STA was installed on this server, this directory may already exist. If so, you should verify the correct ownership and permissions. The Oracle group (not root) must own this directory. The Oracle user must have full permissions the directory. If this directory does not exist, the STA installer will automatically create it if the Oracle user has full permissions to the parent directory.
The instructions and examples in this guide use /Oracle for this location.
The directory where all STA software is installed. This directory is assigned the name StorageTek_Tape_Analytics, and the STA installer automatically creates it within the Oracle storage home location.
The instructions and examples in this guide use /Oracle/StorageTek_Tape_Analytics for this location.
The directory where you download the STA installer. This location should be separate from the other directories described in this section.
The instructions and examples in this guide use /Installers for this location.
By default, the STA and WebLogic installer files are unpacked to the STA_home/tmp directory, which requires a minimum 11 GB of space. You can have the STA installer files unpacked to a different working location by running the STA installer with the following option:
–J–Djava.io.tmpdir=<absolute path for working directory>
For example:
$ ./sta_installer_linux64.bin –J–Djava.io.tmpdir=/Oracle/tmp
Location of the STA and MySQL logs. The contents tend to grow and are managed through log rotation. The default location is /var/log/tbi, but you can change this location at any time after STA installation (see Relocate the STA Logs Directory (optional) for instructions. See Review STA File System Layout for space requirements.
The STA installation creates specific administration and database accounts. These accounts are specific to STA (they are not Linux usernames).
STA and third-party applications use the database accounts to access and manage the STA database. These accounts must exist for normal STA operations, but you will not need to log in to any of them.
You can change the passwords for these accounts at any time using the STA Password Change Utility. See the STA Administration Guide for details.
Account for logging into the WebLogic Administration console to configure and manage the WebLogic environment—for example, to connect WebLogic to an LDAP or RACF server. This account is used infrequently.
An STA user with administrator privileges created during the installation. This account can log in to the STA user interface with full access privileges. This user can create and manage other user interface accounts (see the STA User's Guide).
A MySQL account that owns the STA database. It is used internally by the STA application to create the database and provide full access to all database tables. The username for this account is automatically set to root and cannot be changed. This is separate from the system root user.
A user-defined MySQL account (for example stadb) used internally by the STA application to connect to and update the STA database. It provides create, update, delete, and read access to all database tables.
A user-defined MySQL account (for example starpt) used by non-STA and third-party applications to connect to the STA database. It provides read-only access to selected database tables.
A user-defined MySQL account (for example stadba) used internally by STA utilities to connect to the database and configure and run backups. It provides full access, except the "grant" option, to all database tables.
An internal MySQL account that is automatically created during STA installation. It has full create, update, and delete privileges to the database. The username is automatically set to mysql and cannot be changed.
Do not modify the credentials for this account, as it may affect the ability of STA to access the database. Unlike the other database accounts, you cannot change its credentials through STA.
You will configure ports during the STA installation. These are dedicated ports that must remain available to STA. The installer will verify that the ports are not already in use on the network.
See the STA Administration Guide for a complete list of ports and for instructions on changing the configurable ports after installation using the Port Change Utility.
The typical port configuration is:
| Type | Typical Port |
|---|---|
| WebLogic Admin Console HTTP | 7019 |
| WebLogic Admin Console HTTPS | 7020 |
| staEngine HTTP | 7023 |
| staEngine HTTPS | 7024 |
| staAdapter HTTP | 7025 |
| staAdapter HTTPS | 7026 |
| staUI HTTP | 7021 |
| staUI HTTPS | 7022 |
| SNMP Trap Redirection Port | 7027 |