Web Application Firewall(waf) as reverse proxy in Oracle Cloud (OCI)

 Oracle Cloud Infrastructure Web Application Firewall is a regional-based and edge enforcement service that is attached to an enforcement point, such as a load balancer or a web application domain name. WAF protects applications from malicious and unwanted internet traffic. WAF can protect any internet facing endpoint, providing consistent rule enforcement across a customer's applications. In this post, WAF works as a reverse proxy between the client and your website server. The real IP addresses of your website server are hidden from the visitors, and only the IP addresses of WAF are visible to them. The IP address of the web server is already mapped with DNS mapping.

Create WAF Policy

WAF Origin is basically the host or IP address of the public internet facing application that is being protected by the application. 

This takes time. Once it is created successfully, you will get the below screen.

Now test your application. Reference:-https://docs.oracle.com/en-us/iaas/Content/WAF/Concepts/gettingstarted.htm

Now, go to the OCI DNS Service and create a CNAME.

Publish the changes.

Next, modify the security lists of the webserver to recieve the requests from WAF. At this moment, we would need the IPV4 address of the WAF. If you scroll above, when we tested the application, we had recieved one IPV4 address. If I check the IP address for WAF server, it gives me the CIDR value with reference 192.29.50.64 and thus i used 192.29.0.0/16.

In the browser now, test it

We can verify the logs from WAF

Response code is 200.

I hope this post will be helpful for someone. In the next post, we will see how we can use Access Control in WAF for OCI. Till then, happy learning cloud.

Reference:-https://docs.oracle.com/en-us/iaas/Content/WAF/Concepts/overview.htm#:~:text=Oracle%20Cloud%20Infrastructure%20Web%20Application%20Firewall%20is%20a%20regional%2Dbased,malicious%20and%20unwanted%20internet%20traffic.

OCI load balancer redirection using Routing Policies

In Layman terms, load balancers helps in distributing the requests to the backend servers based upon certain algorithms. OCI Load Balancers helps in achieving high availability and scalability. Based upon our requirement we can induce multiple policies and application level health checks in OCI Load Balancer. In this post, i am going to demonstrate how we can leverage routing policies to redirect requests to backend servers using certain conditions. If you want to know how to create a Load balancer, you can refer to my earlier post https://samappsdba.blogspot.com/2020/05/configuring-oci-load-balancer-for-ebs.html

 I have a webserver1 with Public IP:-X.X.X.65. This is registered under DNS as dumka.tk 

I have an another webserver2 with Public IP:-X.X.X.61. This is registered under DNS as dumka.ml

Now i will create the Load balancer

I will add the backend later

Load balancer will now be created.

Add the backends now

Create listener for two backends

Now create the hostnames

Edit the listener and add the respective hostnames

Now Define the Routing Policies

At last, add the Public IP of the Load balancer to the DNS Zones.

Perform the testing

There are many other advanced configurations which we can use with our OCI Load Balancer for which we can go through the Advanced OCI LB Concepts. You can also refer my earlier post OCI LB Redirection on how i had used Path Route set for Load balance Redirection. This post is all about how using one Network load balancer, we can serve multiple websites using hostname and Routing policies. Hope this post helps someone. Keep learning cloud.

ebs 12.2 clone fails in the FMW pre-requisite section

The goal of this post is to give details on the issue which we had encountered when we were trying to do a clone for EBS 12.2.6 to target running on OEL 8.  Source was running on OEL7. As part of cloning steps, we need to run adcfgclone.pl appsTier dualfs for configuring the file system. As part of the process, the steps were failing on the pre checks for FMW. It was erroring out with

=====================================

Expected result: One of oracle-7,redhat-7,redhat-6,oracle-6,oracle-5,enterprise-5.4,enterprise-4,enterprise-5,redhat-5.4,redhat-4,redhat-5,SuSE-10,SuSE-11

Actual Result: oracle-8.5

Check complete. The overall result of this check is: Failed <<<<

=======================================

OS being used was OEL8 and thus it shouldn't have been an issue. Upon deep dive into the configuration files, i found that the pre checks for FMW use the file refhost.xml which basically resides under EBSapps/comn/clone/prereq/webtier/Scripts/prereq/linux64. So as a workaround, i added the copied the contents for oracle-7 and made it look like as oracle-8 and pasted it at the top of the file.

Then i reran the adcfgclone again and now it passed the prechecks for FMW. The intention of the post is just a way for workaround and it should not be a solution.

