Specify Cloud Manager Settings

Before You Begin

This 30-minute tutorial shows you how to access the Cloud Manager instance in a browser and fill out the Cloud Manager settings and infrastructure settings pages.

Background

After you install the Cloud Manager image on an Oracle Cloud Infrastructure instance, you must fill in the settings pages to prepare to use it for provisioning environments.

The method that you use to access the Cloud Manager instance in a browser depends upon the choices that you made when you installed Cloud Manager and the VCN.

If you created Network resources, private subnets, and a bastion, you must create an SSH port forwarding session, and then access the Cloud Manager PIA URL.
See the section Access a Private Cloud Manager Instance with an SSH Port Forwarding Session.
If you created Network resources, public subnets, and a bastion, you must create an SSH port forwarding session, and then access the Cloud Manager PIA URL.
See the section Access the Cloud Manager Instance with an SSH Port Forwarding Session. Alternatively, you can modify the Cloud Manager subnet to allow Internet access.
If you created Network resources, public subnets, and no bastion, you can access the Cloud Manager PIA URL.
Note that when you create Network resources with no bastion, the subnet includes a security rule that allows traffic from the Internet (0.0.0.0/0) to the default PIA TCP ports 8000 and 8443.

See the section Access the Cloud Manager Instance in a Browser.

This is the twelfth tutorial in the Install PeopleSoft Cloud Manager series. Read the tutorials in the order listed. The optional tutorials offer alternate methods for setup.

Step 1: Access the Cloud Manager Instance in a Browser

This section assumes that you have set up the networking resources to allow Internet access to the Cloud Manager instance. If you set up the Cloud Manager instance with private subnets and a bastion, skip this section and follow the instructions in the section Access a Private Cloud Manager Instance with an SSH Port Forwarding Session.

To access Cloud Manager in a browser:

To locate the URL for Cloud Manager, review the /home/opc/bootstrap/CloudManagerStatus.log file created after the successful completion of the Resource Manager Apply job for the Cloud Manager stack.

See the tutorial Log in to the Cloud Manager Instance.

The URLs for Cloud Manager Pure Internet Architecture (PIA) are included at the end of the file. For example:
```
CM installed successfully
Cloud Manager PIA URL: http://psftcm.subnet1.pscmnetwork.oraclevcn.com:8000
Cloud Manager PIA SSL URL: https://psftcm.subnet1.pscmnetwork.oraclevcn.com:8443
```
To access the URL over the Internet, the DNS for the instance must be successfully resolved.

If you do not have a public DNS, edit the etc\hosts file (for example, C:\Windows\System32\drivers\etc\hosts on Microsoft Windows 10) on the machine from which you want to access the Cloud Manager URL. To modify the file, add a line with the Public IP address and fully-qualified domain name for the Cloud Manager instance, such as:
```
198.51.100.67  psftcm.subnet1.pscmnetwork.oraclevcn.com
```
Enter the Cloud Manager URL in a browser. You see a window for Weblogic Application Server.
Click the link Please click here to PeopleSoft logon page to display the Cloud Manager sign-in window.

Description of this illustration (access_cloud_manager_browser_PIAsignin.png)

Note:

Oracle strongly recommends that you change the default PeopleSoft Pure Internet Architecture (PIA) user passwords, especially when the Cloud Manager instances are on the public Internet.

Access a Private Cloud Manager Instance with an SSH Port Forwarding Session

If you created Network resources, private or public subnets, and a bastion as part of the Cloud Manager installation, you must create an SSH port forwarding session to access the Cloud Manager PIA URL. Use these instructions to connect to the Cloud Manager instance in a browser.

For more information on creating and using bastions, see the Oracle Cloud Infrastructure documentation for the Bastion service.

If you set up the Cloud Manager instance to allow Internet access, skip this section and use the instructions in the previous section, Access the Cloud Manager Instance in a Browser.

You must supply an SSH private key in the OpenSSH format for these commands. If you created an SSH private key in PuTTY in the RSA format, convert it to the OpenSSH format, as follows:

Open the PuTTY generator and load the current private key.
Select Conversions > Export OpenSSH key.
Save the file, and make a note of the full path and key name.

Note:
If you want to distinguish this private key from the private key that you use with PuTTY, you can save the file to a different name. You cannot use this version of the key with PuTTY.
Use the newly exported key in the command to create the SOCKS proxy.

To create the bastion SSH port forwarding session:

In the Compute console, click the menu icon at the top left, and select Compute > Instances.
If necessary, select your compartment, and locate the Cloud Manager instance.
Select the Oracle Cloud Agent tab, and verify that the Bastion plugin has been enabled. If it is not enabled, turn it on.
The Resource Manager Apply job for the Cloud Manager instance enables the Bastion plugin by default. If you are using these instructions to access a PeopleSoft provisioned environment, you may need to enable the Bastion plugin. It will take a little time to become active.

Description of this illustration (ssh_access_instance_details_bastion_enabled.png)
Select Resource Manager, then Stacks, and locate the Cloud Manager stack.
On the Stack Details page for the Cloud Manager instance, select the Apply job.
On the Job Details page, select Outputs from the Resources list on the left, and make a note of the bastion name.
Select Identity & Security, then Bastion, and locate the bastion.
If there is no active session, click Create Session.
Select SSH port forwarding session from the Session type drop-down list.
Enter a name for the session, or accept the default.
Select Instance name as the method to connect to the target host (Cloud Manager instance).
If necessary, change the compartment, and select the Cloud Manager instance from the Compute instance drop-down list.
Enter the target port number that you want to connect to, such as port 8000 for the default Cloud Manager PIA URL.

Description of this illustration (create_ssh_port_fwd_session.png)
Alternatively, select the IP address option and enter the private IP address for the Cloud Manager instance.
Supply the public SSH key by browsing to the key file, pasting the text for the key file, or generating a new key pair.
Click Create session.
Wait until the session state is Active. Click the Actions icon and select Copy SSH command.
Paste the command in a text editor, and replace <privateKey> with the full path and key name to the OpenSSH-formatted key.
Replace <localPort> with the port to access the Cloud Manager PIA URL through the bastion.
Supply a port that is greater than 1024 and is not in use by any other process on your system.
In a Bash shell (Linux) or a git bash shell (Microsoft Windows), enter the edited command to create the SSH port forwarding session to the Cloud Manager instance.

If you created a passphrase when generating the private key, you will be prompted to enter it two times. The process does not exit. That is, it does not return to the prompt.

Note:
If you are unable to connect, it may be due to the version of git bash you are using. See the workaround at the end of this section.

Tip:
The session lasts until you close the Bash shell or git bash shell, or until the bastion session ends. If the prompt closes, it means the session has disconnected. By default the session will time out after a few minutes of inactivity. For information on managing bastion sessions, see the Oracle Cloud Infrastructure documentation for the Bastion service.
Edit the etc\hosts file (for example, C:\Windows\System32\drivers\etc\hosts on Microsoft Windows 10) on the machine from which you want to access the Cloud Manager URL.
To modify the file, add a line with the local IP address and fully-qualified domain name for the Cloud Manager instance, such as:
```
127.0.0.1  psftcm.subnet1.pscmnetwork.oraclevcn.com
```
To access Cloud Manager in a browser, modify the PIA URL from the CloudManagerStatus.log:
```
http://psftcm.subnet1.pscmnetwork.oraclevcn.com:8000
```
Replace the port with the <localPort> value you used in the SSH command. For example, if you entered 8888 for the <localPort>:
```
http://psftcm.subnet1.pscmnetwork.oraclevcn.com:8888
```

With some versions of git bash, you may see an error message such as "Unable to negotiate with <port number>" when you enter the command to create the SSH port forwarding session. Use these steps to avoid the error.

Make a note of the bastion host from the SSH command that you copied after creating the session (step 17). In this sample command, it would be the text in bold beginning host.bastion.
```
ssh -i <privateKey> -N -L <localPort>:xx.x.x.xxx:8000 -p 22 ocid1.bastionsession.oc1.iad.xxxxxxxxx@host.bastion.us-ashburn-1.oci.oraclecloud.com
```
In the git-bash shell, change to the user's home directory:
```
$ cd ~
```
Make a new directory called ".ssh" under the home directory:
```
$ mkdir .ssh
```
Change to the .ssh directory.
```
$ cd .ssh
```
Create a file called config; for example using vi or another editor:
```
$ vi config
```
Tip:
Review the usage with vi --help.

Add these contents to the file and save.

Host <bastion host>
User opc
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa

For <bastion host> enter the information from the SSH command; for example:

Host host.bastion.us-ashburn-1.oci.oraclecloud.com
User opc
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa

Enter the SSH command to create the SSH port forwarding session to the Cloud Manager instance.

Alternatively, you can create the .ssh directory and config file in Windows File Explorer before using them in the git-bash shell.

Make a note of the bastion host from the SSH command that you copied after creating the session (step 15). In this sample command, it would be the text in bold.
```
ssh -i <privateKey> -N -L <localPort>:xx.x.x.xxx:8000 -p 22 ocid1.bastionsession.oc1.iad.xxxxxxxxx@host.bastion.us-ashburn-1.oci.oraclecloud.com
```
In the git-bash shell, change to the user's home directory.
```
$ cd ~
```
Determine the user's home directory.
```
$ pwd
```
```
/c/Users/username
```
The path /c/Users/username in the git-bash shell corresponds to C:\Users\username in Windows File Explorer.
In Windows File Explorer, go to C:\Users\username and create the .ssh directory.
Go to the C:\Users\username\.ssh directory.

Using Notepad or another text editor, create the config file with these contents, and save.

Host <bastion host>
User opc
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa

For <bastion host> enter the information from the SSH command; for example:

Host host.bastion.us-ashburn-1.oci.oraclecloud.com
User opc
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa

Go to the git-bash shell and run the SSH command to create the SSH port forwarding session to the Cloud Manager instance.

Step 2: Specify Cloud Manager Settings

Use the Cloud Manager Settings page to specify user IDs and other information before using Cloud Manager to create topologies and templates.

Sign in to Cloud Manager in a browser using the Cloud Administrator user ID and password.
On the home page, select the Cloud Manager Settings tile.

Note that the Cloud Manager Settings tile appears only for users who sign in with the Cloud Administrator user ID.

Description of this illustration (cldmgrsettings_cldmgr_homepage_settingstile.png)
Select Cloud Manager Settings from the left-hand panel if necessary.

Description of this illustration (cldmgrsettings_select_cloud_manager_settings.png)
In the My Oracle Support (MOS) Credentials section, the values that you entered in the Cloud Manager stack input form are used to populate the User ID and password fields. If you change to a different user, the new user's credentials will be used for subsequent environment provisioning.

Note:
If you use the Lift Utility to create and upload DPKs, you can specify this user as the required Oracle Cloud Infrastructure user.
- User ID: Confirm the user ID for the registered My Oracle Support account, or change to another registered user ID.
- Password: Enter the password for the My Oracle Support account.
- Url: This field displays the URL https://updates.oracle.com for access to My Oracle Support. Do not change this value.
- Authorization Mechanism: Accept the default OAuth 2.0, or select Basic Auth.
  This determines which mechanism is used to authorize access to My Oracle Support downloads, for example when downloading to the Repository. Note that choosing OAuth 2.0, which is the recommended mechanism, does not change the way you log in to Cloud Manager or provisioned environments. With Basic Auth, your MOS user account credentials are used for authorization. With OAuth 2.0, the Cloud Manager application is configured with the necessary authorization token.
Description of this illustration (cldmgrsettings_MOSCreds.png)
In the PeopleSoft Credentials section, expand the REST Services section, and verify the delivered Cloud Manager Administrator user name, CLADM, and password. This information is based on the input to the Cloud Manager stack input form.

REST Services refers to the standard Integration Broker REST services that are available in the Cloud Manager instance. These REST services are used internally by Cloud Manager modules to send and receive the results of long-running, asynchronous activities.

Description of this illustration (cldmgrsettings_RESTcreds.png)
Expand the User Credentials section.
The user and passwords listed are based on the input to the Cloud Manager stack configuration variables. If you want to use different values for provisioned environments, you can change them here. See the tutorial Install the PeopleSoft Cloud Manager Stack with Resource Manager.
In the Lift & Shift Container section, the container name is included for information.

