Oe
Applications Azure

Oracle E-Business Suite 12.2.12 Vision ERP Demo on Oracle Linux 7 (Azure) User Guide

| Product: Oracle E-Business Suite 12.2.12 Vision ERP Demo on Oracle Linux 7

Overview

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

Bring Your Own Licence (BYOL). This is a BYOL image. It contains no Oracle licence. You must hold appropriate Oracle licences to use Oracle E-Business Suite and Oracle Database. The Oracle Technology Network (OTN) Developer Licence that accompanies the EBS Vision demonstration media permits development, testing, and prototyping only — not production use. For production you must obtain the correct Oracle licences from Oracle or an authorised reseller. The cloudimg image fee covers cloudimg pre-configuration, the Oracle Linux 7 base, and 24/7 cloudimg support only — never any Oracle licence.

What's included in this image:

  • Oracle E-Business Suite 12.2.12 Vision installed at /u01
  • Oracle Database 19c (19.18 RU) as the backend RDBMS
  • Oracle WebLogic Server 10.3.6.0.230117
  • Oracle Forms and Reports 10.1.2.3
  • Web Tier 11.1.1.9
  • JDK 1.7.0_371 and JRE 8 Update 361
  • Critical Patch Updates applied (April 2023)
  • Helper scripts for host, database, and web-entry configuration
  • Pre-seeded credentials for the EBS Vision installation (see below — change before any non-demo use)
  • Azure Linux Agent (waagent) for provisioning and Azure integration
  • Latest OS security patches applied at build time
  • 24/7 cloudimg 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. Standard_B4ms (4 vCPU, 16 GB) is an acceptable burstable alternative.
  • Disk: the image is delivered as a two-disk appliance — a ~50 GB OS disk plus a ~400 GB data disk that carries the EBS software and Vision database, mounted at /u01. Both disks are attached automatically when you deploy from the Marketplace image.
  • Boot: Generation 1 (BIOS) VM.

Before deploying, ensure you have:

  1. An active Azure subscription
  2. An SSH key pair for access as azureuser
  3. Appropriate Oracle licences (BYOL — see Overview)
  4. Familiarity with Azure VM management, SSH, and Oracle EBS administration

Step 1: Deploy the VM

  1. From the Azure Marketplace, locate Oracle E-Business Suite 12.2.12 Vision ERP Demo on Oracle Linux 7 by cloudimg and select Get It Now / Create.
  2. Choose your subscription, resource group, and region.
  3. Select VM size Standard_D4s_v3 (16 GB RAM minimum).
  4. Set the authentication type to SSH public key, username azureuser, and paste your public key.
  5. Under Networking, the image ships with only SSH (port 22) open by default. You will open the EBS ports after deployment (see Step 7).
  6. (Recommended) On the VM's Public IP resource, set a DNS name label (for example mycompany-ebs) so the VM has a stable public hostname such as mycompany-ebs.<region>.cloudapp.azure.com. You will use this hostname as the EBS Web Entry point in Step 5.
  7. Review and create. Wait for the VM to finish provisioning.

Step 2: Connect via SSH

Connect as azureuser:

ssh -i your-key.pem azureuser@<vm-public-ip-or-dns>

Switch to the root user:

sudo su -

Step 3: Configure the hosts file

As root, run the hosts configuration script. This sets the VM's private IP and a stable internal hostname in /etc/hosts. It only needs to be run once:

cd /u01/install/scripts
. ./updatehosts.sh
hostnamectl set-hostname apps.example.com

When prompted with cp: overwrite '/etc/hosts.org'?, enter y.

The script reads the VM's local IP address automatically (it is cloud-agnostic and does not depend on any cloud metadata service), so it works unchanged on Azure.

Step 4: Start the Oracle Database

Start the Oracle Database and Listener as root. First start takes approximately 10 minutes:

service ebscdb start

Wait for Database opened. and Listener service EBSDB started.

Step 5: Configure the Web Entry Point

Switch to the oracle user and run the web-entry configuration script. This tells EBS the public hostname users will use to reach the suite, then runs AutoConfig (~10 minutes):

sudo su - oracle
cd /u01/install/scripts/
./configwebentry.sh

Answer the prompts using your Azure public hostname (the DNS label you set in Step 1):

Prompt Example value (Azure)
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 (must be uppercase)
Run FS Context File press Enter to accept the default
APPS user password apps

Wait for AutoConfig completed successfully.

If you did not set a DNS label, you may use the VM's public IP address as the Web Entry Host Name, but a DNS label is strongly recommended because EBS embeds this value in generated URLs.

Step 6: Start the application tier

Return to root and start the application services (first start ~20 minutes):

exit
service apps start

Wait for the control scripts to finish (adapcctl.sh: exiting with status 0, etc.).

Step 7: Open the EBS ports and access the console

By default only SSH (22) is open. In the VM's Network Security Group, add inbound rules — restricted to your own IP / trusted networks only — for the EBS ports:

Port Purpose
8000 EBS HTTP (application login)
7001 / 7002 WebLogic Admin Console
1521 Oracle Database Listener (only if you need direct DB access)

Then browse to:

http://<your-dns-name>:8000/OA_HTML/AppsLogin

for example http://mycompany-ebs.<region>.cloudapp.azure.com:8000/OA_HTML/AppsLogin.

Log in as sysadmin. The pre-seeded EBS Vision credentials are stored on the VM at /stage/scripts/oracle-credentials.

Important — change the demo credentials. The Vision demo ships with pre-seeded application and schema passwords (sysadmin, SYSTEM, SYS, WebLogic, and the demo/schema users) so the demonstration works out of the box. These are documented demo values and must be changed before any non-demonstration or internet-exposed use. Rotate the EBS application passwords (FNDCPASS / AFPASSWD), the database account passwords, and the WebLogic credentials, and keep the EBS/WebLogic ports restricted to trusted networks.

Managing services

Always start the database before the application tier, and stop the application tier before the database.

sudo su -
service ebscdb start | stop      # database + listener
service apps  start | stop       # application tier

The database and application services do not start automatically on boot — start them manually after each VM restart.

Filesystem layout

Mount point Size Description
/ ~38 GB Root filesystem (OS disk)
/boot ~2 GB Kernel files (OS disk)
/u01 ~393 GB Oracle software + Vision database (data disk)

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
RDBMS Oracle Home Oracle Database 19c (19.18 RU)
Oracle WebLogic Server 10.3.6.0.230117
Oracle Forms and Reports 10.1.2.3
Web Tier 11.1.1.9
JDK / JRE 1.7.0_371 / JRE 8u361

Security recommendations

  • Restrict ports: allow 8000, 7001, 7002, and 1521 only from trusted IPs — never the public internet.
  • Change the demo credentials (EBS application, database, and WebLogic) before any non-demo use.
  • Use HTTPS: terminate TLS at a load balancer or configure SSL for the EBS web tier.
  • Keep patched: apply Oracle Critical Patch Updates and OS updates regularly.
  • BYOL compliance: ensure your Oracle licensing covers your usage; OTN terms are development/test 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.

Database fails to start: run service ebscdb status; verify /etc/hosts was configured (Step 3); check df -h /u01.

AutoConfig fails during configwebentry.sh: ensure the database is running first; enter EBSDB in uppercase; enter apps as the APPS password.

Cannot reach the console on 8000: confirm both database and application tier are running, the NSG allows TCP 8000 from your IP, and the Web Entry hostname matches the DNS name you are browsing to.

Support

  • Email: support@cloudimg.co.uk
  • Website: www.cloudimg.co.uk
  • Support hours: 24/7 with a guaranteed 24 hour response SLA