how to configure GUI via VNC in OCI aka Oracle Cloud

Virtual Network Computing, or VNC, is a connection system that allows you to use your keyboard and mouse to interact with a graphical desktop environment on a remote server. It makes managing files, software, and settings on a remote server easier for users who are not yet comfortable with the command line.

Installation:

As root user: 

 

1) Install the following rpms:

yum install xorg-x11-xauth xterm 

yum install tigervnc-server 

yum -y install xterm* xorg* xclock xauth

 

2) Enable the firewall daemon process

systemctl status firewalld

 

 3) Sudo to user for installation and start vncserver

   vncserver :2 

4) Check if availability of 5902 port [2 as VNC port, if its 1 then post would be 5901…so on]

    

   

 

5) Add rule in ip table to allow traffic to 5902 port

            iptables -I INPUT -m state --state NEW -p tcp --destination-port 8001 -j ACCEPT

fir        firewall-cmd --zone=public --add-port=5902/tcp --permanent

fir       firewall-cmd --reload

   

 

6) Access vnc.

 

 

 

lift and shift ebs to oci using cloud manager

 Lift and Shift ebs to OCI is an approach, one among many for migrating your on Premises Oracle EBS to Oracle Cloud Infrastructure. In this post, i will try to explain the steps on how we can lift and shift ebs to oci using cloud manager. It is already assumed that cloud manager is already configured to be used for your environment. You can check my previous post https://samappsdba.blogspot.com/2021/01/step-by-step-configure-ebs-cloud-manager.html on how we can configure ebs cloud manager in oracle cloud infrastructure. 

I have followed the traditional approach of lift and shift of on premise EBS to Oracle Cloud. There is an another approach now in the latest version of Cloud manager where you can create a standby environment in OCI and later promote it to primary after sync. In the traditional method, the first step would be prepare the environment and installing the backup module.

Source Environment Requirements

 Note:-My target DB will be in compute and the below listed patches are for database running on  compute only. 

Source database should be in archive log mode

Check if ntp service is configured

In the apps tier, AD/TXK should have minimum level 11 and should have the below patches    applied in application tier and database tier respectively

Patch 28371446:R12.TXK.C

Patch 29965377:R12.TXK.C

Patch 30601878:R12.TXK.C

Patch 30713114:R12.TXK.C

Patch 31314595:R12.TXK.C

database patches-31113249

Generating API Signing Key:-

 [oracle@apps ~]$ mkdir ~/.oci

Generate private key

[oracle@apps ~]$ openssl genrsa -out ~/.oci/oci_api_key.pem 2048

Generating RSA private key, 2048 bit long modulus

...........................+++

..............................................................................+++

e is 65537 (0x10001)

Generate public key

[oracle@apps ~]$ openssl rsa -pubout -in ~/.oci/oci_api_key.pem -out ~/.oci/oci_api_key_public.pem

writing RSA key

get the fingerprint:-

[oracle@apps ~]$ openssl rsa -pubout -outform DER -in ~/.oci/oci_api_key.pem | openssl md5 -c

writing RSA key

(stdin)= c6:2e:e1:d0:78:53:13:87:93:15:4a:85:6e:13:96:70

[oracle@apps ~]$

Upload the public key to the user's api signing key in OCI console.

Note: The user which you select should have the privileges to create resources in the compartments.

Note:-On the application tier server and the database tier server, the SSH configuration files (~/.ssh/config) must have the entry "ServerAliveInterval 100—under root server

Using the backup, we will now provision a new EBS instance in OCI

We will use the advance provisioning.

In this section, password validation will be done. If there are any validation issues, errors will be displayed. Correct the passwords and click Next to proceed. 

Select the Cloud Database Service option for your environment, either Compute, Virtual Machine DB System, or Exadata DB System. I had choosen Compute.

Click Next to enter the application details:-

A new feature has been added which is Zone. You can now segregate the instance as internal and external zones. We can have a load balancer shared between multiple zones of the same type. This configuration allows for two separate URLs to resolve to the same IP address and the shared load balancer will target one backend set or another.

 

Define the internal zone

In the Web Entry Point region, Choose one of the following: New Load Balancer (LBaaS), Manually Configured Load Balancer to select a manually deployed existing load balancer, or Application Tier Node to choose the primary application tier as the entry point.

If we choose New load balancer or manually configured load balancer option and file system as shared, then going forward, using Cloud manager we can add a secondary node using the "ADD Node"  

 

We can click on add here and add a secondary node if we want and click on save zone

