This document describes you the deployment of the Oracle VM virtual appliances for Oracle E-Business Suite Release 12.2.4. These virtual appliances can be imported into Oracle VM Manager to deploy Oracle E-Business Suite Linux 64-bit environments on compatible server-class machines running Oracle VM Server. Alternatively, they can be imported into Oracle VM VirtualBox to create virtual machines.
The requirements listed below apply to the machine used to host the Oracle VM VirtualBox appliances used with Oracle E-Business Suite.
Host Computer: You need a physical host computer to install VirtualBox and deploy the Oracle E-Business Suite.
Host Operating System: The host operating system must be one that is supported to run VirtualBox.
CPU Capabilities: The processor must be a 64-bit processor with hardware virtualization capabilities.
RAM and Disk Space: Minimum of 6GB RAM and more than 60 GB Disk Space is required for hosting Oracle E-Business Suite Single Node Vision Appliance.
Download the oracle VM Appliances for Oracle E-Business Suite Release 12.2.4 from www.edelivery.com.
- Login to edevlivery.com and search for Oracle VM Virtual VM appliances for 12.2.4 and select platform.
- Select the Release and Click on continue.
- Download the Software files as per your requirement. Here we are explaining the procedure with Single Node Vision Appliance. So Need to download total 16 files for Single Node Vision Install.
- Download the assemble.zip, Attachment 1928303.1:2, to the machine where you placed the downloaded zip files. Unzip the assemble.zip file to retrieve assemble.sh.
- Execute assemble.sh script in the directory that contain the downloaded files to extract and assemble the appliance file.
- For Single Node Vision Install we get the appliance file as “Oracle-E-Business-Suite-12.2.4-VISION-INSTALL.ova”.
Importing the Individual VirtualBox Appliances using the VirtualBox Manager:
Perform the following tasks to import the Oracle E-Business suite VirtualBox appliances.
- Open Oracle VM VirtualBox Manager and select File > Import Appliance.
- The Import Virtual Appliance wizard will be displayed.
- Click the Choose icon and locate the *.ova file of the virtual machine to import. Click the Next button.
- The Appliance Settings dialog is displayed. Before importing the selected virtual machine, make proper adjustments to the display settings and click the Import button.
- The Import Virtual Appliance wizard is closed. After a few moments, the imported virtual machine is listed in the Oracle VM VirtualBox Manager.
- After the import, select the imported virtual machine and click the Settings icon from the toolbar. Review the virtual machine settings to make sure that the virtual machine has the required hardware resources as mentioned in order to operate.
- Start the virtual machine and log in as the root user enter the new configuration password for root.
- Change the passwords for default oracle user and applmgr user by answering the prompts to configure the virtual machine.
- Enter the default Hostname which EBS already configured as ebs.example.com when it prompted for Hostname. Later we can change hostname as per you requirement. Enter the IP address, Gateway, Subnet and DNS server details.
- Choose whether to configure the database tier processes to be managed on boot or just boot into the VM. Enter an appropriate response to the prompt or NONE to boot into the VM.
- Connect to oracle user and run the enviStart the Oracle E-Business Suite database tier processes using the scripts provided in /u01/install/VISION directory
Default Hostname on which the EBS pre-configured : ebs.example.com
Default user who owns the Database and Application : oracle
Default login credentials:
EBS URL : http://ebs.example.com:8000
DB Name : EBSDB
INSTANCE NAME : EBSDB
Username/Password : sysadmin/sysadmin
- The scripts to manage the Oracle E-Business Suite single node Vision installation are:
START SCRIPT FOR DB : /u01/install/VISION/scripts/startvisiondb.sh
STOP SCRIPT FOR DB : /u01/install/VISION/scripts/stopvisiondb.sh
START SCRIPT FOR APPS : /u01/install/VISION/scripts/startvisionapps.sh
STOP SCRIPT FOR APPS : /u01/install/VISION/scripts/stopvisionapps.sh
DB RE-CONFIG SCRIPT : /u01/install/VISION/scripts/visiondbconfig.sh
APPS RE-CONFIG SCRIPT : /u01/install/VISION/scripts/visionappsconfig.sh
DB CLEANUP SCRIPT : /u01/install/VISION/scripts/visiondbcleanup.sh
APPS CLEANUP SCRIPT : /u01/install/VISION/scripts/visionappscleanup.sh
CONFIGURE A NEW WEB ENTRY POINT : /u01/install/scripts/configwebentry.sh
- The scripts to reconfigure the network for the virtual machines are:
CONFIGURE DHCP : /u01/install/scripts/configdhcp.sh
CONFIGURE STATIC IP : /u01/install/scripts/configstatic.sh
SCRIPT TO CLEANUP VM : /u01/install/scripts/cleanup.sh
Procedure to change the host name of the virtual machine:
Changing the logical host name of the virtual machine is not mandatory for accessing Oracle E-Business Suite applications but you can change the hostname by using below steps.
- Start the virtual machine with the default ebs.example.com host name.
- Log in as the oracle user and Source the runtime environment file.
$ . /u01/install/VISION/EBSapps.env Run
- Execute the following command.
- Run adpreclone.pl appstier by using following command.
- Source the patch environment in the patch file system.
$ . /u01/install/VISION/EBSapps.env Patch
- Execute the following command.
$INST_TOP/admin/scripts/adadminsrvctl.sh start forcepatchfs
- Run adpreclone.pl scripts as below.
- Run the following command to stop the Oracle E-Business Suite application tier services.
- Stop the Oracle E-Business Suite database tier services.
- Execute either one of the following commands as the root user to configure hostname and IP’s.
- Reboot the virtual machine for the new host name to take effect. Ensure echo $HOSTNAME returns the new host name.
- Execute the following command as the root user to configure database .
- Execute the following command as the root user to configure application tier.
If the script returns an error while creating the patch file system, perform the following steps to re-create the patch file system.
1.Stop any processes that is running from the patch file system.
2.Source the run file system.
3.Execute the following command to create the patch file system.
adop phase=fs_clone force=yes
- Perform the following steps to ensure that you can run online patching cycles without any errors on the reconfigured environment:
1.Bring up processes from the run file system if they are down.
2.Execute two adop empty cycles using the following commands: