SecureAnyCloud
Deployment guide

Oracle WebLogic 14c Windows

Overview

Oracle WebLogic Server 14c is an enterprise Java application server. This guide covers deploying and configuring Oracle WebLogic Server 14c (14.1.2.0.0) on Windows Server, using SecureAnyCloud AMIs from the AWS Marketplace. The AMI gives you a preconfigured WebLogic domain that starts automatically at boot.

What you get:

  • Oracle WebLogic Server 14c (14.1.2.0.0) with Java EE 8 support
  • Oracle JDK 21 LTS
  • Preconfigured WebLogic domain with the Admin Server on port 7001
  • A Scheduled Task for automatic startup at boot
  • Oracle software installed on a separate D: drive (20 GB EBS volume)
  • AWS CLI, Systems Manager Agent, and CloudWatch Agent

Supported Operating Systems: Windows Server 2022, Windows Server 2019

Important change in WebLogic 14.1.2: WebLogic Server 14.1.2 removes the traditional web-based Administration Console. You now administer the server with the WebLogic Remote Console (a desktop application) or the REST Management API. See the Administration section below for details.

Prerequisites

Before you launch this AMI, make sure you have:

  • An active AWS account
  • An active subscription to the Oracle WebLogic 14c on Windows listing on AWS Marketplace
  • An RDP client (Remote Desktop Connection) on your local machine
  • Familiarity with EC2 instance management

Recommended Instance Type: m5.large (2 vCPU, 8 GB RAM) or larger for production workloads.

1

Launch the AMI

  • Go to the AWS Marketplace and search for "Oracle WebLogic 14c Windows SecureAnyCloud"
  • Click Continue to Subscribe, accept the terms, and then click Continue to Configuration
  • Select your preferred Region and Software Version (Windows Server 2022 or 2019)
  • Click Continue to Launch
  • Choose Launch through EC2 for full control over instance configuration
  • Select your instance type (m5.large is recommended)
  • Configure your Security Group with the following inbound rules.

Port Protocol Source Purpose

3389 TCP Your IP RDP access

7001 TCP Your IP WebLogic Server / REST API

7002 TCP Your IP WebLogic Server (SSL)

Important: Restrict all ports to your IP address only. Never open them to 0.0.0.0/0.

2

Connect via RDP

  • In the EC2 console, select your instance and click Connect
  • Choose the RDP client tab
  • Click Get password and upload your key pair (.pem file) to decrypt the Administrator password
  • Download the Remote Desktop file or note the Public DNS

Then open your RDP client and connect with these details:

  • Computer: Your instance's Public IP or DNS
  • Username: Administrator
  • Password: The decrypted password from the EC2 console

Alternatively, use SSM Session Manager to get console access without opening port 3389:

https://us-east-1.console.aws.amazon.com/systems-manager/session-manager/<instance-id>?region=us-east-1
3

Retrieve WebLogic Credentials

The WebLogic admin password is unique to each instance. To retrieve it, open a Command Prompt or PowerShell window and run:

type C:\CREDENTIALS.txt
  • Username: weblogic
  • Password: unique per instance (see C:\CREDENTIALS.txt)

Important: Change the password after your first sign-in. See the Security Hardening section below.

4

Verify the Installation

Open PowerShell and verify the WebLogic installation:

# Check JDK version & "$env:JAVA_HOME\bin\java.exe" -version
# Check WebLogic home exists Test-Path D:\Oracle\Middleware\wlserver\server\bin\setWLSEnv.cmd
# Check domain exists Test-Path D:\Oracle\Middleware\user_projects\domains\base_domain\config\config.xml
# Check scheduled task Get-ScheduledTask -TaskName OracleWebLogicServer | Select TaskName, State
# Check D: drive Get-Volume -DriveLetter D
5

Start WebLogic Server

WebLogic is configured to start automatically at boot via a Scheduled Task. To start it manually:

Start-ScheduledTask -TaskName OracleWebLogicServer

Wait approximately 60 to 90 seconds for the server to start. Then verify that it is running:

# Check the scheduled task state Get-ScheduledTask -TaskName OracleWebLogicServer | Select State
# Test the REST API $cred = Get-Content C:\CREDENTIALS.txt | Select-String "Password" | ForEach-Object { ($_ -split ": ")[1] } curl.exe -u "weblogic:$cred" http://localhost:7001/management/weblogic/latest/serverRuntime?fields=name,state
6

Access the Server

Navigate to http://<public-ip>:7001/console/ in your browser. You see the Welcome to WebLogic Server 14.1.2 page.

In WebLogic 14.1.2, the WebLogic Remote Console desktop application replaces the traditional web-based Admin Console, which has been removed.

To verify that your credentials work, open the Sign In page:

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

Enter your username and password from C:\CREDENTIALS.txt and click Sign In. A successful sign-in redirects you back to the Welcome page.

You can also verify your credentials through the REST API from PowerShell:

curl.exe -u "weblogic:<your-password>" http://localhost:7001/management/weblogic/latest/serverRuntime?fields=name,state

