Oe
Applications AWS

Oracle E-Business Suite 12.2 Vision on Oracle Linux 8 on AWS User Guide

| Product: Oracle E-Business Suite 12.2 Vision on Oracle Linux 8 on AWS

Overview

This guide covers launching and using the Oracle E-Business Suite 12.2 Vision on Oracle Linux 8 AMI from cloudimg on Amazon EC2. Oracle E-Business Suite (EBS) is Oracle's integrated suite of business applications: financials, procurement, order management, manufacturing, supply chain, projects and human resources. The Vision instance is Oracle's demonstration environment, loaded with the sample data of Oracle's fictional Vision company, so every module has realistic records to explore, demonstrate and train on.

The cloudimg image adds:

  • Oracle's own Vision appliance, moved onto Oracle Linux 8.10 on AWS. The application and database tree of Oracle's EBS 12.2.12 Vision demonstration appliance is moved onto Oracle Linux 8.10 on AWS with the Unbreakable Enterprise Kernel (UEK), fully patched through dnf at build time. No Oracle patch from My Oracle Support is applied: you apply Oracle patches with your own Oracle support (see Step 10).
  • Everything starts by itself. systemd services map the EBS host name, start the database, prepare the instance on its first boot and then start the application tier, in that order, on every boot.
  • Credentials made on your instance, not on ours. On the first boot of every instance, a one time service creates new passwords for SYSADMIN, the Vision demo users, APPS and APPLSYS, the WebLogic administrator, SYSTEM, SYS and every internal account, and writes them to a file only root can read. None of Oracle's published Vision default passwords works on your instance. The same first boot also gives the instance its own WebLogic encryption salt, its own keys and wallets for WebLogic, the web tier and the database, and its own jar-signing key.
  • Fail closed. If first boot cannot finish, the EBS web tier is not started, and a message in the login banner says what failed and how to retry.
  • Only SSH on the network. The instance firewall allows SSH only. The EBS web pages, the WebLogic console and the database listener are reached through an SSH tunnel, so nothing but SSH is exposed until you choose otherwise.
  • A separate volume for EBS. The EBS software and the Vision database live on their own EBS volume mounted at /u01, which you resize independently of the root volume.

What is on the image: Oracle E-Business Suite 12.2.12 Vision (application tier with Oracle WebLogic Server 10.3.6, Oracle HTTP Server and the concurrent managers), Oracle Database 19c (container database EBSCDB, pluggable database EBSDB), Oracle Linux 8.10 with UEK, cloud-init and the AWS Systems Manager agent.

Default user: ec2-user (key pair login) | Architecture: x86_64 | Recommended instance type: m5.2xlarge

Licensing and price

Bring your own licence. This image contains no Oracle licence: you must hold your own Oracle licences for Oracle E-Business Suite and Oracle Database to use them. The application tier also runs Oracle WebLogic Server; check the WebLogic Server terms with Oracle, as your E-Business Suite licence may or may not cover it. The Vision demonstration environment is for evaluation, demonstration and training only under Oracle's Vision demonstration terms; it is not for production use. For production you need the correct Oracle licences from Oracle or an authorised reseller.

The listing costs $0.04 per vCPU-hour plus your AWS infrastructure charges, and is priced on every x86_64 instance type AWS offers with at least 16 GiB of memory. The $0.04 per vCPU-hour charge covers what cloudimg adds: moving Oracle's Vision appliance onto a patched Oracle Linux 8.10, the per-instance passwords and keys made at first boot with every published value proven refused, the fail-closed web tier, the SSH-only firewall and the boot services. It never includes an Oracle licence. Licensing questions about Oracle software go to Oracle.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. cloudimg is not affiliated with or endorsed by Oracle.

Prerequisites

  1. An AWS account subscribed to the listing.
  2. An EC2 key pair in the Region you launch in.
  3. A VPC subnet with a route to the internet (or a private route you use for management).
  4. A security group that allows TCP 22 (SSH) from your own IP address only. No other port is needed: the EBS web pages are reached through an SSH tunnel (Step 5).
  5. An SSH client on your workstation, and a web browser. Oracle Forms pages also need a Java runtime on your workstation (see Step 5).
  6. The Oracle licences described under Licensing.

Instance type: EBS runs the database and the whole application tier on one instance, so it needs memory.

