Applications

Oracle E-Business Suite 12.2.12 Vision on OEL7 User Guide

| Product: Oracle E-Business Suite 12.2.12 Vision on OEL7 Supported by cloudimg

Overview

This guide covers the deployment and configuration of Oracle E-Business Suite (EBS) 12.2.12 Vision on Oracle Enterprise Linux 7 using cloudimg AMIs from the AWS Marketplace. Oracle EBS is a comprehensive suite of integrated, global business applications that provides enterprise resource planning (ERP), customer relationship management (CRM), and supply chain management capabilities. The Vision instance includes sample data for demonstration and testing purposes.

What's included in this AMI:

  • 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 hosts configuration, database startup, and web entry point setup
  • Randomly generated credentials for the EBS Vision installation
  • OS package update script for keeping the system current
  • AWS CLI v2 for AWS service integration
  • Systems Manager Agent (SSM) for remote management
  • CloudWatch Agent for monitoring
  • Latest security patches applied at build time
  • 24/7 cloudimg support with guaranteed 24 hour response SLA

Prerequisites

Before launching this AMI, ensure you have:

  1. An active AWS account
  2. An active subscription to the Oracle EBS 12.2.12 Vision listing on AWS Marketplace
  3. An EC2 key pair for SSH access
  4. Familiarity with EC2 instance management and SSH
  5. Understanding of Oracle EBS administration concepts

Recommended Instance Type: t3.xlarge (4 vCPU, 16 GB RAM) or larger. The minimum requirements are 2 vCPU, 16 GB RAM, and 500 GB disk space. Oracle EBS requires significant resources for acceptable performance.

Step 1: Launch the AMI

  1. Navigate to the AWS Marketplace and search for "Oracle E-Business Suite 12.2.12 Vision cloudimg"
  2. Click Continue to Subscribe, accept the terms, then Continue to Configuration
  3. Select your preferred Region and Software Version
  4. Click Continue to Launch
  5. Choose Launch through EC2 for full control over instance configuration
  6. Select your instance type (t3.xlarge recommended, minimum 16 GB RAM)
  7. Configure storage: 500 GB gp3 minimum
  8. Configure your Security Group with the following inbound rules:
Port Protocol Source Purpose
22 TCP Your IP SSH access
1521 TCP Your IP Oracle Database Listener port
8000 TCP Your IP EBS Administration Console Port Pool 1
8001 TCP Your IP EBS Administration Console Port Pool 2
7001 TCP Your IP WebLogic Console Port Pool 1
7002 TCP Your IP WebLogic Console Port Pool 2

Important: Restrict all ports to your IP or trusted networks only. Do not open EBS or WebLogic console ports to the public internet.

  1. Select your EC2 key pair and launch the instance

Step 2: Connect via SSH

Once your instance is running and has passed both status checks (2/2), connect using SSH:

ssh -i your-key.pem ec2-user@<public-ip-address>

To switch to the root user:

sudo su -

Important: Wait for the EC2 instance to reach 2/2 successful status checks before connecting. Early connection attempts may produce permission denied errors while the instance is still initialising.

Step 3: Configure the Hosts File

As the root user, run the hosts configuration script to set the private IP address in /etc/hosts and configure the hostname. This step only needs to be completed once:

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

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

Expected output:

Updating hosts file with the current IP
Fully Qualified Hostname for this server is : apps.example.com
IP Address Configured for this server is    : 172.x.x.x
cp: overwrite '/etc/hosts.org'? y

Step 4: Start the Oracle Database

Start the Oracle Database and Listener services as the root user. The average start time is approximately 10 minutes on a t3.xlarge instance:

service ebscdb start

Expected output includes:

Starting the container database EBSCDB ...
SQL*Plus: Release 19.0.0.0.0 - Production
ORACLE instance started.
Database mounted.
Database opened.

Starting listener process EBSCDB ...
LSNRCTL for Linux: Version 19.0.0.0.0 - Production
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=apps.example.com)(PORT=1521)))
Listener service EBSDB started.

Step 5: Configure the Web Entry Point

Before starting the application services, configure the EBS Web Entry URL. Switch to the oracle user and run the configuration script:

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

When prompted, enter the following values (adjust the hostname to match your EC2 instance Public IPv4 DNS):

Prompt Example Value
Web Entry Protocol http
Web Entry Host Name ec2-x-x-x-x.compute-1
Web Entry Domain Name amazonaws.com
Web Entry Port 8000
ORACLE_SID EBSDB (must be uppercase)
Run FS Context File Press Enter to accept default
APPS user password apps

The script will run AutoConfig to update context files. This takes approximately 10 minutes on a t3.xlarge instance.

Expected output ends with:

AutoConfig completed successfully.

Step 6: Start the Oracle Apps Services