Directory Structure

Path Description

D:\Oracle\Java\jdk-21.x.x\ Oracle JDK 21 LTS (JAVA_HOME)

D:\Oracle\Middleware\ Middleware Home (MW_HOME / ORACLE_HOME)

D:\Oracle\Middleware\wlserver\ WebLogic Server Home (WL_HOME)

D:\Oracle\Middleware\user_projects\domains\base_domain\ Default Domain (DOMAIN_HOME)

D:\Oracle\oraInventory\ Oracle Inventory

C:\CREDENTIALS.txt Admin credentials file

The following environment variables are set system-wide:

JAVA_HOME = D:\Oracle\Java\jdk-21.x.x MW_HOME = D:\Oracle\Middleware WL_HOME = D:\Oracle\Middleware\wlserver DOMAIN_HOME = D:\Oracle\Middleware\user_projects\domains\base_domain

Administration with WebLogic Remote Console

WebLogic 14.1.2 replaces the traditional web-based Administration Console with the WebLogic Remote Console, a modern desktop application. You have three ways to administer the server.

Option 1: WebLogic Remote Console (Desktop Application)

  • Download the WebLogic Remote Console from GitHub Releases
  • Install the application on your desktop (available for Windows, macOS, and Linux)
  • Launch the Remote Console and connect to your WebLogic Server with these details:
  • URL: http://<public-ip>:7001
  • Username: weblogic
  • Password: Your admin password from CREDENTIALS.txt

Option 2: REST Management API

# Get server runtime status curl.exe -u "weblogic:<your-password>" http://localhost:7001/management/weblogic/latest/serverRuntime?fields=name,state
# Get domain configuration curl.exe -u "weblogic:<your-password>" http://localhost:7001/management/weblogic/latest/domainConfig

Option 3: WLST Command Line

# Launch WLST & "D:\Oracle\Middleware\wlserver\common\bin\wlst.cmd"
# In WLST shell: connect('weblogic', '<your-password>', 't3://localhost:7001') serverRuntime() print('Server State: ' + cmo.getState())

Managing WebLogic Server

Using Scheduled Task

# Start WebLogic Start-ScheduledTask -TaskName OracleWebLogicServer
# Stop WebLogic (graceful) Stop-ScheduledTask -TaskName OracleWebLogicServer
# Check status Get-ScheduledTask -TaskName OracleWebLogicServer | Select TaskName, State

Using Domain Scripts Directly

# Start & "D:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd"
# Stop & "D:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd"

Security Hardening

Change the Default Admin Password

Use WLST to change the admin password:

& "D:\Oracle\Middleware\wlserver\common\bin\wlst.cmd"
# In WLST: connect('weblogic', '<your-password>', 't3://localhost:7001')
cd('/SecurityConfiguration/base_domain/Realms/myrealm/AuthenticationProviders/DefaultAuthenticator') cd('Users/weblogic') cmo.setPassword('YourNewSecurePassword') disconnect() exit()

After changing the password, update boot.properties:

Set-Content -Path "D:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\security\boot.properties" -Value "username=weblogic`npassword=YourNewSecurePassword"

Delete the credentials file:

Remove-Item C:\CREDENTIALS.txt

Restrict Network Access

Make sure your Security Group allows access only from trusted IP addresses:

  • Port 3389 (RDP): Your IP only
  • Port 7001/7002 (WebLogic Server): Your IP or VPN CIDR only

Troubleshooting

WebLogic Server fails to start

Check the server log:

Get-Content "D:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log" -Tail 50

Common causes:

  • Insufficient memory: Use an instance type with at least 4 GB RAM.
  • Port conflict: Make sure port 7001 is not in use.
  • Scheduled Task not running: Check it with Get-ScheduledTask -TaskName OracleWebLogicServer.

Cannot connect via RDP

  • Verify the instance is running in the EC2 console
  • Check Security Group allows port 3389 from your IP
  • Verify you have the correct Administrator password (decrypt via EC2 console)
  • Use SSM Session Manager as an alternative

REST API returns 401

Make sure you are using the correct password from C:\CREDENTIALS.txt, not a default password.

Oracle WebLogic 14c Key Features

  • Java EE 8 Platform: Full Java Enterprise Edition 8 compliance
  • JDK 21 LTS: Latest long-term support Java runtime
  • WebLogic Remote Console: Modern desktop application for server management
  • Dynamic Clustering: Elastic server instances for horizontal scaling
  • Zero Downtime Patching: Apply patches without service interruption
  • RESTful Management API: Programmatic server administration

Support

SecureAnyCloud provides 24/7/365 support for all AWS Marketplace products.

  • Email: sales@secureanycloud.com
  • Response Time: Guaranteed 24-hour response
  • Support Plans: View support tiers
  • Oracle Documentation: WebLogic 14.1.2 Documentation
  • WebLogic Remote Console: Download and Documentation

Deploy on AWS

Launch Oracle WebLogic 14c on Windows with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com