This chapter covers the following topics:
This chapter describes how to manage the Oracle E-Business Suite Cloud Manager virtual machine after initial deployment.
Perform the following tasks to ensure you are using the latest version of Oracle E-Business Suite Cloud Manager.
Note: Unless otherwise noted, the Oracle E-Business Suite Cloud Manager administrator performs the tasks in this section.
Check the Oracle E-Business Suite Cloud Manager Version
After deploying Oracle E-Business Suite Cloud Manager, you can log in to Oracle E-Business Suite Cloud Manager and check the version by following the instructions in Log In to Oracle E-Business Suite Cloud Manager and Check the Oracle E-Business Suite Cloud Manager Version. If you see a message that a later version is available than the one you have installed, proceed with the rest of this procedure.
The latest version is 21.1.1.0.1.
Create a Backup of Oracle E-Business Suite Cloud Manager Virtual Machine
Before you run the Self Update Utility, we strongly recommend that you back up your Oracle E-Business Suite Cloud Manager Virtual Machine. To do so, follow the instructions in Cloning a Boot Volume to create a boot volume clone. You will also need to record key details of your provisioning VM for use during a restore process.
From the Oracle Cloud Infrastructure console on the Instances screen, click on your instance (for example, myebscminstance) to go to the Instance Details screen. Record (such as in a screenshot) the instance attributes for later use:
Shape
Availability Domain
Virtual Cloud Network (VCN)
Subnet
Private IP address
When you restore, you will also need the SSH key and host name of the original instance.
To obtain the host name, log in to Oracle E-Business Suite Cloud Manager VM using SSH, and perform the following steps:
Run the hostname command and record the name.
Make a note of the contents of the /etc/hosts file.
Migrate to the Latest Codelevel
Important: Note for Exadata Cloud Service customers:
In Release 20.2.1.1.1 and later, Oracle E-Business Suite Cloud Manager supports the new Exadata Cloud Service resource model. If you use Exadata Cloud Service, you should convert your Exadata DB Systems to this new model, and then update Oracle E-Business Suite Cloud Manager to the latest version.
Alternatively, if you are not ready to convert to the new resource model, and you need to provision Oracle E-Business Suite environments where the database is on an Exadata DB System that uses the old resource model, then you must remain on your existing Oracle E-Business Suite Cloud Manager release of 20.2.1.1 or earlier.
After you have created the backup of the virtual machine, you can proceed to migrate your deployment based on your current Oracle E-Business Suite Cloud Manager version.
If you are on Oracle E-Business Suite Cloud Manager version 19.3.1.X or later, perform the steps in Migrate Version 19.3.1.X or Later to the Latest Codelevel (Conditional).
If you are on Oracle E-Business Suite Cloud Manager version 19.2.1.2, perform the steps in Migrate Version 19.2.1.2 to the Latest Codelevel (Conditional)
If you are on Oracle E-Business Suite Cloud Manager version 19.1.1 through 19.2.1.1, perform the steps in Migrate Version 19.1.1 through 19.2.1.1 to the Latest Codelevel (Conditional).
If you are on a version earlier than 19.1.1, there is no predefined upgrade path. You may need to redeploy Oracle E-Business Suite Cloud Manager by following the instructions in Deploy Oracle E-Business Suite Cloud Manager on Oracle Cloud Infrastructure.
Note: For existing environments created with versions of Oracle E-Business Suite Cloud Manager prior to version 20.2.1, the expected behaviors are as follows:
For instances created using Advanced Provisioning:
The Logical FQDN for both the application tier and database tier will display as "Not Configured" on the Environment Details page.
The Add Node dialog window will not have the "Logical Hostname" field and the corresponding Logical FQDN on the Environment Details page should have "Not Configured" displayed.
For instances created using One-Click Provisioning, the DNS FQDN and Storage will display as "Not Available" on the Environment Details page.
The Logical FQDN will display as "Not Available" where applicable if the logicalHostConfigured flag is 'false' on the source.
Migrate Version 19.3.1.X or Later to the Latest Codelevel (Conditional)
If you are on Oracle E-Business Suite Cloud Manager version 19.3.1.X or later, and you have already created policies for tag-namespaces (such as in Define Additional Policies for Using "tag-namespaces"), then you need to run the Self Update utility to bring up your version to the latest version, 21.1.1.0.1.
Perform the following steps:
Connect to the Oracle E-Business Suite Cloud Manager VM using SSH and switch from the opc user to the oracle user:
$ sudo su - oracle
Run the Self Update utility as follows:
$ cd /u01/install/APPS/apps-unlimited-ebs/bin $ perl selfUpdate.pl
Review the warning for Exadata Cloud Service customers and check whether you are ready to proceed with the update to Release 21.1.1.0.1. If you use Exadata Cloud Service and you are not ready to convert to the new resource model, then you must enter option 2 to exit the utility and remain on your existing Oracle E-Business Suite Cloud Manager release of 20.2.1.1 or earlier.
If you use Exadata Cloud Service and you have converted your existing Exadata DB Systems to the new resource model, or if you do not use Exadata Cloud Service, then you can proceed with the update. In this case, you can enter option 1 to continue.
****************************** WARNING *********************************** Oracle E-Business Suite Cloud Manager Release 21.1.1.0.1 supports the new Exadata Cloud Service resource model. You should convert your Exadata DB Systems to this new model. Be aware that if you have not yet converted to the new model, and plan to provision Oracle E-Business Suite environments where the database is on an Exadata DB System that uses the old resource model, you must choose 2 to exit and remain on your existing Cloud Manager release. **************************************************************************** Do you wish to continue?? 1: yes 2: no Enter your choice: 1
Choose the Oracle E-Business Suite Cloud Manager release from the choices provided:
Available Oracle E-Business Suite Cloud Manager release versions: 1: 21.1.1.0.1 Choose release version to upgrade from the above list: 1
When prompted, enter your Oracle E-Business Suite Cloud Manager administrator password:
Enter Oracle E-Business Suite Cloud Manager Admin Password:
Note: You will have already followed the steps in Configure Oracle E-Business Suite Cloud Manager Compute Instance, to configure your VM. At this prompt, enter the Oracle E-Business Suite Cloud Manager administrator password you specified at that time.
Before continuing with the upgrade, you should ensure that there are no jobs in your Oracle E-Business Suite Cloud Manager with a status of In Progress, Scheduled, Paused, or Failed. Refer to Monitor Job Status.
It is recommended that you allow In Progress and Scheduled jobs to complete before continuing, resume any Paused jobs, and restart any Failed jobs that you want to try again. You can also choose to delete an incomplete installation or an incomplete backup to clean up any resources instead of restarting the Failed job. If there are still any jobs with a status of Failed when you perform the upgrade, their status will be changed to Aborted. In this case, you must manually clean up any incomplete resources from the job after the upgrade.
When prompted, enter y to confirm that you want to continue:
Ensure that there are no Running, Scheduled or Failed Activities before upgrade. Failed activities will be marked as aborted and user has to do failed resource cleanup manually or user can finish cleanup of failed instances before proceeding. Do you wish to continue [y/n]? y
The utility then displays several messages recording the actions it performs. Finally, it displays a screen containing a success message, similar to the following. You can optionally review the log file to verify further details about the upgrade.
============================================================================================================== Oracle E-Business Suite Cloud Manager VM setup successful. Version: 21.1.1.0.1 Refer to /u01/install/APPS/apps-unlimited-ebs/out/self-update-<date>_<time>.log for complete details. ==============================================================================================================
Migrate Version 19.2.1.2 to the Latest Codelevel (Conditional)
If you are on Oracle E-Business Suite Cloud Manager version 19.2.1.2, prior to running the Self Update utility to bring your version to the latest codelevel, you need to define additional policy statements. Then run the Self Update utility.
Define Additional Policies for Using "tag-namespaces"
The tenancy administrator performs the tasks in this section.
To accommodate the addition of tags, create new policies or add the following policy statements to existing policies:
Allow group <Oracle E-Business Suite Cloud Manager administrators group> to manage tag-namespaces in compartment <Oracle E-Business Suite Cloud Manager compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in compartment <Oracle E-Business Suite Cloud Manager compartment> Allow group <Oracle E-Business Suite Cloud Manager administrators group> to manage tag-namespaces in compartment <Oracle E-Business Suite compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in compartment <Oracle E-Business Suite compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in tenancy where target.tag-namespace.name='Oracle-Tags'
For example, create a new policy using the following steps:
From the Oracle Cloud Infrastructure console navigation menu, under Identity & Security, select Identity, and then click Policies.
Select the desired compartment from the drop-down list on the left.
Click Create Policy.
In the dialog window, enter the required details as follows:
NAME: Enter a name. For example, ebstag-policy.
DESCRIPTION: Enter a suitable description.
Add your desired policy statements.
Click Create Policy.
Perform the Migration Tasks
Perform the following steps:
Connect to the Oracle E-Business Suite Cloud Manager VM using SSH and switch from the opc user to the oracle user.
$ sudo su - oracle
Run the Self Update utility as follows:
$ cd /u01/install/APPS/apps-unlimited-ebs/bin $ perl selfUpdate.pl
Review the warning for Exadata Cloud Service customers and check whether you are ready to proceed with the update to Release 21.1.1.0.1. If you use Exadata Cloud Service and you are not ready to convert to the new resource model, then you must enter option 2 to exit the utility and remain on your existing Oracle E-Business Suite Cloud Manager release of 20.2.1.1 or earlier.
If you use Exadata Cloud Service and you have converted your existing Exadata DB Systems to the new resource model, or if you do not use Exadata Cloud Service, then you can proceed with the update. In this case, you can enter option 1 to continue.
****************************** WARNING *********************************** Oracle E-Business Suite Cloud Manager Release 21.1.1.0.1 supports the new Exadata Cloud Service resource model. You should convert your Exadata DB Systems to this new model. Be aware that if you have not yet converted to the new model, and plan to provision Oracle E-Business Suite environments where the database is on an Exadata DB System that uses the old resource model, you must choose 2 to exit and remain on your existing Cloud Manager release. **************************************************************************** Do you wish to continue?? 1: yes 2: no Enter your choice: 1
Choose the Oracle E-Business Suite Cloud Manager release from the choices provided:
Available Oracle E-Business Suite Cloud Manager release versions: 1: 21.1.1.0.1 Choose release version to upgrade from the above list: 1
When prompted, enter your Oracle E-Business Suite Cloud Manager administrator password:
Enter Oracle E-Business Suite Cloud Manager Admin Password:
Note: You will have already followed the steps in Configure Oracle E-Business Suite Cloud Manager Compute Instance, to configure your VM. At this prompt, enter the Oracle E-Business Suite Cloud Manager administrator password you specified at that time.
Before continuing with the upgrade, you should ensure that there are no jobs in your Oracle E-Business Suite Cloud Manager with a status of In Progress, Scheduled, or Failed. Refer to Monitor Job Status.
It is recommended that you allow In Progress and Scheduled jobs to complete before continuing, and restart any Failed jobs that you want to try again. You can also choose to delete an incomplete installation or an incomplete backup to clean up any resources instead of restarting the Failed job. If there are still any jobs with a status of Failed when you perform the upgrade, their status will be changed to Aborted. In this case, you must manually clean up any incomplete resources from the job after the upgrade.
When prompted, enter y to confirm that you want to continue:
Ensure that there are no Running, Scheduled or Failed Activities before upgrade. Failed activities will be marked as aborted and user has to do failed resource cleanup manually or user can finish cleanup of failed instances before proceeding. Do you wish to continue [y/n]? y
The utility then displays several messages recording the actions it performs. Finally, it displays a screen containing a success message, similar to the following. You can optionally review the log file to verify further details about the upgrade.
============================================================================================================== Oracle E-Business Suite Cloud Manager VM setup successful. Version: 21.1.1.0.1 Refer to /u01/install/APPS/apps-unlimited-ebs/out/self-update-<date>_<time>.log for complete details. ==============================================================================================================
Migrate Version 19.1.1 through 19.2.1.1 to the Latest Codelevel (Conditional)
If you are on Oracle E-Business Suite Cloud Manager version 19.1.1 or later, up to and including 19.2.1.1, you must first upgrade to version 19.3.1.2. Then you can migrate from that version to the latest codelevel.
Prior to running the Self Update utility to bring your version to 19.3.1.2, you need to define additional policy statements. Then, run the Self Update utility to migrate to version 19.3.1.2.
If you are upgrading from 19.1.1.X, you must then complete the 19.3.1.2 configuration by running the UpdateOCINetwork.pl script to update the network profile for Oracle E-Business Suite Cloud Manager.
Finally, you can migrate from version 19.3.1.2 to the latest codelevel.
Define Additional Policies for Using "tag-namespaces"
The tenancy administrator performs the tasks in this section.
To accommodate the addition of tags, create new policies or add the following policy statements to existing policies:
Allow group <Oracle E-Business Suite Cloud Manager administrators group> to manage tag-namespaces in compartment <Oracle E-Business Suite Cloud Manager compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in compartment <Oracle E-Business Suite Cloud Manager compartment> Allow group <Oracle E-Business Suite Cloud Manager administrators group> to manage tag-namespaces in compartment <Oracle E-Business Suite compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in compartment <Oracle E-Business Suite compartment> Allow group <Oracle E-Business Suite administrators group> to use tag-namespaces in tenancy where target.tag-namespace.name='Oracle-Tags'
For example, create a new policy using the following steps:
From the Oracle Cloud Infrastructure console navigation menu, under Identity & Security, select Identity, and then click Policies.
Select the desired compartment from the drop-down list on the left.
Click Create Policy.
In the dialog window, enter the required details as follows:
NAME: Enter a name (for example, ebstag-policy).
DESCRIPTION: Enter a suitable description.
Add your desired policy statements.
Click Create Policy.
Perform the Migration Tasks
Perform the following steps:
Connect to the Oracle E-Business Suite Cloud Manager VM using SSH and switch from the opc user to the oracle user.
$ sudo su - oracle
Run the Self Update utility as follows:
$ cd /u01/install/APPS/apps-unlimited-ebs/bin $ perl selfUpdate.pl
Choose the Oracle E-Business Suite Cloud Manager release from the choices provided:
Available Oracle E-Business Suite Cloud Manager release versions: 1: 19.3.1.2 Choose release version to upgrade from the above list: 1
When prompted, enter your Oracle E-Business Suite Cloud Manager administrator password:
Enter Oracle E-Business Suite Cloud Manager Admin Password :
Note: You will have already followed the steps in Configure Oracle E-Business Suite Cloud Manager Compute Instance to configure your VM. At this prompt, enter the Oracle E-Business Suite Cloud Manager administrator password you specified at that time.
Before continuing with the upgrade, you should ensure that there are no jobs in your Oracle E-Business Suite Cloud Manager with a status of In Progress, Scheduled, or Failed. Refer to Monitor Job Status.
It is recommended that you allow In Progress and Scheduled jobs to complete before continuing, and restart any Failed jobs that you want to try again. You can also choose to delete an incomplete installation or an incomplete backup to clean up any resources instead of restarting the Failed job. If there are still any jobs with a status of Failed when you perform the upgrade, their status will be changed to Aborted. In this case, you must manually clean up any incomplete resources from the job after the upgrade.
When prompted, enter y to confirm that you want to continue:
Ensure that there are no Running, Scheduled or Failed Activities before upgrade. Failed activities will be marked as aborted and user has to do failed resource cleanup manually or user can finish cleanup of failed instances before proceeding. Do you wish to continue [y/n]? y
The utility then displays several messages recording the actions it performs. Finally, it displays a screen containing a success message, similar to the one below. You can optionally review the log file to verify further details about the upgrade.
============================================================================================================== Oracle E-Business Suite Cloud Manager VM setup successful. Version: 19.3.1.2 Refer to /u01/install/APPS/apps-unlimited-ebs/out/self-update-<date>_<time>.log for complete details. ==============================================================================================================
Run UpdateOCINetwork.pl (Conditional)
Note: The Oracle E-Business Suite Cloud Manager administrator performs the tasks described in this section.
If you are upgrading from 19.1.1.X, the Oracle E-Business Suite Cloud Manager administrator, you must run the UpdateOCINetwork.pl script to update the network profile for Oracle E-Business Suite Cloud Manager.
As the oracle user, run the UpdateOCINetwork.pl script using the following commands:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ perl UpdateOCINetwork.pl
Run the Self Update Utility to Migrate from 19.3.1.2 to the Latest Codelevel
Complete the migration by following the steps in Migrate Version 19.3.1.X or Later to the Latest Codelevel.
This section covers how to perform administrative tasks on the Oracle E-Business Suite Cloud Manager VM, categorized into three sections:
Manage Services - The ebscloudmgrctl.sh script is used to manage services, which include the following tasks:
Review or Change Configurations - The ebscmadmin utility is used to review or change configurations, which include the following tasks:
Change the Oracle E-Business Suite Cloud Manager Administration Password
Change the Oracle E-Business Suite Cloud Manager Administrator Group
Change the Load Balancer Associated with Your Oracle E-Business Suite Cloud Manager VM
Update the Oracle E-Business Suite Cloud Manager Load Balancer URL
Update the Oracle E-Business Suite Cloud Manager Load Balancer Fully Qualified Domain Name (FQDN)
Standalone Tasks
Note: Apart from Start Services and Stop Services, these tasks are optional.
Common Command Line Arguments
The following are common arguments to many of the commands described in this section.
Passwords
In many instances, the command line help will indicate that a password is required. The following is an example of how to securely provide a password to a command line utility such as ebscmadmin:
$ { echo <EBSCM_admin_password>;} | ebscmadmin <command> [arguments]
Configuration File
The configuration file refers to a file created as part of the user profile. This file is typically located in the Oracle E-Business Suite Cloud Manager Compute instance in the directory /u01/install/APPS/.oci. Take note of the configuration file for your user, as this is a required argument for some commands.
Manage Services
Use ebscloudmgrctl.sh for managing services.
Start Services
Perform the following steps to start services.
As the oracle user, run ebscloudmgrctl.sh with the startall command.
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ sh ebscloudmgrctl.sh startall
Enter the Oracle E-Business Suite Cloud Manager administrator password when prompted.
Enter Oracle E-Business Suite Cloud Manager Admin Password:
Perform the following steps to stop services.
As the oracle user, run ebscloudmgrctl.sh with the stopall command.
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ sh ebscloudmgrctl.sh stopall
Enter the Oracle E-Business Suite Cloud Manager administrator password when prompted.
Enter Oracle E-Business Suite Cloud Manager Admin Password:
Abort Running Jobs
Perform the following steps to abort all jobs and stop all services.
As the oracle user, run ebscloudmgrctl.sh with stopall force.
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ sh ebscloudmgrctl.sh stopall force
Enter the Oracle E-Business Suite Cloud Manager administrator password when prompted.
Enter Oracle E-Business Suite Cloud Manager Admin Password:
Review or Change Configurations
Use the ebscmadmin utility for reviewing or changing configurations.
For help with ebscmadmin, run $ ./ebscmadmin -h.
To get detailed help on a particular command, run $ ./ebscmadmin <command> -h.
Check the Oracle E-Business Suite Cloud Manager Version
Use this command to check what version of Oracle E-Business Suite Cloud Manager you currently have deployed.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the ebscm-version-details command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin ebscm-version-details
This will display your current version Oracle E-Business Suite Cloud Manager, the latest version that is available, as well as a brief message summarizing whether or not you need to or are able to upgrade.
Update the Oracle E-Business Suite Cloud Manager Load Balancer URL
Use this command if you wish to use a DNS-registered host name instead of a public IP address in the Oracle E-Business Suite Cloud Manager UI URL.
For example, if the Oracle E-Business Suite Cloud Manager UI is already configured, the load balancer URL is https://192.0.2.1:443, and you have registered the IP address 192.0.2.1 in your DNS server as example.com, then you can pass the URL https://example.com:443 as the LBaaS URL to the utility by using the steps shown in the following example.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the update-load-balancer-url command followed by an argument.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin update-load-balancer-url --load-balancer-url=https://example.com:443
Run ./ebscmadmin update-load-balancer -h to review all available arguments for this command.
When prompted, enter the Oracle E-Business Suite Cloud Manager administrator password.
Enter Oracle E-Business Suite Cloud Manager Administration Password:
You will then see a confirmation screen indicating that the configuration of the Oracle E-Business Suite Cloud Manager VM is complete. The following is an example of the confirmation message.
Oracle E-Business Suite Cloud Manager Load Balancer URL updated successfully. Ensure the confidential application is correctly configured in IDCS as per the documentation.
Now, sign on to the Oracle Identity Cloud Service Console.
Expand the menu located in the top left corner, and select Applications.
Search for the confidential application that needs to be updated.
Click Confidential Application.
Navigate to the Configuration tab.
Expand Client Configuration.
Review and update the values of the Redirect URL and Post Logout Redirect URL fields.
Click Save.
Change the Oracle E-Business Suite Cloud Manager Administration Password
Use this command if you wish to change the Oracle E-Business Suite Cloud Manager administration password.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the change-admin-password command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin change-admin-password
Run ./ebscmadmin change-admin-password -h to review all available arguments for this command.
When prompted, enter your current Oracle E-Business Suite Cloud Manager administration password, specify the new password, and then re-enter the new password to confirm it.
Enter Current Oracle E-Business Suite Cloud Manager Administration Password: Enter New Oracle E-Business Suite Cloud Manager Administration Password: Re-enter New Oracle E-Business Suite Cloud Manager Administration Password:
The following message appears indicating that you have successfully changed the Oracle E-Business Suite Cloud Manager administration password.
Oracle E-Business Suite Cloud Manager administration Password changed successfully.
Change the Oracle E-Business Suite Cloud Manager Administrator Group
Use this command if you wish to change the Oracle E-Business Suite Cloud administrator group.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the change-admin-group command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin change-admin-group <argument>
Run ./ebscmadmin change-admin-group -h to review the appropriate arguments for this command.
Once you run the command, the following screen appears indicating that you have successfully changed the Oracle E-Business Suite Cloud Manager administrator group.
Created log file: /u01/install/APPS/apps-unlimited-ebs/out/ebscmadmin/change-admin-group_20201120_022249.log Validating if user is authorized member of Oracle E-Business Suite Cloud Administrator Group User is part of Oracle E-Business Suite Cloud Manager Administrator Group OCID: ocid1.group.oc1.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Validating Group OCID Changing Oracle E-Business Suite Cloud Manager Admin Group.. Stopping Node and Job Server if running. Starting Node and Job Server. Oracle E-Business Suite Cloud Manager Admin Group changed successfully.
View a List of Compatible Load Balancers
Use this command to view a list of all load balancers that can be configured with your specific orchestration VM.
As the oracle user, run ebscmadmin with the list-compatible-load-balancers command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin list-compatible-load-balancers <argument>
Run ./ebscmadmin list-compatible-load-balancers -h to review the appropriate arguments for this command.
A log file is created and a list of available load balancers is displayed.
Created log file: /u01/install/APPS/apps-unlimited-ebs/out/ebscmadmin/list-compatible-load-balancers_20201120_022822.log Getting list of available Load Balancers. Please wait. Available Load Balancers: 1: ebs-prov-vm-lbaas -- ocid1.loadbalancer.oc1.uk-london-1.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2: ebs1-lbaas -- ocid1.loadbalancer.oc1.uk-london-1.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 3: ebs2-lbaas -- ocid1.loadbalancer.oc1.uk-london-1.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Change the Load Balancer Associated with Your Oracle E-Business Suite Cloud Manager VM
Use this command if you wish to reconfigure the Oracle E-Business Suite Cloud Manager VM with a different load balancer. The utility will allow you to choose from a list of existing load balancers within your compartment.
As the oracle user, run ebscmadmin with the change-load-balancer command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin change-load-balancer <argument>
Run ./ebscmadmin change-load-balancer -h to review the appropriate arguments for this command.
The following is an example of the confirmation message that is displayed.
Ensure the confidential application is correctly configured in IDCS as per the documentation. Oracle E-Business Suite Cloud Manager URL: https://xxx.xxx.xxx.xxx:xxx Use "ebscmadmin update-load-balancer-url" command to update Oracle E-Business Suite Cloud Manager URL (Optional)
Now, sign on to the Oracle Identity Cloud Service Console.
Expand the menu located in the top left corner, and select Applications.
Search for the confidential application that needs to be updated.
Click Confidential Application.
Navigate to the Configuration tab.
Expand Client Configuration.
Review and update the values of the Redirect URL and Post Logout Redirect URL fields.
Click Save.
Update the Oracle E-Business Suite Cloud Manager Load Balancer Fully Qualified Domain Name
Use this command to update the fully qualified domain name (FQDN) of your Oracle E-Business Suite Cloud Manager load balancer.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the update-load-balancer-fqdn command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin update-load-balancer-fqdn <argument>
Run ./ebscmadmin to review the appropriate arguments for this command.update-load-balancer-fqdn -h
After running the command with the proper arguments, the output will look similar to the following:
Created log file: /u01/install/APPS/apps-unlimited-ebs/out/ebscmadmin/update-load-balancer-fqdn_<date>_<time>.log Validating if user is an authorized member of Oracle E-Business Suite Cloud Administrator Group User is part of Oracle E-Business Suite Cloud Manager Administrator Group OCID: ocid1.group.oc1..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Deriving load balancer details of Oracle E-Business Suite Cloud Manager VM. Creating OCI certificate resource. Updating OCI Listener, yc3-ashburn-prov-vm-listener resource. Updating load balancer frontend host in database. Stopping Node and Job Server if running. Starting Node and Job Server. Following public certificate is used for OCI certificate resource. Public certificate: /u01/install/APPS/apps-unlimited-ebs/orcvm-state/signedcertificates/example.com_exdemocert.crt Oracle E-Business Suite Cloud Manager URL: https://example.com:8082 Note: Ensure the confidential application is correctly configured in IDCS as per the Oracle E-Business Suite Cloud Manager Guide.
Now, sign on to the Oracle Identity Cloud Service Console.
Expand the menu located in the top left corner, and select Applications.
Search for the confidential application that needs to be updated.
Click Confidential Application.
Navigate to the Configuration tab.
Expand Client Configuration.
Review and update the values of the Redirect URL and Post Logout Redirect URL fields.
Click Save.
Update the Oracle Identity Service Cloud Configuration
Use this command if you wish to change your Oracle Identity Cloud Service configuration.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the update-idcs-configuration command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin update-idcs-configuration <argument>
Run ./ebscmadmin update-idcs-configuration -h to review the appropriate arguments for this command.
After running the command with the proper arguments, a confirmation message is displayed:
Oracle E-Business Suite Cloud Manager IDCS details updated successfully. Ensure the confidential application is correctly configured in IDCS as per the documentation.
Now, sign in to the Oracle Identity Cloud Service Console.
Expand the menu located in top left corner, and select Applications.
Search for the confidential application that needs to be updated.
Click Confidential Application.
Navigate to the Configuration tab.
Expand Client Configuration.
Review and update the values of the Redirect URL and Post Logout Redirect URL fields.
Click Save.
Change the Parallel Worker Count
Use this command to specify the number of jobs that will be run in parallel, by updating the parallel worker count.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the update-worker-count command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin update-worker-count <argument>
Run ./ebscmadmin update-worker-count -h to review the appropriate arguments for this command.
After running the command with the proper arguments, a confirmation message is displayed:
Worker count updated successfully.
Create a User Profile
Use this command to create a user profile.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the create-user-profile command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin create-user-profile <argument>
Run ./ebscmadmin create-user-profile -h to review the appropriate arguments for this command.
After running the command with the proper arguments, the output will look similar to the following:
Created/Updated user specific OCI configuration file <configuration file location> successfully. User profile creation completed successfully.
Enable Mailer Configuration
Use this command to enable mailer configuration for Oracle E-Business Suite Cloud Manager.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the enable-mailer command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin enable-mailer <argument>
Run ./ebscmadmin enable-mailer -h to review the appropriate arguments for this command.
After running the command with the proper arguments, a confirmation message is displayed.
Successfully enabled mailer configuration.
Disable Mailer Configuration
Use this command to disable mailer configuration for Oracle E-Business Suite Cloud Manager.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the disable-mailer command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin disable-mailer <argument>
Run ./ebscmadmin disable-mailer -h to review the appropriate arguments for this command.
After running the command with the proper arguments, a confirmation message is displayed.
Successfully disabled mailer configuration.
Tag Oracle E-Business Suite Environments
Use this command to tag all Oracle E-Business Suite environments associated with your Oracle E-Business Suite Cloud Manager.
As the oracle user, change to the appropriate directory, and run ebscmadmin with the tag-ebs-environments command.
For example:
$ sudo su - oracle $ cd /u01/install/APPS/apps-unlimited-ebs/bin $ ./ebscmadmin tag-ebs-environments <argument>
Run ./ebscmadmin tag-ebs-environments -h to review the appropriate arguments for this command.
After running the command with the proper arguments, you will see output similar to the following example:
Created log file: /u01/install/APPS/apps-unlimited-ebs/out/ebscmadmin/tag-ebs-environments_20201111_173423.log Creating Namespace oracle-apps Creating Tag key purpose Tagging all EBS instances. Tagging EBSCM.
Standalone Tasks
Replace the Self-Signed Certificate for the Oracle E-Business Suite Cloud Manager Load Balancer with a Certificate Authority Issued Certificate
When you configure Oracle E-Business Suite Cloud Manager, the listener of the Load Balancer as a Service (LBaaS) is TLS enabled for HTTP inbound connections to Oracle E-Business Suite Cloud Manager. The certificate that is deployed by default for this configuration is a self-signed certificate. You can update the self-signed certificate with a certificate authority (CA) issued certificate using the following steps:
By default the Oracle E-Business Suite Cloud Manager URL uses an IP address rather than a host name. The first step is to map the Oracle E-Business Suite IP address to a host name.
Note: Oracle Cloud Infrastructure provides a public IP address but does not provide a public host name; therefore, you should ensure that appropriate DNS entries are present to resolve host name to the public IP address.
Update the Oracle E-Business Suite Cloud Manager VM by following the instructions in Update the Oracle E-Business Suite Cloud Manager URL.
Obtain a certificate for the host name from a certificate authority.
Log in to the Oracle Cloud Infrastructure console. From the navigation menu, select Networking, then Load Balancers, and then select the load balancer you want to configure.
Add your certificate bundle to the load balancer. See To upload an SSL certificate bundle to your load balancing system in the Oracle Cloud Infrastructure Services documentation.
If you have multiple certificates that form a single certification chain, such as one or more intermediate certificates together with a root certificate, then you must include all relevant certificates in one file before you upload them to the system. Refer to "Uploading Certificate Chains" in Working with SSL Certificates in the Oracle Cloud Infrastructure Documentation.
While still on the Load Balancer page, click the Listeners link under the Resources menu on the left.
Search for the Oracle E-Business Suite Cloud Manager's listener. Note that there can be multiple listeners associated, as the same load balancer can be used by more than one Oracle E-Business Suite Cloud Manager. Ensure to pick the listener corresponding to the Oracle E-Business Suite Cloud Manager you are using.
Click the Actions icon (three dots) associated with the Oracle E-Business Suite Cloud Manager's listener's row, select Edit from the context menu.
In the Edit Listener dialog window, select the certificate bundle added above in the Certificate Name drop-down list. Click Save Changes and wait for the listener to be updated.
Rediscover an Upgraded Environment
If you used Oracle E-Business Suite Cloud Manager to deploy your environment and now plan to upgrade either Oracle E-Business Suite or the Oracle E-Business Suite database, you can continue to use Oracle E-Business Suite Cloud Manager after the upgrade by rediscovering the environment using the steps in this section.
Rediscovery is available for the following use cases, where the database can be running on any supported cloud service:
Your Oracle E-Business Suite Release 12.2 or 12.1 environment running with Oracle Database 12.1.0.2 or 11.2.0.4 is upgraded to Oracle Database 19c.
Your Oracle E-Business Suite Release 12.1 environment (running with any database version) is upgraded to Oracle E-Business Suite Release 12.2.
Important: Before performing rediscovery, ensure that the Resource Owner option is selected under Allowed Grant Types in the registration of Oracle E-Business Suite Cloud Manager as an application in Oracle Identity Cloud Service (IDCS). See Register Oracle E-Business Suite Cloud Manager as a Confidential Application.
Conditional Action: The following requirements apply to an upgrade of Oracle E-Business Suite from Release 12.1.3 to Release 12.2.
If you upgraded your Oracle E-Business Suite environment from Release 12.1.3 to Release 12.2 using a new VM, separate from the VM where the Release 12.1.3 environment is located, then you must perform the corresponding load balancer configuration after the upgrade. You should complete the load balancer configuration before performing rediscovery. See "Upgrading to Oracle E-Business Suite Release 12.2" in My Oracle Support Knowledge Document 2517025.1, Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure.
If you performed the Oracle E-Business Suite upgrade on the same VM as the Release 12.1.3 environment, then you do not need to change the load balancer configuration.
The following scripts are provided to enable rediscovery:
unregister-environment.js - This script end dates the existing metadata entry for the environment and deletes it from the Chef repository.
discover-environment.js - This script performs prediscovery validation, and, if the validation succeeds, submits a discovery job to rediscover the upgraded environment.
discovery-status.js - This script lets you check the status of a discovery job submitted through the discover-environment.js script.
withdraw-discover.js - This script withdraws a failed discovery request to enable you to retry the discovery. You must withdraw a failed discovery request to clean up its registration metadata before you can submit a new discovery request for the same environment.
These scripts are located in the /u01/install/APPS/apps-unlimited-ebs/bin/rediscovery directory. The log file for the scripts is stored in the following location: /u01/install/APPS/apps-unlimited-ebs/out/NodeJSClient.log
To rediscover an updated environment, perform the following steps:
Ensure you are using the minimum Oracle E-Business Suite Cloud Manager version required for your use case, as shown in the following table.
| Upgrade Type | Oracle E-Business Suite Cloud Manager Minimum Version |
|---|---|
| Oracle E-Business Suite upgrade | 20.2.1.1 |
| Oracle Database upgrade on Compute | 21.1.1 |
| Oracle Database upgrade on VM DB Systems and Exadata Cloud Services | 21.1.1.0.1 |
If you need to update your version, follow the instructions in Update Oracle E-Business Suite Cloud Manager to the Latest Version.
Run the unregister-environment.js script using the following commands.
$ cd /u01/install/APPS/apps-unlimited-ebs/bin/rediscovery $ node unregister-environment.js
When prompted, specify the name of the upgraded environment, your Oracle Identity Cloud Service user name and password, and your Oracle E-Business Suite Cloud Manager administrator password.
Create a stage directory on the database node of the upgraded environment to store metadata gathered during the discovery job. For example: /tmp/stage
Run the discover-environment.js script using the following commands.
$ cd /u01/install/APPS/apps-unlimited-ebs/bin/rediscovery $ node discover-environment.js
When prompted, specify the following details:
A name for the discovery request.
The name of the network profile used to provision the environment.
The IP address for the environment's database node.
The stage directory you created for the discovery job on the database node.
The file path for the environment's database context file.
The APPS password for the environment.
Your Oracle Identity Cloud Service user name.
Your Oracle Identity Cloud Service password.
Your Oracle E-Business Suite Cloud Manager administrator password.
The load balancer configured for the environment. The script displays a list of the load balancers that are registered in the load balancer subnet within the specified network profile. If this environment uses multiple zones for the application tier and has more than one load balancer, enter the list of load balancer names separated by commas.
The listener for the environment. The script displays a list of the listeners configured for the specified load balancer. If this environment uses more than one listener, enter the list of listener names separated by commas.
If you need to check the status of a discovery job, run the discovery-status.js script using the following commands.
$ cd /u01/install/APPS/apps-unlimited-ebs/bin/rediscovery $ node discovery-status.js
When prompted, specify the discovery job ID assigned by the discover-environment.js script and your Oracle E-Business Suite Cloud Manager administrator password.
Tip: The discover-environment.js script may take some time to complete. If you want to check the progress of a discovery job that is still running, open a separate terminal window to run the discovery-status.js script without disrupting the running discovery job.
After the discovery job completes successfully, log into Oracle E-Business Suite Cloud Manager and verify the updated information for the environment in the environment details page. See Access Oracle E-Business Suite Cloud Manager and Review Environment Details (Standard).
If a discovery job failed, you must withdraw the failed discovery request before retrying discovery. To withdraw a request, run the withdraw-discover.js script using the following commands.
$ cd /u01/install/APPS/apps-unlimited-ebs/bin/rediscovery $ node withdraw-discover.js
When prompted, specify the name of the failed discovery request, your Oracle Identity Cloud Service user name and password, and your Oracle E-Business Suite Cloud Manager administrator password.
After you have withdrawn the previous discovery request and corrected any issues that caused the discovery to fail, you can retry discovery by rerunning the discover-environment.js script.
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.