Common Tasks for Oracle E-Business Suite on Oracle Cloud Infrastructure Classic


Options



Before You Begin

Purpose

This tutorial describes how to perform the following common tasks:

  • Connect to your Oracle Cloud instance via Secure Shell (SSH)
  • Set up Secure Shell between nodes
  • Determine the cloud service account details that you will need to know
  • Change account passwords for Oracle WebLogic Server Administrator and Oracle E-Business Suite
  • Reconfigure environment with new private IP after a VM reboot
  • Manage Ksplice/Uptrack actions
  • Back up and restore the provisioning virtual machine (VM) - also called the EBS Cloud Admin Tool VM

The document is a supplement to the other Oracle by Example tutorials for Oracle E-Business Suite in the learning library for Oracle Cloud Infrastructure Compute Classic.

What Do You Need?

To perform the steps in this tutorial, you must have:

Connect to Your Oracle Cloud Instance Via Secure Shell (SSH)

After you have provisioned an Oracle Compute Cloud Service instance and enabled it for SSH, you will log in to the instance to perform additional tasks such as stopping and starting services, and applying patches. The next two subsections show how you can log in from UNIX and Windows hosts respectively.

Note: If you do not know the public IP address of your instance, you can find it by going to the Instances tab on the Oracle Compute Cloud Service console or by navigating to Compute > Instances tab of the Oracle Cloud Infrastructure console. From there, select your instance to find the public IP address on the Details page.

Logging in From a UNIX Host

  1. On a UNIX host, edit your ~/.ssh/config file using an editor such as vi:
  2. $ vi ~/.ssh/config
  3. Add a line that sets the ServerAliveInterval property to 100 seconds:
  4. ServerAliveInterval 100
  5. Save the file and exit the editor.
  6. Enter the following command:
  7. $ ssh -i /path/to/private_key opc@<public_ip_address_of_the_instance>
  8. When prompted, enter the passphrase you provided for your SSH key pair.

Logging in From a Windows Host

  1. Start PuTTY. The PuTTY Configuration window is displayed, showing the Session panel.
  2. In the Host Name (or IP address) field, enter the public IP address of your instance.
    PuTTy Configuration dialog
  3. In the Connection type: field underneath the Host Name (or IP address) field, select the SSH radio button if it is not already selected.
  4. In the Category pane, expand Connection, and then select Data to display the Data to send to the server panel.
    1. In the Auto-login username field, enter opc.
    2. Confirm that the When username is not specified option is set to Prompt.
  5. PuTTy Configuration dialog
  6. Still within the Category pane under Connection, expand SSH and select Auth to display the Options controlling SSH authentication panel.
    1. In the Private key file for authentication field, select Browse and select the private key file that you saved earlier.
  7. PuTTy Configuration dialog
  8. Still in the Category pane, select Session to display the Session panel.
    1. In the Saved Sessions field, enter a name for this connection configuration, then select Save.
    2. Select Open to open the connection. The PuTTY Configuration window is closed and the PuTTY SSH Login window is displayed.
  9. Enter the passphrase you provided for your SSH key pair. When you connect to your instance for the first time, the PuTTY Security Alert window displays. When you are prompted to confirm the public key, select Yes to continue.

Set Up Secure Shell Between Nodes

Some functions and integrations require the use of Secure Shell (SSH) to connect between nodes without being prompted for a password. This section outlines how this works and tells you how to set it up.

Principles

The ssh-keygen command is used to generate a private key pair and corresponding public key pair. Each of these pairs is handled very differently:

  • The private key resides on the node from which remote nodes need to be accessible by an SSH login that requires no password. The private key is created in the ~/.ssh/id_rsa directory. As this read-only file is used to decrypt all correspondence encrypted with the public key, its contents should be safeguarded.
  • The public key is saved in ~/.ssh/id_rsa.pub. Using the scp command as shown in the second example below, you then copy the contents of the public key to the ~/.ssh /authorized_keys file on the systems you subsequently wish to connect to via SSH without being prompted for a password.

Detailed Steps

The following example demonstrates creation of the public and private keys:

$ ssh-keygen -t rsa
Generating public/private rsa key pair
Enter file in which to save the key (/u01/user2/.ssh/id_rsa): <File>
Enter passphrase: <passphrase>
Enter same passphrase again: <passphrase>
Your identification has been saved in /u01/user2/.ssh/id_rsa
Your public key has been saved in /u01/user2/.ssh/id_rsa.pub
The key fingerprint is: 16:d0:e2:dd:37:2f:8e:d5:59:3e:12:9d:2f:12:1e:5a

Note: You do not need a passphrase, so as shown press <Enter> when prompted.

This example shows the public key being copied to a system you subsequently wish to connect to via SSH without being prompted for a password:

$ scp -pr /u01/user2/.ssh/id_rsa.pub user2@system1:/tmp/.
$ cat /tmp/id_rsa.pub | ssh $h "umask 077; mkdir -p .ssh ; cat >> .ssh/authorized_keys"
user2@system1's password: <password>
.id_rsa.pub 100% 398 0.4KB/s 00:00

It is then possible to execute a passwordless SSH command such as:

$ ssh user2@system1

Note: If you receive the following messages, they can safely be ignored:

Warning: untrusted X11 forwarding setup failed: xauth key data not generated. 
Warning: No xauth data; using fake authentication data for X11 forwarding.

The copy operation must be performed for the relevant operating system account on all desired nodes, so SSH can log in without a password from a designated application tier node to other application tier nodes. You can then run commands remotely on all the application tier nodes to which you have copied the public key.

Determine Cloud Service Account Details

Many cloud service account details can be found in the welcome email you receive when you sign up for cloud services, including your account name and user name. In addition, for an IDCS-based account, you will receive an IDCS Global User ID (IDCS GUID). Keep this information for later use.

To access additional cloud service account details, you must first log on to the Oracle Cloud My Services dashboard. Then, follow the instructions below to determine your Compute Classic Service Instance ID and specific REST endpoints, as necessary.

Determine Oracle Cloud Infrastructure Compute Classic Service Instance ID

Determine your Compute Classic Service Instance ID by either selecting the Compute Classic link in the Compute Classic pane, or by clicking on View Details in the bottom-right menu of the pane. This will bring up a screen similar to the one below. You will find the Service Instance ID in the Additional Information section, as shown below.

Service Instance ID

Determine Oracle Cloud Infrastructure Compute Classic REST Endpoint

To determine your Compute Classic REST endpoint:

  1. From the Oracle Cloud My Services Dashboard page, navigate to the Compute Classic console by:
    1. Clicking the Action Menu icon near the bottom corner of the Compute Classic area on your Dashboard page, as shown below.
      Compute Classic pane
    2. Select Open Service Console.
  2. On the Compute Classic console, locate the Site selector on the top right hand side of the screen.
    Compute Classic console

  3. On the right of the site indicator, click on the down arrow to open the Site Selector pop-up. This will display your REST Endpoint.
    Site selector window

    Note: Depending on your cloud subscription, you may have access to multiple sites. You cannot run the EBS Cloud Admin Tool (ProvisionEBS.pl) on one site and provision your environment on another. Therefore, if you do have multisite access, first ensure that you select the correct site before recording your endpoint.

Determine Oracle Cloud Infrastructure Object Storage Classic REST Endpoint

Determine your Object Storage Classic REST endpoint by either selecting the Object Storage Classic link in the Object Storage Classic pane, or clicking on View Details in the bottom-right menu of the pane. This will bring up a screen similar to the one below. Click in the REST Endpoint field to select the whole contents, and record the value (for example, by using Ctrl-C).

Oracle Cloud Infrastructure Object Storage Classic Overview Page

Determine Oracle Database Cloud Service REST Endpoint

Your Oracle Database Cloud Service REST Endpoint is dependent on the region where your data center is located. The following are available choices:

  • https://psm.us.oraclecloud.com/
  • https://psm.emea.oraclecloud.com/
  • https://psm.au.oraclecloud.com/

Substitute this value when prompted.

Change Oracle E-Business Suite Account Passwords

Follow the instructions in the next two subsections to change the Oracle E-Business Suite Release 12.2 Oracle WebLogic Server administrator password and Oracle E-Business Suite Release 12.2 and 12.1 account passwords, respectively.

Change the Oracle WebLogic Server Administrator Password (Oracle E-Business Suite Release 12.2 only)

