SecureAnyCloud
Deployment guide

Oracle E-Business Suite 12.2.12 Vision ERP demo

Overview

Oracle E-Business Suite (EBS) is a comprehensive suite of integrated global business applications for enterprise resource planning (ERP), customer relationship management (CRM), and supply chain management. This image from SecureAnyCloud deploys the EBS 12.2.12 Vision demonstration environment on Oracle Linux 8.10 from the Azure Marketplace. The Vision instance ships with Oracle's sample dataset for demonstration, evaluation, and testing.

Bring Your Own License (BYOL). This is a BYOL image, and it contains no Oracle license. You must hold appropriate Oracle licenses to use Oracle E-Business Suite and Oracle Database.

The Oracle Technology Network (OTN) Developer License that accompanies the EBS Vision demonstration media permits development, testing, and prototyping only. It does not permit production use. For production, obtain the correct Oracle licenses from Oracle or an authorized reseller. The SecureAnyCloud image fee covers SecureAnyCloud pre-configuration, the Oracle Linux 8 base, and 24/7 SecureAnyCloud support only, never any Oracle license.

What you get:

  • Oracle E-Business Suite 12.2.12 Vision installed at /u01
  • Oracle Database 19c (19.18 RU, container database EBSCDB, pluggable database EBSDB), relinked on Oracle Linux 8
  • Oracle WebLogic Server 10.3.6, Oracle Forms and Reports 10.1.2.3, Web Tier 11.1.1.9
  • Oracle Linux 8.10 with the Unbreakable Enterprise Kernel (UEK 7), fully patched at build time, one kernel installed
  • oracle-ebs-server-R12-preinstall and oracle-database-preinstall-19c, which are Oracle's EBS and Database prerequisite packages and kernel settings for Oracle Linux 8
  • The database and the EBS application tier start automatically on every boot (systemd services)
  • Per-VM passwords, generated on the first boot of your VM and written to a root-only file, for SYSADMIN, the Vision demo users, APPS/APPLSYS, WebLogic, SYSTEM, SYS and every supporting account (EBS_SYSTEM, all EBS product schemas, APPLSYSPUB, GUEST, RECON). The first-boot service then proves that no previous or published default password (such as GUEST/ORACLE or APPLSYSPUB/PUB) still works. If anything fails, the web tier is not started
  • Swap on the Azure temporary disk (never on the OS disk)
  • Azure Linux Agent and cloud-init for provisioning
  • 24/7 SecureAnyCloud support with a guaranteed 24-hour response SLA

Sizing and prerequisites

Oracle EBS is resource-intensive. The minimum footprint is 16 GB RAM and 500 GB of disk.

  • Recommended VM size: Standard_D4s_v3 (4 vCPU, 16 GB RAM) or larger. For a more responsive demo with several users, use Standard_E4s_v3 (4 vCPU, 32 GB RAM).
  • Disk: the image is delivered as a two-disk appliance with a 64 GB OS disk and a 400 GB data disk. The data disk carries the EBS software and the Vision database, and it is mounted at /u01. Both disks are attached automatically when you deploy from the Marketplace image.
  • Boot: Generation 2 (UEFI) VM.
  • Swap: a 16 GB swap file is created on the VM's temporary disk (/mnt) at every boot. Pick a VM size that has a temporary disk. Sizes ending in s, such as D4s_v3 and E4s_v3, have one.

Before you deploy, make sure you have:

  • An active Azure subscription
  • An SSH key pair for access as azureuser
  • Appropriate Oracle licenses (BYOL, see the Overview)
  • Familiarity with Azure VM management, SSH, and Oracle EBS administration
1

Deploy the VM

  • In the Azure Marketplace, find Oracle E-Business Suite 12.2.12 Vision ERP Demo on Oracle Linux 8 by SecureAnyCloud and select Create.
  • Choose your subscription, resource group, and region.
  • Select VM size Standard_D4s_v3 or larger (16 GB RAM minimum).
  • Set the authentication type to SSH public key, username azureuser, and paste your public key.
  • Under Networking, note that the image opens only SSH (22). Restrict it to your own IP address. EBS serves its login page over plain HTTP on port 8000. Either reach it through an SSH tunnel (Step 4) or, after deployment, add an inbound rule for 8000 limited to your own IP address. Never open it to the internet.
  • Review your settings and create the VM.