Click next

In this section, you want CM to perform any additional tasks, you can specify in this sestion.

click next and add the ssh keys and click next.

Once the provisioning is complete, we can see the details under Environment section in Cloud Manager

There is a new feature added in this new version of Cloud manager of assigning backup policies.

Access the EBS Environment page now

If DNS is not in place, make a modification to the local /etc/hosts file and add the required ingress rules in the subnet security lists.

In the mentioned post, i have tried to demonstrate how we can lift and shift EBS 12.2 from on premise to OCI using traditional method. It wasn't a straightforward method as i had faced many challenges. I have  written a separate post https://samappsdba.blogspot.com/2021/01/oracle-e-business-suite-cloud-manager-compute-instance-configuration-issues.html on the issues encountered and it will be updated regularly as and when i encounter new issues.  Hope this post helps someone. Happy learning Cloud and EBS..:)

The complete step by step document is available at a price of $45. If you need it, please contact me over samratsinha05@gmail.com or Whatsapp at +91-8709658491

References:-https://docs.oracle.com/cd/E26401_01/doc.122/f35809/toc.htm

resize boot volume in oracle cloud infrastructure aka OCI for a Linux instance

 

The Oracle Cloud Infrastructure Block Volume service lets you scaleup the size of block volumes and boot volumes. Well, one fine day, my boot volume was short of space and i was looking for some vaccum in my  mount point. I had the challenge, where  /u01 was mounted on boot volume and it had free space of 30 GB only. My requirement was to have around 150 GB. Thanks to OCI, we can scale up the boot volume. 

P.S:-As per https://docs.oracle.com/en-us/iaas/Content/Block/Tasks/resizingavolume.htm, we cannot scale up IDE type boot volume. Also we cannot scale down the boot volume.

 

Open the navigation menu in Oracle Cloud Infrastructure console. Under Core Infrastructure, go to Compute and click Boot Volumes.

 

 

 

In the Boot Volumes list, click the boot volume you want to resize.Click Edit Size or Performance.Specify the new size in VOLUME SIZE (IN GB). You must specify a larger value than the boot volume's current size.

 

 

 

After the volume is provisioned, for the volume resize to take effect, Log on to your instance and then paste and run the rescan commands

 

1. Run the applicable rescan commands.
sudo dd iflag=direct if=/dev/<device_name> of=/dev/null count=1
echo "1" | sudo tee /sys/class/block/<device_name>/device/rescan
2. Extend the partition manually. 
[opc@apps ~]$ sudo su -
Last login: Mon Jan 11 14:17:16 GMT 2021 on pts/0
[root@apps ~]# df -kh
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        7.2G     0  7.2G   0% /dev
tmpfs           7.3G     0  7.3G   0% /dev/shm
tmpfs           7.3G   25M  7.2G   1% /run
tmpfs           7.3G     0  7.3G   0% /sys/fs/cgroup
/dev/sda3       367G  333G   35G  91% /
/dev/sda1       200M  8.6M  192M   5% /boot/efi
tmpfs           1.5G     0  1.5G   0% /run/user/994
tmpfs           1.5G     0  1.5G   0% /run/user/1000

 

Now, extend the partition

[root@apps ~]# sudo /usr/libexec/oci-growfs
CHANGE: partition=3 start=17188864 old: size=769243102 end=786431966 new: size=1031387102 end=1048575966
Confirm? [y/n]y
CHANGED: partition=3 start=17188864 old: size=769243102 end=786431966 new: size=1031387102 end=1048575966
meta-data=/dev/sda3              isize=256    agcount=39, agsize=2515200 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=0        finobt=0 spinodes=0 rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=96155387, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=4912, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 96155387 to 128923387

 

 

Confirm the changes

 

[root@apps ~]# df -kh
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        7.2G     0  7.2G   0% /dev
tmpfs           7.3G     0  7.3G   0% /dev/shm
tmpfs           7.3G   25M  7.2G   1% /run
tmpfs           7.3G     0  7.3G   0% /sys/fs/cgroup
/dev/sda3       492G  333G  160G  68% /
/dev/sda1       200M  8.6M  192M   5% /boot/efi
tmpfs           1.5G     0  1.5G   0% /run/user/994
tmpfs           1.5G     0  1.5G   0% /run/user/1000
[root@apps ~]#

 

 In this post, i have tried to demonstrate on how we can scale up the boot volume online in Oracle Cloud Infrastructure. Hope it helps someone. Happy learning Cloud.

 

 