Description of this illustration (cldmgrsettings_lascontain.png)
If you want to use COBOL in a provisioned environment, select Visual Cobol 4, Visual Cobol 6, Visual Cobol 7, or Visual Cobol 9 from the Version drop-down list.
Using COBOL for a provisioned environment is optional. If you do choose to use one of the supported Micro Focus Visual COBOL versions, you must use the same version of Visual COBOL for every node in a given provisioned environment. Similarly, if you use the lift and shift process, you must use the same version of Visual COBOL for every node that you provision for the shifted environment.

See the tutorial Prepare to Install PeopleSoft Cloud Manager for information on obtaining the licenses and the PeopleTools releases that are supported for each type of compiler.

Description of this illustration (cldmgrsettings_visualcobolversion.png)
For either Visual COBOL version, select a license type from the drop-down list, and enter the necessary information.
- Authorization code — Enter the code.
- File — Enter the absolute path and license file name.
  The number of characters in the absolute path and license file name must be less than 30.
  
  Upload the license file to the Cloud Manager instance, for example using PSCP. As the root user, copy the file to a convenient location, such as /home/psadm2. Change the file owner to psadm2 so that the file is accessible to psadm2, and save the absolute path.
- Server — Enter the server name.
  For information on setting up a license file server, see the Micro Focus Visual COBOL documentation.
Description of this illustration (cldmgrsettings_visualcobollicense.png)
If you want to add the license information for an additional Visual COBOL compiler version, click the plus button to add another row.
To enable monitoring of provisioned environments using the PeopleSoft Health Center, change the Enable monitoring services switch to Yes.
This is a requirement for the Auto Scaling feature. See the section Data Science Settings Page in PeopleSoft Cloud Manager. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

Description of this illustration (cldmgrsettings_monitoring_services.png)
To enable automatic updating of Cloud Manager pages, accept the default setting, Yes, for the Enable automatic page updates switch.
When this option is set to Yes, Cloud Manager pages display the real-time status of operations. For example, if you perform a PeopleTools Update on a provisioned environment, status changes will be reflected as they occur, in the Provision Task Status page and on the status field on the environment tile.

If you set this option to No, Cloud Manager pages will not be automatically refreshed, and you may need to refresh the browser manually before you can see the status change. You may try setting this option to No if you notice a problem with automatic updates.

Description of this illustration (cldmgrsettings_auto_page_updates.png)
Click Save Settings at the top of the page if you make any changes.

Step 3: Specify Infrastructure Settings

Use the Infrastructure Settings page to verify account, instance, and operating system information.

Select Infrastructure Settings from the left-hand panel.
In the Oracle Cloud Infrastructure Service section, the tenancy, user, and API signing key information that you supplied when provisioning the instance are shown.

Note:
This illustration includes sample text and masking characters. The text you see will vary.

Description of this illustration (infrastruct_settings_tenancy_keys_reg.png)
Verify the following information that you supplied when filling out the Resource Manager stack:
- User name and OCID
- Full path and name for the API Signing Public Key
- Full path and name for the API Signing Private Key
- API Signing Private Key passphrase
- API Version
- Home Region
- Deployment Region
If you want to change the User OCID or API signing keys, see the following section Reset User and API Keys.
In the Object Storage - Bucket area, accept the default name or enter a new name.
You can use the default bucket, cm_default_storage, that Cloud Manager creates in Oracle Cloud Infrastructure Object Storage, or create another bucket and enter the name here. The bucket is required for compare reports generated when upgrading the PeopleTools version of a provisioned environment. See the information on Managing Environments in PeopleSoft Cloud Manager. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

Description of this illustration (infrastruct_settings_obj_stor_bucket.png)
In the Operating System Images section, if you want to select a Linux image from the Oracle Cloud Marketplace, change the Marketplace Image switch to YES and select an image from the Image Version drop-down list.

Description of this illustration (infrastruct_settings_linux_marketplace.png)
If you prepared a custom Linux image, or you created an instance for an Oracle Platform image, change the Marketplace Image switch to NO and enter the OCID for the Linux image.
See the section Choose an Oracle Linux Image in the tutorial Prepare to Install PeopleSoft Cloud Manager.