Follow these instructions to change the Oracle WebLogic Server administrator password.

  1. Log on to the Oracle Compute Cloud Service instance that hosts your Oracle E-Business Suite environment. (See section "Connect to Your Oracle Cloud Instance Via SSH".)
  2. Switch user from the opc user to the oracle user.
  3. $ sudo su - oracle
  4. Set the environment by running the following command:
    $ . /u01/install/APPS/EBSapps.env run
  5. Shut down all application tier services except Node Manager and Admin Server:
    $ $ADMIN_SCRIPTS_HOME/adstpall.sh -skipNM -skipAdmin
  6. On the primary node, run the following command to change the Oracle WebLogic Server administrator password:
    $ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword
  7. Restart all the application tier services by running the following command:
    $ $ADMIN_SCRIPTS_HOME/adstrtal.sh
    

Change Oracle E-Business Suite Passwords

Follow the instructions below according to your Oracle E-Business Suite release.

Oracle E-Business Suite Release 12.2.7, 12.2.6, and 12.2.5

  1. Log on to the Oracle Compute Cloud Service instance that hosts your Oracle E-Business Suite environment. (See section "Connect to Your Oracle Cloud Instance Via SSH".)
  2. Switch from the opc user to the oracle user by running the command:
  3. $ sudo su - oracle
  4. Set the environment and create the logs directory as shown below:
    $ . /u01/install/APPS/EBSapps.env run
    $ mkdir -p ~/logs
  5. Invalidate accounts. (Conditional)
    Applies to Oracle E-Business Suite Release 12.2.5 only. For the 12.2.7 and 12.2.6 images, all application users are invalidated by default.
     
    As the apps user, invalidate the accounts by running the following in SQL*Plus:
    $ sqlplus apps/<apps password>
    SQL> update FND_USER set ENCRYPTED_USER_PASSWORD='INVALID' where USER_ID != 6;
    SQL> commit;
    SQL> exit
  6. Download Patch 24831241. (Conditional)
    Applies to Oracle E-Business Suite Release 12.2.6 multi-node and 12.2.5. Does not apply to Oracle E-Business Suite Release 12.2.7 or 12.2.6 single node as the scripts are already present in the /u01/install/APPS/scripts directory.

    Download Patch 24831241 to the $PATCH_TOP directory to obtain scripts to enable the SYSADMIN user (and demo users if using a VISION demo database).
    Unzip the patch as follows:
    $ cd $PATCH_TOP
    $ unzip p24831241_R12_GENERIC.zip –d /u01/install/APPS/scripts/
  7. To log in via the web interface, you must initially set a password of your choice for the SYSADMIN user. Once the SYSADMIN user is active with the new password, you can create new users or activate existing, locked ones. To enable the SYSADMIN user, perform the following steps:
    1. Run the following commands:
      $ cd  ~/logs
      $ /u01/install/APPS/scripts/enableSYSADMIN.sh
    2. Enter a new password for SYSADMIN when prompted.
  8. (Conditional: For a VISION demo database)
    The SYSADMIN user can now connect to Oracle E-Business Suite via the web interface and can create new users, or activate existing locked ones.
    If this is a VISION demo database, you can now run another script to unlock a set of 36 application users that are typically employed when demonstrating Oracle E-Business using the VISION database.
    The script is /u01/install/APPS/scripts/enableDEMOusers.sh, and you run with the same environment as when running enableSYSADMIN.sh. Run the following commands, supplying a new password when prompted:
    $ cd  ~/logs $ /u01/install/APPS/scripts/enableDEMOusers.sh

    Note: Do not run this script on a FRESH/PROD database.

Oracle E-Business Suite Release 12.1.3

  1. Log on to the Oracle Compute Cloud Service instance that hosts your Oracle E-Business Suite environment. (See section "Connect to Your Oracle Cloud Instance Via SSH".)
  2. Switch from the opc user to the oracle user by running the command:
  3. $ sudo su - oracle
  4. Set the environment and create the logs directory as shown below:
    $ . /u01/install/APPS/apps_st/appl/APPS_<CONTEXT_NAME>.env run
    $ mkdir -p ~/logs
  5. Invalidate accounts. As the apps user, invalidate the accounts by running the following in SQL*Plus:
    $ sqlplus apps/<apps password>
    SQL> update FND_USER set ENCRYPTED_USER_PASSWORD='INVALID' where USER_ID != 6;
    SQL> commit;
    SQL> exit
  6. Download Patch 24831241 to the $PATCH_TOP directory to obtain scripts to enable the SYSADMIN user (and demo users if using a VISION demo database).
    Unzip the patch as follows:
    $ cd $PATCH_TOP
    $ unzip p24831241_R12_GENERIC.zip –d /u01/install/APPS/scripts/
  7. To log in via the web interface, you must initially set a password of your choice for the SYSADMIN user. Once the SYSADMIN user is active with the new password, you can create new users or activate existing, locked ones. To enable the SYSADMIN user, perform the following steps:
    1. Run the following commands:
      $ cd  ~/logs
      $ /u01/install/APPS/scripts/enableSYSADMIN.sh
    2. Enter a new password for SYSADMIN when prompted.
  8. (Conditional: For a VISION demo database)
    The SYSADMIN user can now connect to Oracle E-Business Suite via the web interface and can create new users, or activate existing locked ones.
    If this is a VISION demo database, you can now run another script to unlock a set of 36 application users that are typically employed when demonstrating Oracle E-Business using the VISION database.
    The script is /u01/install/APPS/scripts/enableDEMOusers.sh, and you run with the same environment as when running enableSYSADMIN.sh. Run the following commands, supplying a new password when prompted:
    $ cd  ~/logs $ /u01/install/APPS/scripts/enableDEMOusers.sh

    Note: Do not run this script on a FRESH/PROD database.

Reconfigure an Environment With a New Private IP After a VM Reboot

When there is a reboot of a VM, the private IP address of the VM node is changed. In the case of a VM created by our orchestration, you can run a script to reconfigure the system so that all of the nodes in the Oracle E-Business Suite environment recognize the new IP address.

You can either:

  • Run a script with an environment name to reconfigure that environment after the VM reboot; or
  • Run a cron job periodically to query all environments and reconfigure specific environments as needed.

Follow the relevant sections below to prepare your system to recover from a VM reboot.

Ensure You Are on the Latest Codeline

To take advantage of this capability, you must ensure that you are on the latest codeline by following the instructions in section "Update EBS Cloud Admin Tool to the Latest Codeline" in the Oracle by Example tutorial Deploying the EBS Cloud Admin Tool to Oracle Cloud Infrastructure Classic.

Propagate Changes to Existing Environments (Conditional)

If you have environments that were created using a prior version of the tool, then you also must take the following steps to update those environments.

  1. Copy theupdatehosts.sh and updateip.rc scripts from the provisioning VM to all nodes of the environment.
    1. First, create the /u01/install/scripts/ and /u01/install/APPS/scripts/ directories with execute permissions (755) on each Compute node in the environment.
    2. Use the scp command to copy "oracle-ebs/files/updatehosts.sh" to /u01/install/scripts/ on each Compute node in the environment.
    3. Use the scp command to copy "oracle-ebs/files/updateip.rc" to /u01/install/APPS/scripts/ on each Compute node in the environment.
  2. Upload all new cookbooks to the provisioning VM using the following command:
    $ knife cookbook upload -a -V --cookbook-path /u01/install/APPS/apps-unlimited-ebs/resources/chef-repo/cookbooks
  3. Now run the /u01/install/APPS/apps-unlimited-ebs/bin/updatePrivateIP.sh <envname>on the provisioning VM. This will create the necessary private IP files under /u01/install/APPS/apps-unlimited-ebs/out/privateiplog/.From now on, the subsequent runs will verify and update the private IP changes in /etc/hosts of nodes when there is a change.

Run a Script to Reconfigure a Single Environment (Optional)

You have the option to manually run the updatePrivateIP.sh script on a single environment as shown below.

$ sudo su - oracle 
$ /u01/install/APPS/apps-unlimited-ebs/bin/updatePrivateIP.sh <envname>

Set Up a Cron Job to Reconfigure Environments as Needed (Optional)

You also have the option to set up a periodic cron job to query all environments and reconfigure specific environments as needed. The following example shows a cron-tab schedules for every 30 minutes.

$ sudo su - oracle 
$ crontab -e
0,30 * * * * /u01/install/APPS/apps-unlimited-ebs/bin/updatePrivateIP.sh > /u01/install/APPS/apps-unlimited-ebs/out/privateiplogs/Latestcrontab.log

Validate the entry by running the following command:

$ crontab -l

