Oracle Forms and Reports 14.1.2 on AWS User Guide
Overview
This guide covers launching and using the Oracle Forms and Reports 14.1.2 on Oracle Linux 9 AMI from cloudimg on Amazon EC2.
Oracle Forms builds and runs PL/SQL based business applications against an Oracle database; Oracle Reports produces formatted reports (PDF, HTML, spreadsheet, XML) from database queries. Release 14.1.2 runs on WebLogic Server 14.1.2 and Java SE 17 or 21. Forms applications reach users through Java Web Start or the Forms Standalone Launcher (the browser applet is no longer supported), and both products are administered with Fusion Middleware Control.
The cloudimg image adds:
- Everything per-instance is made on your instance, not on ours. The image holds the Oracle software only: no database, no repository and no domain. On the first boot of every instance a one-time service creates the repository database (Oracle Database 26ai) with its own SYS, SYSTEM and PDBADMIN passwords, creates the Fusion Middleware repository schemas (STB, OPSS, IAU, IAU_APPEND, IAU_VIEWER, WLS, MDS) with a schema password generated on the instance, then creates the Forms and Reports WebLogic domain with its own administrator password, encryption salt and TLS certificate. No two instances share a credential, and the image's own tools never put a password on a command line or in a log. The access logs of nginx and WebLogic record paths without query strings (nginx's error log can still quote a failed request in full, so keep passwords out of URLs: Step 6).
- Ready to use. The domain comes up with the AdminServer (with Fusion Middleware Control), the
WLS_FORMSmanaged server, theWLS_REPORTSmanaged server running the in-process Reports server, a Reports Tools instance and Node Manager. Folders for your compiled forms and your reports are already wired in. - Fail closed. Nothing serves Forms or Reports until first boot has finished. If first boot ever fails, the partial domain and repository are removed, a note is left in
/root, and a reboot retries. - HTTPS from the first boot. nginx serves Forms Services and Reports Services on port 443 with a certificate generated on your instance (port 80 redirects). Every WebLogic server, Node Manager and the database listener listen on
127.0.0.1only. Requests for a host name the instance does not serve get no answer, and WebLogic's internal servlets are switched off on every server. - Administration closed by default. Fusion Middleware Control and the WebLogic REST management API share port 443 with Forms, but they answer only requests from the instance itself: reach them through an SSH tunnel, or allow your own network with one command (Step 7). Your Forms users never reach them.
- Secure defaults. SSH by key only (no passwords, no root login, no X11 forwarding);
roothas no password. WebLogic runs in production mode as theoracleuser, under systemd units withNoNewPrivileges,PrivateTmpandProtectSystem=full. SELinux is permissive, as the Oracle Database 26ai install requires;httpd_can_network_connectis set for nginx. No Oracle process can reach the instance metadata service, and the AMI requires IMDSv2. - Base media only. Fusion Middleware Infrastructure 14.1.2.0.0, Forms and Reports 14.1.2.0.0 and Oracle Database 26ai are installed from Oracle's release media (verified by checksum), and cloudimg applies no Oracle patch. The only patches in the Fusion Middleware home are the two one-off patches the 14.1.2.0.0 installers apply themselves (36964826 and 36990807); the database home is Oracle's 23.26.1.0.0 gold image, whose inventory lists the Release Update it was built from. You apply Oracle's later patches with your own Oracle support (Step 10).
- A Java runtime that dnf keeps patched. Fusion Middleware runs on Oracle Linux's own OpenJDK 21, so Java security updates install with
dnflike any other package. - Fully patched Oracle Linux 9 at build time, with
dnf-automaticapplying Oracle Linux security updates every day.
What is on the image: Oracle Fusion Middleware Infrastructure 14.1.2.0.0 and Oracle Forms and Reports 14.1.2.0.0 in /opt/oracle/middleware/fmw, Oracle Database 26ai Enterprise Edition 23.26.1.0.0 software in /opt/oracle/product/26ai/dbhome_1 (the repository database), Oracle Linux OpenJDK 21, nginx, Oracle Linux 9 with the Unbreakable Enterprise Kernel, cloud-init and the AWS Systems Manager agent.
Default user: ec2-user · Architecture: x86_64 · Recommended instance type: m5.xlarge (16 GiB)
Licensing and price
Bring your own licence. Oracle Forms and Reports and the Oracle Database that holds its repository are commercial Oracle products. Using them requires your own Oracle licences covering the instance under Oracle's licensing policy for cloud computing environments. Pricing: $0.04 per vCPU per hour for the cloudimg software (an m5.xlarge has 4 vCPUs, so $0.16 per hour), plus AWS infrastructure charges; the listing charges the same rate per vCPU on every instance type it offers, and Forms and Reports need one with at least 16 GiB of memory. The charge is for what cloudimg adds to Oracle's base media: the repository database, schemas and domain created on each instance at first boot with their own passwords and TLS certificate, HTTPS through nginx with administration closed by default, every Oracle server on the loopback address, SSH by key pair only, and the Oracle processes blocked from the instance metadata service. It does not include an Oracle licence, and Oracle patches come from your own Oracle support contract.
The Java runtime is Oracle Linux's OpenJDK 21, open source (GPLv2 with the Classpath Exception) and patched through dnf. The Forms and Reports installer puts its own copy of Oracle JDK into the Oracle home (oracle_common/jdk); the image replaces it with a link to OpenJDK 21, so no Oracle JDK is used by Fusion Middleware. The Oracle Database home keeps the JDK that Oracle ships inside it for the database tools. The notices are in /usr/share/doc/cloudimg/licenses/.
Prerequisites
- An AWS account subscribed to the listing, an EC2 key pair and a VPC subnet with a route to the internet (or a private route you use for management).
- A security group that allows TCP 443 (HTTPS: Forms and Reports, and Fusion Middleware Control for the networks you allow) and TCP 80 (redirects to HTTPS) from your users' networks, and TCP 22 (SSH) from your own networks only. No other port is ever needed in the security group. Each Forms session starts a server process before your application's own sign-in, so publish 443 to the networks your users work from rather than to the whole internet where you can.
- For Forms users: a Java runtime on their desktops (Java Web Start, or the Forms Standalone Launcher
frmsal.jarthat the server provides).
Step 1: Launch the instance
Open the listing Oracle Forms and Reports 14.1.2 | cloudimg on AWS Marketplace, choose View purchase options and Subscribe. When the subscription is active choose Launch your software, choose the software version Oracle Forms and Reports 14.1.2 on Oracle Linux 9 and your Region. If the version list also shows an older Oracle Database 11g Express Edition version, that is the product this listing sold before and is not this image. Choose m5.xlarge (16 GiB; the repository database, three WebLogic servers and the Reports engine run on one instance) or larger, your key pair and a security group as above. The security group the listing suggests allows only SSH (TCP 22), from anywhere: change its source to your own IP, and add TCP 443 and TCP 80 from your users' networks. The image has three volumes: the root file system, /opt/oracle (40 GiB, the database software and the repository database) and /opt/oracle/middleware (25 GiB, Fusion Middleware, the domain and your applications). You can enlarge any of them at launch.
With the AWS CLI (replace the values in angle brackets):
aws ec2 run-instances --region <region> --image-id <ami-id-from-the-listing> \
--instance-type m5.xlarge --key-name <your-key-pair> \
--security-group-ids <your-security-group> --subnet-id <your-subnet> \
--metadata-options HttpTokens=required,HttpEndpoint=enabled \
--tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=forms-reports}]'
Step 2: Connect to your instance
| Version | SSH user |
|---|---|
| Oracle Forms and Reports 14.1.2 on Oracle Linux 9 | ec2-user |
ssh -i <your-key.pem> ec2-user@<public-ip>
Confirm the operating system release:
cat /etc/oracle-release
Oracle Linux Server release 9.8
Step 3: Wait for first boot
First boot runs in two stages: the database layer creates the repository database, then forms-firstboot.service creates the repository schemas, the domain, the Reports Tools instance and the TLS certificate, and the managed servers start. A newly launched instance is slower than later boots because its volumes are still loading from the AMI snapshots: measured on fresh 4 vCPU instances, the database took 9.3 minutes, the Forms and Reports first boot 8.5 minutes and the servers 3 minutes more, so Forms and Reports are ready roughly 22 minutes after launch. Until then nginx is not started and port 443 refuses connections. The file /var/lib/cloudimg/forms-firstboot.done appears when first boot has finished; the servers then take about 3 more minutes to start.
sudo systemctl is-active oracle-db.service forms-firstboot.service forms-nodemanager.service forms-adminserver.service forms-wls-forms.service forms-wls-reports.service nginx.service
active
active
active
active
active
active
active
If a unit shows activating, wait a minute and run the command again. Follow first boot as it runs with sudo journalctl -fu forms-firstboot.service. The first boot log shows each stage and how long it took:
sudo cat /var/log/forms-reports-firstboot.log
[<timestamp>] forms-firstboot: waiting for this instance's repository database (database layer first boot)
[<timestamp>] forms-firstboot: configured host: <public-dns>
[<timestamp>] forms-firstboot: creating the Fusion Middleware repository in ORCLPDB (RCU: STB OPSS IAU IAU_APPEND IAU_VIEWER WLS MDS, prefix FRM)
[<timestamp>] forms-firstboot: repository created in 74s
[<timestamp>] forms-firstboot: creating forms_domain (WLST offline: Forms, Reports Application, Enterprise Manager plug-in)
[<timestamp>] forms-firstboot: domain written in 189s
[<timestamp>] forms-firstboot: starting Node Manager and the AdminServer to create the Reports Tools instance (WLST online)
[<timestamp>] forms-firstboot: first start of WLS_FORMS and WLS_REPORTS to generate their application configuration
[<timestamp>] forms-firstboot: Forms FORMS_PATH starts with /opt/oracle/middleware/apps/forms; Reports reads /opt/oracle/middleware/apps/reports, writes /opt/oracle/middleware/apps/reports-output
[<timestamp>] forms-firstboot: TLS certificate + nginx host for <public-dns>
[<timestamp>] forms-firstboot: done in 508s; restarting the AdminServer (its access log format) and starting WLS_FORMS, WLS_REPORTS and nginx
The self-test proves the whole stack with this instance's own credentials, through the same HTTPS path your users take:
sudo /usr/local/sbin/forms-selftest
per-instance WebLogic password: AdminServer, WLS_FORMS and WLS_REPORTS RUNNING over https://<public-dns>/ (instance certificate verified); anonymous HTTP 401; wrong password HTTP 401
Forms: https://<public-dns>/forms/frmservlet?config=webstart serves the Java Web Start launch file (codebase="https://<public-dns>:443/forms/java/", frmall.jar)
Reports: in-process server rep_wls_reports_<private-host> Version 14.1.2.0.0 answers the administrator over https://<public-dns>/reports/; anonymous refused (REP-51019)
Reports: anonymous showenv, showjobs, showmap, killjobs, getjobid and report runs refused (REP-51019); /etc/passwd as a report refused to the administrator (REP-56132)
Forms: the servlet's test commands are disabled
repository: FRM_STB accepts this instance's schema password on 127.0.0.1:1521/ORCLPDB
JVMs (AdminServer, WLS_FORMS, WLS_REPORTS): /usr/lib/jvm/java-21-openjdk-21.0.12.1.1-1.2.0.1.el9.x86_64/bin/java (java-21-openjdk-headless-21.0.12.1.1-1.2.0.1.el9.x86_64)
FORMS_ROUNDTRIP_OK
Step 4: Get your URLs and passwords
The values generated for this instance are in a root-only file. This shows the file with the passwords hidden:
sudo sed -E 's/^((WEBLOGIC|RCU_SCHEMA)_PASSWORD=).*/\1(hidden)/' /root/forms-reports-credentials.txt
# Oracle Forms and Reports 14.1.2.0.0 - this instance's own credentials (generated on its first boot)
# Generated: <timestamp>
WEBLOGIC_USER=weblogic
WEBLOGIC_PASSWORD=(hidden)
FORMS_URL=https://<public-dns>/forms/frmservlet
REPORTS_URL=https://<public-dns>/reports/rwservlet
FMW_CONTROL_URL=https://<public-dns>/em
WEBLOGIC_REST_URL=https://<public-dns>/management/weblogic/latest
RCU_SCHEMA_PREFIX=FRM
RCU_SCHEMA_PASSWORD=(hidden)
RCU_DB_CONNECT=127.0.0.1:1521/ORCLPDB
DOMAIN_HOME=/opt/oracle/middleware/user_projects/domains/forms_domain
TLS_CERT_SHA256_FINGERPRINT=<sha256-fingerprint>
# The repository database's SYS/SYSTEM/PDBADMIN passwords are in /root/oracle-db-credentials.txt.
Print the administrator password when you need it (and store it in your secret manager):
sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /root/forms-reports-credentials.txt
The host name is the instance's public DNS name (or its public or private address when it has no public name). To serve Forms and Reports on your own DNS name, see Step 9. The certificate is self-signed and unique to the instance: compare its fingerprint with the TLS_CERT_SHA256_FINGERPRINT line when your browser shows it, or install your own certificate (Step 9).
Step 5: Run a form
Open https://<your-host>/forms/frmservlet in a browser to see Forms Services. Oracle Forms 14.1.2 starts applications in one of two ways:
- Java Web Start:
https://<your-host>/forms/frmservlet?config=webstartdownloads a.jnlpfile; open it with Java Web Start (javaws) on the user's desktop. - Forms Standalone Launcher (FSAL): download
https://<your-host>/forms/java/frmsal.jaronce, then start a form withjava -jar frmsal.jar -url "https://<your-host>/forms/frmservlet?config=standaloneapp".
The default configuration starts Oracle's test.fmx form. Because the certificate is self-signed, copy the instance's certificate (/etc/cloudimg/forms.crt, for example with scp) to the desktop and add it to the Java trust store first (keytool -importcert -alias forms -file forms.crt -cacerts), or install a CA-signed certificate (Step 9).
Check from the instance that the launch file points at the HTTPS address:
curl -s --cacert /etc/cloudimg/forms.crt 'https://localhost/forms/frmservlet?config=webstart' | grep -o 'codebase="[^"]*"'
Deploy your own forms. Put your compiled forms (.fmx), menus (.mmx) and libraries (.plx) in /opt/oracle/middleware/apps/forms; that folder is first in FORMS_PATH. Add your database connection (tnsnames.ora entry) to the domain's config/fmwconfig/tnsnames.ora, and add a named configuration for your application to formsweb.cfg (Fusion Middleware Control: Forms > Web Configuration). Compile forms on the instance with the Form Compiler:
sudo -u oracle bash -lc 'fr-env >/dev/null; frmcmp_batch help=yes | head -2'
Oracle Forms (Form Compiler) Version 14.1.2.0.0 (Production)
A typical compile is frmcmp_batch module=/opt/oracle/middleware/apps/forms/orders.fmb userid=<user>/<password>@<tns-alias> module_type=form compile_all=yes. The fr-env function in the oracle user's profile sets ORACLE_HOME, TERM=vt220, FORMS_INSTANCE and the library path the Forms and Reports tools need.
Step 6: Run a report
Reports Services answers at https://<your-host>/reports/rwservlet. Its in-process Reports server, rep_wls_reports_<host>, runs inside WLS_REPORTS, and Reports security is on: the weblogic administrator holds the Reports administrator role. Put your report definitions (.rdf, .rep, .jsp or .xml) in /opt/oracle/middleware/apps/reports (the server's source folder); file output may only be written to /opt/oracle/middleware/apps/reports-output.
Never put a database password in a report URL. URLs end up in browser history, proxy logs and Referer headers. (The image's own nginx and WebLogic access logs record paths without query strings.) Keep the connect string on the server instead, in a key map: add a line to the Reports servlet's cgicmd.dat, /opt/oracle/middleware/user_projects/domains/forms_domain/config/fmwconfig/servers/WLS_REPORTS/applications/reports_14.1.2/configuration/cgicmd.dat (owned by oracle), for example
sales: report=sales.rdf userid=<user>/<password>@<tns-alias> destype=cache desformat=PDF %*
then restart Reports (sudo systemctl restart forms-wls-reports). Users then run the report as https://<your-host>/reports/rwservlet?sales; %* passes on any further parameters they add (for example &p_region=EU). Reports security asks each user to sign in before a report runs.
Check the server from the instance. The administrator's password goes in a POST body read from a file, never in a URL or on the command line:
PW="$(sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /root/forms-reports-credentials.txt)"
(umask 077; printf 'data = "authid=weblogic/%s"\n' "$PW" > ~/.rw-auth); unset PW
curl -s --cacert /etc/cloudimg/forms.crt -K ~/.rw-auth https://localhost/reports/rwservlet/getserverinfo | sed 's/<[^>]*>/ /g' | tr -s ' \n' ' ' | grep -o 'Server Name [^ ]* Version [^ ]* Security Mode [A-Za-z]* Running Mode [A-Za-z-]*'
rm -f ~/.rw-auth
Server Name rep_wls_reports_<private-host> Version 14.1.2.0.0 Security Mode Secure Running Mode In-process
Note that Oracle has announced Oracle Reports as deprecated in 14.1.2 (it remains fully supported in this release; Oracle recommends Oracle Analytics Publisher for new reporting work).
Step 7: Fusion Middleware Control
Fusion Middleware Control (/em), the REST management API (/management/) and the other administration paths (/console, which in WebLogic 14.1.2 only points to WebLogic Remote Console, /sysman, /dms) answer only requests from the instance itself. Requests from anywhere else get HTTP 403, and administration requests are rate-limited per address. Because the image ships Oracle's base release without Critical Patch Updates, keep administration closed where you can and reach it through SSH.
Through an SSH tunnel (nothing is opened). For the REST management API and WebLogic Remote Console, forward a local port to the instance's own HTTPS port and use https://localhost:8443/management/weblogic/latest:
ssh -L 8443:127.0.0.1:443 -N -i <your-key.pem> ec2-user@<public-dns>
Fusion Middleware Control in a browser redirects to the instance's own host name on port 443, so for it, forward port 443 itself and point that name at your own machine. Add the line 127.0.0.1 <public-dns> to your hosts file (/etc/hosts, or C:\Windows\System32\drivers\etc\hosts), then run the following (binding local port 443 needs administrator rights) and open https://<public-dns>/em:
sudo ssh -L 443:127.0.0.1:443 -N -i <your-key.pem> ec2-user@<public-ip>
Remove the hosts line when you are done.
Or allow your own network. To reach them directly, allow your own public address or your office's network, never the internet:
sudo forms-admin-allow <your-public-address>/32
sudo forms-admin-allow --list shows the allowed networks, --remove <network> takes one away and --reset closes administration to everyone but the instance again.
Then open https://<your-host>/em and sign in as weblogic with the password from Step 4. Fusion Middleware Control manages the domain, the Forms configuration (formsweb.cfg, environment files, user sessions), the Reports server and the security realm. The WebLogic REST management API at https://<your-host>/management/weblogic/latest also works with WebLogic Remote Console. Check the servers through the REST API from the instance (the certificate is checked against the instance's own copy, /etc/cloudimg/forms.crt):
PW="$(sudo sed -n 's/^WEBLOGIC_PASSWORD=//p' /root/forms-reports-credentials.txt)"
(umask 077; printf 'user = "weblogic:%s"\n' "$PW" > ~/.wls-auth); unset PW
curl -s --cacert /etc/cloudimg/forms.crt -K ~/.wls-auth 'https://localhost/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes?links=none&fields=name,state'
rm -f ~/.wls-auth
{"items": [
{"name": "WLS_REPORTS", "state": "RUNNING"},
{"name": "WLS_FORMS", "state": "RUNNING"},
{"name": "AdminServer", "state": "RUNNING"}
]}
Step 8: The repository database
The repository is an Oracle Database 26ai container database ORCL with the pluggable database ORCLPDB, created on your instance's first boot. Its listener is bound to 127.0.0.1:1521; its SYS, SYSTEM and PDBADMIN passwords are in /root/oracle-db-credentials.txt. The Fusion Middleware schemas use the prefix FRM:
sudo -u oracle bash -lc 'sqlplus -S / as sysdba' <<'SQL'
SET PAGESIZE 50 LINESIZE 120 FEEDBACK OFF
ALTER SESSION SET CONTAINER = ORCLPDB;
COLUMN owner FORMAT A16
COLUMN comp_name FORMAT A40
SELECT owner, comp_name, version, status FROM schema_version_registry ORDER BY owner;
SQL
You can keep your Forms application data in this database (create your own users in ORCLPDB) or point Forms and Reports at your own database through tnsnames.ora. Back the database up with RMAN or EBS snapshots of /opt/oracle.
Step 9: Your own DNS name and certificate
To serve Forms and Reports on your own name, point a DNS record at the instance, then run forms-set-host. It makes a new certificate for the name, updates nginx and sets every server's front-end host (the servers restart, which takes a few minutes):
sudo /usr/local/sbin/forms-set-host forms.example.com
For a CA-signed certificate, replace /etc/nginx/ssl/forms.crt and /etc/nginx/ssl/forms.key (keep the key 0640 root:nginx), copy the certificate to /etc/cloudimg/forms.crt and run sudo systemctl reload nginx.
Step 10: Apply Oracle patches and Java updates
The image ships Oracle's 14.1.2.0.0 base release: the only Oracle patches in the Fusion Middleware home are the two one-off patches the installers apply themselves (listed below), and no Critical Patch Update or bundle patch is applied. Apply Oracle's Critical Patch Updates and bundle patches for Fusion Middleware, Forms and Reports, and Release Updates for the database, with your own Oracle support (My Oracle Support) and OPatch (/opt/oracle/middleware/fmw/OPatch, /opt/oracle/product/26ai/dbhome_1/OPatch); stop the servers first (see Managing the services). The compilers and Motif/X development packages that the Forms relink needs are installed.
Java: Fusion Middleware runs on /usr/lib/jvm/jre-21-openjdk (Oracle Linux OpenJDK 21), which dnf-automatic keeps patched; restart the servers after a Java update (sudo systemctl restart forms-wls-forms forms-wls-reports). Nothing in the Oracle home or the domain names the versioned JDK directory, so a Java update needs no file change. Oracle certifies JDK 21 for Fusion Middleware 14.1.2; if your Oracle support contract requires Oracle JDK itself, see "Running on Oracle JDK instead" below.
/usr/lib/jvm/jre-21-openjdk/bin/java -version 2>&1 | head -1; readlink /opt/oracle/middleware/fmw/oracle_common/jdk
ls /opt/oracle/middleware/fmw/inventory/patches
openjdk version "21.0.12.1" 2026-08-18 LTS
/usr/lib/jvm/jre-21-openjdk
36964826.xml 36990807.xml
The two inventory entries are the one-off fixes Oracle ships inside the 14.1.2.0.0 installers themselves.
Running on Oracle JDK instead (Oracle support customers). If your Oracle support contract requires Oracle JDK, install it yourself under your own Oracle entitlement; cloudimg does not supply it:
- Sign in to Oracle with your account and download the Oracle JDK 21 RPM for Linux x64 (
jdk-21_linux-x64_bin.rpm) under the terms your Oracle licence gives you, then copy it to the instance. - Stop Forms and Reports, install the JDK, find its directory and point the Oracle home's
oracle_common/jdklink at it:
text
sudo systemctl stop forms-wls-forms forms-wls-reports forms-adminserver forms-nodemanager
sudo dnf -y install ./jdk-21_linux-x64_bin.rpm
ORACLE_JDK=$(dirname "$(dirname "$(rpm -ql jdk-21 | grep '/bin/java$' | head -1)")"); echo "${ORACLE_JDK}"
sudo -u oracle ln -sfn "${ORACLE_JDK}" /opt/oracle/middleware/fmw/oracle_common/jdk
- Point every other place that names the OpenJDK path at it (the systemd units, the domain, the Oracle home's install records, the
oracleuser's profile and the cloudimg tools), then start the servers again:
text
sudo grep -rlsIF /usr/lib/jvm/jre-21-openjdk /etc/systemd/system/forms-*.service \
/opt/oracle/middleware/user_projects/domains/forms_domain /opt/oracle/middleware/fmw/oui \
/home/oracle/.bash_profile /usr/local/lib/cloudimg/forms | sudo xargs sed -i "s|/usr/lib/jvm/jre-21-openjdk|${ORACLE_JDK}|g"
sudo systemctl daemon-reload
sudo systemctl start forms-wls-forms forms-wls-reports
From then on you update Oracle JDK under your Oracle entitlement. forms-selftest checks that the servers run Oracle Linux's OpenJDK, so after the switch its Java check fails by design; check the servers with the REST call in Step 7 instead. To go back, point the link at /usr/lib/jvm/jre-21-openjdk again and run the same sed with the two paths swapped.
Step 11: Check the security model
Only SSH and nginx listen on the network; every Oracle server listens on loopback:
sudo ss -Hltnp | awk '{print $4}' | sort -u
0.0.0.0:22
0.0.0.0:443
0.0.0.0:80
127.0.0.1:10803
127.0.0.1:1521
127.0.0.1:28131
127.0.0.1:7001
127.0.0.1:9001
127.0.0.1:9012
127.0.0.1:9501
127.0.0.1:9512
[::]:22
[::]:443
[::]:80
[::ffff:127.0.0.1]:32479
[::ffff:127.0.0.1]:5556
The loopback ports without a name above are the Reports server's and engine's CORBA endpoints, which change at every start. Oracle Reports also listens for its multicast discovery on UDP 14021: the image routes that group (228.5.6.7) over the loopback interface, and the host firewall keeps 14021 closed, so it never sees traffic from outside the instance.
No Oracle process can reach the instance metadata service (the request times out):
sudo -u oracle curl -s -m 5 -o /dev/null -w '%{http_code}\n' -X PUT -H 'X-aws-ec2-metadata-token-ttl-seconds: 60' http://169.254.169.254/latest/api/token || true
000
Fusion Middleware Control answers the instance itself but refuses every other address until you allow one (Step 7). This asks for it from the instance's own private address, which is not on the list:
H="$(cat /etc/cloudimg/forms-host)"; IP="$(hostname -I | awk '{print $1}')"
curl -s -o /dev/null -w '%{http_code}\n' --resolve "$H:443:$IP" --cacert /etc/cloudimg/forms.crt "https://$H/em"
403
The host firewall opens SSH, HTTP and HTTPS only (plus the DHCPv6 client that Oracle Linux keeps for IPv6 addressing):
sudo firewall-cmd --zone=public --list-services
dhcpv6-client http https ssh
Managing the services
| Unit | What it runs |
|---|---|
oracle-db.service |
the repository database and its listener (127.0.0.1:1521) |
forms-nodemanager.service |
Node Manager (127.0.0.1:5556) |
forms-adminserver.service |
AdminServer with Fusion Middleware Control (127.0.0.1:7001) |
forms-wls-forms.service |
WLS_FORMS (127.0.0.1:9001) |
forms-wls-reports.service |
WLS_REPORTS with the in-process Reports server (127.0.0.1:9012) |
nginx.service |
HTTPS on 443, redirect on 80 |
forms-wls-forms and forms-wls-reports start the AdminServer and Node Manager themselves, and every unit starts at boot in order. To restart everything: sudo systemctl restart forms-wls-forms forms-wls-reports; to stop Forms and Reports: sudo systemctl stop forms-wls-forms forms-wls-reports forms-adminserver forms-nodemanager.
Filesystem layout
| Path | Contents |
|---|---|
/opt/oracle/middleware/fmw |
Fusion Middleware Infrastructure + Forms and Reports Oracle home |
/opt/oracle/middleware/user_projects/domains/forms_domain |
the domain (made at first boot) |
/opt/oracle/middleware/apps/forms |
your .fmx/.mmx/.plx files (first in FORMS_PATH) |
/opt/oracle/middleware/apps/reports, .../reports-output |
your report definitions; file output |
/opt/oracle/product/26ai/dbhome_1, /opt/oracle/oradata |
database home; the repository database |
/root/forms-reports-credentials.txt, /root/oracle-db-credentials.txt |
this instance's credentials (root only) |
/etc/cloudimg/forms.crt |
this instance's certificate (public; for curl --cacert and desktop trust stores) |
/etc/nginx/forms-admin-allow.conf |
who may reach the administration paths (managed by forms-admin-allow) |
/var/log/forms-reports-firstboot.log |
first boot log |
Troubleshooting
- Port 443 refuses connections: first boot has not finished (Step 3). Check
sudo journalctl -u forms-firstboot.service -bandsudo cat /var/log/forms-reports-firstboot.log. /root/forms-reports-FIRSTBOOT-FAILED.txtexists: first boot stopped and removed its partial work; reboot once to retry (sudo reboot). If the database first boot failed, see/root/oracle-db-FIRSTBOOT-FAILED.txt.- Java Web Start or FSAL refuses the server: import the instance certificate into the desktop Java trust store, or install a CA-signed certificate (Step 9).
- REP-51002 / REP-52266 from Reports: check
forms-wls-reports.serviceis active and read$DOMAIN_HOME/servers/WLS_REPORTS/logs/reports/rwserver_diagnostic.log. Reports finds its server through multicast discovery, which the image keeps on the loopback interface (cloudimg-reports-discovery.service). - Out of memory: use m5.xlarge or larger; the heap sizes are in the
USER_MEM_ARGSlines of theforms-*.serviceunits.
Security recommendations
- Keep TCP 22 open only to your own networks; publish 443 to your users' networks.
- Reach administration through an SSH tunnel (Step 7); if you allow a network with
forms-admin-allow, allow only the addresses you manage the instance from and remove them when you are done. - Install a CA-signed certificate for your own DNS name (Step 9).
- Never put a database password in a report URL: use a key map (Step 6).
- Change the administrator password with
sudo forms-change-password. It updates the security realm, the three servers' boot identities and/root/forms-reports-credentials.txt, then restarts the servers (a few minutes). Run without options it generates a new random password. To choose the password yourself, store it in your secret manager first, so it cannot be lost if your SSH session drops during the change, and give it on standard input withsudo forms-change-password --stdin(12 or more characters with at least one letter and one digit, and no backslash or double quote). Once the password is in your secret manager you may delete the credentials file: the servers do not need it to start (onlyforms-selftestreads it), and from then onforms-change-password --stdinasks you for the current password. - Apply Oracle's Critical Patch Updates with your Oracle support (Step 10).
Support
For help with this image, contact cloudimg support:
- Support:
support@cloudimg.co.ukor www.cloudimg.co.uk/support, on hand 24 hours a day by email, with a guaranteed response within 24 hours: launch and first boot, the per-instance credentials, Forms Services and Reports Services over HTTPS, Fusion Middleware Control, the repository database, your own DNS name and certificate, Oracle Linux updates and troubleshooting - Website: www.cloudimg.co.uk
- User Guides: www.cloudimg.co.uk/guides
Oracle Forms and Reports documentation is at docs.oracle.com. Oracle software support, Oracle patches and Oracle licences come from Oracle under your own agreement.
Licensing and price
This image is bring your own licence: using Oracle Forms and Reports and the Oracle Database that holds its repository requires your own Oracle licences, and Oracle patches (Critical Patch Updates, bundle patches and database Release Updates) come from Oracle under your own agreement, as Step 10 describes. The Java runtime for Fusion Middleware is Oracle Linux's OpenJDK 21 (GPLv2 with the Classpath Exception). The cloudimg software charge of $0.04 per vCPU per hour (plus AWS infrastructure charges) is for what cloudimg adds to the image: the repository database, schemas and domain created on each instance at first boot with their own passwords and TLS certificate, HTTPS through nginx with administration closed by default, every Oracle server on the loopback address, SSH by key pair only, and the Oracle processes blocked from the instance metadata service. Your Oracle licence is not part of this charge; you obtain it from Oracle.
Oracle, Java and WebLogic are registered trademarks of Oracle and/or its affiliates. cloudimg is not affiliated with or endorsed by Oracle.