This example shows the Operating System Images section of the Infrastructure Settings page.

Description of this illustration (infrastruct_settings_os_ocids.png)
In the Operating System Images section, enter the Image OCID for the Microsoft Windows image.

See the section Choose a Microsoft Windows Image in the tutorial Prepare to Install PeopleSoft Cloud Manager.

Note:
When you add a Microsoft Windows node in Cloud Manager, you will enter an administrator password for accessing the VM created from the Microsoft Windows image.
In the Notifications section, change the Enable External Notification switch to Yes if you want to allow users to receive email notifications for these features:
Allow users to receive weekly email notifications of the recommended action for managed environments when using monitoring. See the information on Monitoring in PeopleSoft Cloud Manager. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

Allow end users performing a PeopleTools upgrade to enable report notifications on the Cloud Manager Upgrade PeopleTools page for an environment. This applies to upgrades to PeopleTools 8.60.x. See the information on Upgrading PeopleTools in PeopleSoft Cloud Manager. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

Description of this illustration (infrastruct_settings_notifications.png)
Enter a Topic OCID for the PeopleTools upgrade compare reports and monitoring notification.
A topic in the Oracle Cloud Infrastructure Notification service is defined as "A communication channel for sending messages to the subscriptions in the topic." Subscribers to this topic will receive notifications when compare reports are generated during the PeopleTools upgrade and from the weekly Recommendation Job (ECL_RECOMEND) for managed environments when using monitoring feature. See the Oracle Cloud Infrastructure documentation, Managing Topics.
Click Save and then Refresh OCI Metadata at the top of the page if you make any changes, to refresh the metadata related to the operating system images.
Click OK on the dialog box with "Import of latest Infrastructure data has been initiated."
Wait a few minutes for the data to be refreshed before creating a file server.

This example shows the Operating System Images section with a Linux Marketplace image after the data has been saved and refreshed.

Note:
This illustration includes sample text and masking characters. The text you see will vary.

Description of this illustration (infrastruct_settings_complete.png)
After the OCI metadata is refreshed, you can use the options in the OCI Metadata Refresh Across Region section.
See the information on disaster recovery in PeopleSoft Cloud Manager. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

Description of this illustration (infrastruct_settings_refresh_across_region.png)

Reset User and API Keys (Optional)

Use these instructions if you need to change the Cloud Manager administrator user and the API private key associated to new values. This may be necessary, for example, in case of job or organization changes.

The new Cloud Manager administrator user must possess the same permissions and roles as the previous user. Otherwise, after you add the new user and new key some Cloud Manager features may not work.

Follow the instructions in the tutorial Log in to the Cloud Manager Instance to access the Cloud Manager instance with SSH.
Sign in as user opc, and then change to the psadm2 user; for example:
```
$ sudo su - psadm2
```
Note:
This is one of the default users created as part of the Cloud Manager deployment.
Create an API signing key pair for the new Cloud Manager user, and save it in a directory under /home/psadm2, such as /home/psadm2/new_api_keys.
Make a note of the key names, path, and the passphrase. The new keys should be owned by the psadm2 account.

See Required Keys and OCIDs in the Oracle Cloud Infrastructure Documentation.

Tip:
To avoid confusion with the key pair generated for the existing user, it is probably a good idea to create the API signing keys with a different name.
Add the new API public key to the new user's account in the Oracle Cloud Infrastructure console, as shown in the tutorial Generate API Signing Keys for PeopleSoft Cloud Manager.
In the Cloud Manager instance, change directory to /home/psadm2/psft/data/cloud/ocihome/keys.
```
$ cd /home/psadm2/psft/data/cloud/ocihome/keys
```

Make a backup copy of the directory; for example:

$ cp -r /home/psadm2/psft/data/cloud/ocihome/keys ./keys_backup

On the Cloud Manager Infrastructure Settings page, replace the User OCID with that for the new user.
Replace the API Signing Private Key with the full path and name for the new private key.
Replace the API Signing Prv Key Passphrase with the value for the new key, if you specified one.
Click Save.
Cloud Manager validates the values. If the validation is successful, it displays updated values for the API Public Signing Key and Fingerprint.
Click Refresh OCI Metadata.