Managing Ksplice/Uptrack Actions

Your Oracle E-Business Suite Cloud Manager Virtual Machine is installed with Ksplice Uptrack software that allows you to enable automatic Linux kernel updates.

To configure Ksplice Uptrack to install updates automatically, enable the autoinstall option in /etc/uptrack/uptrack.conf.

For more information, including other Ksplice Uptrack capabilities, refer to the Oracle Linux Ksplice User's Guide.

Backing Up the Provisioning Virtual Machine

It is recommended that you take a backup of the provisioning virtual machine (VM) prior to updating it to the latest codeline or prior to performing any other changes as might be directed by Oracle Support. This will allow the provisioning VM to be recreated in case the update or change operation fails.

You will achieve this backup by creating a snapshot of the boot storage volume.

You must have the original image used to create the provisioning VM. To restore the provisioning VM at a later date, you would create an instance from this image and associate it with the storage snapshot.

Record Host Name and Host File Contents

Log in to the provisioning VM (also called the EBS Cloud Admin Tool VM) and perform the following steps prior to conducting the backup:

  1. Determine the provisioning VM host name by typing the hostname command. Record this value for later use.
  2. Save the contents of the /etc/hosts for later use. You can copy the contents to a notepad or ftp the file to your devops machine.

Update the IP Reservation to Status Permanent

  1. In the Compute Classic console, select the Network tab and click on "IP Reservations" under Shared Network.
  2. Locate the IP reservation for the Provisioning VM. If the status is "Temporary," select "Permanent" from the Status drop-down listing. Click Update to make this IP reservation permanent.

Back Up the Provisioning VM

Before you proceed, ensure the following:

  • Users are not performing any provisioning when the backup is underway.
  • There are no OS updates being made.
  • All the data in the system memory is flushed to the disk. Execute the following command as the root user:
    # sync ; sync ; sync 

Execute the following steps to proceed with your backup:

  1. In the Compute Classic console, select the Storage tab.
  2. Locate the storage attached to your provisioning VM.
  3. Click on the menu icon () to the right and select Create Snapshot.
  4. In the Create Storage Snapshot window, provide a unique name for your snapshot (for example, provvm_copy), as well as a description. Make sure that the Colocated checkbox is unselected.
  5. Click on Create. This creates a snapshot of the storage attached to your provisioning VM.
Note: The backup process takes some time and is not complete until you see the snapshot status change to "Completed". Once the status confirms that the backup has been completed, then you may proceed to the next section.

Restoring the Provisioning Virtual Machine

Follow the subsections below in order to restore the provisioning virtual machine (VM).

Shut Down the Provisioning VM

Navigate to the Compute Classic console and perform the following tasks to shut down the original provisioning VM:

  1. In the Compute Classic console, click on the Instances tab.
  2. Locate the instance corresponding to your provisioning VM.
  3. Shut down the instance by clicking on the menu icon () to the right and selecting Shut Down.

Note: Instance shutdown may take a few minutes. Ensure the instance is stopped before proceeding.

Restore Storage Volume

On the Compute Classic Console, perform the following tasks:

  1. Click on the Storage tab.
  2. Select "Storage Snapshots" from the drop-down listing.
  3. Choose the storage snapshot you created previously (for example, provvm_copy).
  4. Click on the menu icon () to the right and select Restore Volume.
  5. From the Restore Storage Volume window, enter a name for the storage volume (for example, pvm_restore), and click Restore.
Note: The restore process can take up to 15 minutes. Ensure that the process is finished by verifying that the restored storage volume is online, prior to proceeding to the next step.

Recreate the Provisioning VM

