How to Install Oracle WebLogic Server 14c on Linux (Silent Install)

By /

Updated for 2026: the original version installed WebLogic 10.3.3 with the old binary installer. That release is old enough to vote. Below is a current install — WebLogic Server 14.1.1 on AlmaLinux/RHEL 9 with JDK 11, done the way production installs are actually done: the generic JAR installer, in silent mode, as a dedicated user.

Prerequisites

  • A Linux host (RHEL/AlmaLinux 8 or 9 used here), ~4 GB RAM free, several GB of disk
  • JDK 11 installed — WebLogic 14.1.1 is certified on JDK 8 and 11; use 11: dnf install -y java-11-openjdk-devel
  • The generic installer from Oracle: fmw_14.1.1.0.0_wls.jar (the “Generic” download, not the quick installer)
  • A dedicated, non-root user to own the install

1. Create the oracle user and directories

[root@wls1 ~]# useradd -m oracle
[root@wls1 ~]# mkdir -p /u01/app/oracle/middleware /u01/app/oraInventory
[root@wls1 ~]# chown -R oracle:oracle /u01

2. Run the installer, silently

Silent mode takes a response file and an inventory location file. Both are tiny:

[oracle@wls1 ~]$ cat /tmp/oraInst.loc
inventory_loc=/u01/app/oraInventory
inst_group=oracle

[oracle@wls1 ~]$ cat /tmp/wls.rsp
[ENGINE]
Response File Version=1.0.0.0.0
[GENERIC]
ORACLE_HOME=/u01/app/oracle/middleware
INSTALL_TYPE=WebLogic Server
[oracle@wls1 ~]$ export JAVA_HOME=/usr/lib/jvm/java-11
[oracle@wls1 ~]$ $JAVA_HOME/bin/java -jar fmw_14.1.1.0.0_wls.jar 
    -silent -responseFile /tmp/wls.rsp -invPtrLoc /tmp/oraInst.loc

When it returns, your Middleware Home is /u01/app/oracle/middleware, with WebLogic under wlserver/ and the shared tools under oracle_common/.

3. Create a domain

The Configuration Wizard has a silent mode too, via WLST. The minimal script:

[oracle@wls1 ~]$ cat /tmp/create_domain.py
readTemplate('/u01/app/oracle/middleware/wlserver/common/templates/wls/wls.jar')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('ChangeMe-2026')   # use a real password; store it in a vault
cd('/Server/AdminServer')
cmo.setName('AdminServer')
setOption('ServerStartMode', 'prod')
writeDomain('/u01/app/oracle/user_projects/domains/base_domain')
closeTemplate()
exit()

[oracle@wls1 ~]$ /u01/app/oracle/middleware/oracle_common/common/bin/wlst.sh /tmp/create_domain.py

4. Start and stop

[oracle@wls1 ~]$ cd /u01/app/oracle/user_projects/domains/base_domain
[oracle@wls1 base_domain]$ nohup ./startWebLogic.sh > adminserver.out 2>&1 &
# Admin console: http://wls1.example.local:7001/console

[oracle@wls1 base_domain]$ ./bin/stopWebLogic.sh

For managed servers, create them in the console (or WLST), then start them via the Node Manager or the domain’s bin/startManagedWebLogic.sh <name> <admin-url>.

Notes

  • Quick installer vs. generic: the quick installer (fmw_14.1.1.0.0_wls_quick.jar) is fine for a developer laptop. For anything shared or long-lived, use the generic installer and a response file — your install becomes repeatable and scriptable.
  • Patching is not optional. WebLogic is a frequent CVE target. Apply the quarterly Critical Patch Updates (SPUs) with the bsu/OPatch tooling and track Oracle’s CPU schedule.
  • Licensing: WebLogic is commercial software with per-processor licensing and real audit risk. If you’re evaluating or building something new, price it first — this is exactly where shops get surprised.

Running your own server? These guides assume you have a Linux box somewhere — see our guide to choosing a VPS in 2026 for the 7 specs that actually matter before you spin one up.

Scroll to Top