UTA 6.0.0.2.0 - Installing the Product

The installation of an on-premise version of Utilities Testing Accelerator has been improved upon in both versions 6.0.0.1.0 and 6.0.0.2.0 to allow customers to quickly establish product environments. This article is a summary of this process, which is also outlined in the Oracle Utilities Testing Accelerator installation Guides.

Before installing there are a number of prerequisites necessary for the installation:

• Database. The database to house the UTA objects must be available and accessible to the server you want to install UTA upon. This an be local or remote and can be a separate schema or a PDB in the same location as the Oracle Utilities product. UTA supports the UTA repository as a seperate schema existing on a PDB or non-PDB database or even as a separate PDB on the Multi-tenant database. It does not require any database access to the Oracle Utilities products it is being used against.
• Java. The Java JDK or JRE must be installed on the machine that will house UTA. A Java support license is included with all Oracle products including Oracle Utilities Testing Accelerator.
• XWindows. The Oracle installer used by the Oracle Utilities Testing Accelerator uses XWindows. This is the same installer used by Oracle Database and Oracle WebLogic and a host of other Oracle products so staff familiar with those products will be familiar with the installer.

Note:XWindows is supported natively or via virtualization such as VNC.

The Oracle Utilities Testing Accelerator is available for on-premise customers from Oracle Software Delivery Cloud and includes the documentation and software:

After downloading the software from Oracle Software Delivery Cloud, the following steps are performed:

• Create Database Resources. Create the UTA schema user (UTA) and tablespaces in the database to house the UTA Repository objects using the database tool of your choice as per the installation guide. The installation guide outlines the minimum setup for UTA. Alter as your site standards. Remember the database settings used as the installer will ask you for them later.

Note:The SQL below are examples only and can be altered to suit site standards.

Database ResourceExample SQLData Tablespace CREATE TABLESPACE uta_data DATAFILE '' SIZE 500M AUTOEXTEND ON NEXT 200M MAXSIZE 1024M DEFAULT STORAGE ( INITIAL 10M NEXT 1M pctincrease 10 ) permanent online logging; where <datafile> is the location and filename in Oracle database to store the Oracle Utilities Testing Accelerator repository. Index Tablespace CREATE TABLESPACE uta_idx DATAFILE '' SIZE 250M AUTOEXTEND ON NEXT 50M MAXSIZE 512M DEFAULT STORAGE (INITIAL 10M NEXT 1M PCTINCREASE 10) PERMANENT ONLINE LOGGING; where <indexfile> is the location and filename in Oracle database to store the Oracle Utilities Testing Accelerator repository.

• Execute the Installer. Within XWindows as an appropriate user (usually the same user used to install Oracle Utilities products), execute the installer command. If this command fails, examine the logs and correct the error. The command to start the installer is as follows:

java -jar UTA_6.0.0.2.0_generic.jar

• The Welcome Page is displayed outlining the steps that the installer will follow. Click Next to start the process. For example:

• Inventory Location. As per Oracle products provide the location of the Inventory directory and the group used for the installer. This will default to the group used by the user that initiated the install but can be altered to a group you desire. Click Next after providing the information. For example:

• Installation Location. Provide the directory you want to install the product into. This is effectively the UTA home directory. Click Next after specifying a location. For example:

• Java Home and Application Details. Provide the following information as requested by the installer:
  • Java Home. Home location of the java JDK/JRE for use with Oracle Utilities Testing Accelerator. This will default to the location used for the installer but may reference other java installations if required.
  • Application Server Port. The port number to be used by the Oracle Utilities Testing Accelerator. Default: 8082.
  • Application Administrator User Name. The default user for the administrator. This is the initial user used to create other users. Default: system
  • Application Administrator User Password. The password (and confirmation password) for the Application Administrator User Name.

Note: This is NOT the database system user. It is a user defined to the Utilities Testing Accelerator product.

Click Next after specifying the information.

• Application Keystore Details. As with all Oracle products, the Oracle Utilities Testing Accelerator is installed in secure by default mode. For this to occur a default keystore needs to be generated as part of the process. The information provided generates a unique key used by UTA for communications and encrpytion. Therefore the following information, used by the keytool utility for X.500 generation, via the RFC1779 standard, needs to be provided.
  • Common Name. Name of the organization, machine name (for machine scoped installs) or company root website name. For example: utility.com
  • Organization Unit. Name of Unit associated with use of Utilities Testing Accelerator.
  • Organization Name. Name of company (not web site name)
  • City. Name of Suburb or city.
  • State. Name of State
  • Country Code. The ISO-3166 2 character country code. Default: US (for USA). For other codes, refer to the ISO standard.
  • Keystore Password. Password (and confirmation) to secure keystore. This is used by the product to access the keystore.

Note: It is possible to replace the keystore after installation if your site has a company keystore. Refer to the UTA documentation for post installation steps on how to replace the default keystore and use advanced keystore attributes.

Click Next after specifying the information.

• Target Database Connection Details. Provide the details of the database you want to use for the installation of the UTA Repository. The following information needs to be provided:
  • Database Host. The host name housing the database to house the UTA Repository.
  • Database Port. The listener port number of the database to house the UTA Repository.
  • Database Service Name. The PDB name or database service name of the database to house the UTA Repository.
  • Database Administrator User Name. The DBA user to be used to install the UTA Repository objects. This user MUST have DBA access to create the objects.
  • Database Administrator Password. The associated password (and confirmation) for the DBA user.
  • Application Database Schema Password. The password (and confirmation) for the UTA schema user created in the prerequisite steps.

Click Next after specifying the information.

• Installation Summary. A summary of the information provided is presented prior to executing the Installation. Click Install to start the installation. For example:

• Installation Progress. The installation will be visually shown with progress. If any steps error refer to the log outlined in the previous step. Correct and restart. An example of the Installation Progress is shown below.

• Installation Complete. A dialog will link to the success or failure of the installation process with a link to the log (if desired). Click Finish to close the installer. For example:

After finishing the install it is possible to start UTA using the following commands:

• Navigate to the home directory specified on Page 3 of the installation (Oracle Home) as the user that installed UTA.
• Use the ./startUTA.sh command to start UTA.

Manual Post Installation Steps

The default certificate generated by the installation is limited in its use. It can be replaced or changed using the following process:

• After logging into UTA use the browser to view and export the certificate to your local drive. For example:

• Alter the certificate as necessary using your sites preferred certificate editor.
• Copy the file to the UTA server and execute the following command to set the certificate:

keytool -import -alias <aliasname> -keystore <certificate store location> -file <certificate location>

Where

• <aliasname> - The alias in the keystore to replace. For UTA this value is typically uta
• <certificate store location> - The store location which is the UTA home directory and keystore name utaKeystore.jks
• <certificate location> - The location of the file you altered.

Note: You will be prompted for the keystore password when executing this command.

Note: Other Cacerts can be found in your JDK location under $JAVA_HOME/jre/lib/security subdirectory.

Common Operations

The following commands are available from the UTA home directory.

CommandOperation ./startUTA.sh Starts the Utilities Testing Accelerator ./stopUTA.sh Stops the Utilities Testing Accelerator ./startUTARuntimeExectutor.sh Starts the Server Execution Engine ./stopUTARuntimeExectutor.sh Stop the Server Execution Engine UTA Eclipse Client

Note: Use of this client is optional as the Server execution is the preferred method of execution.

The UTA Eclipse client is located in the UTA Home directory and is named UTA_Client.zip. Download it from this location and refer to the installation guide for additional instructions for sites wanting to use this client.