Ow
Application Servers AWS

Oracle WebLogic Server 14.1.2 on Windows Server 2022 on AWS User Guide

| Product: Oracle WebLogic Server 14.1.2 on Windows Server 2022 on AWS

Overview

This image is Oracle WebLogic Server 14c (14.1.2.0.0) on Windows Server 2022 Datacenter, x86_64, sold by cloudimg on AWS Marketplace. This listing sells one product, Oracle WebLogic Server 14.1.2 on Windows Server 2022. WebLogic Server is installed from Oracle's own base media (Oracle Software Delivery Cloud V1045131-01, the Oracle-signed generic installer fmw_14.1.2.0.0_wls.jar) with no My Oracle Support patch added, on Windows Server 2022, updated at build, with the Microsoft Security Baseline applied. The image includes no Oracle Database and no Oracle Database Express Edition.

Oracle WebLogic Server is Oracle's Jakarta EE / Java EE application server for enterprise Java applications, web services and messaging, with JDBC data sources, JMS, clustering and a full security realm. Release 14.1.2 has no classic Administration Console (/console): it is administered with the WebLogic Remote Console, which this image serves from the AdminServer itself at /rconsole, and with WLST and the REST management API.

Bring your own Oracle WebLogic Server licence. This image includes no WebLogic licence. To run Oracle WebLogic Server you must hold your own Oracle WebLogic Server licence from Oracle that covers this instance. Oracle, Java and WebLogic are trademarks of Oracle; cloudimg is not affiliated with or endorsed by Oracle.

Price: $0.04 per vCPU per hour for cloudimg's image (an m5.large has 2 vCPUs, so $0.08 per hour), plus AWS infrastructure charges (Amazon EC2, which includes the Windows Server licence, and EBS). The charge pays for what cloudimg adds: WebLogic Server installed from Oracle's base media on a free OpenJDK, the domain and the per-instance admin password created at first boot, the admin server on loopback only, the closed-by-default firewall, and Windows Server 2022, updated at build, with the Microsoft Security Baseline applied. No Oracle WebLogic Server licence is included in that price.

The WebLogic domain is created on your instance at first boot. The image contains no domain. Allow about 20-25 minutes after launch on t3.large (up to 30) before WebLogic is ready: first boot reads the WebLogic and Java files from the new disk once before it creates the domain. The first line of the log says about 10 minutes; on a new instance expect the longer time. The progress log is C:\ProgramData\cloudimg\weblogic-firstboot.log.

