Tutorial: Manually install Oracle WebLogic Server on Azure Virtual Machines

This tutorial shows the steps to install Oracle WebLogic Server (WLS) and configure a WebLogic cluster on Azure Virtual Machines (VMs), on Windows or GNU/Linux.

In this tutorial, you learn how to:

• Create a custom virtual network and create the VMs within the network.
• Provision VMs with desired JDK and WLS installed.
• Configure a WLS domain and a WLS cluster using the Oracle Configuration Wizard.
• Deploy and run a Java EE application in the cluster.
• Expose the application to the public internet via Azure Application Gateway.
• Validate the successful configuration.

If you prefer a fully automated solution that does all of these steps on your behalf on GNU/Linux VMs, directly from the Azure portal, see Quickstart: Deploy WebLogic Server on Azure Virtual Machine using the Azure portal. You can find these offers in Azure Marketplace with a query for "WebLogic base image".

Prerequisites

• If you don't have an Azure subscription, create a free account before you begin.
• Install Azure CLI version 2.46.0 or higher to run Azure CLI commands.
  • When you're prompted, install Azure CLI extensions on first use. For more information about extensions, see Use extensions with Azure CLI.
  • Run az version to find the version and dependent libraries that are installed. To upgrade to the latest version, run az upgrade.
• You must have an Oracle account. To create an Oracle account and accept the license agreement for WebLogic Server images, follow the steps in Oracle Container Registry. Make note of your Oracle Account password and email.

Prepare the environment

In this section, you set up the infrastructure within which you install the JDK and WLS.

Assumptions

In this tutorial, you configure a WLS cluster with an administration server and two managed servers on a total of three VMs. To configure the cluster, you need to create the following three Azure VMs within the same availability set:

• The admin VM (VM name adminVM) has the administration server running.
• The managed VMs (VM names mspVM1 and mspVM2) have two managed servers running.

Sign in to Azure

If you haven't done so already, sign in to your Azure subscription by using the az login command and follow the on-screen directions.

az login

Note

If multiple Azure tenants are associated with your Azure credentials, you must specify which tenant you want to sign in to. You can do this by using the --tenant option. For example: az login --tenant contoso.onmicrosoft.com.

Create a resource group

Create a resource group with az group create. Resource group names must be globally unique within a subscription. For this reason, consider prepending some unique identifier to any names you create that must be unique. A useful technique is to use your initials followed by today's date in mmdd format. This example creates a resource group named abc1110rg in the eastus location:

export RESOURCE_GROUP_NAME=abc1110rg

az group create \
    --name ${RESOURCE_GROUP_NAME} \
    --location eastus

Create a virtual network

The resources comprising your WebLogic Server cluster must communicate with each other, and the public internet, using a virtual network. For a complete guide to planning your virtual network, see the Cloud Adoption Framework for Azure guide Plan virtual networks. For more information, see Azure Virtual Network frequently asked questions.

The example in this section creates a virtual network with address space 192.168.0.0/16 and creates a subnet used for VMs.

First, create a virtual network by using az network vnet create. The following example creates a network named myVNet:

az network vnet create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myVNet \
    --address-prefixes 192.168.0.0/24

Create a subnet for the WLS cluster by using az network vnet subnet create. The following example creates a subnet named mySubnet:

az network vnet subnet create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mySubnet \
    --vnet-name myVNet \
    --address-prefixes 192.168.0.0/25

Create a subnet for Application Gateway by using az network vnet subnet create. The following example creates a subnet named wlsVMGateway:

az network vnet subnet create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name wlsVMGateway \
    --vnet-name myVNet \
    --address-prefixes 192.168.0.128/25

Create an availability set

Create an availability set by using az vm availability-set create, as shown in the following example. Creating an availability set is optional, but we recommend it. For more information, see Example Azure infrastructure walkthrough for Windows VMs.

az vm availability-set create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myAvailabilitySet \
    --platform-fault-domain-count 2 \
    --platform-update-domain-count 2

The following sections describe the steps for installing WLS on either GNU/Linux or Windows Server. You can choose the operating system, JDK version, and WLS version according to your requirements, but you should verify that they're available in Oracle Fusion Middleware Supported System Configurations. Also, consider system and platform-specific requirements carefully before proceeding. For more information, see System Requirements and Specifications. Select the tab for your chosen operating system.

This article will use an Azure VM image that is maintained by Oracle and Microsoft containing the latest supported version of the software. For the full list of WLS base images maintained by Oracle and Microsoft, see Azure Marketplace. If you want to use Windows OS, the instructions will start with a base Windows VM and walk you through the steps of installing all of the necessary dependencies.

Oracle Linux

The Marketplace image that you use to create the VMs in this article is Oracle:weblogic-141100-jdk11-ol91:owls-141100-jdk11-ol91:latest.

Note

You can query all the available Oracle WebLogic images provided by Oracle with az vm image list az vm image list --publisher oracle --output table --all | grep "weblogic". For more information, see Oracle VM images and their deployment on Microsoft Azure.

Create an Oracle Linux machine for admin server

In this section, you create Oracle Linux machines with JDK 11 and WebLogic 14.1.1.0 installed, for the admin server and managed servers.

Create a VM using az vm create. You run the Administration Server on this VM.

The following example creates Oracle Linux VMs using user name and password pair for the authentication. If desired, you can use SSL/TLS authentication instead.

export VM_URN=Oracle:weblogic-141100-jdk11-ol91:owls-141100-jdk11-ol91:latest

az vm create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --availability-set myAvailabilitySet \
    --image ${VM_URN} \
    --size Standard_DS1_v2  \
    --admin-username azureuser \
    --admin-password Secret123456 \
    --public-ip-address "" \
    --nsg ""

Create a Windows VM and set up X-server

This tutorial uses the graphical interface of WebLogic Server to complete the installation and configuration. You use a Windows VM as a "jump box" and run an X Windows System server to view the graphical installers on the three VMs of the WLS cluster.

Follow these steps to provision a Windows 10 machine and install an X-server. If you already have a Windows machine within the same network as the Oracle Linux machine, you don't need to provision a new one from Azure. You can jump to the section that installs the X-server.

1. Use the following steps to create a Windows 10 VM from the Azure portal:

   1. Open the resource group abc1110rg from the Azure portal.
   2. Select Create to create the resource.
   3. Select Compute, search for windows 10, and then select Microsoft Windows 10.
   4. Select the plan that you want, and then select Create.
   5. Use the following values to configure the VM:
      • Virtual machine name: myWindowsVM
      • Image: Windows 10 Pro
      • Username: azureuser
      • Password: Secret123456
   6. Select the checkbox under Licensing.
   7. Select Review + create, and then select Create.

   It takes a few minutes to create the VM and supporting resources.

   After the deployment finishes, install the X server and use it to configure WebLogic Server on the Oracle Linux machines by using a graphical interface.

2. Use the following steps to install and launch the X server:

   1. Use Remote Desktop to connect to myWindowsVM. For a detailed guide, see How to connect using Remote Desktop and sign on to an Azure virtual machine running Windows. You must execute the remaining steps in this section on myWindowsVM.
   2. Download and install VcXsrv Windows X Server.
   3. Disable the firewall. To allow communication from the Linux VMs, use the following steps to turn off Windows Defender Firewall:
      1. Search for and open Windows Defender Firewall.
      2. Find Turn Windows Defender Firewall on or off, and then select Turn off in Private network settings. You can leave Public network settings alone.
      3. Select OK.
      4. Close the Windows Defender Firewall settings panel.
   4. Select X-launch from the desktop.
   5. For display settings, set the display number to -1 to use multiple windows, and then select Next.
   6. For Select how to start clients, select Start no client, and then select Next.
   7. For extra settings, select Clipboard and Primary Selection, Native opengl, and Disable access control.
   8. Select Next to finish.

   A Windows Security Alert dialog might appear with this message: "Allow VcXsrv windows X-server to communicate on these networks." Select Allow access.