Reset API Keys (Optional)

Use these instructions to change only the API signing keys, but not the user, for example to conform to a routine update for security reasons. In this case, skip the step to add the User OCID to the Infrastructure Settings page, and add the new API public key to the existing user's account.

Follow the instructions in the tutorial Log in to the Cloud Manager Instance to access the Cloud Manager instance with SSH.
Sign in as user opc, and then change to the psadm2 user; for example:
```
$ sudo su - psadm2
```
Note:
This is one of the default users created as part of the Cloud Manager deployment.
Create a new API signing key pair for the existing Cloud Manager user, and save it in a directory under /home/psadm2, such as /home/psadm2/new_api_keys.
Make a note of the key names, path, and the passphrase. The new keys should be owned by the psadm2 account.

See Required Keys and OCIDs in the Oracle Cloud Infrastructure Documentation.

Tip:
To avoid confusion with the key pair generated for the existing user, it is probably a good idea to create the API signing keys with a different name.
Add the new API public key to the user's account in the Oracle Cloud Infrastructure console, as shown in the tutorial Generate API Signing Keys for PeopleSoft Cloud Manager.
In the Cloud Manager instance, change directory to /home/psadm2/psft/data/cloud/ocihome/keys.
```
$ cd /home/psadm2/psft/data/cloud/ocihome/keys
```

Make a backup copy of the directory; for example:

$ cp -r /home/psadm2/psft/data/cloud/ocihome/keys ./keys_backup

Replace the API Signing Private Key with the full path and name for the new private key.
Replace the API Signing Prv Key Passphrase with the value for the new key, if you specified one.
Click Save.
Cloud Manager validates the values. If the validation is successful, it displays updated values for the API Public Signing Key and Fingerprint.
Click Refresh OCI Metadata.

Enter an SSH Public Key for Provisioned Environments

End users can enter or edit their public SSH key on the My Settings page. After adding this SSH key, Cloud Manager will inject the key into the Linux VM of any PeopleSoft environment that you provision. End users can then use Putty or other interfaces to access the provisioned environments, for example to use PSADMIN.

From the Cloud Manager home page, click the My Settings tile.

Description of this illustration (cldmgr_homepage_mysettings.png)
If necessary, select My SSH Public Key from the frame on the left.

Description of this illustration (mysettings_select_mysshpublickey.png)
To enter a new SSH Public key, enter the text in the My SSH Publish Key field and click Save.

Description of this illustration (mysettings_ssh_public_key_save.png)
To edit or replace an existing key, enter the text for the key, and then click Save.
Click Edit, and change or replace the text.
Click Save again.

Create a Password Group for Provisioned Environments

Use password groups to organize passwords saved in an Oracle Cloud Infrastructure vault. For example, you may want a group for your PUM environments using database compute, and another for environments that use Database as a Service.

See the tutorial Create Vault Resources for Password Management for PeopleSoft Cloud Manager.

See the information on password groups in PeopleSoft Cloud Manager on Oracle Help Center. Select the PeopleSoft Cloud Manager page on the Oracle Help Center.

To create a password group:

From the Cloud Manager home page, click the My Settings tile.
Select Password Groups from the frame on the left.
Click Add New Group.

Description of this illustration (mysettings_add_password_group.png)
Select the compartment and OCI vault, and choose a vault secret for each password.

Description of this illustration (mysettings_password_group_page.png)

Next Steps

Use File Storage Service for PeopleSoft Cloud Manager Repository

Learn More

PeopleSoft Cloud Manager Home Page, My Oracle Support, Doc ID 2231255.2
Cumulative Feature Overview Tool (Click Generate a CFO report and select PeopleSoft Cloud Manager at the top.)
Oracle Cloud Documentation in Oracle Help Center

Title and Copyright Information

Specify Cloud Manager Settings

F26265-10

July 2024

Access the Cloud Manager instance in a browser and fill out the Cloud Manager settings and infrastructure settings pages.

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.

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 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" or "commercial computer software documentation" 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 and Java 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.