Accelerate Weblogic Cluster Deployment in OCI Using Marketplace Image – Part 2

Overview

In this post of the three-part blog series of accelerating Weblogic Cluster deployment in OCI using marketplace UCM image, we will go through the process of configuring the Weblogic Domain.

Part 1: Deployment of first-node of the WebLogic cluster
Part 2: Configure Weblogic Domain
Part 3: Deployment and addition of the second node of the WebLogic cluster

Configure Weblogic Domain

Once the Linux VM is ready, logon to the VM using the opc user, switch to “oracle” and unzip the JDK binaries located at /u01/zips/jcs based on the required JDK version. For this post, we are going to use JDK11.

[opc@wlclusternode01 ~]$
[opc@wlclusternode01 ~]$ sudo su - oracle
[oracle@wlclusternode01 ~]$ cd /u01/zips/jcs
[oracle@wlclusternode01 jcs]$ ls -lrt
total 4
drwxrwxr-x. 2 oracle oracle   21 Oct 15 14:28 JDK8.0
drwxrwxr-x. 4 oracle oracle   36 Oct 15 14:28 JDK
drwxrwxr-x. 2 oracle oracle   21 Oct 15 14:28 JDK11.0
drwxrwxr-x. 8 oracle oracle 4096 Oct 15 14:29 FMW
drwxrwxr-x. 3 oracle oracle   22 Oct 15 14:29 APM-AGENT
drwxrwxr-x. 3 oracle oracle   20 Oct 15 14:29 app_gateway_docker
[oracle@wlclusternode01 jcs]$ unzip /u01/zips/jcs/JDK11.0/jdk.zip -d /
Archive:  /u01/zips/jcs/JDK11.0/jdk.zip
   creating: /u01/jdk/
  inflating: /u01/jdk/README.html
   creating: /u01/jdk/bin/
  inflating: /u01/jdk/bin/jar
.....
  inflating: /u01/jdk/release
   creating: /u01/jdk/sample/
   creating: /u01/jdk/sample/missioncontrol/
   creating: /u01/jdk/sample/missioncontrol/flightrecordings/
  inflating: /u01/jdk/sample/missioncontrol/flightrecordings/java2d_demo.jfr
  inflating: /u01/jdk/sample/missioncontrol/flightrecordings/wldf.jfr
[oracle@wlclusternode01 jcs]$

Unzip the WebLogic binaries and change the permissions of /u01 folder recursively.

[oracle@wlclusternode01 jcs]$ unzip /u01/zips/jcs/FMW/14.1.1.0.0/fmiddleware.zip -d /
Archive:  /u01/zips/jcs/FMW/14.1.1.0.0/fmiddleware.zip
   creating: /u01/app/
   creating: /u01/app/oraInventory/
.....
  inflating: /u01/app/oracle/middleware/.patch_storage/LatestOPatchSession.properties
[oracle@wlclusternode01 jcs]$
[oracle@wlclusternode01 jcs]$ chmod -R 775 /u01/
[oracle@wlclusternode01 jcs]$

For configuring the Weblogic domain, we will need access to UI. Let us install the required packages and xclock.

[oracle@wlclusternode01 jcs]$ exit
logout
[opc@wlclusternode01 ~]$ sudo su -
-bash-4.2# yum install libXrender.i686 -y
-bash-4.2# yum install libX11.i686 -y
-bash-4.2# yum install -y libXrender -y
-bash-4.2# yum install libXtst -y
-bash-4.2# yum install libXtst.i686 -y
-bash-4.2# yum install libXp -y
-bash-4.2# yum install xhost -y
-bash-4.2# yum install xclock -y
-bash-4.2#

Export the DISPLAY, set ORACLE_HOME and execute config.sh to configure the Weblogic domain.

[oracle@wlclusternode01 ~]$ export DISPLAY=<IP Address of your laptop/ desktop>:0.0
[oracle@wlclusternode01 ~]$ export ORACLE_HOME=/u01/app/oracle/middleware
[oracle@wlclusternode01 ~]$ cd $ORACLE_HOME/oracle_common/common/bin
[oracle@wlclusternode01 bin]$ export PATH=$PATH:.
[oracle@wlclusternode01 bin]$ config.sh

This should open the Fusion Middleware Configuration Wizard. Click on “Create a new domain”, update base_domain under “Domain Location” with the name that you are going to use, and click on “Next”.

Click “Next” as no changes are required on page-2.

On page-3, provide the password for WebLogic user and click on “Next”.

On page-4, select “Production” as domain mode and click on “Next”.

