WebLogic 15c on Oracle Linux 9

Option A: Deploy via the Azure Portal

• Sign in to the Azure Portal.
• Choose Create a resource and search for Oracle WebLogic Server 15c on Oracle Linux 9, published by SecureAnyCloud.
• Choose Create on the product listing.
• Complete the Basics tab:
• Subscription: choose your subscription
• Resource group: create a new resource group or pick an existing one
• Virtual machine name: for example weblogic-15c
• Region: your preferred Azure region
• Image: leave at the default (Oracle WebLogic Server 15c on Oracle Linux 9)
• Size: Standard_D2s_v3 minimum. Standard_D4s_v3 or larger is recommended for production
• Authentication type: SSH public key
• Username: azureuser
• SSH public key source: paste your public key
• On the Disks tab, choose Premium SSD and size the OS disk to 64 GB or larger, depending on the size of your applications and logs.
• On the Networking tab, create or select a virtual network and subnet. Open the following inbound ports on the NIC security group:
• 22 (SSH)
• 7001 (WebLogic Admin Console, T3, IIOP, LDAP, SNMP)
• 7002 (SSL listener, optional)
• 5556 (NodeManager, optional)
• Review and create the VM. Deployment typically completes in under five minutes.

Option B: Deploy via the Azure CLI

az group create --name weblogic-rg --location eastus
az vm image terms accept --urn sac1647283583153:oracle-weblogic-15c-oel9:default:latest
az vm create \
  --resource-group weblogic-rg \
  --name weblogic-15c \
  --image sac1647283583153:oracle-weblogic-15c-oel9:default:latest \
  --size Standard_D2s_v3 \
  --admin-username azureuser \
  --ssh-key-values ~/.ssh/id_rsa.pub \
  --public-ip-sku Standard
az vm open-port --resource-group weblogic-rg --name weblogic-15c --port 22 --priority 1001
az vm open-port --resource-group weblogic-rg --name weblogic-15c --port 7001 --priority 1002
az vm open-port --resource-group weblogic-rg --name weblogic-15c --port 7002 --priority 1003
az vm open-port --resource-group weblogic-rg --name weblogic-15c --port 5556 --priority 1004

When the VM is running, retrieve its public IP and connect:

az vm show --resource-group weblogic-rg --name weblogic-15c --show-details --query publicIps -o tsv ssh azureuser@<public-ip>

On first login, you see the standard Oracle Linux 9 welcome banner. All commands below assume you are connected as azureuser.

The first time the VM boots, a one-shot systemd unit named sac-weblogic-firstboot.service performs the following steps:

• Generates a fresh, per-VM administrator password.
• Starts the AdminServer with the temporary password set at build time.
• Connects to the running domain over WLST and rotates the weblogic user password.
• Rewrites boot.properties with the new password (encrypted by WebLogic on the next start).
• Writes the new credentials to /stage/scripts/weblogic-credentials.log.
• Stops the AdminServer, marks the firstboot complete, disables itself, and starts weblogic.service cleanly.

The full first-boot hook usually takes three to five minutes. To watch the most recent log lines, run:

sudo journalctl -u sac-weblogic-firstboot.service -n 50 --no-pager

Re-run the same command every few seconds until the unit reports inactive (dead) with code=exited, status=0/SUCCESS.

When the unit exits successfully, weblogic.service starts the AdminServer in the background. Confirm that both services are healthy:

sudo systemctl status weblogic.service --no-pager sudo systemctl status nodemanager.service --no-pager

The weblogic.service unit should report Active: active (running). The AdminServer process should be listening on TCP 7001 across the loopback interface, IPv6 and the private NIC of the VM, as shown below:

When the first-boot hook has completed, the credentials file is at /stage/scripts/weblogic-credentials.log. It is owned by root with mode 0600. Read it with:

sudo cat /stage/scripts/weblogic-credentials.log

Example output:

# Oracle WebLogic Server 15c — Per-VM Credentials
# Generated: Thu Apr 30 22:18:11 UTC 2026
#
# Admin Console: http://<vm-public-ip>:7001/console WEBLOGIC_USER=weblogic WEBLOGIC_PASSWORD=<set-at-first-boot> DOMAIN_HOME=/u01/app/oracle/product/user_projects/domains/base_domain
#
# Change the password from the Console (Security Realms → myrealm → Users)
# or via WLST: connect → resetUserPassword('weblogic','<new>') → save/activate.

The screenshot below shows the same command on a freshly deployed VM, with the password redacted and the on-disk domain layout shown for reference.

Save the password to a secret manager and treat the file as sensitive material.

In your browser, go to:

http://<vm-public-ip>:7001/console

WebLogic Server 15c removed the legacy in-server /console administration console. Instead, the AdminServer serves a welcome page that confirms the server is up and explains how to administer it. The screenshot below shows the page.

You can also probe the welcome endpoint from the VM itself:

curl -sIL -o /dev/null -w 'HTTP %{http_code}\n' http://localhost:7001/console

A successful response is HTTP 200, after one or two 302 redirects to /console/welcome/.

In 15c, Oracle replaced the in-server admin console with WebLogic Remote Console. It is a standalone Electron desktop application that runs on your workstation and connects to the AdminServer over T3 / HTTP. Two flavours are available, and either works with this image:

• Desktop client: Download the installer from oracle.com/middleware/weblogic-remote-console, or follow the link on the welcome page above. Install it on your laptop or admin jump host. Then add a connection that points at http://<vm-public-ip>:7001, with username weblogic and the password from Step 4.
• Hosted Remote Console: The same UI deployed as a WAR onto a WebLogic server. Choose this if you prefer a browser-based admin surface that does not need a desktop install. Download the console-rest-ext-*.war and wls-remote-console-hosted-*.war files from the Oracle download page, then deploy them through WLST or an automation pipeline.

Both flavours expose the same management surface as the legacy in-server console. You can deploy applications, configure data sources, manage security realms, monitor JVM and JDBC pools, and edit any domain MBean.

For headless administration without a GUI, WLST (Step 7 below) and the WebLogic REST Management API are both supported and unchanged in 15c.

WebLogic Scripting Tool (WLST) is the recommended way to automate domain configuration. Run it from the VM:

sudo -u oracle bash -lc 'export JAVA_HOME=/u01/java/jdk-21; export PATH=$JAVA_HOME/bin:$PATH; /u01/app/oracle/product/wlserver/common/bin/wlst.sh -help' | head -25

You can run WLST online, connected to a running AdminServer, or offline, against the on-disk domain. For an online edit session, run:

connect('weblogic', '<password>', 't3://localhost:7001') edit() startEdit()
# ...
cd into MBean trees and call cmo.* methods ... save() activate() disconnect()

The screenshot below shows a successful WLST online connection that uses the per-VM admin password.

NodeManager is enabled in the image but stopped by default. Start it when you are ready to use it:

sudo systemctl start nodemanager.service
sudo systemctl status nodemanager.service --no-pager

To debug in the foreground, start it manually as the oracle user:

sudo -u oracle /u01/app/oracle/product/user_projects/domains/base_domain/bin/startNodeManager.sh

NodeManager listens on TCP 5556.