SecureAnyCloud
Deployment guide

Oracle WebLogic 12c Windows

Overview

This guide shows you how to deploy and configure Oracle WebLogic Server 12c (12.2.1.4.0) on Windows Server, using the SecureAnyCloud AMIs from AWS Marketplace. You launch the AMI, connect over RDP, retrieve the generated credentials and open the Administration Console.

What you get:

  • Oracle WebLogic Server 12c (12.2.1.4.0) with Java EE 7 support
  • Oracle JDK 8 LTS
  • A preconfigured WebLogic domain with the Admin Server on port 7001
  • The traditional web-based Administration Console at /console
  • A Scheduled Task that starts WebLogic automatically at boot
  • Oracle software installed on a separate D: drive (20 GB EBS volume)
  • The AWS CLI, the Systems Manager Agent and the CloudWatch Agent

Supported operating systems: Windows Server 2022 and Windows Server 2019.

Prerequisites

Before you launch this AMI, make sure you have:

  • An active AWS account
  • An active subscription to the Oracle WebLogic 12c 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

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

Each rule uses the TCP protocol and your own IP address as the source:

  • Port 3389: RDP access
  • Port 7001: WebLogic Administration Console
  • Port 7002: WebLogic Server (SSL)

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

2

Connect with RDP

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

Open your RDP client and connect with these values:

  • Computer: your instance's public IP or DNS name
  • Username: Administrator
  • Password: the decrypted password from the EC2 console

Alternatively, use SSM Session Manager for 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 the WebLogic credentials

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

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

Important: Change the password after first use. See the Security Hardening section below.

4

Verify the installation

Open PowerShell and run these commands to 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 starts automatically at boot through a Scheduled Task. To start it manually, run this command.

Start-ScheduledTask -TaskName OracleWebLogicServer

Wait approximately 60 to 90 seconds for the server to start. To verify that it is running, run this command.

# Check the scheduled task state Get-ScheduledTask -TaskName OracleWebLogicServer | Select State
# Check if port 7001 is listening Get-NetTCPConnection -LocalPort 7001 -ErrorAction SilentlyContinue
6

Open the Administration Console

Open a web browser and go to this address.

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

The Oracle WebLogic Server Administration Console login page opens. Enter your credentials:

  • Username: weblogic
  • Password: the password from C:\CREDENTIALS.txt

Choose Login to open the console. The Administration Console dashboard shows the Domain Structure, the server status and the configuration options.

Directory structure

The AMI uses these paths:

  • D:\Oracle\Java\jdk1.8.0_XXX\ is Oracle JDK 8 LTS (JAVA_HOME).
  • D:\Oracle\Middleware\ is the Middleware Home (MW_HOME / ORACLE_HOME).
  • D:\Oracle\Middleware\wlserver\ is the WebLogic Server Home (WL_HOME).
  • D:\Oracle\Middleware\user_projects\domains\base_domain\ is the default domain (DOMAIN_HOME).
  • D:\Oracle\oraInventory\ is the Oracle Inventory.
  • C:\CREDENTIALS.txt is the admin credentials file.

The following environment variables are set system-wide.

JAVA_HOME = D:\Oracle\Java\jdk1.8.0_XXX MW_HOME = D:\Oracle\Middleware WL_HOME = D:\Oracle\Middleware\wlserver DOMAIN_HOME = D:\Oracle\Middleware\user_projects\domains\base_domain

Using the Administration Console

The WebLogic Administration Console is a web-based interface for managing your WebLogic domain.

Accessing the console

In your web browser, go to http://<PUBLIC_IP>:7001/console and log in as the weblogic user.

Editing the configuration

The console works in lock and edit mode, so that multiple administrators do not make conflicting changes at the same time. To make changes:

  • Choose Lock & Edit in the Change Center panel on the left.
  • Make your configuration changes.
  • Choose Release Configuration to save and apply them.

Key console sections

  • Domain Structure in the left panel shows the domain tree, including Environment, Deployments, Services, Security Realms and Diagnostics.
  • Environment > Servers lists all configured server instances.
  • Deployments lets you deploy and manage Java EE applications and modules.
  • Services > Data Sources is where you configure JDBC connections to databases.
  • Security Realms manages users, groups, roles and authentication providers.
  • Diagnostics provides access to log files, images and performance data.

Deploying an application

  • Choose Lock & Edit.
  • Go to Deployments in the left panel.
  • Choose Install and browse to your WAR, EAR or JAR file.
  • Follow the wizard to select the targeting options and deployment settings.
  • Choose Release Configuration to activate the deployment.

WLST command line

The WebLogic Scripting Tool (WLST) provides command-line administration.

# 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 the 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 the 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

Option 1: Use the Administration Console (recommended)

  • Log in to the console at http://<PUBLIC_IP>:7001/console.
  • Choose Lock & Edit in the top-left pane.
  • In the left navigation, choose Security Realms.
  • Choose myrealm to open the security realm settings.
  • Select the Users and Groups tab.
  • Choose the weblogic user.
  • Select the Passwords tab.
  • Enter your new strong password in both the New Password and Confirm New Password fields.
  • Choose Save.
  • Choose Release Configuration to apply the changes.

Option 2: Use WLST

& "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 you change 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"

Then delete the credentials file.

Remove-Item C:\CREDENTIALS.txt

Restrict network access

Make sure your Security Group only allows access 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 that the instance is running in the EC2 console.
  • Check that the Security Group allows port 3389 from your IP address.
  • Verify that you have the correct Administrator password (decrypt it in the EC2 console).
  • Use SSM Session Manager as an alternative.

Administration Console is not accessible

  • Confirm that WebLogic Server is running: Get-NetTCPConnection -LocalPort 7001 -ErrorAction SilentlyContinue
  • Verify that your Security Group allows inbound traffic on port 7001.
  • Make sure you use http:// (not https://) and the correct port in the URL.
  • Allow 2 to 3 minutes after startup for the Administration Console to initialize fully.

Cannot log in to the Administration Console

  • Verify that you use the username weblogic (case-sensitive).
  • Retrieve the correct password from C:\CREDENTIALS.txt.
  • If you changed the password and forgot it, reset it with WLST from the command line.

Oracle WebLogic 12c key features

  • Java EE 7 platform: support for Java EE 7 standards, including Servlet 3.1, JAX-RS 2.0, JPA 2.1 and WebSocket 1.0.
  • JDK 8 LTS: a long-term support Java runtime.
  • Administration Console: a traditional web-based management interface for server administration.
  • Dynamic Clustering: elastic server instances for horizontal scaling.
  • Oracle Coherence integration: an in-memory data grid for distributed caching.
  • WLST scripting: the WebLogic Scripting Tool for automated administration and deployment.

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 the support tiers
  • Oracle documentation: WebLogic 12.2.1.4 documentation

Deploy on AWS

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

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com