Home

for STA - Oracle Documentation

1. Settings for RactAuthenticater Comtayer stase Commen Poude Speote ave Ths page aloes you b defre De gerera corfg rato of te porde lial Ractiutherricater Orscrpticn Meno TIC fac Athertcaton Powder it Vorio 18 Contre tog OPTIONAL Ts REQUIRED 4 5 Ma o _ 16 Click the Provider Specific tab ee Settings for RacfAuthenticator Configuration com 17 Enter the Host name for example mvshost yourcompany com and Port number for example 8700 where the MVS system is running and then click Save Configuring External Authentication Providers for STA E 33 Tasks for Configuring IBM RACF Authentication Providers Settings for RacfAuthenticator Common Provider Specific Save This page allows you to configure additional attributes for this security provider 4E Supported Groups StorageTapeAnalyticsUser a Host mvshostyourcompany a Port 700 18 In the Change Center section click Activate Changes ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefere h cna Home gt Summary of Securky Messages Pending changes exist They must be activated to take effect WY Settings updated succe Settings for myrealm Configuration Users ar Domain Structure General RDEMS Searit Tei Environment Save 19 Log out of the WebLogic Administration console 20 Stop and restart STA using the STA command See the STA Administrati
2. Configurable Internal Ports The ports described in Table 3 3 are used for internal STA communications These port values must be unique Firewall router configuration Not applicable Table 3 3 Configurable Internal Ports Default Port Protocol Description Purpose 7023 HTTP staEngine managed server Basic STA internals unsecure 7024 HTTPS staEngine managed server Basic STA internals secure 7025 HTTP staAdapter managed server SNMP communication unsecure 7026 HTTPS staAdapter managed server SNMP communication secure STA Installation and Deinstallation Logs You can use the STA installation and deinstallation logs to help troubleshoot issues Most log file names include a timestamp to help identify the installation or deinstallation instance The timestamp is the date and time when the installation or deinstallation began Installing STA 3 5 STA Installation and Deinstallation Logs In particular the following logs provide valuable information if an installation or deinstallation fails See STA_logs install on page 3 6 for details about their location a _ installtimestamp log sta_installtimestamp log a deinstalltimestamp log sta_deinstalltimestamp log Log File Locations The location of STA installation and deinstallation logs varies depending on the status of the installation or deinstallation Logs are found in the following directories See Review STA
3. 4 4 Prerequisite Checks Checking existing STA instance s Checking MYSQL not installed Checking Operating System Compatibility Checking tmp available space iC EZA Checking Operating System has SELINUX disabled Checking Operating System services are stopped iptables Checking Operating System services are stopped snmpd and snmptrapd Checking required ports available 161 and 162 Checking required packages rpm build Checking required packages glibc Checking required packages expect Checking required packages binutils Checking required packages compat libcap1 Checking required packages compat libstdc ESISEL X Chasin annnini ansann omens vl View Successful Tasks View Log Checking tmp write privileges Expected result Directory tmp is writable Actual Result Directory tmp is writable Check complete The overall result of this check is Passed Help lt Back Next gt Cancel a Inthe Message pane click the Expand icon next to the task for which you want to display detail Figure A 3 is an example Click the Collapse icon to hide the detail again STA Graphical Installer and Deinstaller Screen Reference A 11 STA Graphical Installer Screens Figure A 3 Task Detail Displayed by Selecting the Expand Icon StorageTek Tape Analytics Installation 2 1 0 Prerequisite Checks io Welcome y 100 installation Location E e e Prerequisi
4. Cancel Help The installer performs a series of tasks to verify that the server environment meets all required and recommended prerequisites This process may take several minutes The possible outcomes of each verification task are as follows Success P The prerequisite passed successfully a Warning The recommended prerequisite did not pass a Failure 9e tThe required prerequisite did not pass You cannot continue the installation if there are any Failure outcomes Additionally it is recommended that you resolve all Warning outcomes before continuing You can keep the installer up at this screen while you resolve any issues and then return and click Rerun to run the verification process again Depending on the nature of a prerequisite you may need to stop a service change user privileges or install a yum package to resolve issues You can use either of the following methods to display expanded detail to help you troubleshoot issues and determine what action to take Select the task in the main window The task is highlighted in the Message pane with expanded detail Figure A 2 is an example A 10 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Figure A 2 Task Detail Displayed by Selecting the Task in the Main Window StorageTek Tape Analytics Installation 2 1 0 Prerequisite Checks a STORAGETERK Welcome 100 Installation Location
5. Note If you see Can t connect to local MySQL server the MySQL server isn t running Return to Step a and verify you have started MySQL Move the service log snapshot and database snapshot to another server as all STA files will be removed in the next step The snapshots are located in the following directories The service log snapshot is in Oracle_storage_home Middleware rda snapshots For example Oracle Middleware rda snapshots The database snapshot is in the database location specified during STA installation For example dbbackup Back up other files as needed Deinstall STA See Deinstall STA on page 9 2 for instructions Re install STA See Chapter 3 Installing STA for instructions Stop all STA services STA stop all Restore the database See the STA Administration Guide for instructions 10 Start all STA services Deinstalling and Restoring STA 9 3 STA Deinstallation Tasks STA start all 11 Configure STA See Configure SNMP Settings in STA on page 8 25 for instructions 9 4 StorageTek Tape Analytics Installation and Configuration Guide A STA Graphical Installer and Deinstaller Screen Reference This chapter includes the following sections Graphical mode Display Requirements m STA Graphical Installer Screens m STA Graphical Deinstaller Screens Graphical mode Display Requirements The STA graphical mode installer and deinstaller require X Window System v
6. 2014 09 18T17 36 19 470 06 00 sysman NOTIFICATION oracle sysman oii olis OlisVariable host 2014 09 18T17 36 19 4 6 00 sysman NOTIFICATION oracle sysman oii oili Olliinstallinventory 2014 09 18T17 36 19 471 06 00 sysman NOTIFICATION oracle sysman oii olli Olliinstallinventory 2014 09 18T17 36 19 471 06 00 sysman NOTIFICATION oracle sysman oii oiii OtiiinstallAreaContr S gt Close View Log Starting uninstall a Uninstalling oracle jse dms 12 1 2 0 0 Uninstalling oracle help ohj 12 1 2 0 0 Uninstalling oracle help share 12 1 2 0 0 v Help Cancel You can also view the log from the Linux command line While the deinstaller is running logs are kept in a subdirectory within tmp See STA Installation and Deinstallation Logs on page 3 5 for details A 42 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Deinstaller Screens Deinstallation Complete Oracle StorageTek Tape Analytics 2 1 0 Deinstallation Deinstallation Complete va Deinstall Oracle StorageTek Tape Analytics Deinstall Location STA Home Location Oracle StorageTek_Tape_Analytics Log File tmp Orainstall201S 01 07_09 SS 37AM deinstall2015 01 07_09 SS 37AM log Feature Sets Deinstalled Successfully Oracle Application Developer Framework 11 1 2 4 Oracle Weblogic Server 10 3 6 0 8 Oracle JOK 1 6 0 75 Oracle MYSQL 5 6 18 Oracle StorageTek Tape Analytics 2 1 0
7. By default the silent mode installer and deinstaller use the pointer file etc oralnst loc When you register the Oracle central inventory the file is automatically created with this name and location See Register the Oracle Central Inventory Location on page 3 15 for details If the Oracle central inventory location has not been registered you must create the pointer file manually and give it the filename oralnst loc See Create the Oracle Central Inventory Pointer File on page B 4 for details You can locate the pointer file in any directory but if it is not in etc you must use the invPtrLoc parameter to specify the file location when you run the silent mode installer or deinstaller See invPtrLoc pointer_file on page B 10 for details about this parameter Silent mode installer and deinstaller response files To run unattended the STA silent mode installer and deinstaller use configuration settings contained in a response file you create You must use the responseFile parameter to specify the name and location of this file The installer and deinstaller have their own respective response files Example B 1 and Example B 2 show the contents and required entries for each To create your own response files you can copy and paste each template into a text file and make the appropriate changes for your site To ensure password security do not enter clear text passwords into the response file After entering all other configura
8. Deinstatiation Complete Oracle StorageTek Tape Analytics deinstallation completed successfully The screen displays the details about the software packages that have been deinstalled Screen Fields None Screen specific Buttons Finish Click to exit the STA deinstaller STA Graphical Installer and Deinstaller Screen Reference A 43 STA Graphical Deinstaller Screens A 44 StorageTek Tape Analytics Installation and Configuration Guide STA Silent mode Installer and Deinstaller This appendix includes the following sections a Using the STA Silent mode Installer and Deinstaller a Files and Utilities Used With Silent Mode a STA Silent mode Installer Tasks a STA Silent mode Deinstaller Tasks a STA Installer Command Options Using the STA Silent mode Installer and Deinstaller Silent mode allows you to bypass the graphical user interface and supply the STA installation or deinstallation options in an XML properties file called the response file You create the response file using the response file build utility silentInstallUtility_ version jar where version is the version of the utility you have downloaded This mode is useful for unattended installations and for installing STA on multiple machines By using a response file you can supply a single set of parameters and automate the installation You can run the silent mode installer either from a script or from the Linux command line Silent mode Requirements
9. All upgrades You want to retain service logs from the current version of STA You want to retain current STA usernames and configuration settings You have custom templates with names prefixed STA You want to retain the ownership and visibility settings for existing custom templates You want to retain the ownership settings for existing Executive Report policies Upgrading to STA 2 1 x 8 7 Upgrade Preparation Tasks Verify Your Site is Ready for the Upgrade Use this procedure to review the upgrade requirements and verify that your site is ready Verify Upgrade Prerequisites Use this procedure to ensure that your environment meets all STA 2 1 x prerequisites 1 Display your current STA version Some upgrade tasks vary depending on whether you are upgrading from STA 1 0 x STA 2 0 x or STA 2 1 x a Login to STA using an STA administrator username b Click About in the Status Bar c Verify you are running a currently released version of STA See Valid STA 2 1 x Upgrade Paths on page 8 1 for details Choose whether you will be using the single server or two server upgrade method See Upgrade Process Overview on page 8 2 for details Verify that your site and the target server meet STA 2 1 x requirements See the STA Requirements Guide for details Determine whether the tmp filesystem on the target STA server has sufficient space for the upgrade The size of tmp should be at least as large as
10. Change Center View changes and restarts No pending changes exist Cick the Release Configuration button to allow others to edit the domain Home Log Out Preferences 5 Record Help e myrealm Configuration Users and Groups Roles and Pobcdes Credential Mappings Providers General RDEMS Security Store User Lockout Performance Domain Structure Tei a En anman Use this page to configure the general behavior of this security realm 6 Use the Change Center section as follows a To make changes to the screens you must click Lock amp Edit This locks out other users from making changes at the same time ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefer View changes and restarts Home Cikk the Lock amp Edit button to modify add or Home Page delete items in this domain Information and Res DOUA a Configure applications a Configure GridLink for F Recent Task Status a When you have finished editing each screen click Save to keep the changes or Release Configuration to cancel them a When you have finished your editing session click Activate Changes to apply all changes to all screens a Atany time during your editing session you can click Undo All Changes to cancel all changes to all screens 7 For your changes to take effect in STA you must log out of the WebLogic Administration console and stop and restart STA See Tas
11. Database Root User StorageTek Tape Analytics Installation 2 1 0 ORACLE Database Root User Welcome i i Enter a password for the database root user This account provides STA complete y Installation Location access to all database functions i Prerequisite Checks A NOTE The STA database root account username is pre set to root and cannot y Enter Root Password be changed I Set up DB Directories T Password Requirements JA Setup Admin Accounts 8 to 31 characters in length with no spaces A ea uo Datuberce ACEN Must contain at least one capital letter and one number except T R OSST Database Root User Enter STA Database Root User Password Confirm STA Database Root User Password Help lt Back Next gt Cancel The STA database root user owns the STA database This account is used internally by the STA application to create the database and it provides full access to all database tables You will not use this account for normal STA operations The username for this account is automatically set to root and cannot be changed This is a MySQL account and is separate from the Linux root user This account will be created during the installation with the credentials you specify Note Make a secure record of these account credentials To protect your site security usernames and passwords are purposely not preconfigured nor hard coded A 20 StorageTek Tape Analytics Installation and Conf
12. For example Linux_Version name Oracle Linux releasever Update x installation media copy S basearch baseurl http public yum oracle com repo OracleLinux 0L6 x base S basearch gpgkey http public yum oracle com RPM GPG KEY oracle ol6 gpgcheck 1 enabled 1 Save and exit the file Install Required Linux Packages Additional RPM packages are required for STA installation and operation The STA installer will check for the following packages and if they are not present STA installation will fail E O h O O O Note RPM package names are case sensitive binutils d gcc c libstdc compat libcap1 1 glibc M libstdc devel compat libstdc 33 i686 L glibc devel L net snmp utils cronie Ly libaio d rpm build expect LJ libaio devel 4 sysstat gcc L libgce xorg x11 utils 2 10 StorageTek Tape Analytics Installation and Configuration Guide Post Installation Tasks You can use a variety of methods to install the required RPM packages This procedure describes how to use yum The yum package install command checks for the most current version of the package for your Linux version and then installs the package and any dependencies Depending on your Linux installation some of these packages may have already been installed If a package is already installed and at the most current version the system notifies you 1 Open a terminal session on the STA server 2 Proceed as follows Ify
13. The oracle storage home location This can be an existing Oracle Storage Home or a new Oracle Storage Home STORAGE_HOME Oracle Root access passsword var ROOT ACCESS PASSWORD JvPABRzrtVP7LZT1Vin0Qg RESPONSEFILE_LOC Installers SilentInstall rsp KEYFILE_LOC Installers sk1414705403180 DBDATA LOC DBDATA LOC dbdata DBBACKUP LOC DBBACKUP LOC dbbackup Weblogic Admin Name Var WEBLOGIC ADMIN NAME weblogic Weblogic Admin Password Var WEBLOGIC ADMIN PASSWORD k5 c60q1KGwQdUje6C CgA Weblogic Admin ConfirmPassword Var WEBLOGIC ADMIN CONFIRMPASSWORD k5 c60q1KGwQdUj e6C CgA Run the Silent mode Installer Use this procedure to install STA using the silent mode installer 1 Change to the STA installer location For example cd Installers B 6 StorageTek Tape Analytics Installation and Configuration Guide STA Silent mode Installer Tasks 2 Start the STA silent mode installer See STA Installer Command Options on page B 10 for full definitions of these parameters sta_installer_linux64_version bin silent responseFile response file invPtrLoc pointer_file Where version is the version of the STA installer you have downloaded a silent indicates silent mode this parameter is required a responseFile response_file specifies the absolute path of the silent mode installer response file this parameter is required a _ invPtrLoc pointer_file specifies the absolute path of the Oracle centr
14. This page lets you view and define various Secure Sockets Layer SSL settings for ths server instance These settings help you to manage the security of message transmissions Identity and Trust Locations Keystores Change Indicates where SSL should find the server s identity certificate and private key as wel as the server s trust trusted CAs More Info Identity Private Key Location from Custom Identity Keystore The keystore attribute that defines the location of the private key fle More Info Private Key Alias staSelfGenKey The keystore attribute that defines the string alas used to store and retrieve the server s private key More Info a amp Private Key Passphrase eoveeeesecoeocece The keystore attribute that defines the passphrase used to retrieve the server s private key More info Confirm Private Key Passphrase CELTTTTTTTTTTTTTT Certificate Location from Custom Identity Keystore The keystore attribute that defines the location of the trusted certificate More Info Trust Trusted Certificate Authorities from Java Standard Trust Keystore The keystore attribute that defines the location of the certficate authorities More Info 15 Click Save 16 In the Trusted Certificate Authorities section click Advanced D 6 StorageTek Tape Analytics Installation and Configuration Guide Security Certificate Configuration Tasks Settangs for staia Configuration siso loyo Deg Monisme Cotu Oepteew
15. Database Reports User StorageTek Tape Analytics Installation 2 1 0 ORACLE Database Reports User Welcome y A Enter a username and password for the STA database reports account STA uses y Installation Location this account for internal database access I Prerequisite Checks y Username Requirements y Enter Root Password 1 t 16 characters in length I E gt Y Set up DB Directories All usernames must be unique I AK Setup Admin Accounts Password Requirements o3 gt Aw Setup Database Accounts 8 to 31 characters in length with no spaces i Must contain at least one capital letter and one number except Database Root User E OCS i Y Database Application User w Database Reports User Enter STA Database Reports Username starpt Enter STA Database Reports Password eeeeeeee Confirm STA Database Reports Password Help lt Back Next gt Cancel The STA database reports account is a MySQL account used by non STA and third party applications to connect to the STA database The account provides read only access to selected database tables You will not use this account for normal STA operations This account will be created during the installation with the credentials you specify Note Make a secure record of these account credentials To protect your site security usernames and passwords are purposely not preconfigured nor hard coded Screen Fields Enter Username Type th
16. If the connection between WebLogic Server and the external authentication server is to be secured through SSL you must perform the following activities a Ensure that the SSLEnabled attribute is selected on the Provider Specific screen See Task 2 Define Provider specific Information on page E 10 for instructions Create and configure a custom trust keystore in WebLogic Server for use with the external authentication server See Fusion Middleware Securing Oracle WebLogic Server for instructions Authentication Provider Configuration Process Overview This section summarizes the tasks required to configure one or more external authentication providers for STA See the referenced tasks for detailed instructions 1 Prepare the external provider to authenticate STA users and gather configuration information required by WebLogic Server See Prepare the External Authentication Provider for STA Authentication on page E 5 for instructions 2 Configure WebLogic Server to use external authentication providers For each provider perform all of the following tasks in the order indicated a Add the external authentication provider to the WebLogic active security realm See Task 1 Add an External Authentication Provider on page E 8 for instructions b Configure provider specific information for the authentication provider See Task 2 Define Provider specific Information on page E 10 for instructions c Set the JAAS control flag f
17. Network Timeout snmpget v3 u STAsnmp a SHA A authpwd1 x DES X privpwd1 I authPriv 192 0 2 20 1 3 6 1 4 1 1211 1 15 3 1 0 Timeout No Response from 192 0 2 20 Example 6 3 Failed snmpget Command Invalid Password snmpget v3 u WrongUsr a SHA A authpwd1 x DES X WrongPwd I authPriv 192 0 2 20 1 3 6 1 4 1 1211 1 15 3 1 0 snmpget Authentication failure incorrect password community or key 3 Test the SNMP v2c connection snmpget v2c c stasnmp l authPriv library_IP_addr Where a v2c indicates SNMP v2c cstasnmp indicates the SNMP v2c community string a lauthPriv indicates that privacy is performed on the command _ library_IP_addris the IP address of the public port on the library 4 Ifboth SNMP connection tests are successful you can quit this procedure If either test fails proceed to the next step to troubleshoot suspected network issues as necessary 5 Confirm packet routing from the STA server to the library traceroute I library_IP_addr Where uppercase I indicates to use Internet Control Message Protocol ICMP echo request packets instead of User Datagram Protocol UDP datagrams a library_IP_addris the IP address of the public port on the library The output shows the number of hops and the round trip time to reach each one The round trip time the last line in the command output should be less than one second If it is not confirm the network s performance with y
18. What is the response file used for i for Install d for Deinstall i Enter system root password Confirm system root password Enter mySQL DB root password Confirm mySQL DB root password Enter STA user password Confirm STA user password STA Silent mode Installer and Deinstaller B 5 STA Silent mode Installer Tasks Enter Weblogic console password Confirm Weblogic console password Enter STA DB Application password Confirm STA DB Application password Enter STA DB Report password Confirm STA DB Report password Enter STA DBA password Confirm STA DBA password 7 After the utility has completed verify that the encryption key file has been created in the directory where the response file is located This is a hidden file with a randomly generated name that starts with sk For example Is la Installers sk oh 1 oracle oinstall 17 Sep 22 12 00 sk1414440339833 8 View the response file and verify the following values a The RESPONSEFILE_LOC has been updated with the correct response file location a The KEYFILE_LOC has been updated with the correct encryption key file location a All passwords have been updated with an encrypted value Example B 4 is a sample of the first part of the file showing proper values Example B 4 Sample Installer Utility File After Using the Build Utility view Installers SilentInstall rsp ENGINE DO NOT CHANGE THIS Response File Version 1 0 0 0 0 GENERIC
19. a The RESPONSEFILE_LOC has been updated with the correct response file location a The KEYFILE_LOC has been updated with an encryption key file location Example B 8 is a sample file showing proper values Example B 8 Sample Deinstaller Response File After Using the Build Utility view Installers SilentDeinst rsp ENGINE DO NOT CHANGE THIS Response File Version 1 0 0 0 0 GENERIC This will be blank when there is nothing to be de installed in distribution level SELECTED _DISTRIBUTION STA_Install 2 1 0 0 0 Root access passsword var DEINSTALL ROOT ACCESS PASSWORD zMZJYDbrhiRZUQL35r7uEg RESPONSEFILE_LOC Installers silentdeinstall rsp KEYFILE_LOC Installers sk1414700056981 Run the Silent mode Deinstaller Use this procedure to deinstall STA using the silent mode deinstaller 1 Log in as the Oracle install user 2 Change to the STA home directory For example cd Oracle StorageTek_Tape Analytics 3 Change to the STA utilities directory ed oui bin 4 Start the STA silent mode deinstaller See STA Installer Command Options on page B 10 for full definitions of these parameters deinstall sh silent responseFile response_file invPtrLoc pointer file Where a silent indicates silent mode this parameter is required m responseFile response_file specifies the absolute path of the STA deinstaller response file this parameter is required a invPtrLoc pointer_file specifies the absolute path of the
20. 2 1 0 64 124_linux64 2 zip rw r r 1 oracle oinstall 1599220560 Oct 23 13 01 sta_install_ 2 1 0 64 124 linux64 bin chmod u x sta_install bin chmod utr sta_install zip 1s la rw r r 1 oracle oinstall 5964 Oct 23 16 14 silentInstallUtility jar Installing STA 3 11 STA Installation Tasks Install STA 10 rw r r 1 oracle oinstall 1275158996 Oct 23 13 35 sta_install_ 2 1 0 64 124_linux64 2 zip rwxr r 1 oracle oinstall 1599220560 Oct 23 13 01 sta_install_ 2 1 0 64 124 linux64 bin Review the STA Release Notes which are included in the installer download package Use this procedure to run the STA installer You can install STA using either the graphical or silent mode See STA Installer Modes on page 3 7 for details 1 In a terminal window connect to the STA server and log in as the Oracle install user See Oracle install user on page 3 1 for details Change to the STA installer location see STA installer location on page 3 2 for details For example cd Installers Launch the STA installer with one of the following commands To use the STA graphical installer sta_install_version_linux64 bin Where version is the version of the STA installer you downloaded For example sta_install_2 1 0 64 124 linux64 bin This mode requires an X11 display See Appendix A STA Graphical Installer and Deinstaller Screen Reference for instructions To use the STA silent instal
21. 3 4 T trap recipients adding 8 25 U upgrading STA 8 1 user accounts MySQL requirements 3 3 WebLogic requirements 3 3 V v2c mode configuration process F 1 create trap recipient F 2 Index 1 enable F 3 overview F 1 volume label formatting 4 4 volume serial numbers duplicate 4 5 Index 2
22. Display the user attributes to confirm that all information has been entered correctly For example cat etc passwd grep sta stabck x 98765 54321 STA database backup user home stabck bin bash 7 Assign exclusive ownership and access rights for the directory to the STA Backups user and group For example chown R stabck stabckgr STAbackups chmod R 700 STAbackups chmod 755 home stabck In this example the R option is used to recursively assign the attributes to the directory and its files 8 List the directory to confirm that all information has been entered correctly For example ls la grep STA drw 2 stabck stabckgr 4096 Oct 19 14 20 STAbackups Configure the STA Database Backup Service Use this procedure to configure the STA database backup service You can designate a directory where the backup files will be copied Oracle recommends that this directory be located on a remote backup server Your configuration settings take effect as soon as the service wakes from its current sleep interval and processes new settings or you manually restart the STA Services daemon Restart the STA Services Daemon optional on page 7 2 1 On the STA server log in as the system root user 2 Display the current STA Backup Service settings using the staservadm Q command This example shows that the service is not yet configured and is therefore not performing backups staservadm Q 7 4 StorageTek Tape
23. Locate the STA installer location or create the directory if it does not exist See STA installer location on page 3 2 for details For example mkdir Installers 8 Obtain the password for the Linux root user The STA installer requires root access to perform certain tasks and will prompt for the password 9 Choose user names for the WebLogic Administrator STA Administrator and MySQL accounts that will be created during the installation See User Accounts for Managing STA on page 3 3 for details 10 Choose port numbers for the configurable internal and external ports required for STA operations Ensure that the external ports are open on the required networks See Ports Used by STA on page 3 4 for details 11 Obtain your site s domain name for configuring Oracle s Remote Diagnostics Agent RDA See the STA User s Guide for details 3 8 StorageTek Tape Analytics Installation and Configuration Guide STA Installation Tasks Verify Installation Prerequisites Use this procedure to verify prerequisites before running the STA installer This procedure is optional but if any of these prerequisites are not met the STA installation will fail See the STA Requirements Guidefor a complete list of installation requirements All these steps are performed on the STA server Contact your Linux administrator if you need assistance Note STA installation assumes 64 bit Linux has been installed with the Linux RPM packages sp
24. Organization name Configuring External Authentication Providers for STA E 27 Tasks for Configuring IBM RACF Authentication Providers unitname Organizational unit name country Country clientlabel Label for the server certificate TBICLIENT calabel Label for certificate authority specified in the CA certificate definition b Connect the CA SERVER and CLIENT certificates to the keyring specified in the PAGENT configuration RACDCERT ID stcuser CONNECT CERTAUTH LABEL calabel RING keyringname USAGE CERTAUTH where stcuser RACF user id associated with the TCPIP address space calabel Label for certificate authority specified in the CA certificate definition keyringname Name of the keyring must match the Keyring specified in the PAGENT configuration RACDCERT ID stcuser CONNECT ID stcuser LABEL serverlabel RING keyingname DEFAULT USEAGE PERSONAL where stcuser RACF user id associated with the TCPIP address space serverlabel Label for the server certificate keyringname Name of keyring must match the Keyring specified in the PAGENT configuration RACDCERT ID stcuser CONNECT ID stcuser LABEL clientlabel RING keyingname USEAGE PERSONAL where stcuser RACF user id associated with the TCPIP address space clientlabel Label for the client certificate keyringname Name of keyring must match the Keyring specified in the PAGENT con
25. You can perform this procedure anytime after STA has been installed See Review STA File System Layout on page 2 2 for the location requirements 1 Log in as the system root user 2 Stop all STA services STA stop all Stopping the staui service Successfully stopped the staui service Stopping the staadapter service Installing STA 3 13 STA Installation Tasks Successfully Stopping the Successfully Stopping the Successfully Stopping the Successfully Stopping the Successfully topped the staadapter service taengine service topped the staengine service eblogic service topped the weblogic service taservd Service topped staservd service sql service topped mysql service BUH H ZTNNH NA n Create the new STA logs directory you want to use for STA and MySQL logs For example mkdir p LOGS_DIR 1log ls ld LOGS_DIR 1log drwxr xr x 2 root root 4096 Jan 20 14 17 LOGS_DIR log Change access permissions to the directory so STA and MySQL can write to it For example chmod 777 LOGS_DIR 1log ls 1d LOGS_DIR 1log drwxrwxrwx 2 root root 4096 Jan 20 14 17 LOGS_DIR log Move the current var log tbi directory to the STA logs directory you have just created mv var log tbi LOGS_DIR 1log ls 1 LOGS_DIR 1log tbi total 20 drwxrwxrwx 2 mysql mysql 4096 Jan 7 10 45 backups drwxrwxrwx 3 mysql mysql 4096 Jan 7 10 45 db drwxrwxrwx 2 mysql mysql 4096 Jan 7 11 3
26. You can reorder your Authentication Providers using the ist below By reordering Authentication Providers you can alter the authentication sequence Select authenticator s in the ist and use arrows to move them up and down in the ist dE Authentication Providers Available External OpenLDAP Server DefaultAuthenticator DefaultidentityAsserter 5 When the providers are listed in the order you want click OK E 18 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Reorder Authentication Providers OK Cancel Reorder Authentication Providers You can reorder your Authentication Providers using the ist below By reordering Authentication Providers you can alter the suthentication sequence Select authenticator s in the ist and use arrows to move them up and down in the ist A Authentication Providers Available DefaultAuthenticator DefaultidentityAsserter a Provider that performs LDAP authenticaton 1 0 My AD Server Provider that performs LDAP authentication 1 0 Rb cocina Showing 1 to 40f 4 Previous Next 6 Proceed to Task 5 Apply All Configuration Changes on page E 19 Task 5 Apply All Configuration Changes Use this procedure to apply all changes you have made during this editing session The changes are applied to WebLogic Server and STA 1 Inthe Change Center section click Activa
27. as part of the upgrade preparation you will ensure that all required RPM package levels are installed and as a final check the STA installer will also notify you if any packages are missing Default WebLogic Port Numbers The default WebLogic Administration console port numbers have changed for STA 2 1 x If you are currently using the old default port numbers you may want to change to the new default values The new and old default port numbers are as follows a New defaults for STA 2 1 0 and higher 7019 HTTP and 7020 HTTPS a Old defaults STA 1 0 x and STA 2 0 x 7001 HTTP and 7002 HTTPS Upgrading to STA 2 1 x 8 5 Upgrade Preparation Tasks Note The WebLogic Administration console ports are external Your network administrator may need to configure firewalls and routers to open communication between the STA server and the clients accessing the WebLogic Administration interface Required Ports for STA 2 0 and Higher Note This change was introduced in STA 2 0 so is relevant only if you are upgrading from STA 1 0 x In STA 2 0 STA ports were added for the StaUi and StaEngine managed servers The default STA managed server port numbers for STA2 0 x and STA 2 1 x are as follows a StaUi 7021 HTTP and 7022 HTTPS a StaEngine 7023 HTTP and 7024 HTTPS a StaAdapter 7025 HTTP and 7026 HTTPS Note The StaUi ports are external Your network administrator may need to co
28. dev mapper vg_sta_server lv_root 51606140 42896756 6087944 88 Note You can optionally specify a different working directory when you start the STA installer See STA installer working location on page 3 3 for details Installing STA 3 9 STA Installation Tasks 4 Verify SELinux is disabled If you have followed the instructions in Post Installation Tasks SELinux should already be disabled see Disable SELinux on page 2 8 for details sestatus SELinux status disabled 5 Verify Linux firewall IPTables is stopped If you have followed the instructions in Post Installation Tasks IPTables should already be stopped see Disable the Linux Firewall on page 2 8 for details service iptables status iptables Firewall is not running Note If your site requires the IPTables service to be running you can start the service after you have installed STA configured the libraries and confirmed that STA is monitoring the libraries After starting IPTables you should reconfirm that STA is monitoring the libraries 6 Stop and deconfigure SNMP services To avoid network port collisions and other issues the STA server must not be running other SNMP services The STA installer will quit in either of the following situations The snmpd and snmptrapd daemon services are running a UDP ports 161 SNMP and 162 SGNMPTRAP are not available Perform the following steps as required a Display
29. opt oracie orainventory Browse Enter the full path for the directory Operating System Croup oinstall v Specify a Linux Croup ID that has write permission to the central inventory directory Help OK Cancel The Oracle central inventory directory is used to keep track of the names and locations of all Oracle software installed on this server All STA installation and deinstallation logs are saved automatically to this location To ensure that other users in the Oracle install group have access to this directory it should be separate from the Oracle install user s home directory Home directories may not have proper permissions for the Oracle install group This screen is part of the Oracle Universal Installer If you follow the recommended practices for registering the Oracle central inventory location this screen appears only the first time you install STA on this server Subsequent installations will automatically find the location without prompting you See Register the Oracle Central Inventory Location on page 3 15 for details Screen Fields Inventory Directory Enter the name of the directory you want to designate as the Oracle central inventory directory The default is USER_HOME oralnventory You must specify an absolute path or click the Browse button to navigate to an existing directory a Ifyou specify an existing directory the Oracle install user must have full permissions to it a If you specify a directory that do
30. see Figure 8 2 Two server Upgrade Task Overview for the task order Task 1 Dump the Old STA Database on page 8 15 Task 2 Transfer the Old Database Dump on page 8 17 Task 3a Install the New Linux Version Upgrades From STA 1 0 x on page 8 18 Task 3b Deinstall the Old STA Version Upgrades From STA 2 0 x and Higher on page 8 18 Task 4 Install the New STA Version on page 8 18 Task 5 Dump the New STA Database optional on page 8 19 Task 6 Transfer the Old STA Database to the STA Server on page 8 20 Task 7 Process and Load the Old STA Database on page 8 21 Task 8 Upgrade the Old Database on page 8 22 Task 9 Configure the New STA Version on page 8 24 Recover a Failed Database Upgrade optional on page 8 26 Task 1 Dump the Old STA Database Use this procedure to perform a full dump of the old current STA database 1 Use the following steps to display the size of your current STA database a Log in to STA using an STA administrator username b Click About in the Status Bar c Inthe About dialog box scroll down to where the Database Current Size is displayed and record the value Use the following steps to verify that the location where you want to dump the database has sufficient space Upgrading to STA 2 1 x 8 15 Upgrade Tasks 1 Open a terminal session on the STA server and log in as the system root user 2 Display the space available in the database dump destination and ve
31. u stabck Backup Password p ARERR Backup Directory d Database Username U Database Password P home stabck STAbackups sta_dba REKEKEKEEE 4 Review the command output to verify that the values have been set correctly Review the STA Resource Monitor Utility Preferences Review the option descriptions in Table 7 2 and define your settings A default value of 1 indicates the attribute has not been configured Configuring STA Services 7 5 STA Services Configuration Tasks Table 7 2 STA Resource Monitor staresmonadm Attributes Option Attribute Description Default Value Your Value T time Daily report time Time of day STA sends a standard daily 00 00 report The report is sent automatically every 24 hours at approximately this time The actual time is sometime within sleep interval seconds after this time Format is hh mm using 24 hour time i interval Sleep interval Number of seconds the STA Resource 300 Monitor waits between scans n nag Nag mode Indicates how frequently STA alerts if any Off high watermarks are reached If set to on STA sends alert emails every time the system is scanned If set to off alerts are simply noted in the standard daily report U dbusr Database Database username authorized to perform NA username queries against the information_schema tables and the MySQL server internal system global variables You should specify either the
32. 2 7 Post installation a Disable SELinux on page 2 8 Disable the Linux Firewall on page 2 8 Disable Access Control on page 2 9 Set Up the Network Proxy on page 2 9 Ensure Proper Setup of yum optional on page 2 9 Install Required Linux Packages on page 2 10 aoo O gm F Y DN Ensure Proper Setup of SSH on page 2 11 Installing Linux 2 1 Preparation Tasks 8 Ensure Proper DNS Settings on page 2 11 9 Disable Name Services on page 2 12 10 Ensure Local Browser Functionality optional on page 2 12 Table 2 1 Linux Installation Tasks Category Task Preparation Review Related Documentation on page 2 2 N Download the Linux Installer Media Pack on page 2 4 Installation Gather Required Information on page 2 5 Install Linux on page 2 5 P Run the Linux Setup Agent on page 2 7 Post Installation Disable SELinux on page 2 8 Disable the Linux Firewall on page 2 8 Disable Access Control on page 2 9 Set Up the Network Proxy on page 2 9 Ensure Proper Setup of yum optional on page 2 9 Install Required Linux Packages on page 2 10 Ensure Proper Setup of SSH on page 2 11 Ensure Proper DNS Settings on page 2 11 een eaPpe y Disable Name Services on page 2 12 10 Ensure Local Browser Functionality optional on page 2 12 Preparation Tasks Before installing Linux on the STA server perform the procedures in the following sect
33. 25 27 41 45 61 63 65 81 85 100 m Version Select v2c Community Specify the SNMP v2c trap community string for example stasnmp Click Apply to add the trap recipient Using the SL150 user interface 1 2 3 4 5 Log in to the library In the navigation tree select Settings Select the SNMP tab In the SNMP Trap Recipients table select Add Trap Recipient Complete the Add Trap Recipient screen as follows Host Address IP address of the STA server Trap Level Comma separated list of trap levels the library should send to STA 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 a Version Select v2c Community Name Specify the SNMP v2c trap community string for example stasnmp Click OK to add the trap recipient Enable SNMP v2c Mode for STA By default SNMP v2c is disabled on STA Use this procedure to enable it 1 2 Establish a terminal session with the STA server and log in as the system root user Change to the STA configuration files directory cd Oracle_storage_home Middleware user_projects domains TBI Where Oracle_storage_home is the Oracle storage home location defined during STA installation Edit the SNMP version properties file vi TbiSnmpVersionSupport properties Change the SNMP v2c parameter to true Vac true Save and exit the file Configuring SNMP v2c Mode F 3 SNMP v2c Configuration Tasks 6 Stop and restart all STA processes to activate the cha
34. 3 1 Oracle central inventory registration Beginning with STA 2 1 0 the STA installer uses the Oracle central inventory location which is a convention common to many Oracle products After STA installation is complete you should register the Oracle central inventory location on the STA server by running the provided registration script Registering the location will facilitate the installation of STA upgrades in the future See Register the Oracle Central Inventory Location on page 3 15 Browser usage on the STA server For optimal STA server performance you should not run a browser on the STA server to access the STA user interface or for any other purpose Run browsers on platforms separate from the STA server See Ensure Local Browser Functionality optional on page 2 12 Library Configuration for STA Library and drive firmware levels To ensure richer library and drive data use the most current library and drive firmware levels See the following sections a STA Requirements Guide for library firmware requirements a STA Requirements Guide for drive firmware requirements Important library configuration steps To ensure complete compatibility with STA some library parameters must be set to specific values Be sure to make the following changes before you configure the library connection to STA so the libraries send data to STA in the correct format a For SL8500 libraries make sure the complex ID is unique for each mo
35. 80 104 54 10 80 175 36 eron rT erT OTTS TO PITTS SOO OOo TOTS OS eib18 38500_2 10 580 104 98 10 580 175 36 0x80001f880436303030313030343337 GOOD 00 15 00 US Mountain 2014 08 enon tne an The Connection Test Status message box appears displaying results for the MIB Walk Channel Trap Channel and Media Validation Support tests Connection Test Status for Library MIB Walk Channel Good SNMP V3 Trap Channel Good SNMP V3 Media Validation Support Good x 3 Click OK to dismiss the message box The Monitored Libraries table is updated with the results of the test Monitored Libraries Z XxX Qa B Recent SNMP Trap Automated Daly Ubrary Engine ID Communication Data Refresh Livary Time Zone Status Time Lbrary IP Address es Last Suc Connect Ubrary Name Ubrary Complex SE OO T s7 Gaa RU 7 Ps7 j a ais y eib18 SL8500_2 10 80 104 95 10 80 175 36 0x80001f880436303030313030343337 GOOD 00 15 00 US Mountain 2014 05 a If the Library Complex field is blank it will be supplied after you perform a manual data collection Library Engine ID indicates the unique SNMP engine ID for the library a Last Connection Attempt indicates the date and time when the connection test was initiated Last Successful Connection indicates the date and time when the test was completed if successful Last Connection Status indicates the results of the test If the test fails STA provides information in the Last C
36. Analytics Installation and Configuration Guide STA Services Configuration Tasks Contacting daemon connected Que Current STA Backup Service Settings rying Preferences Configured File Transfer S Full Backup T Sleep Interval i Backup Hostname s Backup Username u Backup Password p Backup Directory d Database Username U Database Password P no SCP 00 00 300 sec 3 Using Table 7 1 as a reference set the attribute values with the staservadm command You can submit the attributes in separate commands or combine them into one For example staservadm S T 11 00 i 350 s stabaksvr u stabck p bckpwdi d home stabck STAbackups U sta_dba P password1 The utility sets each value included in your command and then displays all current settings For example Co Se Se Se Se Se Se Se Se B GCE eth r Gh ck cet ar e et Se Don tacting daemon connected ting File Transfer Type SCP ting Sleep Interval 350 ting Backup Hostname stabaksvr ting Backup Username stabck ting Backup Password SAREE IS ting Backup Directory home stabck STAbackups ting Full Backup Time 11 00 ting Database Username sta_dba ting Database Password e Current STA Backup Service Settings Configured yes File Transfer S SCP Full Backup T 11 00 Sleep Interval i 350 sec Backup Hostname s stabaksvr Backup Username
37. Builtin SSL Validation Only Outbound Certificate Builtin SSL Validation Only Validation E a Use ISSE SSL Save 18 Click Save Spedfies whether to ignore the installed implementation of the weblogic security SSL Hostname Verifier interface when this server is acting as a dent to another applicaton server More Info The name of the dass that implements the wedlogc searity 5S HostrmevVerifier interface More Indicates the number of times WebLogic Server can use an exportable key between a domestic server and an exportable cient before generating a new key The more secure you want WebLogic Server to be the fewer times the key should be used before generating a new key More Info Sets whether the cient should use the server certificates key as the cient identity when initiating an outbound connection over https More Info The form of SS that should be used More info The name of the Java dass that implements the wedloge security ad CertAuthenticator dass which is deprecated in this release of WebLogic Server This field is for Compatiity security only and is only used when the Realm Adapter Authentication provider is configured More Info Indicates whether warning messages are logged in the server log when SSL connectors are rejected More Test if the AlowUnEncryptedNuiCipher is enabled More Indcates the cient certificate validation rules for inbound SSL More Info Indicates the s
38. DES privPass priv_password Where nameis the SNMP v3 user name auth_password and priv_password are the authorization password and privacy password Note For SL3000 and SL8500 libraries enclose all variables in single quotes Example 5 1 Example 5 1 Create SNMP v3 User on SL3000 or SL8500 SL3000 gt snmp addUser version v3 name STAsnmp auth SHA authPass authpwd1 priv DES privPass privpwd1 Example 5 2 Create SNMP v3 User on SL500 SL500 gt snmp addUser version v3 name STAsnmp auth SHA authPass authpwd1 priv DES privPass privpwdl 2 List the SNMP users to verify that the SNMP v3 user has been added correctly gt snmp listUsers Using the SL Console SL500 libraries only 1 From the Tools menu select System Detail 2 Inthe navigation tree select Library 3 Select the SNMP tab then select the Add Users tab 4 Complete the Add Users tab as follows m Version Select v3 a UserName The name of the SNMP v3 user m Auth Select SHA Configuring SNMP on the Libraries 5 7 Library SNMP Configuration Tasks 5 m AuthPass Specify an authorization password a Priv Select DES PrivPass Specify a privacy password Click Apply Using the SL150 user interface 1 2 3 In the navigation tree select SNMP In the SNMP Users section select Add SNMP User For Version select v3 and then complete the information as follows a User Name The name of the SNMP v3 user Authen
39. Drive Clean Warning SL3000 and SL8500 only s sesssssssssssstsstestissserstssssesttsnteestisnsesstsntesssesn ee 4 4 Volume Label Format SL500 and SL150 only ssesssssssesssssississesssesissiessnsnessentsnsisnnsnsnrensessesneene 4 4 SCSI FastLoad Option SL500 only sssssssssesssssessessessesstssesssstinsisnesnsnstesinsesnesnenstenienesntnnteneenesneens 4 5 Duplicate Volume Serial Numbers s ssssssssssssissesisssestiseessentestesnesnetenstssesnestentesresnententennisnenenteneens 4 5 Library User Interfaces noron ing tei At ets hte IE e a a a E ESE 4 5 Library CLT Usage Tips nieni aa a a SS RE 4 5 Library Configuration Script optional sssssesssssssssessestsssessessestensessesnestentisresnententenressesneneennens 4 6 Library Feature Configuration Tasks s ssesssesessseseessestetestessestsntestessententessinnsnentesrisnesnententeseesnts 4 6 Eog tothe Library anse a e ea an eaae Eae Nae EEr Saera E e eaa Ea E AED Nea aeS PELEA EEN Eaei 4 7 Verify the Library Firmware Version sssesessesssssiesississssssesississtiseesnentessisnnsnentennisnesntenteneeneneess 4 7 Verify the Drive Controller Card Version SL3000 and SL8500 only eects 4 8 Enable ADI on the Library all libraries except SL150 oo ecesesecsssesesesescseseeececsesnseseeceesnens 4 9 Ensure the Correct Library Complex ID SL8500 Only cccccscceseseeeeteteeseeeeseseeeeceesesesneneneaees 4 9 Set the Drive Clean Warning optional SL3
40. File System Layout on page 2 2 for details about these directories tmp Oralnstalltimestamp This directory includes logs for in progress installations or deinstallations Following is a sample listing of logs you might see in this directory instal1l2014 09 24 04 14 04PM log installProfile2014 09 24 04 14 04PM log launcher2014 09 24 04 14 04PM log Oracle_storage_home oralnventory logs Where Oracle_storage_home is the Oracle storage home location defined during STA installation This directory includes logs for installations and deinstallations that have completed successfully Some logs such as error or patch logs are included only as applicable Following is a sample listing of logs you might see in this directory 2014 09 24 _02 57 41PM log instal12014 09 24 02 57 41PM log instal12014 09 24 02 57 41PM out installActions2014 09 24_02 57 41PM log installProfile2014 09 24 02 57 41PM log installSummary2014 09 24_02 57 41PM txt launcher2014 09 24 02 57 41PM log1 OPatch2014 09 24 02 58 47 PM log oraInstal12014 09 24_02 57 41PM err oraInstal12014 09 24_02 57 41PM out STA_logs install By default STA_logs is located at var log tbi You can optionally relocate this directory to a location of your choice any time after STA installation See Relocate the STA Logs Directory optional on page 3 13 for instructions This directory includes logs for installations and deinstallations that have completed successfully or failed It
41. HH a Enter staEngine HTTP Port 7023 Enter staEngine HTTPS Port 7024 Help lt Back Next gt Cancel The staEngine managed server ports are used for internal STA server communication only Note Make a secure record of these port numbers they cannot be changed once STA is installed To protect your site security these numbers are purposely not preconfigured nor hard coded Screen Fields Enter HTTP Port Enter the HTTP port number for unsecure access to the staEngine managed server Typically this port number is 7023 Port numbers must be unique and available Enter HTTPS Port Enter the HTTPS port number for secure access to the staEngine managed server Typically this port number is 7024 Port numbers must be unique and available Screen specific Buttons None A 28 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens c StorageTek Tape Analytics Installation 2 1 0 5 STA Adapter va y Mecoms Enter HTTP and HTTPS port numbers for the staAdapter managed server These y installation Location ports are for internal STA server communication only Prerequisite Checks Enter Root Password T T Set up DB Directories T Set up Admin Accounts ha Set up Database Accounts T Enter Communication Ports y WebLogic Admin Console y STA Engine STA Adapter I T j Emer staAdapter HTTP Port 7025 Enter staAdapter HTTPS Port 7
42. Java Standard Trust Keystore geeecceseceseseee Passphrase Confirm Java Standard Trust sesseeooocooooooe Keystore Passphrase L Seve 12 Click Save 13 Select the SSL tab _ The path and fie name of the trust keystore More The type of the keystore Generally fisis KS More The password for the Java Standard Trust keystore This password is defined when the keystore is ceated More info Configuration Protocols Logging Debug Monitoring Control General Cluster Services Keystores ssu Federation services 14 Enter the Private Key Alias and Private Key Passphrase supplied by the MVS system programmer Configuring Security Certificates D 5 Security Certificate Configuration Tasks Note To determine the Private Key Alias use the keytool command at the system command line For example keytool list keystore CLTBI PKCS12DR D080411 storetype PKCS12 Enter keystore password password from the MVS sysadmin Keystore type PKCS12 Keystore provider SunJSSE Your keystore contains 1 entry tbiclient Aug 17 2011 PrivateKeyEntry Certificate fingerprint MD5 9A F7 D1 13 AE 9E 9C 47 55 83 75 3F 11 0C BB 46 Settings for stati Configuration Protocols Logging Debug Monitoring Control Deployments Services Security Notes General Custer Services Keystores SSL Federation Services Deployment Migraton Tuning Overload Health Monitoring Server Start Web Services Save
43. Linux on the STA server before installing STA Post installation upgrades are necessary in the following situations a The new version of STA requires a new version of Linux For example STA 1 0 x requires Linux 5 while STA 2 0 and subsequent versions require Linux 6 therefore to upgrade to STA 2 0 or higher from STA 1 0 x a new version of Linux must be installed which requires a post installation upgrade 8 2 StorageTek Tape Analytics Installation and Configuration Guide Choosing Whether to Use One Server or Two The STA installation framework has changed significantly For example the installer for STA 2 1 0 and subsequent versions use the Oracle Universal Installer framework therefore to upgrade to STA 2 1 0 or higher from any previous version of STA requires a post installation upgrade Choosing Whether to Use One Server or Two For post installation upgrades you can choose to use either one server or two depending on your goals and available resources Automatic upgrades are by nature always done on one server The upgrade tasks are largely the same for the two methods but the tasks are performed in different orders The two methods are discussed in the following sections a Single server Upgrade Method on page 8 3 a Two server Upgrade Method on page 8 4 Single server Upgrade Method Using the single server method you must deinstall STA before you install the new version and upgrade the database on the
44. Location Bar or Address field enter the URL of the WebLogic Administrator console The URL uses one of the following formats http local_host_name port_numberconsole https local_host_name port_number console where ocal_host_name and port_number are the name and port number of the WebLogic Administrator console defined during STA installation The default HTTP port number is 7019 and the default HTTPS port number is 7020 For example https sta_server 7020 console On the Welcome screen enter the WebLogic Administration console username and password defined during STA installation and then click Login ORACLE WebLogic Server 11g Administration Console Welcome Log fo rot nai the aog Server Gomer weblog nemame Passwort eeeeeeee The WebLogic Server Administration Console Home page appears D 2 StorageTek Tape Analytics Installation and Configuration Guide Security Certificate Configuration Tasks ORACLE WebLogic Server Adminstration Console Change Coster Veew changes and restarts cen CA Pe Lock A Edt durian o medify add o Mume Page mas roen n tu omar Intormation amd Resources Lock 5 Et neiphd 7 Cortese apkators Configure Garh fr RAC Oria Source Revert Tack Seana Set yas oree referers Oomam Configurations Now o 1 Semin Pe configs ston Une the Change Center Record WAS Soot Change Corese prefereroes e Mage Cormcle estermore Here tog Ot Preteen
45. Mapping Certificaton Path Keystores An Authentication provider allows WebLogic Server to establish trust by validating a user You must have one Authentication provider in a searity realm and you can configure multiple Authentication providers in a security realm Different types of Authentication providers are designed to access different data stores such as LDAP servers or DBMS You can also configure a Realm Adapter Authentication provider that allows you to work with users and groups from previous releases of WebLogic Server gt Customize this table Showing 1 to 3of3 Previous Next DefauitAuthentcator WebLogic Authentication Provider Lo T DefauitidenttyAsserter WebLoge Idenbdty Assertion provider 10 My AD Server X Provider that performs LDAP authentication 10 Showing Lto 3of3 Previous Next 5 Proceed to Task 2 Define Provider specific Information on page E 10 Task 2 Define Provider specific Information Use this procedure to define provider specific information for each external authentication provider you have added to the WebLogic Server active security realm Before using this procedure you must gather the necessary configuration information from the external authentication provider see Prepare the External Authentication Provider for STA Authentication on page E 5 for instructions E 10 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active D
46. SE Ea ENESENN AE AEE stan sees sbieaebeeeties E 3 Default STA User ROE aaa islets ot Oee a ea ata taap a A Eada e A ea ree edi E 3 Configuring the Authentication Process for Multiple Providers sees e cesses E 3 LDAP Authentication Referrals nas areena Aa a a a N E 3 Using SSL for Communications cciccscccscivivciisstosscisssceevsibisedesvctsavsotoestbessntesecsesssietecteoestbiecvessseviecd E 4 Authentication Provider Configuration Process Overview cccccc cece cece ceceeeeeneceeeeeeees E 4 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers E 4 Prepare the External Authentication Provider for STA Authentication eee E 5 Edit the WebLogic Server Active Security Realm cccc ec ceeeee ee neeesseesesesessseeenenesenenenes E 5 Task 1 Add an External Authentication Provider ccccccccccsscssecsscsseesscessesssesceeesesceseessecssessecaes E 8 Task 2 Define Provider specific Information cccccccccce eee ceeeseececeeeeeeessseseesneneseseneeees E 10 Task 3 Set the JAAS Control Flag ccccccccceeeccscsesesescscsesesesescsssesescecsssnsesescscssssseesscessnesesesenes E 15 Task 4 Ensure Proper Order of Authentication Providers ccccc cece eeeeenseeeeeeees E 17 Task 5 Apply All Configuration Changes ccccccsssscessscsssesescsesesesescsesssesesescscsssesesescseseseseeces E 19 Verify Configuration of Authentication Providers ccccccc cece cceeeececeseeseseececesensnecec
47. STA Database DBA Account username or STA Database Root Account username root P dbpwd Database The password assigned to the database NA password username t tolsphwm Database High watermark for the database tablespace 1 tablespace HWM entered as a percentage of the maximum available b backvolhwm Local backup High watermark for the STA database local 1 HWM backups volume sta_db_backup entered as a percentage of the maximum possible d dbvolhwm Database disk High watermark for the STA database 1 volume HWM volume sta_db mysql entered as a percentage of the maximum available logvolhwm Logging disk High watermark for the STA database logs 1 volume HWM STA_logs db entered as a percentage of the maximum available Z rootvolhwm Root volume HWM High watermark for the root volume entered as a percentage of the maximum available X tmpvolhwm Tmp volume HWM High watermark for the temporary directory volume tmp entered as a percentage of the maximum available 4 m memhwm Physical memory RAM HWM High watermark for the total system memory except virtual memory entered as a percentage of the maximum available f from Email from Name or email address that appears in the From field of the standard daily report email StaResMon localhost f recips Email recipients Recipient email addresses entered as a colon delimited
48. Select a keyboard layout and then click Next Select Basic Storage Devices and then click Next Enter a hostname for the STA server and then click Configure Network Select the network adapter name and then click Edit Ensure that Connect automatically and Available to all users are both selected Inthe remaining tabs configure the adapter according to your network administrator s IPv4 or IPv6 specifications You must specify a static IP address for the STA server and at least one DNS server When done click Apply Close and Next Select the STA server s time zone select the System clock uses UTC check box and then click Next Enter and confirm a Linux root password for the server and then click Next Identify a partitioning layout to use on the server a Because STA requires a dedicated server Oracle recommends selecting Use All Space b Select the Review and modify partitioning layout check box and then click Next Installing Linux 2 5 Installation Tasks 16 Use Table 2 2 to modify the file system layout as the default does not meet the minimum requirements for STA Alternatively you can use the system config lvm utility to modify the file system after Linux installation When done click Next 17 When ready select Write changes to disk 18 In the boot loader screen leave all options as is and then click Next 19 In the software selection screen select Basic Server and do not change th
49. Types STA supports the following authentication provider types OpenLDAP a Microsoft Active Directory AD a IBM Resource Access Control Facility RACF Using the WebLogic Administration Console Use the WebLogic Administration console for all STA authentication provider configuration tasks in WebLogic Server See Edit the WebLogic Server Active Security Realm on page E 5 for instructions LDAP Principal User Each external authentication provider must include a user account that WebLogic Server can use to connect to the external provider In WebLogic Sever this user is called the Principal user You can either create a new user account for this purpose or use an existing one See Prepare the External Authentication Provider for STA Authentication on page E 5 for instructions This user must have read and write access to the external provider s authentication directory so WebLogic Server can resolve user and group searches and authentications This user does not need to be assigned to the STA access group see STA Access Group on page E 3 below E 2 StorageTek Tape Analytics Installation and Configuration Guide Considerations for Configuring External Authentication Providers STA Access Group All users requiring access to STA must belong to the STA access group which has the name StorageTapeAnalyticsUser All providers performing authentication for STA must include this group For the DefaultAuthenticator this group
50. Use this procedure to deinstall STA Caution Deinstallation removes all STA database data Before starting this procedure you should perform a full database dump See Task 1 Dump the Old STA Database on page 8 15 for instructions Note To deinstall STA you must log in as a user that is a member of the Oracle install group You cannot deinstall STA as the Linux root user nor any other user with superuser privileges See Oracle install group for details Log in as the Oracle install user Change to the Oracle storage home directory For example cd Oracle Change to the STA installer binary directory cd StorageTek_Tape_Analytics oui bin Launch the STA deinstaller with one of the following commands a To use the STA graphical deinstaller deinstall sh This mode requires an X11 display See STA Graphical Installer and Deinstaller Screen Reference on page A 1 for instructions a To use the STA silent deinstaller deinstall sh silent responseFile response_file Where response_tfile is the absolute path of the previously created response file Before using this mode you must also download the silentInstallUtility jar file and create a response file specifying the installation options See Appendix B STA Silent mode Installer and Deinstaller for instructions Verify Successful Deinstallation Use this procedure to verify that all STA components have been removed from the STA ser
51. Users and Groups Roles and Pokies m e Dm a RDGMS Security Store User Lockout Performance Cic the Lock amp Editbutton in the Change Center to modify the settings on this page The Authentication secondary tab is selected by default Configuring External Authentication Providers for STA E 17 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Settings for myrealm Configuraton UsersandGroups RolesandPolides Credential Mappings Providers Migration Authentication Password Validation Authorizaton Adjudication Role Mapping Auditing Credential Mapping Certification Path Keystores 3 Inthe Authentication Providers table click Reorder gt Customize this table Authentication Providers New Delete ED Name Description DefaultAuthenticator Weblogic Authentication Provider DefauitidenttyAsserter WebLog Identity Assertion provi External OpenLDAP Server Provider that performs LDAP auth New Delete Reorder 4 Inthe Reorder Authentication Providers table arrange the providers in the order you want WebLogic Server to access them from first to last Select the check box of the providers you want to reorder then use the arrow buttons to move them up or down in the list Note The DefaultAuthenticator and the DefaultldentityAsserter must be the first two providers in the list Reorder Authentication Providers LOK Cancel Reorder Authentication Providers
52. a aeaa iaa aaa a Ria 1 2 STA Installatori neesi oh a ole R E E eed Se ee E es 1 3 Library Configuration fOrs TAs esrsge e e e e e e 1 3 SNMP Connections With the Libraries ccccccesecssesseesecescesseseceseeseceseesesseeeceessecseecsecaseeaecseeass 1 4 Data COWNCCHONS isrener haai Hose beatin aa a a aa t 1 4 STA Services Comfgurationiic sii ihisorehssieseadhtsdeuebsiories a EE REE ea E e aE A 1 5 STA Database T nin gissen e N a a ina a a aaa 1 5 Prepare Service Requests for the Libraries and Drives ssss ssssssessessestessisrrsrenterrisresnenrenressesses 1 5 Installing Linux Linux Installation Processen onse Boe ees a aea aaa aata ee eae ce eid Bee ii iai 2 1 Pr paration Tasks 2020s ien orir E E es ERA Speci aan ha ease gthesesh RE G ioe 2 2 Review Related Documentation cccccsccssecssessscsscessesscesseesesseceesseeseecssessecsecssecaecsasensceeseeseeseeeaes 2 2 Review STA File System Layout siescccc ccedivevtsssivecsuiss blvasstsedsivasasstsdveisadsassbavsatssssveiesuesdssevevueadesivtstine 2 2 Download the Linux Installer Media Pack cc ccceessesscessesseecceeceeecescecsecsecsaecsecesseseceecseseeseeenes 2 4 Installation Tasks remitirnos aa E ids arated eintilaninal iria 2 5 Gather Required Informations siisii i ee del aeii obima Es eth wi inate 2 5 stal ENU e Science p a a a a a ea a A a dene ees deta iad ait es 2 5 Run the Lin x Setup Agent aeriinresrirriiiii a RE E A REE E h E 2 7 Post Installation Tasks ro
53. all existing trap recipients and note the index number of the STA recipient snmp listTrapRecipients c Delete the STA trap recipient snmp deleteTrapRecipient id index Where index is the index number of the STA trap recipient 8 24 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks d Re add the STA trap recipient and include the new trap levels in the trap level list See Create the STA SNMP v3 Trap Recipient on page 5 8 or Create the STA SNMP v2c Trap Recipient on the Library on page F 2 for instructions SL150 libraries a Log in to the browser based user interface b From the SNMP menu select SNMP Trap Recipients c Select the STA trap recipient from the list d Select Modify Trap Recipient e Add the new trap levels to the trap level list and then click Save If you are using the two server upgrade method add the new STA 2 1 x server as a trap recipient on each library See Create the STA SNMP v3 Trap Recipient on page 5 8 or Create the STA SNMP v2c Trap Recipient on the Library on page F 2 Configure SNMP Settings in STA Perform these steps for all upgrades These steps are performed in STA 1 2 Log in to STA as an STA administrator user Reenter the configuration settings for the STA SNMP client using the values you recorded before the upgrade see Record Current STA User and Configuration Settings optional on page 8 9 These values must match what i
54. and STA is always through the SNMP v2c protocol therefore you must define an SNMP v2c community string even if you are using the recommended SNMP v3 protocol for SNMP communication The community string is a password or phrase you assign for the STA community Following are requirements STA supports only one SNMP v2c community string You must define the same community string on STA and on all libraries monitored by that STA instance Your libraries may already have one or more SNMP v2c community strings and you can use one of these for STA however Oracle highly recommends defining a new unique SNMP v2c community string for this purpose a Oracle recommends not using the values public or private for the STA community string as these values are well known and present a security risk Oracle recommends using values that are not as easily discovered a fa library includes a community string set to public do not remove it without first consulting Oracle Support in some cases a community string with this value is required for Oracle Service Delivery Platform SDP The community string can only contain alphanumeric characters a z A Z 0 9 Special characters are not allowed Unique SNMP v3 User Following are requirements for the SNMP v3 user STA supports only one SNMP v3 user You must define the same user on STA and on all libraries monitored by that STA instance a Your libraries may already have one or m
55. as follows a To change any of the Installation Details click Back to return to the applicable screen or select the screen link in the navigation pane to go directly to the screen a To save the displayed details in a text file click Save a To install using the displayed values click Install a To cancel the installation click Cancel Screen Fields None Screen specific Buttons Save Click to save the displayed information to a text file with the name STA_Installation_ Profile_timestamp txt In the Open dialog box specify the directory where you want the file to be saved A 32 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Lote cB orhe a 2a ape Install Click to begin the installation Once you click this button you cannot pause or cancel the installation Installation Progress StorageTek Tape Analytics Installation 2 1 0 5 ORACLE Installation Progress va PH Prepare PH Copy PH Generating Libraries GP Performing String Substitutions Mi Linking Setup Saving the inventory Post install scripts Installation Progress v View Successful Tasks View Log az Help The STA installation begins and the screen displays the status of each task Caution Do not close this window or otherwise interrupt the installation while it is in progress as this may leave incomplete installation components on the server If a task fa
56. central inventory directory For example cd opt oracle oraInventory Run the registration script located in that directory createCentralInventory sh Setting the inventory to opt oracle oraInventory Setting the group name to oinstall Creating the Oracle inventory pointer file etc oraInst loc Changing permissions of opt oracle oraInventory to 770 Changing groupname of opt oracle oraInventory to oinstall The execution of the script is complete The Oracle central inventory location and the Oracle install group and are now identified in the Oracle central inventory pointer file etc oralnst loc Installing STA 3 15 STA Installation Tasks 3 16 StorageTek Tape Analytics Installation and Configuration Guide 4 Configuring Library Features for STA For the libraries to send high quality SNMP data to STA selected features must be configured appropriately These features vary by library model You should complete the activities in this chapter before continuing to Chapter 5 Configuring SNMP on the Libraries This chapter includes the following sections a Library Features Affecting STA Data Library User Interfaces Library Feature Configuration Tasks Library Features Affecting STA Data a ADI Interface for LTO Drives on page 4 1 a Dual TCP IP and Redundant Electronics SL3000 and SL8500 only on page 4 2 a Library Complex ID SL8500 only on page 4 3 Drive Clean Warning SL3000 and S
57. click the Browse button to navigate to the directory you want to specify A 8 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens STA Home Display only This is the subdirectory within Oracle Storage Home where STA will be installed This subdirectory is assigned the name StorageTek_Tape_Analytics and it will be created automatically during the installation Screen specific Buttons Browse Click to navigate to the directory you want to specify View Click to display a list of all software currently installed in the Oracle Storage Home directory you have specified For new installations this list is blank Figure A 1 is an example of the display after STA has been installed Figure A 1 Sample Listing of Oracle Storage Home StorageTek Tape Analytics Installation 2 1 0 Installation Location A Welcome i Oracle Storage Home Installation Location This is a central location to host all library products LE JOracie hd Browse STA Home This is the location where StorageTek Tape Analytics 2 1 0 will be installed The directory is automatically determined from Oracle Storage Home Oracle StorageTek_Tape_Analytics Feature Sets Installed At Selected Oracle Storage Home View 5 STA install 2 1 0 0 0 S Storage Product Core Stack Oracle Application Developer Framework 11 1 2 4 Oracle Weblogic Server 10 3 6 Oracle JOK 1 6 0 75 Oracle MYSQL 5 6 18 StorageTek Tape Analy
58. connect to the database primarily User to perform scheduled backups Port Number Worksheets Table C4 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 Installation and Upgrade Worksheets C 3 Installation and Upgrade Worksheets Table C 4 Unconfigurable External Ports STA 2 1 x Port Description Protocol Port Verified Secure Shell Used to log in from the STA server to the STA database SSH 22 backup and the monitored libraries Used for transmitting Simple Network Management Protocol SNMP 161 SNMP requests to the monitored libraries 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 The default WebLogic Administration console ports have been changed for STA 2 1 x Table C 5 Configurable Internal and External Ports STA 2 1 x Default Current STA 2 1 x Port Description Type Protocol Port Port Port Verified Unsecure port for the WebLogic External HTTP 7019 Administration console de
59. details about the requested information Table C 7 SNMP v3 User Configuration Information Required Information Previous Values STA 2 1 x Values SNMP v3 Username SNMP v3 Authorization Password Auth SNMP v3 Privacy Encryption Password Privacy SNMP v2c User Community SNMP v2c Trap Community Installation and Upgrade Worksheets C 5 Post installation Configuration Worksheet C 6 StorageTek Tape Analytics Installation and Configuration Guide D Configuring Security Certificates Oracle supplies self generated security certificates to be used with HTTPS SSL ports During installation STA uses the Java keytool to generate a certificate on the STA server using the server hostname You can optionally replace the Oracle certificate with your own approved certificate from a selected certificate authority for example VeriSign This chapter includes the following section Security Certificate Configuration Tasks Security Certificate Configuration Tasks If you want to use a different security certificate than the default perform these procedures in the order listed Establish the Initial HTTPS SSL Connection on page D 1 Reconfigure WebLogic to use a Different Security Certificate on page D 2 Replace the Oracle Certificate on page D 9 Note These procedures use Mozilla Firefox running on a Windows platform Establish the Initial HTTPS SSL Connecti
60. display help for any CLI command type help and the command name for example help snmp a SL500 library commands are case sensitive SL3000 and SL85000 commands are not To avoid entry errors you can first type a command in a text file and then copy and paste it into the CLI For help with CLI commands type help snmp a You can reduce keystrokes by using the following CLI features Press the Tab key for automatic command completion Press the Up Arrow and Down Arrow keys to scroll through your command history You can modify a previously entered command and then press Enter to execute it To correct a command before you press Enter to execute it use the Left Arrow and Right Arrow keys to move the cursor to the location of the error and then type the correction New characters are inserted at the cursor to delete characters use the Backspace key Library Configuration Script optional STA provides a library configuration script to help you complete the configuration process on the libraries The script prompts for library configuration settings and based on the values you enter the script displays complete commands that you can copy and paste into the library CLI Note It is recommended that you review and understand the library configuration steps in this chapter before initiating the script To initiate the script open a terminal session on the STA server and issue the following command s
61. for communication between STA and the libraries The authentication encryption and message integrity features in SNMP v3 provide a secure mechanism for sending library data SNMP v3 is also required for the STA media validation feature STA media validation is available for supported libraries only see the STA Requirements Guide for details This chapter describes the recommended SNMP v3 configuration Depending on your site requirements however and if security is not a concern you may choose to use the less secure SNMP v2c protocol for one or more libraries See Appendix F Configuring SNMP v2c Mode for SNMP v2c configuration instructions Note While the SNMP v3 protocol is used for SNMP traps and get functions the initial communication handshake between a library and STA is always through the SNMP v2c protocol Configuring the SNMP v3 Protocol on the Libraries On each library you set up SNMP v3 communication between STA and each library by defining the library as an SNMP v3 user and the STA server as an SNMP v3 trap recipient In addition you must specify authorization and privacy mechanisms and Configuring SNMP on the Libraries 5 1 Understanding Library SNMP Configuration for STA passwords For STA the authorization method is always SHA Secure Hash Algorithm and the privacy method is always DES Data Encryption Standard SNMP v2c Community String The initial communication handshake between a library
62. includes logs related to the installation of the WebLogic server and MySQL database as well as logs for installation and configuration of the STA application Following is a sample listing of logs you might see in this directory dbinstall log dbinstall mysqld err dbinstall stadb slow log instal12014 09 24 02 52 09PM log install_weblogic log sta_instal12014 09 24 02 53 22PM log 3 6 StorageTek Tape Analytics Installation and Configuration Guide STA Installation Tasks STA Installer Modes You can install STA using either of the following modes Graphical mode This is the recommended installation mode This mode provides a graphical user interface for installing STA and it requires an X11 display See STA Graphical Installer and Deinstaller Screen Reference for details Silent mode This mode allows you to bypass the graphical user interface and supply the installation options in an XML properties file called the response file See STA Silent mode Installer and Deinstaller on page B 1 for details This mode is useful for unattended installations and for installing STA on multiple machines By using a response file you can supply a single set of parameters and automate the installation You can run the silent mode installer either from a script or from the Linux command line STA Installation Tasks To install STA perform all the following tasks in the order listed Identify or Create Information Required for the
63. localhost Note If you see the message Can t connect to local MySQL server the MySQL server is not running Make sure you have started MySQL Step 3 Task 6 Transfer the Old STA Database to the STA Server Note This procedure applies to the single server method only Use this procedure to transfer the backup of the old database to the STA 2 1 x server 1 If you have not done so already stop all STA services STA stop all 2 Transfer the database The p option on for SCP preserves timestamp values scp p backup_host path_to_dump_file dump_file_name sql gz local_path In Example 8 5 SCP is used to transfer the compressed database dump file Dec14_ dump sql gz from dbdumpfiles on host backup1 to the dbdumpfiles folder on the STA 2 1 x server Example 8 5 Old Database Transfer to New STA Server scp p backup1 dbdumpfiles Dec14_dump sql gz dbdumpfiles 3 Perform a checksum of the transferred file Verify the checksum value matches the one you received in Task 1 Dump the Old STA Database on page 8 15 cd path_to_dump_file cksum dump_file_name sql gz 8 20 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks Task 7 Process and Load the Old STA Database Use this procedure to decompress the old database and reinstate it on the STA 2 1 x server The decompressed database may require 10 to 15 times as much space as the compressed database 1 If
64. not stop and restart STA using the STA command See the STA Administration Guide for command usage details 9 Verify the RACF provider is included in the Authentication Providers table The DefaultAuthenticator and DefaultldentityAsserter must always be the first two providers in this list 10 Select the DefaultAuthenticator active link select the name itself not the check box E DefaultAuthenticator DefaultIdentityAsserter RacfAuthenticator 11 In the Control Flag menu select Sufficient and then click Save 12 Click the Provider Specific tab and then click Save E 32 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers Settings for DefaultAuthenticator Configuration Performance Migration cor 13 Click the Providers locator link to return to the Authentication Providers screen Home Log Out Preferences E Record Hep Q Home Su ary cf Se ty Reska yea Dif aultAuthentscator Messages W Settings updated successfully 14 In the Authentication Providers table select the RACF authenticator name you created in Step 8 select the name itself not the check box Name Description E DefaultAuthenticator WebLogic Authentication Provider E DefaultIdentityAsserter WebLogic Identity Assertion provider al rs e 15 In the Control Flag menu select Sufficient and then click Save
65. on page E 23 Task 2 Enable Mainframe Support for STA RACF Authorization on page E 23 a Task 3 Configure AT TLS on page E 24 a Task 4 Create the RACF Profiles Used by the CGI Routine on page E 29 a Task 5 Import the Certificate File and Private Key File optional on page E 29 a Task 6 Test the CGI Routine on page E 29 a Task 7 Set Up RACF SSP for the WebLogic Console on page E 30 a Task 8 Configure SSL Between STA and RACF on page E 30 a Task 9 Configure the WebLogic Server on page E 30 a Task 10 Install RACF SSP on the WebLogic Console on page E 31 Note STA supports third party products that are compatible with IBM RACF for example CA s ACF 2 and Top Secret It is up to the person installing STA or a security administrator to issue the commands appropriate for the security product installed Task 1 Review IBM RACF Mainframe Minimum Requirements See the STA Requirements Guide for complete RACF requirements Task 2 Enable Mainframe Support for STA RACF Authorization The mainframe side of the RACF service for STA is provided by a CGI routine that is part of the SMC component for ELS 7 0 and 7 1 This CGI routine is called by the SMC HTTP server and uses RACF profiles defined in the FACILITY class Configuring External Authentication Providers for STA E 23 Tasks for Configuring IBM RACF Authentication Providers For STA to use RACF for access authentication on the mainframe you must
66. page New Delete Showing ito lof 1 Previous Next Showing 1 to lof 1 Previous Next 5 In the Change Center section click Lock amp Edit Configuring External Authentication Providers for STA E 31 Tasks for Configuring IBM RACF Authentication Providers ORACLE WebLogic Server Administration Console Home Log Out Prefer Change Center View changes and restarts Home Cik the Lock amp Edit button to modify add or Home Page delete items in this domain Information and Res a Configure appicatbons a Configure Gridlink for F Recent Task Status Domain Structure 6 Select the Providers tab Home Log Out Preferences Help Q Welcome weblogic myrealm Settings for myrealm Configuration Users and Groups Roles and Poles m e V General ROMS Security Store User Lockout Performance Cick the Lock amp Editbutton in the Change Center to modify the settings on this page 7 Inthe Authentication Providers section click New P Customize this table Authentication Providers Reorder Description DefaultAuthentcator WebLogic Authentication Provider DefauitidentityAsserter Weblogic Identity Assertion provider New Delete Reorder 8 Enter the name of the authentication provider you want to add for example STA RacfAuthenticator and select RacfAuthenticator in the Type menu Click OK Note The RACF jar file should be listed in the Type menu If it is
67. points on the STA server the following message is displayed notifying you that the mount point has been retained Click OK to dismiss the message i Warning x amount poim or includes user defined files dbdats mysql has been removed Database location dbbackup was retained because t ia amp mount point or includes user defined files dbdackup local has been removed Database location dbdata was retained because it ia OK When the deinstallation completes the message Deinstallation Successful appears in the Message pane Click Next or Finish to proceed to the final screen If a task fails the STA deinstaller quits rolls back the deinstallation and returns the server to its original state You can view the deinstallation log to troubleshoot the issue See STA Installation and Deinstallation Logs on page 3 5 for details STA Graphical Installer and Deinstaller Screen Reference A 41 STA Graphical Deinstaller Screens Screen Fields None Screen specific Buttons View Successful Tasks Select the check box to include Success outcomes in the display this is the default Clear the check box to display only Failure outcomes This allows you to filter out successful tasks so you can focus on the ones requiring attention View Log Click to display the deinstallation log in a separate window Figure A 7 is an example Click Close to dismiss the log window Figure A 7 Sample Deinsiallation Progress Log Displ
68. purposely not i preconfigured nor hard coded jg Set up Admin Accounts Help lt Back Next gt Cancel This screen describes the types of information you will define on the next two screens Read the text then click Next to continue Screen Fields None Screen specific Buttons None A 16 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens WebLogic Administrator StorageTek Tape Analytics Installation 2 1 0 beat ORACLE WebLogic Administrator va Welcome y Enter a username and password for the WebLogic Admin Console login This 1 Installation Location account is limited to administration tasks for WebLogic the application server that Y Mna Chevy hosts STA and is infrequently used i y Enter Root Password Username Requirements i 1t0 16 Set up DE Directories 1 to 16 characters in length H DS a ad All usernames must be unique AX Setup Admin Accounts I Weblogic Administrator Password Requirements 8 to 31 characters in length with no spaces Must contain at least one capital letter and one number except ROEST E Enter WebLogic Administrator Username weblogic Enter WebLogic Administrator Password eecccces Confirm WebLogic Administrator Password Help j lt Back Next gt Cancel WebLogic is the application server that hosts STA You use the WebLogic Administrator account to log into the WebLogic administration console to configure and manage the We
69. section The instructions and examples in this guide use Installers for this location substitute the directory you have chosen if it is different 3 2 StorageTek Tape Analytics Installation and Configuration Guide Accounts and Ports Configured During STA Installation STA installer working location By default the STA installer unpacks to the tmp directory and it consumes around 4 GB of space You can specify a different working location by running the STA installer with the following option J Djava io tmpdir working_directory working_directory must be an absolute path For example sta_installer_linux64 bin J Djava io tmpdir Oracle tmp See STA Silent mode Installer and Deinstaller on page B 1 for details about using this option STA logs location 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 on page 3 13 for instructions See Review STA File System Layout on page 2 2 for space requirements Username and Password Requirements Username requirements are as follows a Must be 1 16 characters in length a All usernames must be unique Password requirements are as follows Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include
70. specified file in encrypted form It also saves an encryption key file to a directory of your choice You can download the response file build utility when you download the STA installer The utility name is silentlnstallUtility_version jar where version is the version of the utility you have downloaded After STA has been installed or deinstalled successfully the encrypted passwords are removed from the respective response file To run the silent mode installer or deinstaller again you can rerun the build utility to resupply the encrypted passwords The build utility writes the response file location into the contents of the file therefore you cannot relocate the response file once you have updated it with this utility See Create the Silent mode Installer Response File on page B 5 for instructions STA Silent mode Installer Tasks Before using these tasks you should obtain the necessary installation information verify prerequisites and download the STA installer See STA Installation Tasks on page 3 7 for instructions Then to install STA with the silent mode installer use the following tasks in the order listed a Create the Oracle Central Inventory Pointer File on page B 4 a Create the Silent mode Installer Response File on page B 5 a Run the Silent mode Installer on page B 6 Create the Oracle Central Inventory Pointer File Use this procedure to create the Oracle central inventory pointer file if it does not e
71. the current status of the SNMP snmpd and snmptrapd services service snmpd status snmpd is stopped service snmptrapd status snmptrapd is stopped b If necessary stop the SNMP services immediately service snmpd stop service snmptrapd stop Note If you receive a FAILED error with either of these commands the services may already be stopped c Type the following to disable the SNMP services in the Linux services configuration file so they do not start automatically when Linux reboots chkconfig snmpd off chkconfig list snmpd snmpd 0 off l off 2 0ff 3 o0ff 4 off 5 0ff 6 o0ff chkconfig snmptrapd off chkconfig list snmptrapd snmptrapd 0 off l off 2 0ff 3 0ff 4 off 5 0ff 6 o0ff 7 Review and verify the applicable mode specific requirements as follows 3 10 StorageTek Tape Analytics Installation and Configuration Guide STA Installation Tasks Download STA For the STA graphical installer see Graphical mode Display Requirements on page A 1 a For the STA silent mode installer see Silent mode Requirements on page B 1 The STA installer download includes the following files version is the STA installation version number sta_install_version_linux64 bin Required for all installations sta_install_version_linux64 2 zip Required for all installations silentinstallUtility_version jar Response file build utility Required only if you will be using the STA silent mode ins
72. the ports must remain available and dedicated to STA Note Before completing these screens verify the correct port number values with your network administrator Once STA has been installed the port numbers cannot be changed without deinstalling and reinstalling STA Screen Fields None Screen specific Buttons None WebLogic Admin Console StorageTek Tape Analytics Installation 2 1 0 ORACLE WebLogic Admin Console A Welcome i 7 T Enter HTTP and HTTPS port numbers for the WebLogic Admin Console login y installation Location i praraniseke Chicts NOTE These are external communications ports Your network administrator may Prerequisite Checks if need to configure firewalls and routers to open communication between the STA y Enter Root Password server and the client accessing the WebLogic administration console If you are Y TE D ATEI unsure of which port numbers to specify contact your network administrator i m Set up Admin Accounts t A t 4 Set up Database Accounts A Enter Communication Ports Weblogic Admin Console ji Enter WebLogic Administration Console HTTP Port 7019 Enter WebLogic Administration Console HTTPS Por Help lt Back Next gt Cancel You specify the WebLogic Administrator console port number when you log into the WebLogic Administrator console which is used to administer and configure the WebLogic application server A 26 StorageTek Tape Analytics Installation and Configurat
73. the process in Table 5 1 perform Enable SNMP v2c Mode for STA on page F 3 2 Configure SNMP v2c in STA See Chapter 6 Configuring Library Connections in STA for instructions SNMP v2c Configuration Tasks Create the STA SNMP v2c Trap Recipient on the Library on page F 2 a Enable SNMP v2c Mode for STA on page F 3 Configuring SNMP v2c Mode F 1 SNMP v2c Configuration Tasks Create the STA SNMP v2c Trap Recipient on the Library Use this procedure to define the STA server as an authorized recipient of SNMP v2c traps and to define traps the library sends Depending on library model you can use the library CLI SL Console or SL150 browser interface Note the following Separate trap levels with commas To avoid duplicate records do not define the STA server as a trap recipient in multiple instances For example do not create both an SNMP v3 and SNMP v2c trap recipient definition for the STA server Trap level 4 may not be supported by older library firmware versions however it can always be specified when creating a trap recipient To avoid entry errors in the CLI you can first type the command in a text file and then copy and paste it into the CLI For help with CLI commands type help snmp Oracle recommends not using the values public or private for the community string as these values are well known and present a security risk See SNMP v2c Community String on page 5 2 for additional requirements Us
74. the size of your existing uncompressed STA database a minimum of 4 GB is required and for large databases Oracle recommends you increase the size of tmp to 32 GB at minimum If you determine you must increase the size of tmp you can do this just before you run the upgrade script see Task 8 Upgrade the Old Database on page 8 22 for instructions Review the environment changes relevant to your upgrade path and make any necessary adjustments to your plan or environment See Environment Changes for STA 2 1 x on page 8 5 for details If you are upgrading from STA 2 0 x ensure that all required RPM packages are installed on the STA server See Install Required Linux Packages on page 2 10 for instructions As a final check the STA installer will also notify you if any packages are missing If you are upgrading from STA 2 0 x review the file system structure on the STA server and verify that the required users and groups have proper access to the locations used by the STA installer See Recommended File System Layout on page 2 3 and Users Groups and Locations Used by the STA Installer on page 3 1 Verify Current STA Activity Use this procedure to verify that your current STA environment is functioning normally 1 Use the following steps to verify that the current version of STA has had recent successful communication with each monitored library a Login to STA as an STA administrator user b From the Setup a
75. time Monitored Libraries A 7xX aa Lbrary Name Livary Complex L150_abe Library IP Address es 192 0 2 20 192 0 221 0x8000 1 880430 STA IP Address Livary Engine ID A confirmation message box appears Information mS Get latest data initiated for library x 3 Click OK to dismiss the message box The data collection proceeds and the Monitored Libraries table is updated with the results Library Complex indicates the library complex ID Library Engine ID indicates the unique SNMP engine ID for the library Last Connection Attempt indicates the date and time when the data collection was initiated Last Successful Connection indicates the date and time when the data collection was completed if successful Last Connection Status is updated as follows IN PROGRESS The data collection process is underway SUCCESS The data collection was successful STA starts receiving exchange data from the library Configuring Library Connections in STA 6 9 STA Configuration Tasks FAILED The data collection was not successful If possible STA provides information in the Last Connection Failure Detail field You may need to extend the column width to see the entire value Note The status is updated every four minutes and the default screen refresh interval is 480 seconds However you can click the Refresh Table button to force a refresh of the table at any time Monitored Libraries
76. to support Redundant Electronics as this feature is more critical to maintaining continuous library operations If STA is configured to support Dual TCP IP STA maintains a connection with the library in the event of a port failover If STA is configured to support Redundant Electronics if a controller card switch occurs STA maintains a connection with the library through the port specified as the secondary library IP address See the library User s Guide for more information about these features Table 4 2 summarizes the recommended library IP addresses to use when configuring the STA connection to the library Table 4 2 Recommended Library IP Addresses for STA Connection Activated Features Primary Library IP Secondary Library IP Neither 2B port NA Dual TCP IP only 2B port 2A port on the active card Redundant Electronics only 2B port on the active card 2B port on the standby card Both 2B port on the active card 2B port on the standby card Additional Considerations for These Features To configure STA to support Dual TCP IP on an L3000 or SL8500 library you may need to use policy routing For more information consult the SL3000 or SL8500 Host Connectivity Guide If you need assistance with Dual TCP IP configuration contact Oracle Support a fa library has both Redundant Electronics and Dual TCP IP the STA server s subnet must be different from the subnet of the library port not configured for STA s
77. v x OEB a Recent SNMP Trap Communication Status may intermittently indicate MISSED HEARTBEAT This is normal 6 10 StorageTek Tape Analytics Installation and Configuration Guide T Configuring STA Services Use these procedures to configure the STA Backup service and STA Resource Monitor service utilities This chapter includes the following sections a STA Services Overview a STA Services Configuration Tasks STA Services Overview a STA database backup service You configure the STA backup service with its administration utility staservadm To display a complete list of command options for the utility type staservadm h See the STA Administration Guide for details STA resource monitor service You configure the STA resource monitor service with its administration utility staresmonadm To display a complete list of command options for the utility type staresmonadm h at the command line See the STA Administration Guide for details These service utilities are located in the Oracle_storage_home StorageTek_Tape_ Analytics common bin directory See Users Groups and Locations Used by the STA Installer on page 3 1 for details about the Oracle storage home STA Services Configuration Tasks General Tasks a Update the System Path optional on page 7 2 m Restart the STA Services Daemon optional on page 7 2 a Verify Library Connectivity on page 7 2 STA Database Backup Configuration Tasks a Review t
78. v3 connection The values you specify must match the corresponding ones on the library snmpget v3 u SNMP_user a SHA A auth_pwd x DES X priv_pwd 1 authPriv library_IP_addr 1 3 6 1 4 1 1211 1 15 3 1 0 Where v3 indicates SNMP v3 SNMP_useris the SNMP v3 user name SHA indicates the authentication protocol auth_pwd is the authorization password DES indicates the privacy protocol priv_pwd is the privacy password authPriv indicates that privacy is performed on the command library_IP_addr is the IP address of the public port on the library For SL150 libraries this is Network Port 1 For SL500 libraries this is port 1B For SL3000 and SL8500 libraries there may be multiple ports to test depending on whether Dual TCP IP or Redundant Electronics are activated on the library If there are multiple ports run this command for each IP address 1 3 6 1 4 1 1211 1 15 3 1 0 is the SNMP object identifier OID for the library which is the same for all library models If the command output displays the library model the test is successful Following are some command examples Example 6 1 Successful snmpget Command snmpget v3 u STAsnmp a SHA A authpwdi x DES X privpwd1 I authPriv 192 0 2 20 1 3 6 1 4 1 1211 1 15 3 1 0 SNMPv2 SMI enterprises 1211 1 15 3 1 0 STRING SL8500 6 2 StorageTek Tape Analytics Installation and Configuration Guide STA Configuration Tasks Example 6 2 Failed snmpget Command
79. you have not done so already stop all STA services STA stop all 2 Decompress the backup file gunzip dump_file_name sql gz 3 Use the following steps to purge the STA database of obsolete data such as processed SNMP records and empty analytics records Note A permanent record of purgerecs command activity is saved in the STA database Starting with STA 2 0 database purging also occurs automatically at runtime Periodically the MySQL Event Scheduler purges records from various tables to attenuate database growth a Change to the STA database updates directory cd Oracle_storage_home StorageTek_Tape_Analytics db updates b Initiate the purge purgerecs path_to_dump_file dump_file_name sql path_to_dump_ file dump_file_name_PURGED sql Note For help with the purgerecs command type the following command purgerecs h In Example 8 6 the purgerecs utility processes the MySQL dump file Dec14_dump sal in dbdumpfiles The output is directed to a new file named Dec14_dump_PURGED sq in dbdumpfiles A progress dot appears for each 200 records processed Example 8 6 Purge Obsolete Data From the Old Database Backup cd Oracle StorageTek_ Tape Analytics db updates purgerecs dbdumpfiles Dec14_ dump sql dbdumpfiles Dec14_dump_PURGED sql STA v1 0 2 Schema 33 02 Processed 11 689 lines from 20130711_dump sql snmp_storage_cells 1 614 255 snmp_media 1
80. you must re install STA D 4 StorageTek Tape Analytics Installation and Configuration Guide Security Certificate Configuration Tasks Settings for stali Configuration Protocols Logging Debug Monitoring Control Deployments Services Seaity Notes General Cluster Services Keystores SSL FederationServices Deployment Migration Tuning Overload Health Monitoring Server Start Web Services Save Keystores ensure the secure storage and management of private keys and trusted certficate authorities CAs This page lets you view and define various keystore configurations These settings help you to manage the security of message transmissions Keystores Custom Identity and Java Standard Trust Which configuration rules should be used for finding the Change server s identity and trust keystores More Info Identity Custom Identity Keystore Oracie Middleware us The path and fie name of the identity keystore More Custom Identity Keystore PKCS12 The type of the keystore Generally this is KS More Type Info Custom Identity Keystore PTTTTTITITITT TTT The encrypted custom identity keystore s passphrase If Passphrase empty or nul then the keystore will be opened without a passphrase More Info Confirm Custom Identity Pritiiiiiti ii iitt Keystore Passphrase Trust Java Standard Trust Keystore Orade StorageTek_Tape_Analytics jdk1 6 0_75 ye fb seamity cacerts Java Standard Trust Keystore ks Type
81. you selected during STA installation https yourHostName PortNumber console For example https sta_server 7020 console Log in using the WebLogic administration console username and password you defined during STA installation In the Domain Structure section select Security Realms ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefere View changes and restarts Neme No pending changes exist Cick the Release Home Page Configuration button to allow others to edit the domain Information and Resa a Configure app catons 4 Summary of Security Realms P Customize this table a Configure Gridlink for R a Recent Task Status a Set your console prefere Domain Configuration Doman In the Realms section select the myrealm active link select the name itself not the check box A searity reaim is a container for the mechaniems including users groups security roles security poles and security providers that are used to protect WebLogic resources You can have multiple security realms in a WebLogic Server domain but only one can be set as the default active resin This Security Reaims page lists each security realm that has been configured in this WebLogic Server domain Click the name of the realm to explore and configure that realm Realms Filtered More Columns Exist Cick the Lock amp Editbutton in the Change Center to activate all the buttons on this
82. 0 install rwxrwxrwx 1 root root 1191 Jan 20 13 04 monitor_staserver log drwxrwxrwx 2 root root 4096 Jan 7 11 03 uidumps Create a symbolic link from your new STA logs directory to the default location For example ln s LOGS_DIR log tbi var log tbi Is 1 var log tbi lrwxrwxrwx 1 root root 15 Jan 20 14 22 var log tbi gt LOGS_ DIR log tbi Restart STA STA start all Starting mysql Service mysql service was successfully started Starting staservd Service staservd service was successfully started Starting weblogic Service weblogic service was successfully started Starting staengine Service staengine service was successfully started Starting staadapter Service staadapter service was successfully started Starting staui Service staui service was successfully started 3 14 StorageTek Tape Analytics Installation and Configuration Guide STA Installation Tasks Register the Oracle Central Inventory Location Use this procedure after STA installation has completed to register the Oracle central inventory location on the STA server You only need to use this procedure once on this server This procedure creates an Oracle central inventory pointer file etc oralnst loc which allows the Oracle central inventory location and Oracle install group to be known to all Oracle installers used on the server 1 2 Log in as the Linux root user Change to the Oracle
83. 0 only on page 4 8 3 Enable ADI on library and LTO drives For libraries with LTO drives only See Enable ADI on the Library all libraries except SL150 on page 4 9 4 Set the library complex ID SL8500 only See Ensure the Correct Library Complex ID SL8500 only on page 4 9 5 Set the library date and time To ensure that library data date time stamps correlate to STA server date time stamps the library clock should be set appropriately by Oracle Support 6 Submit the necessary service requests 1 6 StorageTek Tape Analytics Installation and Configuration Guide 2 Installing Linux This chapter includes the following topics a Linux Installation Process a Preparation Tasks a Installation Tasks a Post Installation Tasks Before installing Linux on the STA server review the system requirements in the STA Requirements Guide Note You cannot perform an in place upgrade of Linux 5 x to Linux 6 x If you are installing Linux 6 x as part of an upgrade to STA 2 0 x see Chapter 8 Upgrading to STA 2 1 x Linux Installation Process To install and configure Linux for STA perform the following tasks in the following sections in the order indicated Preparation 1 Review Related Documentation on page 2 2 2 Download the Linux Installer Media Pack on page 2 4 Installation 1 Gather Required Information on page 2 5 2 Install Linux on page 2 5 3 Run the Linux Setup Agent on page
84. 000 and SL8500 only ccccccsseeseststeeseeseteeeeees 4 10 Set the SL500 Volume Label Format SL500 only cccceccecesssssesesescseseesescscseseseecscsesssneseeaes 4 10 Set the SL150 Volume Label Format and Drive Element Addressing Mode SL150 only 4 11 5 Configuring SNMP on the Libraries Understanding Library SNMP Configuration for STA 0 c cece cece ceeseseeeesessssseeseseeeesenees 5 1 Configuring the SNMP v3 Protocol on the Libraries ssssssessssssssssissestestessissesnetessesnesnenreeness 5 1 Library SNMP Configuration Tasks c ccccccccscscssssescsnetesesesseesesescecesescsnaneneseseseeseseseececesessseaanenens 5 3 Retrieve the Library TPA Gress crannan oaa aaia ai a a Ea aaa saaara lussuersiecsine 5 4 Enable SNMP r the Library s ssspeai nunan a Aas ssla a detent e r E EE 5 5 Ens rean SNMP v2 USE Pn rooie e E E i e E e a 5 6 Create ani SNMP V3 Usetie ccnsc ccticki ce evetchie el eE EEEE EE hice a o aes aa E a ieee iata 5 7 Retrieve the Library SNMP Engine ID all libraries except SL150 0 0 cece cesses cece 5 8 Create the STA SNMP v3 Trap Recipient cccceecceesssssesesesesssesesescsesesesesescsesesesescsssnsneseeeeesen 5 8 6 Configuring Library Connections in STA STA Configuration Tasks 02 c csecciiiedeseseh ieatieeeeedissvesbest ee paa ra E tench E E a aaa aa dacs 6 1 Login to STAs ir e e T e aaa ae ga E E A R shee nee e 6 1 Verify SNMP Communication With a Library se ss
85. 026 Help lt Back Next gt Cancel Oe ndaka The staAdapter managed server ports are used for internal SNMP communication only Note Make a secure record of these port numbers they cannot be changed once STA is installed To protect your site security these numbers are purposely not preconfigured nor hard coded Screen Fields Enter HTTP Port Enter the HTTP port number for unsecure access to the staAdapter managed server Typically this port number is 7025 Port numbers must be unique and available Enter HTTPS Port Enter the HTTPS port number for secure access to the staAdapter managed server Typically this port number is 7026 Port numbers must be unique and available Screen specific Buttons None STA Graphical Installer and Deinstaller Screen Reference A 29 STA Graphical Installer Screens STA UI StorageTek Tape Analytics Installation 2 1 0 ae A Wel elcome Enter HTTP and HTTPS port numbers for the staUi managed server Installation Location NOTE These are external communications ports Your network administrator may Prerequisite Checks need to configure firewalls and routers to open communication between the STA Enter Root Password server and the client accessing the STA user interface If you are unsure of which port numbers to specify contact your network administrator Set up OB Directories Setup Admin Accounts Set up Database Accounts Enter Communication Ports W
86. 10 205 media_summaries 254 transform_logs 0 Records Processed 13 143 283 Records Purged 2 857 623 Records Remaining 10 285 660 Elapsed Time 00 00 11 Upgrading to STA 2 1 x 8 21 Upgrade Tasks This step is optional Determine the database file size and estimate the load process time Is s h dump_file_name_PURGED sql Start the MySQL server STA start mysql Load the old STA database Enter the database root user password when prompted Unless you specify the v verbose option not recommended there is no command output as the process runs Note The optional v parameter for verbose output is not recommended as a large number of messages are displayed in the terminal window and it can significantly slow down the command process for large databases mysql uroot p e SET SESSION SQL_LOG BIN 0 SOURCE path_to_dump_ file dump_file_name_PURGED sql Password mysql_root_password Where p Prompts for the database root password established during STA installation a e Execute the following quote enclosed statements SET SESSION SQL_LOG_BIN 0 Turns off unnecessary binary logging speeding up the load SOURCE path_to_dump_file dump_file_name_PURGED sql Loads the dump file into the DB If the command is successful you are returned to the command prompt once the process completes Task 8 Upgrade the Old D
87. 15 Set Up Admin Accounts on page A 16 WebLogic Administrator on page A 17 a STA Administrator on page A 18 Set Up Database Accounts on page A 19 a Database Root User on page A 20 Database Application User on page A 21 a Database Reports User on page A 23 Database Administrator on page A 24 Enter Communication Ports on page A 25 a WebLogic Admin Console on page A 26 a STA Engine on page A 28 a STA Adapter on page A 29 STA UI on page A 30 Diagnostic Agent on page A 31 Installation Summary on page A 32 Installation Progress on page A 33 Configuration Progress on page A 35 Installation Complete on page A 37 Note When you launch the STA graphical installer the Oracle Universal Installer displays messages in the terminal window as it performs some basic environment checks Requirements for running the STA graphical installer may exceed these minimal checks A 4 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Installation and Inventory Setup Oracle StorageTek Tape Analytics 2 1 0 Installation Inventory Setup x Installation Inventory Setup fe Central inventory Directory The Oracle Central Inventory contains information relating to all Oracle products installed on a host Enter directory name for the central inventory The installer will create the directory if amp does not exist Central Inventory Directory
88. 21AM log id Enter Root Password WebLogic Admin Username weblogic I Ser un Os Directories STA CUI Admin Username sta admin ji MySQL Account Application Username stadb AN Setup Admin Accounts MySQL Account Reports Username starpt Set up Database Accounts MySQL Account OBA Username stadba Ap HTTP HTTPS Communication Ports for AdminServer 7019 7020 Enter Communication Ports als aS S HTTP HTTPS Communication Ports for StaAdapter 7025 7026 Configure RDA HTTP HTTPS Communication Ports for StaEngine 702 Installation Summary HTTP HTTPS Communication Ports for Stali 7021 70 RDA Domain Name us oracie com 3 Disk Space Required 2962 MB Available 30439 MB amp Distribution Details Oracle Application Developer Framework 11 1 2 4 Oracle Weblogic Server 10 3 6 0 8 Oracle JOK 1 6 0 75 Oracle MYSQL 5 6 18 Oracle StorageTek Tape Analytics 2 1 0 Save To change this configuration before installing click Back or select atopic in the navigation pane on the left To install with the above configuration click Install Help lt Gack Jnstall Cancel The screen displays the following details about the installation You can save this information to a text file for your records a Installation Details Information you have entered on the installer screens a Disk Space Required and available disk space in MB a Distribution Details Names and version numbers of the software packages that will be installed Continue
89. 5535 for all ephemeral ports HTTPserverJobname Jobname of the HTTP Server certificatelabel Label from the certificate definition _ keyringname Name from the RACF keyring definition 3 Activate RACF Classes Either the RACF panels or the CLI can be used The RACF classes include DIGTCERT DIGTNMAP DIGTRING SERVAUTH class must be RACLISTed to prevent PORTMAP and RXSERV from abending SETROPTS RACLIST SERVAUTH RDEFINE SERVAUTH UACC ALTER OWNER RACFADM RDEFINE STARTED PAGENT OWNER RACFADM STDATA USER TCPIP GROUP STCGROUP RDEFINE FACILITY IRR DIGTCERT LISTRING UACC NONE OWNER RACFADM RDEFINE FACLITY IRR DIGTCERT LIST UACC NONE OWNER RACFADM RDEFINE FACILITY IRR DIGTCERT GENCERT UACC NONE OWNER RACFADM 4 Define RACF Keyrings and Certificates a Enter the following RACF commands to create Keyrings and certificates RACDCERT ID stcuser ADDRING keyringname where stcuser RACF user id associated with the TCPIP address space E 26 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers keyringname Name of the keyring must match the Keyring specified in the PAGENT configuration RACDCERT ID stcuser GENCERT CERTAUTH SUBJECTSDN CN serverdomainname O companyname OU unitname C country WITHLABEL calabel TRUST SIZE 1024 KEYUSAGE HANDSHAKE DATAENCRYPT CERTSIGN Note This is the
90. 8 2 SCP is used to transfer the compressed database dump file Dec14_ dump sql gz to the dodumpfiles folder on backup host backup1 The dbdumpfiles folder already exists on the backup host Example 8 2 Old Database Transfer to Backup Server Single server Method cd dbdumpfiles scp p Dec14_dump sql gz backup1 dbdumpfiles In Example 8 3 SCP is used to transfer the compressed database dump file Dec14_ dump sql gz to the dbdumpfiles folder on STA 2 1 x host sta_new Example 8 3 Old Database Transfer to New STA Server Two server Method cd dbdumpfiles scp p Dec14_dump sql gz sta_new dbdumpfiles 4 On the target server perform a checksum of the transferred file Verify that the checksum values match cd path_to_dump_file cksum dump_file_name sql gz Upgrading to STA 2 1 x 8 17 Upgrade Tasks Task 3a Install the New Linux Version Upgrades From STA 1 0 x Caution This activity destroys all data on the server If you are using the single server upgrade method use this procedure only after you have performed Task 1 Dump the Old STA Database on page 8 15 and Task 2 Transfer the Old Database Dump on page 8 17 This procedure applies only to upgrades from STA 1 0 x Install Linux 6 3 or higher on the STA server see Chapter 2 Installing Linux for instructions Task 3b Deinstall the Old STA Version Upgrades From STA 2 0 x and Higher Caution This activity destroys all STA d
91. CA certificate for the STA system where stcuser RACF user id associated with the TCPIP address space serverdomainname Domain name of the z OS server for example MVSA COMPANY COM companyname Organization name unitname Organizational unit name country Country calabel Label for certificate authority for example CATBISERVER RACDCERT ID stcuser GENCERT SUBJECTSDN CN serverdomainname O companyname OU unitname C country WITHLABEL serverlabel TRUST SIZE 1024 SIGNWITH CERTAUTH LABEL calabel Note This is the SERVER certificate where stcuser RACF user id associated with the TCPIP address space serverdomainname Domain name of the z OS server for example MVSA COMPANY COM companyname Organization name unithame Organizational unit name country Country serverlabel Label for the server certificate for example TBISERVER calabel Label for certificate authority specified in the CA certificate definition RACDCERT ID stcuser GENCERT SUBJECTSDN CN clientdomainname O companyname OU unitname C country WITHLABEL clientlabel TRUST SIZE 1024 SIGNWITH CERTAUTH LABEL calabel Note This is the CLIENT certificate where stcuser RACF user id associated with the TCPIP address space clientdomainname Domain name of the STA client for example TBIA COMPANY COM companyname
92. Central Inventory Pointer File ssnsensssssssstsrtssttstterstsrttestesnterstesntesneentessnernee B 4 Create the Silent mode Installer Response File ccccssccescscsseseseseeteseseeeeeeesescesenesesesneneseseees B 5 Run the Silent mode Installer ccccccccccccesssssecscessecscessecsecsscesssecsseseeceseceecseeesecseesaecaecsaecseseeeeeees B 6 STA Silent mode Deinstaller Tasks cccccccccccscssscsseesscesceseeceseeecesceseesseceeecsecssecaecsaecaesesseeseeees B 8 Create the Silent mode Deinstaller Response File c ccccsccsessssseseenetesesesneneseseecenesescsnananeneees B 8 Run the Silent mode Deinstaller cccccccccccsccssessessecsseesececesceseceseseeceseessecsecseecsecsaeeasceeeeeeeseeeees B 9 STA Installer Command Options 0 0 0 0 eee ceeeeeeececeeseecenececeseseeeseseseseseneseseesenenesesenenenes B 10 Silent MOMS OPNS yaari ie ep E a E loventysedgusrordiplvestetvaptevessrtialees B 10 Logging Optiohs Ssmi ai e e aeaa tudes a Ea S a aaa ra aa ara aene oaa eaaa Da TAEA IAE B 11 Other OPtions sissisotaan iskinita ini eia B 11 C Installation and Upgrade Worksheets Upgrade Preparation Worksheet nnani C 1 Installation and Upgrade Worksheets cccccccccsssesecscssseescscscseseseecscsssesesescscssseseececscsssnseeceeesens C 2 Installation Users and Locations Worksheet cccccccccese cesses cecseeeseeesceseeeeseesesesesessneseeseeees C 2 User Accounts Worksheets iic csdisisscsscecsssssdsscutss
93. Community Trap Corr STAsrenp SHA DES Crcabodief00000000000000000000 pubic pubic The Define SNMP Client Settings dialog box appears If this is a new configuration the fields are blank 3 Complete the dialog box as follows The values you specify must match the corresponding ones on the libraries Note Even if STA will only be monitoring libraries configured for SNMP v2c communication you must complete all fields including those applicable to SNMP v3 You cannot leave any fields blank a STA SNMP Connection Username Auth Type the SNMP v3 user name a Enter STA SNMP Connection Password Auth Type the connection authorization password Enter Privacy Encryption Password Privacy Type the privacy encryption password User Community Type the SNMP v2c community string specified on the library This field is required for the SNMP handshake with the library a Trap Community Type the SNMP v2c community string specified on the library This field is used only if SNMP v2c is used for communication with the library 6 4 StorageTek Tape Analytics Installation and Configuration Guide STA Configuration Tasks Define SUMP Chent Settings DA STA SNMP Connection Username Auth amp Enter STA SNMP Commecton Password Auth esccese Verify STA SNMP Connecton Password Auth eesccee Connection Password Encryption Auth SHA Enter Privacy Encrypton Password Privacy eeeccee Verify Privacy Encryp
94. ConfirmPassword Var MYSQL RPTS CONFIRMPASSWORD MySQL DBA Name Var MYSQL DBA NAME required MySQL DBA Password Var MYSQL DBA PASSWORD MySQL DBA ConfirmPassword Var MYSQL DBA CONFIRMPASSWORD ADMINSERVER HTTP Port Var ADMINSERVER HTTP PORT 7019 ADMINSERVER HTTPS Port Var ADMINSERVER HTTPS PORT 7020 taEngine HTTP Port Var STAENGINE HTTP PORT 7023 taEngine HTTPS Port Var TAENGINE HTTPS PORT 7024 taAdapter HTTP Port Var TAADAPTER HTTP PORT 7025 taAdapter HTTPS Port Var AADAPTER HTTPS PORT 7026 taUi HTTP Port Var AUI HTTP PORT 7021 taUi HTTPS Port Var TAUI HTTPS PORT 7022 Domain name var DOMAIN NAME required n a n E wn E 4d wn i J n Example B 2 STA Silent mode Deinstaller Response File Template ENGINE DO NOT CHANGE THIS Response File Version 1 0 0 0 0 GENERIC This will be blank when there is nothing to be de installed in distribution level SELECTED_DISTRIBUTION STA_Instal1 2 1 0 0 0 Root access passsword var DEINSTALL ROOT ACCESS PASSWORD RESPONSEFILE_LOC KEYFILE_LOC STA Silent mode Installer and Deinstaller B 3 STA Silent mode Installer Tasks STA installer response file build utility The installer response file build utility allows you to insert encrypted passwords into the silent mode installer and deinstaller response files The utility prompts you for the passwords and adds them to the
95. Deinstaller Screens Enter Root Password StorageTek Tape Analytics Installation 2 1 0 ORACLE ae Enter Root Password JORAG 6 va Welcome Some deinstallation steps require system root privileges Specify the existing Enter Root Pass word system root account password rir NOTE Validation of the root account password will take a few seconds Enter System Root Password Help lt Back Next gt Cancel The STA deinstaller requires Linux root access to perform the deinstallation tasks Screen Fields Enter Root Password Type the password for the Linux root user The entry is masked as you type It may take several seconds to validate the password Screen specific Buttons None STA Graphical Installer and Deinstaller Screen Reference A 39 STA Graphical Deinstaller Screens Deinstallation Summary Oracle StorageTek Tape Analytics 2 1 0 Deinstallation i s ORACLE Deinstallation Summary va y Welcome Deinstall Oracle StorageTek Tape Analytics Y Enter Root Password Directory Details I STA Home Location Oracle StorageTek_Tape_Analytics Deinstaltation Summary Log File tmp Orainstall201S 01 07_09 SS 37AM deinstall2015 01 07_09 SS 37AM log Feature Sets To Deinstall Oracle Application Developer Framework 11 1 2 4 Oracle Weblogic Server 10 3 6 0 8 Oracle JOK 1 6 0 75 Oracle MYSQL 5 6 18 Oracle StorageTek Tape Analytics 2 1 0 To change this configuration before deinstalling click Back or
96. Details Locations of the installed STA application and installer log file and connection details for the WebLogic and STA application user interfaces a Feature sets have been installed Names and version numbers of the software packages that have been installed You may wish to save a screen shot of this information for your records Click Finish to exit the installer Screen Fields None Screen specific Buttons Finish Click to exit the STA installer STA Graphical Deinstaller Screens This section provides detailed reference for each screen of the STA graphical deinstaller a Welcome on page A 38 a Enter Root Password on page A 39 a Deinstallation Summary on page A 40 STA Graphical Installer and Deinstaller Screen Reference A 37 STA Graphical Deinstaller Screens a Deinstallation Progress on page A 41 a Deinstallation Complete on page A 43 Oracle StorageTek Tape Analytics 2 1 0 Deinstallation ORACLE ae Welcome va Welcome t Enter Root Password You are about to deinstall the applications contained in Oracle Home Click Next to begin Y Deinstallation Summary Copyright c 2012 2015 Oracle and or its affiliates All rights reserved Help F Next gt Cancel The screen describes the actions you are about to take Read the text and click Next to proceed Screen Fields None Screen specific Buttons None A 38 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical
97. Devices UNIX is a registered trademark of The Open Group This software or hardware and documentation may provide access to or information about content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services unless otherwise set forth in an applicable agreement between you and Oracle Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services except as set forth in an applicable agreement between you and Oracle Contents PCR AG Cs seats aarares cache aah E ET E T T a xi Adee a RE OS YA e E aR AP SE RE xi Documentation Accessibility sic e ivcieavets iveceivi st leven e inves sp E a feu Eiaa a a i xi Related DO Guimen ts ieee si8 235 es este acta eee Aa Sabet Presse ae mec ee en eit aE ae xi GONV ECHELONS 5 oss ch A AAE ENE EAA TEE sated eden EE EE EEE EA OENES A AANA A xii What S INOW a aa nea iia beast ti ta a R a ar E xiii STA 21 1 June 2015 nra ann a a aa a S aTa Eat xiii Pre installation Planning STA Deployment Process Overview nsss ait ssi aias 1 1 Best Practices for STA Deployment iioii iiba iniii biaia iaiia 1 2 Pr paration neenon iee niian Sees SO e EA E E Bs ee A ee A E N GO AER 1 2 Linux Installati n ss apaan gp nan Seite techie Aaaa aiat iaa
98. E e a ER 3 4 STA Installation and Deinstallation Logs s e ssssseessesisssesesssestestssressestentestisnnsnentestisneneneeeneseesnes 3 5 Log File Locations 0 c esikadinie i henna adi Aas salir a A 3 6 STA Installer Mod eSis atia e a i arees tda eseni een eir ai 3 7 STA Installation TaskS nnspingon maea ae aaa pa a aaa ae Eaa esa etae 3 7 Identify or Create Information Required for the Installation cccceceseseeeteteeseeteteeeeeees 3 7 Verify Installation Preregtisit s sssri annons eien aiarar baiia aeaa e aaae iesse saiia 3 9 Download STA r na ie ee A E E E RO E EE TN 3 11 NaS CALS TAG a heater T e T a a 3 12 Verify Successfull Installation iiscic csiccssscscuceccsseotvcasssseseveacesdecsesestucedstseseutetstinsessucatessestuculigdesvbavas 3 12 Relocate the STA Logs Directory optional cccccssssesesesessssesesescsesssesesescssseseecsesessaeseecsees 3 13 Register the Oracle Central Inventory Location ccccccccsecsestseseseeneteescecesescsnensneneseseeseneseeeees 3 15 4 Configuring Library Features for STA Library Features Affecting STA Data ccccccccccecese cs ceseseseecscseseseecscscsssnsescecesenssseesecesessnesesecenes 4 1 ADI Interface for LTO Drives eessescsseseesesceseseecseecesesssasscsscecesescsseaseseaceasscsaseesaseeeaeeesaeenees 4 1 Dual TCP IP and Redundant Electronics SL3000 and SL8500 only sssssssssssssessssssesesseeseess 4 2 Library Complex ID SL8500 ONIY isiin ep a aa e 4 3
99. EE 65 65 65 65 70 80 75 StaResMon localhost john doe company com STA Resource Monitor Report Done Current STA Resource Monitor Service Settings Configured Send Reports T Sleep Interval i Alert Nagging n DB Username U DB Password P DB Tablespace hwm t DB Backup hwm dbbackup b DB Data hwm dbdata d Log Volume hwm var log tbi 1 Root Volume hwm Z Tmp Volume hwm tmp X System Memory hwm m Email From f Email To r Email Subject s Output File 0 var log tbi db staresmon csv 4 Review the command output to verify that the values have been set correctly 7 8 StorageTek Tape Analytics Installation and Configuration Guide 8 Upgrading to STA 2 1 x This chapter provides instructions for upgrading any previously released version of STA to STA 2 1 0 and subsequent STA 2 1 x versions It includes the following sections Valid STA 2 1 x Upgrade Paths Upgrade Process Overview Choosing Whether to Use One Server or Two Environment Changes for STA 2 1 x Upgrade Preparation Tasks Upgrade Tasks If you are installing STA for the first time you should perform a new base installation see Chapter 3 Installing STA for instructions Appendix C includes worksheets you can use to organize your upgrade activities and record your settings Valid STA 2 1 x Upgrade Paths You can upgrade to STA 2 1 x from any of the following released STA versions STA 2 1 0
100. Installation on page 3 7 a Verify Installation Prerequisites on page 3 9 Download STA on page 3 11 a Install STA on page 3 12 a Verify Successful Installation on page 3 12 a Relocate the STA Logs Directory optional on page 3 13 a Register the Oracle Central Inventory Location on page 3 15 Identify or Create Information Required for the Installation Use this procedure to identify and if necessary create users and locations to run the STA installer You can use Table C 2 Installation Users and Locations Worksheet to record this information See Users Groups and Locations Used by the STA Installer on page 3 1 for details about these items 1 Log in as the Linux root user 2 Determine whether there is an Oracle central inventory pointer file etc oralnst loc on the STA server The file is present if the Oracle central inventory has been registered previously see Oracle central inventory location on page 3 2 for details a If the file exists record its contents For example cat etc oraInst loc inventory_loc opt oracle oraInventory inst_group oinstall The inventory_loc entry identifies the Oracle central inventory location and the inst_group entry identifies the Oracle install group a Ifthe file is not present proceed to Step 3 to create the necessary users and locations For example Installing STA 3 7 STA Installation Tasks cat etc oraInst loc cat etc oraInst loc No s
101. L8500 only on page 4 4 Volume Label Format SL500 and SL150 only on page 4 4 a SCSI FastLoad Option SL500 only on page 4 5 a Duplicate Volume Serial Numbers on page 4 5 ADI Interface for LTO Drives StorageTek modular libraries support Linear Tape Open LTO drives from HP and IBM LTO drives that support the Automation Drive Interface ADJ can provide rich data for example drive performance and utilization to the library depending on drive configuration and firmware level For a library to send rich LTO drive data to STA ADI must be enabled on both the library and the LTO drives If ADI is not enabled on both the library will only send basic data about the LTO drives See the STA Requirements Guide for details about required drive firmware levels Enabling ADI on LTO Drives The method for enabling ADI depends on the drive manufacturer and model Configuring Library Features for STA 4 1 Library Features Affecting STA Data HPLTO 3 LTO 4 LTO 5 and LTO 6 These drives switch automatically to ADI mode after ADI is enabled on the library the library is rebooted and the drives are rebooted Drives can be rebooted with SL Console IBMLTO 3 LTO 4 LTO 5 and LTO 6 These drives must be explicitly configured for ADI mode and will not be recognized until ADI is enabled on the library and the library is rebooted Table 4 1 provides additional detail Note The Belisarius adapter card provides the in
102. Location of the response file containing input for the STA silent mode installer or deinstaller response_file must be an absolute path See Example B 1 and Example B 2 for the contents of the installer and deinstaller response files silent Required for silent mode Indicates to use silent mode Inputs are taken from the specified response file Logging Options The following options allow you to control the types of information provided in the installer and deinstaller logs They can be used with both graphical and silent modes debug Log debug information Some debug information will also appear in the console window logLevel level Omit log messages whose priority levels are lower than the specified level Values for level are as follows m severe a warning a info config a fine a finer a finest printdiskusage Log debug information about disk usage printmemory Log debug information about memory usage printtime Log debug information about elapsed time Other Options The following command options are for general use They can be used with both graphical and silent modes compatibilityFile compatibility_file Location of the file that specifies feature set dependency changes executeSysPrereqs Execute the system environment prerequisite checks for running the installer then exit without performing the installation help Display help STA Silent mode Installer and Deinstal
103. ORACLE StorageTek Tape Analytics Installation and Configuration Guide Version 2 1 1 E58068 03 June 2015 StorageTek Tape Analytics Installation and Configuration Guide Version 2 1 1 E58068 03 Copyright 2013 2015 Oracle and or its affiliates All rights reserved Primary Author Nancy Stevens Contributing Author This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this is software or related documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government then the following notice is applicable U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software purs
104. Oracle and or its affiliates All rights reserved Help Next gt Cancel This screen provides some general information for running the STA installer Read the text then click Next to begin the installation Note System changes are not implemented until you have completed all the STA installer input screens and clicked Install in Installation Summary on page A 32 Anytime before then you can return to a previous screen and modify your entries See General Installer Screen Layout on page A 6 for details about the STA installer screens General Installer Screen Layout All STA installer screens follow the same basic layout The main parts are illustrated and described below A 6 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens StorageTek Tape Analytics installation 2 1 0 installation Location A fer y talon location Item Name Description A Screen title Title of the STA installer screen B Navigation tree Displays your current position in the installation sequence Screen titles become active links as you complete each screen You can click any active link to return directly to that screen and review or change your entries C Expand and Click to hide or display the Navigation tree and the Message pane Collapse icons D Resize control Click and drag to resize the Navigation tree or the Message pane bar D Message pane Included only on select
105. Oracle central inventory pointer file this parameter is required only if the file does not exist in the etc directory or you want to use a different file For example deinstall sh silent responseFile Installers SilentDeinst rsp invPtrLoc opt oracle oraInst loc 5 The deinstaller displays status messages in the terminal window as it performs the following deinstallation steps This process may take up to 30 minutes to complete STA Silent mode Installer and Deinstaller B 9 STA Installer Command Options Example B 9 shows messages that appear at the end of successful deinstallation Example B 10 shows some messages you might see at the end of a failed deinstallation Example B 9 Successful STA Silent mode Deinstallation Final Messages Reading response file Starting silent deinstallation 20 40 60 80 Successfully moved logs to var log tbi install s common bin uninstall sh mysql was removed with s common bin uninstall sh left because there are user defined files in s common bin uninstall sh or it is a mount point dbdata local was removed with dbdata left because there are user defined files in dbdata or it is a mount point 100 The uninstall of STA_ Install 2 1 0 0 0 completed successfully Logs successfully copied to home oracle oraInventory logs Example B 10 Sample Failed STA Silent mode Deinstallation Final Messages Reading response file St
106. Oracle_storage_home Middleware rda output STA GUI snapshot log bundles Oracle_storage_home Middleware rda snapshots Installing Linux 2 3 Preparation Tasks Table 2 2 Cont Recommended File System Layout Default Mount File System Point Size Description and Recommendations STA database dbdata 250 GB to 2 TB Location of the STA database This location is user defined Oracle highly location recommends you place this directory on its own volume separate from root swap Oracle storage home and the STA logs location For performance backup and maintainability best practice is to use a separate set of mirrored or striped drives Required size depends on the number of libraries drives media exchanges per day and historical years of data Oracle recommends that you configure STA services to alert if space utilization exceeds a specified percentage STA database dbbackup 70 to 80 Location of the most recent local database backup This location is local backup percent of user defined Oracle recommends that it be on a different volume from the location dbdata size STA database and on mirrored or striped drives in case of database corruption or failure STA logs Nat log tbi 30 GB Location of STA and MySQL logs This location should be a separate volume location minimum at a separate mount point The contents tend to grow and are managed 50 GB to through log rotation The default location is var log tbi but
107. S server certificate in ASCII format and the STA client private key in binary PKCS12 format The MVS system administrator has given you the password to the PKCS12 file Place the certificate in Oracle_storage_home Middleware user_projects domains tbi cert where Oracle_storage_home is the Oracle storage home location specified during STA installation Convert the certificate from the DER format to the PEM format openssl pkcs12 clcerts in PKCS12DR xxxxxx out mycert pem You will be asked to enter the Import Password given to you with the certificate a new PEM password and password verification Using the Java keytool command import the certificate file into the Oracle_storage_ home Middleware jdk1 6 0_xx jre lib security cacerts file Oracle_storage_home Middleware jdk1 6 0_xx jre bin keytool importcert alias tbiServer file certificate keystore Oracle Middleware jdk1 6 0_ xx jre lib security cacerts storetype jks Task 9 Configure the WebLogic Server To configure WebLogic for RACF authentication follow the procedure in Reconfigure WebLogic to use a Different Security Certificate on page D 2 E 30 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers Task 10 Install RACF SSP on the WebLogic Console 1 3 Go to the WebLogic console login screen using the HTTP STA 2 1 x default is 7019 or HTTPS STA 2 1 x default is 7020 port number
108. See Verify Installation Prerequisites on page 3 9 for general STA installation requirements In addition the STA silent mode installer and deinstaller have the following mode specific requirements a You can use silent mode from telnet clients such as PuTTY which do not use the X11 protocol The xorg x11 utils RPM package must be installed on the STA server however a Before using silent mode you must download the silentInstallUtility_version jar file from the Oracle Software Delivery Cloud website and use it to create the response file with encrypted passwords See Create the Silent mode Installer Response File on page B 5 for instructions a Silent mode also requires a central inventory pointer file specifying the location of the Oracle central inventory directory and the Oracle install group You must create the file manually if it does not exist already See Oracle central inventory pointer file on page B 2 for details STA Silent mode Installer and Deinstaller B 1 Files and Utilities Used With Silent Mode Files and Utilities Used With Silent Mode This section describes key concepts and terms for silent mode installation and deinstallation Oracle central inventory pointer file The STA silent mode installer and deinstaller use the Oracle central inventory location and Oracle install group specified in the central inventory pointer file See Users Groups and Locations Used by the STA Installer on page 3 1 for details
109. Services daemon staservd This procedure is useful if you changed the configuration settings of the STA Backup or STA Resource Monitor services and you want the new settings to take effect immediately If you do not use this procedure the new settings will take effect as soon as the service wakes up from its sleep interval and processes them 1 Stop the STA Services daemon STA stop staservd 2 Start the STA Services daemon STA start staservd 3 Display the status of the daemon to confirm that it is running STA status staservd Verify Library Connectivity When you have finished configuring the services confirm that all configured libraries have completed their Get latest data requests Last Connection Status should indicate SUCCESS and STA should be receiving exchange data from the libraries See the STA User s Guide for details Review the STA Database Backup Utility Preferences Review Table 7 1 for descriptions of the available preference settings and to define your settings 7 2 StorageTek Tape Analytics Installation and Configuration Guide STA Services Configuration Tasks Table 7 1 STA Backup Service Administration Utility staservadm Attributes Option Attribute Description Default Value Your Value S scp File transfer type Method of file transfer used to copy the backup SCP Eat files from the STA server to the backup host p Options are SCP recommended or F
110. T card This is mainly a concern for older libraries shipped before mid 2006 as newer units are shipped with a high memory card See the STA Requirements Guide for detailed firmware level requirements Use this procedure to verify that a high memory HBT card is installed in the library If the library does not have a high memory HBT card submit a service request to Oracle Support to have one installed This procedure is performed using the SL Console For SL8500 FRS 8 x and SL3000 FRS 4 x you can also use the CLI config print command to display HBT card information This procedure is performed using the SL Console 1 Inthe Tools menu select System Detail 2 In the navigation tree select Library 3 Select the Properties tab then select the Drive Controller tab The screen displays details about the active drive controller HBT card 4 Verify that High Memory HBT indicates true 5 If you have an SL3000 FRS 4 x or an SL8500 FRS 8 x library with Redundant Electronics expand the Redundant Electronics folder and then select each HBT card hbta hbtb Both should indicate True for High Memory HBT Note Both the active and standby HBT cards must be installed and communicating and both must have high memory 4 8 StorageTek Tape Analytics Installation and Configuration Guide Library Feature Configuration Tasks Enable ADI on the Library all libraries except SL150 If your library includes LTO drives ADI mu
111. T ALL RACDCERT ID stcuser LIST RACDCERT ID stcuser LISTRING keyringname RACDCERT CERTAUTH LIST To configure AT TLS do the following 1 Specify the following parameter in the TCPIP profile data set to activate AT TLS TCPCONFIG TTLS This statement may be placed in the TCP OBEY file 2 Configure the Policy Agent PAGENT The Policy Agent address space controls which TCP IP traffic is encrypted a Enter the PAGENT started task JCL For example E 24 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers PAGENT PROC PAGENT EXEC PGM PAGENT REGION 0K TIME NOLIMIT PARM POSIX ON ALL31 ON ENVAR _CEE_ENVFILE DD STDENV d1 STDENV DD DSN pagentdataset DISP SHR SYSPRINT DD SYSOUT SYSOUT DD SYSOUT CEEDUMP DD SYSOUT DCB RECFM FB LRECL 132 BLKSIZE 132 Enter the PAGENT environment variables The pagentdataset data set contains the PAGENT environment variables For example LIBPATH 1lib usr lib usr lpp ldapclient lib PAGENT_CONFIG_FILE etc pagent conf PAGENT_LOG_FILE tmp pagent log PAGENT_LOG_FILE_CONTROL 3000 2 _BPXK_SETIBMOPT_TRANSPORT TCPIP TZ MST7MDT In this example etc pagent conf contains the PAGENT configuration parameters Use your own time zone for the TZ parameter Configure PAGENT For example TTLSRule TBI TO ZOS LocalAddr localtcpipaddress RemoteA
112. TA database STA database local backup and STA logs locations For example Is ld Oracle dbdata dbbackup var log tbi drwxr xr x 2 oracle oinstall 4096 Jul 30 14 48 Oracle drwxr xr x 3 root root 4096 Jul 30 14 46 dbdata drwxr xr x 3 root root 4096 Jul 29 14 13 dbbackup drwxrwxrwx 4 root root 4096 Jul 30 14 46 var log tbi In the output for each command look for a dot at the end of the permissions In the following example note the after drxwr xr x ls ld Oracle drxwr xr x 5 oracle oinstall 4096 Jul 30 18 27 Oracle If none of the directories contain a dot after the permissions statement access control is already disabled and you can proceed to the next task If access control is enabled on a directory as the system root user execute the following command for that directory setfattr h x security selinux directory_name For example setfattr h x security selinux Oracle Set Up the Network Proxy You can configure the STA server to connect to the network directly or through a proxy server 1 From the Linux desktop System menu select Preferences then select Network Proxy In the Network Proxy Preferences dialog box specify the proxy configuration according to your site requirements Click Close Ensure Proper Setup of yum optional There are a variety of methods for installing the required RPM Red Hat Package Manager Linux software packages Oracle recommends you use yum Yello
113. TA to perform the other procedures in this section See the STA User s Guide for full instructions 1 Start a supported Web browser on your computer and enter the URL of the STA application http s STA_host_name port_numbernSTA Where a _ host_name is the hostname of the STA server port_numberis the STA port number you specified during installation The default HTTP port is 7021 the default HTTPS port is 7022 a STA must be uppercase For example https staserver example com 7022 STA At the Login screen enter the STA administrator username and password Configuring Library Connections in STA 6 1 STA Configuration Tasks Verify SNMP Communication With a Library Use this procedure to confirm a good SNMP connection between the STA server and a library This procedure verifies that UDP ports 161 and 162 have been enabled on all network nodes between the STA server and the library It cannot validate that an SNMP v3 trap recipient has been specified correctly Perform this procedure for each monitored library For SL3000 or SL8500 libraries with either Redundant Electronics or Dual TCP IP perform this procedure twice for the library once for the primary library IP address and once for the secondary IP address Note This procedure is performed from the system command line on the STA server 1 Open a terminal window on the STA server and log in as the system root user 2 Test the SNMP
114. TP T time Full backup Time of day STA performs a full database backup 00 00 dump time dump The dump is performed automatically every 24 hours at approximately this time The actual time is sometime within sleep interval seconds after this time Format is hh mm using 24 hour time i int Sleep interval Number of seconds the STA Services daemon 300 waits before checking for new incremental backup files S Server Backup host IPv4 or IPv6 address or fully qualified DNS host NA name name of the server host to which the STA server copies its backup files u USr Backup user ID System user ID authorized to perform SCP file NA transfers to the backup host p pwd Backup Password assigned to the backup user NA password d dir Backup directory Directory on the backup host where the backup NA files will be copied U dbusr Database Database username authorized to perform a NA username mysqldump command You should specify the STA Database DBA Account username P dbpwd Database Password of the database username NA password Configure the Remote Database Backup Server Use this procedure to configure a remote backup server or equivalent to receive the compressed backup files generated by the STA database backup service Oracle recommends that you configure a remote backup server The required space is variable the size should be a multiple of the size used for the STA database local backup depe
115. a STA 2 1 64 124 STA 2 0 x STA 2 0 0 83 STA2 0 1 4 STA 1 0 x STA 1 0 0 99 STA 1 0 1 133 STA 1 0 2 24 Note If you are upgrading from STA 1 0 x you must also install a new version of Linux before installing STA 2 1 x See the STA Requirements Guide for details See the following sections for related information Upgrading to STA 2 1 x 8 1 Upgrade Process Overview a See Verify Upgrade Prerequisites on page 8 8 to determine your current STA version See Understanding Automatic and Post installation Upgrades on page 8 2 To determine the type of upgrade Upgrade Process Overview During an upgrade your existing STA data is transformed from the current STA version to the new Your existing STA database is not valid with the new version of STA until these transformations are done After the upgrade STA processes new data according to the new STA schema and analytic rules and historical data is not reprocessed Preparing for the Upgrade Before beginning the upgrade read all instructions in this chapter and be sure to allocate sufficient time for the entire process Some upgrade preparation tasks may require you to coordinate with other groups at your site such as network administration You should have all preparation tasks done in advance so you can complete the upgrade itself in as little time as possible While you are performing the upgrade process STA does not receive exchange info
116. ablespace hwm t 1 DB Backup hwm dbbackup b 1 DB Data hwm dbdata d 1 oe Log Volume hwm var log tbi 1 1 Root Volume hwm z 1 Tmp Volume hwm tmp x 1 System Memory hwm m 1 Email From f StaResMon localhost Email To r Email Subject s STA Resource Monitor Report Output File o var log tbi db staresmon csv Using Table 7 2 as a reference set the attribute values with the staresmonadm command You can submit the attributes in separate commands or combine them into one For example staresmonadm T 13 00 i 600 n on U sta_dba P password1 t 65 b 65 d 65 1 65 z 70 x 80 m 75 r john doe company com The utility sets each value included in your command and then displays all current settings For example Contacting daemon connected Setting DB Tablespace HWM 65 Setting DB Disk Volume HWM 65 Setting Logging Volume HWM 65 Setting Backup Volume HWM 65 Setting Root Volume HWM 70 Setting Temp Volume HWM 80 Setting System Memory HWM 75 Setting To addresses john doe company com Setting Send Time 13 00 Setting Sleep Interval 600 Setting Alert Nag Mode ON Setting DB Username sta_dba Configuring STA Services 7 7 STA Services Configuration Tasks Setting DB Password KKKKKKKKK yes 13 00 600 sec on sta_dba RREKKRE
117. ad the Old STA Database Step 6 through Task 8 Upgrade the Old Database If the upgrade fails again the database is in an unknown possibly damaged state and you should restore the database to its original freshly installed state Proceed to the next step 2 Delete the damaged upgraded database mysql uroot p e drop database stadb 3 Change to the STA database backup location and load the new installation database dump file you created in Task 5 Dump the New STA Database optional on page 8 19 For example cd dbbackup mysql uroot p e lt home oracle STA_FRESH_INSTALL_BACKUP sql 4 Perform Task 8 Upgrade the Old Database on page 8 22 5 Configure STA as a new installation See the following sections for details 8 26 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks a Configuring Library Connections in STA on page 6 1 a Configuring STA Services on page 7 1 Upgrading to STA 2 1 x 8 27 Upgrade Tasks 8 28 StorageTek Tape Analytics Installation and Configuration Guide 9 Deinstalling and Restoring STA This chapter includes the following sections a STA Deinstallation Overview a STA Deinstallation Tasks Caution Oracle does not support downgrading STA to a prior version Database data created with a newer version of STA will be lost when installing an older version of STA STA Deinstallation Overview The STA deinstaller rem
118. ade Preparation Tasks 2 Display all STA database usernames by issuing the following query Enter the database root user password when prompted For example mysql uroot p e select distinct user from user order by user mysql Enter password password root staapp stadba starpt 3 Record the usernames Record STA SNMP Client Settings Use this procedure to display and record SNMP client settings for STA You will reenter these values after the upgrade Note In the new version of STA the SNMP values must match what is specified on the monitored libraries 1 Log in to STA using an STA administrator username 2 From the Setup amp Administration tab select SNMP Connections The Client Attributes table displays configuration settings for the STA SNMP client Configuration SNMP Connections Client Attributes amp tdicetah 3 Record the values from the following columns SNMP Username User Community Trap Community Record WebLogic Usernames Upgrades from STA 1 0 x Only For upgrades from STA 1 0 x use this procedure to display and record existing WebLogic usernames used to log in to STA You will reenter these values after the upgrade You cannot retrieve the passwords Note Starting with STA 2 0 usernames are created and maintained through the STA user interface see Record STA Usernames Upgrades From STA 2 0 x and Higher on page 8 12 for instructi
119. age E 21 Prepare the External Authentication Provider for STA Authentication Use this procedure to prepare an external authentication provider to authenticate STA users This procedure provides general guidelines only as the specific details depend on your site configuration Perform these steps on the external authentication server 1 Identify or create the LDAP Principal user which WebLogic Server will use to access the external authentication provider See LDAP Principal User on page E 2 for details Create the STA access group This group must have the name StorageTapeAnalyticsUser See STA Access Group on page E 3 for details Identify all users needing access to STA and assign them to the STA access group Record site specific configuration information which you will use to configure the provider in WebLogic Server See Task 2 Define Provider specific Information on page E 10 for examples of the information to gather Edit the WebLogic Server Active Security Realm This procedure provides general instructions for logging in to the WebLogic Administration console and making changes to the WebLogic Server active security realm 1 2 Start a supported Web browser on your computer In the Location Bar or Address field enter the URL of the WebLogic Administrator console The URL uses one of the following formats http local_host_name port_numberconsole https local_host_name port_numberconsole where ocal_h
120. ageTek Tape Analytics Installation and Configuration Guide STA Installation and Deinstallation Logs Firewall router configuration Must be reachable between the STA server and the backup server for SSH and between the STA server and the monitored libraries for SNMP and SNMPTRAP Table 3 1 Unconfigurable External Ports Port Protocol Description Purpose 22 SSH Secure Shell STA database backup library log in 161 SNMP Simple Network Management Protocol SNMP For transmittal of SNMP requests 162 SNMPTRAP For reception of SNMP notifications traps Configurable External Ports The ports described in Table 3 2 are external ports used for communication between the STA server and other network entities These ports are the configurable equivalent of standard ports 80 and 8080 HTTP and 443 HTTPS and they must be unique from other HTTP and HTTPS ports on the network Contact your network administrator for assistance in choosing their values Firewall router configuration Must be reachable between the STA server and the client running the STA GUI Table 3 2 Configurable External Ports Default Port Protocol Description Purpose 7019 HTTP Access to the WebLogic Administration console unsecure 7020 HTTPS Access to the WebLogic Administration console secure 7021 HTTP staUi managed server Access to the STA GUI unsecure 7022 HTTPS staUi managed server Access to the STA GUI secure
121. al inventory pointer file this parameter is required only if the file does not exist in the etc directory or you want to use a different file For example sta_install_ 2 1 0 64 124 linux64 bin silent responseFile Installers SilentInstall rsp invPtrLoc opt oracle oraInst loc 3 The installer displays status messages in the terminal window as it performs the following installation steps This process may take 30 to 60 minutes to complete a Performs prerequisite checks on the STA server environment a Installs the included software packages including MySQL WebLogic and the STA application a Configures the STA environment using the settings you have supplied in the response file Starts the STA application Example B 5 shows messages that appear at the end of successful installation Example B 6 shows some messages you might see at the end of a failed installation Example B 5 Successful STA Silent mode Installation Final Messages Started Configuration Deploying STA Application Configuration Deploying STA Application completed successfully Started Configuration Restarting STA this can take up to 30 minutes Configuration Restarting STA this can take up to 30 minutes completed successfully Started Configuration Post Configuration Successfully moved logs to var log tbi install Configuration Post Configuration completed successfully The installation of STA_Install 2 1 0 0 0 completed successfully Logs succe
122. and cleaning driveWarning set off Set the SL500 Volume Label Format SL500 only 4 10 Use this procedure to ensure that volume serial numbers volsers are formatted correctly in SNMP data sent to STA See Volume Label Format SL500 and SL150 only on page 4 4 for details This procedure is performed using the SL500 CLI Note Oracle recommends that you quiesce all activity to the library before changing these parameters Tape applications and or hosts may require configuration changes after changing these parameters 1 Display the current setting of the orientlabel flag SL500 gt orientlabel print Host left8 Window left justified with 6 character label StorageTek Tape Analytics Installation and Configuration Guide Library Feature Configuration Tasks Op Panel left8 Window left justified with 8 character label The host flag must be set to left6 To do so use the following command SL500 gt orientlabel host left6 New settings were accepted Setting are now in effect Display the setting again to verify it was updated correctly SL500 gt orientlabel print Host left6 Window left justified with 6 character label Op Panel left8 Window left justified with 8 character label Display the current setting of the staConfig flag SL500 gt staConfig print STA mode is disabled The staConfig flag must be set to on To do so use the following command SL500 gt staConfig on Display the settin
123. any of the following special characters ee eee ae Accounts and Ports Configured During STA Installation The STA installer configures user accounts and port numbers according to the specifications you provide User Accounts for Managing STA The following required accounts are created during STA installation These accounts are specific to STA and they are not Linux usernames a WebLogic Accounts a STA Database Accounts WebLogic Accounts The following WebLogic accounts are used to log in to the WebLogic administration console or the STA application WebLogic Administration Use to log in to the WebLogic administration console to make changes to the WebLogic environment for example to connect WebLogic to an LDAP or RACF server Installing STA 3 3 Accounts and Ports Configured During STA Installation Caution The username and password for this account are not retrievable If these credentials are lost STA must be re installed STA Administrator Use to log in to the STA application with full access privileges After the STA installation has been completed you can use the STA application to create additional user accounts with assignable roles see the STA User s Guide for details STA Database Accounts The following STA database accounts are MySQL accounts used by STA to access and manage the STA database STA Database Root User Owns the MySQL database and is used to create the root database instal
124. arting silent deinstallation SSeS 20 40 60 80 Internal Error File Copy failed Aborting Install Logs are located here tmp OraInstal12014 09 25_10 07 18AM 6 When the deinstaller completes verify that the STA directories have been removed See Verify Successful Deinstallation on page 9 2 for instructions STA Installer Command Options This section provides reference information for the STA installer options Silent mode options are used exclusively with the silent mode installer and deinstaller Logging and Other options can be used with both modes of installation and deinstallation Silent mode Options The following options are used with the silent mode installer and deinstaller force Allow silent mode installation into a non empty directory invPtrLoc pointer_file Use the specified Oracle central inventory pointer file instead of the one located in etc oralnst loc pointer_file must be an absolute path The contents of the Oracle central inventory file are as follows inventory_loc 0racle_central_inventory_location inst_group 0racle_install_group Where Oracle_central_inventory_location is the absolute path of the Oracle central inventory Oracle_install_group is the name of the Oracle install group B 10 StorageTek Tape Analytics Installation and Configuration Guide STA Installer Command Options response responseFile response_file Required for silent mode
125. assnsgsdsonesdaess issvaedbsccvonsuedsatansas sbacvsessnedtasanonbioacbveesbaata C 3 Port Number Worksheetsis ierste diiirn a na E TE E E E E covdeedts C 3 Domains Namie Worksheet wasise devin coven cite e E E e E AE EE tobeaavisedoese C 4 Post installation Configuration Worksheet cccccccccseses ccs ceeseecscsesesesescscsnseseececsesssnseececenens C 5 vii D Configuring Security Certificates Security Certificate Configuration Tasks 0 ccccsccsssssssssesesescseesesesescsesesesescsesesesesescseseseseseeeses D 1 Establish the Initial HTTPS SSL Connection 0 ccccccccceccsceessscecsssssececssssssecesssscsssessesssseeesesscseesass D 1 Reconfigure WebLogic to use a Different Security Certificate 00 0 ee ce ceeeeeeeeees D 2 Replace th Oracle Certificate iiciccccnweiisierace iis tas inii ie e a A A R dies D 9 E Configuring External Authentication Providers for STA Understanding the WebLogic Server Active Security Realm cee eeeneneeeneees E 1 Considerations for Configuring External Authentication Providers 0 0 ccs E 2 Supported Authentication Provider Types cccscessesesescensnesesesesneesesceeesescsesnseneseseeeeneeeees E 2 Using the WebLogic Administration Console ccccscssseescecesssesnsneseseseeseescsseenesesesnaeneneees E 2 EDAP Principal User oi ieee seuss been eouit toveists A Su toocuasavees beter sells ious avbedsuee E E 2 STA ACCESS Groups ssi titer tne ri as esas aE lee EEES SENAN
126. ata on the server If you are using the single server upgrade method use this procedure only after you have performed Task 1 Dump the Old STA Database on page 8 15 and Task 2 Transfer the Old Database Dump on page 8 17 This procedure applies only to upgrades from STA 2 0 x and higher Deinstall the current version of STA as follows the location of the deinstaller varies depending on the version of STA For upgrades from STA 2 1 x see Deinstall STA on page 9 2 and Verify Successful Deinstallation on page 9 2 for instructions a For upgrades from STA 2 0 x use the following steps 1 Log in as the system root user 2 Change to the STA installation directory For example cd Oracle StorageTek_Tape Analytics_install 3 Launch the STA deinstaller with one of the following commands To use the STA graphical deinstaller Uninstall_StorageTek_Tape_Analytics This mode requires an X11 display See STA Graphical Installer and Dein staller Screen Reference on page A 1 for instructions To use the STA console deinstaller Uninstall_StorageTek_Tape_ Analytics i console Task 4 Install the New STA Version Use this procedure to install STA 2 1 x 1 Install STA 2 1 x see Installing STA on page 3 1 for instructions 2 To verify STA is working properly and complete the STA Administrator setup in WebLogic log in to the STA application The Dashboard is displayed 8 18 StorageTek Tape Analytics Ins
127. atabase Use this procedure to upgrade the old STA database to the new STA 2 1 x schema 1 If you have not done so already stop all STA services STA stop all If you determined in Verify Upgrade Prerequisites on page 8 8 that the size of tmp is not sufficient for the upgrade increase the size of tmp as necessary If this is not possible use the following steps to set an environment variable for MySQL to use an alternate temp location a Create an alternate temp location and assign open permissions to it For example mkdir dbbackup tmp chmod 777 dbbackup tmp b Stop MySQL STA stop mysql 8 22 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks c Edit the MySQL configuration file For example vi etc my cnf d Inthe mysqld section of the file add a line defining the alternate temp location which is identified by the tmpdir variable Following is an example of the file after this line has been added mysqld fasce mysqld MySQL Server Options tmpdir dbbackup tmp server id 1 e Restart MySQL STA start mysql Change to the database updates directory cd Oracle_storage_home StorageTek_Tape_Analytics db updates Start the upgrade script and enter the database root user password when prompted For security reasons the password is not displayed on the screen upgradedb sh Note You can perform this step as either th
128. ath for the response file you have created 6 Respond to each prompt with the appropriate information The password values you enter are not displayed on the screen Example B 7 is a sample utility run Example B 7 Sample Deinstaller Response File Build Utility Run java jar silentInstallUtility 2 1 0 64 124 jar Installers SilentIDeinstall rsp Oracle StorageTek Tape Analytics Silent Installation Utility This utility is used to assist users with the password fields in the Silent Installation response file The silent installation process requireds the password fields in the response file requires the password fields to be encrypted The utility will ask the users for the required passwords and encrypt these values then update the values into the supplied response file Please enter the location to save the key file Installers What is the response file used for i for Install d for Deinstall d Enter system root password Confirm system root password 7 After the utility has completed verify that the encryption key file has been created This is a hidden file with a randomly generated name For example Is la Installers sk i a a 1 oracle oinstall 17 Sep 22 12 00 sk1414437879829 B 8 StorageTek Tape Analytics Installation and Configuration Guide STA Silent mode Deinstaller Tasks 8 View the response file and verify the following values a The system root password has been updated with an encrypted value
129. ay StorageTek Tape Analytics Installation 2 1 0 Deinstallation Progress A 18T17 36 19 339 06 00 sysman NOTIFICATION oracte sysman oii oiii_OiliinstallAresContrd 18T17 36 19 341 06 00 sysman NOTIFICATION oracte sysman oil olli_ Olliinstallinventory 0 187T17 36 19 341 06 00 sysman NOTIFICATION oracte sysman oii oiii Olliinstallinventory 2014 09 18T17 36 19 341 06 00 sysman NOTIFICATION oracle sysman oii olli_ Olllinstallinventory 2014 09 18T17 36 19 342 06 00 sysman NOTIFICATION oracle sysman oii oili Olliinstallinventory 2014 09 18T17 36 19 354 06 00 sysman NOTIFICATION oracle sysman oii olli Olliinstallinventory 2014 09 18T17 36 19 423 06 00 sysman NOTIFICATION oracte sysman oii oiii Oliiinstallinventory Oracle Home STALHome This Oracle Home has not been changed in this session Oracle Home OH193460059 This Oracle Home has not been changed in this session n 2014 09 18T17 36 19 437 06 00 sysman NOTIFICATION oracle sysman oii oiif olifw OilfwOeinstallP 2014 09 18T17 36 19 447 06 00 as NOTIFICATION oracle as install engine modules install actionA 2014 09 18T17 36 19 447 06 00 as NOTIFICATION oracle as install engine modules presentation 2014 09 18T17 36 19 448 06 00 as NOTIFICATION oracie as install engine modules deinstall Deins 2014 09 18T17 36 19 449 06 00 as NOTIFICATION oracle as install engine modules presentation
130. bLogic server This account is used infrequently The account will be created during the installation with the credentials you specify Caution Make a secure record of these account credentials if you lose them you will not be able to log into the WebLogic administration console and STA must be re installed To protect your site security usernames and passwords are purposely not preconfigured nor hard coded Screen Fields Enter Username Type the name you want to assign to the WebLogic Administrator account Username requirements are as follows a Must be 1 16 characters in length a All usernames must be unique Enter Password Type the password you want to assign to this account The entry is masked as you type Password requirements are as follows STA Graphical Installer and Deinstaller Screen Reference A 17 STA Graphical Installer Screens a Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters amp fp lt a fp Nhe Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None STA Administrator StorageTek Tape Analytics Installation 2 1 0 ORACLE STA Administrator va Welcome i H Please enter a username and password for the STA GUI Administrator This y Installation Location account is used to access the STA use
131. c Server Active Security Realm Considerations for Configuring External Authentication Providers a Authentication Provider Configuration Process Overview Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Tasks for Configuring IBM RACF Authentication Providers See Fusion Middleware Securing Oracle WebLogic Server for complete details about managing user authentication with WebLogic Server To create users from within the STA application see the STA User s Guide Understanding the WebLogic Server Active Security Realm WebLogic Server which is included in the STA installation manages all user authentication for STA The STA installation includes one WebLogic Server active security realm named myrealm All authentication providers for STA must be defined in this security realm WebLogic Server includes an embedded LDAP server and this is the default authentication provider for STA During STA installation the embedded LDAP server is configured in the active security realm with the name DefaultAuthenticator The DefaultAuthenticator data store includes credentials for the two default user accounts defined during STA installation the WebLogic Administrator and the default STA Administrator It also includes credentials for all STA usernames created through the STA user interface Note Do not change the names of the myrealm security realm and the DefaultAuthenticator these names are required
132. click Forward and then Yes to continue The STA server does not require a non administrative user In the Date and Time screen a Set the current date and time b Select the Synchronize date and time over the network check box c Add or remove the desired NTP servers obtained from your IT administrator and then click Forward Note To ensure that STA data and log files are correct the date and time on the STA server must be correct Additionally any library connected to STA must also have the correct time On the Kdump screen do not select Enable kdump Then click Finish The system reboots After the system reboots log in as the root user a Click Other b Enter username root and then click Log In c Enter the root password and then click Log In again If a message appears about being logged in as root super user you may ignore the message Confirm the Linux release and update level This step is optional cat etc release Oracle Linux Server release 6 4 Installing Linux 2 7 Post Installation Tasks Red Hat Enterprise Linux Server release 6 4 Santiago Oracle Linux Server release 6 4 Post Installation Tasks Perform the following tasks to ensure that the STA server is configured properly for STA installation Disable SELinux Oracle recommends disabling SELinux on the STA server 1 Open a terminal session on the STA server 2 Open the SELinux configuration file with a text
133. clude any of the following special characters Sg ee fe yr Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None Enter Communication Ports StorageTek Tape Analytics Installation 2 1 0 Ser ORA Enter Communication Ports va Welcome In the following screens you will set port numbers for HTTP and HTTPS Installation Location communication for WebLogic and STA Prerequisite Checks IMPORTANT Make a note of these port numbers Specifically you will need the Enter Root Password port numbers for the WebLogic Admin Console to administer and configure the WebLogic application server and staUi managed server to access the STA user Set up DE Directories interface Set up Admin Accounts Set up Database Accounts Database Root User Database Application User Database Reports User Database Administrator i HH H HK HK 4 4 Emer Communication Ports Help lt Back Next gt Cancel STA Graphical Installer and Deinstaller Screen Reference A 25 STA Graphical Installer Screens This screen describes the types of information you will define on the next four screens Read the text then click Next to continue You will provide values for the configurable internal and external WebLogic and STA ports The ports will be configured and enabled during the installation with the values you specify The port numbers you specify must be unique and
134. ctory and OpenLDAP Authentication Providers Connection Timeout The default value is 0 which indicates no timeout limit Oracle recommends setting this value to a nonzero value such as 60 expressed in seconds a Follow Referrals Select this check box if the external authentication provider is configured to use referrals to other authentication servers See LDAP Authentication Referrals on page E 3 for details Example E 1 and Example E 2 show sample values for an OpenLDAP and a Microsoft Active Directory provider respectively The values you enter will be different but these examples may assist you with entry syntax 6 When you have finished entering screen values click Save Settings for My AD Server Configuration Performance Common Provider Specific Use this page to define provider specific configuration for this LDAP Authentication provider Connection 4E Most 10 123 456 789 tor Pa More Info Example E 1 Sample Provider specific Values for an OpenLDAP Provider Host 10 123 456 789 Port 389 Principle cn root o staOpen dc mycompany dc com Credential OpenLDAP root password gt Confirm credential OpenLDAP root password SSL Enable not selected User Base DN ou users o staOpen dc mycompany dc com All Users Filter User From Name Filter amp cn u objectclass posixAccount User Search Scope subtree User Name Attribute cn User Object Class posixAccount Use Retrieve User Name as Principle se
135. d then the Groups secondary tab Settings for myrealm andPoides Credential Mappings Providers Migration This page Gsplays information about each user that has been configured in this security realm P Customize this table Users Filtered More Columns Exist New Delete Showing 1 to 20f2 Previous Next Name s Description Provider sta_admrin STA administrator DefauttAuthentcator weblogic This user is the default administrator DefauitAuthenticator New Caime Showing 1 to 20f2 Previous Next The Groups screen appears Verify that the Groups table includes groups from all configured external authentication providers The following example shows groups from two external providers Users Groups Ths poge dioi mformation about each goap fet hes bem configured n thes security resin P Customare thes table Groups New me Showing 1 te lief tt Previous Mest Tl Admncnaretises AdmnCharnetisers can access the adain chanel Detanauterncats pram agnrawanrs can ven ard aodfy al resmere stetutes and start and siap servers Detastausreracater teplesies AgoTestes gap Cefata metas lCenDesanCanracters CoenenainConrecters Can muse nier donan calls fom foregn dinara DefndeActharacater Caclovers loaned ahn a sadhana Defaauharaeas es nerars cn wew and mest al resore atirtustes and perform operators rot eS py sa Comeies Coeetors can vien ard myo resource atte and perform server Wecrce PISS losita ond
136. ddr remotetcpipaddress LocalPortRange localportrange RemotePortRange remoteportrange Jobname HTTPserverJobname Direction Inbound Priority 255 TTLSGroupActionRef gAct1 TBI_ICSF TTLSEnvironmentActionRef eAct1 TBI_ICSF TTLSConnectionActionRef cAct1 TBI_ICSF TTLSGroupAction gAct1 TBI_ICSF TTLSEnabled On Trace 2 J TTLSEnvironmentAction eAct1 TBI_ICSF HandshakeRole Server EnvironmentUserInstance 0 TTLSKeyringParmsRef keyR ZOS TTLSConnectionAction cAct1 TBI_ICSF HandshakeRole ServerWithClientAuth TTLSCipherParmsRef cipher1 AT TLS_ Gold TTLSConnectionAdvancedParmsRef cAdv1 TBI_ICSF CtraceClearText Off Trace 2 TTLSConnectionAdvancedParms cAdv1 TBI_ICSF Configuring External Authentication Providers for STA E 25 Tasks for Configuring IBM RACF Authentication Providers ApplicationControlled Off HandshakeTimeout 10 ResetCipherTimer 0 CertificateLabel certificatelabel SecondaryMap Off TTLSKeyringParms keyR ZOS Keyring keyringname TTLSCipherParms cipher1 AT TLS__Gold V3CipherSuites TLS_RSA_WITH_3DES_EDE_CBC_SHA V3CipherSuites TLS_RSA_WITH_AES_128 CBC_SHA where _ localtcpipaddress Local TCP IP address for the HTTP server remotetcpipaddress Remote TCP IP address for the STA client This can be ALL for all TCP IP addresses localportrange Local port of HTTP server specified in the HTTP or SMC startup remoteportrange Remote port range 1024 6
137. de If it does not submit a service request to Oracle Support to upgrade the firmware For SL8500 libraries Oracle Support must record the network connection settings before performing a firmware upgrade as these settings may need to be re entered or updated after the upgrade Using the library CLI all libraries except SL150 not applicable to SL3000 libraries be low FRS 4 x 1 Execute the following command SL500 gt version print Configuring Library Features for STA 4 7 Library Feature Configuration Tasks Library Hardware Information Library Vendor STK Firmware Version xxxx X XX XX Note If the screen displays SYNTAX ERRORI the library firmware is down level Contact Oracle Support to upgrade the firmware Using the SL Console all libraries except SL150 1 Inthe Tools menu select System Detail 2 Inthe navigation tree select Library 3 Select the Properties tab then select the Library Controller tab The firmware version is displayed under the Code Version section Using the SL150 user interface 1 Inthe navigation tree select Firmware The firmware version is displayed under the Library Firmware section Alternately you can click the About button in the status bar to obtain the firmware version Verify the Drive Controller Card Version SL3000 and SL8500 only For SL3000 and SL8500 libraries to send rich drive data to STA the library must have a high memory drive controller HB
138. dules presentation 18713 07 52 393 06 00 as NOTIFICATION oracle as install engine modules presentation iS X Sy gt Close View Log Preparing the installer Starting File Copy Help You can also view the log from the Linux command line While the installer is running logs are kept in a subdirectory within tmp See STA Installation and Deinstallation Logs on page 3 5 for details A 34 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Configuration Progress StorageTek Tape Analytics Installation 2 1 0 ORACLE ae Configuration Progress va The installer will now set up and configure the STA components it will take some time to complete Name Status md Installing MySQL 100 d Setting up STA Schema 100 YA Configuring STA Components 100 C installing Weblogic 7x Installing ADF and Patches Creating STA Domain Configuring STA Domain Configuring STA Managed Servers Starting up STA Managed Servers this can take up to 20 minutes Deploying STA Application Restarting STA his can take up to 30 minutes Daes Canfinurstian a Configuration Progress Configuration Log Location tmp Orainstali2014 10 27_03 21 S9PM install2014 10 27_03 21 S9PM log B y Installing MySQL D vy Setting up STA Schema Y Configuring STA Components 2 Installing WebLogic 2 t installing ADF and Patches Creating STA Domain Help The STA configurat
139. e repository options Then select Customize now and then click Next 20 In the package selection screen use Table 2 3 to configure the packages for each If a package requires an option indicated with a highlight the parent package click the Optional packages button select the child package in the package category a Select a package category b Select the box for each package in the Select column c list and then click Close d Deselect the box for each package in the Deselect column e Leave other check boxes as is Table 2 3 Linux Package Selection Package Category Select Deselect Base System Base a Debugging Tools Compatibility libraries a Dial up Networking Support Console internet tools Directory Client Java Platform a Hardware monitoring utilities Legacy UNIX compatibility Large Systems Performance kSH XXXXXXXX Xx E16 x86_64 a Network file system client Performance Tools Servers optional System administration tools NA Web Services NA All packages Databases NA All packages System Management NA NA Virtualization NA NA Desktops recommended Desktop NA Used to perform certain Desktop Platform post installation steps in a graphical environment see General Purpose Desktop Post Installation Tasks on Graphical Administration Tools page 2 8 for details system config lvm x x xx xx el6 noarch Legacy X Window System compatibilit
140. e Connections Using a Secure Shell SSH If you use a secure shell SSH with X11 forwarding enabled X11 authorization and display are handled automatically for the login user For example if you use this method and log in as the oracle user the SSH service on the STA server automatically sets up the proper X11 authorization and display for the oracle user You should not set the DISPLAY variable manually However if you log in as a different user root for example and then su to oracle the X11 authorizations and display will not be set correctly for the oracle user and you must set them manually Instructions for doing this are outside the scope of this guide contact your Linux administrator for assistance Connecting From a Linux Machine To enable X11 forwarding on a Linux machine use the ssh command with the X or Y options For example ssh X oracle sta_server Connecting From a Microsoft Windows PC Your PC must be running an X11 server such as Xming or Cygwin X and an SSH client such as PuTTY or WinSCP Following is a sample procedure for connecting using PuTTY 1 Verify that the X11 server is running on your PC Contact your system administrator for assistance if necessary 2 Start PuTTY and proceed as follows a Inthe main Session window make the following entries Inthe Host Name field type the name or IP address of the STA server Inthe SSH Connection type field select SSH b Inthe Category menu
141. e complex ID and that all libraries in each library complex share the same complex ID If you need to change the complex ID of a standalone library continue this procedure Configuring Library Features for STA 4 9 Library Feature Configuration Tasks Caution If you need to change the complex ID of a library in a library complex contact Oracle Support Do not continue with this procedure 3 Place the library offline and then wait for all transactions to complete 4 Change the complex ID of a standalone library complex_ID is a number 1 127 config complexId set complex_ID Example 4 1 Change standalone SL8500 complex ID SL8500 gt config complexId set 5 Complex Id 5 Success true Done Note TCP IP stack reset may take a few seconds after command completion Note All TCP IP connections are terminated when executing this command You may have to log back in to the library Set the Drive Clean Warning optional SL3000 and SL8500 only Use this optional procedure to check the current setting of the drive clean warning flag on the library and change it if necessary See Drive Clean Warning SL3000 and SL8500 only on page 4 4 for details This procedure is performed using the library CLI 1 Display the current setting of the drive cleaning warning flag SL3000 gt cleaning driveWarning get Object Drive Cleaning Warning true 2 If you want to set the flag to false off use the following comm
142. e name you want to assign to the STA database reports account for example starpt Username requirements are as follows a Must be 1 16 characters in length a All usernames must be unique Enter Password Type the password to want to assign to this account The entry is masked as you type Password requirements are as follows a Must be 8 31 characters in length STA Graphical Installer and Deinstaller Screen Reference A 23 STA Graphical Installer Screens a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters amp lt gt y o Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None Database Administrator StorageTek Tape Analytics Installation 2 1 0 Database Administrator va Welcome Enter a username and password for the STA database administrator account STA Installation Location uses this account for internal database access Prerequisite Checks Username Requirements Enter Root Password 1 to 16 characters in length Sci i Dis Directories All usernames must be unique Set up Admin Accounts Password Requirements ne P Set up Database Accounts Sto 31 characters in length with no spaces Must contain at least one capital letter and one number except Database Root User amp lt gt Database Application User Database Repor
143. e system root user or the Oracle install user Following is an example of the screen display upgradedb sh DB Root Password STA DATABASE UPGRADE Upgrading DB schema from 58 00r0 to 59 00r0 Started 2014 12 12 15 14 45 STA database is 5 15 GB and contains approximately 12 636 002 records Checking if current database v58 00 is a valid upgrade candidate DB v58 00 is a valid upgrade candidate gt You may ABORT using CTRL C within 7 seconds Sao guaris Oi ast Diba Aire Brake wets PAA 1 gt CTRL C disabled Starting upgrade When the process is complete a banner similar to the following is displayed Caution Wait until you see this banner before proceeding rs rr rr re rr rrr rn nan Started s cue pecnta ee 2014 12 12 15 14 45 Finished sa e aiis 2014 12 12 17 07 11 l Elapsed Time 01 52 26 Upgrading to STA 2 1 x 8 23 Upgrade Tasks Starting Version 58 00r0 Final Schema Version 59 00r0 l Schema Release Date 2014 12 12 11 00 00 Records approximate 12 636 002 l If in Task 8 Upgrade the Old Database on page 8 22 you increased the size of tmp or created an alternate temp location restore it to its normal size and locatio
144. e that the STA server s IP address is mapped to its hostname 1 Open the hosts file with a text editor vi etc hosts Installing Linux 2 11 Post Installation Tasks 2 At the end of the file add the STA server s IP address followed by a tab and then the STA server s hostname For example 127 0 0 1 localhost localhost localdomain localhost4 eel localhost localhost localdomain localhost6 19220220 sta_server 3 Save and exit the file You do not need to restart the STA server for the new setting to take effect Disable Name Services Name services such as LDAP can conflict with STA installation Use this procedure to temporarily disable these services 1 Open the Name Service Switch configuration file with a text editor vi etc nsswitch conf 2 Disable any name service entries For example to disable LDAP comment out Idap from the following lines as shown passwd files ldap nis nisplus shadow files ldap nis nisplus group files ldap nis nisplus 3 Save and exit the file You do not need to restart the STA server for the new setting to take effect After you install STA you can modify the nsswitch conf file to re enable the name services Ensure Local Browser Functionality optional To configure and administer STA locally on the STA server ensure you have the minimum supported browser versions and plugins installed see the STA Requirements Guide Note Oracle does not recomme
145. ease invtate a Check Test Connection or Get Latest Data to enable STA to monitor ibraries OK 5 Click OK to dismiss the message If you have modified an existing library connection the Library Engine ID field in the Monitored Libraries table is cleared indicating the SNMP connection has been dropped Test a Library SNMP Connection Use this procedure to test the SNMP connection between STA and a library and establish or re establish the communication handshake To avoid dropped connections and lost SNMP traps you should perform this procedure for each monitored library whenever you add or change SNMP configuration settings for the library or the STA client You can test only one library connection at a time Note Because a connection test can cause a momentary loss of incoming SNMP packets you should perform this procedure only when necessary Note Before performing this procedure you may want to verify that the library is operational Configuring Library Connections in STA 6 7 STA Configuration Tasks 1 From the Setup amp Administration tab select Configuration then select SNMP Connections 2 Inthe Monitored Libraries table select a library then click Check Test Connection Monitored Libraries as 7x Qaan Recent SMP Trap Automated Dally Last Sux Sry Name Library Complex pE STA IP Address Library Engine ID Communicaton DataRefresh LivaryTme Zone S Connect 10
146. ebLogic Admin Console STA Engine Emer staUi HTTP Port STA Adapter Doz STA UI IAA lt 3 3 3 4 M 4 Enter staUi HTTPS Port Help lt Back Next gt Cancel You specify the staUi managed server port number when you log into the STA application user interface Note These are external communication ports Your network administrator may need to configure firewalls and routers to open communication between the STA server and the client accessing the WebLogic Administration console Note Make a secure record of these port numbers they cannot be changed once STA is installed To protect your site security these numbers are purposely not preconfigured nor hard coded Screen Fields Enter HTTP Port Enter the HTTP port number for unsecure access to the staUi managed server Typically this port number is 7021 Port numbers must be unique and available Enter HTTPS Port Enter the HTTP port number for secure access to the staUi managed server Typically this port number is 7022 Port numbers must be unique and available A 30 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Screen specific Buttons None Diagnostic Agent StorageTek Tape Analytics Installation 2 1 0 A 5 ORACLE Diagnostic Agent va Welcome Enter your sites fully qualified domain name for example us oracle com to Installati
147. ecified in Chapter 2 Installing Linux If a required package is not installed the STA installation will display an error message and not allow you to continue until the package is installed See the following documents for details The STA Requirements Guide for supported Linux versions a Install Required Linux Packages on page 2 10 for a list of required packages Caution Before choosing to permanently remove or replace existing software back up files as needed 1 Verify that STA is not installed on the server The STA installer is used for new installations only See the following sections for other instructions as applicable If you want to upgrade STA from a previous version see Chapter 8 Upgrading to STA 2 1 x a Ifyou need to reinstall STA or repair a current installation see Deinstalling and Restoring STA on page 9 1 The following example shows that STA is not installed ls etc init d sta ls cannot access etc init d sta No such file or directory ls usr bin STA ls cannot access usr bin STA No such file or directory 2 Verify that MySQL is not installed on the STA server If MySQL is installed the installer will remove and reinstall it and all existing MySQL databases will be deleted 3 Verify the tmp directory has at least 4 GB of free space This is the default STA installer working location df tmp Filesystem 1K blocks Used Available Use Mounted on
148. ed screens Displays status messages relevant to processes performed on that screen E Common The following buttons are common to all STA Installer screens buttons a Help Click to display context sensitive help for the screen a Back Click to go to the previous screen to review or change your entries You can go back one screen at a time to the beginning of the installation Next Click to proceed to the next screen after making the necessary entries a Finish Click to complete the installation This button is active only for the final screen Cancel Click to cancel the installation at any time If any part of the installation has been performed the installer will roll back the installation and return the server to its original state You will be prompted to confirm the cancellation STA Graphical Installer and Deinstaller Screen Reference A 7 STA Graphical Installer Screens Installation Location StorageTek Tape Analytics Installation 2 1 0 r ORACLE Installation Location va Welcome y Oracle Storage Home Y installation Location This is a central location to host all library products Oraciel X Browse STA Home This is the location where StorageTek Tape Analytics 2 1 0 will be installed The directory is automatically determined from Oracle Storage Home Oracle StorageTek_Tape_Anaiytics Feature Sets Installed At Selected Oracle Storage Home View Oracle Storage Home must be an absolute
149. editor vi etc sysconfig selinux 3 In the file set SELINUX to disabled SELINUX disabled 4 Save and exit the file Disable the Linux Firewall For optimal system performance Oracle recommends disabling the firewall on the STA server However you may choose to enable and configure the firewall depending on your site requirements Use this procedure to disable the firewall 1 Open a terminal session on the STA server 2 Check the settings of the Linux firewall for next boot chkconfig list grep ip If the firewall is set to be disabled on next boot all output for both iptables and ip6tables will show as off If this is not the case disable the firewall chkconfig iptables off chkconfig ip6tables off 3 Check the current status of the Linux firewall service iptables status service ip6tables status The command output will indicate if the firewall is currently running If the firewall is running stop the firewall service iptables stop service ip6tables stop 4 If either of the following is true you will need to reboot the server a You disabled SELinux in Disable SELinux on page 2 8 a You disabled the Linux firewall using chkconfig in this section 2 8 StorageTek Tape Analytics Installation and Configuration Guide Post Installation Tasks Disable Access Control Access control must be disabled for certain directories 1 List permissions for the Oracle storage home S
150. ee Configure the SNMP Connection to a Library on page 6 5 Otherwise the library may try to send data through those ports unknown to STA and the data will be rejected by STA a Make sure your default gateway is the 2B interface Library Complex ID SL8500 only For STA to roll up library complex data correctly each library complex at your site must have a unique complex ID On SL8500 libraries complex IDs are set manually On all other library models the complex IDs are set automatically and therefore do not require manual intervention or verification Each standalone SL8500 is considered to be a separate complex and therefore must have a unique complex ID In addition each multi library complex must have a Configuring Library Features for STA 4 3 Library Features Affecting STA Data unique complex ID and all libraries within the complex must share the same ID Valid complex ID values are 1 127 Table 4 3 lists some sample valid SL8500 complex ID assignments Table 4 3 Example Complex ID Assignments Complex Type Libraries Assigned Complex ID Multi library complex SL8500 1 1 SL8500 2 1 SL8500 3 1 Standalone libraries SL8500 4 2 SL8500 5 3 Caution The Oracle Service Delivery Platform SDP also uses unique complex IDs for tracking library data If your site uses SDP contact Oracle Support before changing any complex ID Changing the complex ID could cause SDP to fail In most cases co
151. eeees E 21 Tasks for Configuring IBM RACF Authentication Providers 0 cccccce eects ee eeceees E 23 Task 1 Review IBM RACF Mainframe Minimum Requirement cece cece E 23 Task 2 Enable Mainframe Support for STA RACF Authorization ccc E 23 TASK BR COMMSUTC VATE TLS pin ere ea pap ane Aa aeeoe Aeae areae re aa struts E 24 Task 4 Create the RACF Profiles Used by the CGI Routine s ssssssssersssstssttssststesssesttesssestes E 29 Task 5 Import the Certificate File and Private Key File optional cccceceseseseeneteeees E 29 Task 6 Test the CGI Routine cccccccssscsscessesscesseecesceseecsecseecsscsscsaecneceascesssseeeeseseeeeeeseeseecaeenees E 29 Task 7 Set Up RACF SSP for the WebLogic Console eceeeeseececsseesneceeeeees E 30 Task 8 Configure SSL Between STA and RACE ccccccccececcseseseseecscseseseecscssseseeceesssnsnseecsees E 30 Task 9 Configure the WebLogic Server cccececcssssesesescessesesesesesesesesesesesesescsesssesesescseseseseeees E 30 Task 10 Install RACF SSP on the WebLogic Console cccccseseseccsssesesescsceeseescsseseecsees E 31 F Configuring SNMP v2c Mode viii When to Use SNMP v2 Mod ne ataa evk ibaiei a a iE F 1 SNMP v2c Mode Configuration Process se esesseessesissseseessestestiseessestetisresnnsnetestesnesnenteenesnesnee te F 1 SNMP v2c Configurati n Tasks i c cciceccsscscscsescsessctanecccesusscgscodestesstiedeshstucutieetcbveveisuvsbseveububeb
152. efaultidentityAsserter WebLog Idenbty Asser bon promder New Delete Reorder 4 Complete the Create a New Authentication Provider screen as follows and then click OK Name Enter a name to identify the authentication provider in the WebLogic Server security realm For example My External OpenLDAP Server or My AD Server a Type Select one of the following options For OpenLDAP providers select OpenLDAPAuthenticator For Microsoft Active Directory providers select LDAPAuthenticator Note The ActiveDirectoryAuthenticator option is not supported do not use it even for Microsoft Active Directory providers Configuring External Authentication Providers for STA E 9 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Create a New Authentication Provider LOK Cancel Create a new Authentication Provider The following properties wil be used to identify your new Authentication Provider Indicates required fields The name of the authentication provider Name My AD Server This is the type of authentication provider you wish to create Type LDAP Authenticator Cancel y The external authentication provider is added to bottom of the Authentication Providers table Settings for myrealm Configuration Users and Groups Roles and Poldes Credential Mappings Providers Migration Authentication Password Vabdation Authorizaton Adjudication Role Mapping Auditing Credential
153. en click Continue For Linux version requirements see the STA Requirements Guide Click Download for the 64 bit option Save the ISO file and write it to media 2 4 StorageTek Tape Analytics Installation and Configuration Guide Installation Tasks Installation Tasks The following procedures assume an Oracle Enterprise Linux OEL 6u4 DVD installation with graphical installer and setup agent If you install a different version of Linux use different media or use the console mode the steps and packages may vary Gather Required Information Contact your system administrator to obtain the following information Install Linux Hostname and IP address for the STA server Gateway IP address and netmask for your network DNS server IP addresses and search domains for your network IP address of the NTP network time protocol servers you will be using Network proxy information if applicable Use this procedure to perform the Linux installation 1 Bo N 13 14 15 Connect the installation media to the STA server Start the Linux installer using the instructions in the README file on the media Select Install or upgrade an existing system If you are installing from a DVD the CD Found screen appears You can optionally perform a test of the media To skip the test press Tab to highlight the Skip option and then press Spacebar On the Welcome screen click Next Select a language and then click Next
154. er Settings table select the StorageTek Tape Analytics Alerts record then click the Edit Selected SMTP Server icon The Define SMTP Server Details dialog box appears Define SMTP Server Details D SMTP Host Address internal emal router example com SMTP Port From Name StorageTek Tape Analytics Alert From Ema Address sta Gexamole com Enabled J Use Seare Connection Protocol TLS Requires Authentcaton sername Save Cancel 4 Record the values from the following fields Use Secure Connection Protocol Username Rename Custom Templates With STA Prefix optional This procedure applies only if you have custom templates with names prefixed STA During STA 2 1 x installation all templates with the STA prefix are deleted and replaced by new STA predefined templates Use this procedure to assign new names to the templates so they will be preserved during the upgrade Note STA predefined templates are prefixed STA therefore Oracle recommends that you not use this prefix when naming custom templates 1 Log in to STA with an administrator username 2 From the Setup amp Administration tab select Templates Management Upgrading to STA 2 1 x 8 13 Upgrade Preparation Tasks 3 Sort the table by date Created Updated to focus on templates that have been modified since the STA installation date 4 Select the text link of a custom template with name prefixed STA You are ta
155. ernts Servers Sariy foes Ged Onte Sam Gpe SA PedestonServees ecient Moston Tung Owbef rest Monterng Server Surt Pred Servers Seve Ths page kts you veew ant Gefrw eeraa Senare Sockets Layer OR m5ng for Oye server metarce Theos settings Sem you te menage fe serr dl nessa Frenne Meet ty ered Iront lim etmas amira Oange More ja lehewetity Private Key Location or Custom ldertty Keystore t Mise oh Private Key Akas ttaSetientoy More i te A Private Key Passpghrase rrrrrrrr erreen i More Contem Provate Ley Passphrase ocococoocooooooooe Certihcete Location bor Caton Ident Heystore e Mwe JA Trt Trusted Certificate Asthorites fom lowe Sirisd Trust Geystore ot de More rA 17 Complete the Advanced section of the SSL screen as follows Use Server Certs Select the check box a Two Way Client Cert Behavior Select Client Certs Requested But Not Enforced Inbound Certification Validation Select Builtin SSL Validation Only a Outbound Certificate Validation Select Builtin SSL Validation Only Configuring Security Certificates D 7 Security Certificate Configuration Tasks amp Advanced Hostname Verification a Custom Hostname Verifier 1J Use Server Certs Two Way Client Cert a Cert Authenticator BEA Hostname Verifier x Client Certs Requested But Not Enforced IJ SLRejection Logging Enabled 1 G amp Allow Unencrypted Null Cipher Inbound Certificate Validation
156. ersion 11 X11 X11 configuration is outside the scope of this guide however the following general guidelines apply For additional information contact your system administrator For you to run the graphical mode installer and deinstaller the X11 service must be running on the STA server and configured to allow X11 forwarding If Linux was installed as instructed in Chapter 2 Installing Linux these conditions should already be met In addition X11 authorizations and display must be set correctly for the Oracle install user This is handled differently depending on whether you are logging in through a local or remote connection See the following sections for details a Local Connections on page A 1 a Remote Connections Using a Secure Shell SSH on page A 2 a Remote Connections Using Desktop Sharing on page A 2 a Troubleshooting Graphical Display Issues on page A 3 Note Response time for remote connections depends on your network and VPN configurations and performance Local Connections For direct connections to the STA server you must log in as the Oracle install user and then set the DISPLAY variable manually For example export DISPLAY hostname 0 0 STA Graphical Installer and Deinstaller Screen Reference A 1 Graphical mode Display Requirements You may also need to verify that the Oracle install user has the proper X11 authorization Contact your Linux administrator for assistance Remot
157. erver certificate validation rules for outbound SSL More Info Select the ISSE SSL implementation to be used in Weblogic More Info 19 In the Change Center section click Activate Changes ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefere View changes and restarts Home Summery of Securty Pending changes exist They must be activated Settings updated succe Settings for myrealm Save 20 Log out of WebLogic 21 Stop all STA services See the STA Administration Guide for command usage details Configuration Users ar Generat roes seare D 8 StorageTek Tape Analytics Installation and Configuration Guide Security Certificate Configuration Tasks 22 STA stop all topping the uccessfully topping the staui service stopped the staui service staadapter service uccessfully stopped the staadapter service topping the staengine service uccessfully stopped the staengine service topping the weblogic service uccessfully stopped the weblogic service topping the staservd Service uccessfully stopped staservd service topping the mysql service Successfully stopped mysql service NDNANNNNNNNNYN NHN Start all STA services STA start all tarting mysql Service sql service was successfully started tarting staservd Service taservd service was successfully started tarting weblogic Service eblogic service was success
158. es See Chapter 7 Configuring STA Services for details 2 Create STA usernames and passwords see the STA User s Guide for instructions You may also want to do the following a Notify users of the new password requirements for STA 2 1 x a Direct users to reenter their custom user preferences if applicable 3 Ifthe STA email server requires authentication you must enter the email account username and password see the STA User s Guide for instructions 4 Restore original ownership to custom templates as applicable see the STA User s Guide for instructions 5 Restore original ownership to private Executive Report policies as applicable see the STA User s Guide for instructions Decommission the Old STA Server optional This procedure applies only if you used the two server upgrade method You can use this procedure after verifying that the new STA server is functioning as expected 1 Remove the old STA server as a trap recipient from each library s SNMP configuration See the STA User s Guide for instructions 2 Decommission the old STA server Recover a Failed Database Upgrade optional Caution Perform this procedure only under the direction of your Oracle support representative Use this procedure only if the database upgrade in Task 8 Upgrade the Old Database on page 8 22 does not complete successfully and attempts to repeat the upgrade have also failed 1 Repeat Task 7 Process and Lo
159. es and Drives STA Deployment Process Overview To install and configure STA for the first time perform the following activities in the order listed You can perform the process yourself or purchase Oracle installation services 10 11 Note To upgrade STA from a previous version see Chapter 8 Upgrading to STA 2 1 x Review and verify STA requirements at your site See the STA Requirements Guide Review installation and configuration best practices See Best Practices for STA Deployment on page 1 2 Prepare service requests for the drives and libraries as necessary See Prepare Service Requests for the Libraries and Drives on page 1 5 Install Linux on the STA server See Installing Linux on page 2 1 Install STA on the STA server See Installing STA on page 3 1 Configure the libraries to send data to STA See Configuring SNMP on the Libraries on page 5 1 Configure STA to receive data from the libraries and begin monitoring See Configuring Library Connections in STA on page 6 1 Configure additional STA usernames and email addresses See the STA User s Guide Configure STA monitoring and database backup services See Configuring STA Services on page 7 1 Configure one or more approved security certificates optional See Configuring Security Certificates on page D 1 Configure one or more external providers for STA access control optional See Configuring External Authentication P
160. es not exist the installer will create it automatically if the Oracle install user has full permissions to the parent directory Operating System Group Select the Linux group you want to designate as the Oracle install group All members of this group will be able to install Oracle software on this server The menu lists all groups to which the Oracle install user belongs The default is the Oracle install user s primary group STA Graphical Installer and Deinstaller Screen Reference A 5 STA Graphical Installer Screens Screen specific Buttons Browse Click to navigate to the directory you want to specify OK Click to initiate the STA installer The Installation Inventory Setup window disappears and there may be a slight delay before the STA Installer Splash Screen appears Welcome StorageTek Tape Analytics Installation 2 1 0 ORACLE Welcome va Welcome Installation Location The following screens will guide through the installation of StorageTek Tape Analytics STA 2 1 0 Prerequisite Checks Oracle strongly recommends that you quit all programs before beginning installation Enter Root Password To change the settings on a previous screen click Back To cancel the installation at any time click Cancel Set up 08 Directories Set up Admin Accounts Set up Database Accounts Enter Communication Ports Configure RDA installation Summary 3J 4 Copyright c 2012 2015
161. ese worksheets include information required by the STA installer See Accounts and Ports Configured During STA Installation on page 3 3 for complete details about the requested information If you are upgrading from a previous version of STA you can use the Current columns in the worksheets to record the values used in your current installation Use the STA 2 1 x columns to record the values you will use for STA 2 1 x Installation Users and Locations Worksheet 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 STA 2 1 x Value Oracle install Linux group used for installing and upgrading group Oracle products on the STA server New for STA 2 1 x Oracle install Linux user for installing and upgrading Oracle user products on the STA server New for STA 2 1 x Oracle central Directory for tracking information about Oracle inventory products installed on the STA server New for location STA 2 1 x Oracle storage Directory where STA and associated Oracle home location software are installed New for STA 2 1 x C 2 StorageTek Tape Analytics Installation and Configuration Guide Installation and Upgrade Worksheets Table C 2 Cont Installation Users and Locations Worksheet Item Description Current Value STA 2 1 x Value STA installer Location where the STA installe
162. esscsssnsneseeeeesen 7 7 8 Upgrading to STA 2 1 x Valid STA Z1 x Upgrade Paths cics aa a iae a o EE E a 8 1 Upgrade Process OvetvieW n nieas teinerie tess hates datcaeteehsniseuesesdetenessetersgpiebenacisscsesbendusdsvedneatibstehestebies 8 2 Preparing forthe Upgr dep missotisnie pe aaa aeaaea Ea aa 8 2 Understanding Automatic and Post installation Upgrades cccccssseseeeesesesceneneesesneneteneees 8 2 Choosing Whether to Use One Server or TWO ccccccscscssssesseseesesceceseecenenenenesesneseseseeceeesessseananenens 8 3 Single server Upgrade M thodsssssrireskiieniiieiiecan iii n E E R i aii 8 3 Two server Upgrade M thod dreii er E E E E 8 4 Environment Changes for STA ZIX ii nei a a pao rA E S SE A a 8 5 kinux Yerle kansan EA E E E RS 8 5 Default WebLogic Port Numbers 5 00 scohsccesneedsnaedtaseatavisedeissiatacesstepeeiea aa Apiai 8 5 Required Ports for STA 2 0 and Higher ccccc cece ccc cece ceeeeseececssessssnesesesesenesesesesesenesesenans 8 6 Username and Password Requirements cccccccccescsnsseesesseisiesescecesesesnenssneseseeeseseseecesesssesnanenes 8 6 Upgrade Preparation Tasks enrritine ianen niner ie ete costes i E ieS 8 6 Verify Your Site is Ready for the Upgrade sssssssssesrssessesississtsssesisstesensnestentessessnsnentennessesnente 8 8 Save Existing Logs optional sesssserss nads iaa ar i N 8 9 Record Current STA User and Configuration Settings Optional se ssssesssssssrsrsssess
163. essssssssissesssesiesisssessesiesieseesnnsneneesrnssesnentenness 6 2 Configure SNMP Client Settings for STA s ssssssessessississessesssesisrissesstesiesiestsnensteniesrentnsneneeneeneens 6 3 Configure the SNMP Connection to a Library s s ss ssessssssssissssssesssstessessesnestentisresnesnennesnesnesneenees 6 5 Testa Library SNMP Connections aitase an EEE E a E a aget aa ikoa ee a 6 7 Perform a Manual Data Collection sperii eenaa a aa ipanaa sia eaaa 6 9 7 Configuring STA Services STA Services OVeryIeW ispida a aenar ata ai i Daana inania iri 7 1 STA Services Configuration Tasks 0 ccccccecc cesses pidades iii irii iiiaio 7 1 Update the System Path optionals enonsa a e e 7 2 Restart the STA Services Daemon optional se ssessessessissessesrsesieseessessesrestestnsnesnentennessesnesneenees 7 2 Verify Library Connectivity e sneti ie e E EE E R RR A 7 2 Review the STA Database Backup Utility Preferences se sssssestsseserstsrssrsttsstesstesntesstenteessertte 7 2 Configure the Remote Database Backup Server ss ses sseseritsrisrstesriesstsrtessserttesstetisnterstestesstn tt 7 3 Configure the STA Database Backup Service ss ssssssssssisssissessestetissessestetissisnnsnentessessesnenteeness 7 4 Review the STA Resource Monitor Utility PreferenceS e seessesssresesstsrisssterttesstestesssertessseentes 7 5 Configure the STA Resource MOmitor cccccccccssescssssssssnesesescsesesesescseseseecsesssssese
164. ew Successful Tasks Select the check box to include Success outcomes in the display this is the default Clear the check box to display only Failure or Warning outcomes This allows you to filter out successful tasks so you can focus on the ones requiring attention View Log Click to display the prerequisite verification log in a separate window Figure A 4 is an example Click Close to dismiss the log window A 12 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Figure A 4 Sample Prerequisite Verification Log Display StorageTek Tape Analytics Installation 2 1 0 Prerequisite Checks Pr Welcome i 100 Installation Location Prerequisite 6 lt lt Enter Root Pad Check complete The overall result of this check is Passed et up DB Dire 1n Set up Admin 2014 09 18713 19 03 770 06 00 as NOTIFICATION oracle as install engine modules prereq host et up Databal I 2014 09 18T13 19 03 775 06 00 as NOTIFICATION oracle as install engine modules presentation Enter Commuf 2014 09 18T13 19 03 779 06 00 as NOTIFICATION oracle as install engine modules prereq host 1 Check Description This is a prerequisite condition to test whether xauth is installed nfigure R n 2014 09 18T13 19 05 197 06 00 as NOTIFICATION oracle asinstall engine modules presemation 2014 09 18713 19 05 199 06 00 as NOTIFICATION oracie as insta
165. fault for STA 1 0 x and 2 0 x was 7001 Secure port for the WebLogic External HTTPS 7020 Administration console default for STA 1 0 x and 2 0 x was 7002 Unsecure port for the staUi managed server External HTTP 7021 which manages the STA GUI Secure port for the staUi managed server External HTTPS 7022 Unsecure port for the staEngine managed Internal HTTP 7023 server which manages basic STA internals Secure port for the staEngine managed Internal HTTPS 7024 server Unsecure port for the staAdapter managed Internal HTTP 7025 server which manages SNMP communication with the monitored libraries Secure port for the staAdapter managed Internal HTTPS 7026 server Domain Name Worksheet Table C 6 includes your site s fully qualified domain name used by Oracle s Remote Diagnostic Agent RDA when generating STA service logs C 4 StorageTek Tape Analytics Installation and Configuration Guide Post installation Configuration Worksheet Table C 6 Company Domain Name Required Information Current Value STA 2 1 x Value Company domain name for example us example com Post installation Configuration Worksheet 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 on page 5 1 for complete
166. fer Old Database Process amp Load Old Upgrade Database Configure New STA Database optional Database SETTE Two server Upgrade Method The two server upgrade method requires a second dedicated STA server but it offers the advantage of reduced STA application downtime This method is especially useful if you are upgrading from STA 1 0 x as the old version of STA can continue to monitor libraries on the old server while both Linux and the new version of STA are installed on the new server Even with this method however STA is not monitoring libraries while you upgrade the current database to the new STA version The length of downtime depends on the size of your current database Figure 8 2 illustrates the two server method You must complete the tasks in the order shown they are not done in sequential order and Task 6 is omitted Note that you do not dump the current STA database until after you install the new version of STA on the new server In summary Depending on whether the second server is currently running a version of STA either install Linux 6 x Task 3a or deinstall the old version of STA Task 3b a Install STA 2 1 x on the new server and as a precaution dump the new database Task 4 and Task 5 Dump the current database on the old server and transfer it to the new server Task 1 and Task 2 Load and upgrade the current database to the new STA version Task 7 and Task 8 _Reestablish connections t
167. figuration c Export the CA and client certificates to be transmitted to STA RACDCERT EXPORT LABEL calabel CERTAUTH DSN datasetname FORMAT CERTB64 where calabel Label for certificate authority specified in the CA certificate definition datasetname Data set to receive the exported certificate RACDCERT EXPORT LABEL clientlabel ID stcuser DSN datasetname FORMAT PKCS12DER PASSWORD password where clientlabel Label for the client certificate E 28 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers stcuser RACF user id associated with the TCPIP address space datasetname Data set to receive the exported certificate password Password for data encryption Needed when the certificate is received on STA The password must be eight characters or more The export data sets are now transmitted to STA and FTP can be used The CA certificate is transmitted with an EBCDIC to ASCII conversion The CLIENT certificate is transmitted as a BINARY file and contains both the client certificate and its private key Task 4 Create the RACF Profiles Used by the CGI Routine The profiles are defined in the FACILITY class The first of the profiles is called SMC ACCESS STA and determines whether a user has access to the STA application A user who requires access to STA must have READ access to this profile The o
168. for STA Note The active security realm also includes a provider named DefaultidentityAsserter Do not make any changes to this provider Configuring External Authentication Providers for STA E 1 Considerations for Configuring External Authentication Providers Considerations for Configuring External Authentication Providers For most sites the DefaultAuthenticator may be the only authentication provider needed for STA You can create and maintain STA usernames through the STA user interface and the DefaultAuthenticator will authenticate and authorize users as they log in For some sites however it may be desirable to use external providers in addition to the DefaultAuthenticator to authenticate STA users This is useful if your site has many users with credentials already defined on external authentication servers You can configure one or more external authentication providers for STA The following sections provide information for configuring external authentication providers for STA a Supported Authentication Provider Types on page E 2 Using the WebLogic Administration Console on page E 2 LDAP Principal User on page E 2 m STA Access Group on page E 3 a Default STA User Role on page E 3 a Configuring the Authentication Process for Multiple Providers on page E 3 a LDAP Authentication Referrals on page E 3 a Using SSL for Communications on page E 4 Supported Authentication Provider
169. fully started tarting staengine Service taengine service was successfully started tarting staadapter Service taadapter service was successfully started tarting staui Service taui service was successfully started n 3 a NN NN NE NN NWN Replace the Oracle Certificate 1 Start a supported Web browser on your computer and enter the HTTPS SSL version of the URL for the STA application https STA_host_name port_number STA Where a __ host_name is the hostname of the STA server port numberis the STA port number you specified during installation The default HTTP port is 7021 the default HTTPS port is 7022 a STA must be uppercase For example https staserver example com 7022 STA Select I Understand the Risks on the This Connection is Untrusted screen Click Add Exception To specify a certificate for your organization click Get Certificate on the Add Security Certificate screen and select the appropriate file Click Confirm Security Exception Configuring Security Certificates D 9 Security Certificate Configuration Tasks D 10 StorageTek Tape Analytics Installation and Configuration Guide E Configuring External Authentication Providers for STA This appendix describes how to configure Oracle s WebLogic Server to use one or more external authentication providers to authenticate users for STA It includes the following sections Understanding the WebLogi
170. g the following parameters must be set a For all SL500 libraries monitored by STA the label orientation for the host must be set to left and STA mode controlled by the staConfig flag must be set to on STA 4 4 StorageTek Tape Analytics Installation and Configuration Guide Library User Interfaces mode affects only the format of the volser sent to the STA server through SNMP not the format used on the SL500 library itself a For all SL150 libraries monitored by STA the Volume Label Format must be set to Trim last two characters Caution If these parameters are not set properly volsers will be formatted incorrectly causing exchanges processing to be blocked superfluous attempts to get the latest media data and irreversible eight character volser records to appear on the Media Overview screen whenever the Show Removed Media preference is set See Set the SL500 Volume Label Format SL500 only on page 4 10 and Set the SL150 Volume Label Format and Drive Element Addressing Mode SL150 only on page 4 11 for instructions SCSI FastLoad Option SL500 only The SCSI FastLoad option should be disabled on SL500 libraries as cartridge mount traps are not properly sent to STA when SCSI FastLoad is enabled FastLoad is disabled by default Contact Oracle Support if you are not sure of the status of this option Duplicate Volume Serial Numbers In the STA data store media history is retained by volume ser
171. g again to verify it was updated correctly SL500 gt staConfig print STA mode is enabled Set the SL150 Volume Label Format and Drive Element Addressing Mode SL150 only Use this procedure to ensure that volume serial numbers volsers are formatted correctly in SNMP data sent to STA Also for SL150 firmware 2 xx and above use this procedure to set the Drive Element Addressing Mode so that empty drive bays are included in the data sent to STA See Volume Label Format SL500 and SL150 only on page 4 4 for details Note Oracle recommends that you quiesce all activity to the library before changing these parameters Tape applications and hosts may require configuration changes after changing these parameters This procedure is performed using the SL150 browser based interface 1 2 3 In the navigation tree select Configuration Select the Configure button In the Configuration Wizard window select the Configure Library Settings check box and then click Next Set the following parameters accordingly a Drive Element Addressing Mode Address All Drive Slots Recommended Library Volume Label Format Trim last two characters Default Note After changing the Drive Element Addressing Mode you should wait at least 10 minutes before configuring SNMP in STA Click Next Configuring Library Features for STA 4 11 Library Feature Configuration Tasks 6 On the Summary of Configuration C
172. gt snmp addTrapRecipient trapLevel 5 8 StorageTek Tape Analytics Installation and Configuration Guide Library SNMP Configuration Tasks 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 host STA_server_IP version v3 name recipient_name auth SHA authPass auth_password priv DES privPass priv_ password engineId library_engineID Where a STA_server_IP is the IP address of the STA server recipient_name is the SNMP user name you created in Create an SNMP v3 User on page 5 7 a auth_password and priv_password are the authorization and privacy passwords you created in Create an SNMP v3 User on page 5 7 library_enginelD is the library engine ID you displayed in Retrieve the Library SNMP Engine ID all libraries except SL150 on page 5 8 including the 0x prefix Note For SL3000 and SL8500 libraries enclose recipient_name auth_ password and priv_password in single quotes Example 5 3 Example 5 3 Create SNMP v3 Trap Recipient on SL3000 or SL8500 SL3000 gt snmp addTrapRecipient trapLevel 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 host 192 0 2 20 version v3 name STAsnmp auth SHA authPass authpwd1 priv DES privPass privpwd1 engineId 0x00abcde 000000000000000000 Example 5 4 Create SNMP v3 Trap Recipient on SL500 SL500 gt snmp addTrapRecipient trapLevel 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 host 192 0 2 20 version v3 name STAsnmp auth SHA authPass authpwd1 priv DES privPass pri
173. gure multiple Authentication providers in a security realm Different types of Authentication providers are designed to access Gfferent data stores such as LDAP servers or DBMS You can also configure a Realm Adapter Authentication provider that allows you to work with users and groups from previous releases of WebLogic Server Customize this table Showing ito 3of3 Previous Next 1 0 t 4 0 T 1 Lo WebLogic Authentication Provider WebLogic Identity Assertion provider Provider that performs LDAP authentication Showing 1 to 3of3 Previous Next The Settings for authenticator screen appears In the control bar select the Configuration tab and then the Provider Specific secondary tab Configuring External Authentication Providers for STA E 11 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Settings for My AD Server Configuration Performance Save This page displays basic information about this LDAP Authen to control how this provider is used in the login sequence a Mame My AD Server The Provider Specific screen appears Settings for External OpenLDAP Server This page displays basic information about this Open LDAP A control how this provider is used in the login sequence 5 Complete the screen attributes using the values you gathered from the external authentication provider These values must match the directory schema and other configuration att
174. h Oracle_storage_home StorageTek_Tape_Analytics common bin STA lib config steps sh where Oracle_storage_home is the directory where STA and associated Oracle software are installed See Users Groups and Locations Used by the STA Installer on page 3 1 for details For additional information about the script and to see example usage issue the following command sh Oracle_storage_home StorageTek_Tape_Analytics common bin STA lib config steps sh more Library Feature Configuration Tasks Use Table 4 4 to determine which tasks apply to the library models at your site You must perform the applicable tasks on each library you want STA to monitor Table 4 4 Tasks to Configure Libraries for STA Task SL150 SL500 SL3000 SL8500 Log In to the Library on page 4 7 Yes Yes Yes Yes Verify the Library Firmware Version on page 4 7 Yes Yes Yes Yes Verify the Drive Controller Card Version SL3000 and SL8500 only on page 4 8 Yes Yes 4 6 StorageTek Tape Analytics Installation and Configuration Guide Library Feature Configuration Tasks Table 4 4 Cont Tasks to Configure Libraries for STA Task SL150 SL500 SL3000 SL8500 Enable ADI on the Library all libraries except SL150 on page 4 9 Yes Yes Yes Ensure the Correct Library Complex ID SL8500 only on page 4 9 Yes Set the Drive Clean Warning optional SL3000 and SL8500 only on Yes Yes page 4 10 Se
175. hanges screen select the Accept all changes check box and then click Apply 7 Inthe Apply Configuration Changes screen select the Set the Library back Online after applying the changes check box and then click OK 8 When you see All configuration changes have been applied successfully click Close 4 12 StorageTek Tape Analytics Installation and Configuration Guide 9 Configuring SNMP on the Libraries For STA to monitor libraries at your site you must perform some configuration activities on the libraries and some on the STA server This chapter describes activities performed on the libraries You should complete the activities in this chapter before continuing to Chapter 6 Configuring Library Connections in STA This chapter includes the following sections Understanding Library SNMP Configuration for STA a Library SNMP Configuration Tasks For general information about the SNMP implementation on the StorageTek libraries see the StorageTek Modular Libraries SNMP Reference Guide Understanding Library SNMP Configuration for STA Communication between STA and the libraries it monitors is through the Simple Network Management Protocol SNMP The libraries send data to STA through SNMP traps and informs and STA retrieves library configuration data through SNMP get functions In SNMP terms STA is a client agent and each library is a server agent For optimal SNMP security Oracle recommends using the SNMP v3 protocol
176. he STA Database Backup Utility Preferences on page 7 2 a Configure the Remote Database Backup Server on page 7 3 a Configure the STA Database Backup Service on page 7 4 STA Resource Monitor Configuration Tasks a Review the STA Resource Monitor Utility Preferences on page 7 5 a Configure the STA Resource Monitor on page 7 7 Configuring STA Services 7 1 STA Services Configuration Tasks Update the System Path optional Use this procedure to ensure that the STA bin directory is included in the PATH variable for the system root user The bin directory includes the STA service utilities staservadm and staresmonadm 1 Open a terminal session on the current STA server and log in as the system root user 2 Use a text editor to open the user profile For example vi root bash_profile 3 Add the STA bin directory to the PATH definition For example add the following line to the file PATH PATH Oracle_storage_home StorageTek_Tape_Analytics common bin Where Oracle_storage_home is the Oracle storage home location specified during STA installation 4 Save and exit the file 5 Log out and log back in as the system root user 6 Confirm that the PATH variable has been updated correctly echo PATH usr 1ib64 qt 3 3 bin usr local sbin usr local bin sbin bin usr sbin usr bin root bin Oracle StorageTek_Tape_Analytics common bin Restart the STA Services Daemon optional Use this procedure to restart the STA
177. he StorageTapeAnalyticsUser role Configuring External Authentication Providers for STA E 29 Tasks for Configuring IBM RACF Authentication Providers Note The STA RACF authorization facility does not support changing the password of mainframe user IDs If a user ID password expires STA indicates this and the password must be reset through normal mainframe channels before attempting to log in to STA again Task 7 Set Up RACF SSP for the WebLogic Console The RACF Security Service Provider or RACF SSP must be installed as a plug in into WebLogic If the RACF SSP has been installed the STA installer should put the RACF SSP in the appropriate location within WebLogic If it has not been installed place the RACF security jar file into the directory as follows Oracle_storage_home Middleware wlserver_10 3 server lib mbeantypes staRACF jar where Oracle_storage_home is the Oracle storage home location specified during STA installation Task 8 Configure SSL Between STA and RACF 1 Install the required PTFs on the MVS system These PTFs allow for authentication with RACF or other third party security software when you are logging on to the STA For PTF requirements see the STA Requirements Guide The Application Transparent TLS AT TLS has been configured on MVS so that the port number defined to the SMC HTTP Server and WebLogic is encrypted to the server Before proceeding ensure you possess two files the MV
178. he database application account is a MySQL account used internally by the STA application to connect to and update the STA database The account provides create update delete and read access to all database tables You will not use this account for normal STA operations This account will be created during the installation with the credentials you specify STA Graphical Installer and Deinstaller Screen Reference A 21 STA Graphical Installer Screens Note Make a secure record of these account credentials To protect your site security usernames and passwords are purposely not preconfigured nor hard coded Screen Fields Enter Username Type the name you want to assign to the STA database application account for example stadb Username requirements are as follows Must be 1 16 characters in length a All usernames must be unique Enter Password Type the password to want to assign to the STA database application account The entry is masked as you type Password requirements are as follows Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters E i a re a E poe Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None A 22 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens
179. ial number volser Because all history for a particular piece of media is tied to its volser Oracle recommends that you avoid duplicate volsers Volsers should be unique across all monitored libraries Duplicate volsers will result in co mingling of data for different pieces of media See the STA User s Guide for additional detail about duplicate volsers Library User Interfaces The SL500 SL3000 and SL8500 libraries have a command line interface CLI and a graphical user interface the StorageTek Library Console SL Console The SL150 library uses a browser based user interface exclusively You will use these interfaces to perform the procedures in this chapter Library CLI Usage Tips For most CLI commands the syntax is the same across the SL500 SL3000 and SL8500 library models For the few commands where the syntax varies by library model examples are provided Most CLI examples use an SL500 library If you are configuring an SL3000 or SL8500 library the details returned by each command may vary slightly from what is shown Following are some tips for using the library CLI a Use a terminal emulator such as PuTTY to establish an SSH secure shell connection to the library CLI Enable logging so you can review your activity should you need to troubleshoot errors a With some firmware versions the CLI times out after six hours Configuring Library Features for STA 4 5 Library Feature Configuration Tasks To
180. iguration Guide STA Graphical Installer Screens Screen Fields Enter Password Type the password to want to assign to the STA database root user The entry is masked as you type Password requirements are as follows a Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters amp 4s 72 Ye Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None Database Application User StorageTek Tape Analytics Installation 2 1 0 i ORACLE Database Application User Welcome 1 Enter a username and password for the STA database application account STA T installation Location uses this account for internal database access Prerequisite Checks T Username Requirements y Enter Root Password 1 t 16 characters in length I SA x y Set up D8 Directories All usernames must be unique I AA Setup Admin Accounts Password Requirements 8to3 spac Ap Setup Database Accounts 8 to 31 characters in length with no spaces i Must contain at least one capital letter and one number except y Database Root User OE S r A E a aa Database Application User i Emer STA Database Application Username stadb Enter STA Database Application Password eeeceeee Confirm STA Oatabase Application Password eeeeeeee Help lt Back Next gt Cancel T
181. ils the installation stops and you must exit the installer by clicking Cancel The installer will roll back the installation and return the server to its original state STA Graphical Installer and Deinstaller Screen Reference A 33 STA Graphical Installer Screens Before you exit you can view additional detail in the Message pane to help you troubleshoot issues and determine what action to take You can also view the installation log for additional information Screen Fields None Screen specific Buttons View Successful Tasks Select the check box to include Success outcomes in the display this is the default Clear the check box to display only Failure outcomes This allows you to filter out successful tasks so you can focus on the ones requiring attention View Log Click to display the installation log in a separate window Figure A 5 is an example Click Close to dismiss the log window Figure A 5 Sample Installation Progress Log Display StorageTek Tape Analytics Installation 2 1 0 RA A Installation Progress ia 18T13 07 44 875 06 00 as NOTIFICATION oracle as install engine modules install host tla 18T13 07 44 875 06 00 as NOTIFICATION oracle as install engine modules presentation 18T13 07 44 876 06 00 sysman NOTIFICATION oracle sysm an oii clic OiicAPlinstalier ho 0 sysman NOTIFICATION oracle sysman oll clic OlicAPliinstaller ho 0 sysman NOTIFICATION oracle sy
182. ine service Stopping the weblogic service Successfully stopped the weblogic service Stopping the staservd Service Successfully stopped staservd service Stopping the mysql service Successfully stopped mysql service 5 Start all STA services STA start all Starting mysql Service mysql service was successfully started Starting staservd Service staservd service was successfully started Starting weblogic Service weblogic service was successfully started Starting staengine Service staengine service was successfully started Starting staadapter Service staadapter service was successfully started Starting staui Service staui service was successfully started 6 Proceed to Verify Configuration of Authentication Providers on page E 21 E 20 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Verify Configuration of Authentication Providers After you have finished configuring one or more external authentication providers for STA use this procedure to verify that WebLogic Server can access the appropriate users and groups 1 If you have not done so already access the active security realm and lock it for editing See Edit the WebLogic Server Active Security Realm on page E 5 for instructions In the Settings for myrealm control bar select the Users and Groups tab an
183. ing the library CLI all libraries except SL150 1 2 Establish a CLI session on the library Create an SNMP v2c trap recipient gt snmp addTrapRecipient trapLevel 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 host STA_server_IP version v2c community community_name Where STA_server_IP IP address of the STA server community_name SNMP v2c trap community string For example gt snmp addTrapRecipient trapLevel 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 host 192 0 2 20 version v2c community stasnmp request Id request Id 2 Device 1 0 0 0 Success true Done Failure Count 0 Success Count 1 List the trap recipients to verify that STA has been added correctly gt snmp listTrapRecipients requestId requestId 3 Attributes Community stasnmp Host 192 0 2 20 Index 1 Port 162 Trap Level 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 Version v2c Object Snmp snmp Using the SL Console SL500 libraries only F 2 StorageTek Tape Analytics Installation and Configuration Guide SNMP vec Configuration Tasks h 9 Be ON 6 Use the SL Console to log in to the library From the Tools menu select System Detail In the navigation tree select Library Select the SNMP tab and then the Add Trap Recipients tab Complete the screen as follows a Host IP address of the STA server a TrapLevel Comma separated list of trap levels the library should send to STA 1 2 3 4 11 13 14 21
184. ion Guide STA Graphical Installer Screens Note These are external communication ports Your network administrator may need to configure firewalls and routers to open communication between the STA server and the client accessing the WebLogic Administration console Note Make a secure record of these port numbers they cannot be changed once STA is installed To protect your site security these numbers are purposely not preconfigured nor hard coded Screen Fields Enter HTTP Port Enter the HTTP port number for unsecure access to the WebLogic Administrator console login Typically this port number is 7019 Port numbers must be unique and available Enter HTTPS Port Enter the HTTPS port number for secure access to the WebLogic Administrator console login Typically this port number is 7020 Port numbers must be unique and available Screen specific Buttons None STA Graphical Installer and Deinstaller Screen Reference A 27 STA Graphical Installer Screens STA Engine StorageTek Tape Analytics Installation 2 1 0 STA Engine va ume Enter HTTP and HTTPS port numbers for the staEngine managed server These Installation Location ports are for internal STA server communication only Prerequisite Checks Enter Root Password Set up DB Directories Set up Admin Accounts Set up Database Accounts Enter Communication Ports WebLogic Admin Console STA Engine 3 3 4 4 HK
185. ion and deployment begins and the screen displays the status of each task Caution Do not close this window or otherwise interrupt the configuration while it is in progress as this may leave incomplete installation components on the server During this process the WebLogic server STA managed servers and the STA application are configured and started This may take 30 to 60 minutes to complete You can display expanded detail for any completed or in progress task In the Message pane click the Expand icon next to the task for which you want to display detail Click the Collapse icon to hide the detail again Figure A 6 is an example showing expanded detail for successful and unsuccessful tasks If a task fails the STA installer quits rolls back the installation and returns the server to its original state You can view the installation log to troubleshoot the issue See STA Installation and Deinstallation Logs on page 3 5 for details STA Graphical Installer and Deinstaller Screen Reference A 35 STA Graphical Installer Screens Figure A 6 Sample Configuration Progress Detail StorageTek Tape Analytics Installation 2 1 0 Configuration Progress Configuration Log Location tmp Orainstall2014 07 23_10 S2 33AM install2014 07 23_10 52 33AM up Database unt CUNUNI SIA Compuriens y Installing WebLogic log Config Action Installing WebLogic started Config Action Installing WebLogic ended s
186. ions a Review Related Documentation on page 2 2 Review STA File System Layout on page 2 2 a Download the Linux Installer Media Pack on page 2 4 Review Related Documentation Due to the wide variety of network configuration requirements and options refer to the following documents for help with installing and configuring the hardware software and network IPv4 and IPv6 network configuration are discussed in detail in these documents a Oracle Linux Installation Guides http docs oracle com en operating systems a RedHat Linux Documentation https access redhat com home Review STA File System Layout Table 2 2 describes the recommended file system layout for the STA server You configure the layout during Linux installation 2 2 StorageTek Tape Analytics Installation and Configuration Guide Preparation Tasks Table 2 2 Recommended File System Layout The following locations are user defined meaning you can configure the layout to meet your site requirements Oracle storage home The STA installer will prompt you for this location There is no default See Oracle storage home location on page 3 2 for details STA database The STA installer will prompt you for this location The default is dbdata a STA database local backup tThe STA installer will prompt you for this location The default is dbbackup STA and MySQL logs The default is var log tbi If you want to use a different locati
187. irectory and OpenLDAP Authentication Providers 1 If you have not done so already access the active security realm and lock it for editing See Edit the WebLogic Server Active Security Realm on page E 5 for instructions 2 Inthe Settings for myrealm control bar select the Providers tab Home Log Out Preferences E Record Help Q Welcome weblogic Home gt Summary of Securty Asaims gt myreailm Settings for myrcalm Configuration Users and Groups Roles and Pokies ee etg pm General ROGMSSeasity Store User Lockout Performance Cic the Lock amp Editbutton in the Change Center to modify the settings on this page C a The Authentication secondary tab is selected by default Settings for myrealm Configuraton Users and Groups Roles and Pobdes Credential Mappings Providers Migration Authentication Password Validation Authoriza on Adjudication Role Mapping Auditing Credential Mapping Certification Path Keystores In the Authentication Providers table select the active link for the provider you want to configure 3 Settings for myrealm Configuraton Users andGroups RolesandPobdes CredentalMappings Providers Migration Authentication Password Validation Authorizaton Adjudikation Role Mapping Auditing Credential Mapping Certification Path Keystores An Authentication provider allows WebLogic Server to establish trust by validating a user You must have one Authentication provider in a security realm and you can confi
188. is created during STA installation and all users added through the STA installer WebLogic Administration console and STA user interface are assigned to this group automatically For external authentication providers you must create this group in the provider and assign the appropriate users to it See Prepare the External Authentication Provider for STA Authentication on page E 5 for instructions Default STA User Role STA users from external authentication providers are assigned the STA Viewer role by default If a user requires a different role Operator or Administrator you must modify it manually through the STA user interface See theSTA User s Guide for details about STA user roles Configuring the Authentication Process for Multiple Providers When configuring multiple authentication providers you can use the following options to control how WebLogic Server uses the providers in the authentication process Authentication Provider Order When a user attempts to log in to STA WebLogic Server calls authentication providers in the order they are listed in the Authentication Providers table By default the providers are listed in the order they were added to the active security realm but you can change their order to better meet the needs of your site For example if an external authentication provider includes many STA users you may want to put that provider at the top of the list so it is called first See Task 4 Ensure Pro
189. is domain Lock amp Ede W Al changes have been activated How Settings for myrealm M1 Pf iioa 7 Verify that you can use a user account from the external authentication provider to log in to STA and display the Dashboard Login Username StaUser1 Password eeeeeeee Unauthorized use of prohibited and may lead to disciplinary action up to and induding termination and or criminal prosecution E 22 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring IBM RACF Authentication Providers Tape Analytics Preferences Help rouser 10 weve roger oO Dashboard Tempter stadeeut B 8 a Format ColumnCount 3 RowHeghtt 2034 Q Media Heath Ef F X orivetteath Q A FXR Librarystaus A F X 8 Ifa user from an external authentication provider requires STA Operator or Administrator privileges use the STA user interface to change their role See the STA User s Guide for instructions See Default STA User Role on page E 3 for additional information Tasks for Configuring IBM RACF Authentication Providers Use the following procedures to configure IBM RACF authentication providers You must complete the procedures in the order listed To configure OpenLDAP and Microsoft Active Directory authentication providers see Tasks for Configuring Active Directory and OpenLDAP Authentication Providers on page E 4 a Task 1 Review IBM RACF Mainframe Minimum Requirements
190. k 5 Apply All Configuration Changes on page E 19 for instructions Task 1 Add an External Authentication Provider Use this procedure to add an external authentication provider to the WebLogic Server active security realm 1 If you have not done so already access the active security realm and lock it from other users See Edit the WebLogic Server Active Security Realm on page E 5 for instructions 2 Inthe Settings for myrealm control bar select the Providers tab E 8 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Home Log Out Preferences E Record Help a Welcome weblogic mmary of Securty Realms gt myreaim Settings for myrcalm Configuration Users and Groups Roles and Pokies m e y cuma RDSMS Security Store User Lockout Performance Cick the Lock amp Edit button in the Change Center to modify the settings on this page The Authentication secondary tab is selected by default Settings for myrealm Configuraton UsersandGroups RolesandPolides Credential Mappings Providers Migration Authentication Password Validation Authorizaton Adjudication Role Mapping Auditing Credential Mapping Certification Path Keystores 3 Inthe Authentication Providers table click New gt Customize this table Authentication Providers ete Reorder Name Description Defaulthuthenbeator WebLogic Authenbeation Provider D
191. ked required and you can change the port numbers as necessary for your site RESPONSEFILE_LOC m KEYFILE_LOC a All PASSWORD variables 3 Save the file with a name and location of your choice 4 Change to the directory where the response file build utility has been downloaded The name of the utility is silentInstallUtility_versionjar For example cd Installers 5 Run the response file build utility java jar silentInstallUtility_2 1 0 64 124 jar response file Where response_file is the absolute path for the response file you have created 6 Respond to each prompt with the appropriate information The password values you enter are not displayed on the screen See User Accounts for Managing STA on page 3 3 for password requirements Example B 3 is a sample response file build utility run Example B 3 Sample Installer Response File Build Utility Run java jar silentInstallUtility_2 1 0 64 124 jar Installers SilentInstall rsp Oracle StorageTek Tape Analytics Silent Installation Utility This utility is used to assist users with the password fields in the Silent Installation response file The silent installation process requireds the password fields in the response file requires the password fields to be encrypted The utility will ask the users for the required passwords and encrypt these values then update the values into the supplied response file Please enter the location to save the key file Installers
192. ken to the screen with the selected template applied 5 Click Save Template in the Templates Toolbar The Save Template dialog box appears 6 Inthe Template Name field assign a new name not prefixed STA Your entry must be unique 7 Click Save The template is saved Record Current Custom Template Settings optional This section applies only if you have custom templates The upgrade preserves custom templates but after the upgrade all custom templates are owned by STA with public visibility Use this procedure to record the current ownership and visibility settings for all custom templates so you can restore them after the upgrade if necessary You can skip this procedure if template ownership and visibility are not critical to your implementation 1 Log in to STA with an administrator username 2 From the Setup amp Administration tab select Templates Management 3 Select the Filter icon and filter the screen to show only templates not owned by STA this will display custom templates only T Filter Data Da Match ANY of the folowing Fiter Matching mania Match ALL of the following barney w isnt STA x 4 Record the current Owner and Public Visibility settings for each custom template If you have many templates you may want to take a screen shot Record Executive Report Policy Settings optional This section applies only if you have privately owned Executive Report policies The upgrade preserves all E
193. lation The predefined username is root and it cannot be changed Caution The password for this account is not retrievable STA Database Application User A user defined MySQL username for example stadb that STA uses to connect to the database It is required to create update delete and read privileges on data tables STA Database Reports User A user defined MySQL username for example starpt that non STA and third party applications may use to connect to the database It has read only access to certain database tables STA Database Administrator User A user defined MySQL username for example stadba that STA administration and monitoring utilities use to connect to the database primarily to configure and run scheduled backups It has all DBA privileges except the grant option on all database tables Ports Used by STA STA uses the following ports to retrieve and receive data These are dedicated ports and they must remain available to STA The STA installer will verify that the ports are not already in use on the network Caution Once these ports have been configured during STA installation they cannot be changed without deinstalling and reinstalling STA Unconfigurable External Ports The ports described in Table 3 1 are external ports used for communication between the STA server and other network entities The port values are fixed and cannot be changed during STA installation 3 4 Stor
194. le select the active link for the provider you want to update Settings for myrealm Configuraton Users andGroups Roles and Pobdes CredentalMappings Providers Migration Authentication Password Vakdation Authorizaton Adjudication Role Mapping Auditing Credential Mapping Certification Path Keystores An Authendcaton provider allows WebLogic Server to establish trust by validating a user You must have one Authenticaton provider in a security teaim and you can configure multiple Authentication providers in a security resim Different types of Authentication providers are designed to access Gfferent data stores such as LDAP servers or DBMS You can also configure a Realn Adapter Authentication provider that allows you to work with users and groups from previous releases of WebLogic Server Customize this table New Delete Reorder Showing 1 to of3 Previous Next WebLoge Authenteabon Provider p t WebLogic Identity Assertion provider 10 Provider that performs LDAP authentication 10 Showing 1 to 3of3 Previous Next The Configuration tab and Common secondary tab are selected by default 4 Inthe Control Flag menu select Sufficient E 16 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Settings for My AD Server Configuration Performance Common Provider Specific Save This page displays basic inf
195. lected Group Base DN ou groups o staOpen dc mycompany dc com All Groups Filter Group From Name Filter amp cn g objectclass groupOfUniqueNames Group Search Scope subtree Group Membership Searching unlimited Max Group Membership Search Level 0 Configuring External Authentication Providers for STA E 13 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Ignore Duplicate Membership not selected Static Group Name Attribute cn Static Group Object Class groupOfUniqueNames Static Member URL Attribute uniquemember Static Group DNs from Member DN Filter amp uniqueMember M objectclass groupOfUniqueNames Dynamic Group Name Attribute Dynamic Group Object Class Dynamic Member URL Attribute User Dynamic Group DN Attribute Connection Pool Size 6 Connect Timeout 60 Connection Retry Limit 1 Parallel Connect Delay 0 Results Time Limit 0 Keep Alive Enabled not selected Follow Referrals selected Bind Anonymously On Referrals not selected Propagate Cause For Login Exception selected Cache Enabled selected Cache Size 32 Cache TTL 60 GUID Attribute entryuuid Example E 2 Sample Provider specific Values for an Active Directory Provider Host 10 123 456 789 Port 389 Principle CN StaLdapUser OU Users O STA DC oracle DC com Credential LDAP SAM password Confirm credential LDAP SAM password gt SSL Enable not selected User Base DN OU Users O STA DC mycompan
196. ler sta_install_version_linux64 bin silent responseFile response_file Where version is the version of the STA installer you downloaded response_file is the absolute path of the previously created response file For example sta_install_2 1 0 64 124 linux64 bin silent responseFile Installers SilentInstall rsp Before using this mode you must also download the silentInstallUtility jar file and create a response file specifying the installation options See Appendix B STA Silent mode Installer and Deinstaller for instructions Verify Successful Installation Use this procedure to verify that STA is running 1 Use the following steps to ensure that the STA bin directory is included in the PATH variable for the system root user a Open a terminal session on the current STA server and log in as the system root user b Use a text editor to open the user profile For example 3 12 StorageTek Tape Analytics Installation and Configuration Guide STA Installation Tasks vi root bash_profile c Add the STA bin directory to the PATH definition For example add the following line to the file PATH PATH Oracle_storage_home StorageTek_Tape_Analytics common bin Where Oracle_storage_home is the Oracle storage home location specified during STA installation d Save and exit the file e Log out and log back in as the system root user f Confirm that the PATH variable has been updated cor
197. ler B 11 STA Installer Command Options i install Use graphical mode This is the default J Djava io tmpdir working_directory Unpack the STA installer to the specified working directory instead of tmp working_ directory must be an absolute path and the directory must allow the execution of binaries paramFile initialization_file Use the specified initialization file instead of one located in STA_home oui oraparam ini initialization_file must be an absolute path The STA installer uses the file you specify for all operations including the prerequisite checks The default location is in the STA_home ui directory B 12 StorageTek Tape Analytics Installation and Configuration Guide C Installation and Upgrade Worksheets The worksheets in this appendix are planning tools to help you organize the activities and information you must gather to perform an STA installation This appendix includes the following sections Upgrade Preparation Worksheet Installation and Upgrade Worksheets Post installation Configuration Worksheet Upgrade Preparation Worksheet Table C lis 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 Upgrade Preparation Tasks on page 8 6 for complete details about these activities Table C 1 Upgrade Prepara
198. lis a lithe ettiithe dete hg A 29 STAN EE E A A AE ENE Bi A ele eset Sate tees del eect ae es i eeteh hehe Cote Me At eat A 30 Diagnostic Agent perirono A 31 Installation Summary desiitiniiion kietai kii et aa ea e i eaii A 32 Installation Progress 2 secsscots ces stetiecetss naaa a iapa aaan e as aaaea ia eire i A 33 Configuration Progress oaio a n A EE EER ARE EE RE S E seetevecouuctacees A 35 Installation Com plete scesi tccawavies E loweervet bonds E EEEE E E RANES A 37 STA Graphical Deinstaller Screens cccceccccceseseses cs cseesescscscsesesescsesesesesesesesesesescseseseseseecsensa A 37 Weleomite comaa a tele eects a a a cee bte ecto BU te Sit eet A 38 Enter Root Password tc220 cigiabiinucee diet a ne a a ar a A 39 Deinstallation Summary vei scgesece cashes eased cvevele es a a Vea vtvesees a Eei oes ats A 40 Deinstallation Processes iatan n e a ean E a a e e a e EEES A 41 Deinstallation Completeisssirisii ern tiv ele ieee E E E E ARRAN A 43 B STA Silent mode Installer and Deinstaller Using the STA Silent mode Installer and Deinstaller 0 0 0 0 eee cece ee ceneeeeeeeneneneeeeeees B 1 Silent mode RequireMents cccceccssesssssssesesssessesesesesesesesescscsesesesescsessseseecscsessseseecessssssnessseneses B 1 Files and Utilities Used With Silent Mode 0 ccccecccscecsescesesseesceeeceneeseeeecaceaeeseeaecaeeeeeaeeaeeeseeeeeens B 2 STA Silent mode Installer Tasks ennan a an a E aT eee B 4 Create the Oracle
199. list NA S Subject Email subject Entry that appears in the Subject field of the standard daily report email up to 128 characters Use quotes if it contains spaces A timestamp in yyyy mm dd hh mm ss form will be appended to your entry when the email is sent STA Resource Monitor Report 0 outfile Output data file Absolute path of the comma separated CSV output data file 7 6 StorageTek Tape Analytics Installation and Configuration Guide ISTA_ logs db staresmon csv For example Nar log tbi db staresmon csv STA Services Configuration Tasks Configure the STA Resource Monitor Use this procedure to configure the STA Resource Monitor service Your configuration settings take effect as soon as the service wakes from its current sleep interval and processes new settings or you manually restart the STA Services daemon Restart the STA Services Daemon optional on page 7 2 1 2 On the STA server log in as the system root user Display the current STA Resource Monitor settings using the staresmonadm Q command This example shows the service is not yet configured and is therefore not performing scans staresmonadm Q Contacting daemon connected Querying Preferences Current STA Resource Monitor Service Settings Configured no Send Reports T 00 00 Sleep Interval i 300 sec Alert Nagging n off DB Username U DB Password P DB T
200. ll engine modules prereq host nstallation Me Actual Result Package xauth is installed Check complete The overall result of this checkis Passed n nstallation Cd 2014 09 18T13 19 05 200 06 00 fas NOTIFICATION oracie as install engine modules prereq host t 1 2024 09 28T13 19 05 201 06 00 as NOTIFICATION oracie as install engine modules presentation 2014 09 18T13 19 05 267 06 00 as NOTIFICATION oracle as install engine host tbivb03 nwadadi 00 2014 09 18T13 19 0S 638 06 as NOTIFICATION oracte as install engine modules prereq host S X gt z Close View Log ax E PChecking existing STA instance s a PChecking MySQL not installed E PChecking Operating System Compatibility E PChecking tmp available space 1G Bernt r Help lt Back Next gt Cancel You can also view the log from the Linux command line While the installer is running logs are kept in a subdirectory within tmp See STA Installation and Deinstallation Logs on page 3 5 for details STA Graphical Installer and Deinstaller Screen Reference A 13 STA Graphical Installer Screens Enter Root Password StorageTek Tape Analytics Installation 2 1 0 a 7 ant N Enter Root Password va Welcome y H n The STA installer requires system root privileges to perform certain background y installation Location tasks Specify the existing system root account password Prerequisite Checks g
201. ly 1 2 3 4 5 From the Tools menu select System Detail In the navigation tree select Library Select the SNMP tab then select the Port Control tab Complete the Port Control section as follows Port Select Public 1B Command Select Enable Click Apply Using the SL150 user interface 1 2 3 In the navigation tree select SNMP If SNMP shows as disabled select Enable SNMP In the confirmation window click OK Configuring SNMP on the Libraries 5 5 Library SNMP Configuration Tasks Ensure an SNMP v2c User An SNMP v2c user is required for the initial handshake between the library and the STA server See SNMP v2c Community String on page 5 2 for complete requirements Using the library CLI all libraries except SL150 1 Establish a CLI session on the library 2 Add the SNMP v2c user gt snmp addUser version v2c community community_name Where community_name is the SNMP v2c user community string For example SL3000 gt snmp addUser version v2c community stasnmp 3 List the SNMP users to verify that the SNMP v2c user has been added correctly gt snmp listUsers Attributes Community stasnmp Index 1 Version v2c Object Snmp snmp Using the SL Console SL500 only 1 Use the SL Console to log in to the library 2 From the Tools menu select System Detail 3 In the navigation tree select Library 4 Select the SNMP tab and then the Add Users tab 5 Complete the Add Users sc
202. ly one can be set as the default active resin This Security Realms page ists each security realm that has been configured in this WebLogic Server domain Click the name of the realm to explore and configure that realm P Customize this table Realms Filtered More Columns Exist Cik the Lock amp Fdit button in the Change Center to activate all the buttons on this page wen Delete Showing ito lof 1 Previous Next jj Default Realm 4 true Showing 1 to lof 1 Previous Next 5 The Settings for myrealm screen appears Select the Users and Groups tab Upgrading to STA 2 1 x 8 11 Upgrade Preparation Tasks Settings for myrealm Configuration Users and Groups Roles and Polkies Credential Mappings Providers Migration is General DOME Seo SUF Lockout Performance Cik the Lock amp Editbutton in the Change Center to modify the settings on this page Use this page to configure the general behavior of this security realm The Users table lists the available usernames Settings for myrealm Configuration Users and Groups RolesandPolides Credential Mappings Providers Migration Users Groups This page dsplays informaton about each user that has been configured in this security realm P Customize this table Users Filtered More Columns Exist New eiste Showing 1to 2of2 Previous Next Provider STA administrator DefauitAuthentcator This user is the default administrato
203. mp Administration tab select SNMP Connections c Verify the following values in the Monitored Libraries table Recent SNMP Trap Communication Status GOOD 8 8 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Preparation Tasks 2 Last Connection Status SUCCESS Use the following steps to verify that STA is processing exchanges across all libraries a From the Tape System Activity tab select Exchanges Overview b Select the Filter icon and filter for Exchange End No Days Less Than 1 c Inthe Table Toolbar select View then select Sort then select Advanced Sort by Drive Library Name Drive Serial Number d Verify that all libraries have exchange activity Save Existing Logs optional Existing application and service logs are not retained after the upgrade because you must deinstall the current version of STA or install a new version of Linux before installing STA 2 1 x Use this procedure to save any logs you want to keep 1 Locate any installation and database logs you want to retain and move them to a safe place Logs that may be of interest are located in the STA logs location you have defined for your installation See Review STA File System Layout on page 2 2 for details Use the following steps to perform a service log snapshot on the current STA installation This step is optional but recommended as Oracle Support can use the logs to troubleshoot any issues that ma
204. mplex IDs are set correctly when SDP is connected See Ensure the Correct Library Complex ID SL8500 only on page 4 9 for instructions Drive Clean Warning SL3000 and SL8500 only The drive clean warning flag indicates whether a drive warning should be issued whenever a drive needs cleaning This flag is set at the library level so the same setting applies to all drives in a library a When the flag is set to on each drive shows a warning health status whenever it needs cleaning This also causes the top level health status of the library to be degraded in the STA monitor a When the flag is set to off each drive s status is not affected by the need for cleaning therefore the library top level status in STA is not degraded If you have a large number of drives in the library you may want to set this flag to off so that the library top level condition is not degraded whenever a drive needs cleaning See Set the Drive Clean Warning optional SL3000 and SL8500 only on page 4 10 for instructions Volume Label Format SL500 and SL150 only Volume serial numbers volsers in SNMP data must be formatted properly for STA to process library exchange data correctly The media volser includes a two character suffix that indicates the media type For example if a cartridge volser is ABC123L4 L4 indicates the media type is LTO4 For proper STA reporting the volser suffix must be excluded To ensure proper formattin
205. n Start all STA services STA start all This step is optional Delete the STA_FRESH_INSTALL_BACKUP sq file to free up disk space on the STA database backup volume Task 9 Configure the New STA Version Use these procedures to configure the libraries and STA 2 1 x so STA can begin monitoring library activity Update the STA Trap Recipient on the Libraries Two new trap levels 13 Test Trap and 14 Health Trap were introduced in STA 2 0 Perform the following steps on each monitored library to ensure these trap levels are included in the STA trap recipient definition 1 Depending on your upgrade path proceed as follows Ifyou are using the single server method to upgrade from STA 2 0 x or STA 2 1 x proceed to Configure SNMP Settings in STA on page 8 25 Ifyou are using the single server method to upgrade from STA 1 0 x go to Step 2 to add the new trap levels to the existing STA trap recipient on each monitored library Ifyou are using the two server upgrade method go to Step 3 to add a new STA trap recipient to each monitored library If you are using the single server method to upgrade from STA 1 0 x use the appropriate steps for the library model to add the new trap levels to the STA trap recipient For all library models except SL150 to modify a trap recipient you must delete the existing definition and then add a new one All libraries except SL150 a Log in to the library CLI b Display
206. n and Res Helpful Tools a Configure appicatbons a Configure Gridlink for F Recent Task Status 8 In the Keystores section click Change Demo Identity and Demo Trust 9 Inthe Keystores menu select Custom Identity and Java Standard Trust Settings for staUi Configuration Protocols Logging Debug Monitoring Control Deployments Services Seaxity Notes General Cluster Services Keystores SSL Federaton Services Deployment Migration Tuning Overload Health Monitoring Server Stat Web Services Save Cancel Keystores ensure the secure storage and management of private keys and trusted certificate authorites CAs This page lets you view and define various keystore configurations These settings help you to manage the security of message transmissions Keystores Custom Identity and Java Standard Trust Which configuration rules should be used for Airai the e servers Toty trust keystores ss Custom Identity and Command Line Trust eS ee ae 10 Click Save 11 Complete the Keystores screen as follows Custom Identity Keystore Path and file of the private key file Custom Identity Keystore Type Keystore type If configuring for RACF authentication enter PKCS12 a Custom Identity Keystore Passphrase Password supplied by the MVS system administrator a Java Standard Trust Keystore Passphrase New password for the Java Standard Trust Keystore file Caution If you forget these passwords
207. n page 5 6 Yes Yes Yes Yes Create an SNMP v3 User on page 5 7 Yes Yes Yes Yes Retrieve the Library SNMP Engine ID all libraries except SL150 on Yes Yes Yes page 5 8 Create the STA SNMP v3 Trap Recipient on page 5 8 Yes Yes Yes Yes Note These procedures assume you are using the recommended SNMP v3 protocol for communication between STA and the libraries See Understanding Library SNMP Configuration for STA on page 5 1 for details Note For SL500 SL3000 and SL8500 libraries some tasks allow you to choose which interface to use CLI or SL Console For SL150 libraries you must always use the browser based user interface Configuring SNMP on the Libraries 5 3 Library SNMP Configuration Tasks Retrieve the Library IP Address Use this procedure to retrieve and record the library IP address which you will use to configure the connection with the library For SL3000 and SL8500 libraries choose the method to support either Redundant Electronics Dual TCP IP or neither See Dual TCP IP and Redundant Electronics SL3000 and SL8500 only on page 4 2 for details This procedure is performed using the SL Console or the SL150 browser based interface SL500 IP Address 1 From the Tools menu select System Detail 2 In the navigation tree select Library 3 Select the Properties tab then select the General tab The library IP address is listed under the Library Interface TCP IP
208. nd it is automatically provided when the initial connection between STA and the library is made It is blank for new connections Automated Daily Data Refresh Specify the time of day you want STA to collect the latest configuration data from the library The data is collected automatically every 24 hours at this time You should choose a time when there is typically lighter library usage The default is 00 00 12 00 am Use 24 hour time format Caution If you leave this field blank scheduled automatic library data collections are disabled This will cause your STA library configuration data to become out of sync with the library Library Time Zone Select the library s local time zone 6 6 StorageTek Tape Analytics Installation and Configuration Guide STA Configuration Tasks Define Library Connection Details D Lbrary Complex 8500_1 library Name ibrary1 Livary Primary IP Address 10 890 123 456 Library Secondary IP Address STA IP Address 10 80 175 36 Library Engine IL 0x8000 1 8304363030303 13030323237 Automated Dady Data Refres 0 0 amp Livary Time Zone UTC X 4 Click Save The configuration record is updated and a message box is displayed indicating you should perform a library connection test to establish or re establish the SNMP communication handshake with the libraries Library Connection Tests a Connection information has been changed There are now untested STA4ibrary connections Pl
209. nd local access to the STA application due to server performance degradation 2 12 StorageTek Tape Analytics Installation and Configuration Guide 3 Installing STA This chapter assumes you are performing a new installation of STA on this server Ifyou are upgrading STA from a previous version see Chapter 8 Upgrading to STA 2 1 x Oracle recommends you install or upgrade to the latest version of STA a If you need to reinstall STA or repair a current installation see Chapter 9 Deinstalling and Restoring STA Note Oracle provides support only if STA is installed on a dedicated server called the STA server This chapter includes the following topics a Users Groups and Locations Used by the STA Installer a Username and Password Requirements a Accounts and Ports Configured During STA Installation a STA Installation and Deinstallation Logs a STA Installer Modes STA Installation Tasks Appendix C includes worksheets you can use to organize your installation activities and record your settings Users Groups and Locations Used by the STA Installer This section describes key concepts and terms used in the STA installation process Oracle install group 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 the STA installation you must log in as a user that is a member of this gr
210. nding on the number of copies to be retained Backup server storage should be mirrored or striped 1 On the backup server log in as the system root user 2 Create a new group for the STA Backup user For example groupadd g 54321 stabckgr In this example the group ID is stabckgr and the g option is used to specify a numerical GID 3 Create the STA Backup user For example adduser stabck c STA database backup user m d home stabck g stabckgr s bin bash u 98765 In this example the user ID is stabck and the following options are used c Comment m Create a home directory for the user d Absolute path of the home directory a g Assign the user to the specified group Configuring STA Services 7 3 STA Services Configuration Tasks a S Assign the specified login shell to the user a u Assign the specified numerical UID to the user 4 Assign a password to the STA Backup user For example passwd stabck Changing password for user stabck New UNIX password bckpwd1 Retype new UNIX password bckpwd1 passwd all authentication tokens updated successfully 5 Create the directory where the STA backups will be copied For example cd home stabck pwd home stabck mkdir p STAbackups 1s STAbackups In this example the STAbackups directory is created in the STA Backup user s home directory and the p option is used to make parent directories as needed 6
211. nfigure firewalls and routers to open communication between the STA server and the clients accessing the STA user interface Username and Password Requirements Username and password requirements for STA and MySQL have changed for STA 2 1 x You may need to coordinate these requirements with any internal requirements at your site Username requirements are as follows Must be 1 16 characters in length a All usernames must be unique Password requirements are as follows Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters et C Set Fe ye Upgrade Preparation Tasks Perform the following tasks before starting the STA upgrade Most of these tasks are optional and Table 8 1 provides guidelines on when to use each one 8 6 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Preparation Tasks Table 8 1 Guidelines for When to Perform Upgrade Preparation Tasks Task When to Perform It Verify Your Site is Ready for the Upgrade on page 8 8 Save Existing Logs optional on page 8 9 Record Current STA User and Configuration Settings optional on page 8 9 Rename Custom Templates With STA Prefix optional on page 8 13 Record Current Custom Template Settings optional on page 8 14 Record Executive Report Policy Settings optional on page 8 14
212. nge STA stop all STA start all F 4 StorageTek Tape Analytics Installation and Configuration Guide C changing SNMP client attributes 6 3 client attributes 6 3 complex IDs 4 3 D deinstalling 9 1 F firewall port configuration 3 4 L LDAP configuration E 8 library configuration 5 1 complex IDs 4 3 Dual TCP IP 4 2 optional configuration script 4 6 Redundant Electronics 4 2 SL500 fast load 4 5 SNMP configuration 5 1 SNMP worksheet C 5 tasks 4 6 user interfaces 4 5 volume label formatting 4 4 Linux installation overview 2 1 post installation tasks 2 8 preparation tasks 2 2 tasks 2 5 Linux PATH setting 7 2 R RACF configuration E 23 reinstalling 9 1 9 3 S service requests 1 5 SNMP confirm connectivity 6 2 management add trap recipient 8 25 Index change client attributes 6 3 SSP configuration E 1 configure RACF E 23 configure WebLogic Open LDAP E 8 STA download 3 11 STA configuration certificates D 1 establish initial connection D 1 reconfigure WebLogic D 2 replace Oracle certificate D 9 services 7 1 resource monitor 7 1 restart services daemon 7 2 update Linux PATH setting 7 2 verify library connectivity 7 2 SNMP 6 1 STA database backup service 7 1 tasks 6 1 STA installation console installer 3 12 general prerequisites 3 9 graphical installer 3 12 overview 3 1 steps to install 3 12 STA server port configuration
213. nie tipna a lin eee a a ew a ia ee 2 8 Disable SEW x srini geane aa iaa aa a i aa a a Sa Relies ead a a aa 2 8 Disable the Linu Firewall pnsan ana ea hie thas a a a aa igh a a 2 8 3 Disable Access Controls imene SR ola cs Lect RTE eA Se aoa lh Sa A EEGs EN INR Ee cdo 2 9 Set Up the Network Proxy e crecn Rion Sih Sereda cieelenain a invited a 2 9 Ensure Proper Setup of yum optional 0 0 0 cece cceeeececeseeseececeseesssnecesesseeseseesenesesesesanens 2 9 Install Requir d Linux Packages cocccsstsccctesccstosscubsetscvvcsasessoceseesssssveeedisvessdescesuerstvesesresesoeseststate 2 10 Ensure Prop r Settip of SSH ssi sutisee hasten nhi en en iak 2 11 Ensure Proper DNS Settinngs c cccccccesssescsseesscseseeecsesesesesseececseseeeseesescssnecesscneseseesssesenseseessenestees 2 11 Disable Name Services 5 285s ines ihe ie ee i RI ele 2 12 Ensure Local Browser Functionality optional ccccessesssesssesesescsessesesescseseseecscsessseseeesees 2 12 Installing STA Users Groups and Locations Used by the STA Installer oo cece ceseseeceeerenseeseeeneeesenens 3 1 Username and Password Requirements cccccccssesesscsesssesesescsesesesesesesesesesescsesesesesescseseseseseees 3 3 Accounts and Ports Configured During STA Installation 0 0 ccc ccc seceseneseseseeeeneseee 3 3 User Accounts for Managing ST Apiece ie inene ea a ARELA RE AeA RESSE IRE AEAEE REEE 3 3 Ports Used By STA isinisi irti aaa E RAR REEE EN R
214. nitored SL8500 complex See Ensure the Correct Library Complex ID SL8500 only on page 4 9 a ForSL150 and SL500 libraries ensure the volume label format is set correctly See Set the SL500 Volume Label Format SL500 only on page 4 10 Quiesce the libraries before changing library parameters It is recommended that you quiesce all activity to a library before changing its parameters In addition tape applications and hosts may require configuration changes after library parameters have been changed See Set the SL500 Volume Label Format SL500 only on page 4 10 Duplicate volsers Because all history for a particular piece of media is tied to its volume serial number volser you should avoid duplicate volsers in your tape library environment Pre installation Planning 1 3 Best Practices for STA Deployment See Duplicate Volume Serial Numbers on page 4 5 SNMP Connections With the Libraries SNMP version For communication between STA and the monitored libraries Oracle recommends the more secure SNMP v3 protocol rather than SNMP v2c The authentication encryption and message integrity features in SNMP v3 provide a secure mechanism for sending library data SNMP v3 is also required for the STA media validation feature See Understanding Library SNMP Configuration for STA on page 5 1 SNMP v3 user Oracle recommends creating a new unique SNMP v3 user on the libraries for STA communications See Unique SNMP
215. nstalled with no data see Recover a Failed Database Upgrade optional for details on the recovery process 1 2 Open a terminal session on the STA server and log in as the system root user If you have not done so already stop all STA services STA stop all Start the MySQL service STA start mysql Create the database backup file Enter the database root user password when prompted mysqldump uroot p opt add drop database comments complete insert dump date events flush logs routines single transaction triggers databases stadb gt dumpfile_path dumpfile_name sql Upgrading to STA 2 1 x 8 19 Upgrade Tasks Note The optional v parameter for verbose output is not recommended as a large number of messages are displayed in the terminal window and it can significantly slow down the command process for large databases In Example 8 4 the STA 2 1 x database is dumped to the dbdumpfiles folder on the STA server with filename STA_FRESH_INSTALL_BACKUP sq Example 8 4 New Database Dump mysqldump uroot p opt add drop database comments complete insert dump date events flush logs routines single transaction triggers databases stadb gt dbdumpfiles STA_FRESH_INSTALL_BACKUP sql Enter password mysql_root_password Retrieving view structure for table v_mdv_request_states Retrieving view structure for table version_info Disconnecting from
216. nt of network disruptions or failure on one subnet the library host connection automatically fails over to the other port Redundant Electronics protects against hardware failures on the library controller by providing two separate and fully functional library controller cards an active and a standby If the active controller experiences significant errors library control can be switched to the standby card with minimal disruption to library and host operations See the library User s Guide for complete details about these features Configuring the STA Connection to Support These Features Depending on which of these features are activated Dual TCP IP Redundant Electronics or both an SL3000 or SL8500 library can have one two or four IP addresses However STA is capable of maintaining uninterrupted connections with 4 2 StorageTek Tape Analytics Installation and Configuration Guide Library Features Affecting STA Data only up to two library IP addresses at a time Therefore on a given library you can configure STA to support either Dual TCP IP or Redundant Electronics but not both When you configure the STA connection to the library you must always specify a primary library IP address You can optionally specify a secondary IP address depending on the feature configuration of the library and which feature you want STA to support Note For libraries with both features Oracle recommends that you configure STA
217. nterface a STA User s Guide Use this guide for instructions on using all STA application features including the Dashboard templates filters alerts Executive Reports logical groups and STA media validation This guide also provides instructions for administering and managing STA usernames email addresses service logs and SNMP connections with the monitored libraries xi For STA Screen Basics Guide Use this guide for full details about the STA user interface It describes the screen navigation and layout and the use of graphs and tables STA Data Reference Guide Use this guide to look up definitions for all STA tape library system screens and data attributes installers and administrators of the STA server and application STA Release Notes Read this document before installing and using STA It contains important release information including known issues This document is included in the STA media pack download STA Requirements Guide Use this guide to learn about minimum and recommended requirements for using STA This guide includes the following requirements library drive server user interface STA media validation and IBM RACF access control STA Installation and Configuration Guide Use this guide to plan for installation of STA install the Linux operating system install the STA application and then configure STA to begin monitoring the libraries This guide also provides instructions for upgrading t
218. ntly installed RPM packages yum list installed The xorg x11 util entry should be included in the displayed list For example xorg x1ll utils x86_64 7 5 6 e16 2 Display the current display settings for the Oracle install user For example echo DISPLAY 20 0 3 Verify the display has the proper X11 configuration For example xdpyinfo display 0 0 Example A 1 is a sample of the first part of the command output showing a properly configured display Example A 1 Sample Properly Configured X11 Display xdpyinfo name of display 20 0 version number 11 0 vendor string The X Org Foundation vendor release number 11300000 X Org version 1 13 0 maximum request size 16777212 bytes motion buffer size 256 Example A 2 shows some examples of the command output from displays that are not configured correctly Example A 2 Sample Improperly Configured X11 Displays xdpyinfo xdpyinfo unable to open display 0 0 xdpyinfo PuTTY X11 proxy MIT MAGIC COOKIE 1 data did not matchxdpyinfo unable to open display 0 0 STA Graphical Installer Screens This section provides detailed reference for each screen of the STA graphical installer a Welcome on page A 6 a Installation Location on page A 8 STA Graphical Installer and Deinstaller Screen Reference A 3 STA Graphical Installer Screens Prerequisite Checks on page A 10 Enter Root Password on page A 14 Set Up DB Directories on page A
219. ntrol Flag Use this procedure to set the JAAS control flag to indicate how WebLogic Server will use each provider in the user authentication process See JAAS Control Flag on page E 3 for details Note You must perform this procedure for all authentication providers including the DefaultAuthenticator Do not perform this procedure for the DefaultidentityAsserter Configuring External Authentication Providers for STA E 15 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers 1 If you have not done so already access the active security realm and lock it for editing See Edit the WebLogic Server Active Security Realm on page E 5 for instructions 2 Inthe Settings for myrealm control bar select the Providers tab Home Log Out Preferences E Record Help a Welcome weblogic Home gt Summary of Securty Realms gt myreailm Settings for myreaim Configuration Users and Groups Roles and Poles m e pam General ROSMS Searity Store User Lockout Performance Cik the Lock amp Editbutton in the Change Center to modify the settings on this page Cua The Authentication secondary tab is selected by default Settings for myrealm Confguraton Users and Groups Roles and Pobdes Credential Mappings Providers Migration Authentication Password Validation Authorization Adjudication Role Mapping Auditing Credential Mapping Certification Path Keystores 3 Inthe Authentication Providers tab
220. ny previously released STA version a Support for Active Directory authentication providers a For optimal SNMP security Oracle recommends using the SNMP v3 protocol for communication between STA and the libraries Oracle also recommends not using the values public or private for the community string as these values are well known and present a security risk a For optimal SNMP security SNMP v2c is disabled by default on STA If necessary you can enable and configure SNMP v2c mode for STA a New Best Practices section for pre installation planning providing tips for optimizing the performance and value of the STA server database and application Described in the STA Quick Start Guide a No changes Described in the STA User s Guide a New Best Practices sections providing tips for login sessions templates alert policies Executive Reports logical groups STA media validation and investigating tape environment issues Described in the STA Screen Basics Guide a New Best Practices sections providing tips for using the screen layout and navigation graphs and tables Described in the STA Data Reference Guide Corrections to selected data attribute definitions Described in the STA Administration Guide a No changes xiii xiv 1 Pre installation Planning This chapter includes the following sections STA Deployment Process Overview Best Practices for STA Deployment Prepare Service Requests for the Librari
221. o a new version of STA STA Administration Guide Use this guide for information about STA server administration tasks such as STA services configuration database backup and restore and password administration for database accounts STA Security Guide Read this document for important STA security information including requirements recommendations and general security principles STA Licensing Information User Manual Read this document for information about use of third party technology distributed with the STA product Conventions The following text conventions are used in this document Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action or terms defined in text or the glossary italic Italic type indicates book titles emphasis or placeholder variables for which you supply particular values monospace Monospace type indicates commands within a paragraph URLs code xii in examples text that appears on the screen or text that you enter What s New This section summarizes new and enhanced features for StorageTek Tape Analytics 2 1 1 STA 2 1 1 June 2015 See the indicated manuals for details about the following new and enhanced features Described in the STA Requirements Guide a STA server sizing considerations for larger installations Described in the STA Installation and Configuration Guide a Process for upgrading to STA 2 1 1 from a
222. o the monitored libraries and perform necessary manual configuration tasks Task 9 8 4 StorageTek Tape Analytics Installation and Configuration Guide Environment Changes for STA 2 1 x Figure 8 2 Two server Upgrade Task Overview Task 3a Install New Linux oe SA a Task 4 Task 5 Task 1 Server 2 Install New STA Dump New STA Dump Old STA Database optional Database N PSA Server 2 Task 3b Deinstall Old STA ORACLE Loe Task 2 Task 7 Task 8 Task 9 Transfer Old Database Process 5 Load Old Upgrade Database Configure New STA atabase Environment Changes for STA 2 1 x Following is a summary of environment changes that you should take into account when planning the upgrade to STA 2 1 x Linux Version STA 2 1 x requires Linux 6 3 or higher see the STA Requirements Guide for details Depending on your current STA version you may need to install a new version of Linux as part of the STA upgrade process a Ifyou are upgrading from STA 1 0 x you must install Linux 6 3 or higher before installing STA 2 1 x Linux does not support an in place upgrade from Linux 5 x to Linux 6 x instead you must perform a new Linux 6 x installation on the STA server a Ifyou are upgrading from STA 2 0 x you are already running Linux 6 3 or higher however you must deinstall the current version of STA before installing STA 2 1 x You may also need to install or update the required Linux RPM packages
223. on 1 Start a supported Web browser on your computer and enter the HTTPS SSL version of the URL for the STA application https STA_host_name port_number STA Where a _ host_name is the hostname of the STA server port_numberis the STA port number you specified during installation The default HTTP port is 7021 the default HTTPS port is 7022 a STA must be uppercase For example https staserver example com 7022 STA The Connection is Untrusted screen appears Select I Understand the Risks and then click Add Exception Configuring Security Certificates D 1 Security Certificate Configuration Tasks The Add Security Exception screen appears Click View The Certificate Viewer screen appears The certificate is not shown as verified because it is not from a certificate authority To examine the certificate click the Details tab In the Certificate Fields panel select issuer Following is a sample display CN indicates the server name on which the certificate was generated CN staserver example com OU Tape Systems O Oracle America Inc L Redwood City ST California C USA Click Close to return to the Add Security Certificate screen Select Confirm Security Exception The certificate is added to the STA server and you can now use HTTPS with the certificate Reconfigure WebLogic to use a Different Security Certificate 1 2 Start a supported Web browser on your computer In the
224. on you must create a symbolic link from your desired location to var log tbi after STA has been installed See Relocate the STA Logs Directory optional on page 3 13 for instructions Oracle recommends creating all these file systems before installing STA otherwise STA will be installed in the root and var directories requiring additional space allocation to these directories While the STA installer creates directories as needed you have greater control of file system properties if you create the files systems in advance Default Mount File System Point Size Description and Recommendations root 32 GB If tmp is included in this file system a minimum of 4 GB of free space should minimum be maintained this space is required during STA installations and upgrades swap None 50 to 100 Used for swap space Defined as__ percent of memory RAM size Oracle storage Oracle 30 GB Location of the STA and Oracle Middleware WebLogic MySQL RDA home minimum application files 50 GB This location is user defined It should be a separate file system on a separate recommended volume Maintain a minimum of 4 GB free space for STA installations and upgrades Maintain an additional 5 GB free space for WebLogic log rotation STA automatically creates the following Oracle Middleware subdirectories Rotated WebLogic logs Oracle_storage_home Middleware user_projects domains TBl servers RDA last CLI snapshot
225. on Guide for command usage details STA stop all STA start all E 34 StorageTek Tape Analytics Installation and Configuration Guide F Configuring SNMP v2c Mode This appendix includes the following sections When to Use SNMP v2c Mode a SNMP v2c Mode Configuration Process a SNMP v2c Configuration Tasks When to Use SNMP v2c Mode For optimal SNMP security Oracle recommends using the SNMP v3 protocol for communication between STA and the libraries See Understanding Library SNMP Configuration for STA on page 5 1 for details The SNMP v2c protocol is less secure than SNMP v3 and by default is not enabled on STA However if SNMP v3 communication is not possible for instance SNMP v3 is not configured on a library that STA will be monitoring you can enable and configure SNMP v2c mode for STA The SNMP v3 configuration process is described in Chapter 5 Configuring SNMP on the Libraries and Chapter 6 Configuring Library Connections in STA This appendix describes the procedures that differ for SNMP v2c configuration SNMP v2c Mode Configuration Process The process for configuring the libraries and STA to use SNMP v2c for SNMP communications is as follows 1 In Chapter 5 follow all procedures shown in Table 5 1 Tasks to Configure Libraries for STA except Replace Create the STA SNMP v3 Trap Recipient with Create the STA SNMP v2c Trap Recipient on the Library on page F 2 After completing
226. on Location configure Remote Diagnostic Agent RDA Prerequisite Checks STA uses RDA to take snapshots of all logs related to the STA application and Enter Root Password database including OS installation and configuration information Set up DS Directories Set up Admin Accounts Set up Database Accounts Enter Communication Ports WebLogic Admin Console STA Engine STA Adapter STA UI Enter Domain Name jus example com 6 lt x 4 HK A 3 HK HK H 4 Configure RDA Help lt Back Next gt Cancel The STA installer uses your site s fully qualified domain name to configure Oracle s Remote Diagnostic Agent RDA STA uses RDA to take snapshots of all logs related to the STA application and database including operating system installation and configuration information See the STA User s Guide for additional information Screen Fields Enter Domain Name Enter your site s fully qualified domain name for example us example com Screen specific Buttons None STA Graphical Installer and Deinstaller Screen Reference A 31 STA Graphical Installer Screens Installation Summary StorageTek Tape Analytics Installation 2 1 0 Installation Summary A y Welcome gt Install StorageTek Tape Analytics y Installation Location Installation Details I STA Home Location Oracle StorageTek_Tape_ Analytics f Prerequisite Checks Log File tmp Orainstall2015 01 07_10 34 21AM install2015 01 07_10 34
227. ondary IP address 2A section SL3000 or SL8500 IP Addresses Neither Dual TCP IP Nor Redundant Electronics 5 4 StorageTek Tape Analytics Installation and Configuration Guide Library SNMP Configuration Tasks 4 From the Tools menu select System Detail In the navigation tree select Library Select the Properties tab then select the General tab The IP address information is displayed in the Host Interface TCP IP 2B section There is no IP address information in the 2A section Record the IP address as the primary library IP address SL150 IP Address 1 In the navigation tree select Configuration Select Settings then select Network The library IP address is displayed in the Network Port 1 Settings section The Network Port 2 Settings section is reserved for service use Note The Configure IPxx field value must be Static If it is not click the Configure button and then select Configure Network Settings to specify a static IP address Enable SNMP on the Library Use this procedure to enable SNMP on the library public port Using the library CLI 1 Depending on library model use one of the following commands a For SL3000 and SL8500 libraries enable SNMP on port 2B If the library includes the Dual TCP IP feature this command also enables SNMP on port 2A gt snmp enable port2b a For SL500 libraries enable SNMP on port 1B gt snmp enable portiB Using the SL Console SL500 on
228. onnection Failure Detail field You may need to extend the column width to see the entire value Note If the test fails because of a timeout repeat this procedure during a period of lower library activity Once the test completes you can compare the timestamps to verify that the library is providing current information 6 8 StorageTek Tape Analytics Installation and Configuration Guide STA Configuration Tasks Perform a Manual Data Collection Use this procedure to initiate a manual data collection for a library and get the latest library configuration data If this procedure is completed successfully STA begins monitoring the library and performing analytics on the data Although STA performs a data collection automatically every 24 hours at the scheduled time you must perform a manual data collection for each monitored library whenever you add or change SNMP configuration settings for the library or the STA client Data collections may take several minutes to an hour depending on library size Note You can run multiple data collections simultaneously but you must initiate them one at a time Repeat this procedure as many times as necessary selecting a different library each time 1 From the Setup amp Administration tab select Configuration then select SNMP Connections 2 Selecta library in the Monitored Libraries table and then click Get latest data You can select only one library at a
229. ons 8 10 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Preparation Tasks Start a supported Web browser on your computer and enter the URL of the WebLogic administration console http s STA_host_name port_number console Where host_name is the hostname of the STA server port_number is the STA port number of the WebLogic administration console in the current STA version STA must be uppercase For example https staserver example com 7002 console 2 Login using the WebLogic administration console username and password 3 Inthe Domain Structure navigation tree click Security Realms ORACLE WebLogic Server Administration Console Change Center M Home Log Out Prefere View changes and restarts Home No pending changes exist Cick the Release Home Page Configuration button to allow others to edit the domain Information and Resa a Configure applications a Configure Gridlink for R a Recent Task Status a Set your console prefere Domain Configuration The Summary of Security Realms screen appears 4 Inthe Name column select the myrealm active link do not select the check box Summary of Security Realms A security realm is a container for the mechantems indluding users groups security roles security poles and security providers that are used to protect WebLogic resources You can have multiple security realms in a WebLogic Server domain but on
230. or table v_mdv_status_codes It s a view create dummy table for view Disconnecting from localhost 6 To reduce the dump file size by approximately 50 percent gzip the file cd path_to_dump_file gzip dump_file_name sql 8 16 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks Task 2 Transfer the Old Database Dump Use this procedure to transfer the compressed dump of the old STA database to either an off platform backup server single server method or the new STA 2 1 x server two server method Caution If you are upgrading from STA 1 0 x with the single server method you must back up the STA database to another server Do not back up the database to a filesystem on the current STA server as the Linux 6 x installation in Task 3a Install the New Linux Version Upgrades From STA 1 0 x on page 8 18 will destroy all data on the server 1 If you have not done so already stop all STA services STA stop all 2 Performa checksum before transferring the file to the backup server cksum dump_file_name sql gz The output includes a checksum value and byte count Record the checksum value you will use it to verify the file integrity after transferring the file to the backup server 3 Transfer the file to the target server using a transfer utility such as SCP The p option preserves timestamp values scp p dump_file_name sql gz target_host path In Example
231. or the provider See Task 3 Set the JAAS Control Flag on page E 15 for instructions d Ensure WebLogic Server will call all authentication providers in the order you want See Task 4 Ensure Proper Order of Authentication Providers on page E 17 for instructions e Apply the changes to WebLogic Server and STA See Task 5 Apply All Configuration Changes on page E 19 for instructions 3 Verify the configuration See Verify Configuration of Authentication Providers on page E 21 for instructions Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Use the following procedures to configure OpenLDAP and Microsoft Active Directory authentication providers To configure IBM RACF providers see Tasks for Configuring IBM RACF Authentication Providers on page E 23 a Prepare the External Authentication Provider for STA Authentication on page E 5 a Edit the WebLogic Server Active Security Realm on page E 5 a Task 1 Add an External Authentication Provider on page E 8 E 4 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Task 2 Define Provider specific Information on page E 10 Task 3 Set the JAAS Control Flag on page E 15 Task 4 Ensure Proper Order of Authentication Providers on page E 17 Task 5 Apply All Configuration Changes on page E 19 Verify Configuration of Authentication Providers on p
232. ore SNMP v3 users and you can use one of these for STA however Oracle highly recommends defining a new unique SNMP v3 user for this purpose a Oracle recommends not using the values public or private for the SNMP v3 username as these values are well known and present a security risk Oracle recommends using values that are not as easily discovered a The username can only contain alphanumeric characters a z A Z 0 9 Special characters are not allowed To define the SNMP v3 user you must provide the following values See Appendix C for a worksheet you can use to record the values you will use SNMP v3 username The STA server listens for traps sent by this user It is also the SNMP v3 recipient name used when creating trap recipients Must be the same on all libraries SNMP v3 authorization password Authorization password you assign to the SNMP v3 user Must be at least eight characters in length and cannot contain commas semicolons or equal signs SNMP v3 privacy encryption password Privacy password you assign to the SNMP v3 user Must be at least eight characters in length and cannot contain commas semicolons or equal signs 5 2 StorageTek Tape Analytics Installation and Configuration Guide Library SNMP Configuration Tasks SNMP v2c user community SNMP v2c user community string Oracle recommends not using the values public or private as these values are well known and present a sec
233. ormation about this LDAP Authentication provider You can also use this page to set the JAAS Control Flag to control how this provider is used in the login sequence AE Mame My AD Server The name of the Java dass used to load the LDAP Authentication provider More Info a Description Provider that performs LDAP authenticaton A short description of the LDAP Authe r pe er More info Version 1 0 The version number of the LOAP Authentication wovider More info a Control Flag OPTIONAL Returns how the login sequence uses the REQUIRED REN OR PRE ae 5 Click Save 6 Proceed to Task 4 Ensure Proper Order of Authentication Providers on page E 17 Task 4 Ensure Proper Order of Authentication Providers Once you have added external authentication providers to the active security realm use this procedure to define the order in which they are called by WebLogic Server By default new authentication providers are added to the bottom of the list and are therefore called last See Authentication Provider Order on page E 3 for details 1 If you have not done so already access the active security realm and lock it for editing See Edit the WebLogic Server Active Security Realm on page E 5 for instructions 2 Inthe Settings for myrealm control bar select the Providers tab Home Log Out Preferences 3 Record Help Q Welcome weblogic Home gt Summary of Securty Aeaims gt myreaim Settings for myrcalm Configuration
234. ose the best time for your organization See the STA User s Guide As needed data collections For STA to receive SNMP data from a library you must perform a manual data collection at the following times 1 4 StorageTek Tape Analytics Installation and Configuration Guide Prepare Service Requests for the Libraries and Drives After anew library connection has been configured a After SNMP settings in STA and on the library have been modified a After a Redundant Electronics switch has occurred a After there have been any hardware configuration changes to the library including moving drives See the STA User s Guide STA Services Configuration Database backups You should configure a remote backup server for STA database backups See Configure the Remote Database Backup Server on page 7 3 Database backup space management It is the customer s responsibility to manage space on the STA remote backup server You should periodically check the amount of space consumed by the STA database backups and take appropriate action when space is running low Configure the STA Resource Monitor on the STA server To assist with management of the STA server you can define high water marks for disk and memory usage and the Resource Monitor will alert you if these are exceeded See Configure the STA Resource Monitor on page 7 7 STA Database Tuning Database considerations for larger installations If you have significant exchanges
235. ost_name and port_number are the name and port number of the WebLogic Administrator console defined during STA installation The default HTTP port number is 7019 and the default HTTPS port number is 7020 For example https sta_server 7020 console On the Welcome screen enter the WebLogic Administration console username and password defined during STA installation and then click Login Configuring External Authentication Providers for STA E 5 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers ORACLE WebLogic Server 11g Administration Console The WebLogic Server Administration Console Home page appears ORACLE WebLogi Serer Aina Col D tere isp Oa helemens Eten tee La Wekeme webiog Corr tes to rea OA Pe Lock amp Edt Button to medify act or wets tees n Oye Somer earners al Iniborpeat bees Common idut stor Tak Crscrptors head De doretate tah 2 Qucsben on My Crede Support Cade urdan Over ven 4 Use the following steps to access the active security realm a Inthe Domain Structure navigation tree select Security Realms E 6 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefere View changes and restarts No pending changes exist Cick the Release Home Page Configura
236. ou can reach Oracle s public yum server see Ensure Proper Setup of yum optional on page 2 9 use one of the following methods to install packages Install packages one at a time The specified package will be downloaded and checked and you must answer all prompts yum install package_name Install all packages at once with no prompting The y option automatically answers yes to all installation prompts yum y install binutils compat libcapl compat libstdc 33 1686 cronie expect gcc gcc ct glibc glibc devel libaio libaio devel libgcc libstdc libstdc devel net snmp utils rpm build sysstat xorg x11 utils a If your network firewall prohibits external network access you can use yum to install locally available packages from the Linux media For example cd mnt install_media_mount_location packages yum install package_name Ensure Proper Setup of SSH Use this procedure to ensure that SSH secure shell is set up correctly on the STA server This will speed up transfers of STA database backups to a remote host 1 Open the SSH configuration file with a text editor vi etc ssh sshd_config 2 Search for the AddressFamily and UseDNS entries Modify them so they are not preceded with the comment character and their values are as follows AddressFamily inet UseDNS no 3 Save and exit the file 4 Restart the sshd daemon service sshd restart Ensure Proper DNS Settings Use this procedure to ensur
237. ou want to assign to this account The entry is masked as you type Password requirements are as follows a Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not include any of the following special characters EnS SRE Ne Confirm Password Type the password again to ensure you have entered it correctly Screen specific Buttons None Set Up Database Accounts StorageTek Tape Analytics Installation 2 1 0 ORACLE Set up Database Accounts Welcome i i 11 e In the following screens you will set up four accounts used by STA for internal y installation Location database access You will not use these accounts for normal STA operations Prerequisite Checks IMPORTANT Make a note of these account credentials in a secure manner The y Enter Root Password STA database root account password is not retrievable To protect your site l Setup D6 Directories security usernames and passwords are purposely not preconfigured nor ji hard coded x Set up Admin Accounts WebLogic Administrator Y STA Administrator I SR Set up Database Accounts Help lt Back Next gt Cancel STA Graphical Installer and Deinstaller Screen Reference A 19 STA Graphical Installer Screens This screen describes the types of information you will define on the next four screens Read the text then click Next to continue Screen Fields None Screen specific Buttons None
238. ould send to STA 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 Version Select v3 Trap User Name SNMP user name you created in Create an SNMP v3 User on page 5 7 Authentication Protocol Select SHA Authentication Passphrase Authorization password you created in Create an SNMP v3 User on page 5 7 Privacy Protocol Select DES Privacy Passphrase Privacy password you created in Create an SNMP v3 User on page 5 7 Engine ID This field will be supplied automatically Do not modify the value 4 Click OK 5 10 StorageTek Tape Analytics Installation and Configuration Guide 6 Configuring Library Connections in STA For STA to monitor libraries at your site you must perform some configuration activities on the libraries and some on the STA server This chapter describes activities performed on the STA server This chapter includes the following section STA Configuration Tasks STA Configuration Tasks You must complete the procedures in the order listed Once you have completed this process STA can begin monitoring the libraries and performing analytics Log In to STA Log In to STA on page 6 1 Verify SNMP Communication With a Library on page 6 2 Configure SNMP Client Settings for STA on page 6 3 Configure the SNMP Connection to a Library on page 6 5 Test a Library SNMP Connection on page 6 7 Perform a Manual Data Collection on page 6 9 Use this procedure to log in to S
239. oup 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 substitute the name you have chosen if it is different Oracle install user A Linux user for installing and upgrading Oracle products on the STA server This can be any user that is a member of the Oracle install group Installing STA 3 1 Users Groups and Locations Used by the STA Installer The instructions and examples in this guide use the name oracle for this user substitute the name you have chosen if it is different Oracle central inventory location 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 install user must own this directory and have full permissions to it To ensure other users in the Oracle install group have proper access so they can install Oracle products you should not use the Oracle install user s home directory This location should be separate from the other directories described in this section The instructions and examples in this guide use opt oracle oralnventory for this location substitute the directory you have chosen if it is different Note Oracle recommends registering this location after STA installation is complete so all Oracle installers use the same central in
240. our network administrator 6 Monitor TCP IP packets sent between the STA server and the library tcpdump v host library_IP_addr gt var tmp file_name amp Where a Vindicates verbose output a host indicates to collect packets to or from the indicated host only in this case the library a library_IP_addris the IP address of the public port on the library a file_name is the name of the file to which to save the output Configure SNMP Client Settings for STA Use this procedure to add or modify SNMP client settings for STA These settings configure STA to receive SNMP data from one or more libraries There is just one SNMP client entry for each STA instance at your site Configuring Library Connections in STA 6 3 STA Configuration Tasks 1 From the Setup amp Administration tab select Configuration then select SNMP Connections 2 Proceed as follows a To configure the client settings for the first time select the empty table row in the Client Attributes table then click Edit Configuration SNMP Connections Chent Attributes L Ef Detach a 7 Password Privacy A m r SNMP Username Encryption Encryption Engne ID User Community Trap Communit SHA DES pubic pubic a To modify existing client settings select the entry in the Client Attributes table then click Edit Configuration SNMP Connections Client Attributes Ei Detach Password Privac SNMP Username Sem wr E aie Engine ID User
241. oves the STA application and all associated data and Oracle software The following updates are made The StorageTek_Tape_Analytics subdirectory within the Oracle storage home location is removed completely Other directories in the Oracle storage home location are not affected All STA and MySQL logs are removed from the logs location See Review STA File System Layout on page 2 2 for details about this location a All STA service logs are removed The STA database and all local backups are removed If the database directory or the local backups directory are mount points or include user defined files the directories are retained otherwise they are removed The Oracle central inventory location is not removed by STA deinstallation All data in this directory is retained including all STA installation and deinstallation logs and Oracle software inventory information See Oracle central inventory location for details The STA deinstaller is available in both graphical and silent modes See STA Installer Modes on page 3 7 for details See STA Installation and Deinstallation Logs on page 3 5 for details about the STA deinstallation logs STA Deinstallation Tasks The following sections describe how to use the STA deinstaller Deinstall STA on page 9 2 a Verify Successful Deinstallation on page 9 2 Deinstalling and Restoring STA 9 1 STA Deinstallation Tasks Deinstall STA Restore STA on page 9 3
242. path must begin with an alphanumeric character and must only contain alphanumeric characters underscores L hyphens or periods 0 Help lt Back Next gt Cancel This screen allows you to specify the location where STA and associated Oracle software will be installed on the server You cannot install over a previously installed version of STA To verify that STA is not already installed in a particular location you can enter a directory in the Oracle Storage Home field and then click the View button a fno software has been installed in that location the list is blank a If software has been installed it is listed as shown in Figure A 1 Sample Listing of Oracle Storage Home Screen Fields Oracle Storage Home Enter the directory where STA and associated Oracle software will be installed Each software package will be installed in its own subdirectory within this directory You cannot specify a directory where STA is already installed See Table 2 2 Recommended File System Layout for technical recommendations about this directory Depending on whether this directory already exists the Oracle install user and group must have the following permissions a If the directory does exist they must have full permissions to it a If the directory does not exist they must have full permissions to the parent directory so the STA installer can create the Oracle Storage Home directory You must enter an absolute path or
243. per Order of Authentication Providers on page E 17 for instructions Note The DefaultAuthenticator and the DefaultldentityAsserter must be the first two providers in the list JAAS Control Flag The Java Authentication and Authorization Service JAAS Control Flag attribute assigned to each provider defines whether users must be authenticated by that provider The default value for this attribute is Optional but for STA Oracle recommends setting it to Sufficient for each provider including the DefaultAuthenticator See Task 3 Set the JAAS Control Flag on page E 15 for instructions The Sufficient setting indicates that if the provider successfully authenticates a user no additional authentication is required and if the provider cannot authenticate the user authentication continues to the next provider in the list See Fusion Middleware Securing Oracle WebLogic Server for descriptions of all options for this attribute LDAP Authentication Referrals If an external authentication provider uses LDAP referrals you must ensure that the Follow Referrals attribute is selected on the Provider Specific screen This attribute is Configuring External Authentication Providers for STA E 3 Authentication Provider Configuration Process Overview selected by default but Oracle recommends you verify the setting See Task 2 Define Provider specific Information on page E 10 for instructions Using SSL for Communications
244. per hour rates that is greater than 300 EPH with multiple libraries attached to a single STA server and a long history with STA you might need to make adjustments to two InnoDB buffer pool parameters in the MySQL configuration file etc my cnf To change these parameters first stop STA then modify the my cnf file and then restart STA to activate the new values The key parameters that may need adjusting based on your server configuration are as follows Minimum Recommended Parameter Value Comments innodb_buffer_pool_size 24 GB or greater The value should be 70 80 percent of the STA server s physical memory innodb_buffer_pool_instances 8 More buffer pools improve concurrent processing Prepare Service Requests for the Libraries and Drives Use this procedure and the referenced sections to provide Oracle Support with the information needed to prepare your libraries and drives for monitoring by STA Note If STA will be monitoring a library complex prepare a service request for each library in the complex Additionally open a Service Request to install the latest drive firmware supported by STA Pre installation Planning 1 5 Prepare Service Requests for the Libraries and Drives 1 Verify the library firmware version See Verify the Library Firmware Version on page 4 7 2 Verify a high memory HBT card is installed SL3000 and SL8500 only See Verify the Drive Controller Card Version SL3000 and SL850
245. r DefaultAuthenticator _New t e Showing 1to 2of2 Previous Next 6 Record the usernames you want to retain Record STA Usernames Upgrades From STA 2 0 x and Higher For upgrades from STA 2 0 x and higher use this procedure to display and record usernames used to log in to STA You will reenter this information after the upgrade You cannot retrieve the passwords Note For STA 1 0 x usernames were created and maintained through the WebLogic administration console see Record WebLogic Usernames Upgrades from STA 1 0 x Only on page 8 10 for instructions 1 Log in to STA using an STA administrator username 2 From the Setup amp Administration tab select Users The Configuration Users screen displays all STA usernames and their roles Configuration Users ka User Name Description Role sta_sdmin STA admrestrator Administrator sta_operator Operator Operator 3 Record the usernames and roles you want to retain 8 12 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Preparation Tasks Record STA Email Server Settings Use this procedure to display and record the STA email protocol and if the email server requires authentication the account username You will reenter these values after the upgrade You cannot display the password 1 Log in to STA using an STA administrator username 2 From the Setup amp Administration tab select Email 3 Inthe SMTP Serv
246. r interface and has access to all features of Y Prerequisite Checks STA Y Enter Root Password Username Requirements a Directories 1 to 16 characters in length T aaa All usernames must be unique A Set up Admin Accounts Y WebLogic Administrator Password Requirements i 8to 31 characters in length with no spaces STA Administrator Must contain at least one capital letter and one number except a O lt S TIS Enter STA Administrator Username sta admin Enter STA Administrator Password eeeeecee Confirm STA Administrator Password Help lt Back Next gt Cancel You use the STA Administrator account to log into the STA user interface This user has administrator privileges for the STA application and therefore access to all STA screens The account will be created during the installation with the credentials you specify Caution Make a secure record of these account credentials if you lose them you will not be able to log into the STA user interface To protect your site security usernames and passwords are purposely not preconfigured nor hard coded A 18 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Screen Fields Enter Username Type the username you want to assign to the STA Administrator Username requirements are as follows Must be 1 16 characters in length a All usernames must be unique Enter Password Type the password y
247. r is downloaded location STA database Location of the STA database data location STA database backup location Location of the STA database backups on the STA server User Accounts Worksheet 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 1 x See Username and Password Requirements on page 3 3 for details Table C 3 User Accounts Worksheet STA 2 1 x Current Username Username and Account Description and Password Password WebLogic Used to log in to the WebLogic Administration Administration console Caution The username and password for this account are not retrievable If these credentials are lost STA must be re installed STA Used to log in to the STA application with full Administrator access privileges STA Database Owns the MySQL database The predefined username root username root Root User username of root cannot be changed Caution The password for this account is not retrievable STA Database STA uses this account to connect to the database Application User STA Database Non STA and third party applications use this Reports User account to connect to the database STA Database STA administration and monitoring utilities use Administrator this account to
248. rau ninti pia DetndtActhertacater seoraguTapeanelytcsueer lsarege Tape Acabytcs Uner Role Grop Defadtactherscator deerme rr New wee Showng ite Lief Li Previous Nest 4 Inthe Settings for myrealm control bar select the Users secondary tab Configuring External Authentication Providers for STA E 21 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers Settings for myreaim Configuration UsersandGroups RolesandPoldes Credential Mappings Providers Migration a The Users screen appears 5 Verify that the Users table includes all users assigned to the STA access group StorageTapeAnalyticsUser on the configured external providers The following example shows users from two external providers Settings for myrealm Configuraten UsersamdGrowps RolesandPolces CredentalMappings Provides Maaton Users Gope This page deploys nformaton abot each user Put has been configured in thes seaazity resim P Custoenize this table Users Filtered More Columns Exist Nen Ociete Showing ito 40f4 Previous Next sta _sdmn STA adminstrator Defadtauthendcator wedioge Ths user n the defaut aderstater OefavtAuthentcator Nen Desete Showng 1 to 40f 4 Prewous Next 6 Log out of the WebLogic Server Administration console ORACLE WebLogic Server Administration Console Change Center View changes and restarts Click the Lock amp Edit button to modify add or repens delete items in th
249. rectly echo PATH usr 1ib64 qt 3 3 bin usr local sbin usr local bin sbin bin usr sbin usr bin root bin Oracle StorageTek_Tape_Analytics common bin 2 Use the STA command to verify that all STA services are running and active Example 3 1 is a sample successful status display See the STA Administration Guide for details Example 3 1 STA Successful Status Display STA status all mysql is running staservd service is running weblogic service is running staengine service is running and the deployed application for staengine is in an ACTIVE state staadapter service is running and the deployed application for staadapter is in an ACTIVE state staui service is running and the deployed application for staui is in an ACTIVE state 3 Proceed as follows a If the STA services are running and active you can begin configuring the libraries and STA See Chapter 5 Configuring SNMP on the Libraries and Chapter 6 Configuring Library Connections in STA for instructions a If there are any issues with the STA services you can review the installation and STA logs for more information See STA Installation and Deinstallation Logs on page 3 5 for their locations Relocate the STA Logs Directory optional Use this procedure only if you want to relocate the STA and MySQL logs to a location other than the default which is var log tbi After you complete this procedure new logs will be written to the location you designate
250. reen as follows m Version Select v2c a Community Specify the SNMP v2c user community string for example stasnmp 6 Click Apply Using the SL150 user interface 1 Login to the library In the navigation tree select Settings Select the SNMP tab In the SNMP Users table select Add SNMP User Complete the Add SNMP User screen as follows Version Select v2c ame YP NM Community Name Specify the SNMP v2c user community string for example stasnmp 6 Click OK 5 6 StorageTek Tape Analytics Installation and Configuration Guide Library SNMP Configuration Tasks Create an SNMP v3 User All SNMP traps and MIB management information base data are sent to the STA server through the SNMP v3 user Note the user name and passwords you specify as you will use this information when you define an SNMP v3 trap recipient Note the following configuration requirements a The authorization method must be SHA Secure Hash Algorithm and the privacy method must be DES Data Encryption Standard a All libraries monitored by a single STA instance must have the same SNMP v3 user name You should create a new unique user for this purpose a Authorization and privacy passwords must be at least eight characters in length and cannot contain commas semicolons or equal signs Using the library CLI all libraries except SL150 1 Create an SNMP v3 user gt snmp addUser version v3 name name auth SHA authPass auth_password priv
251. ributes specific to that provider Following are guidelines for attributes required for a basic configuration Depending on your site requirements you may need to enter values for other attributes as well Host IP address of the external authentication server Port Port number on which the external authentication server is listening Typically this is 389 a Principal Distinguished Name of the user account on the external provider that WebLogic Server will use to connect to the external authentication server See LDAP Principal User on page E 2 for details Credential and Confirm Credential Password for the Principal user a SSLEnabled Select this check box if communication between WebLogic Server and the external authentication server will be through SSL You must perform additional configuration tasks to fully enable this feature See Using SSL for Communications on page E 4 for details a User Base DN Base distinguished name DN of the tree that contains users a User From Name Filter Filter WebLogic Server should use to find users a User Object Class LDAP object class that stores users a Group Base DN Base distinguished name DN of the tree that contains groups a Group From Name Filter Filter WebLogic Server should use to find groups a Group Object Class LDAP object class that stores groups E 12 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Dire
252. rify it is sufficient for the dump file For example df h dbdumpfiles Filesystem Size Used Avail Use Mounted on dev mapper sta_server STA_DbVol 200G 53G 243G 27 dbdumpfiles 3 Stop all STA services STA stop all 4 Start the MySQL service service mysql start 5 Dump the STA database into a single file Enter the database root user password when prompted mysqldump uroot p opt add drop database comments complete insert dump date events flush logs routines single transaction triggers databases stadb gt dumpfile_path dumpfile_name sql Enter password mysql_root_password Note The optional v parameter for verbose output is not recommended as a large number of messages are displayed in the terminal window and it can significantly slow down the command process for large databases In Example 8 1 the STA 1 0 x database is dumped into the dodumpfiles folder on the STA server with filename Dec14_dump sal Example 8 1 Old Database Dump mysqldump uroot p opt add drop database comments complete insert dump date events flush logs routines single transaction triggers databases stadb gt dbdumpfiles Dec14_dump sql Enter password mysql_root_password Retrieving view structure for table v_library_complex_io Retrieving view structure for table v_library_summary_averages It s base table skipped Retrieving table structure f
253. rmation from the monitored libraries Additionally the new version of STA does not begin receiving information from the libraries until after you have completed all steps in the upgrade and tested the SNMP connection to each monitored library Understanding Automatic and Post installation Upgrades Depending on the new version of STA and your upgrade path the upgrade may be either automatic or post installation The upgrade to STA 2 1 x from any previous version of STA is a post installation upgrade The differences between these upgrade types are described below Automatic upgrades In an automatic upgrade the STA installer takes a snapshot of your existing data installs the new version of STA and then upgrades your data to the new version All these activities are handled automatically Automatic upgrades are possible when the underlying operating system database and installation framework are consistent from one version of STA to the next For example the upgrades from STA 2 0 to STA 2 0 1 and from STA 1 0 to STA 1 0 2 are automatic upgrades Post installation upgrades In a post installation upgrade you must take a snapshot of your existing data then deinstall the current version of STA and install the new one and then run a supplied script to upgrade your data to the new version You must perform these activities manually and in the proper sequence Depending on the new STA version you may also need to install a new version of
254. roviders for STA on page E 1 Pre installation Planning 1 1 Best Practices for STA Deployment Best Practices for STA Deployment Preparation This section provides tips for optimizing the performance and value of the STA server database and application Dedicated STA server To ensure optimal performance and functionality of the STA application STA must be installed on a dedicated server called the STA server Additionally there should be no other applications running on the server Oracle Service can provide support only if these conditions are met Assistance with STA server sizing As soon as possible in the planning process contact your Oracle sales representative for assistance with sizing your STA server Your sales representative can use the STA Server Sizing Tool to provide you with best sizing recommendations to meet your site s current needs and expected growth See the STA Requirements Guide Sizing considerations for larger installations If you have significant exchanges per hour rates that is greater than 300 EPH with multiple libraries attached to a single STA server and a long history with STA you should carefully consider the size and configuration of the following key areas Operating system and main application area Oracle recommends this to be on its own appropriately sized HDD The Oracle storage home location for example Oracle needs to be at least 100GB but you should allocate 200GB if
255. ry for the first time click Add in the Monitored Libraries toolbar Configuring Library Connections in STA 6 5 STA Configuration Tasks Monitored Libraries ZO k ag d Lbrary Name Lbrary Compiex No Gata to display To modify an existing library connection select the library in the Monitored Libraries table then click Edit Monitored Libraries Yas Qa Library Name Library Complex coach A STA IP Address Address es The Define Library Connection Details dialog box appears If this is a new library connection the fields are blank 3 Complete the dialog box as follows The values you specify must match the corresponding ones on the library Library Name Type a name to identify the library throughout the STA user interface screens for example the library host name Library Primary IP Address Type the IP address of the primary public port on the library You cannot specify the IP address of another monitored library Library Secondary IP Address Applies only to SL3000 and SL8500 libraries using Dual TCP IP or Redundant Electronics Specify the IP address of the secondary public port on the library You cannot specify the IP address of another monitored library Leave the field blank for all other libraries including all SL500 and SL150 libraries STA IP Address Select the IP address of the STA server Library Engine ID Do not change this field This is the unique SNMP engine ID of the library a
256. s E et ee le Oan Acuret ster Tas Omopion deed te harnertetor A a queen on My Crede Sopot Oxi Gurdin Omwen emage Sewers Store et orned Apes p6 Medes a Pat Serves orga e Osis Soron o Seruatert Soe M Regeres MA Betty Coches forage POI Proveters Werk Contexts spon o Mei Sere Met om Welcome webloger Corre tet to Ted WTC Serves doh Conmecter Pooks og Mies e Apor Mades iyoni brager iagat Performarce hemes Content 5 0 Montarng Dashboard 4 Inthe Domain Structure section select Environment and then select Servers Domain Structure TBI Environment Clusters Virtual Hosts Migratable Targets 5 Inthe Servers table select the staUi active link select the name itself not the check box Ce OOO O OO soni fa core stern fe swans _ 6 Select the Keystores tab Settings for staUi Configuration Protocols Logging Debug Monitoring Control Deployments Genera Cluster series Keystores ss Federation Services Deployment 7 Inthe Change Center section click Lock amp Edit Configuring Security Certificates D 3 Security Certificate Configuration Tasks ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefer View changes and restarts Home Cikk the Lock amp Edit button to modify add or Home Page Informatio
257. s configured on the monitored libraries See Configure SNMP Client Settings for STA on page 6 3 for instructions To restore SNMP communication between STA and the libraries test the connection to each monitored library See Test a Library SNMP Connection on page 6 7 for instructions Note Once this step has completed successfully STA begins receiving and processing data from each monitored library You may notice incomplete exchanges on the Exchanges Overview screen from exchanges in process either when STA was stopped or when the library connections were restored See the STA User s Guide for details about incomplete exchanges 4 Get the latest SNMP library configuration data from each library See Perform a Manual Data Collection on page 6 9 for instructions Configure STA Services and User Information Perform these steps for all upgrades These steps are performed on the STA server If you want to retain settings from the previous STA version use the values you recorded before the upgrade see Record Current STA User and Configuration Settings optional on page 8 9 Note After the upgrade all logical groups are owned by STA Logical group ownership is not critical to STA functioning and any STA user with Operator or Administrator privileges can modify logical groups Upgrading to STA 2 1 x 8 25 Upgrade Tasks 1 Configure the STA Backup service and STA Resource Monitor service utiliti
258. same server STA is not monitoring libraries while you perform this process This method offers the advantage of not requiring an additional dedicated server for the upgrade If you are upgrading from STA 2 0 or higher you do not need to install a new version of Linux so this method may be sufficient for your needs Figure 8 1 illustrates the single server method You perform Task 1 through Task 9 in sequential order In summary Dump the current database and transfer it to a backup server for safekeeping Task 1 and Task 2 Depending on your current version of STA either install Linux 6 x Task 3a or Deinstall STA 2 0 x Task 3b a Install STA 2 1 x and as a precaution dump the new database Task 4 and Task 5 a Transfer the dump of the old database from the backup server and then load and upgrade it to the new STA version Task 6 through Task 8 Reestablish connections to the monitored libraries and perform necessary manual configuration tasks Task 9 Because the old version of STA must be deinstalled before you install STA 2 1 x you must reenter some user configuration data manually Upgrading to STA 2 1 x 8 3 Choosing Whether to Use One Server or Two Figure 8 1 Single server Upgrade Task Overview Task 3a Install New Linux Task 1 Task 2 Task 4 Dump Old STA Transfer Old STA Install New STA Database Database Task 5 Task 6 Task 7 Task 8 Task 9 Dump New STA Trans
259. scsssssesescsessssseecsesssssnsnesesenes A 5 Welcome serenan icv ses n aaa a a a a a obits et A LM iian A 6 Installati n LOCa tions isscss c is ccs cdscsezecacdecdscdeaecaciaadesecedcauscaacedieascsoasdigsanenettaaceseasesaacsva eadadasesivedensteades A 8 Prerequisite CHECKS isis eee deas nae re iia i AEA a REEE A 10 Enter ROOt Passw Ord T e eaa aT and ar a a E Eai aa D arate a ana ie EEOAE A 14 Set UP DB Directories es ori i neioii erite EEE E lea a Geass eee bh Leas Gta wala Beetaa ses tebe incl A 15 Set Up Admn Accounts epa e E acest E E E E E e Seas teede ebaee A 16 WebLogic Administrator siener iara i pairan ai rae a p a a Va A E Ry A 17 STA Admiitis trator esmas nhen n e a a a aara a A 18 Set Up Database AcCOuUNtS nnen a a tapaea e ad a aint A 19 Database Roof Userni iin ite nial ea ee e a BAe ith ieee A 20 Database Application User riian ca ices atds a ceeds ieee esa adie aie ste ai A 21 Database Reports User stivici cetisscctescslisesedesecieis sesvede svete dade A a E E i E a A 23 Database Admiunistrator s0c3cie Seca cinch Seed Li oede ee aiia ie es A 24 Enter Communication POrts seccescccccccecdessccoseccsadassencecadava cu scecdssdestdastcessecNedd estes ea ecssateastasceetiastna A 25 Webliogic Admim Console nsise sosina ahaaa aa aa Eaa ieh aa A 26 DEAS BI SIO siih eeii in ea esaks sok gus cust in Ves aghptgicanedvsbesnesubdasuaveveer cass asveehgeavbeesrav ie a ea A 28 SLA Adapter titi ii ad tins eaters de ho ec ae veda ea E it fe
260. section 4 Record the library IP address as the primary library IP address This address corresponds to the 1B port SL3000 or SL8500 IP Addresses Redundant Electronics Support 1 From the Tools menu select System Detail 2 Inthe navigation tree select the Redundant Electronics folder If this folder is not listed the Redundant Electronics feature is not available on the library 3 In the Device State field verify that one library controller shows Duplex software ready switch possible this is the active card and the other shows Standby software ready this is the standby card These statuses indicate that the controller cards are functioning normally If you do not see these statuses contact Oracle Support 4 Expand the Redundant Electronics folder and then select the active controller card 5 Record the IP address of the 2B port 6 Repeat Step 4 and Step 5 for the alternate standby controller card SL3000 or SL8500 IP Addresses Dual TCP IP Support 1 From the Tools menu select System Detail 2 In the navigation tree select Library 3 Select the Properties tab then select the General tab The IP address information is displayed in the Host Interface TCP IP 2B and Host Interface TCP IP 2A sections Note If the library also includes the Redundant Electronics feature the IP addresses displayed are for the active controller card only 4 Record the primary IP address 2B section and sec
261. select a topic in the navigation pane on the left To deinstall with the above configuration click Deinstall Help lt Back Deinstall Cancel The screen displays the following details about the software that will be deinstalled a Directory Details Locations of the STA application software and the deinstallation log a Feature Sets to Deinstall Names and version numbers of the software packages that will be deinstalled Verify this information and then continue as follows a Click Cancel to cancel and exit the deinstaller a Click Deinstall to proceed Screen Fields None Screen specific Buttons Deinstall Click to begin deinstalling STA Once you click this button you cannot pause or cancel the deinstallation A 40 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Deinstaller Screens Deinstallation Progress Oracle StorageTek Tape Analytics 2 1 0 Deinstallation RA Deinstallation Progress ORACLE va 100 2 Deinstali Deinstallation Progress I w Deinstallation Complete v View Successful Tasks View Log Deinstallation Successfu Help Next gt The STA deinstallation begins and the screen displays the status of each task Caution Do not close this window or otherwise interrupt the deinstallation while it is in progress as this may leave incomplete STA components on the server Note If either of the database locations are mount
262. sesbratst F 1 Create the STA SNMP v2c Trap Recipient on the Library cccececes cesses eseeteteseseeteteseeneenens F 2 Index Enable SNMP v2c Mode for STA Preface This document provides concepts and procedures for installing and configuring Oracle s StorageTek Tape Analytics STA Audience This document is intended for the following audiences a Linux Administrator Installs configures and administers Linux on the STA server a STA Administrator Installs configures and administers the STA application a Library Administrator Configures and administers StorageTek libraries a MVS System Programmer Configures and administers access to STA by IBM mainframe users Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http www oracle com pls topic lookup ctx acc amp id docacc Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support For information visit http www oracle com pls topic lookup ctx acc amp id info or visit http www oracle com pls topic lookup ctx acc amp id trs if you are hearing impaired Related Documents The STA documentation set consists of the following documents For users of the STA application a STA Quick Start Guide Use this guide to introduce yourself to the STA application and some features of the user i
263. set up an SMC Started Task that runs the HTTP server See the ELS document Configuring and Managing SMC for detailed instructions Note The SMC Started Task must match the AT TLS rule that has been defined Alternately allow the AT TLS definition to use a generic jobname for example SMCW If you are using a value supplied STC identifier for example JOBNAME JOB this will cause a CGI routine connection failure The port number used for the HTTP server must match the one defined in the WebLogic console and the host must match the IP name for the host where the SMC task runs Note An existing SMC can be used if it exists on the host where RACF authorization is to be performed In this case use the port number of the existing HTTP server when you are performing the WebLogic configuration Task 3 Configure AT TLS AT TLS is an encryption solution for TCP IP applications that is transparent to the application server and client Packet encryption and decryption occurs in the z OS TCPIP address space at the TCP protocol level AT TLS requirements for RACF authorization are stated in the STA Requirements Guide The following RACF commands list the status of the various RACF objects that you will define in the configuration process a RLIST STARTED PAGENT STDATA ALL a RLIST DIGTRING ALL a RLIST FACILITY IRR DIGTCERT LISTRING ALL RLIST FACILITY IRR DIGCERT LST ALL a RLIST FACILITY IRR DIGCERT GENCER
264. sman oii clic OiicinstallAPISessiot 18T13 07 44 879 06 00 sysman NOTIFICATION oracle sysman oil olic OlicinstallAPiSessiot 18T13 07 44 880 06 00 sysman NOTIFICATION oracle sysman oii clic OlicinstallAPiSessiog 18713 07 44 884 06 00 sysman NOTIFICATION oracle sysman_oil clic OlicNextCeninstallA 18T13 07 44 887 06 00 sysman NOTIFICATION oracle sysman cii cite OlicNextCeninstallA 18T13 07 44 889 06 00 sysman NOTIFICATION oracle sysman oil clic OlicNextCeninstallA sysman NOTIFICATION oracle sysman oil clic OiicNextCeninstallA sysman NOTIFICATION oracle sysman oil clic OlicConfigContext 9 sysman NOTIFICATION oracle sysman oii oiif oilfw OiifwinstallPhal 18713 07 46 702 06 00 sysman NOTIFICATION oracle sysman oil ollf_olifw OlifwinstallPhai 18T13 07 46 704 0 sysm an NOTIFICATION oracle sysm an oil ollf ollfw OlifwinstallPha 18T13 07 46 711 06 00 sysman NOTIFICATION oracle sysman oil ollf olifw OlifwHomeSetu 18T13 07 46 712 0 s sman NOTIFICATION oracle sysman cii clip olipg OlipgActionsF 18713 07 46 712 00 sysman NOTIFICATION oracle sysman oil olls OlisVariable host 18T13 07 46 713 06 00 sysman NOTIFICATION oracle sysman oii ciip olipg OlipgActionsF 18T13 07 46 763 06 00 sysman NOTIFICATION oracle sysman oil olls OlisVariable host 18T13 07 50 926 06 00 as NOTIFICATION oracle as install engine mo
265. specify an absolute path If the directory you specify already contains a database subdirectory mysql a warning message is displayed You can either specify a different database location or accept the current entry in which case the database subdirectory will be removed during the STA installation Database Backup Location Enter the directory where STA database backups will be located on the server This directory cannot be the same as the Database Data Location You must specify an absolute path If the directory you specify already contains a database backup subdirectory local a warning message is displayed You can either specify a different backup location or accept the current entry in which case the backup subdirectory will be removed during the STA installation STA Graphical Installer and Deinstaller Screen Reference A 15 STA Graphical Installer Screens Screen specific Buttons None Set Up Admin Accounts StorageTek Tape Analytics Installation 2 1 0 ORACLE Set up Admin Accounts va Welcome y H In the following screens you will set up two accounts used for administering y installation Location configuring and accessing STA i Prerequisite Checks T IMPORTANT Make a note of these account credentials in a secure manner If you y Enter Root Password lose the WebLogic Admin Console credentials then STA must be re installed To set up D8 Directories protect your site security usernames and passwords are
266. ssfully copied to home oracle oraInventory logs Example B 6 Sample Failed STA Silent mode Installation Final Messages ERROR Rule_CalculateFreeSpace_Error Aborting Install Logs are located here tmp OraInstall2014 09 24_09 29 29AM Error during execution error code 256 STA Silent mode Installer and Deinstaller B 7 STA Silent mode Deinstaller Tasks 4 When the installer completes successfully verify that STA is running See Verify Successful Installation on page 3 12 for instructions STA Silent mode Deinstaller Tasks a Create the Silent mode Deinstaller Response File on page B 8 a Run the Silent mode Deinstaller on page B 9 Create the Silent mode Deinstaller Response File Use this procedure to create the silent mode deinstaller response file and add encrypted passwords to it 1 Log in as the Oracle install user 2 Use a text editor to create the deinstaller response file with a name of your choice See Example B 2 for a file template Copy and paste the template into a text file and leave all variables blank 3 Save the file with a name and location of your choice 4 Change to the directory where the response file build utility has been downloaded The name of the utility is silentlnstallUtility_version jar For example ed Installers 5 Run the response file build utility java jar silentInstallUtility_2 1 0 64 124 jar response file Where response_file is the absolute p
267. ssssseseseesssssesesesesssesesesesesseseessens 8 24 Recover a Failed Database Upgrade optional ccccsecseesseseseseenetesesesneeseseecesesesesneneneneees 8 26 9 Deinstalling and Restoring STA STA Deinstallation Overview c ccccccssessscsscesssssceseecseseescessecseecssessecsecssecaeceasesceeseseseesseseeeeseeeseeaes 9 1 STA Deinstallation Tasks ienn ci betees Seetacdt Bs Aan sande ana asas Aaaa aia 9 1 Deiristall STA 2 2 o82scet heehee a a india leinieiia ised awa feeds 9 2 Verify Successful Deinstallation srinata sree reside aiana dp vaasi iri aint 9 2 EEO n DT A SE A E E E E AE A IE EE 9 3 A STA Graphical Installer and Deinstaller Screen Reference vi Graphical mode Display Requirements sse sesssesssstsstesresrertersisstsstsstnsissesnesnentienesnesnsenienesnenneenees A 1 Local Connections inane narra ar iaire a i a r a a a raa a leeds A 1 Remote Connections Using a Secure Shell SSH e ss sssssssssssissessresisstessssrssnertensesresnesnsesessesnes A 2 Remote Connections Using Desktop Sharing see sssssrsssssrrtssstesttesssertisnterstssssestesnteestesntesnten te A 2 Troubleshooting Graphical Display ISSUES ssessessssssessesssssissessesstestestesessrestentesresnesnesneesessesses A 3 STA Graphical Installer Screens 0 0 0 cc cece eee ceeseeeecececeseeeeeceseseesenesesesesseesesesseseeesessseenenes A 3 Installation and Inventory Setup ccccccssesesescsssssesesescsesesesesescsesesese
268. st be enabled on both the drives and the library for STA tor receive rich drive data Use this procedure to ensure that the ADI drive interface is enabled on the library See ADI Interface for LTO Drives on page 4 1 for details This procedure is performed using the library CLI For SL3000 or SL8500 Libraries 1 Display the status of the ADI interface drive adiEnable print 2 If Attributes Adi Status is true you can quit this task If it is false proceed to the next step 3 Enable the ADI interface drive adiEnable on 4 Reboot the library to activate the change For SL500 Libraries 1 Display the status of the ADI interface enableADI print 2 If enableADI set to is on you can quit this task If it is set to off proceed to the next step 3 Enable the ADI interface enableADI on 4 Reboot the library to activate the change Ensure the Correct Library Complex ID SL8500 only For STA to roll up library complex data correctly each library complex at your site must have a unique complex ID Use this procedure to ensure the correct library complex ID for each SL8500 library See Library Complex ID SL8500 only on page 4 3 for details This procedure is performed using the library CLI 1 For each SL8500 library that will be monitored by STA display the complex ID currently assigned SL8500 gt config complexId print Complex Id 3 2 Verify that each standalone library and each library complex has a uniqu
269. t T NOTE Validation of the root account password will take a few seconds Enter Root Password Enter System Root Password seeeees Help lt Back Next gt Cancel The STA installer requires Linux root access to perform the installation Screen Fields Enter Root Password Type the password for the Linux root user The entry is masked as you type It may take several seconds to validate the password Screen specific Buttons None A 14 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Set Up DB Directories StorageTek Tape Analytics Installation 2 1 0 Set up DB Directories a Welcome q a Please specify the locations for the STA database and local backup files installation Location Prerequisite Checks Enter Root Password HH Set up DB Directories Database Data Location for example dbdata ddd Database Backup Location for example dbbackup ddbackup Help lt Back Next gt Cancel This screen allows you to specify locations for the STA database and local STA database backups The STA installer will create these directories if they do not already exist See the STA Administration Guide for information on managing the database services and backups Screen Fields Database Data Location Enter the directory where the STA database will be located This directory cannot be the same as the Database Backup Location You must
270. t the SL500 Volume Label Format SL500 only on page 4 10 Yes Set the SL150 Volume Label Format and Drive Element Addressing Yes Mode SL150 only on page 4 11 Note For SL500 SL3000 and SL8500 libraries many tasks allow you to choose which interface to use CLI or SL Console For SL150 libraries you must use the browser based user interface exclusively Log In to the Library Using the library CLI all libraries except SL150 1 Establish an SSH connection to the library using the IP address or DNS alias 2 Log in to the CLI using the admin username and password Using the SL Console all libraries except SL150 1 Start the SL Console application 2 Click the About button to display the current SL Console version and verify that it meets the library firmware minimum requirements 3 Click Close to return to the Login screen 4 Log in using the admin user name password and library IP address or DNS alias For SL3000 and SL8500 libraries with the Redundant Electronics feature you can only log in to the active controller Using the SL150 user interface 1 Browse to the hostname or IP address of the SL150 library 2 Login with your user ID and password The user ID must have the role of administrator Verify the Library Firmware Version Use this procedure to verify that the library firmware meets or exceeds the minimum requirements stated in the STA Requirements Gui
271. tallation and Configuration Guide Upgrade Tasks Note Because the upgrade process is not yet complete the Dashboard portlets display the message No data to display this is normal The library data will be displayed correctly after you upgrade the database and configure the new STA version Log out of STA Open a terminal session on the STA server and log in as the system root user Stop all STA services STA stop all This step applies only if you want STA to monitor the libraries using SNMP v2c see Appendix F Configuring SNMP v2c Mode for details Starting with STA 2 0 SNMP v2c is enabled by default Use the following steps to confirm that it is enabled a Change to the STA configuration files directory cd Oracle_storage_home Middleware user_projects domains TBI b Display the SNMP version properties file and verify that the V2c parameter is set to true cat TbiSnmpVersionSupport properties Vac true Verbal false c Ifthe parameter is not set to true see Enable SNMP v2c Mode for STA on page F 3 for instructions on how to change it Task 5 Dump the New STA Database optional This procedure is optional but recommended Use this procedure to dump the empty STA 2 1 x database as a safeguard If the database upgrade Task 8 Upgrade the Old Database cannot be completed you can restore the empty database to recover STA 2 1 x to a state in which it can be configured to run as if it were newly i
272. taller or deinstaller See Appendix B STA Silent mode Installer and Deinstaller for details In a browser window access the Oracle Software Delivery Cloud website at the following URL http edelivery oracle com Click Sign In Register Enter the user ID and password provided by Oracle Support or create a new account On the Terms amp Restrictions screen select the check boxes to indicate your acceptance of the License Agreement and Export Restrictions and then click Continue Perform the following steps on the Media Pack Search screen a Inthe Select a Product Pack menu select Oracle StorageTek Products b Inthe Platform menu select Linux x86 64 c Click Go In the Results table select Oracle StorageTek Tape Analytics 2 1 1 and click Continue Click Download for each of the media pack zip files and save them to a location containing at least 4 GB of free space Use an unzip tool to extract the contents of the zip files to the STA installer location you have selected in Identify or Create Information Required for the Installation on page 3 7 for example Installers Ensure that the Oracle install user has execute permissions to the sta_install_version_ linux64 bin file and read access to the sta_install_version_linux64 2 zip file For example cd Installers Is la rw r r 1 oracle oinstall 5964 Oct 23 16 14 silentInstallUtility jar rw r r 1 oracle oinstall 1275158996 Oct 23 13 35 sta_install_
273. te Changes ORACLE WebLogic Server Administration Console Change Center Home Log Out Prefere View changes and restarts Home gt Summary of Security Messages Pending changes exist They must be activated W Settings updated succe Settings for myrealm Configuration Users ar General ROEM Seat Save Configuring External Authentication Providers for STA E 19 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers The Messages area indicates that STA must be restarted for the changes to take effect Home Log Out Preferences Help Q Rea yras jers gt test Messages Al changes have been activated However 4items must be restarted for the changes to take effect 2 Log out of the WebLogic Administration console ORACLE WebLogic Server Administration Console Change Center t toe Se a resm gt Providers Cick the Lock amp Edit button to modify add or delete items in this domain Lock amp Edt Messages W Al changes have been actvated How Settings for myrealm 3 Open a terminal session on the STA server and log in as the system root user 4 Stop all STA services See the STA Administration Guide for command usage details STA stop all Stopping the staui service Successfully stopped the staui service Stopping the staadapter service Successfully stopped the staadapter service Stopping the staengine service Successfully stopped the staeng
274. te Checks Checking existing STA instances Checking MySQL not installed Checking Operating System Compatibility Checking tmp available space 1G Wi Checking tmp write privileges Checking Operating System has SELINUX disabled Checking Operating System services are stopped iptables Checking Operating System services are stopped snmpd and snmptrapd Checking required ports available 161 and 162 mar Checking required packages rpm build _ Checking required packages glibc Checking required packages expect Checking required packages binutils 2 2 2 2 2 2 lt 7 2 2 v 2 2 2 2 Checking required packages compat libcap1 View Successful Tasks View Log Ope P Checking rating System services are stopped iptables R Expected result Service iptables is stopped 5 Actual Result Service iptables is stopped Check complete The overall result of this check is Passed f StOPPEd SAMPA and snmptrapd PChecking required ports available 161 and 162 bed Help lt Back Next gt y Cancel Screen Fields None Screen specific Buttons Stop Click to stop the verification process at the current task You may want to do this so you can display detail for a selected task that has already completed Rerun Click to run the verification process again from the beginning This allows you to resolve any Failure or Warning outcomes without exiting and restarting the STA installer Vi
275. terface to the Oracle Key Manager OKM tape encryption solution Both the drive and the Belisarius card firmware must meet the minimum requirements for STA Table 4 1 How ADI is Enabled on IBM LTO Drives IBM LTO Drive LTO 3 LTO 4 LTO 5 LTO 6 IBM without the Oracle Support configures Oracle Support configures NA Belisarius adapter card the drive hardware for ADI mode the drive hardware for ADI mode IBM with the Belisarius adapter card NA Oracle Support configures The drive firmware must the drive hardware for ADI be configured for ADI mode mode with Virtual Operator Panel VOP Contact Oracle Support for assistance Enabling ADI on the Library By default ADI is not enabled on SL500 SL3000 and SL8500 libraries and you or Oracle Support must enable it manually Because enabling ADI requires a reboot of the library you should enable it in advance if you are planning to install LTO drives For SL3000 and SL8500 libraries you can enable ADI only if the library has a high memory drive controller HBT card See the STA Requirements Guide for details about the HBT card Dual TCP IP and Redundant Electronics SL3000 and SL8500 only Redundant Electronics and Dual TCP IP are optional features for SL3000 and SL8500 libraries Dual TCP IP protects library host operations from network failures by providing two library TCP IP ports typically configured on separate subnets In the eve
276. ther profiles are all shown as SMC ROLE nnn and are used to determine which roles the user has once logged on Note The only role defined to STA is StorageTapeAnalyticsUser To obtain this role you must request your user ID to be added to the SMC ROLE STORAGETAPEANALYTICSUSER profile with READ access Task 5 Import the Certificate File and Private Key File optional This procedure can be valuable to test that public and private keys have been generated successfully and that user IDs and passwords with the appropriate permissions have been defined correctly The test can be done using any browser but Firefox is used here as an example 1 Inthe Firefox Tools menu select Options 2 Select the Advanced tab and then select the Encryption tab 3 Click View Certificates 4 In the Certificate Manager dialog box select the Authorities tab and then select the certificate file to import Click Import Select the Your Certificates tab and then enter the private key file to import Click Import Non Click OK to save and exit the dialog box Task 6 Test the CGI Routine To test the CGI routine from a browser enter the following URL where host port userid and password are set to appropriate values https host port smcegsaf type authentication amp userid userid amp password password amp role s StorageTapeAnalyticsUser The resulting output indicates whether or not the user is authorized to access STA and t
277. tication Protocol Select SHA a Authentication Passphrase Specify an authorization password Privacy Protocol Select DES Privacy Passphrase Specify a privacy password Click OK Retrieve the Library SNMP Engine ID all libraries except SL150 Use this procedure to display the library s SNMP engine ID for example 0x81031 88804b7e542f49701753 This procedure is performed using the library CLI 1 2 Depending on the library model use one of the following commands a For SL3000 and SL8500 libraries gt snmp engineId print For SL500 libraries gt snmp enginelId Save the engine ID to a text file for use in the remaining SNMP configuration tasks Create the STA SNMP v3 Trap Recipient Use this procedure to define the STA server as an authorized recipient of SNMP traps and to define the traps that the library will send Note the following configuration requirements To avoid duplicate records do not define the STA server as a trap recipient in multiple instances For example do not create both an SNMP v3 and SNMP v2c trap recipient definition for the STA server Trap levels 13 Test Trap and 14 Health Trap are new for STA 2 0 x Trap level 4 may not be supported by older library firmware versions however it can always be specified when creating a trap recipient Using the library CLI all libraries except SL150 1 Create an SNMP v3 trap recipient Separate the trap levels with commas
278. tics 2 1 0 Oracle StorageTek Tape Analytics 2 1 0 8 Bere SEU EY OI UT SRTE Fre EYE TENS VEY ee HE ee HORT eT er Wr AAA AA vere wr this installation This page only shows Feature Sets installed at the selected Oracle Storage Home 4 ZA Help lt Back Next gt Cancel STA Graphical Installer and Deinstaller Screen Reference A 9 STA Graphical Installer Screens Prerequisite Checks StorageTek Tape Analytics Installation 2 1 0 Prerequisite Checks Y Prerequisite Checks Checking MYSQL not installed nor Pr CIE JE JE JE JE JE 38 Jh Se Checking required packages ii Checking required packages Checking required packages Checking required packages Checking required packages Checking required packages Checking existing STA instance s Checking imp write privileges 34 Checking Operating System Compatibility Checking tmp available space 1C N X NY Checking Operating System has SELINUX disabled Checking Operating System services are stopped iptables Checking Operating System services are stopped snmpd and snmptrapd Checking required ports available 161 and 162 rpm build glibc expect binutils compat libcap1 compat libstdc ViewLog Stop P Checking Operating System has SELINUX disabled P Checking Operating System services are stopped iptables Checking Operating System services are stopped snmpd and snmptrapad Checking required ports available 161 and 162 eee
279. tion 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 STA 2 1 0 Choose single server or two server upgrade method Verify site and target server meet STA 2 1 0 requirements Determine whether you will need to temporarily increase the size of your tmp filesystem for the upgrade Review environment changes for STA 2 1 0 for 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 Installation and Upgrade Worksheets C 1 Installation and Upgrade Worksheets Table C 1 Cont Upgrade Preparation Activities Activity Comments Done Verify STA is processing exchanges across all monitored libraries Move installation and database logs you wish to retain to a safe place optional Perform service log snapshot on current STA installation optional Download service log bundles you wish to retain optional Rename custom templates with STA prefix optional Record current custom template settings you wish to retain optional Record Executive Report policy settings you wish to retain optional Installation and Upgrade Worksheets Th
280. tion button to allow others to edit the domain Information and Resa Lock amp Edt Helpful Tools a Configure appikations a Configure Gridlink for RZ a Recent Task Status a Set your console prefere Domain Configuration Domain Doman Environment b Inthe Realms table select the myrealm active link Summary of Security Realms A searity reaim is a container for the mechaniems induding users groups security roles security podades and security providers that are used to protect WebLogic resources You can have multiple security realms in a WebLogic Server domain but only one can be set as the default active resin This Security Realms page ists each security realm that has been configured in this WebLogic Server domain Click the name of the reaim to explore and configure that realm gt Customize this table Realms Filtered More Columns Exist Cik the Lock amp Edit button in the Change Center to activate all the buttons on this page New Delete Showing 1 to lof 1 Previous Next Showing 1 to lof 1 Previous Next The Settings for myrealm screen appears 5 Use the tabs in the control bar to navigate to the screens you want to edit You can make changes to multiple screens during a single editing session Configuring External Authentication Providers for STA E 7 Tasks for Configuring Active Directory and OpenLDAP Authentication Providers ORACLE WebLogic Server Administration Console
281. tion settings and saving the file you must use the response file build utility to insert encrypted passwords into the file See STA installer response file build utility on page B 4 for details Example B 1 STA Silent mode Installer Response File Template ENGINE DO NOT CHANGE THIS Response File Version 1 0 0 0 0 GENERIC The oracle storage home location This can be an existing Oracle Storage Home or a new Oracle Storage Home STORAGE_HOME required Root access passsword var ROOT ACCESS PASSWORD RESPONSEFILE LOC KEYFILE_LOC DBDATA LOC DBDATA LOC required DBBACKUP LOC DBBACKUP LOC required Weblogic Admin Name Var WEBLOGIC ADMIN NAME required Weblogic Admin Password Var WEBLOGIC ADMIN PASSWORD Weblogic Admin ConfirmPassword Var WEBLOGIC ADMIN CONFIRMPASSWORD STAGUI Admin Name Var B 2 StorageTek Tape Analytics Installation and Configuration Guide Files and Utilities Used With Silent Mode STAGUI ADMIN NAME required STAGUI Admin Password Var STAGUI ADMIN PASSWORD STAGUI Admin ConfirmPassword Var STAGUI ADMIN CONFIRMPASSWORD MySQL root passsword var MYSQL ROOT PASSWORD MySQL root confirm passsword var MYSQL ROOT CONFIRM PASSWORD MySQL App Name Var MYSQL APP NAME required MySQL App Password Var MYSQL APP PASSWORD MySQL App ConfirmPassword Var MYSQL APP CONFIRMPASSWORD MySQL RPTS Name Var MYSQL RPTS NAME required MySQL RPTS Password Var MYSQL RPTS PASSWORD MySQL RPTS
282. tmp is in the root partition Allocate another 200GB if var log tbi is also in the root partition a STA database data for example dbdata Oracle recommends this to be on its own appropriately sized HDD Guidance is from 250GB up to 500GB a STA database backups for example dbbackup Oracle recommends this to be on its own appropriately sized HDD Guidance is from 500GB up to 2TB You may also want to consider using SSDs Filesystem layout For optimal performance and functionality of the STA application plan your STA filesystem layout and space allocations carefully The file system is configured during Linux installation See Review STA File System Layout on page 2 2 Linux Installation Firewalls For optimal system performance you may want to disable the firewall on the STA server See Disable the Linux Firewall on page 2 8 yum for RPM package updates Use yum to install Linux RPM packages yum greatly simplifies the package installation process by automatically searching RPM package repositories for the latest package versions and their dependencies 1 2 StorageTek Tape Analytics Installation and Configuration Guide Best Practices for STA Deployment See Ensure Proper Setup of yum optional on page 2 9 STA Installation Use the latest version of STA For best system performance and the most robust analytics and reporting always upgrade to the latest version of STA See Installing STA on page
283. ton Password Privacy eeececse Privacy Encryption Protocol Privacy DES STA Engine ID 0x800000230 500000 1485000002 Trap Levels 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 User Community stasnmo Trap Community stasnmo Save Cancel 4 Click Save The configuration record is updated and a message box is displayed indicating you should perform a library connection test to establish or re establish the SNMP communication handshake with the libraries Library Connection Tests fa Connectton information has been changed There are now untested STA4brary connections Please initiate a Check Test Connection or Get Latest Data to enable STA to monitor libraries XK 5 Click OK to dismiss the message Configure the SNMP Connection to a Library Use this procedure to configure an SNMP connection to each library you want STA to monitor or to modify an existing connection For existing connections you must perform this procedure if there are changes to any of the SNMP configuration settings on a monitored library such as a change to the library IP address Note If you are configuring multiple library connections at one time to minimize library disruption complete this procedure for all libraries before testing the SNMP connections 1 From the Setup amp Administration tab select Configuration then select SNMP Connections 2 Proceed as follows To configure a connection to a libra
284. tree expand Connection then expand SSH then select X11 In this window make the following selections Inthe X11 forwarding field select the Enable X11 forwarding check box Inthe Remote X11 authentication protocol field select MIT Magic Cookie 1 Leave the other fields blank Remote Connections Using Desktop Sharing To run the STA installer through desktop sharing both the STA server and your local computer must be running a desktop sharing application such as VNC Server on the STA server and VNC Viewer on your local computer In addition your local computer must be able to connect to the STA server through a private network such as Virtual Private Network VPN Following is a sample process for connecting using VNC 1 Install and configure the VNC Server on the STA server 2 Install and configure the VNC Viewer on your local computer A 2 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens 3 Connect to the STA server through the private network Contact your IT administrator for instructions Troubleshooting Graphical Display Issues The STA installer and deinstaller verify that X11 is properly configured for the Oracle install user If these prerequisite checks fail contact your Linux system administrator for assistance You can use the following steps to help troubleshoot problems 1 Log in to the STA server as the Oracle install user and display the curre
285. ts User Database Administrator oe oe ne a i ee a Sin Enter STA Database Administrator Username Stadba Enter STA Database Administrator Password seeeeece Confirm STA Database Administrator Password Help lt Back Next gt Cancel The STA database administrator account is a MySQL account used internally by STA administration and monitoring utilities to connect to the STA database and configure and run scheduled backups The account provides full access except the grant option to all database tables You will not use this account for normal STA operations This account will be created during the installation with the credentials you specify Note Make a secure record of these account credentials To protect your site security usernames and passwords are purposely not preconfigured nor hard coded A 24 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Installer Screens Screen Fields Enter Username Type the name you want to assign to the STA database administrator account for example stadba Username requirements are as follows a Must be 1 16 characters in length a All usernames must be unique Enter Password Type the password to want to assign to this account The entry is masked as you type Password requirements are as follows a Must be 8 31 characters in length a Must include at least one number and one capital letter a Must not include spaces a Must not in
286. tsrtsssseseee 8 9 Rename Custom Templates With STA Prefix optional s ssssssssssstsrrsssssrstsrsserstessserttessses 8 13 Record Current Custom Template Settings optional cccccceeceeesesesteteesceeenescsneneneneees 8 14 Record Executive Report Policy Settings optional cccccccccecseseeceeeesesesteneseeceeenesceneneneneees 8 14 Uperade Tasksi norce asenin ii na aiia ses e tes dlg unas E dior E EA A cede 8 15 Task1 Dump the Old STA Database snnm nomani a aaia i 8 15 Task 2 Transfer the Old Database Dump se sssssssrssssissessesrssinsisrtsnteniesesntsntnniesensesnenntenieneenenns 8 17 Task 3a Install the New Linux Version Upgrades From STA 1 0 X ss ssssssssississssssesesseeseess 8 18 Task 3b Deinstall the Old STA Version Upgrades From STA 2 0 x and Higherv 8 18 Task 4 Install the New STA V ersiOntstss tstsssesevesseoeesesesttecasecesivscnensesivnnnentsnstesveuinbdeesvevs insit 8 18 Task 5 Dump the New STA Database optional ccecccceceseseenetesesesneeseeeecesesescsnaneneneaes 8 19 Task 6 Transfer the Old STA Database to the STA Server cccccccsssssesesessssseseseseseeesesesees 8 20 Task 7 Process and Load the Old STA Database ccesecsssssesesesssesseeseseessesesesesssesesesesees 8 21 Task 8 Upgrade the Old Database cccceccesesescesesesestseseseseseesesceceenesesesneneseececenesesssnaaneneess 8 22 Task 9 Configure the New STA Version cccccesesscssssssesesese
287. uant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
288. uccessfully Raltariommpogre installing ADF and Patches Configuration Progress 3 Error Config Action Installing ADF and Patches failed Fail to install ADF patch LEH nstallation Complete log Y N Config Action Installing ADF and Patches started Config Action Installing AOF and Patches failed Creating STA Domain Configuring STA Domain Configuring STA Managed Servers Staring up STA Managed Servers this can take up to 20 minutes pon RSS gt Cancel Help Screen Fields None Screen specific Buttons None A 36 StorageTek Tape Analytics Installation and Configuration Guide STA Graphical Deinstaller Screens Installation Complete StorageTek Tape Analytics Installation 2 1 0 Installation Complete a install StorageTek Tape Analytics Installation Details STA Home Location Oracle StorageTek_Tape_Analytics Log File tmp Oralnstall201S 01 07_10 34 21AM install2015 01 07_10 34 21AM log WebLogic Admin Console URL http tbivb03 7019 console STA CUI Console URL hatp tbivb03 7021 STA Feature sets have been installed Oracle Application Developer Framework 11 124 Oracle Weblogic Server 10 3 6 0 8 Oracle JDK 1 6 0 75 Oracle MYSQL 5 6 18 Oracle StorageTek Tape Analytics 2 1 0 Installation Complete Oracle StorageTek Tape Analytics installation completed successfully Help Einish The screen displays the following details about the completed installation a Installation
289. uch file or directory 3 If there was no Oracle central inventory pointer file in Step 2 create the Oracle install group See Oracle install group on page 3 1 for details For example groupadd oinstall 4 Obtain the username and password of an Oracle install user or create a new one if necessary This user must belong to the Oracle install group See Oracle install user on page 3 1 for details For example useradd g oinstall d home oracle oracle passwd oracle Changing password for user oracle New password Retype new password passwd all authentication tokens updated successfully 5 If there was no Oracle central inventory pointer file in Step 2 create the Oracle central inventory location This directory must be owned by the Oracle install user See Oracle central inventory location on page 3 2 for details For example mkdir opt oracle oraInventory chown oracle opt oracle oraInventory Is la opt oracle oraInventory total 8 drwxr xr x 2 oracle oinstall 4096 Feb 11 10 49 drwxr xr x 3 root root 4096 Feb 11 10 49 6 Locate the Oracle storage home location or create the directory if it does not exist This directory must be owned by the Oracle install user See Oracle storage home location on page 3 2 for details For example mkdir Oracle chown oracle Oracle Is la Oracle total 8 drwxr xr x 2 oracle oinstall 4096 Feb 11 10 49 drwxr xr x 3 root root 4096 Feb 11 10 49 7
290. urity risk See SNMP v2c Community String on page 5 2 for complete requirements SNMP v2c trap community The SNMP v2c trap community string This field is used only if SNMP v2c is used for communication with the library and is ignored if you are using the recommended SNMP v3 protocol Oracle recommends not using the values public or private as these values are well known and present a security risk See SNMP v2c Community String on page 5 2 for complete requirements SNMP Engine IDs Because the SNMP v3 protocol requires each SNMP device to have a globally unique engine ID the STA server and the libraries each have their own engine IDs In the case of SL8500 library complexes each library in the complex also has its own SNMP agent and therefore its own unique engine ID The engine ID contains a maximum of 31 hexadecimal characters SNMP traps use the sender s engine ID therefore you must specify the library engine ID when you define STA as the SNMP v3 trap recipient Library SNMP Configuration Tasks Table 5 1 summarizes the process for configuring libraries to send proper SNMP data to STA You must perform the tasks in the order listed on each library you want STA to monitor Table 5 1 Tasks to Configure Libraries for STA Task SL150 SL500 SL3000 SL8500 Retrieve the Library IP Address on page 5 4 Yes Yes Yes Yes Enable SNMP on the Library on page 5 5 Yes Yes Yes Yes Ensure an SNMP v2c User o
291. v3 User on page 5 2 Data Collections Connection testing Certain activities performed in STA or on a monitored library may cause the SNMP connection with the affected library to be dropped To minimize the dropped connection time and prevent the loss of large amounts of SNMP data you should perform a connection test at the following times a After the initial SNMP connection between STA and a library has been configured After any STA SNMP client settings have been modified a After any SNMP settings for a monitored library have been modified a After a monitored library has been rebooted After a monitored library has experienced a Redundant Electronics switch a Any time the library engine ID field is blank on the SNMP Connections Monitored Libraries screen a After STA has been upgraded See the STA User s Guide Initial library data collections MIB walks After configuring STA you should perform a manual library data collection on each library configured to the STA server It is recommended that you perform these initial data collections while library activity is low or quiesced See the STA User s Guide Automatic daily library data collections STA relies on automatic daily library data collections to gather key information for processing exchanges and evaluating the state of the library Ideally the daily data collections should be scheduled for times when the library is less busy It is recommended that you cho
292. ventory location on this server See Register the Oracle Central Inventory Location on page 3 15 for details Oracle storage home location The directory where STA and associated Oracle software are installed STA is automatically installed in the StorageTek_Tape_Analytics subdirectory within this location see STA home If this directory already exists the Oracle install user must have full permissions to it If this directory does not exist the STA installer will automatically create it if the Oracle install user has full permissions to the parent directory Note If an earlier version of STA was installed on this server this directory may already exist If so you should verify that it is owned by the Oracle install group not root This location should be separate from the other directories described in this section The instructions and examples in this guide use Oracle for this location substitute the directory you have chosen if it is different STA home 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 STA installer location The directory where you download the STA installer This location should be separate from the other directories described in this
293. ver after deinstallation 1 2 Log in as the Oracle install user List the contents of the Oracle storage home directory It should be empty For example ls la Oracle total 8 drwxr xr x 2 oracle oinstall 4096 Sep 23 14 55 dr xr xr x 31 root root 4096 Sep 23 16 41 9 2 StorageTek Tape Analytics Installation and Configuration Guide STA Deinstallation Tasks Restore STA Use this procedure to deinstall and then reinstall STA for example to repair a current installation You cannot use the STA installer to reinstall or overwrite a current installation 1 en p o 9 Perform a service log snapshot on the current STA installation Oracle Support can use the generated service logs to troubleshoot any issues that may have existed before the upgrade See the STA User s Guide for detailed instructions Stop all STA services STA stop all Perform a database snapshot a Start the MySQL service STA start mysql b Create a backup file usr bin mysqldump uroot p opt routines triggers events flush logs single transaction complete insert comments dump date add drop database databases stadb v gt sta_db_backup backup_ filename sql Enter password mysql_root_password Output will be similar to the following Retrieving view structure for table v_mdv_request_states Retrieving view structure for table version_info Disconnecting from localhost
294. vpwdl engineId 0x00abcde 000000000000000000 2 List the trap recipients and verify the recipient has been added correctly gt snmp listTrapRecipients Using the SL Console SL500 libraries only 1 From the Tools menu select System Detail 2 In the navigation tree select Library 3 Select the SNMP tab then select the Add Trap Recipients tab 4 Complete the Trap Recipients screen fields as follows a Host The IP address of the STA server TrapLeve Comma separated list of trap levels the library should send to STA 1 2 3 4 11 13 14 21 25 27 41 45 61 63 65 81 85 100 a Version Select v3 a TrapUserName SNMP user name you created in Create an SNMP v3 User on page 5 7 a Auth Select SHA a AuthPass Authorization password you created in Create an SNMP v3 User on page 5 7 Configuring SNMP on the Libraries 5 9 Library SNMP Configuration Tasks Priv Select DES PrivPass Privacy password you created in Create an SNMP v3 User on page 5 7 EnginelD Library engine ID you displayed in Retrieve the Library SNMP Engine ID all libraries except SL150 on page 5 8 Do not enter the Ox prefix 5 Click Apply Using the SL150 user interface 1 Inthe navigation tree select SNMP 2 Inthe SNMP Trap Recipients section select Add Trap Recipient 3 Complete the fields as follows Host Address IP address of the STA server Trap Level Commaz separated list of trap levels the library sh
295. wdog Updater Modified as it greatly simplifies the package installation process yum automatically searches RPM package repositories for the latest package versions and their dependencies See Install Required Linux Packages on page 2 10 for the required packages If you will be using yum use this procedure to ensure that yum is configured correctly on the STA server Note The following command examples use the yum repository for Oracle Linux In the commands the 1 in ol6 is lowercase L Installing Linux 2 9 Post Installation Tasks Ping the Oracle public yum server to ensure the network connection is working ping public yum oracle com Change to the yum repository directory and determine the yum repository filename cd etc yum repos d 1s public yum ol6 repo Remove the existing yum repository file rm public yum ol6 repo Download the latest yum repository file from the yum website wget http public yum oracle com public yum ol6 repo Note Subsequent executions of this command will copy anew repository file into the yum repos d folder with a new extension for example public yum ol6 repo 1 However yum always uses the repository file with no extension Open the repository file with a text editor vi public yum ol6 repo In the file locate the entry that matches your Linux version and enable it by setting enabled 1 Disable all other entries by setting enabled 0
296. xecutive Report policies but after the upgrade all private policies are assigned public ownership Use this procedure to record the current ownership settings for all private policies so you can restore them after the upgrade if necessary You can skip this procedure if Executive Report policy ownership is not critical to your implementation 1 Log in to STA using an STA administrator username 2 From the Setup amp Administration tab select Executive Reports Policies 3 Select the Filter icon and filter the screen to show only policies not owned by STA this will display private policies only 8 14 StorageTek Tape Analytics Installation and Configuration Guide Upgrade Tasks f Fitter Data Da Match ANY of the following Fiter Matching ma Se Match ALL of the following Report Owner w Ist STA Xx 4 Record the current Report Owner for each policy If you have many policies you may want to take a screen shot Upgrade Tasks Caution Only a Linux administrator and STA administrator should perform the upgrade All tasks are required and must be performed precisely as written in the order specified or data loss could result If you are using the single server upgrade method you perform the tasks in sequential order see Figure 8 1 Single server Upgrade Task Overview for details If you are using the two server upgrade method you do not perform the tasks in sequential order and Task 6 is omitted
297. xist already 1 Login as the Oracle install user 2 Issue the following command to determine whether the Oracle central inventory pointer file exists cat etc oraInst loc Following are examples of the display depending on whether the file exists a File does not exist cat etc oraInst loc No such file or directory a File exists inventory_loc opt oracle oraInventory inst_group oinstall 3 If the file exists you can quit this procedure otherwise proceed to the next step 4 Usea text editor to create the inventory pointer file It must have the name oralnst loc See invPtrLoc pointer_file on page B 10 for the contents of this file B 4 StorageTek Tape Analytics Installation and Configuration Guide STA Silent mode Installer Tasks 5 Save the file in a directory of your choice If you save the file in the etc directory the STA silent mode installer and deinstaller will find it automatically otherwise you must specify the location when you run these utilities Create the Silent mode Installer Response File Use this procedure to create the silent mode installer response file and add encrypted passwords to it 1 Log in as the Oracle install user 2 Use a text editor to create the response file with a name of your choice See Example B 1 for a file template Copy and paste the template into a text file and make the appropriate changes for your site You must provide values for all variables mar
298. y n X11 X Window System version 11 Applications optional m Internet Browser NA Can be used to configure and manage the STA server locally with the GUI interface Development Development tools NA expect x xx x xx x el6 x86_64 Languages NA NA 2 6 StorageTek Tape Analytics Installation and Configuration Guide Installation Tasks 1 Optional Can be used to configure or re configure the file system once Linux installation is complete 21 When you are finished with package selection click Next Installation will begin If you accidentally click Next before configuring all the packages click Back after the software completes a dependency check 22 When the Congratulations screen appears remove the installation media and then click Reboot A complete log of the installation can be found in root nstall log Run the Linux Setup Agent The Linux Setup Agent starts automatically when you reboot the Linux server Use this procedure to configure the system environment 1 2 On the Welcome screen click Forward Read the License Agreement select Yes I agree to the License Agreement and click Forward On the Software Updates screen if you d like to register your system for updates select Yes I d like to register now Otherwise select No I prefer to register at a later time and click Forward On the Finish Updates Setup screen click Forward On the Create User screen leave the fields blank
299. y DC com All Users Filter User From Name Filter amp cn u objectclass user User Search Scope subtree User Name Attribute cn User Object Class user Use Retrieve User Name as Principle selected Group Base DN OU Groups O STA DC oracle DC com E 14 StorageTek Tape Analytics Installation and Configuration Guide Tasks for Configuring Active Directory and OpenLDAP Authentication Providers All Groups Filter Group From Name Filter amp cn qg objectclass group Group Search Scope subtree Group Membership Searching unlimited Max Group Membership Search Level 0 Ignore Duplicate Membership not selected Use Token Groups for Group Membership Lookup not selected Static Group Name Attribute cn Static Group Object Class group Static Member URL Attribute member Static Group DNs from Member DN Filter amp member M objectclass group Dynamic Group Name Attribute gt Dynamic Group Object Class Dynamic Member URL Attribute User Dynamic Group DN Attribute Connection Pool Size 6 Connect Timeout 60 Connection Retry Limit 1 Parallel Connect Delay 0 Results Time Limit 0 Keep Alive Enabled not selected Follow Referrals selected Bind Anonymously On Referrals not selected Propagate Cause For Login Exception selected Cache Enabled selected Cache Size 32 Cache TTL 60 GUID Attribute objectguid 7 Proceed to Task 3 Set the JAAS Control Flag on page E 15 Task 3 Set the JAAS Co
300. y have existed before the upgrade a Log into STA as an STA Administrator user b From the Setup amp Administration tab select Logs 9 On the Service Logs screen click the Create New Log Bundle icon d Inthe Create New Log Bundle dialog box assign a bundle name and click Save It may take several minutes for the process to complete Use the following steps to download the service log bundle you just created as well as any others you want to retain You must download the bundles one at a time a On the Service Logs screen select the bundle you want to download b Click the Download Selected Log Bundle icon c Inthe dialog box specify the destination location and save the log bundle Record Current STA User and Configuration Settings optional This section applies only if you want to retain current STA usernames and configuration settings in STA 2 1 x Use these procedures to display and record the current values so you can reenter them for STA 2 1 x You will reenter most of these values after the upgrade see Task 9 Configure the New STA Version on page 8 24 for details Record MySQL Usernames Use this procedure to display and record existing MySQL usernames used to access the STA database The STA installer will prompt you for these values You cannot retrieve the passwords 1 Open a terminal session on the current STA server and log in as the system root user Upgrading to STA 2 1 x 8 9 Upgr
301. you can change this 100 GB location at any time after STA installation see Relocate the STA Logs recommended Ditectory optional on page 3 13 for instructions Note Except for log rotation STA does not perform space management Caution You must configure the STA backup utility to manage the log files in STA_logs db stadb_bin Otherwise these files may require manual management see the STA Administration Guide for details Download the Linux Installer Media Pack Use this procedure to download the Linux installer media pack from the Oracle Software Delivery Cloud website The media pack is delivered as a compressed ISO image file which you can extract and write to portable media of your choice flash drive DVD etc Before performing this task you must obtain an Oracle Software Delivery Cloud user ID and password from your Oracle support representative 1 Start a Web browser and navigate to the Oracle Software Delivery Cloud website http edelivery oracle com linux Click Sign In Register Enter the user ID and password provided by Oracle Support On the Terms amp Restrictions screen select the boxes to indicate your acceptance of the License Agreement and Export Restrictions and then click Continue On the Media Pack Search screen a Inthe Select a Product Pack menu select Oracle Linux b Inthe Platform menu select x86 64 bit STA requires 64 bit Linux c Click Go Select a Linux version and th

for STA - Oracle Documentation

Contents

Download Pdf Manuals

Related Search

Related Contents