Use Instance type
Recommended m5.2xlarge (8 vCPU, 32 GiB memory)
Minimum 16 GiB memory, for example m5.xlarge or r5.large
Short evaluation only Burstable t3 types work for a short look, but are not recommended for sustained use: EBS keeps the CPU busy and a burstable instance runs out of CPU credits

Step 1: Launch the instance

In the AWS Marketplace listing choose Continue to Subscribe, then Continue to Configuration, choose your Region, then Launch through EC2. In the EC2 launch page:

  1. Choose m5.2xlarge (or another type from the table above).
  2. Choose your key pair.
  3. Under Network settings, the listing's suggested security group allows SSH (TCP 22) from anywhere (0.0.0.0/0): change the source to your own IP (choose My IP). Do not add any other inbound rule.
  4. Under Configure storage you see the two volumes of the image: a 64 GiB root volume and the /u01 volume of 400 GiB that holds the EBS software and the Vision database. Keep both. You can make either one larger here, or later (see "Resizing the /u01 volume").
  5. Launch.

With the AWS CLI (replace the values in angle brackets; the AMI's own block device mappings create both volumes):

aws ec2 run-instances --region <region> --image-id <ami-id-from-the-listing> \
  --instance-type m5.2xlarge --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=ebs-vision}]'

A security group that allows only SSH from your own address can be created like this (replace the values; <your-ip> is your workstation's public IPv4 address):

aws ec2 create-security-group --region <region> --vpc-id <your-vpc> \
  --group-name ebs-vision-ssh --description "SSH from my IP only"
aws ec2 authorize-security-group-ingress --region <region> --group-id <new-security-group-id> \
  --protocol tcp --port 22 --cidr <your-ip>/32

Step 2: Connect to your instance

Version SSH user
Oracle E-Business Suite 12.2 Vision on Oracle Linux 8 ec2-user
ssh -i <your-key.pem> ec2-user@<public-ip>

ec2-user logs in with your EC2 key pair only and has sudo for root. EBS itself runs as the oracle operating system account, which owns /u01. That account has no password and cannot log in directly; switch to it from ec2-user with:

sudo su - oracle

Confirm the operating system release:

cat /etc/oracle-release

The instance's host name is the fixed EBS host name apps.example.com. EBS is installed against that name, and a boot service (ebs-hostfix) maps it to the instance's own private IP address in /etc/hosts on every boot, so the same image works on every instance:

hostname
getent hosts apps.example.com

hostname prints apps.example.com, and getent prints your instance's private IP address followed by apps.example.com apps.

Step 3: Wait for the first boot to finish

Four systemd services run in order on the first boot:

Service What it does
ebs-hostfix Maps apps.example.com to this instance's private IP address (every boot)
ebs-db Starts the database EBSCDB and its listener (every boot)
ebs-firstboot Creates this instance's own passwords and keys (first boot only; on later boots it sees it has already run and does nothing)
ebs-apps Starts the application tier: WebLogic, Oracle HTTP Server and the concurrent managers (every boot)

The first boot takes about 35 minutes before the login page answers (measured on t3.2xlarge). Later boots are faster, because the passwords are already in place. To follow the first boot as it happens (press Ctrl-C to stop following):

sudo journalctl -u ebs-firstboot -u ebs-apps -f

EBS is ready when both of these checks pass: ebs-apps prints active, and the login page answers with 200:

systemctl is-active ebs-apps
curl -s -L -o /dev/null -w '%{http_code}\n' http://apps.example.com:8000/OA_HTML/AppsLogin

While the first boot is still running, systemctl is-active ebs-apps prints activating (or inactive before it has begun) and curl prints 000. See all four services at once with:

systemctl is-active ebs-hostfix ebs-db ebs-firstboot ebs-apps

If first boot fails, the web tier stays down on purpose (fail closed). The login banner shows a message naming the step that failed, and the same message is in /root/EBS-FIRSTBOOT-FAILED.txt. Read the log, then retry; first boot picks up where it stopped:

sudo cat /root/EBS-FIRSTBOOT-FAILED.txt
sudo journalctl -u ebs-firstboot --no-pager | tail -50
sudo systemctl restart ebs-db ebs-firstboot && sudo systemctl start ebs-apps

If it fails again, contact support@cloudimg.co.uk with the message.

Step 4: Read your credentials

The passwords for this instance are created on its first boot and written to /root/ebs-credentials, readable by root only (mode 0600). This shows the file with every password hidden:

sudo sed -E 's/^([A-Z_]+_PASSWORD=).*/\1<hidden>/' /root/ebs-credentials
Entry Used for
SYSADMIN_PASSWORD EBS web sign in as SYSADMIN
DEMO_USERS_PASSWORD the Vision demo users, such as OPERATIONS, CBROWN and MFG
APPS_PASSWORD the APPS and APPLSYS schemas (control scripts, AutoConfig, adop)
WEBLOGIC_PASSWORD the WebLogic administrator weblogic
SYSTEM_PASSWORD, SYS_PASSWORD the database administrators
EBS_SYSTEM_PASSWORD, BASE_SCHEMAS_PASSWORD, APPLSYSPUB_PASSWORD, GUEST_PASSWORD, RECON_PASSWORD internal accounts: EBS_SYSTEM, all EBS product schemas, APPLSYSPUB, GUEST and RECON. You do not sign in with these; they are changed so that no shared value remains

Print a single password when you need it, for example the SYSADMIN password (and keep it in your password manager):

sudo sed -n 's/^SYSADMIN_PASSWORD=//p' /root/ebs-credentials

To see every value at once:

sudo cat /root/ebs-credentials

Every instance gets its own values; nothing is shared between instances, and none of Oracle's published Vision default passwords (sysadmin, welcome, apps, manager, ORACLE, PUB, RECON) works. First boot proves this before it starts the web tier: every new password must be accepted and every old or published default must be refused.

First boot also gives each instance its own keys. No two instances share any of them:

Secret What it protects
WebLogic domain encryption salt (SerializedSystemIni.dat) Every encrypted value stored in the WebLogic domain. A new salt is made for both the run (fs1) and patch (fs2) domains, and every stored encrypted value is re-encrypted under it
WebLogic DemoIdentity key The WebLogic servers' own TLS identity
Oracle HTTP Server (OHS) key and certificate The HTTPS port 4443 of the web tier
OHS proxy, OPMN and database XDB wallet keys The web tier's internal connections and the database's XML DB wallet
Jar-signing key (adkeystore.dat) The signature on EBS jar files. It is made by Oracle's own adjkey tool (see Step 10)
WebLogic administrator and Node Manager credentials of the patch file system (fs2) Oracle's password tools change the run file system only, so first boot also gives the patch file system's own WebLogic security store and Node Manager this instance's weblogic password, and both file systems' initial user record a hash of it

Step 5: Open the EBS login page through an SSH tunnel

The instance firewall allows SSH only, so the EBS web port (8000) and the WebLogic console (7001) are not reachable from the network. You reach them through an SSH tunnel from your workstation. EBS also redirects every request to its configured host name, apps.example.com, so your workstation must resolve that name to the tunnel.

1. Map apps.example.com to your own machine. Add this line to your workstation's hosts file:

127.0.0.1   apps.example.com
Workstation Hosts file How to edit
Windows C:\Windows\System32\drivers\etc\hosts Open Notepad with Run as administrator, then open the file
macOS /etc/hosts sudo nano /etc/hosts; afterwards run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux /etc/hosts sudo nano /etc/hosts

2. Start the tunnel. On your workstation, keep this session open while you use EBS:

ssh -i <your-key.pem> -L 8000:apps.example.com:8000 -L 7001:apps.example.com:7001 ec2-user@<public-ip>

Each -L forwards a port on your workstation to the same port on the instance, addressed by the name apps.example.com, which the instance resolves to its own private IP. If port 8000 or 7001 is already in use on your workstation, stop the program that uses it first: EBS redirects to port 8000 by name, so the local port must also be 8000.

3. Sign in. In your browser open:

http://apps.example.com:8000/OA_HTML/AppsLogin

Sign in as SYSADMIN with SYSADMIN_PASSWORD, or as a Vision demo user such as OPERATIONS with DEMO_USERS_PASSWORD (Step 4). OPERATIONS has responsibilities across the financial and supply chain modules of the Vision company; SYSADMIN has the System Administrator responsibilities.

Java for Oracle Forms. Oracle Application Framework (OA Framework) pages, such as the home page, the navigator and self service pages, run in any modern browser. Pages built with Oracle Forms (most setup and many core transaction screens) open in a Java client, so your workstation needs a Java runtime: Java Web Start or Oracle's Java Runtime Environment (JRE) browser plug in, as described in Oracle's EBS client documentation.

Step 6: Open the WebLogic Administration Console

With the tunnel from Step 5 running, open:

http://apps.example.com:7001/console

Sign in as weblogic with WEBLOGIC_PASSWORD (Step 4). The console manages the EBS WebLogic domain EBS_domain (WebLogic Server 10.3.6, the Fusion Middleware 11g stack Oracle ships with EBS 12.2): the AdminServer, the managed servers that run the EBS web applications (such as oacore, forms and oafm) and their data sources. In EBS 12.2, make configuration changes through Oracle's documented EBS procedures, because AutoConfig and online patching own most of the domain's settings.

Step 7: Work with the database

The database is Oracle Database 19c: container database EBSCDB with the pluggable database EBSDB that holds the EBS and Vision data, and a listener on port 1521 that is reachable on the instance only (the firewall does not open it). This shows the pluggable databases and their state:

sudo su - oracle -c '. /u01/install/APPS/19.0.0/EBSCDB_apps.env >/dev/null; sqlplus -s / as sysdba' <<'SQL'
set heading off feedback off pagesize 0
select name || ' ' || open_mode from v$pdbs;
SQL

EBSDB shows READ WRITE. For an interactive session as SYSDBA:

sudo su - oracle
. /u01/install/APPS/19.0.0/EBSCDB_apps.env
sqlplus / as sysdba

The environment files:

File Sets up
/u01/install/APPS/19.0.0/EBSCDB_apps.env the container database EBSCDB (SYSDBA work, the listener)
/u01/install/APPS/19.0.0/EBSDB_apps.env the pluggable database EBSDB
/u01/install/APPS/EBSapps.env run the application tier on the run file system (AutoConfig, adop, control scripts)

As oracle, source the application tier environment with:

. /u01/install/APPS/EBSapps.env run

EBS 12.2 uses online patching with two application file systems: fs1 is the run file system that serves users and fs2 is the patch file system that adop patches (the two swap roles at each cutover). EBSapps.env run always points at whichever one is currently the run file system.

Step 8: Start and stop EBS

The database and application tier start on every boot through the systemd services ebs-db and ebs-apps. The ebs-ctl command does the same by hand, reading the APPS and WebLogic passwords from /root/ebs-credentials for you. Check what is running:

sudo /usr/local/sbin/ebs-ctl status

The status lists the running database, listener, concurrent manager and WebLogic processes. Stop and start everything (the application tier stops before the database, and starts after it):

sudo /usr/local/sbin/ebs-ctl stop
sudo /usr/local/sbin/ebs-ctl start
Command What it does
sudo /usr/local/sbin/ebs-ctl status Shows the running EBS processes
sudo /usr/local/sbin/ebs-ctl stop Stops the application tier, then the database
sudo /usr/local/sbin/ebs-ctl start Starts the database, then the application tier
sudo /usr/local/sbin/ebs-ctl stop-apps, start-apps Stops or starts the application tier only
sudo /usr/local/sbin/ebs-ctl stop-db, start-db Stops or starts the database and listener only (stop the application tier first)

Stop EBS before you stop the instance. Run sudo /usr/local/sbin/ebs-ctl stop and wait for it to finish, then stop the instance from the EC2 console. A full stop of the application tier can take several minutes. When you start the instance again, the services bring EBS back by themselves; check readiness as in Step 3.

Step 9: Change passwords later

The passwords from first boot are already unique to your instance. To set your own values, use Oracle's documented tools as oracle, with the run file system environment (. /u01/install/APPS/EBSapps.env run), and follow the password management chapters of the Oracle E-Business Suite Security Guide for your release:

  • EBS users and EBS schemas: AFPASSWD. For example AFPASSWD -f SYSADMIN changes the SYSADMIN sign in, AFPASSWD -c APPS -s APPLSYS changes APPLSYS (and with it APPS), and AFPASSWD -c APPS -a changes all EBS product schemas. Changing APPLSYS has extra steps in Oracle's procedure: the application tier must be stopped, and afterwards AutoConfig is run and the WebLogic data source password is updated.
  • The WebLogic administrator: perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword.
  • SYSTEM and SYS: ALTER USER in SQL*Plus.

After every change, update /root/ebs-credentials to the new value (for example with sudo vi /root/ebs-credentials, keeping the file at mode 0600). ebs-ctl and the boot services read the APPS and WebLogic passwords from that file; if it is out of step, EBS does not start on the next boot.

First boot gives the patch file system (fs2) this instance's APPS and WebLogic passwords as well. Oracle's password tools change the run file system only, so if you change APPS or the WebLogic password yourself, run adop phase=fs_clone before your next online patching cycle so that fs2 carries the new values too.

Step 10: Apply Oracle patches

This image is built from Oracle's EBS 12.2.12 Vision media with no Oracle patch from My Oracle Support applied, because Oracle distributes EBS and Database patches to licensed customers through My Oracle Support. Apply Oracle's patches, including the quarterly Critical Patch Updates, under your own Oracle support, following the patching documentation in the Oracle E-Business Suite 12.2 documentation library (EBS patches are applied online with adop).

Oracle Linux packages are updated with dnf:

sudo dnf -y update

Stop EBS first (sudo /usr/local/sbin/ebs-ctl stop) when an update includes a new kernel, then reboot.

Jar signing. The jar files shipped in the image still carry the signature that Oracle's Vision appliance gave them. Every jar signed from first boot on, for example by patching or by adadmin, is signed with your instance's own key (Step 4). To re-sign all jars with your own key now:

  1. Stop the application tier:

text sudo systemctl stop ebs-apps

  1. As oracle, source the run file system environment and start adadmin:

text sudo su - oracle . /u01/install/APPS/EBSapps.env run adadmin

  1. Choose Generate Applications Files menu, then Generate product JAR files, and answer Yes to force regeneration of all jar files. This takes about an hour.
  2. Start the application tier again:

text sudo systemctl start ebs-apps

Optional: Open the EBS web port to your own IP address

The SSH tunnel is the recommended way in. If you prefer to reach EBS directly from one workstation, open port 8000 to your own IP address only, in both places that block it:

  1. Add an inbound security group rule for TCP 8000 from your address (replace the values):

text aws ec2 authorize-security-group-ingress --region <region> --group-id <your-security-group> \ --protocol tcp --port 8000 --cidr <your-ip>/32

  1. Open the port in the instance firewall:

text sudo firewall-cmd --permanent --add-port=8000/tcp && sudo firewall-cmd --reload

  1. In your workstation's hosts file, map apps.example.com to the instance's public IP address instead of 127.0.0.1, then browse to http://apps.example.com:8000/OA_HTML/AppsLogin.

Warning: EBS web traffic on port 8000 is plain HTTP. Passwords and business data cross the network unencrypted, which is why the tunnel (encrypted by SSH) is the default. Never open port 8000 to 0.0.0.0/0, and close it again when you are done (sudo firewall-cmd --permanent --remove-port=8000/tcp && sudo firewall-cmd --reload, and remove the security group rule). Keep 7001, 7002 and 1521 closed; use the tunnel for them.

Ports

Port Purpose Default
22 SSH Open in the instance firewall; allow it in the security group from your own IP only
8000 EBS web pages (Oracle HTTP Server, plain HTTP) Closed to the network; use the SSH tunnel (Step 5)
7001, 7002 WebLogic AdminServer and console Closed to the network; use the SSH tunnel for 7001 (Step 6)
1521 Database listener Closed to the network; use it on the instance (Step 7) or add -L 1521:apps.example.com:1521 to your tunnel

Check the instance firewall:

sudo firewall-cmd --list-services
sudo firewall-cmd --list-ports

The services list shows ssh, and no EBS port is listed.

Filesystem layout

Mount point Size Description
/ 64 GiB Root EBS volume: Oracle Linux 8
/u01 400 GiB Dedicated EBS volume: the EBS software, both application file systems and the Vision database

Key directories:

Path Purpose
/u01/install/APPS EBS installation base (application tier and database)
/u01/install/APPS/19.0.0 Oracle Database 19c home and its environment files
/u01/install/APPS/fs1, /u01/install/APPS/fs2 The two online patching file systems (run and patch)
/u01/install/APPS/EBSapps.env Application tier environment (. /u01/install/APPS/EBSapps.env run)
/root/ebs-credentials This instance's passwords (root only)
/root/EBS-FIRSTBOOT-FAILED.txt Present only if first boot failed
/usr/local/sbin/ebs-ctl Start, stop and status of EBS

Check space with:

df -h / /u01

Resizing the /u01 volume

The /u01 volume is separate from the root volume, so you can give EBS more room without touching the operating system:

  1. In the EC2 console, open the instance's Storage tab, choose the /u01 volume, then Actions, Modify volume, and enter the new size. Wait until the volume state shows optimizing or completed.
  2. On the instance, find the device that holds /u01 (the file system is ext4), then grow the file system:

text lsblk df -hT /u01 sudo resize2fs <device-of-u01>

If lsblk shows /u01 on a partition (for example nvme1n1p1) rather than on the whole disk, grow the partition first with sudo growpart <disk> <partition-number> (for example sudo growpart /dev/nvme1n1 1). ext4 grows while mounted, so no restart of EBS is needed.

Server components

Component Version
Oracle E-Business Suite 12.2.12 Vision demonstration instance
Oracle Database 19c (container EBSCDB, pluggable database EBSDB)
Oracle WebLogic Server 10.3.6 (domain EBS_domain)
Oracle HTTP Server Fusion Middleware 11g web tier shipped with EBS 12.2 (port 8000)
Oracle Forms and Reports 10.1.2.3, as shipped with EBS 12.2
Operating system Oracle Linux 8.10 with the Unbreakable Enterprise Kernel

Troubleshooting

SSH times out. Check that the security group allows TCP 22 from your current public IP address, that the instance has a public IP (or you use a private route), and that you log in as ec2-user with the key pair you chose at launch.

The login page does not answer yet. On the first boot allow about 35 minutes (measured on t3.2xlarge). Check the services and the log:

systemctl is-active ebs-hostfix ebs-db ebs-firstboot ebs-apps
sudo journalctl -u ebs-apps --no-pager | tail -20

The login banner says first boot failed. Follow "If first boot fails" in Step 3.

The browser says apps.example.com cannot be found, or it cannot connect. Check the hosts file entry on your workstation (Step 5) and that the SSH tunnel session is still open. EBS always redirects to http://apps.example.com:8000/, so browsing to localhost or an IP address ends on that name anyway.

Oracle Forms pages do not open. Install a Java runtime on your workstation (Java Web Start or Oracle's JRE browser plug in); OA Framework pages work without it.

The database does not start. Check free space on /u01 (df -h /u01) and that /etc/hosts maps apps.example.com to the instance's current private IP (getent hosts apps.example.com); sudo systemctl restart ebs-hostfix refreshes the mapping. Then sudo systemctl start ebs-db ebs-apps.

ebs-ctl says /root/ebs-credentials is missing or incomplete. First boot has not finished, or the file was edited. See sudo journalctl -u ebs-firstboot, and if you changed a password, check that the file has the new value (Step 9).

Security recommendations

  • Allow only TCP 22 in the security group, and only from your own IP address. Reach EBS through the SSH tunnel.
  • Keep ports 8000, 7001, 7002 and 1521 closed to the network. If you open 8000 for one workstation, remember it is plain HTTP.
  • Protect /root/ebs-credentials: it holds this instance's administrative passwords. Keep a copy in your password manager.
  • Create named EBS users for the people who use the system instead of sharing SYSADMIN.
  • Apply Oracle Critical Patch Updates under your own Oracle support, and update Oracle Linux with dnf.
  • Use the Vision instance for evaluation, demonstration and training only, as Oracle's Vision terms require.

How the starting passwords are handled

Most accounts can be reset by Oracle's tools without the current password: SYS, SYSTEM, EBS_SYSTEM, RECON, SYSADMIN and the Vision demo users, and every EBS product schema. At the end of the build these were reset to random values that were never written down, and the database stores them only as password hashes or in Oracle's encrypted form, so no value for them is on the image. GUEST can only be set by Oracle's AutoConfig, which first boot runs: it keeps a random build value that only the database holds, in Oracle's encrypted form, and every plain-text copy of it was removed from the image's files. First boot sets new values for all of them.

Three accounts are named exceptions to the rule that no build value is on the image:

Account Why Where its build value is on the image
APPS, with APPLSYS and APPS_NE, which share its password Oracle's AFPASSWD changes it only when given the current APPS password a random starting value in /etc/ebs/image-passwords (root only, mode 0600), and in encrypted form only, under the image's WebLogic encryption salt, in the EBSDataSource and ISGDatasource configuration
The WebLogic administrator weblogic Oracle's txkUpdateEBSDomain.pl changes it only when given the current password a random starting value in /etc/ebs/image-passwords, and in encrypted form only, under the image's salt, in the servers' boot.properties files, config.xml (Node Manager) and init-info/security.xml
APPLSYSPUB, the public sign-on schema EBS uses before anyone has signed in Oracle stores its password in plain text by design, in the GWYUID profile option in the database and in the .dbc file every application-tier client reads only inside the Oracle database files under /u01/install/APPS/data: the image's value and earlier build values, in the undo tablespace, the online redo logs and old row versions in the transaction data files. No other file on the image holds an APPLSYSPUB value

First boot gives each WebLogic domain a new salt and re-encrypts every stored value, so the image's encrypted copies of the APPS and weblogic values are gone. APPLSYSPUB is changed with AFPASSWD using the APPS password, so its build value is never needed on the image. Its earlier values stay inside the database files until Oracle reuses that space; the database refuses every one of them for sign-in, and APPLSYSPUB has only the few privileges EBS needs to check a sign-on.

First boot then:

  1. changes all three to values unique to the instance, before the database or web tier accepts a remote connection;
  2. proves that the APPS and weblogic starting values and Oracle's published appliance defaults are refused;
  3. checks that no copy of them is left in the EBS configuration, install (INST_TOP/admin/install, adgendbc.sh), log or home directories;
  4. shreds /etc/ebs/image-passwords.

Oracle's own tools change the APPS and WebLogic passwords on the run file system (fs1) only. The patch file system (fs2) keeps the appliance's own WebLogic security store, and a few files on both file systems keep Oracle's published appliance defaults (apps, welcome1) in encrypted form. First boot therefore also:

  • starts the patch file system's WebLogic AdminServer once, behind the connection guard described below, and changes its weblogic password and Node Manager password to this instance's value;
  • re-encrypts every stored value on either file system that is a starting value or a published appliance default to this instance's value;
  • gives the weblogic entry of both file systems' initial user record (DefaultAuthenticatorInit.ldift) a hash of this instance's password, and removes WebLogic's backup copies of earlier configurations;
  • proves that the patch file system's AdminServer starts with this instance's password and refuses welcome1 and the starting value, and that no stored value on either file system decrypts to an old one.

Until first boot has finished, the instance accepts new inbound TCP connections on port 22 only. This is an nftables guard, set before the database listener starts, so neither the database listener nor WebLogic nor the web tier can be reached remotely while a starting value is live.

If any step fails, the web tier stays down and the database is stopped. The login banner and /root/EBS-FIRSTBOOT-FAILED.txt say what failed and how to retry (see Step 3).

Oracle demonstration keys that are the same everywhere

A few files hold demonstration keys that are identical in every copy of Oracle's Vision appliance. EBS 12.2 does not use them, and they protect nothing of yours, so they are left as Oracle ships them: the demonstration certificate authority in the Fusion Middleware keystore service (config/fmwconfig/keystores.xml, with its bootstrap key), the demonstration wallets of the Oracle Application Server 10.1.2 components that EBS 12.2 does not run (Apache, OPMN and Web Cache), and the Oracle Java Object Cache demonstration keystore (.joc_demo_keystore.jks). Do not use any of them to protect anything.

Support

cloudimg's support team is on hand 24 hours a day by email for this image, with a guaranteed response within 24 hours: launch and first login, first boot and the per-instance credentials, the SSH tunnel to the EBS login page, starting and stopping EBS, Oracle Linux updates and troubleshooting.

  • Email: support@cloudimg.co.uk
  • Website: www.cloudimg.co.uk/support
  • Hours: 24 hours a day by email, with a guaranteed response within 24 hours

Oracle software support, patches and licences come from Oracle, and licensing questions about Oracle software go to Oracle. Oracle E-Business Suite documentation is at docs.oracle.com.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. cloudimg is not affiliated with or endorsed by Oracle.