localhost: timed out, nothing received while running ntpq -p

 I was trying to configure NTP in my Oracle Linux 7 Server. The content of /etc/ntp.conf file was

server NTP_server_1

server NTP_server_2

server NTP_server_3

server  127.127.1.0

fudge   127.127.1.0 stratum 10

driftfile /var/lib/ntp/drift

restrict default nomodify notrap nopeer noquery

Changed the firewall

[root@apps etc]# firewall-cmd --zone=public --add-service=ntp

success

[root@apps etc]# firewall-cmd --zone=public --permanent --add-service=ntp

success

[root@apps etc]# systemctl start ntpd

[root@apps etc]# systemctl enable ntpd

Now, when i tried to run ntpq -p, got the below error

Error Message:-

localhost: timed out, nothing received

***Request timed out

Solution:-

The error message indicates that the ntpq command can not access localhost.localdomain, it means the localhost can not access the local ntpq service.

The restrict option in /etc/ntp.conf allows you to control which machines can access your server.

added the below line in /etc/ntp.conf file.

[root@apps etc]# grep 127.0.0.1 /etc/ntp.conf

restrict 127.0.0.1

[root@apps etc]# service ntpd restart

Redirecting to /bin/systemctl restart ntpd.service

[root@apps etc]# ntpq -p

     remote           refid      st t when poll reach   delay   offset  jitter

==============================================================================

*LOCAL(0)        .LOCL.          10 l   12   64    1    0.000    0.000   0.000

step by step configure EBS cloud manager

In this post, i will try to give the step by step on how to configure EBS cloud manager. It is already assumed that by going through the link Oracle® E-Business Suite Cloud Manager Guide https://docs.oracle.com/cd/E26401_01/doc.122/f35809/toc.htm, all the prerequisite tasks and EBS Cloud manager topology have been have been completed. If you need an overview of EBS Cloud manager, you can go through my earlier blog https://samappsdba.blogspot.com/2021/01/oracle-e-business-suite-cloud-manager-compute-instance-configuration-issues.html

In the EBS Cloud manager compute instance, Run Oracle E-Business Suite Cloud Manager Configure Script for the First Time

-bash-4.2$ perl configure.pl

Created log file: /u01/install/APPS/apps-unlimited-ebs/out/configure_2021-01-09_09_33_15.log

===========================================================

Configuring Oracle E-Business Suite Cloud Manager VM 20.2.1

===========================================================

Enter Oracle E-Business Suite Cloud Manager Admin Password                       : *************

Enter Oracle E-Business Suite Cloud Manager Admin User OCID (Non-Federated)      : ocid1.user.oc1..********************

Enter Full path to API Private Signing Key                                       : /u01/install/APPS/.oci/oci_api_key.pem

Enter Tenancy OCID                                                               : ocid1.tenancy.oc1..*******************

Validating OCI credentials. Please wait.

Do you wish to use an existing Load Balancer??

1: yes

2: no

Enter your choice: 1

Getting list of available Load Balancers. Please wait.

Available Load Balancers:

1: Cloud_manager

Choose Load Balancer from above list: 1

Enter Load Balancer Listener Port                                                : 443

Validating Port. Please wait.

Enter CIDR Block (Range) from which Client can Access Load Balancer Listener Port: 192.0***/24

----------------------------------------------------------------------------------------------------------

Summary of Inputs

----------------------------------------------------------------------------------------------------------

Oracle E-Business Suite Cloud Manager User Name ( Non Federated )           : *****

Oracle E-Business Suite Cloud Manager User OCID ( Non Federated )           : ocid1.user.oc******************

Fingerprint of API Public Key                                               : 1d:**************

Path to Private PEM key file                                                : /u01/install/APPS/.oci/oci_api_key.pem

Tenancy OCID                                                                : ocid1.tenancy.*************

Region                                                                      : us-ashburn-1

Oracle E-Business Suite Cloud Manager VM Compartment Name                   : ebscm-compartment

Oracle E-Business Suite Cloud Manager VM Compartment OCID                   : ocid1.com****************

Network Compartment Name                                                    : ebscm-compartment

Network Compartment OCID                                                    : ocid1.compartment.*********************

Network VCN Name                                                            : ebscm-vcn

Network VCN OCID                                                            : ocid1.vcn.oc1.***************

Use an existing Load Balancer                                               : true

Load Balancer Listener Port                                                 : 443

CIDR Block (Range) from which Client can Access Load Balancer Listener Port : 192*****