Switch back to the root user and start the application tier services. The first start takes approximately 20 minutes on a t3.xlarge instance:

exit
service apps start

Expected output includes multiple service scripts completing with:

jtffmctl.sh: exiting with status 0
adopmnctl.sh: exiting with status 0
adapcctl.sh: exiting with status 0
adnodemgrctl.sh: exiting with status 0
adalnctl.sh: exiting with status 0

Wait for all services to finish starting before proceeding.

Step 7: Access the EBS Console

Once all services are running, access the EBS Administration Console in your web browser:

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

Example: http://ec2-x-x-x-x.compute-1.amazonaws.com:8000/OA_HTML/AppsLogin

Log in using the credentials from the oracle-credentials file located at /stage/scripts/oracle-credentials.

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 1.7.0_371
JRE Oracle Java Runtime Environment (JRE) 8 Update 361

Filesystem Layout

Mount Point Size Description
/ 38 GB Root filesystem
/boot 2.0 GB Operating system kernel files
/u01 393 GB Oracle software installation directory (EBS, Database, WebLogic)

Key directories:

Directory Purpose
/u01/install EBS installation base
/u01/install/APPS Application tier software
/u01/install/APPS/19.0.0 Oracle Database 19c home
/u01/install/scripts Helper scripts for configuration

Managing Services

Start the database:

sudo su -
service ebscdb start

Stop the database:

sudo su -
service ebscdb stop

Start the application services:

sudo su -
service apps start

Stop the application services:

sudo su -
service apps stop

Important: Always start the database before the application services, and stop the application services before the database.

Scripts and Log Files

Script/Log Path Description
initial_boot_update.sh /stage/scripts Updates the OS with the latest packages on first boot
initial_boot_update.log /stage/scripts Output log for the boot update script
oracle-credentials /stage/scripts Randomly generated credentials for the EBS Vision installation
updatehosts.sh /u01/install/scripts Configures /etc/hosts with the private IP
configwebentry.sh /u01/install/scripts Configures the EBS Web Entry URL and runs AutoConfig

On Startup

An OS package update script runs on first boot to ensure the image is fully up to date. You can disable this by removing the script and its crontab entry:

rm -f /stage/scripts/initial_boot_update.sh

crontab -e
# Delete the following line, save and exit:
@reboot /stage/scripts/initial_boot_update.sh

Note: The Oracle Database and EBS application services do not start automatically on boot. You must start them manually after each instance restart using the commands in the Managing Services section.

Troubleshooting

Cannot connect via SSH

  1. Verify the instance has reached 2/2 status checks in the EC2 console
  2. Confirm your security group allows inbound TCP port 22 from your IP
  3. Ensure you are using the correct key pair and connecting as ec2-user

Database fails to start

  1. Check the service status: service ebscdb status
  2. Verify /etc/hosts is correctly configured with the private IP
  3. Check disk space: df -h /u01
  4. Review the database log at /u01/install/APPS/19.0.0/appsutil/log/EBSDB_apps/adcdblnctl.txt

Application services fail to start

  1. Ensure the database is running first: service ebscdb start
  2. Ensure the web entry point has been configured: run configwebentry.sh if not done
  3. Review the application logs at /u01/install/APPS/fs1/inst/apps/EBSDB_apps/logs/appl/admin/log/
  4. Verify sufficient memory is available: free -m (minimum 16 GB recommended)

Cannot access EBS console on port 8000

  1. Verify both database and application services are running
  2. Confirm your security group allows inbound TCP port 8000 from your IP
  3. Check that the web entry hostname matches your EC2 Public IPv4 DNS
  4. Try accessing directly: http://<public-dns>:8000/OA_HTML/AppsLogin

AutoConfig fails during configwebentry.sh

  1. Ensure the database is running before running AutoConfig
  2. Verify the ORACLE_SID is entered in uppercase: EBSDB
  3. Enter apps as the APPS user password when prompted
  4. Review the AutoConfig log in /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/log/

Security Recommendations

  • Restrict port access: Only allow ports 22, 1521, 8000, 8001, 7001, and 7002 from trusted IP addresses
  • Change default passwords: Update the EBS application passwords and database passwords after initial setup
  • Use HTTPS: Configure SSL/TLS for the EBS web tier to encrypt traffic
  • Limit OS access: Restrict SSH access to authorised administrators only
  • Apply Critical Patch Updates: Keep the EBS stack up to date with the latest Oracle CPUs
  • Monitor access logs: Review WebLogic and EBS access logs regularly
  • Restrict WebLogic Console access: Limit ports 7001/7002 to administrators only
  • Back up regularly: Create EBS backups and database exports on a regular schedule

Support

If you encounter any issues with this product, contact cloudimg support:

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