Conduct the following steps to create a new provisioning instance and associate it with the storage snapshot you created in section "Backing Up the Provisioning Virtual Machine."

  1. In the Compute Classic console, select the Instances tab and click Create Instance.
  2. In the Create Instance wizard, click Customize and select Private Images.
  3. Select the original image used to create the provisioning VM from the list of Private Images and proceed to the Shape screen by clicking the > button located at the top right.
  4. On the Shape screen, select the appropriate shape for your instance.
    1. For example, select oc3 (OCPUs: 1, Memory: 7.5 GB).
    2. Click the > button to proceed to the Instance screen.
  5. On the Instance screen, perform the following steps:
    1. Using the Persistent drop-down list, ensure that the default option "False" is selected.
    2. Using the Placement drop-down list, ensure that the default option "Auto" is selected.
    3. In the Name field, enter an appropriate name. In the Name field, enter the name of your provisioning VM (for example, provvm).
    4. In the Label field, enter a description to help identify the instance. If you provide a label, the label is used to list the instance on the Instances tab.
    5. Click in the SSH Keys field and select your SSH key from the drop-down list.
    6. Click the > button to proceed to the Network screen.
  6. On the Network screen, perform the following steps:
    1. In the DNS Hostname Prefix field, enter the host name that was associated with the original provisioning VM, which was captured in "Record Host Name and Host File Contents."
    2. For Network Options, select Shared Network. Ensure that IP Network is not selected.
    3. Using the Public IP Address drop-down, choose Persistent Public IP Reservation.
    4. An IP Reservation drop-down list will appear. Choose your reserved IP reservation.
    5. In the Security Lists field, specify the security list associated with the original provisioning VM from the drop-down listing.
    6. Click the > button to proceed to the Storage screen.
  7. On the Storage screen:
    1. Under the Name column, you will see one volume listed, called <instance_name>_storage. Remove this storage by clicking on the menu icon () to the right and selecting Remove.
    2. Attach the storage that you previously restored by selecting "Attach Existing Volume".
    3. In the Attach Existing Storage Volume window, click in the Attach Storage Volume field and selecting the storage from the drop-down. Specify to attach it as Disk #1.
    4. Ensure the Boot Drive checkbox is selected.
      Note: If the Boot Drive checkbox is disabled, this means that the image that you selected is not the one originally used, or the account owner is different. Return to step 3 of this section and select the correct image to proceed.
    5. Click Add to return to the Storage screen.
    6. Click the > button to proceed to the Review screen.
  8. On the Review screen, check your selections. Click the < button to make any necessary edits.
    1. When you are ready, click Create to start the creation of your provisioning VM. You will see the message: "Starting orchestration <instance name>".
    2. The instance creation process goes through several phases, and may take a total of around 15 minutes to complete.
      Note: You can monitor progress by selecting the Orchestrations tab.
    3. When the process is complete, you will be able to click on the Instances tab to view your recreated provisioning VM.

Want to Learn More?

Change Log

Date Description
2019-04-24
  • Updated footer.
2018-09-14
  • Updated Managing Ksplice/Uptrack Actions content.
2018-06-28
  • Added Oracle E-Business Suite 12.2.7 information to "Change Oracle E-Business Suite Passwords" subsection.
  • Minor formatting enhancements.

2018-06-12

  • Added sections "Backing Up the Provisioning Virtual Machine" and "Recreating the Provisioning Virtual Machine" for 18.2.1 release.

2018-03-13

  • Updated "Determine Oracle Database Cloud Service REST Endpoint."

2018-03-09

  • Updated intro text of section "Determining Cloud Service Account Details" and subsection "Determine Oracle Database Cloud Service REST Endpoint."

2018-03-08

  • Added section "Managing Ksplice/Uptrack Actions."

2018-02-20

  • Changed "Determine REST Endpoints" to "Determine Cloud Service Account Details." Updated section contents and added subsection "Determine Oracle Cloud Infrastructure Compute Classic Service Instance ID."

2017-11-08

  • Made various updates in document to reflect updates in product/service name changes as well as UI updates.
  • Updated "Determine REST Endpoints" section.
  • Made minor edits throughout document for formatting and grammar.
  • Updated "Propagate Changes to Existing Environments (Conditional)" subsection.

2017-09-29

  • Made update to "Determine REST Endpoints in Oracle Cloud Infrastructure Compute Classic" section.
  • Made various updates to differentiate between Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic.
2017-08-15
  • Updated step order in subsection "Logging in From a Windows Host."
  • Added section "Reconfiguring an Environment with a New Private IP After a VM Reboot."
  • Updated various text and EBS Admin Tool UI screens throughout document for 1.7.2 release.
2017-06-30
  • Updated "Determine Oracle Compute Cloud Service REST Endpoint."
  • Updated content in "Change Oracle E-Business Suite Account Passwords."
  • Added Release 12.1.3 to to "Change Oracle E-Business Suite Passwords."
2017-05-05
  • Made various enhancements.
2017-02-28
  • Initial publication.
Back to top