Load Balancer Name                                                          : Cloud_manager

Load Balancer OCID                                                          : ocid1.*****************************

Load Balancer Visibility Type                                               : Public

Load Balancer Shape                                                         : flexible

Load Balancer Subnet Name                                                   : lbaas-subnet-phx

Load Balancer Subnet OCID                                                   : ocid1.subnet*******************

Load Balancer Subnet CIDR                                                   : 10.******

----------------------------------------------------------------------------------------------------------

Do you wish to continue??

1: yes

2: no

Enter your choice: 1

Database schema is already configured. No action needed.

Setting up Load Balancer for Oracle E-Business Suite Cloud Manager VM. This may take a few minutes. Please wait.

Checking Security Lists of LBaaS Subnet, lbaas-subnet-phx

Checking Security Lists of Oracle E-Business Suite Cloud Manager VM Subnet, ebscm-subnet-phx with source CIDR 10.0**********

============================================================================================================================================

Load Balancer Cloud_manager configuration completed. It is not ready to use until you add required rules as per any errors mentioned above.

============================================================================================================================================

==============================================================================================================================================

Register confidential application in IDCS with URL: https://193.********:443 and then re-run this script to update your IDCS configuration.

==============================================================================================================================================

============================================================================================

Finished Configuring Oracle E-Business Suite Cloud Manager VM.

Login URL: https://193.*********:443

Ensure the confidential application is correctly configured in IDCS as per the documentation.

============================================================================================

Register Oracle E-Business Suite Cloud Manager as a Confidential Application

Login to the IDCS console using the non federated user credentials which you have created during the initial setup.

Select confidential application

Under grant, click on add and select authenticator and me

Note down the following

Client ID, Client Secret and Oracle identity service tenant value.

Run Oracle E-Business Suite Cloud Manager Configure Script for the Second Time

-bash-4.2$ perl configure.pl

Created log file: /u01/install/APPS/apps-unlimited-ebs/out/configure_2021-01-09_10_27_12.log

===========================================================

Configuring Oracle E-Business Suite Cloud Manager VM 20.2.1

===========================================================

Enter Oracle E-Business Suite Cloud Manager Admin Password                       : *************

Enter IDCS Client ID                                                             : d*********************

Enter IDCS Client Secret                                                         : 6********************************

Enter IDCS Client Tenant                                                         : idcs-*****************

----------------------------------------------------------------------------------------------------------

Summary of Inputs

----------------------------------------------------------------------------------------------------------

IDCS Client ID                                                              : d*******************

IDCS Client Secret                                                          : 6********************

IDCS Client Tenant                                                          : idcs-*****************

IDCS Host                                                                   : https://idc******************

----------------------------------------------------------------------------------------------------------

Do you wish to continue??

1: yes

2: no

Enter your choice: 1

Database schema is already configured. No action needed.

Load Balancer Cloud_manager is already configured. No action needed.

Configuring IDCS

Installing Chef Server. Please wait.

Starting ChefServer.

Uploading cookbooks

Stopping Node and Job Server if running.

Starting Node and Job Server.

============================================================================================

Finished Configuring Oracle E-Business Suite Cloud Manager VM.

Login URL: https://19**********:443

Ensure the confidential application is correctly configured in IDCS as per the documentation.

============================================================================================

Update local machine etc host file.

load balancer IP        public IP for EBS Compute instance

Create Network Profile

bash-4.2$ cd /u01/install/APPS/apps-unlimited-ebs/bin

-bash-4.2$ perl ProvisionOCINetwork.pl

Program: ProvisionOCINetwork.pl started at Sun Jan 10 08:58:23 2021

Log File : /u01/install/APPS/apps-unlimited-ebs/out/ProvisionOCINetwork_Sun_Jan_10_08_58_23_2021.log

This script will be creating following subnets

EBS subnet 1: This subnet will be used in One-Click Provisioning to deploy Single Image EBS VM. For Advanced Provisioning this subnet will be used to deploy EBS apps tier VM.

EBS subnet 2: This subnet will be used in Advanced Provisioning to deploy EBS db tier VM.

LBaaS subnet: This subnet will be used for Advanced Provisioning and One-Click Provisioning to deploy Load Balancer.

Enter Y to proceed or N to exit: Y

Enter user ocid: *******************

Enter absolute path of private key of API signing key: /u01/install/APPS/.oci/oci_api_key.pem

Enter tenancy ocid: *********************************************

Validating user and fetching OCI metadata...