The first boot takes about 25 to 35 minutes before the login page answers. During that time the database starts, the per-VM passwords are generated and applied (including an AutoConfig run), and the application tier (WebLogic, Oracle HTTP Server and the concurrent managers) starts. Later boots take about 10 minutes.

2

Connect via SSH and check the services

Connect to the VM over SSH:

ssh azureuser@<vm-public-ip>

Check the progress of the first boot:

sudo systemctl status ebs-db ebs-firstboot ebs-apps --no-pager

All three show active (exited) when EBS is up. To follow the first boot as it happens:

sudo journalctl -fu ebs-firstboot -u ebs-apps
3

Read your credentials

The passwords for this VM are generated at first boot and stored in a root-only file:

sudo cat /root/ebs-credentials

Entry Used for

SYSADMIN_PASSWORD EBS web sign-in as SYSADMIN

APPS_PASSWORD the APPS / APPLSYS schema (AutoConfig, adop, control scripts)

WEBLOGIC_PASSWORD the WebLogic weblogic administrator

SYSTEM_PASSWORD / SYS_PASSWORD database administrators (container database EBSCDB)

DEMO_USERS_PASSWORD the Vision demo users (OPERATIONS, CBROWN, MFG, HRMS, ...)

EBS_SYSTEM_PASSWORD the EBS system schema in the EBSDB pluggable database

BASE_SCHEMAS_PASSWORD, APPLSYSPUB_PASSWORD, GUEST_PASSWORD, RECON_PASSWORD supporting EBS accounts. You do not sign in with these, and they are rotated so no shared value remains

Every VM gets its own values, and nothing is shared between deployments. Keep a copy in your password manager.

4

Open the EBS login page

EBS identifies itself as the host apps.example.com on port 8000, and the login page redirects to that name. With the port 8000 rule from Step 1 in place, map that name to your VM's public IP in your local hosts file.

Add the entry for your operating system:

  • macOS / Linux: add <vm-public-ip> apps.example.com to /etc/hosts
  • Windows: add the same line to C:\Windows\System32\drivers\etc\hosts (edit as Administrator)

Then browse to this address:

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

Sign in as SYSADMIN with SYSADMIN_PASSWORD from Step 3, or as a Vision demo user such as OPERATIONS with DEMO_USERS_PASSWORD.

Alternatively, keep port 8000 closed and use an SSH tunnel. Map apps.example.com to 127.0.0.1 in your hosts file, then run ssh -L 8000:apps.example.com:8000 azureuser@<vm-public-ip>.

Step 5 (optional): Use your own host name

To have users reach EBS on a real DNS name (for example an Azure DNS label mycompany-ebs.<region>.cloudapp.azure.com), set the DNS name label on the VM's public IP resource. Then run the web-entry configuration script as oracle. The script runs AutoConfig, which takes about 10 minutes:

sudo systemctl stop ebs-apps
sudo su - oracle cd /u01/install/scripts/ ./configwebentry.sh

Prompt Example value

Web Entry Protocol http

Web Entry Host Name mycompany-ebs

Web Entry Domain Name <region>.cloudapp.azure.com

Web Entry Port 8000

ORACLE_SID EBSDB (uppercase)

Run FS Context File press Enter to accept the default

APPS user password APPS_PASSWORD from /root/ebs-credentials

Wait for AutoConfig completed successfully., then exit back to azureuser and run sudo systemctl start ebs-apps, which takes about 10 minutes. Then browse to http://mycompany-ebs.<region>.cloudapp.azure.com:8000/OA_HTML/AppsLogin.

The server's own host name stays apps.example.com. EBS is installed against that name, and the image keeps it mapped to the VM's private IP at every boot.

Managing services

The database and application tier are systemd services and start automatically on boot, database first:

sudo systemctl stop ebs-apps
# application tier
sudo systemctl stop ebs-db
# database + listener (stop the application tier first)
sudo systemctl start ebs-db ebs-apps

/usr/local/sbin/ebs-ctl, the script those services call, does the same and reads the APPS and WebLogic passwords from /root/ebs-credentials for you:

