Installation Guide
Release 13.3.0.1
E55188-09
July 2023
This document explains the installation procedures for the Oracle Application Testing Suite.
Caution:
The machines where the OpenScript product is installed should be strictly used for testing. The security features of the browsers have been disabled on this machine to enable recording and playback operations. The browsers cannot be used for secure browsing.
Note:
The user should have privileges to create, remove, and change files in all subdirectories of JREs.
For example, C:\program files\java\jre and its subdirectory or subdirectories.
If you have any questions or problems, please contact our support group at https://www.oracle.com/support/.
This section explains the procedure for installing Oracle Application Testing Suite on Windows machines.
The Oracle Application Testing Suite installer requires a working instance of Oracle XE or Oracle EE database, before installing the Oracle Application Testing Suite server components. This database instance can either be on the system where the application is being installed or in a server accessible via the network.
Note:
See the Oracle® Database Installation Guide in the Oracle Database Documentation Library for additional information about installing Oracle database.
https://www.oracle.com/enterprise-manager/downloads/oats-downloads.html,
Select and download the Oracle Application Testing Suite zip file(s) from the website and save it to a temporary directory on your hard disk.
oats-win64-version.zip contains all the components of OATS for Windows bundled along with JDK and Web Logic Server. Components of Application Testing Suite include OracleATSHelperService, OracleATSAgent. OpenScript, OracleTestManager, OracleLoadTesting.
Note:
Master password should be alphanumeric and should contain at least 1 upper case character, 1 lower case character and length should be between 8 to 20 characters.
There are two ways to uninstall Oracle Application Testing Suite:
<OATS_HOME>\Uninstall.bat or Select Uninstall OracleATSHome from the Start menu. This would open the uninstallation wizarddeinstall.cmd -silent
Oracle Application Testing Suite server components (Oracle Load Test/Oracle Test Manager) and Agent components (Oracle Load Test agent/Data Collector) can be installed on Linux via a separate installer; however Oracle OpenScript is Windows only. Oracle Application Testing Suite components have been tested with Oracle Enterprise Linux 8 64 bit. Note that some Data Sources (Perfmon, Ping and COM+) cannot be used on a Linux Data Collector.
The Oracle Application Testing Suite Linux installer is based on the Oracle Universal Installer (OUI) which requires UI based access. To install the Oracle Application Testing Suite server components on Linux you will need to access XTerm. XTerm, most typically, can be accessed over VNC.
The Oracle Application Testing Suite installer requires a working instance of Oracle XE or Oracle EE database, before installing the Oracle Application Testing Suite server components. This database instance can either be on the system where the application is being installed or in a server accessible via the network.
Note:
See the Oracle® Database Installation Guide in the Oracle Database Documentation Library for additional information about installing Oracle database.
https://www.oracle.com/enterprise-manager/downloads/oats-downloads.html
Select and download the Oracle Application Testing Suite zip file(s) from the web site and save it to a temporary directory on your hard disk.
oats-linux64-version.zip: Contains all the components of OATS bundled along with JDK and Web Logic Server. Components of OATS include OracleATSHelperService, OracleATSAgent, OracleTestManager, OracleLoadTesting.
chmod -R 755 *
Run the setup.sh through a terminal. After the basic prerequisite system check, this would launch the installer wizard.
Note:
Master password should be alphanumeric and should contain at least 1 upper case character, 1 lower case character and length should be between 8 to 20 characters.
sudo sh <OATS_HOME>/root.sh
Enter the master password, when prompted.
http://<linux-host-name>:8088/ to verify if the installation was successful and to start using the OATS application.This section provides basic troubleshooting tips for Linux installation issues.
If the OATS service does not restart, try removing the OracleATSServer PID file. If the service stopped abnormally or the installation failed, this file may prevent subsequent installs of the service from succeeding. Use the following command:
sudo rm /var/run/OracleATSServer.pid
This section lists how to start Oracle Application Testing Suite applications and utilities on Linux machines. It also lists how to restart and stop the application service.
To start the Oracle Application Testing Suite Administrator:
http://<machine>:8088/admin or http://localhost:8088/admin
To start the Oracle Test Manager application:
http://<machine>:8088/otm or http://localhost:8088/otm
To start the Oracle Load Testing application:
http://<machine>:8088/olt or http://localhost:8088/olt
To start the Database Configuration utility:
<installdir>/bin/DbConfig.sh
To start the Oracle Load Testing Agent Authentication Manager utility:
<installdir>/jdk/jre/bin/java -jar <installdir>/agentmanager/AMAuthManager.jar
To restart the Oracle Application Testing Suite service:
<installdir>/bin/restartSvc.sh [OracleATSServer|OracleATSAgent]
To stop the Oracle Application Testing Suite service:
<installdir>/bin/stopSvc.sh [OracleATSServer|OracleATSAgent]
To create a support package for troubleshooting purposes (OATSSupport.zip):
<installdir>/bin/oats_support.sh Oracle Application Testing Suite can be uninstalled in two modes:
uninstall.sh file to start the GUI uninstallation for the Oracle Application Testing Suite.
sh <OATS_HOME>/uninstall.sh
deinstall.sh by passing an additional flag -silent
sh <OATS_HOME>/bin/deinstall.sh -silent
Note:
Make sure to stop the services before starting the uninstallation process
Oracle Load Testing allows you to distribute your Virtual Users to run from remote Agent machines. The Oracle Load Testing Server will connect to Oracle Load Testing Agent systems to start and run your Virtual Users on those machines. The Oracle Application Testing Suite Remote Agent is a component of the Oracle Application Testing Suite installation that enables Virtual Users to be distributed to these Agent systems. Users can either install the full Oracle Application Testing Suite installation or just the Remote Agent install component on their Agent machines to enable this functionality.
To install the Remote agent:
https://www.oracle.com/enterprise-manager/downloads/oats-downloads.html, download the appropriate installer for your environment
To specify the user login for the Oracle Load Testing Agent Service, open the Services control panel on the Agent machine and change the login credentials for the "Oracle Load Testing Agent Service". By default, the Oracle Load Testing Agent Service will run under the Local System account.
Once you have the Oracle Load Testing Server and Agent software installed on the individual systems, you should verify network access between the Oracle Load Testing Server system and each Remote Agent system. This section provides basic tips and techniques to make sure the Oracle Load Testing Server system can successfully communicate with each Remote Agent system.
Make sure that you have the Oracle Load Testing Agent software loaded on the Agent system(s) and that it is the same version as the Oracle Application Testing Suite software that is loaded on the Oracle Load Testing Server system. The systems you plan to use as Agents must have either the Oracle Load Testing Agent software or the full Oracle Application Testing Suite installed to work as agents.
Make sure you can successfully Ping all of the Agent systems from the Oracle Load Testing Server system. The machine names you use to Ping the systems are the same names that you will specify for the Agent systems in the Oracle Load Testing server. You can also use the IP addresses of the agent systems. If you cannot successfully Ping the Agent systems, contact your network administrator to resolve the issue. If you cannot Ping the Agent systems from the Oracle Load Testing Server system, you will not be able to run the Agents from the server.
Make sure that the same user is logged in on both the Oracle Load Testing server system and all of the Agent systems. All of the Agent systems must have a user logged in to be controlled by the Oracle Load Testing Server system. You may be able to log in as a different user on the Agent systems as long as the user login has the same administrative privileges as the user logged in on the server system.
From the server system, try mapping a drive on each of the Agent systems using Windows Explorer. Depending on how your network is setup, the server system may not be allowed to start up processes on the Agent systems. The easiest way around this is to map a drive to the Agent system in order to authenticate with Windows.
In the Oracle Load Testing server add a script to the Scenario Profiles list. Enter the machine name or IP address of the Agent system where you want to run the script into the Systems Manager and select that machine in the Systems field on the Build Scenario tab of Oracle Load Testing.
In some cases, you may want to prepare a system for "Clean" installation of the Oracle Application Testing Suite product. This may be required in the following cases:
The following sections provide step-by-step instructions to perform a clean installation of the Oracle Application Testing Suite product on your system.
Make sure to backup all scripts and databases before proceeding.
This section explains how to do a clean installation in Windows machine
To perform a silent uninstallation, navigate to <OATS_HOME>/oui/bin in a command window and enter the command
deinstall.cmd -silent
To remove or rename installation folders:
If you plan to perform an OpenScript only install after removing the Oracle Application Testing Suite applications, you must also remove the OATS_HOME environment variable and the browserHelper.properties file to prepare the machine for the installation.
To remove the OATS_HOME environment variable:
To remove the browserHelper.properties file:
To remove Oracle Application Testing Suite services:
cmd and click OK.sc delete servicename, where servicename is each of the following:
OracleATSAgentOracleATSServerOracleATSHelperIf the message "The specified services does not exist as an installed services" is returned from the program, the service was successfully removed by the previous steps.
To remove Oracle Application Testing Suite Registry keys:
regedit and click OK.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleATSServerHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleATSAgentHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleATSHelperIf you do not find the keys in the Registry, they were successfully removed by the previous steps. Note: The keys may be found in the different location depends on your Operating System (search by the key to find the correct location).
While not required, it is considered to be a good practice to restart the system after uninstalling applications.
Select Shutdown from the Start menu, then select Restart.
To install Oracle Application Testing Suite, follow the installation instructions: Installing the Applications on Windows Machines
This section explains how to do a clean installation in Linux machine
To perform a silent uninstallation, navigate to <OATS_HOME>/oui/bin in a terminal and enter the command
deinstall.cmd -silent
To remove or rename installation folders:
To remove Oracle Application Testing Suite services:
systemctl | grep OracleATS
If you don't find any services listed, then they were successfully removed by the previous steps.
systemctl stop OracleATSHelper
systemctl stop OracleATSAgent
systemctl stop OracleATSServer
Note:
To remove a service, you will need to have root privileges.systemctl reset-failed
While not required, it is considered to be a good practice to restart the system after uninstalling applications.
sudo shutdown -r
To install Oracle Application Testing Suite, follow the installation instructions: Installing the Applications on Linux Machines
Oracle Application Testing Suite uses the Oracle Universal Installer application to perform the installation of the server, agent and OpenScript. You can use the Silent installation feature of the Oracle Universal Installer to install the Oracle Application Testing Suite without using the GUI.
This section provides basic instructions for installing Oracle Application Testing Suite using the silent installation.
Note:
See the Oracle Universal Installer (OUI) User's Guide in the Oracle Help Center library for additional information about using the Oracle Universal Installer in silent mode
To use the Silent install, you will need to create or customize a batch file to run the setup program with the appropriate arguments and a corresponding Response File to provide inputs during the installation process.
Generation the Response File
The easiest way to generate a response file is by recording a GUI installation. This can be done by the following steps:
-record -destinationFile C:\oats_install_temp\oats.rsp)This will generate the response file called oats.rsp in the directory C:\oats_install_temp.
Silent Installation
To silently install Oracle Application Testing Suite on Windows, run the following command:
./jdk/bin/java -jar OATS_win64_13.3.0.1.jar ORACLE_HOME=C:\OracleATS -nowait -silent -responseFile C:\oats_install_temp\oats.rsp
This section shows the procedures for Oracle Application Testing Suite silent installation on Linux.
Generating the Response File
The easiest way to generate a response file is by recording a GUI installation. This can be done by the following steps:
This will generate the response file called oats.rsp in the directory /tmp.
Silent Installation
To silently install Oracle Application Testing Suite on Linux, run the following command:
./jdk/bin/java -jar OATS_linux64_13.3.0.1.jar ORACLE_HOME=/scratch/app/OracleATS -nowait -silent -responseFile /tmp/oats.rsp
The following is an example Response file (.rsp) that shows the settings for Oracle Application Testing Suite silent installation.
The following is an example Response file (.rsp) that shows the settings for Oracle Application Testing Suite silent installation.
####################################################################
## Copyright (c) 1999, 2023 Oracle. All rights reserved. ##
## ##
## Specify values for the variables listed below to customize ##
## your installation. ##
## ##
## Each variable is associated with a comment. The comment ##
## identifies the variable type. ##
## ##
## Please specify the values in the following format: ##
## ##
## Type Example ##
## String "Sample Value" ##
## Boolean True or False ##
## Number 1000 ##
## StringList {"String value 1","String Value 2"} ##
## ##
## The values that are given as <Value Required> need to be ##
## specified for a silent installation to be successful. ##
## ##
## ##
## This response file is generated by Oracle Software ##
## Packager. ##
####################################################################
#[INSTALLER VARIABLES]
#-------------------------------------------------------------------------------
#Name : ACCEPT_LICENSE_AGREEMENT
#Datatype : Boolean
#Description: By setting this variable to true, you are accepting the license
agreement. This variable is used only for silent installations.
#Example: ACCEPT_LICENSE_AGREEMENT = true
#-------------------------------------------------------------------------------
ACCEPT_LICENSE_AGREEMENT=true
COLLECTOR_IGNORE_CONFIGURATION=false
COLLECTOR_IGNORE_FAILURES=false
COLLECTOR_UPGRADE=false
COLLECTOR_USE_OBFUSCATED_PASSWORDS=false
CRS=false
DECLINE_AUTO_UPDATES=false
DECLINE_SECURITY_UPDATES=false
FROM_LOCATION=" "
FROM_LOCATION_CD_LABEL="CD Label"
INSTALL_TYPE="Complete"
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=true
#-------------------------------------------------------------------------------
#Name : ORACLE_HOME
#Datatype : String
#Description: Complete path of the Oracle Home.
#Example: ORACLE_HOME="C:\OracleATS"
#-------------------------------------------------------------------------------
ORACLE_HOME="C:\OracleATS"
RESTART_REMOTE_SYSTEM=false
RESTART_SYSTEM=false
ROOTSH_STATUS=0
SECURITY_UPDATES_VIA_METALINK=false
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
SELECTED_LANGUAGES={ALL_LOCALES}
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CONFIG_TOOL_PAGE=true
SHOW_CUSTOM_TREE_PAGE=false
#-------------------------------------------------------------------------------
#Name : SHOW_DEINSTALL_CONFIRMATION
#Datatype : Boolean
#Description: Set to true if deinstall confimation is needed during a deinstall
session.
#Example: SHOW_DEINSTALL_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_CONFIRMATION=true
#-------------------------------------------------------------------------------
#Name : SHOW_DEINSTALL_PROGRESS
#Datatype : Boolean
#Description: Set to true if deinstall progress is needed during a deinstall
session.
#Example: SHOW_DEINSTALL_PROGRESS = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_PROGRESS=true
SHOW_END_OF_INSTALL_MSGS=true
SHOW_END_SESSION_PAGE=true
SHOW_EXIT_CONFIRMATION=true
SHOW_INSTALL_PROGRESS_PAGE=true
SHOW_NEXT_SESSION_PROGRESS=false
SHOW_NODE_SELECTION_PAGE=false
SHOW_RELEASE_NOTES=true
SHOW_REQUIRED_CONFIG_TOOL_PAGE=true
#-------------------------------------------------------------------------------
#Name : SHOW_ROOTSH_CONFIRMATION
#Datatype : Boolean
#Description: Set to true if the Confirmation dialog asking to run the root.sh
script in OUI needs to be shown.
#Valid only for Unix platforms.
#Example: SHOW_ROOTSH_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_ROOTSH_CONFIRMATION=true
SHOW_SUMMARY_PAGE=true
SHOW_WELCOME_PAGE=false
SHOW_XML_PREREQ_PAGE=true
SUPPRESS_BUGLIST_WARNING=false
UMASK="install"
UNZIP_LOCATION="install"
USE_OLD_INSTALL_PREREQS=false
USE_PREREQ_CHECKER=false
#[PRODUCT VARIABLES]
#-------------------------------------------------------------------------------
# Name : DBCONECTION_TYPE
# Datatype : Boolean
# Description: Database connection to be used for installation.
# Valid values are new, existing and manual
# Example: DBCONECTION_TYPE="existing"
#-------------------------------------------------------------------------------
DBCONECTION_TYPE=""
#-------------------------------------------------------------------------------
# Name : DB_HOST_NAME
# Datatype : Boolean
# Description: Database hostname
# Valid values are new, existing and manual
# Example: DB_HOST_NAME="localhost"
#-------------------------------------------------------------------------------
DB_HOST_NAME=""
#-------------------------------------------------------------------------------
# Name : DB_PASSWORD
# Datatype : String
# Description: Database password.
# Example: DB_PASSWORD="MyDatabasePassword"
#-------------------------------------------------------------------------------
DB_PASSWORD=""
#-------------------------------------------------------------------------------
# Name : DB_PORT
# Datatype : Number
# Description: Database Port
# Example: DB_PORT="1521"
#-------------------------------------------------------------------------------
DB_PORT=""
#-------------------------------------------------------------------------------
# Name : DB_USER
# Datatype : String
# Description: Database username
# Example: DB_USER="system"
#-------------------------------------------------------------------------------
DB_USER=""
#-------------------------------------------------------------------------------
# Name : MASTER_PASSWORD
# Datatype : String
# Description: Oracle Application Testing Suite Master Password
# Password Criteria: Alphanumeric with at least 1 uppercase and 1 lowercase
# character. Length between 8 - 20 characters
# Example: MASTER_PASSWORD="MyMasterPassword"
#-------------------------------------------------------------------------------
MASTER_PASSWORD=""
#-------------------------------------------------------------------------------
# Name : OATS_DB_PASSWD
# Datatype : String
# Description: Database password for OATS schema
# Example: DBCONECTION_TYPE="MyOatsPassword"
#-------------------------------------------------------------------------------
OATS_DB_PASSWD=""
#-------------------------------------------------------------------------------
# Name : OATS_DB_USER
# Datatype : String
# Description: Database username for OATS schema
# Example: OATS_DB_USER="oats"
#-------------------------------------------------------------------------------
OATS_DB_USER=""
#-------------------------------------------------------------------------------
# Name : OLT_DB_PASSWD
# Datatype : String
# Description: Database password for OLT schema
# Example: OLT_DB_PASSWD="MyOltPassword"
#-------------------------------------------------------------------------------
OLT_DB_PASSWD=""
#-------------------------------------------------------------------------------
# Name : OLT_DB_USER
# Datatype : String
# Description: Database username for OLT schema
# Example: OLT_DB_USER="olt"
#-------------------------------------------------------------------------------
OLT_DB_USER=""
#-------------------------------------------------------------------------------
# Name : OTM_DB_PASSWD
# Datatype : String
# Description: Database password for OTM schema
# Example: OTM_DB_PASSWD="MyOtmPassword"
#-------------------------------------------------------------------------------
OTM_DB_PASSWD=""
#-------------------------------------------------------------------------------
# Name : OTM_DB_USER
# Datatype : String
# Description: Database username for OTM schema
# Example: OTM_DB_USER="otm"
#-------------------------------------------------------------------------------
OTM_DB_USER=""
#-------------------------------------------------------------------------------
# Name : SID_SERVICE_ID
# Datatype : String
# Description: Service name for the Database connection
# Example: SID_SERVICE_ID="orcl"
#-------------------------------------------------------------------------------
SID_SERVICE_ID=""The procedure for upgrading an existing Oracle Application Testing Suite components instance is similar to a fresh installation. The exceptions are that the existing Oracle Application Testing Suite services need to be stopped before proceeding and certain system configuration files may be reverted before continuing the upgrade procedure.
The setup.sh script handles the stopping and removal of the service Oracle Application Testing Suite services after providing a notice. The setup.sh script also handles reverting system configuration files.
Caution:
The Uninstall procedure will revert system configuration files made by the previous Oracle Application Testing Suite agent installation. Changes made to these files by other applications (installed after the previous Oracle Application Testing Suite Agent) may get reverted.
If you have installed other applications after the previous Oracle Application Testing Suite Agent installation, you may want to make backup copies of the system configuration files before proceeding with the Oracle Application Testing Suite upgrade procedure.
To upgrade Oracle Application Testing Suite components:
setup.bat for Windows or setup.sh for Linux to start the upgrade installation. This will open the installation wizard.The Reset Password utility allows the installing user of the Oracle Application Testing Suite web applications to reset the password for the Administrator account in an Oracle Load Testing or Oracle Test Manager database.
The installing user of the Oracle Application Testing Suite can reset the password for:
The default Administrator user password is the master password specified during the Oracle Application Testing Suite installation.
You run the Reset Password utility using the command line Java file ResetPassword.jar located in the \lib directory under the installation directory.
The Reset Password utility is run from a command prompt.
Note:
This operation requires elevated access from the command line. You could run this as Administrator in Windows or with root privileges in Linux
The following procedure resets the Administrator user password for the Oracle Load Testing database. This procedure can only be performed by the user who installed the Oracle Application Testing Suite on the system.
To reset the Administrator user password for an Oracle Load Testing database connection:
Select Run from the Start menu.
Type cmd and press Enter.
Type cd \installdir\lib where installdir is the installation directory for the Oracle Application Testing Suite. The default is c:\OracleATS.
Type $installdir\jdk\bin\java.exe -jar ResetPassword.jar -olt "DB Name" at the command prompt. $installdir is the actual installation directory path. For example, the default installation directory is c:\OracleATS. DB Name is the database connection name. For example the default installation database connection name for Oracle Load Testing is Default OLT Database. The following command shows a complete example using the default values:
c:\OracleATS\jdk\bin\java.exe -jar ResetPassword.jar -olt "Default OLT Database"
Press Enter.
Type the new password and press Enter.
Note:
The password must start with alphabetic character, be a minimum of 8 characters in length, include at least one number and not contain any spaces. These are the same restrictions enforced during product installation.
Type the confirm password and press Enter.
Close the command window.
The following procedure resets the Administrator user password for the Oracle Test Manager database. This procedure can only be performed by the user who installed the Oracle Application Testing Suite on the system.
To reset the Administrator user password for an Oracle Test Manager database connection:
Select Run from the Start menu.
Type cmd and press Enter.
Type cd \installdir\lib where installdir is the installation directory for the Oracle Application Testing Suite. The default is c:\OracelATS.
Type $installdir\jdk\bin\java.exe -Djava.library.path=$installdir\oats\lib -jar ResetPassword.jar -otm "DB Name" at the command prompt. $installdir is the actual installation directory path. For example, the default installation directory is c:\OracleATS. DB Name is the database connection name. For example the default installation database connection name for Oracle Test Manager database is OATS_otm_DS. The following command shows a complete example using the default values:
c:\OracleATS\jdk\bin\java.exe -java.library.path=c:\OracleATS\oats\lib -jar ResetPassword.jar -otm "OATS_otm_DS"
Press Enter.
Type the new password and press Enter.
Note:
The password must start with alphabetic character, be a minimum of 8 characters in length, include at least one number and not contain any spaces. These are the same restrictions enforced during product installation.
Type the confirm password and press Enter.
The Reset Password utility has the following command line option flags:
| Flag | Description |
|---|---|
|
|
|
|
|
|
|
|
Displays Reset Password utility usage information and exits. |
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&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&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Application Testing Suite Installation Guide, Release 13.3.0.1
E55188-09
Copyright © 1997, 2023, Oracle and/or its affiliates.
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, software documentation, data (as defined in the Federal Acquisition Regulation), 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 embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. 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®, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside 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, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro 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.