On page-5, select “Topology” and click. on”Next”. You would notice that has enabled additional steps on the left-panel.

On page-6, click on “Add” twice to add 02 managed servers. For the first server, choose the private IP address of the VM you are configuring Weblogic on. For the second managed server, enter the next IP address in line and update the listen port to 2003. We will update the IP address in subsequent steps once node-02 of the cluster is ready. Click on “Next”.

On page-7, click on “Add”, provide a name to your Weblogic cluster and click on “Next”.

No changes are required on page-8, click on “Next”.

Same for page-9, click on “Next”.

On page-10, select “Server” under Servers, select your Weblogic Cluster name and click on the right-arrow button to move the managed servers under the Weblogic cluster.

On page-11, choose the “Unix Machine” tab, click on “Add” twice to add node manager nodes. Update the “Listen IP Address” as you did for “Managed Servers”, and click on “Next”.

Now move “Admin Server” and “ManagedServer_1” under wl_cluster_node_01 and “ManagedServer_2” under wl_cluster_node_02 by selecting the appropriate servers, machine names and by clicking the right-arrow button. Click on “Next”.

On the Summary screen (page-13), click on “Create”.

Once the configuration completes, click on “Next”.

On page-14, copy the “Domain Location” and “Admin Server URL” and click. on”Finish”.

Open port 7001 on Linux Firewall

[opc@wlclusternode01 ~]$ sudo su -
Last login: Tue Nov 15 21:44:47 GMT 2022 on pts/0
-bash-4.2# firewall-cmd --permanent --zone=public --add-port=7001/tcp
success
-bash-4.2# firewall-cmd --reload
success
-bash-4.2#

Start Weblogic Server on Node-01

Add login credentials:

-bash-4.2# sudo su - oracle
[oracle@wlclusternode01 ~]$ cd /u01/app/oracle/middleware/user_projects/domains/wlcluster_domain/
[oracle@wlclusternode01 wlcluster_domain]$ mkdir -p servers/AdminServer/security
[oracle@wlclusternode01 wlcluster_domain]$
[oracle@wlclusternode01 wlcluster_domain]$ cd servers/AdminServer/security
[oracle@wlclusternode01 security]$ vi boot.properties
username=weblogic
password=<your_weblogic_password>
wq!

Now start Weblogic server and access it using the URL you copied during domain creation. It is in the format “HTTP://<server_name>:7001/console

[oracle@wlclusternode01 security]$ export WLS_DOMAIN_HOME=/u01/app/oracle/middleware/user_projects/domains/wlcluster_domain
[oracle@wlclusternode01 security]$ cd $WLS_DOMAIN_HOME/bin
[oracle@wlclusternode01 bin]$ nohup ./startWebLogic.sh > adminserver.log &
[1] 25608
[oracle@wlclusternode01 bin]$ nohup: ignoring input and redirecting stderr to stdout
[oracle@wlclusternode01 bin]$

Start first managed server and configure node manager

Let us create the credentials file as earlier and start managedserver_1.

[oracle@wlclusternode01 bin]$ export WLS_DOMAIN_HOME=/u01/app/oracle/middleware/user_projects/domains/wlcluster_domain
[oracle@wlclusternode01 bin]$ cd $WLS_DOMAIN_HOME
[oracle@wlclusternode01 wlcluster_domain]$ mkdir -p servers/ManagedServer_1/security
[oracle@wlclusternode01 wlcluster_domain]$ cd servers/ManagedServer_1/security
[oracle@wlclusternode01 security]$ vi boot.properties
username=weblogic
password=<your_weblogic_password>
wq!
[oracle@wlclusternode01 security]$ cd $WLS_DOMAIN_HOME/bin
[oracle@wlclusternode01 bin]$ nohup ./startManagedWebLogic.sh ManagedServer_1 localhost:7001 > ManagedServer_1.log &

You can monitor the status by following ManagedServer_1.log. Once the status changes to “Running”, logon on to the Weblogic console and verify the status under Envrinvironment –> Servers.

Let us start the node manager now.

[oracle@wlclusternode01 bin]$ cd $WLS_DOMAIN_HOME/bin
[oracle@wlclusternode01 bin]$ nohup ./startNodeManager.sh > NodeManager.log &
[3] 9687
[oracle@wlclusternode01 bin]$ nohup: ignoring input and redirecting stderr to stdout

Monitor the log “NodeManager.log” and once the status changes to running, navigate to Environment –> Machines –> wl_cluster_node_01 and verify that the status is reachable under Monitoring tab.

Next Step: Deployment and addition of the second node of the WebLogic cluster