Enter unique identifier for the EBS network: ebscmnet

Enter EBS subnet 1 CIDR (E.g. 10.0.1.0/24): 

Enter EBS subnet 2 CIDR (E.g. 10.0.2.0/24): 

Enter LBaaS subnet CIDR (E.g. 10.0.3.0/24): 

Are you sure you want to proceed with the above inputs? [Y/N]: Y

Creating network for EBS with unique identifier ebscmnet

Executing command: /u01/install/APPS/bin/terraform init

Executing command: /u01/install/APPS/bin/terraform apply -auto-approve

Creating network profile /u01/install/APPS/apps-unlimited-ebs/ebscmnet_networkprofile.txt

Creating ingress Security Rule with source 10.****** and port 443 for Security List ebscmvm-seclist.

Creating ingress Security Rule with source 10.0.******** and port 443 for Security List ebscmvm-seclist.

Oracle EBS Cloud related network created successfully.

List of resources created:

ebscmnet_lbaas_subnet

ebscmnet_lbaas_seclist

ebscmnet_lbaas_routetable

ebscmnet_db_subnet

ebscmnet_db_seclist

ebscmnet_db_routetable

ebscmnet_apps_subnet

ebscmnet_apps_seclist

ebscmnet_apps_routetable

Program: ProvisionOCINetwork.pl completed at Sun Jan 10 09:04:03 2021

Advanced Network Profile JSON Path: /u01/install/APPS/apps-unlimited-ebs/build/ebscmnet/ebscmnet_DEFAULT_PROFILE_ADVANCED.json

OneClick Network Profile JSON Path: /u01/install/APPS/apps-unlimited-ebs/build/ebscmnet/ebscmnet_DEFAULT_PROFILE_ONECLICK.json

Execute /u01/install/APPS/apps-unlimited-ebs/bin/UploadOCINetworkProfile.pl to Upload JSON into DB

-bash-4.2$

Now run the upload script. The script needs to be uploaded twice, the first time for the One-Click Provisioning default network profile and the second time for the Advanced Provisioning default network profile.

-bash-4.2$ cd /u01/install/APPS/apps-unlimited-ebs/bin

-bash-4.2$ perl UploadOCINetworkProfile.pl

Log File : /u01/install/APPS/apps-unlimited-ebs/out/UploadOCINetworkProfile_Sun_Jan_10_09_04_56_2021.log

Enter Network profile JSON file absolute path: /u01/install/APPS/apps-unlimited-ebs/build/ebscmnet/ebscmnet_DEFAULT_PROFILE_ADVANCED.json

Enter User OCID: oci**************************

Enter Absolute path of private key of API signing key: /u01/install/APPS/.oci/oci_api_key.pem

Enter Tenancy OCID: ocid1.*************

Enter Oracle E-Business Suite Cloud Manager Admin Password:

Executing: ebscm_add_default_network_profile API for DEFAULT_PROFILE_ADVANCE

Executing Stored Procedure: ebscm_add_default_network_profile

RetCode: 0

Row count: 0

ADVANCED Network Profile uploaded successfully.

-bash-4.2$ perl UploadOCINetworkProfile.pl

Log File : /u01/install/APPS/apps-unlimited-ebs/out/UploadOCINetworkProfile_Sun_Jan_10_09_07_15_2021.log

Enter Network profile JSON file absolute path: /u01/install/APPS/apps-unlimited-ebs/build/ebscmnet/ebscmnet_DEFAULT_PROFILE_ONECLICK.json

Enter User OCID: ocid******************

Enter Absolute path of private key of API signing key: /u01/install/APPS/.oci/oci_api_key.pem

Enter Tenancy OCID: ocid1****************

Enter Oracle E-Business Suite Cloud Manager Admin Password:

Executing: ebscm_add_default_network_profile API for DEFAULT_PROFILE_ONECLICK

Executing Stored Procedure: ebscm_add_default_network_profile

RetCode: 0

Row count: 0

ONECLICK Network Profile uploaded successfully.

-bash-4.2$

Access your EBS Cloud Manager URL now

This completes the configuration of EBS Cloud Manager and on how we can launch the GUI based interface. Lots of improvisation have been done which i will be exploring now and hopefully i will be able to blog them as well. Till then happy learning Oracle Cloud and off course EBS :)

References:-

https://docs.oracle.com/cd/E26401_01/doc.122/f35809/toc.htm

                https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679340.htm#cmg_prepare_createnetrsrcs