Oracle WebLogic 14c on Oracle Linux 9

Option A: Azure Portal

• Sign in to the Azure Portal.
• Search the Marketplace for Oracle Linux 9 VM with WebLogic Server 14c (published by SecureAnyCloud) and choose Create.
• On the Basics tab, choose your subscription, resource group, region and VM size. Select SSH public key authentication and set the username to azureuser.
• On the Networking tab, allow SSH (22) from your own IP range. Open 7001 only if you need direct access to the AdminServer.
• Review and create the VM.

Option B: Azure CLI

Accept the Marketplace terms once per subscription, then create the VM:

az vm image terms accept --urn sac1647283583153:oracle-weblogic-14c-oel9:default:latest
az vm create \
  --resource-group myResourceGroup \
  --name my-weblogic-14c-vm \
  --image sac1647283583153:oracle-weblogic-14c-oel9:default:latest \
  --size Standard_D4s_v3 \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard

When the VM is running, connect as azureuser:

ssh azureuser@<public-ip>

Confirm the operating system release:

cat /etc/oracle-release

Oracle Linux Server release 9.8

First boot generates the credentials and then starts the AdminServer and NodeManager. It usually completes within a minute of the VM booting. The AdminServer is ready around thirty seconds later. Check all three units:

sudo systemctl is-active weblogic-firstboot.service weblogic.service nodemanager.service

active active active

weblogic-firstboot.service reports active because it is a one-shot unit that has exited successfully. It disables itself once it has run. The two server units stay enabled for every boot:

sudo systemctl is-enabled weblogic-firstboot.service weblogic.service nodemanager.service

disabled enabled enabled

If a unit shows activating, wait a few seconds and run the command again. The first boot log is at /var/log/weblogic-firstboot.log.

The credentials generated for this VM are stored in a root-only file:

sudo cat /home/oracle/CREDENTIALS.txt

The file looks like this, with your VM's own address and password:

# Oracle WebLogic Server 14c - per-VM credentials (generated on this VM's first boot) # Generated: 2026-09-14T14:46:45Z WEBLOGIC_USER=weblogic WEBLOGIC_PASSWORD=<your per VM password> WEBLOGIC_ADMIN_URL=http://<public-ip>:7001 WEBLOGIC_REST_URL=http://<public-ip>:7001/management/weblogic/latest NODEMANAGER_USER=weblogic NODEMANAGER_PASSWORD=<your per VM password> DOMAIN_HOME=/u01/app/oracle/product/user_projects/domains/base_domain

Store the password in your secret manager. The NodeManager credential is set to the same value.

The AdminServer listens on port 7001 and NodeManager on port 5556:

sudo ss -tlnp | grep -E ':7001|:5556'

LISTEN 0 300 [::ffff:10.0.0.16]:7001 *:* users:(("java",pid=12534,fd=669)) LISTEN 0 300 [::ffff:127.0.0.1]:7001 *:* users:(("java",pid=12534,fd=667)) LISTEN 0 300 [::1]:7001 [::]:* users:(("java",pid=12534,fd=668)) LISTEN 0 50 *:5556 *:* users:(("java",pid=11436,fd=627))

A health check against the AdminServer's welcome page should return 200:

curl -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1:7001/console/welcome/

Management requests without credentials are refused. To confirm, make an anonymous call to the REST management API and expect 401:

curl -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1:7001/management/weblogic/latest/serverRuntime

WebLogic Server 14.1.2.0.0 no longer includes the classic in-server Administration Console. The AdminServer serves a welcome page instead. It explains how to administer the domain and links to the WebLogic Remote Console download.

From your workstation, open an SSH tunnel to the VM:

ssh -L 7001:127.0.0.1:7001 azureuser@<public-ip>

Then browse to http://127.0.0.1:7001/console, which redirects to the welcome page:

To administer the domain from a graphical interface, install WebLogic Remote Console on your workstation. The welcome page links to the download. Keep the SSH tunnel open and add a connection to http://127.0.0.1:7001 with the username weblogic and the password from Step 4.

Remote Console covers deployments, data sources, JMS, security realms and monitoring.

The WebLogic REST management API is enabled and uses the same administrator credentials. This command reads the password from the credentials file and queries the AdminServer:

PW=$(sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /home/oracle/CREDENTIALS.txt)
curl -s -u "weblogic:${PW}" "http://127.0.0.1:7001/management/weblogic/latest/serverRuntime?links=none&fields=name,state,weblogicVersion"

{ "weblogicVersion": "WebLogic Server 14.1.2.0.0 Tue Nov 26 02:40:45 GMT 2024 2171472", "state": "RUNNING", "name": "AdminServer" }

Check the domain itself:

PW=$(sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /home/oracle/CREDENTIALS.txt)
curl -s -u "weblogic:${PW}" "http://127.0.0.1:7001/management/weblogic/latest/domainConfig?links=none&fields=name,domainVersion,productionModeEnabled"

{ "productionModeEnabled": true, "domainVersion": "14.1.2.0.0", "name": "base_domain" }

The WebLogic Scripting Tool (WLST) runs as the oracle user. This example connects to the running AdminServer over T3 and prints the domain and server state:

PW=$(sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /home/oracle/CREDENTIALS.txt)
cat > /tmp/wlst-check.py <<'PY' import os connect('weblogic', os.environ['WLS_PW'], 't3://127.0.0.1:7001') print('Connected to domain: ' + cmo.getName()) serverRuntime() print('AdminServer state: ' + cmo.getState()) disconnect() PY
sudo -u oracle WLS_PW="$PW" /u01/app/oracle/product/oracle_common/common/bin/wlst.sh /tmp/wlst-check.py 2>&1 | grep -E 'Connected to domain|AdminServer state' rm -f /tmp/wlst-check.py

Connected to domain: base_domain AdminServer state: RUNNING

For an interactive session, run sudo -u oracle /u01/app/oracle/product/oracle_common/common/bin/wlst.sh and use connect('weblogic', '<password>', 't3://127.0.0.1:7001'), then edit(), startEdit(), your changes, save() and activate().

To replace the generated password with your own, reset it online with WLST. Then update boot.properties so the AdminServer can still start unattended. Run the following as azureuser and replace both example values with your own:

sudo -u oracle /u01/app/oracle/product/oracle_common/common/bin/wlst.sh connect('weblogic', '<current-password>', 't3://127.0.0.1:7001') cd('/SecurityConfiguration/base_domain/Realms/myrealm/AuthenticationProviders/DefaultAuthenticator') cmo.resetUserPassword('weblogic', '<new-password>') disconnect() exit()

Then write the new password into boot.properties (WebLogic encrypts it on the next start), update your record of the password and restart the AdminServer:

printf 'username=weblogic\npassword=<new-password>\n' | sudo -u oracle tee /u01/app/oracle/product/user_projects/domains/base_domain/servers/AdminServer/security/boot.properties >/dev/null
sudo systemctl restart weblogic.service

The NodeManager credential is a separate setting in the domain security configuration and can be changed the same way through Remote Console or WLST.