What cloudimg does to the image:

  • No domain and no password in the image. The AMI holds the WebLogic Server 14.1.2.0.0 Oracle home in C:\Oracle\Middleware\Oracle_Home only. On first boot your instance creates base_domain with WLST from Oracle's own domain template, with its own embedded LDAP store, its own encryption salt (SerializedSystemIni.dat), its own keystores and a random 24-character password for the admin user weblogic generated on the instance. Nothing is shared between instances.
  • A password that only Administrators can read. The admin password is written to C:\ProgramData\cloudimg\weblogic\weblogic-credentials.txt, which only the Administrators group and SYSTEM can open. It never appears on a command line, in an environment variable or in a log. First boot writes the file only after it has proved that the password signs in and that a wrong password, the old demo password welcome1 and an anonymous request are all refused.
  • Production mode, admin server on loopback only. The AdminServer listens on 127.0.0.1:7001 and nowhere else, in production mode, with IIOP, anonymous T3 and IIOP RMI and WebLogic's default internal servlets (HTTP tunnelling) turned off. You administer it from a browser inside your Remote Desktop session, or through a port forward that opens no inbound port (see Reach the admin server from your workstation, below).
  • Its own service account. The AdminServer runs as the Windows service wlsvc base_domain_AdminServer, registered with Oracle's own installSvc.cmd, under its own virtual account NT SERVICE\wlsvc base_domain_AdminServer (not SYSTEM). The domain folder can be read only by Administrators, SYSTEM and that account.
  • Fail closed. If first boot fails, the WebLogic service stays stopped and disabled, the partial domain is removed, no credentials are written and a weblogic-firstboot.failed file says why. The next restart tries again from a clean slate, up to three attempts.
  • A free Java runtime. WebLogic runs on Eclipse Temurin OpenJDK 21 (21.0.13+9, from the Eclipse Foundation's Adoptium project, GPLv2 with the Classpath Exception), reached through the junction C:\Oracle\java\jdk-21. No Oracle JDK is included: Oracle's JDK 21 updates are licensed under Oracle's OTN licence, which does not allow them to ship in a paid image.
  • WebLogic closed to the network. The listing's security group opens Remote Desktop (3389) only, and the Windows Firewall has no inbound rule for 7001, 7002, 5556 or any Java or WebLogic program.
  • Blocked from the instance metadata service. Windows Firewall rules stop the WebLogic service, Oracle's service host wlsvcx64.exe and the Temurin java.exe from reaching the instance metadata service, so a flaw in an application you deploy cannot be used to read the instance role's credentials. The AMI requires IMDSv2.
  • Microsoft Security Baseline for Windows Server 2022 (Member Server), applied with Microsoft's LGPO tool and measured with HardeningKitty on a fresh instance: 320 of 320 scored rules pass. The report ships in C:\ProgramData\cloudimg\baseline\. This is a measurement made with open-source tooling against Microsoft's published baseline, not an accreditation by Microsoft or any other body.
  • Windows updated at build (OS build 20348.5870, the November 2026 cumulative update). The build fails if any update is still pending or a reboot is owed.
  • A unique Administrator password on every instance (Sysprep through EC2Launch v2; retrieve it with your key pair). Remote Desktop requires Network Level Authentication, SMBv1 is off, and DES and Triple DES are turned off in Windows TLS.
  • No build residue: installer media, build tools, history and event logs are removed and free space is wiped before capture.

Connecting to your instance

Connect with Remote Desktop as the Administrator:

Operating system variant Remote Desktop login user
Windows Server 2022 Datacenter Administrator

Launch from AWS Marketplace

  1. Open the listing on AWS Marketplace and choose View purchase options, then Subscribe.
  2. Once the subscription is active, choose Launch your software.
  3. Choose the version whose title starts Oracle WebLogic 14.1.2 on Windows Server 2022. The listing may still show its earlier Oracle Database 21c Express Edition version for a while; that is a different product, so do not pick it for WebLogic.
  4. Choose your Region and an instance type. m5.large (2 vCPU, 8 GiB) is the recommended starting size (t3.large is fine for development and testing); use a larger instance for production workloads, and make sure your Oracle licence covers the size you run.
  5. Choose a key pair. You need its private key to get the Administrator password.
  6. Use a security group that allows RDP (TCP 3389) from your own address only. The suggested security group allows RDP from anywhere: change the source to your own IP. Do not open 7001 or any other WebLogic port.
  7. Keep the root volume on gp3; choose a larger volume at launch if your applications and logs need room.
  8. Optional: attach an IAM instance profile with the AmazonSSMManagedInstanceCore policy, so you can reach the admin server from your workstation with Session Manager port forwarding (see Reach the admin server from your workstation, below) without opening any port.
  9. Launch.

First boot: WebLogic is set up on your instance

After Windows finishes its first boot, a one-time task creates the domain C:\Oracle\user_projects\domains\base_domain, generates the weblogic password, registers and starts the wlsvc base_domain_AdminServer service, checks the sign-in, writes the credentials file and sets the service to start automatically. Allow about 20-25 minutes after launch in all (up to 30); most of it is the first read of the WebLogic and Java files from the new disk. The Administrator password is ready once Windows setup has finished, so you can sign in and watch. Check progress in PowerShell:

Get-Content C:\ProgramData\cloudimg\weblogic-firstboot.log -Tail 6

WebLogic is ready when the ready marker exists and the service is running:

Test-Path C:\ProgramData\cloudimg\weblogic-firstboot.done
Get-Service 'wlsvc base_domain_AdminServer' | Select-Object Name, Status, StartType

The ready marker also records what first boot made and how long it took:

Get-Content C:\ProgramData\cloudimg\weblogic-firstboot.done | ConvertFrom-Json |
  Select-Object version, seconds, domain, service, account, adminUrl

To follow the log live in a Remote Desktop session, run Get-Content C:\ProgramData\cloudimg\weblogic-firstboot.log -Wait.

If first boot fails, the log and C:\ProgramData\cloudimg\weblogic-firstboot.failed say why, the WebLogic service stays stopped and no credentials are written. Restart the instance to try again (first boot makes up to three attempts), or contact cloudimg (see Support, below).

Get the Administrator password

In the EC2 console select the instance, choose Actions, Security, Get Windows password, upload the private key of your key pair and choose Decrypt password. Or with the AWS CLI on your workstation:

aws ec2 get-password-data --region <region> --instance-id <instance-id> \
  --priv-launch-key ~/.ssh/my-key-pair.pem --query PasswordData --output text

An empty result means Windows has not finished setting the password yet; try again a minute later.

Connect over Remote Desktop

Connect to the instance's public DNS name or IP address on port 3389 with a Remote Desktop client that supports Network Level Authentication (Microsoft Remote Desktop on Windows and macOS, FreeRDP on Linux), as Administrator with the password from the previous step. Each instance generates its own Remote Desktop certificate, so your client asks you to trust it on first connection.

Read your WebLogic password

Open an elevated PowerShell in the Remote Desktop session and read the credentials file:

Get-Content C:\ProgramData\cloudimg\weblogic\weblogic-credentials.txt

It holds WEBLOGIC_USER=weblogic, WEBLOGIC_PASSWORD (the password generated on this instance), WEBLOGIC_ADMIN_URL=http://127.0.0.1:7001, WEBLOGIC_DOMAIN_HOME and WEBLOGIC_SERVICE. Store the password in your password manager. If you copy it anywhere else, change it (see Change the admin password, below).

Open the WebLogic Remote Console

The AdminServer serves the hosted WebLogic Remote Console (Oracle's own wls-remote-console.war from the Oracle home) on the loopback address. In the Remote Desktop session, open this address in Microsoft Edge on the instance:

http://127.0.0.1:7001/rconsole

If the instance has no Edge, install it from Microsoft or use the port forward from your workstation (below); Internet Explorer is not suitable for the Remote Console. The console is loaded on its first request, so the first visit can take up to two minutes. Sign in as weblogic with the password from the credentials file.

The Remote Console covers deployments, data sources, JMS, the security realm (users and groups) and monitoring. The domain runs in production mode, so configuration changes collect in a pending change list until you commit them. http://127.0.0.1:7001/console/welcome/ shows WebLogic's own welcome page for release 14.1.2.

After five wrong passwords in a row WebLogic locks the account (for 30 minutes with WebLogic's default lockout settings), so copy the password rather than typing it.

Use the REST management API

The REST management API on http://127.0.0.1:7001/management/weblogic/latest uses the same admin credentials. This reads the password from the credentials file in memory and asks for the AdminServer's state and version:

$kv = @{}
Get-Content C:\ProgramData\cloudimg\weblogic\weblogic-credentials.txt | Where-Object { $_ -match '^[A-Z_]+=' } |
  ForEach-Object { $k, $v = $_ -split '=', 2; $kv[$k] = $v }
$auth = 'Basic ' + [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes('weblogic:' + $kv['WEBLOGIC_PASSWORD']))
Invoke-RestMethod -Uri 'http://127.0.0.1:7001/management/weblogic/latest/serverRuntime?links=none&fields=name,state,weblogicVersion' -Headers @{ Authorization = $auth }
Remove-Variable kv, auth

state is RUNNING and weblogicVersion starts WebLogic Server 14.1.2.0.0. A request without credentials is refused with 401:

curl.exe -s -o NUL -w "%{http_code}\n" http://127.0.0.1:7001/management/weblogic/latest/serverRuntime

Requests that change configuration also need the X-Requested-By header (WebLogic's protection against cross-site requests).

Script administration with WLST

The WebLogic Scripting Tool is C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\wlst.cmd; it connects to the AdminServer over T3 on the loopback address. Start it from PowerShell in the Remote Desktop session and connect (type the password at the prompt rather than putting it in a script):

C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\wlst.cmd
connect('weblogic', '<password>', 't3://127.0.0.1:7001')
print(cmo.getName())
serverRuntime()
print(cmo.getState())
exit()

The first print shows base_domain and the second RUNNING. To change configuration, use edit(), startEdit(), your changes, save() and activate().

Deploy an application

Copy your application archive to the instance (for example C:\apps\myapp.war), then deploy it with WLST. upload='true' copies the archive into the domain, where the WebLogic service account can read it:

C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\wlst.cmd
connect('weblogic', '<password>', 't3://127.0.0.1:7001')
deploy('myapp', 'C:/apps/myapp.war', targets='AdminServer', upload='true')
disconnect()
exit()

Or in the Remote Console, add it under Deployments in the edit tree and commit the change. An application deployed to the AdminServer answers on the loopback address only, at http://127.0.0.1:7001/<context-root>/ inside the instance. To serve applications to your users, see Serve applications beyond the instance below.

The WebLogic service and files

The Windows service wlsvc base_domain_AdminServer runs the AdminServer, starts automatically and restarts itself if it stops unexpectedly:

Get-Service 'wlsvc base_domain_AdminServer' | Select-Object Name, Status, StartType
(Get-CimInstance Win32_Service -Filter "Name='wlsvc base_domain_AdminServer'").StartName
Get-NetTCPConnection -State Listen -LocalPort 7001 | Select-Object LocalAddress, LocalPort, OwningProcess

The service runs as NT SERVICE\wlsvc base_domain_AdminServer, and the only listening address is 127.0.0.1. To stop and start WebLogic cleanly:

Stop-Service 'wlsvc base_domain_AdminServer'
Start-Service 'wlsvc base_domain_AdminServer'

The AdminServer is back in RUNNING a minute or two after a start. Check the installed WebLogic release and the Java runtime:

cmd /c 'C:\Oracle\java\jdk-21\bin\java.exe -cp C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib\weblogic.jar weblogic.version 2>&1' | Select-String '^WebLogic Server'
Get-Content C:\Oracle\java\jdk-21\release | Select-String '^(IMPLEMENTOR|JAVA_VERSION)='
(Get-Item C:\Oracle\java\jdk-21).Target
Item Location
Oracle home (ORACLE_HOME) C:\Oracle\Middleware\Oracle_Home
WebLogic Server (WL_HOME) C:\Oracle\Middleware\Oracle_Home\wlserver
WLST C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\wlst.cmd
Java runtime (JAVA_HOME, machine-wide, also on the machine PATH) C:\Oracle\java\jdk-21, a junction to the Eclipse Temurin JDK 21 folder in C:\Program Files\Eclipse Adoptium
Your domain (DOMAIN_HOME), created at first boot C:\Oracle\user_projects\domains\base_domain
AdminServer log C:\Oracle\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log
First boot log, ready and failure markers C:\ProgramData\cloudimg\weblogic-firstboot.log, weblogic-firstboot.done, weblogic-firstboot.failed in the same folder
Admin credentials C:\ProgramData\cloudimg\weblogic\weblogic-credentials.txt
Baseline report and tool versions C:\ProgramData\cloudimg\baseline\
Port Purpose Open by default
7001 AdminServer: Remote Console, REST management API, T3 for WLST No: listens on 127.0.0.1 only, no Windows Firewall rule, not in the security group
3389 Remote Desktop Yes, in the security group and the Windows Firewall

The AdminServer's Java heap is -Xms512m -Xmx2g, set when first boot registered the service. NodeManager is not configured in this single-server domain.

Reach the admin server from your workstation

To use the Remote Console from a browser on your workstation, use AWS Systems Manager Session Manager port forwarding, which needs no inbound port at all. With the instance profile from the launch step and the AWS CLI with the Session Manager plugin on your workstation:

aws ssm start-session --region <region> --target <instance-id> \
  --document-name AWS-StartPortForwardingSession \
  --parameters portNumber=7001,localPortNumber=7001

Leave it running and open http://localhost:7001/rconsole on your workstation (or add http://localhost:7001 as an Admin Server connection in the desktop WebLogic Remote Console). The traffic travels inside the Session Manager tunnel.

Do not open port 7001 to the network. The AdminServer serves the admin password over plain HTTP, and it listens on the loopback address only, so a security group rule for 7001 would reach nothing. Keep administration on the tunnel or the Remote Desktop session.

Serve applications beyond the instance

The AdminServer is for administration. To serve an application to other machines, add a managed server to the domain that listens on the instance's private address, preferably on an SSL listen port with your own identity and trust keystores (Oracle's Administering Security for Oracle WebLogic Server describes them), target your application at it, and keep the AdminServer on 127.0.0.1. Then open only that port, and only to your own networks, in both the Windows Firewall and the security group. For example, for an SSL port 7002 and your application subnet 10.0.1.0/24:

New-NetFirewallRule -DisplayName 'WebLogic managed server 7002 from app subnet' -Direction Inbound -Protocol TCP -LocalPort 7002 -RemoteAddress 10.0.1.0/24 -Action Allow

Add the same port and source range (or your load balancer's security group) to the instance's security group. Never open a WebLogic port to 0.0.0.0/0. If you add NodeManager, have it listen on 127.0.0.1 and keep port 5556 out of the security group.

Change the admin password

Reset the password online with WLST, then put the new password in boot.properties so the service can still start unattended, update the credentials file and restart the service. In WLST:

C:\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\wlst.cmd
connect('weblogic', '<current password>', 't3://127.0.0.1:7001')
cd('/SecurityConfiguration/base_domain/Realms/myrealm/AuthenticationProviders/DefaultAuthenticator')
cmo.resetUserPassword('weblogic', '<new password>')
disconnect()
exit()

Then open Notepad as administrator and:

  1. Replace the contents of C:\Oracle\user_projects\domains\base_domain\servers\AdminServer\security\boot.properties with two lines, username=weblogic and password=<new password>. WebLogic encrypts the file again the next time the AdminServer starts.
  2. Change the WEBLOGIC_PASSWORD= line of C:\ProgramData\cloudimg\weblogic\weblogic-credentials.txt, or delete the file.

Restart the service and check that it comes back:

Restart-Service 'wlsvc base_domain_AdminServer'
Get-Service 'wlsvc base_domain_AdminServer' | Select-Object Name, Status

Create separate users in the security realm for operators and deployers rather than sharing the weblogic account.

View the baseline report

Everything the build measured ships in C:\ProgramData\cloudimg\baseline\:

File What it is
baseline-report.html Every rule audited, its result and the recommended value; waived rules marked
hardeningkitty-report.csv The raw HardeningKitty audit
baseline-summary.json Rules audited, waived, scored and passed, the pass rate and threshold
waivers.txt / waivers.json The waived rules and why
tool-versions.json The baseline, LGPO, HardeningKitty, Temurin JDK and WebLogic media versions and SHA-256 values
Get-Content C:\ProgramData\cloudimg\baseline\baseline-summary.json | ConvertFrom-Json |
  Select-Object profile, audited, waived, scored, pass, fail, ratePct, thresholdPct, evaluatedAt

Open baseline-report.html in a browser on the instance, or copy it to your workstation.

Re-run the audit yourself

HardeningKitty v.0.9.4 stays in the image. Run it in an elevated PowerShell; it only reads settings and takes a minute or two:

$hk = 'C:\ProgramData\cloudimg\tools\HardeningKitty-0.9.4'
Import-Module "$hk\HardeningKitty.psm1" -Force
$list = "$hk\lists\finding_list_msft_security_baseline_windows_server_2022_21h2_member_machine.csv"
$csv = Join-Path $env:TEMP 'hardeningkitty-now.csv'
Remove-Item $csv -ErrorAction SilentlyContinue
$null = Invoke-HardeningKitty -Mode Audit -FileFindingList $list -Report -ReportFile $csv -SkipMachineInformation *>&1
$waived = (Get-Content -Raw C:\ProgramData\cloudimg\baseline\waivers.json | ConvertFrom-Json).waivers.id
$scored = @(Import-Csv $csv | Where-Object { $waived -notcontains $_.ID })
$pass = @($scored | Where-Object { $_.Severity -eq 'Passed' }).Count
"{0} of {1} scored rules pass ({2:N1}%)" -f $pass, $scored.Count, (100 * $pass / $scored.Count)
$scored | Where-Object { $_.Severity -ne 'Passed' } | Select-Object ID, Name, Result, Recommended

Waived rules

These rules are set differently on purpose. Each one is in waivers.txt with its reason:

ID Rule Set to Why
10311 Deny access to this computer from the network Guests The baseline denies network logon to local administrators. Remote Desktop with Network Level Authentication checks the Administrator's password with a network logon first, so the EC2 Administrator could not sign in.
10312 Deny log on through Remote Desktop Services Guests The baseline denies Remote Desktop to every local account. On a stand-alone EC2 instance the local Administrator is the only way in.
10672-10677 Device Guard: Virtualization Based Security and Credential Guard (6 rules) Not configured Credential Guard needs UEFI Secure Boot. This image boots in legacy BIOS mode on EC2, so the policy could not run and a "pass" would be misleading.

Windows Firewall

Every firewall profile is on with inbound traffic blocked unless a rule allows it. The only inbound rules enabled are Remote Desktop (3389, TCP and UDP) and core networking (ICMP, DHCP); there is no rule for 7001, 7002, 5556 or any Java or WebLogic program:

Get-NetFirewallRule -Direction Inbound -Enabled True -Action Allow |
  Select-Object DisplayGroup, DisplayName, Profile | Sort-Object DisplayGroup, DisplayName
Get-NetFirewallProfile | Select-Object Name, Enabled, DefaultInboundAction

Instance metadata (IMDSv2)

The image requires IMDSv2: a request to the instance metadata service without a session token is refused. Windows, EC2Launch v2 and the SSM agent all use IMDSv2 and keep working. Three outbound Windows Firewall rules block the WebLogic service, wlsvcx64.exe and the Temurin java.exe from the metadata addresses 169.254.169.254 and 168.63.129.16:

Get-NetFirewallRule -Group 'cloudimg metadata block' | Select-Object DisplayName, Direction, Action, Enabled

If an application you deploy needs AWS credentials, give it its own (for example from AWS Secrets Manager) rather than removing these rules.

Patching

Windows has every update installed when the image is built. Check for newer updates with:

$searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()
$searcher.Search("IsInstalled=0 and IsHidden=0 and Type='Software'").Updates | Select-Object Title

and install them from Settings, Windows Update (or sconfig option 6). The WebLogic service starts again on its own when Windows restarts.

WebLogic Server is Oracle's 14.1.2.0.0 base release: its Oracle inventory lists only the two one-off fixes Oracle's installer itself carries, and no Patch Set Update has been applied. Oracle distributes WebLogic patches through My Oracle Support to licensed customers, so apply the current WebLogic Patch Set Update and security patches with your own Oracle account, following Oracle's Patching with OPatch documentation and the quarterly Oracle Critical Patch Update advisories. Stop the wlsvc base_domain_AdminServer service first, apply the patch from an elevated prompt, then start the service again.

Java. Temurin does not update itself; Adoptium publishes JDK 21 updates every quarter. WebLogic, the machine JAVA_HOME and the machine PATH all use the junction C:\Oracle\java\jdk-21, so a Java update only re-points the junction. Download the new Windows x64 JDK 21 MSI from adoptium.net and check its SHA-256 against the one Adoptium publishes. Then stop WebLogic, install it (files only, as in the image), and look up the new folder:

Stop-Service 'wlsvc base_domain_AdminServer'
Start-Process msiexec.exe -Wait -ArgumentList '/i', "$env:USERPROFILE\Downloads\<temurin-21-msi-file>.msi", 'ADDLOCAL=FeatureMain', '/qn'
Get-ChildItem 'C:\Program Files\Eclipse Adoptium' -Directory -Filter 'jdk-21*'

Point the junction and the java.exe metadata block rule at the new folder, and start WebLogic again:

$new = 'C:\Program Files\Eclipse Adoptium\<new jdk-21 folder>'
cmd /c rmdir C:\Oracle\java\jdk-21
cmd /c mklink /J C:\Oracle\java\jdk-21 "$new"
Set-NetFirewallRule -DisplayName 'cloudimg: no instance metadata for java.exe' -Program "$new\bin\java.exe"
Start-Service 'wlsvc base_domain_AdminServer'

rmdir on the junction removes only the link, not the JDK it points to. Oracle certifies WebLogic Server 14.1.2 with Oracle JDK 17 and 21; if your Oracle support terms require Oracle JDK, install it yourself under your own Oracle entitlement (cloudimg does not supply it) and point the junction and the rule at it the same way.

Backups

Back up the domain folder C:\Oracle\user_projects\domains\base_domain (it holds the configuration, the embedded LDAP store with your users, the encryption salt and your uploaded applications) with the service stopped, together with your application archives, and copy the backup off the instance, for example to Amazon S3. EBS snapshots of a running instance are crash-consistent only; stop the service first when you need a clean copy. The salt security\SerializedSystemIni.dat and the domain must be restored together, since encrypted values in the domain can only be read with the salt they were made with.

Support

cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours: support@cloudimg.co.uk or https://www.cloudimg.co.uk/support. We help with launch and Remote Desktop sign-in, first boot and the credentials file, the WebLogic Remote Console, WLST and the REST management API, deploying applications, adding managed servers and reaching the admin server safely from your network. Oracle WebLogic Server licensing questions go to Oracle under your own agreement; Windows Server licensing questions go to AWS and Microsoft.

Licensing and price

This image includes no Oracle WebLogic Server licence. You must hold your own Oracle WebLogic Server licence that covers this instance, and use WebLogic Server under your agreement with Oracle. The cloudimg charge on AWS Marketplace is $0.04 per vCPU per hour plus AWS infrastructure charges, and it pays for the image: the install from Oracle's base media, the first-boot domain with its per-instance admin password, the loopback-only admin server, the closed-by-default firewall and Windows Server 2022, updated at build, with the Microsoft Security Baseline applied. The Windows Server licence is included in the Amazon EC2 charge. Oracle WebLogic Server patches come to you from Oracle under your own Oracle agreement, not from cloudimg.

The Java runtime is Eclipse Temurin OpenJDK 21, free to use under GPLv2 with the Classpath Exception; no Oracle JDK is included. The image includes no Oracle Database and no Oracle Database Express Edition. Oracle WebLogic Server documentation is at docs.oracle.com.

Oracle, Java and WebLogic are registered trademarks of Oracle and/or its affiliates. Eclipse Temurin and Adoptium are trademarks of the Eclipse Foundation. Microsoft and Windows Server are trademarks of the Microsoft group of companies. cloudimg is not affiliated with or endorsed by Oracle, the Eclipse Foundation or Microsoft.