Oracle WebLogic 14c

What is Oracle WebLogic Server?

Oracle WebLogic Server is a leading Java EE and Jakarta EE application server for deploying enterprise applications. WebLogic 14c (version 14.1.2.0.0) is the current long-term support release, succeeding the 12c generation. It supports Java EE 8 and Jakarta EE 8 applications, JDBC datasources, JMS, EJBs and the full enterprise Java stack.

The AdminServer listens on port 7001 and serves the WebLogic sign-in page. You can also administer the full domain with the WebLogic Remote Console desktop application or the WLST scripting tool. A NodeManager is configured on port 5556 for managed-server lifecycle operations.

Supported Versions

The "Oracle WebLogic Server" listing offers more than one delivery option. This image provides WebLogic 14c (14.1.2.0.0) on Oracle Linux 8 or AlmaLinux 8. The listing also offers WebLogic 15c on AlmaLinux 9 or Oracle Linux 9.

All variants deploy the same core application server, with the base_domain AdminServer configuration and the same first-boot password rotation.

Launch and Connect to Your Instance

OS Variant SSH Login User

Oracle Linux 8 ec2-user

AlmaLinux 8 ec2-user

Connect with the key pair you selected at launch:

ssh -i your-key.pem ec2-user@<instance-public-ip>

First Boot - Password Generation

On the first boot of your instance, the sac-weblogic-firstboot.service systemd unit runs automatically. It does the following:

• Starts the WebLogic AdminServer.
• Generates a fresh, cryptographically random admin password that is unique to this instance.
• Rotates the weblogic user password via WLST.
• Writes the credentials to /stage/scripts/weblogic-credentials.log (readable by root only).
• Restarts the AdminServer with the new password.
• Creates the sentinel file /var/lib/sac/data/weblogic-firstboot.done.

To retrieve your credentials, run:

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

The file contains the weblogic username, the per-instance password, and the domain home path. Treat it as a secret. Only root can read it (chmod 0600).

Verifying the Installation

JDK and WebLogic Versions

/u01/java/jdk-21/bin/java -version sudo unzip -p /u01/app/oracle/product/wlserver/server/lib/weblogic.jar META-INF/MANIFEST.MF | grep Implementation-Version
sudo systemctl is-active weblogic.service nodemanager.service
sudo systemctl is-enabled weblogic.service nodemanager.service

WebLogic Sign In Page

Open a browser and go to http://<instance-public-ip>:7001/console/welcome/. You should see the Oracle WebLogic Server Sign In page:

After Sign In

Sign in with username weblogic and the password from /stage/scripts/weblogic-credentials.log. After you authenticate, the WebLogic Server 14.1.2 welcome page appears:

The welcome page confirms that the AdminServer is running and is the starting point for domain management.

WebLogic Remote Console

WebLogic Server 14.1.2 also supports the WebLogic Remote Console for administration. Download it from Oracle:

https://docs.oracle.com/en/middleware/standalone/weblogic-server/14.1.2.0/wlmgc/

After you install the Remote Console on your workstation, create a new connection:

• Connection Type: Admin Server
• URL: http://<instance-public-ip>:7001
• Username: weblogic
• Password: from /stage/scripts/weblogic-credentials.log

The Remote Console provides a full domain management interface. Use it to deploy applications, configure JDBC datasources, manage JMS, view server logs and administer security realms.

WLST (WebLogic Scripting Tool)

WLST is a command-line administration tool that is available on the instance. Switch to the oracle user and start WLST:

sudo su - oracle export JAVA_HOME=/u01/java/jdk-21 /u01/app/oracle/product/wlserver/common/bin/wlst.sh

Connect to the running AdminServer:

connect('weblogic', '<password>', 't3://127.0.0.1:7001')

These WLST commands are useful:

# Show AdminServer runtime state serverRuntime() cmo.getState()
# List deployed applications domainConfig()
ls('/AppDeployments')
# Inspect server configuration serverConfig()
cd('/Servers/AdminServer') ls()
# Exit disconnect() exit()

Managing the WebLogic Services

systemd manages the AdminServer as the weblogic.service unit and the NodeManager as nodemanager.service:

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

To start, stop or restart the AdminServer, run:

sudo systemctl start weblogic.service
sudo systemctl stop weblogic.service
sudo systemctl restart weblogic.service

Deploying Applications

To deploy a Java EE application (WAR, EAR or JAR), use the WebLogic Remote Console or WLST. To deploy with WLST, start it first:

sudo su - oracle export JAVA_HOME=/u01/java/jdk-21 /u01/app/oracle/product/wlserver/common/bin/wlst.sh

Then, in WLST, run:

connect('weblogic', '<password>', 't3://127.0.0.1:7001') deploy('myapp', '/path/to/myapp.war', targets='AdminServer')

Configuring JDBC Datasources

You can create JDBC datasources in the WebLogic Remote Console or with WLST. This is an example WLST session:

connect('weblogic', '<password>', 't3://127.0.0.1:7001') edit() startEdit() cd('/JDBCSystemResources') cmo.createJDBCSystemResource('MyDataSource')
# ... configure driver, URL, credentials activate()

Installation Layout

Path Description

/u01/java/jdk-21 JDK 21 LTS (symlink to jdk-21.0.11)

/u01/app/oracle/product WebLogic Middleware home (MW_HOME)

/u01/app/oracle/product/wlserver WebLogic Server home (WL_HOME)

/u01/app/oracle/product/user_projects/domains/base_domain AdminServer domain home

/stage/scripts/weblogic-credentials.log Per-instance credentials (root 0600)

/var/lib/sac/data/weblogic-firstboot.done Firstboot sentinel

/var/log/sac/sac-weblogic-firstboot.log Firstboot service log

Security Notes

• Unique admin password. The admin password is unique per instance and is never shared across AMIs.
• Protected credentials file. Only root can read /stage/scripts/weblogic-credentials.log (chmod 0600).
• Restrict port 7001. Port 7001 is exposed by default for WebLogic management. Restrict access with AWS Security Groups for production deployments.
• SELinux mode. SELinux ships in a non-enforcing mode, because WebLogic's ClassLoader and JNI are not compatible with enforcing SELinux. Consider additional OS-level hardening for production deployments.
• Rotate the admin password. For additional security, change the admin password after your first login, using the WebLogic Remote Console or WLST.

Support

SecureAnyCloud maintains this image. For technical support, deployment assistance, application configuration, JVM tuning and upgrades, contact SecureAnyCloud support at sales@secureanycloud.com.

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com