Oracle WebLogic Server 15c (15.1.1) and 14c AMI User Guide
Overview
This guide covers the cloudimg Oracle WebLogic Server 15c AMI on Amazon EC2. The listing offers three versions, all built the same way: WebLogic Server on Oracle JDK 21 with a domain that systemd starts at boot and an admin password generated on each instance.
| Version you choose | Operating system | WebLogic Server | JDK | Oracle patches on the image |
|---|---|---|---|---|
| Oracle WebLogic 15c on OEL 9 | Oracle Linux 9.7 | 15.1.1.0.0 | Oracle JDK 21.0.10 | none (base release) |
| Oracle WebLogic 14c on OEL 8 | Oracle Linux 8.10 | 14.1.2.0.0 | Oracle JDK 21.0.11 | one-off patches 36990807 and 36964826 |
| Oracle WebLogic 14c on AlmaLinux 8 | AlmaLinux 8.10 | 14.1.2.0.0 | Oracle JDK 21.0.11 | one-off patches 36990807 and 36964826 |
Every step in this guide applies to all three versions unless it says otherwise.
What's included in this AMI:
- Oracle WebLogic Server (15.1.1.0.0 or 14.1.2.0.0, as above) with the middleware home at
/u01/app/oracle/productand Oracle JDK 21 at/u01/java/jdk-21 base_domainwith an AdminServer in production mode on TCP 7001, started byweblogic.serviceat boot- Node Manager on TCP 5556, started by
nodemanager.service - A per-instance admin password: on the first boot
weblogic-firstboot.servicechanges theweblogicpassword to a random value and writes it to/stage/scripts/weblogic-credentials.log, readable only by root - WLST and the REST management API; the WebLogic Remote Console connects from your desktop
- AWS CLI v2, the AWS Systems Manager Agent (running at boot) and the Amazon CloudWatch agent (installed, not configured)
- A 50 GB root EBS volume that holds everything, including
/u01. There is no separate data volume; the root volume is deleted when the instance is terminated.
The web Administration Console is gone in WebLogic 14.1.2 and 15.1.1. You administer the server with the WebLogic Remote Console (a desktop application), WLST or the REST management API. Browsing to /console shows a welcome page that links to the Remote Console.
Do not use the security group the listing suggests
When you launch from AWS Marketplace, the launch page offers a security group "based on seller settings". Do not use it. It opens TCP 22, 80, 7001, 7002, 8001 and 5556 to the whole internet (0.0.0.0/0), which exposes the AdminServer and Node Manager, both of which listen on all interfaces of the instance.
Choose or create a security group that allows only TCP 22 from your own address. You reach WebLogic through an SSH tunnel (Step 4), which needs no other inbound rule.
Licensing and Oracle support
This listing does not include an Oracle WebLogic Server licence. You must hold a valid Oracle WebLogic Server licence and use it under your agreement with Oracle. The hourly charge on the listing is cloudimg's, for installing, configuring and packaging the software on this image.
The images were built in June 2026. The 15c version carries no Oracle patches beyond the 15.1.1.0.0 base release, and the 14c versions carry only the two one-off patches above. Apply current Oracle Critical Patch Updates under your Oracle support contract before production use. AlmaLinux is not on Oracle's certified platform list for WebLogic Server; check Oracle's certification matrix for the operating system you choose.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. AlmaLinux is a trademark of the AlmaLinux OS Foundation. cloudimg is not affiliated with or endorsed by Oracle.
Prerequisites
- An AWS account and a subscription to the cloudimg Oracle WebLogic Server 15c listing
- An EC2 key pair in the region you launch in
- A security group that allows TCP 22 from your own address only (see above)
Recommended instance type: m5.large (2 vCPU, 8 GB RAM) or larger.
Step 1: Launch the instance
- Open the listing in AWS Marketplace, click Continue to Subscribe, then Continue to Configuration.
- Choose the Software Version (15c on Oracle Linux 9, or 14c on Oracle Linux 8 or AlmaLinux 8) and your region, then Continue to Launch.
- Choose Launch through EC2, then
m5.largeor larger, your VPC and subnet and your key pair. - Under Network settings, select or create a security group that allows only TCP 22 from My IP. Do not keep the security group the listing suggests.
- Launch the instance.
Step 2: Connect over SSH and read the admin password
Wait for 2/2 status checks, then connect as ec2-user:
ssh -i your-key.pem ec2-user@<public-ip-address>
The first boot takes a few minutes longer than later boots: weblogic-firstboot.service starts the AdminServer, changes the weblogic password to a random value with WLST, writes it to the credentials file and then starts weblogic.service. Check that it has finished and that WebLogic is running:
sudo systemctl status weblogic-firstboot.service
ls /var/lib/cloudimg/weblogic-firstboot.done
sudo systemctl status weblogic.service nodemanager.service
weblogic-firstboot.done exists once the password has been changed. The first-boot log is /var/log/cloudimg-weblogic-firstboot.log. Then read the password:
sudo cat /stage/scripts/weblogic-credentials.log
The file lists WEBLOGIC_USER=weblogic and WEBLOGIC_PASSWORD=... for this instance. Every instance gets its own password. While the first-boot service runs (about a minute), the AdminServer still holds the password the image was built with; this is one more reason to keep port 7001 closed in the security group.
Check that the password works:
curl -s -o /dev/null -w '%{http_code}\n' -u weblogic \
http://localhost:7001/management/weblogic/latest/serverRuntime
curl asks for the password. 200 means it works; 401 means it does not.
Step 3: Change the admin password (optional)
The generated password is unique to the instance. If you want your own, change it with WLST from the SSH session. Replace <current> with the password from the credentials file and <new> with your own strong password (at least 8 characters with a number or symbol):
sudo su - oracle
/u01/app/oracle/product/wlserver/common/bin/wlst.sh
connect('weblogic', '<current>', 't3://localhost:7001')
realm = cmo.getSecurityConfiguration().getDefaultRealm()
atn = realm.lookupAuthenticationProvider('DefaultAuthenticator')
atn.changeUserPassword('weblogic', '<current>', '<new>')
disconnect()
exit()
Then give the server the new password for its next start:
cat > /u01/app/oracle/product/user_projects/domains/base_domain/servers/AdminServer/security/boot.properties <<EOF
username=weblogic
password=<new>
EOF
chmod 600 /u01/app/oracle/product/user_projects/domains/base_domain/servers/AdminServer/security/boot.properties
exit
sudo systemctl restart weblogic.service
WebLogic encrypts boot.properties when it starts. Check the new password with the curl command from Step 2. After the change, /stage/scripts/weblogic-credentials.log still shows the first password, which no longer works.
Step 4: Reach the server through an SSH tunnel
An SSH tunnel needs no extra port in the security group:
ssh -i your-key.pem -L 7001:localhost:7001 ec2-user@<public-ip-address>
Then use http://localhost:7001 from your own machine. If you must reach the server directly, add an inbound rule for TCP 7001 from your own address only. Never open 7001 or Node Manager's 5556 to 0.0.0.0/0. SSL is not configured on the image, so use http://, not https://.
Browsing to http://localhost:7001/console takes you to the welcome page, which links to the Remote Console download. The sign-in page confirms that your credentials work:

After you sign in as weblogic:

The 14c versions show the same pages for WebLogic Server 14.1.2.
Administration with the WebLogic Remote Console
- Download the WebLogic Remote Console from GitHub Releases and install it on your desktop (Windows, macOS or Linux).
- Open the SSH tunnel from Step 4.
- Add an admin server connection with URL
http://localhost:7001, userweblogicand the password from Step 2 (or your own from Step 3).
The Remote Console manages servers, deployments, data sources, JMS and security.
The REST management API
# Server state
curl -s -u weblogic \
'http://localhost:7001/management/weblogic/latest/serverRuntime?fields=name,state'
# Deployed applications
curl -s -u weblogic \
http://localhost:7001/management/weblogic/latest/domainRuntime/serverRuntimes/AdminServer/applicationRuntimes
WLST
sudo su - oracle
/u01/app/oracle/product/wlserver/common/bin/wlst.sh
connect('weblogic', '<password>', 't3://localhost:7001')
serverRuntime()
print('Server State: ' + cmo.getState())
Directory structure
| Path | Description |
|---|---|
/u01/java/jdk-21/ |
Oracle JDK 21 (JAVA_HOME) |
/u01/app/oracle/product/ |
Middleware home (MW_HOME, ORACLE_HOME) |
/u01/app/oracle/product/wlserver/ |
WebLogic Server home (WL_HOME) |
/u01/app/oracle/product/user_projects/domains/base_domain/ |
The domain (DOMAIN_HOME) |
/stage/scripts/weblogic-credentials.log |
The admin password generated on the first boot (root only) |
/usr/local/sbin/cloudimg-weblogic-firstboot.sh |
The first-boot script run by weblogic-firstboot.service |
/var/log/cloudimg-weblogic-firstboot.log |
The first-boot log |
/u01 is a directory on the 50 GB root volume, not a separate volume. Environment variables for the oracle user are set in /home/oracle/.bash_profile; sudo su - oracle loads them.
Check the WebLogic version and patch level yourself:
sudo unzip -p /u01/app/oracle/product/wlserver/server/lib/weblogic.jar META-INF/MANIFEST.MF | grep Implementation-Version
sudo su - oracle -c '/u01/app/oracle/product/OPatch/opatch lspatches'
Managing WebLogic services
sudo systemctl start weblogic.service # start the AdminServer
sudo systemctl stop weblogic.service # stop it
sudo systemctl status weblogic.service # status
sudo systemctl status nodemanager.service # Node Manager
sudo journalctl -u weblogic.service -f # follow the server output
weblogic.service and nodemanager.service are enabled at boot. weblogic-firstboot.service runs once and then disables itself.
Troubleshooting
WebLogic is not running after the first boot. Check sudo systemctl status weblogic-firstboot.service and /var/log/cloudimg-weblogic-firstboot.log. If the first-boot service failed, /var/lib/cloudimg/weblogic-firstboot.done does not exist and the credentials file was not written; contact support with that log. The script waits up to 240 seconds for the AdminServer to start; use m5.large or larger.
WebLogic stopped later. Check sudo systemctl status weblogic.service and the server log at /u01/app/oracle/product/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log. Common causes: too little memory, another process on port 7001, or a boot.properties with a wrong password after a password change.
The server does not answer from my machine. Use the SSH tunnel from Step 4, and http://, not https://.
My login is rejected (401). Use the user weblogic and the password from /stage/scripts/weblogic-credentials.log, or the one you set in Step 3.
I cannot connect over SSH. Wait for 2/2 status checks, check the security group allows TCP 22 from your address, and connect as ec2-user with the key pair you chose (chmod 400 on the key file).
Node Manager problems. Check sudo systemctl status nodemanager.service and /u01/app/oracle/product/user_projects/domains/base_domain/nodemanager/nodemanager.log.
Security recommendations
- Use a security group that allows only TCP 22 from your address, not the one the listing suggests.
- Reach WebLogic through an SSH tunnel, or open 7001 to trusted addresses only. Never open Node Manager's port 5556.
- Configure SSL for the AdminServer before any production use.
- Apply Oracle Critical Patch Updates under your Oracle support contract.
- Keep the operating system patched (
sudo dnf update). - Back up the domain with EBS snapshots of the root volume.
What WebLogic Server 15.1.1 and 14.1.2 include
- WebLogic Server 15.1.1: Jakarta EE 9.1 applications (the
jakarta.*namespace) on JDK 17 or JDK 21 - WebLogic Server 14.1.2: Java EE 8 and Jakarta EE 8 applications (the
javax.*namespace) on JDK 17 or JDK 21 - Both: servlets, EJB, JMS, JTA transactions, JDBC data sources, clusters, managed servers and Node Manager (this image configures a single AdminServer), WLST and the REST management API
Applications built for WebLogic 14.1.2 and earlier use the javax.* packages and need migrating to jakarta.* before they run on 15.1.1.
Support
cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours.
- Email: support@cloudimg.co.uk
- Oracle documentation: WebLogic Server 15.1.1 and WebLogic Server 14.1.2
- WebLogic Remote Console: Download and documentation
Oracle software support and Oracle licences come from Oracle under your own agreement.