sudo /usr/local/sbin/ebs-ctl status
sudo /usr/local/sbin/ebs-ctl stop
# application tier, then database
sudo /usr/local/sbin/ebs-ctl start
# database, then application tier

As oracle, /u01/install/APPS/scripts/startapps.sh and stopapps.sh prompt for the APPS user, APPS password and WebLogic password.

Changing the passwords later

The per-VM passwords are already unique to your VM. To set your own values, use Oracle's standard tools as oracle with the run edition environment (. /u01/install/APPS/EBSapps.env run): FNDCPASS / AFPASSWD for SYSADMIN and APPLSYS (after an APPLSYS change, update the WebLogic data source with txkManageDBConnectionPool.pl -options=updateDSPassword), txkUpdateEBSDomain.pl -action=updateAdminPassword for WebLogic, and ALTER USER for SYSTEM and SYS. Update /root/ebs-credentials afterwards so ebs-ctl and the boot services keep working.

If you plan to apply EBS patches with adop, run adop phase=fs_clone once first so the patch file system picks up this VM's APPS and WebLogic passwords.

Ports

Port Purpose Default

22 SSH open in the NSG (restrict it to your IP)

8000 EBS HTTP (application login) open in the VM firewall; add an NSG rule from your own IP, or use an SSH tunnel

7001 / 7002 WebLogic Admin Console closed. Open in the NSG and with firewall-cmd only if you need it, from trusted IPs

1521 Database listener closed. Open only for direct database access from trusted IPs

To open an extra port in the VM firewall, run, for example, sudo firewall-cmd --permanent --add-port=7001/tcp && sudo firewall-cmd --reload.

Filesystem layout

Mount point Size Description

/ ~37 GB (LVM rootvg) Root filesystem (OS disk)

/boot, /boot/efi ~1 GB Kernel and UEFI boot files (OS disk)

/u01 ~393 GB Oracle software + Vision database (data disk, LUN 0)

/mnt varies Azure temporary disk, holds the swap file (contents are lost on deallocation)

The /u01 data disk is mounted automatically via /etc/fstab (by filesystem UUID, with nofail).

Server components

Component Version

Oracle E-Business Suite 12.2.12

Operating system Oracle Linux 8.10, UEK 7

RDBMS Oracle Home Oracle Database 19c (19.18 RU)

Oracle WebLogic Server 10.3.6

Oracle Forms and Reports 10.1.2.3

Web Tier 11.1.1.9

Security recommendations

  • Restrict ports: allow 22 and 8000 only from trusted IPs, and keep 7001, 7002 and 1521 closed unless you need them.
  • Protect /root/ebs-credentials. It holds this VM's administrative passwords.
  • Use HTTPS: terminate TLS at an Azure Application Gateway or load balancer, or configure SSL for the EBS web tier.
  • Keep patched: run sudo dnf update for Oracle Linux updates and apply Oracle Critical Patch Updates for EBS and the database.
  • BYOL compliance: make sure your Oracle licensing covers your usage. OTN terms cover development and testing only.

Troubleshooting

Cannot SSH: confirm the VM finished provisioning, that the NSG allows TCP 22 from your IP, and that you are connecting as azureuser.

Login page does not answer yet: on first boot allow up to 35 minutes; check sudo systemctl status ebs-db ebs-firstboot ebs-apps and sudo journalctl -u ebs-apps.

Browser shows "apps.example.com" cannot be found: add the hosts-file entry from Step 4, or configure your own web entry host (Step 5).

/root/ebs-credentials is missing: the first-boot service has not finished or has failed. See sudo journalctl -u ebs-firstboot. It resumes where it stopped: sudo systemctl restart ebs-firstboot && sudo systemctl start ebs-apps.

Database fails to start: check df -h /u01 and that /etc/hosts maps apps.example.com to the VM's private IP (sudo systemctl restart ebs-hostfix refreshes it).

Support

  • Email: sales@secureanycloud.com
  • Website: secureanycloud.com
  • Support hours: 24/7 with a guaranteed 24-hour response SLA

Deploy on Azure

Launch Oracle E-Business Suite 12.2.12 Vision ERP Demo on Oracle Linux 8 with 24/7 support from SecureAnyCloud.

View this image

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com

Deploy on Azure