SecureAnyCloud
Deployment guide

Oracle E-Business Suite 12.2.12 Vision on Oel7 Supported by Sac

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. The Vision instance includes sample data for demonstration and testing. This guide covers deploying and configuring Oracle EBS 12.2.12 Vision on Oracle Enterprise Linux 7 from the SecureAnyCloud AMI on AWS Marketplace.

What you get:

  • 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
  • An OS package update script that keeps 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 SecureAnyCloud support with guaranteed 24 hour response SLA

Prerequisites

Before you launch the AMI, make sure you have:

  • An active AWS account
  • An active subscription to the Oracle EBS 12.2.12 Vision listing on AWS Marketplace
  • An EC2 key pair for SSH access
  • Familiarity with EC2 instance management and SSH
  • An 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 of disk space. Oracle EBS needs significant resources to perform acceptably.

1

Launch the AMI

  • Go to AWS Marketplace and search for "Oracle E-Business Suite 12.2.12 Vision SecureAnyCloud".
  • Click Continue to Subscribe, accept the terms, then click Continue to Configuration.
  • Select your preferred Region and Software Version.
  • Click Continue to Launch.
  • Choose Launch through EC2 for full control over the instance configuration.
  • Select your instance type (t3.xlarge recommended, minimum 16 GB RAM).
  • Configure storage: 500 GB gp3 minimum.
  • Configure your Security Group with these inbound rules:
    • 22 (TCP), source your IP: SSH access
    • 1521 (TCP), source your IP: Oracle Database Listener port
    • 8000 (TCP), source your IP: EBS Administration Console, port pool 1
    • 8001 (TCP), source your IP: EBS Administration Console, port pool 2
    • 7001 (TCP), source your IP: WebLogic Console, port pool 1
    • 7002 (TCP), source your IP: WebLogic Console, port pool 2
  • Select your EC2 key pair and launch the instance.

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

2

Connect via SSH

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

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

To switch to the root user:

sudo su -

Important: Wait for the instance to reach 2/2 successful status checks before you connect. If you connect too early, you may see permission denied errors while the instance is still initializing.

3

Configure the Hosts File

As the root user, run the hosts configuration script. It sets the private IP address in /etc/hosts and configures the hostname. You only need to do this once:

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

When the script prompts 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
4

Start the Oracle Database

As the root user, start the Oracle Database and Listener services. Startup takes about 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.
5

Configure the Web Entry Point

Before you start 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 the script prompts you, enter these values. Adjust the hostname to match your EC2 instance Public IPv4 DNS.

  • 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 the default
  • APPS user password: apps

The script runs AutoConfig to update the context files. This takes about 10 minutes on a t3.xlarge instance.

Expected output ends with:

AutoConfig completed successfully.
6

Start the Oracle Apps Services

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

exit service apps start

Expected output shows several 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 you continue.

7

Access the EBS Console

When all services are running, open 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 with the credentials in the oracle-credentials file at /stage/scripts/oracle-credentials.

Server Components

The image includes these components:

  • 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

The image uses these mount points:

  • / (38 GB): root filesystem
  • /boot (2.0 GB): operating system kernel files
  • /u01 (393 GB): Oracle software installation directory (EBS, Database, WebLogic)

Key directories:

  • /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

Scripts and logs, with their locations:

  • 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 bring the image fully up to date. To disable it, remove 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. After each instance restart, start them manually with the commands in the Managing Services section.

Troubleshooting

You cannot connect over SSH

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

The database fails to start

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

The application services fail to start

  • Make sure the database is running first: service ebscdb start
  • Make sure you have configured the web entry point. If not, run configwebentry.sh.
  • Review the application logs at /u01/install/APPS/fs1/inst/apps/EBSDB_apps/logs/appl/admin/log/.
  • Verify that enough memory is available: free -m (16 GB minimum recommended)

You cannot reach the EBS console on port 8000

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

AutoConfig fails during configwebentry.sh

  • Make sure the database is running before you run AutoConfig.
  • Verify that you entered the ORACLE_SID in uppercase: EBSDB
  • When prompted, enter apps as the APPS user password.
  • Review the AutoConfig log in /u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/log/.

Security Recommendations

  • Restrict port access. Allow ports 22, 1521, 8000, 8001, 7001 and 7002 only from trusted IP addresses.
  • Change default passwords. Update the EBS application passwords and database passwords after the initial setup.
  • Use HTTPS. Configure SSL/TLS for the EBS web tier to encrypt traffic.
  • Limit OS access. Restrict SSH access to authorized 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 and 7002 to administrators only.
  • Back up regularly. Create EBS backups and database exports on a regular schedule.

Support

If you have any issues with this product, contact SecureAnyCloud support:

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

Deploy on AWS

Launch Oracle E-Business Suite 12.2.12 Vision on OEL7, supported by SecureAnyCloud, with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com