Create Oracle Linux machines for managed servers

Create two VMs using az vm create. You run the managed servers on this VM.

The following example creates Oracle Linux VMs using user name and password pair for the authentication. If desired, you can use SSL/TLS authentication instead.

export VM_URN=Oracle:weblogic-141100-jdk11-ol91:owls-141100-jdk11-ol91:latest

az vm create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM1 \
    --availability-set myAvailabilitySet \
    --image ${VM_URN} \
    --size Standard_DS1_v2  \
    --admin-username azureuser \
    --admin-password Secret123456 \
    --public-ip-address "" \
    --nsg ""

az vm create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM2 \
    --availability-set myAvailabilitySet \
    --image ${VM_URN} \
    --size Standard_DS1_v2  \
    --admin-username azureuser \
    --admin-password Secret123456 \
    --public-ip-address "" \
    --nsg ""

Use the following commands to get and show the private IP addresses, which you use in later sections:

export ADMINVM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export ADMINVM_IP=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
export MSPVM1_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM1 \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export MSPVM1_IP=$(az network nic show \
    --ids ${MSPVM1_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
export MSPVM2_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM2 \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export MSPVM2_IP=$(az network nic show \
    --ids ${MSPVM2_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
echo "Private IP of adminVM: ${ADMINVM_IP}"
echo "Private IP of mspVM1: ${MSPVM1_IP}"
echo "Private IP of mspVM2: ${MSPVM2_IP}"

Now, you're ready to connect to the Oracle Linux machine to configure a WebLogic cluster with graphical interface.

Configure WebLogic Server domain and cluster

A WebLogic Server domain is a logically related group of WebLogic Server instances, and the resources running on and connected to them, that can be managed as a single administrative unit. For more information, see WebLogic Server Domains.

The foundation of high availability in WebLogic Server is the cluster. A WebLogic Server cluster is a group of WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. For more information, see Oracle WebLogic Cluster.

There are two kinds of cluster, as described in the following list. For more information, see About Dynamic Clusters.

• Dynamic cluster: A cluster that contains one or more generated (dynamic) server instances that are based on a single shared server template. When you create a dynamic cluster, the dynamic servers are preconfigured and automatically generated for you, enabling you to easily scale up the number of server instances in your dynamic cluster when you need another server capacity. You can start the dynamic servers without having to first manually configure and add them to the cluster.
• Configured cluster: A cluster in which you manually configure and add each server instance. You have to configure and add new server instance to increase server capacity.

To show you how to form a WebLogic cluster, this tutorial guides you through the process of creating a configured cluster.

Create the domain using the configuration wizard

You keep using the X-server and Oracle Configuration Wizard to create the WLS domain.

The following section shows how to create a new WLS domain on the adminVM. Make sure you're still on your Windows machine, if not, remote connect to myWindowsVM.

1. Connect to adminVM from a command prompt.

   Run the following commands on your Windows machine myWindowsVM:

   set ADMINVM_IP="192.168.0.4"
   ssh azureuser@%ADMINVM_IP%
   

2. Use the following commands to initialize the folder for domain configuration:

   sudo su
   
   export DOMAIN_PATH="/u01/domains"
   mkdir -p ${DOMAIN_PATH}
   chown oracle:oracle -R ${DOMAIN_PATH}
   

3. Use the following commands to Install the dependency for X-server:

   # install dependencies for X-server
   sudo yum install -y libXtst libSM libXrender
   # install dependencies to run a Java GUI client
   sudo yum install -y fontconfig urw-base35-fonts
   

4. Use the following commands to become the oracle user and set the DISPLAY variable:

   sudo su - oracle
   
   export DISPLAY=<my-windows-vm-private-ip>:0.0
   #export DISPLAY=192.168.0.5:0.0
   

5. Run the following command to launch the Oracle Configuration Wizard:

   bash /u01/app/wls/install/oracle/middleware/oracle_home/oracle_common/common/bin/config.sh
   

The Oracle Configuration Wizard starts and directs you to configure the domain. The following page asks for domain type and location. Select Create a new domain and set domain location to /u01/domains/wlsd. The domain configuration is saved to this folder.

Select Next, then select Create Domain Using Product Templates. Keep the default selected template, as shown in the following screenshot:

Select Next, then input Administration Account. Set the Name as weblogic and Password as Secret123456.

Select Next. For domain mode, select Production. For JDK, keep the default option.

Select Next. For advanced configurations, select Administration Server, Node Manager, and Topology.

Select Next and fill in the Administration Server name with admin. Fill in the Listen IP Address with the private IP of adminVM. The value is 192.168.0.4 in this example.

Select Next. For Node Manager Type, select Per Domain Custom Location, and fill in location with /u01/domains/wlsd/nodemanager. For Node Manager Credentials, the username is weblogic and the password is Secret123456.

Select Next. For managed servers, add the following items. Use the IP addresses you discovered earlier:

Server name	Listen address	Listen port
msp1	The private IP address of mspVM1.	8001
msp2	The private IP address of mspVM2.	8001

Select Next, then create a cluster with the name cluster1.

Select Next. Don't change the values for Server Templates and Dynamic Servers. The defaults are acceptable for a dynamic cluster.

For Assign Servers to Clusters, assign both msp1 and msp2 to cluster1.

Select Next. Add the machines adminVM, mspVM1, and mspVM2. Use the IP addresses you discovered earlier.

Name	Node manager listen address	Node manager listen port
mspVM1	The private IP address of mspVM1.	5556
mspVM2	The private IP address of mspVM2.	5556
adminVM	The private IP address of adminVM.	5556

Select Next. For Assign Servers to Machines, assign server admin to adminVM, msp1 to mspVM1, and msp2 to mspVM2.

Select Next. You're shown the Configuration Summary, which should look like the following screenshot:

Select Create. The Configuration Progress page shows the progress. All the listed items should be configured successfully.

Finally, there's an End of Configuration page to show the URL of the Administration Server.

The Administration Server isn't running, so the URL doesn't resolve. Select Next, then Finish. You've now finished configuring the wlsd domain with a cluster cluster1 including two managed servers.

Next, apply the domain configuration to mspVM1 and mspVM2.

You use the pack and unpack command to extend the domain.

Create replicas using the pack and unpack command

This tutorial uses the WLS pack and unpack command to extend the domain. For more information, see Overview of the Pack and Unpack Commands.

1. Pack the domain configuration on adminVM with the following steps, assuming you're still on adminVM and logged in with the oracle user:

   cd /u01/app/wls/install/oracle/middleware/oracle_home/oracle_common/common/bin
   bash pack.sh -domain=/u01/domains/wlsd -managed=true -template=/tmp/cluster.jar -template_name="wlsd"
   

   If the command is completed successfully, you see output similar the following example:

   [oracle@adminVM bin]$ bash pack.sh -domain=/u01/domains/wlsd -managed=true -template=/tmp/cluster.jar -template_name="wlsd"
   << read domain from "/u01/domains/wlsd"
   >>  succeed: read domain from "/u01/domains/wlsd"
   << set config option Managed to "true"
   >>  succeed: set config option Managed to "true"
   << write template to "/tmp/cluster.jar"
   ..............................
   >>  succeed: write template to "/tmp/cluster.jar"
   << close template
   >>  succeed: close template
   

   Use the following commands to copy /tmp/cluster.jar to mspVM1 and mspVM2 using scp. If prompted for key fingerprint, type yes. Enter the password Secret123456 when prompted.

   scp /tmp/cluster.jar azureuser@<mspvm1-private-ip>:/tmp/cluster.jar
   scp /tmp/cluster.jar azureuser@<mspvm2-private-ip>:/tmp/cluster.jar
   #scp /tmp/cluster.jar azureuser@192.168.0.6:/tmp/cluster.jar
   #scp /tmp/cluster.jar azureuser@192.168.0.7:/tmp/cluster.jar
   

2. Use the following instructions to apply domain configuration to mspVM1:

   Open a new command prompt, and use the following commands to connect to mspVM1. Replace 192.168.0.6 with your mspVM1 private IP address:

   set MSPVM1_IP="192.168.0.6"
   ssh azureuser@%MSPVM1_IP%
   

   You're asked for the password for the connection. For this example, the password is Secret123456.

   You're now logged into mspVM1 with user azureuser. Next, use the following commands to become the root user and update file ownership of /tmp/cluster.jar to be owned by oracle:

   sudo su
   
   chown oracle:oracle /tmp/cluster.jar
   
   export DOMAIN_PATH="/u01/domains"
   mkdir -p ${DOMAIN_PATH}
   chown oracle:oracle -R ${DOMAIN_PATH}
   

   As the oracle user, use the following commands to apply the domain configuration:

   sudo su - oracle
   
   cd /u01/app/wls/install/oracle/middleware/oracle_home/oracle_common/common/bin
   bash unpack.sh -domain=/u01/domains/wlsd -template=/tmp/cluster.jar
   

   If the command completes successfully, you see output similar to the following example:

   [oracle@mspVM1 bin]$ bash unpack.sh -domain=/u01/domains/wlsd -template=/tmp/cluster.jar
   << read template from "/tmp/cluster.jar"
   >>  succeed: read template from "/tmp/cluster.jar"
   << set config option DomainName to "wlsd"
   >>  succeed: set config option DomainName to "wlsd"
   >>  validateConfig "KeyStorePasswords"
   >>  succeed: validateConfig "KeyStorePasswords"
   << write Domain to "/u01/domains/wlsd"
   ..................................................
   >>  succeed: write Domain to "/u01/domains/wlsd"
   << close template
   >>  succeed: close template
   

3. Use the following instructions to apply domain configuration to mspVM2:

   Connect mspVM2 in a new command prompt. Replace 192.168.0.7 with your mspVM2 private IP address:

   set MSPVM2_IP="192.168.0.7"
   ssh azureuser@%MSPVM2_IP%
   

   You're asked for a password for the connection. For this example, the password is Secret123456.

   You're now logged into mspVM2 with user azureuser. Use the following commands to change to the root user and update the file ownership of /tmp/cluster.jar and initialize the folder for domain configuration:

   sudo su
   
   chown oracle:oracle /tmp/cluster.jar
   
   export DOMAIN_PATH="/u01/domains"
   mkdir -p ${DOMAIN_PATH}
   chown oracle:oracle -R ${DOMAIN_PATH}
   
   sudo su - oracle
   
   cd /u01/app/wls/install/oracle/middleware/oracle_home/oracle_common/common/bin
   bash unpack.sh -domain=/u01/domains/wlsd -template=/tmp/cluster.jar
   

You've now replicated the domain configuration on mspVM1 and mspVM2, and you're ready to start the servers.

Start servers

The steps in this section direct you to perform the following two tasks:

1. Make it so the admin and managed servers start automatically after server reboot.
2. Start the servers for immediate use.

These two tasks aren't easily separated, so the steps for the two tasks are intermixed.

Start admin

Go back to the command prompt that connects to adminVM. If you've lost it, run the following command to connect to it:

set ADMINVM_IP="192.168.0.4"
ssh azureuser@%ADMINVM_IP%

If you aren't working with the oracle user, log in with oracle:

sudo su - oracle

The following command persists the admin account to /u01/domains/wlsd/servers/admin/security/boot.properties to enable automatically starting the admin server without asking for credentials:

Replace the username and password with yours.

mkdir -p /u01/domains/wlsd/servers/admin/security

cat <<EOF >/u01/domains/wlsd/servers/admin/security/boot.properties
username=weblogic
password=Secret123456
EOF

Use the following commands to inspect the file. Be sure it has the correct ownership, permissions, and contents.

ls -la /u01/domains/wlsd/servers/admin/security/boot.properties
cat /u01/domains/wlsd/servers/admin/security/boot.properties

The output should look nearly identical to the following example:

[oracle@adminVM bin]$ ls -la /u01/domains/wlsd/servers/admin/security/boot.properties
-rw-rw-r--. 1 oracle oracle 40 Nov 28 17:00 /u01/domains/wlsd/servers/admin/security/boot.properties
[oracle@adminVM bin]$ cat /u01/domains/wlsd/servers/admin/security/boot.properties
username=weblogic
password=Secret123456

Enable the admin server and node manager to start automatically after VM restart

Create a Linux service for the WLS admin server and node manager, to start the process automatically after reboot. For more information, see Use systemd on Oracle Linux.

Exit the oracle user and sign in with the root user.

exit

sudo su

Create the Linux service for the node manager:

cat <<EOF >/etc/systemd/system/wls_nodemanager.service
[Unit]
Description=WebLogic nodemanager service
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
# Note that the following three parameters should be changed to the correct paths
# on your own system
WorkingDirectory=/u01/domains/wlsd
ExecStart="/u01/domains/wlsd/bin/startNodeManager.sh"
ExecStop="/u01/domains/wlsd/bin/stopNodeManager.sh"
User=oracle
Group=oracle
KillMode=process
LimitNOFILE=65535
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target
EOF

Create the Linux service for the admin server:

cat <<EOF >/etc/systemd/system/wls_admin.service
[Unit]
Description=WebLogic Adminserver service
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
WorkingDirectory=/u01/domains/wlsd
ExecStart="/u01/domains/wlsd/startWebLogic.sh"
ExecStop="/u01/domains/wlsd/bin/stopWebLogic.sh"
User=oracle
Group=oracle
KillMode=process
LimitNOFILE=65535
Restart=always
RestartSec=3

[Install]
WantedBy=multi-user.target
EOF

You're now ready to start the node manager and admin server on adminVM by using the following commands:

sudo systemctl enable wls_nodemanager
sudo systemctl enable wls_admin
sudo systemctl daemon-reload
sudo systemctl start wls_nodemanager
sudo systemctl start wls_admin

Check the admin server state with sudo systemctl status wls_admin -l. The Administration Server should be ready when you find similar logs:

[root@adminVM wlsd]# sudo systemctl status wls_admin -l
● wls_admin.service - WebLogic Adminserver service
Loaded: loaded (/etc/systemd/system/wls_admin.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2022-09-26 07:47:34 UTC; 54s ago
Main PID: 26738 (startWebLogic.s)
    Tasks: 61 (limit: 20654)
Memory: 649.2M

... ...

Sep 26 07:48:15 adminVM startWebLogic.sh[26802]: <Sep 26, 2022, 7:48:15,411 AM Coordinated Universal Time> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

Press Q to exit the log monitoring mode.

You can't access admin server before opening ports 7001 and 5556. Run the following command to open ports:

sudo firewall-cmd --zone=public --add-port=7001/tcp
sudo firewall-cmd --zone=public --add-port=5556/tcp
sudo firewall-cmd --runtime-to-permanent
sudo systemctl restart firewalld

At this point, you can access the admin server on the browser of myWindowsVM with the URL http://<adminvm-private-ip>:7001/console. Verify that you can view the admin server, but don't sign in yet. If the admin server isn't running, troubleshoot and resolve the problem before proceeding. The admin server isn't accessible outside of Azure.

Start msp1

Go back to the command prompt that connects to mspVM1. If you've lost it, run the following command to connect to it:

set MSPVM1_IP="192.168.0.6"
ssh azureuser@%MSPVM1_IP%

If you aren't working with oracle user, log in with oracle:

sudo su - oracle

Persist the admin account to /u01/domains/wlsd/servers/msp1/security/boot.properties to enable automatically starting msp1 without asking for credentials. Replace the username and password with yours.

mkdir -p /u01/domains/wlsd/servers/msp1/security

cat <<EOF >/u01/domains/wlsd/servers/msp1/security/boot.properties
username=weblogic
password=Secret123456
EOF

Now, you create a Linux service for node manager, to start the process automatically on machine reboot. For more information, see Use systemd on Oracle Linux.

Exit the oracle user and sign in with the root user.

exit

#Skip this command if you are root
sudo su

Create the Linux service for the node manager:

cat <<EOF >/etc/systemd/system/wls_nodemanager.service
[Unit]
Description=WebLogic nodemanager service
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
# Note that the following three parameters should be changed to the correct paths
# on your own system
WorkingDirectory=/u01/domains/wlsd
ExecStart="/u01/domains/wlsd/bin/startNodeManager.sh"
ExecStop="/u01/domains/wlsd/bin/stopNodeManager.sh"
User=oracle
Group=oracle
KillMode=process
LimitNOFILE=65535
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target
EOF

Next, start the node manager.

sudo systemctl enable wls_nodemanager
sudo systemctl daemon-reload
sudo systemctl start wls_nodemanager

If the node manager is running successfully, you see logs similar to the following example:

[root@mspVM1 azureuser]# systemctl status wls_nodemanager -l
● wls_nodemanager.service - WebLogic nodemanager service
Loaded: loaded (/etc/systemd/system/wls_nodemanager.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-27 01:23:42 UTC; 19s ago
Main PID: 107544 (startNodeManage)
    Tasks: 15 (limit: 20654)
Memory: 146.7M

... ...

Sep 27 01:23:45 mspVM1 startNodeManager.sh[107592]: <Sep 27, 2022 1:23:45 AM Coordinated Universal Time> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>
Sep 27 01:23:46 mspVM1 startNodeManager.sh[107592]: <Sep 27, 2022 1:23:46 AM Coordinated Universal Time> <INFO> <Secure socket listener started on port 5556, host /192.168.0.6>

Press Q to exit log monitoring mode.

You must open port 8001 to access application that deployed to the cluster and 5556 for communication inside the domain. Run the following command to open ports:

sudo firewall-cmd --zone=public --add-port=8001/tcp
sudo firewall-cmd --zone=public --add-port=5556/tcp
sudo firewall-cmd --runtime-to-permanent
sudo systemctl restart firewalld

Start msp2

Go back to the command prompt that connects to mspVM2. If you've lost it, run the following command to connect to it:

set MSPVM2_IP="192.168.0.7"
ssh azureuser@%MSPVM2_IP%

If you aren't working with the oracle user, sign in with oracle:

sudo su - oracle

Persist the admin account to /u01/domains/wlsd/servers/msp2/security/boot.properties to enable automatically starting msp2 without asking for credentials. Replace the username and password with yours.

mkdir -p /u01/domains/wlsd/servers/msp2/security

cat <<EOF >/u01/domains/wlsd/servers/msp2/security/boot.properties
username=weblogic
password=Secret123456
EOF

Next, create a Linux service for the node manager.

Exit the oracle user and sign in with the root user.

exit

#SKip this command if you are in root
sudo su

Create the Linux service for the node manager:

cat <<EOF >/etc/systemd/system/wls_nodemanager.service
[Unit]
Description=WebLogic nodemanager service
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
# Note that the following three parameters should be changed to the correct paths
# on your own system
WorkingDirectory=/u01/domains/wlsd
ExecStart="/u01/domains/wlsd/bin/startNodeManager.sh"
ExecStop="/u01/domains/wlsd/bin/stopNodeManager.sh"
User=oracle
Group=oracle
KillMode=process
LimitNOFILE=65535
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target
EOF

Start the node manager.

sudo systemctl enable wls_nodemanager
sudo systemctl daemon-reload
sudo systemctl start wls_nodemanager

If the node manager is running successfully, you see logs similar to the following example:

[root@mspVM2 azureuser]# systemctl status wls_nodemanager -l
● wls_nodemanager.service - WebLogic nodemanager service
Loaded: loaded (/etc/systemd/system/wls_nodemanager.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-27 01:23:42 UTC; 19s ago
Main PID: 107544 (startNodeManage)
    Tasks: 15 (limit: 20654)
Memory: 146.7M

... ...

Sep 27 01:23:45 mspVM2 startNodeManager.sh[107592]: <Sep 27, 2022 1:23:45 AM Coordinated Universal Time> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>
Sep 27 01:23:46 mspVM2 startNodeManager.sh[107592]: <Sep 27, 2022 1:23:46 AM Coordinated Universal Time> <INFO> <Secure socket listener started on port 5556, host /192.168.0.6>

Press Q to exit log monitoring mode.

Open port 8001 and 5556.

sudo firewall-cmd --zone=public --add-port=8001/tcp
sudo firewall-cmd --zone=public --add-port=5556/tcp
sudo firewall-cmd --runtime-to-permanent
sudo systemctl restart firewalld

Start managed servers

Now, open the Administration Console portal from a browser in your Windows machine myWindowsVM, and use the following steps to start the managed servers:

1. Sign in to the Administration Console portal with your admin account and password. The URL is http://<adminvm-private-ip>:7001/console/. In this example, the admin account and password are weblogic/Secret123456. You'll find the state of managed servers are Shutdown.
2. Under the Domain Structure, select Environments, Servers, and Control, select msp1 and msp2, and then select Start.
3. You may be be prompted to confirm starting the servers. If so, select Yes. You'll see the message "A request has been sent to the Node Manager to start the selected servers."
4. You can select the "refresh" icon at the top of the table to start or stop the dynamic refresh of the data in that table. This icon is shown in the next screenshot.
5. You'll find the servers are up soon.

Clean up the Windows machine

You've now completed the WLS cluster configuration. If desired, remove the Windows machine with the following commands. Alternatively, you could shut down the Windows machine myWindowsVM and continue to use it as a jump box for ongoing cluster maintenance tasks.

export WINDOWSVM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myWindowsVM \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export WINDOWSVM_NSG_ID=$(az network nic show \
    --ids ${WINDOWSVM_NIC_ID} \
    --query networkSecurityGroup.id \
    --output tsv)
export WINDOWSVM_DISK_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myWindowsVM \
    --query storageProfile.osDisk.managedDisk.id \
    --output tsv)
export WINDOWSVM_PUBLIC_IP=$(az network public-ip list \
    -g ${RESOURCE_GROUP_NAME} --query [0].id \
    --output tsv)

echo "deleting myWindowsVM"
az vm delete --resource-group ${RESOURCE_GROUP_NAME} --name myWindowsVM --yes
echo "deleting nic ${WINDOWSVM_NIC_ID}"
az network nic delete --ids ${WINDOWSVM_NIC_ID}
echo "deleting public-ip ${WINDOWSVM_PUBLIC_IP}"
az network public-ip delete --ids ${WINDOWSVM_PUBLIC_IP}
echo "deleting disk ${WINDOWSVM_DISK_ID}"
az disk delete --yes --ids ${WINDOWSVM_DISK_ID}
echo "deleting nsg ${WINDOWSVM_NSG_ID}"
az network nsg delete --ids ${WINDOWSVM_NSG_ID}

Windows Server

The Marketplace image that you use to create the VMs is MicrosoftWindowsServer:WindowsServer:2022-datacenter-azure-edition:latest.

Note

You can query all the available Windows Server images by using az vm image list, as shown in the following command: az vm image list --offer WindowsServer --all --output table. For more information, see Comparison of Standard, Datacenter, and Datacenter: Azure Edition editions of Windows Server 2022.

Create a Windows Server machine

Next, you create a basic VM, install all the required tools on it, then take a snapshot from it and create replicas based on the snapshot.

Create the basic VM using az vm create. You run the WebLogic Administration Server on it.

The following example creates a Windows Server 2022 Datacenter Azure Edition machine named adminVM. This example uses azureuser for an administrative user name and Secret123456 for the password.

az vm create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --availability-set myAvailabilitySet \
    --image MicrosoftWindowsServer:WindowsServer:2022-datacenter-azure-edition:latest \
    --size Standard_B2S \
    --public-ip-sku Standard \
    --vnet-name myVNet \
    --subnet mySubnet \
    --admin-username azureuser \
    --admin-password Secret123456

It takes a few minutes to create the VM and supporting resources.

After the deployment completes, connect to the machine. For a detailed guide on remote connection, see How to connect using Remote Desktop and sign on to an Azure virtual machine running Windows.

After you're connected, search for and open Windows Defender Firewall. Select Turn Windows Defender Firewall on or off and select Turn off Windows Defender Firewall for both private and public network settings. Select OK. Close Windows Defender Firewall. Because numerous ports must be opened during the configuration, this step greatly simplifies the process of setting up the cluster.

After the configuration is complete, lock down the WebLogic Server by following an authoritative guide on the topic, such as Securing a Production Environment for Oracle WebLogic Server.

Note

To stand up the WLS cluster, open the ports to access Administration Server, Managed Servers, and form the cluster. This tutorial turns off Windows Defender Firewall to enable the required ports. If you don't want to turn off the firewall, make sure those ports are available inside the private virtual network: 7001 for Administration Server, 8001 for Managed Servers, and 5556 for Node Manager.

Next, you install the required tools with the graphical installer. The following sections guide you to install Oracle JDK 11 and Oracle WebLogic 14c Enterprise Edition.

Download Oracle JDK 11 and Oracle WebLogic 14c

Oracle WebLogic Server 14c (14.1.1.0.0) is certified for use with JDK 11. Supported Oracle WebLogic Server 14c (14.1.1.0.0) clients are certified for use with JDK 11.0.6. For more information, see JDK 11 Certification.

To download the Oracle JDK 11 and Oracle WebLogic 14c Windows installer, follow these steps:

1. If you're not already connected, connect to adminVM, and open the Microsoft Edge browser.

2. Navigate to the Oracle JDK 11 downloads page. Select the Windows x64 Installer, accept the Oracle License Agreement, and download EXE file. You get a file similar to jdk-11.*_windows-x64_bin.exe.

3. Navigate to the Oracle Fusion Middleware Software downloads page. Select the Generic Installer, and accept the Oracle License Agreement and download the ZIP archive. You get a file similar to fmw_14.*_wls_lite_Disk1_1of1.zip. Pay attention to the support lifetime of the WebLogic Server version you download. For more information, see the Oracle Support Lifetime Policy.

Install Oracle JDK 11

This section shows you how to install Oracle JDK 11 on Windows Server.

Open the download folder that contains JDK installer. Here the installer name is jdk-11.0.16_windows-x64_bin.exe. Right click the file and select Run as administrator. Install the JDK to the default folder C:\Program Files\Java\jdk-11.0.16\.

After the installation finishes, you can validate its version in a command prompt by running the command java -version, with output similar to the following example:

java version "11.0.16" 2022-07-19 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.16+11-LTS-199)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.16+11-LTS-199, mixed mode)

Install Oracle WebLogic Server 14c Enterprise Edition

This section shows you how to install WLS 14c on Windows Server.

Open the download folder that contains WLS installer ZIP file. Here the file name is fmw_14.1.1.0.0_wls_lite_Disk1_1of1.zip. Right click the file and select Extract all to the default path.

Open a command prompt, then run the following command to install WLS:

set WLS_VERSION_PREFIX=fmw_14.1.1.0.0_wls_lite
java -jar C:\Users\azureuser\Downloads\%WLS_VERSION_PREFIX%_Disk1_1of1\%WLS_VERSION_PREFIX%_wls_lite_generic.jar

The command launches the WLS installer, as shown in the following screenshot:

Select Next. Allow Skip Auto Updates to remain selected and select Next. Set Oracle Home to C:\Oracle\Middleware\Oracle_Home, which should be the default value. Select Next.

Select installation type WebLogic Server.

Select Next. You're shown operating system warnings in the Prerequisite Checks page. Windows Server 2022 OS versions are supported on all Windows Server editions. To fix the warnings, you need to apply Patch 34500720 after the installation.

Select Next, then Install. You're shown the installation progress as shown in the following screenshot:

All of the listed installs should complete without error. Select the Next button. You're shown the Installation Complete page. Unselect any actions in the Next Steps section. You perform those steps after all the machines are ready.

Select Finished. You've now finished installing Oracle WebLogic 14c and its dependencies on adminVM. Next, you create snapshot of adminVM and prepare machines for two managed severs.

Note

For Oracle Weblogic Server Critical Patch, download the patches from My Oracle Support and apply them following "Patch an existing installation" in Install Patch and Upgrade. Make sure you've patched adminVM before taking a snapshot from it's OS disk. If you run into problems unzipping the patch file, see this MyOracleSupport document. You can skip this step for experimentation, but do not go to production with an unpatched WLS.

Create machines for managed servers

Now you've installed Oracle JDK 11 and Oracle WebLogic Server 14c Enterprise Edition on adminVM, which runs the WLS Administration Server. You still need to prepare machines to run two managed servers.

This section introduces an approach to prepare machines with the snapshot of adminVM. You create the machines from the Azure portal.

1. Stop adminVM. Open adminVM from the Azure portal, then select Stop to stop the machine. Make sure the machine is stopped completely before doing the next step.

2. Use the following steps to take a snapshot of the adminVM OS disk:

   1. Open adminVM from the Azure portal. Under Settings, select Disks, then OS Disk. Select the OS disk starting with adminVM_OsDisk_.
   2. Select Create snapshot. Under Instance details, fill in Name with snapshotAdminVMOsDisk.
   3. Select Review and create then Create. It takes several seconds to take the snapshot.

3. Use the following steps to create mspVM1:

   1. First, create the OS disk for mspVM1. Open the snapshot you created in previous step, snapshotAdminVMOsDisk. Select Create disk. Under Disk details, fill in Disk name with mspVM1_Os_Disk_1. Select Review and create, then Create. It takes several seconds. When the process is complete, select Go to resource.

   2. Create the virtual machine mspVM1. Open the OS disk you created previously. In this example, its name is mspVM1_Os_Disk_1. Select Create VM. Under Instance details, fill in Virtual machine name with mspVM1. Select Review and create then Create. Ensure you have no errors before proceeding. The process takes several minutes.

   3. The machine is created from the snapshot of adminVM, it has the same computer name as adminVM. To change computer name to mspVM1, first remote connect to the machine. The user name and password are the same as with adminVM. Open a PowerShell terminal, and run the following command:

      Rename-Computer -NewName mspvm1 -Restart
      

4. Use the following steps to create mspVM2:

   1. Create the OS disk for mspVM2. Open the snapshot you created previously. In this example, its name is snapshotAdminVMOsDisk. If you can't find the disk, search for snapshotAdminVMOsDisk in the Search resources, services and docs. Select Create disk. Under Disk details, fill in Name with mspVM2_Os_Disk_1. Select Review and create, then Create. It takes several seconds. When the process is complete, select Go to resource.

   2. Create virtual machine mspVM2. Open the OS disk you created previously, mspVM2_Os_Disk_1， select Create VM. Under Instance details, fill in Virtual machine name with mspVM2. Select Review + create then Create. It takes several minutes.

   3. Remote connect to the machine, the user name and password are the same as with adminVM. Open a PowerShell terminal, and run the following command to change computer name:

      Rename-Computer -NewName mspvm2 -Restart
      

5. Use the az vm start command to start adminVM.

   az vm start --resource-group ${RESOURCE_GROUP_NAME} --name adminVM
   

Use the following commands to get and show the private IP addresses, which you use in later sections:

export ADMINVM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export ADMINVM_IP=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
export MSPVM1_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM1 \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export MSPVM1_IP=$(az network nic show \
    --ids ${MSPVM1_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
export MSPVM2_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM2 \
    --query networkProfile.networkInterfaces'[0]'.id \
    --output tsv)
export MSPVM2_IP=$(az network nic show \
    --ids ${MSPVM2_NIC_ID} \
    --query ipConfigurations'[0]'.privateIPAddress \
    --output tsv)
echo "Private IP of adminVM: ${ADMINVM_IP}"
echo "Private IP of mspVM1: ${MSPVM1_IP}"
echo "Private IP of mspVM2: ${MSPVM2_IP}"

Now, all the machines are ready. Next, you configure a WebLogic cluster.

Configure the WebLogic Server domain and cluster

A WebLogic Server domain is a logically related group of WebLogic Server instances, and the resources running on and connected to them, that can be managed as a single administrative unit. For more information, see WebLogic Server Domains.

The foundation of high availability in WebLogic Server is the cluster. A WebLogic Server cluster is a group of WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. For more information, see Oracle WebLogic Cluster.

There are two kinds of cluster, as described in the following list. For more information, see About Dynamic Clusters.

• Dynamic cluster: A cluster that contains one or more generated (dynamic) server instances that are based on a single shared server template. When you create a dynamic cluster, the dynamic servers are preconfigured and automatically generated for you, enabling you to easily scale up the number of server instances in your dynamic cluster when you need another server capacity. You can start the dynamic servers without having to first manually configure and add them to the cluster.
• Configured cluster: A cluster in which you manually configure and add each server instance. You have to configure and add new server instance to increase server capacity.

To show you how to form a WebLogic cluster, this tutorial guides you through the process of creating a configured cluster.

Create the domain using configuration wizard

This section shows the steps to create a new WLS domain on adminVM.

Connect to adminVM, open a command prompt, and run the following command to start Oracle Configuration Wizard:

cd C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin
config.cmd

The Oracle Configuration Wizard directs you to configure the domain. The following page asks for domain type and location. Select Create a new domain and set domain location to C:\domains\wlsd. The domain configuration is saved to this folder.

Select Next, select Create Domain Using Product Templates, and keep the default selected template, as shown in the following screenshot:

Select Next, then input the Administration Account name as weblogic and the password as Secret123456, as shown in the following screenshot:

Select Next. For domain mode, select Production; for JDK, keep the default option.

Select Next. For advanced configurations, select Administration Server, Node Manager, and Topology.

Select Next, fill in the administration Server Name with admin. Fill in the Listen IP Address with the private IP for the adminVM you obtained previously. In this example, the value is 192.168.0.4.

Select Next. For Node Manager Type, select Per Domain Custom Location, and fill in the location with C:\domains\wlsd\nodemanager. This location should be filled in as the default. For Node Manager Credentials, the username is weblogic and the password is Secret123456.

Select Next. For managed servers, add the following items:

Server name	Listen address	Listen port
msp1	The private IP address of mspVM1.	8001
msp2	The private IP address of mspVM2.	8001

Select Next. Create a cluster with name cluster1. You can leave the Cluster Address, Frontend Host, and other values blank.

Select Next. Don't change the values for Server Templates or Dynamic Servers.

For Assign Servers to Clusters, assign both msp1 and msp2 to cluster1.

Select Next. Add machines adminVM, mspVM1, and mspVM2.

Name	Node manager listen address	Node manager listen port
mspVM1	The private IP address of mspVM1.	5556
mspVM2	The private IP address of mspVM2.	5556
adminVM	The private IP address of adminVM.	5556

Select Next. For Assign Servers to Machines, assign server admin to adminVM, msp1 to mspVM1, and msp2 to mspVM2.

Select Next. You're shown the Configuration Summary, as shown in the following screenshot:

Carefully examine the summary to verify everything looks as expected. Select Create. The Configuration Progress page shows the progress. All the listed items should be configured successfully.

Select Next. Finally, the URL of the Administration Server is shown. The server isn't yet running, and you don't need this URL anyway, so select Finish.

You've now finished configuring the wlsd domain with a cluster cluster1 including two managed servers.

Create replicas using the pack and unpack command

This tutorial uses the WLS pack and unpack command to extend the domain. For more information, see Overview of the Pack and Unpack Commands. Use the following steps to create the replicas:

1. First, pack the domain configuration on adminVM by following these instructions:

   Remote connect to the machine and run the following command:

   cd C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin
   pack.cmd -domain=C:\domains\wlsd -managed=true -template=C:\Temp\cluster.jar -template_name="wlsd"
   

   You're shown output similar to the following example if the command completes successfully:

   C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin>pack.cmd -domain=C:\domains\wlsd -managed=true -template=C:\Temp\cluster.jar -template_name="wlsd"
   << read domain from "C:/domains/wlsd"
   >>  succeed: read domain from "C:/domains/wlsd"
   << set config option Managed to "true"
   >>  succeed: set config option Managed to "true"
   << write template to "C:/Temp/cluster.jar"
   ..............................
   >>  succeed: write template to "C:/Temp/cluster.jar"
   << close template
   >>  succeed: close template
   

   Then, copy C:\Temp\cluster.jar to mspVM1 and mspVM2 and save to the same path.

2. Next, apply the domain configuration to mspVM1.

   Remote connect to the machine and run the following command:

   cd C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin
   unpack.cmd -domain=C:\domains\wlsd -template=C:\Temp\cluster.jar
   

   You're shown output similar to the following example if the command completes successfully:

   C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin>unpack.cmd -domain=C:\domains\wlsd -template=C:\Temp\cluster.jar
   << read template from "C:/Temp/cluster.jar"
   >>  succeed: read template from "C:/Temp/cluster.jar"
   << set config option DomainName to "wlsd"
   >>  succeed: set config option DomainName to "wlsd"
   >>  validateConfig "KeyStorePasswords"
   >>  succeed: validateConfig "KeyStorePasswords"
   << write Domain to "C:\domains\wlsd"
   ..................................................
   >>  succeed: write Domain to "C:\domains\wlsd"
   << close template
   >>  succeed: close template
   

   Next, rename the configuration file config_bootstrap.xml to config.xml. In the command prompt, run the following commands:

   cd C:\domains\wlsd\config
   ren config_bootstrap.xml config.xml
   

3. Next, apply the domain configuration to mspVM2.

   Remote connect to the machine and run the following command:

   cd C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin
   unpack.cmd -domain=C:\domains\wlsd -template=C:\Temp\cluster.jar
   

   Then, rename the configuration file config_bootstrap.xml to config.xml:

   cd C:\domains\wlsd\config
   ren config_bootstrap.xml config.xml
   

Note

The unpack command generates the config_bootstrap.xml file based on the config.xml file in the template, which may cause error java.io.FileNotFoundException: C:\domains\wlsd\.\config\config.xml (The system cannot find the file specified) when starting the managed server. This tutorial renames config_bootstrap.xml to config.xml to avoid this problem.

You've now replicated the domain configuration on mspVM1 and mspVM2, so you're ready to start the servers.

Set up the WebLogic Server as a Windows service

This section uses a Windows service to configure Oracle WebLogic Server to start automatically when you boot a Windows host computer. For more information, see Setting Up a WebLogic Server Instance as a Windows Service.

Note

This section doesn't enable graceful shutdowns. If you use the Microsoft Management Console to stop a server instance, it kills the server's Java Virtual Machine (JVM). If you kill the JVM, the server immediately stops all processing. To set up graceful shutdowns, see Enabling Graceful Shutdowns.

Set up the Administration Server as Windows service

You're now ready to start the Administration Server. Use the following instructions to create a Windows service to start the Administration Server:

Remote connect to adminVM. In the command prompt, change to the directory C:\domains\wlsd. Enter startWebLogic.cmd. For the credentials of the admin account, enter weblogic for the username and Secret123456 for the password. If the server is running, it prints a line to standard out that is similar to the following output:

... ...
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:Secret123456

... ...
<Oct 18, 2022, 6:48:56,997 AM Coordinated Universal Time> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

Create a Boot Identity file C:\domains\wlsd\servers\admin\security\boot.properties and save the admin account user name and password to the file. For more information, see Boot Identity Files. Paste the following text into a command prompt:

MKDIR C:\domains\wlsd\servers\admin\security
TYPE CON > C:\domains\wlsd\servers\admin\security\boot.properties
username=weblogic
password=Secret123456

Press Enter, Ctrl+Z, Enter.

Next, create a Windows service for the Administration Server. Paste the following text into a command prompt. Press Enter, Ctrl+Z, Enter.

TYPE CON > C:\domains\wlsd\autoStartup.cmd
echo off
SETLOCAL
set MW_HOME=C:\Oracle\Middleware\Oracle_Home
set DOMAIN_NAME=wlsd
set USERDOMAIN_HOME=C:\domains\wlsd
set SERVER_NAME=admin
set WL_HOME=C:\Oracle\Middleware\Oracle_Home\wlserver
set DOMAIN_PRODUCTION_MODE=true
call "C:\domains\wlsd\bin\setDomainEnv.cmd"
call "C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin\installSvc.cmd"
ENDLOCAL

Run the newly created file. Enter C:\domains\wlsd\autoStartup.cmd. The command prompt runs the script as a batch file.

If the script runs successfully, it creates a Windows service named wlsd_admin and prints a line to standard out that is similar to the following output:

... ...
wlsvc wlsd_admin installed.

This example uses node manager to control managed servers. Create a Windows service for node manager on adminVM.

In the command prompt, change to the directory C:\domains\wlsd\bin. Enter installNodeMgrSvc.cmd. If the service is created successfully, it prints a line to standard out that is similar to the following output:

... ...
Oracle Weblogic wlsd NodeManager (C_Oracle_MIDDLE~1_ORACLE~1_wlserver) installed.

Finally, restart the machine to activate the Windows services.

Configure and start the managed servers

Next, set up the node manager as a Windows service on mspVM1 and mspVM2.

Remote connect to mspVM1 and mspVM2, open a command prompt, and then change to directory C:\domains\wlsd\bin. Enter installNodeMgrSvc.cmd. If the service is created successfully, it prints a line to standard out that is similar to the following output:

... ...
Oracle Weblogic wlsd NodeManager (C_Oracle_MIDDLE~1_ORACLE~1_wlserver) installed.

Restart mspVM1 and mspVM2 to start the node manager.

Next, start the managed server from the Administration Console portal. Open a browser on adminVM and use the following steps to start the server:

1. Sign in to the Administration Console portal with your admin account and password. The URL is http://<adminvm-private-ip>:7001/console/. In this example, the admin account and password are weblogic/Secret123456. You'll find the state of managed servers are Shutdown.
2. Under the Domain Structure, select Environments, Servers, and Control, select msp1 and msp2, and then select Start.
3. You may be be prompted to confirm starting the servers. If so, select Yes. You'll see the message "A request has been sent to the Node Manager to start the selected servers."
4. You can select the "refresh" icon at the top of the table to start or stop the dynamic refresh of the data in that table. This icon is shown in the next screenshot.
5. You'll find the servers are up soon.

Set up the managed server as a Windows service

The steps in this section show how to create a Windows service for each of the managed servers. This service starts the managed server automatically when the machine is rebooted.

1. Use the following instructions to set up msp1 as a Windows service:

   Remote connect to mspVM1. Open a command prompt and paste the following text, replacing ADMIN_URL with the actual value. Press Enter, Ctrl+Z, Enter.

   TYPE CON > C:\domains\wlsd\autoStartup.cmd
   echo off
   SETLOCAL
   set MW_HOME=C:\Oracle\Middleware\Oracle_Home
   set DOMAIN_NAME=wlsd
   set USERDOMAIN_HOME=C:\domains\wlsd
   set SERVER_NAME=msp1
   set ADMIN_URL=http://192.168.0.4:7001
   set WL_HOME=C:\Oracle\Middleware\Oracle_Home\wlserver
   set DOMAIN_PRODUCTION_MODE=true
   call "C:\domains\wlsd\bin\setDomainEnv.cmd"
   call "C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin\installSvc.cmd"
   ENDLOCAL
   

   Enter C:\domains\wlsd\autoStartup.cmd. The command prompt runs the script as a batch file.

   Create a Boot Identity file C:\domains\wlsd\servers\msp1\security\boot.properties and save the admin account user name and password to the file.

   Paste the following text into a command prompt:

   MKDIR C:\domains\wlsd\servers\msp1\security
   TYPE CON > C:\domains\wlsd\servers\msp1\security\boot.properties
   username=weblogic
   password=Secret123456
   

   Press Enter, Ctrl+Z, Enter.

2. Set up msp2 as a Windows service

   Remote connect to mspVM2. Open a command prompt and paste the following text, replacing ADMIN_URL with the actual value. Press Enter, Ctrl+Z, Enter.

   TYPE CON > C:\domains\wlsd\autoStartup.cmd
   echo off
   SETLOCAL
   set MW_HOME=C:\Oracle\Middleware\Oracle_Home
   set DOMAIN_NAME=wlsd
   set USERDOMAIN_HOME=C:\domains\wlsd
   set SERVER_NAME=msp2
   set ADMIN_URL=http://192.168.0.4:7001
   set WL_HOME=C:\Oracle\Middleware\Oracle_Home\wlserver
   set DOMAIN_PRODUCTION_MODE=true
   call "C:\domains\wlsd\bin\setDomainEnv.cmd"
   call "C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin\installSvc.cmd"
   ENDLOCAL
   

   Enter C:\domains\wlsd\autoStartup.cmd. The command prompt runs the script as a batch file.

   Create a Boot Identity file C:\domains\wlsd\servers\msp1\security\boot.properties and save the admin account user name and password to the file.

   Paste the following text into a command prompt:

   MKDIR C:\domains\wlsd\servers\msp2\security
   TYPE CON > C:\domains\wlsd\servers\msp2\security\boot.properties
   username=weblogic
   password=Secret123456
   

   Press Enter, Ctrl+Z, Enter.

Now, the managed servers start up automatically when the machine restarts.

Remove the public IPs

In order to remote connect to the Windows Server machines, all of them are assigned a public IP address. Now that the configuration is done, there's no need to keep the public IP address. For security, remove the public IP addresses from adminVM, mspVM1, and mspVM2, as shown in the following example. For more information, see Dissociate a public IP address from an Azure VM.

export ADMINVM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export ADMINVM_NIC_NAME=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query name \
    --output tsv)
export ADMINVM_NIC_IP_CONFIG=$(az network nic show \
    --ids $ADMINVM_NIC_ID \
    --query ipConfigurations[0].name \
    --output tsv)
export ADMINVM_PUBLIC_IP=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query ipConfigurations[0].publicIpAddress.id \
    --output tsv)
export ADMINVM_NSG_ID=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query networkSecurityGroup.id \
    --output tsv)

az network nic ip-config update \
    --name ${ADMINVM_NIC_IP_CONFIG} \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --nic-name ${ADMINVM_NIC_NAME} \
    --remove PublicIpAddress
az network public-ip delete --ids ${ADMINVM_PUBLIC_IP}
az network nic update \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name ${ADMINVM_NIC_NAME} \
    --remove networkSecurityGroup
az network nsg delete --ids ${ADMINVM_NSG_ID}

export MSPVM1VM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM1 \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export MSPVM1VM_NIC_NAME=$(az network nic show \
    --ids ${MSPVM1VM_NIC_ID} \
    --query name \
    --output tsv)
export MSPVM1VM_NIC_IP_CONFIG=$(az network nic show \
    --ids ${MSPVM1VM_NIC_ID} \
    --query ipConfigurations[0].name \
    --output tsv)
export MSPVM1VM_PUBLIC_IP=$(az network nic show \
    --ids ${MSPVM1VM_NIC_ID} \
    --query ipConfigurations[0].publicIpAddress.id \
    --output tsv)
export MSPVM1VM_NSG_ID=$(az network nic show \
    --ids ${MSPVM1VM_NIC_ID} \
    --query networkSecurityGroup.id \
    --output tsv)

az network nic ip-config update \
    --name ${MSPVM1VM_NIC_IP_CONFIG} \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --nic-name ${MSPVM1VM_NIC_NAME} \
    --remove PublicIpAddress
az network public-ip delete --ids ${MSPVM1VM_PUBLIC_IP}
az network nic update \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name ${MSPVM1VM_NIC_NAME} \
    --remove networkSecurityGroup
az network nsg delete --ids ${MSPVM1VM_NSG_ID}

export MSPVM2VM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM2 \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export MSPVM2VM_NIC_NAME=$(az network nic show \
    --ids ${MSPVM2VM_NIC_ID} \
    --query name \
    --output tsv)
export MSPVM2VM_NIC_IP_CONFIG=$(az network nic show \
    --ids ${MSPVM2VM_NIC_ID} \
    --query ipConfigurations[0].name \
    --output tsv)
export MSPVM2VM_PUBLIC_IP=$(az network nic show \
    --ids ${MSPVM2VM_NIC_ID} \
    --query ipConfigurations[0].publicIpAddress.id \
    --output tsv)
export MSPVM2VM_NSG_ID=$(az network nic show \
    --ids ${MSPVM2VM_NIC_ID} \
    --query networkSecurityGroup.id \
    --output tsv)

az network nic ip-config update \
    --name ${MSPVM2VM_NIC_IP_CONFIG} \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --nic-name ${MSPVM2VM_NIC_NAME} \
    --remove PublicIpAddress
az network public-ip delete --ids ${MSPVM2VM_PUBLIC_IP}
az network nic update \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name ${MSPVM2VM_NIC_NAME} \
    --remove networkSecurityGroup
az network nsg delete --ids ${MSPVM2VM_NSG_ID}

Expose WLS with Azure Application Gateway

Now that you've created the WebLogic Server (WLS) cluster on either Windows or GNU/Linux virtual machines, this section walks you through the process of exposing WLS to the internet with Azure Application Gateway.

Create the Azure Application Gateway

To expose WLS to the internet, a public IP address is required. Create the public IP address and then associate an Azure Application gateway with it. Use az network public-ip create to create it, as shown in the following example:

az network public-ip create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myAGPublicIPAddress \
    --allocation-method Static \
    --sku Standard

You add the backend servers to Application Gateway backend pool. Query backend IP addresses using the following commands:

export ADMINVM_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name adminVM \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export ADMINVM_IP=$(az network nic show \
    --ids ${ADMINVM_NIC_ID} \
    --query ipConfigurations[0].privateIPAddress \
    --output tsv)
export MSPVM1_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM1 \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export MSPVM1_IP=$(az network nic show \
    --ids ${MSPVM1_NIC_ID} \
    --query ipConfigurations[0].privateIPAddress \
    --output tsv)
export MSPVM2_NIC_ID=$(az vm show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name mspVM2 \
    --query networkProfile.networkInterfaces[0].id \
    --output tsv)
export MSPVM2_IP=$(az network nic show \
    --ids ${MSPVM2_NIC_ID} \
    --query ipConfigurations[0].privateIPAddress \
    --output tsv)

Next, create an Azure Application Gateway. The following example creates an application gateway with managed servers in the default backend pool:

az network application-gateway create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myAppGateway \
    --public-ip-address myAGPublicIPAddress \
    --location eastus \
    --capacity 2 \
    --http-settings-port 80 \
    --http-settings-protocol Http \
    --frontend-port 80 \
    --sku Standard_V2 \
    --subnet wlsVMGateway \
    --vnet-name myVNet \
    --priority 1001 \
    --servers ${MSPVM1_IP} ${MSPVM2_IP}

The managed servers expose their workloads with port 8001. Use the following commands to update the appGatewayBackendHttpSettings by specifying backend port 8001 and creating a probe for it:

az network application-gateway probe create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --gateway-name myAppGateway \
    --name clusterProbe \
    --protocol http \
    --host 127.0.0.1 \
    --path /weblogic/ready

az network application-gateway http-settings update \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --gateway-name myAppGateway \
    --name appGatewayBackendHttpSettings \
    --port 8001 \
    --probe clusterProbe

The next commands provision a basic rule rule1. This example adds a path to the Administration Server. First, use the following commands to create a URL path map:

az network application-gateway address-pool create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --gateway-name myAppGateway \
    --name adminServerAddressPool \
    --servers ${ADMINVM_IP}

az network application-gateway probe create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --gateway-name myAppGateway \
    --name adminProbe \
    --protocol http \
    --host 127.0.0.1 \
    --path /weblogic/ready

az network application-gateway http-settings create \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --gateway-name myAppGateway \
    --name adminBackendSettings \
    --port 7001 \
    --protocol Http \
    --probe adminProbe

az network application-gateway url-path-map create \
    --gateway-name myAppGateway \
    --name urlpathmap \
    --paths /console/* \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --address-pool adminServerAddressPool \
    --default-address-pool appGatewayBackendPool \
    --default-http-settings appGatewayBackendHttpSettings \
    --http-settings adminBackendSettings \
    --rule-name consolePathRule

Next, use az network application-gateway rule update to update the rule type to be PathBasedRouting.

az network application-gateway rule update \
    --gateway-name myAppGateway \
    --name rule1 \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --http-listener appGatewayHttpListener \
    --rule-type PathBasedRouting \
    --url-path-map urlpathmap \
    --priority 1001 \
    --address-pool appGatewayBackendPool \
    --http-settings appGatewayBackendHttpSettings

You're now able to access the Administration Server with the URL http://<gateway-public-ip-address>/console/. Run the following commands to get the URL:

export APPGATEWAY_IP=$(az network public-ip show \
    --resource-group ${RESOURCE_GROUP_NAME} \
    --name myAGPublicIPAddress \
    --query [ipAddress] \
    --output tsv)
echo "admin console URL is http://${APPGATEWAY_IP}/console/"

Verify that you can log into the Administration Server console. If you can't, troubleshoot and resolve the problem before proceeding.

Note

This example sets up simple access to the WebLogic servers with HTTP. If you want secure access, configure SSL/TLS termination by follow the instructions in End to end TLS with Application Gateway.

This example exposes the Administration Server console via the Application Gateway. Don't do this in a production environment.

Deploy a sample application

This section shows you how to deploy a simple application to the WLS cluster. First, download testwebapp.war from Oracle and save the file to your local filesystem. Then, use the following steps to deploy the application:

1. Open a web browser.
2. Navigate to the Administration Console portal with the URL http://<gateway-public-ip-address>/console/, then sign in with your admin account and password. In this example, they're weblogic/Secret123456.
3. Under the Change Center, if such a button exists, select Lock and Edit. If this button doesn't exist, verify that some text such as "Future changes will automatically be activated as you modify, add or delete items in this domain" exists under Change Center.
4. Under Domain Structure, select Deployments. If you see an error message similar to Unexpected error encountered while obtaining monitoring information for applications., you can safely ignore it. Select Configuration then Install. Nestled within the text is a hyperlink with the text Upload your files. Select it. Select Choose file , then select the testwebapp.war built in the preceding step. Select Next then Next.
5. Ensure that Install this deployment as an application is selected. Select Next.
6. Under Available targets for cargo-tracker, select deployment target cluster1, select Next, then select Finish.
7. Under the Change Center, if such a button exists, select Activate Changes. You must complete this step. Failure to complete this step causes the changes you made to not take effect. If this button doesn't exist, verify that some text such as Future changes will automatically be activated as you modify, add or delete items in this domain exists under Change Center.
8. Under Domain Structure, select Deployments then Control. Select cargo-tracker then select Start, Servicing all requests.
9. Select Yes.
10. You're shown a message saying Start requests have been sent to the selected deployments. The status of the application must be Active.

Test the WLS cluster configuration

You've now finished configuring the WLS cluster and deploying the Java EE application to it. Use the following steps to access the application to validate all the settings:

1. Open a web browser.
2. Navigate to the application with the URL http://<gateway-public-ip-address>/testwebapp/.

Clean up resources

Delete abc1110rg with the following command:

az group delete --name ${RESOURCE_GROUP_NAME} --yes --no-wait

Next steps

Continue to explore options to run WLS on Azure.

Learn more about Oracle WebLogic on Azure