Você está na página 1de 41

Installing EBS R12.1.

3 using Oracle VM Template without VM Server & Manager (Part 1 of 4)


Lets start with installing EBS R12.13 instance using Oracle VM Template. Using the guided steps any
one will be able to have its own vision instance. The prerequisites will take most of your time (I
would say 80-90%), otherwise the installation will take just an hour or so. This is divided into 5
sections.

Section 1 Hardware and Software Pre-requisites

Section 2 Downloading software and making it available to


use

Section 3 Configuring Database Tier Template

Section 4 Configuring Application Tier Template

Section 5 Using Oracle Applications 12.1.3

Section 1 Hardware and Software Pre-requisites


Its a best to have two different machines to (one for database server and another for application
server), but spending on two physical machines is very costly and just to practice and use oracle
application I dont think any once is willing to pay much. So I thought of using virtualization and
used Virtual Box to install oracle application.
I have used my personal laptop to implement this guide and it works fine. My laptop runs on
Windows 7, I used virtual machines inside my Host OS to install EBS 12.1.3 visions instance. We can
use this guide even we have Host Operating System as Linux, just we need to install the Linux
version of Virtual Box / VM Ware.
Hardware Requirement
Recommended configuration
Processor Intel Dual Core / Core3Duo 2.5 Ghz
RAM

6 GB of RAM (we can live with 4 GB but


that will be too tight fit)

HDD
Network

500 GB of HDD (We need extra 300 GB of


HDD to convert VM template image to
Virtual Box readable format)
Network adapter

Used configuration
Processor Intel Core i5 2.5 Ghz
RAM
8 GB
500 GB internal HDD + 500 GB external
HDD
HDD
Network
Network adapter
Software Requirement
Virtualizatio
Oracle Virtual Box / VM Ware Player

n
Operating
System
EBS Software
Other
Software

Oracle Enterprise Linux Release5


Update6
R12.13 OVM Template
CygWin, Unzip Utility

Section 2 Downloading software and making it available to use


Downloading Software
Download the Oracle virtual machine template form Oracle Software delivery could
(https://edelivery.oracle.com/linux). Make sure to select Oracle Linux/VM from Cloud Portal LOV
on the right hand side.

Login to Oracle software delivery cloud Delivery portal using your credentials and search for Oracle
VM Template, select your platform. I opted for 64 bit as to extract maximum performance out of my
hardware.
a OVM Templates

From the list select Oracle VM Templates for Oracle E-Business Suite Release 12.1.3 Vision Media Pack
for x86 (64 bit) and download all the 11 files under it (V25323-01 to V25330-01 for database server
and V25331-01 - V25333-01 for application server).
b Oracle Linux Release5 Update6
Also down Oracle Oracle Linux Release 5 Update 6 Media Pack for x86_64 (64 bit) ISO disk from
oracle software cloud. We need this to first boot the virtual machine and configure the operating
system provided by oracle in template. We could have done with later releases but I dont want to
take a chance as OVM templates are built on Oracle Linux Release 5 Update 6.

c CygWin
Download and install Cygwin from internet (http://cygwin.com/install.html)
Extracting Template files
Unzip OVM Templates - Unzip all the 11 files we download. We can use any window tool like
winzip / winrar to perform this activity or we can down load CygWin to create unix like environment
under Windows and use unzip command to unzip the files. I have used CygWin to perform the
extraction.
Upon completion we will get two set of files (one for db template and one for apps template) like this

OVM_OL5U6_X86_64_EBIZ12.1.3_DB_VIS_PVM.tgz.0-7 (8 Files Database tier)


OVM_OL5U6_X86_64_EBIZ12.1.3_APPS_VIS_PVM.tgz.0-2 (3 Files Application tier
template)

Concatenate and decompress OVM Template files Once done the unzip we need to
concatenate the files which are in .tgz format along with decompressing it. Oracle splitted entire DB
and APPS image into smaller chunks and compressed it. I browsed to the directory where files were
place or you can provide the path as well.

[root@ultimatix]# cat OVM_EL5U3_X86_64_EBIZ12.1.1_APPS_VIS_PVM.tgz.0 \


OVM_EL5U3_X86_64_EBIZ12.1.1_APPS_VIS_PVM.tgz.1 \
OVM_EL5U3_X86_64_EBIZ12.1.1_APPS_VIS_PVM.tgz.2 | tar xz

[root@ultimatix]# cat OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.0 \


OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.1 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.2 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.3 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.4 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.5 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.6 \
OVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM.tgz.7 | tar -xz

This will create 2 directoriesOVM_EL5U3_X86_64_EBIZ12.1.1_DB_VIS_PVM (2 Image files, 1 config file and 1 readme file)
OVM_EL5U3_X86_64_EBIZ12.1.1_APPS_VIS_PVM (2 Image files, 1 config file and 1 readme file)
Convert the disk to Virtual Machine readable format To use the .img files that we got after
concatenating and decompressing we need to convert them into some readable format that can be
read by Virtual machines. The native file format of Virtual Box is .vdi but I opted to convert the files
into .vmdk (VM Ware native format) since Virtual Box supports .vmdk files and if I wish I can use it
in VM Ware as well.
Before proceeding with guide please follow the below link to understand how to download and install
Oracle Virtual Box
Installing Virtual Box and Creating Virtual Machines
Virtual Box provides a utility called VBoxManage that will be used to convert the file format. We
can find the utility inside the installation folder where Virtual Box is installed. To make use of it
either we can browse inside the directory or we can add the path into environment variables. To do
this goto -> System Properties

Click on Environment Variables to update the path:

Select the Path and click on Edit

Add the directory path of Virtual Box installation where VBOXManage.exe is located

Now covert the .img files to .vmdk files. While converting I have changed the names of the files so
that I can easily identify it.
Apps Server Files
=================
VBoxManage.exe convertfromraw g:\OracleVM\Apps-VM\ebs1211apps.img
d:\OracleVM\Apps-VM\EBIZ12.1.3_APPS_VIS\ebs1213apps.vmdk
VBoxManage.exe convertfromraw g:\OracleVM\Apps-VM\System.img d:\OracleVM\AppsVM\EBIZ12.1.3_APPS_VIS\ebs1213appsroot.vmdk
DB Server Files
===============
VBoxManage.exe convertfromraw g:\OracleVM\DB-VM\ebs1211db.img d:\OracleVM\DBVM\EBIZ12.1.3_DB_VIS\ebs1213db.vmdk
VBoxManage.exe convertfromraw g:\OracleVM\DB-VM\System.img d:\OracleVM\DBVM\EBIZ12.1.3_DB_VIS\ebs1213dbroot.vmdk

*** Above steps are performed on Windows system, you can find equivalent command for other
Operating System if your HOST Operating System is different.
Please follow the below link to understand how to Create Virtual Machine in Virtual Box
Creating Virtual Machine in Oracle Virtual Box {{{{PROVIDE LINK for Blog - }}}}
Configuration for Virtual Machines
Database Server
Application Server
Processor/CPU
1 Processor/CPU
1
RAM
3 GB
RAM
1.5 GB
Operating
Operating
System
Oracle Linux 64bit
System
Oracle Linux 64bit
Boot Order
CD-ROM, Hard Disk
Boot Order
CD-ROM, Hard Disk
Oracle Linux R5U6 ISO, IDE
Oracle Linux R5U6 ISO,
Controller to attached two
IDE Controller to attached
Storage
.vmdk files
Storage
two .vmdk files
1-Host-Only Adapter, 1-NAT
1-Host-Only Adapter, 1Network
Adapter
Network
NAT Adapter
Data Base Server & Application Server Virtual Machine Final Configuration

Once we done with creating pre-requisites and virtual machine creation now we will move to next
section.
Next -: Section 3 Configuring Database Tier Template
Posted 22nd January by Tauseef E. Ahmad
Labels: Apps Installation VM Template Oracle Applications EBS Installation

Installing EBS R12.1.3 using Oracle VM Template without VM Server & Manager (Part 2 of 4)
Section
3

Configuring
Database
Tier
Template
Booting Linux in Rescue Mode Start the Virtual Machine created for Database Server. Make
sure the Linux bootable disk are inserted into CD-ROM / ISO Image and its supposed to boot from
CD-ROM.
Enter Linux Rescue at the prompt and enter to boot linux in rescue mode.

Choose the language and Keyboard layout

Configure both the network interfaces (eth0 and eth1). Right now we can just make it to use the IP
address from DHCP, that will do the job. If you are confident enough your manual configuration will
work and accessible from HOST along with Guest able to access the internet.

Just enable IPv4 support, that will do the job.

Used DHCP to obtain IP information.

Now we are done with configuring the first network adapter (i.e Host-Only adapter used to connect
the Guest Machine from HOST). Same we did we have to configure the second network adapter (i.e
NAT adapter it will be used to connect to the internet to download and update kernel files). Same
can be achieved by browsing the files from installation media.
Now click on Continue and make a note of the mount point where system has been mounted. We
need to access that to make the system work.

Click OK to return to shell prompt. As instructed in the above screen shot please go to root
environment by running command: chroot /mnt/sysimage
To proceed further we have two ways to accessing the virtual machine:

# service sshd start

Access from VM Console

Access from HOST system. To use this we need to enable


sshd services in VM console before it can be used. Use
command:

Before we proceed further and if you are planning to use the guest OS from HOST via SSH then
please first check the IP of guest and OS and make sure its getting pinged from HOST OS
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 08:00:27:88:88:C4
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0

C:\>ping 192.168.1.4
Pinging 192.168.1.4 with 32 bytes of data:
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Update the configuration files

The kernels that are loaded while we booted the system in rescue mode supports Xen Kernel, where
as our target kernel will going to support that. To make it work we need to modify modprobe.conf
and install new kernel.
Before modifying the modprobe.conf its better to make a copy of it, so if something goes wrong we
can recover that.
[root@localhost ~]# cp /etc/modprobe.conf /etc/modprobe.conf.xen
[root@localhost ~]# cat /etc/modprobe.conf
alias eth0 xennet
alias scsi_hostadapter xenblk

[root@localhost ~]# vi /etc/modprobe.conf


alias eth0 e1000
alias scsi_hostadapter ata_piix
alias scsi_hostadapter1 ahci
~

[root@localhost ~]# diff /etc/modprobe.conf /etc/modprobe.conf.xen


1,9c1,2
< alias eth0 e1000
< alias scsi_hostadapter ata_piix
< alias scsi_hostadapter1 ahci
--> alias eth0 xennet
> alias scsi_hostadapter xenblk
[root@localhost ~]#

The data base disk images that we have added are mounted on mount point /u01. Please edit
/etc/fstab so that fsck will not check to check and repair file system. Since the size of disk is large it
better to skip the fsck test for /u01. Make sure /u01 looks like as image below
[root@localhost ~]# vi /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-VM swap swap defaults 0 0
LABEL=ebs1211db /u01 ext3 defaults 1 0
[root@localhost ~]#

Update the /etc/sysconfig/oraclevm-template to disable automatic template configuration at boot


time. Before running the configuration we need to make sure every thing is fine and we can proceed
with template configuration. If we dont disable then we may have to run through the same process
again after boot. We could have directly updated the file, but I though its better not to delete content
of the file where as just disable it and add a new entry as we needed.
[root@localhost ~]#vi /etc/sysconfig/oraclevm-template
# Template configuration
#
# Allow configuration of the template when the service is enabled
#
#RUN_TEMPLATE_CONF=YES
RUN_TEMPLATE_CONF=NO
~

[root@localhost ~]# grep RUN /etc/sysconfig/oraclevm-template


#RUN_TEMPLATE_CONF=YES
RUN_TEMPLATE_CONF=NO
[root@localhost ~]#

Installing a new Kernel The kernel that were loaded while booting (Xen) is not going to work
with OVM template, to make it work we need to replace it with standard kernel of same version. We
could have used the ISO CD-ROM that we used to boot in rescue mode to install standard kernel or
we can get it from the internet. I preferred to go over internet (Oracle Public Yum Server) to get the
Kernel. That would defilnalty need an internet connection and the NAT adapter will do the job for us.
[root@localhost ~]# cd /etc/yum.repos.d
[root@localhost]# wget http://public-yum.oracle.com/public-yum-el5.repo
--2013-01-18 05:15:08-- http://public-yum.oracle.com/public-yum-el5.repo
Resolving public-yum.oracle.com... 141.146.44.34
Connecting to public-yum.oracle.com|141.146.44.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4220 (4.1K) [text/plain]
Saving to: `public-yum-el5.repo'
100%[======================================>] 4,220 --.-K/s in 0s
2013-01-18 05:15:11 (71.9 MB/s) - `public-yum-el5.repo' saved [4220/4220]
[root@localhost]#

Update the yum repo file and make sure to set enabled=1 only for [ol5_u6_base]
[root@localhost]# vi public-yum-el5.repo

Validate if changes are correctly set


[root@localhost]# grep B5 enabled=1 public-yum-el5.repo

Now install Kernel OL5U6 (2.6.18-238) from Oracle public yum server.
[root@localhost]# yum install kernel-2.6.18-238.el5
Press Y to download and install the kernel.

Also install screen if its not available. For me its not there so I installed it. This will be use full to
create saved ssh sessions.
[root@localhost]# yum install screen

Upon completion create initrd for the new kernel.


[root@localhost]# mkinitrd -v -f /boot/initrd-2.6.18-238.el5.img 2.6.18238.el5

Now rescue tasks are done. We need to restart the system now.
Reboot the Virtual Machine
- Remove the disk from CD-ROM or change the boot order from Virtual Machine boot setting.
- Start Virtual Machine and login with root user. The default root user password is ovsroot as given in
the read me file.
- The SSH services would be starting automatically this time so no need to start SSH services manually.

Configure Oracle VM Database Server


The image file provided by Oracle already has template configuration script that runs and configure
the database server as per our specs. In step it configures network adapters, directory paths,
hostnames etc. While we started the system in rescue mode we disabled the script. Now first enable
the script and run it.
Enable OracleVM Template script
[root@localhost ~]# vi /etc/sysconfig/oraclevm-template
# Template configuration
#
# Allow configuration of the template when the service is enabled
#
RUN_TEMPLATE_CONF=YES
#RUN_TEMPLATE_CONF=NO
~

[root@localhost ~]# grep RUN /etc/sysconfig/oraclevm-template


RUN_TEMPLATE_CONF=YES
#RUN_TEMPLATE_CONF=NO
[root@localhost ~]#

After enabling the script we will execute it. Since we configured our network adapters use DHCP,
while configuration we it requires to be changed to a static IP address. The script will automatically
ask you about the details to configure the database server. Make sure to assign an IP address that is
accessible in your network and by HOST. Also while the network adapters are configured system will
restart the network adapters, So if you are connecting via SSH tools (like Putty) then you will get
disconnected from Guest OS. That is the reason we installed Screen so that we can recover the
session and continue configuration. Its advisable to use Guest console for configuration. I have used
Putty, So have saved a session using screen.
[root@localhost ~]# screen S ebsdb

Now start the OracleVM-Template script


[root@localhost ~]# /etc/init.d/oraclevm-template start

It will ask for static IP address that we want to assign to our Oracle EBS database server. Provide
NetMask and Gateway and DNS server as specified in the screenshot above. Once you specified the
DNS and press enter the screen stops at this point (because I am using Putty). The network adapter
are getting restarted and assigned with new IP address. After few seconds start a new session with
new IP address that you assigned and proceed. Just invoke the saved SSH session.

Now we can see the same session. Please proceed further by providing requested details

Enter valid domain name for database server anything (host.domain.com). After that it will show
network summary and ask APPS password to continue (APPS password is apps for this instance).

There after the script will and configure your vision instance database server.

Now database server configuration is completed. If you check the OracleVM-Template file
(/etc/sysconfig/oraclevm-template) you will see the RUN_TEMPLATE_CONF =NO.
DO NOT SHUTDOWN DB SERVER WHILE WE CONFIGURE APPS SERVER.
Lets proceed to next section where we will be configuring Application Tier Server.
Next-: Section 4 Configuring Application Tier Template
Previous-: Section 1 & 2
Posted 22nd January by Tauseef E. Ahmad
Labels: Apps Installation VM Template Oracle Applications EBS Installation
Installing EBS R12.1.3 using Oracle VM Template without VM Server & Manager (Part 3 of 4)
Section 4 Configuring Application Tier Template
We need to perform the exact same steps as we did for Database template configuration with few
additional steps. Below screen shot just summarizes what all need to be done before we checkout the
additional steps involved. If you want details of each one then please follow the details below
otherwise skip the duplicate steps and check only additional steps

Booting Linux in Rescue Mode Start the Virtual Machine created for Application Server. Make
sure the Linux bootable disk are inserted into CDROM / ISO Image and its supposed to boot from
CD-ROM.
Enter Linux Rescue at the prompt and enter to boot linux in rescue mode.

Choose the language and Keyboard layout

Configure both the network interfaces (eth0 and eth1). Right now we can just make it to use the IP
address from DHCP, that will do the job. If you are confident enough your manual configuration will
work and accessible from HOST along with Guest able to access the internet.

Just enable IPv4 support, that will do the job.

Used DHCP to obtain IP information.

Now we are done with configuring the first network adapter (i.e Host-Only adapter used to connect
the Guest Machine from HOST). Same we did we have to configure the second network adapter (i.e
NAT adapter it will be used to connect to the internet to download and update kernel files). Same
can be achieved by browsing the files from installation media.
Now click on Continue and make a note of the mount point where system has been mounted. We
need to access that to make the system work.

Click OK to return to shell prompt. As instructed in the above screen shot please go to root
environment by running command: chroot /mnt/sysimage
To proceed further we have two ways to accessing the virtual machine:

Use command:
# service sshd start

Access from VM Console

Access from HOST system. To use this we need to enable


sshd services in VM console before it can be used.

Update the configuration files


The kernels that are loaded while we booted the system in rescue mode supports Xen Kernel, where
as our target kernel will going to support that. To make it work we need to modify modprobe.conf
and install new kernel.
Before modifying the modprobe.conf its better to make a copy of it, so if something goes wrong we
can recover that.
[root@localhost ~]# cp /etc/modprobe.conf /etc/modprobe.conf.xen
[root@localhost ~]# cat /etc/modprobe.conf
alias eth0 xennet
alias scsi_hostadapter xenblk

[root@localhost ~]# vi /etc/modprobe.conf


alias eth0 e1000
alias scsi_hostadapter ata_piix
alias scsi_hostadapter1 ahci
~

[root@localhost ~]# diff /etc/modprobe.conf /etc/modprobe.conf.xen


1,9c1,2
< alias eth0 e1000
< alias scsi_hostadapter ata_piix
< alias scsi_hostadapter1 ahci

--> alias eth0 xennet


> alias scsi_hostadapter xenblk
[root@localhost ~]#

[root@localhost ~]# vi /etc/fstab


LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-VM swap swap defaults 0 0
LABEL=ebs1211db /u01 ext3 defaults 1 0
[root@localhost ~]#

Update the /etc/sysconfig/oraclevm-template to disable automatic template configuration at boot


time. Before running the configuration we need to make sure every thing is fine and we can proceed
with template configuration. If we dont disable then we may have to run through the same process
again after boot. We could have directly updated the file, but I though its better not to delete content
of the file where as just disable it and add a new entry as we needed.
[root@localhost ~]#vi /etc/sysconfig/oraclevm-template
# Template configuration
#
# Allow configuration of the template when the service is enabled
#
#RUN_TEMPLATE_CONF=YES
RUN_TEMPLATE_CONF=NO
~
[root@localhost ~]# grep RUN /etc/sysconfig/oraclevm-template
#RUN_TEMPLATE_CONF=YES
RUN_TEMPLATE_CONF=NO
[root@localhost ~]#

Installing a new Kernel The kernel that were loaded while booting (Xen) is not going to work
with OVM template, to make it work we need to replace it with standard kernel of same version. We
could have used the ISO CD-ROM that we used to boot in rescue mode to install standard kernel or
we can get it from the internet. I preferred to go over internet (Oracle Public Yum Server) to get the
Kernel. That would definitely need an internet connection and the NAT adapter will do the job for us.

Before we install new kernel we need to perform Additional steps. We would like to use our DB
server as server to get the updates, otherwise we can connect to internet from application server
system and update the kernel. Please perform below steps
[root@localhost]# echo "nameserver 8.8.8.8" > /etc/resolv.conf
[root@localhost]# cat /etc/resolv.conf
nameserver 8.8.8.8
[root@localhost]# nslookup public-yum.oracle.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
public-yum.oracle.com canonical name = bigip-public-yum.oracle.com.
Name: bigip-public-yum.oracle.com
Address: 141.146.44.34

[root@localhost]# cat /etc/yum.repos.d

Open the repo file and make sure [ol5_u6_base] is enabled


[root@localhost]# vi public-yum-el5.repo
[root@localhost]# grep -B5 'enabled=1' public-yum-el5.repo | grep ']'
[ol5_u6_base]

Now install Kernel OL5U6 (2.6.18-238) from Oracle public yum server.
[root@localhost]# yum install kernel-2.6.18-238.el5
Press Y to download and install the kernel.

Also install screen if its not available. For me its not there so I installed it. This will be use full to
create saved ssh sessions.
Upon completion create initrd for the new kernel.
[root@localhost]# mkinitrd -v -f /boot/initrd-2.6.18-238.el5.img 2.6.18238.el5

Install Screen as we did in database server

[root@localhost ~]# yum install screen

Now rescue taks are done. We need to restart the system now.
Reboot the Virtual Machine

Remove the disk from CD-ROM or change the boot order


from Virtual Machine boot setting.

Start Virtual Machine and login with root user. The default
root user password is ovsroot as given in the read me file.

The SSH services would be starting automatically this time


so no need to start SSH services manually.

Configure Oracle VM Application Tier Server


First we need to enable the OracleVM Template as we disabled it while started the system in rescue
mode.
[root@localhost ~]# vi /etc/sysconfig/oraclevm-template
# Template configuration
#
# Allow configuration of the template when the service is enabled
#
RUN_TEMPLATE_CONF=YES
#RUN_TEMPLATE_CONF=NO
~

Start the OracleVM-Template configuration script


[root@localhost ~]# screen S ebsapp
Now start the OracleVM-Template script
[root@localhost ~]# /etc/init.d/oraclevm-template start

Same as DB server configuration after entering DNS details system will reconfigure network adapter
and your current session is gone. After few seconds start a new session with the new IP address we
assigned and pull the stored seesion that we created using screen.
[root@localhost ~]# screen d -R ebsapp

You session will be recovered, Now we need to enter APPS password to continue (ie. apps). But
before proceeding further we need to perform some of the additional steps.
Update the host file in application tier server: Start a new session and perform below steps
[root@localhost ~]# vi /etc/hosts

[root@localhost ~]# cat /etc/hosts

Ping the DB host from application and make sure its responding

Once done please go back to old session and enter the APPS password (apps) to continue.

Now script will start all the services related to Application Tier.

Now we are done with the installation. Lets see how to use it in our next and last
section
Next-: Section 5 Using Oracle Applications
Previous-: Section 3 Configuring Database Tier Template
Posted 22nd January by Tauseef E. Ahmad
Labels: Apps Installation VM Template Oracle Applications EBS Installation

Installing EBS R12.1.3 using Oracle VM Template without VM Server & Manager (Part 4 of 4)
Section 5 Using Oracle Applications 12.1.3

Now every ting is done and we are ready feel the first glimpse of Oracle EBS 12.1.3 on our own
machine.

First update the HOST on system from where we want to access the application. For me, I am using
the same laptop where I installed Oracle EBS12.1.3. So I will update the hosts file on HOST system.

You can fine the hosts file under %system32%/drivers/etc/hosts

Your login URL would be http://hostname.domainname.com:80NN (where NN is the port we have


given while configuration). For me its 'http://ebsapp.apps.com:8002'

ON the login screen login with generic login details


Operations / welcome
Sysadmin / sysadmin

Maintaining your instance:


< !--[if !supportLists]-->- <!--[endif]-->Every time you need to switch off your system please follow the
below steps.
< !--[if !supportLists]-->o <!--[endif]-->Stop the application tier services.
Oracle has provided prebuilt script when ran with oracle user starts / stops the application tier
service.
Login with oracle user (oracle / oracle) and run the script
[oracle@ebsapp]# . /u01/stopapps.sh

< !--[if !supportLists]-->o <!--[endif]-->Shut down the application tier server


[root@ebsapp]# shutdown h now

< !--[if !supportLists]-->o <!--[endif]-->Stop the database tier services


Same as application tier run the start/stop script on database tier server to stop the data base
services
Login with oracle user (oracle / oracle) and run the script

[oracle@ebsdb]# . /u01/stopapps.sh

< !--[if !supportLists]-->o <!--[endif]-->Shut down the database tier server


[root@ebsdb]# shutdown h now

< !--[if !supportLists]-->- <!--[endif]-->The first time we start the database / application tier server, the
oracle user account has configured to ask for password change. Its a good idea to change the default
password.

If you dont want to change the default password then enter NO at every prompt and run the below
command at both the servers.

[root@ebsdb]# touch /home/oracle/.passchanged


[root@ebsapps]# touch /home/oracle/.passchanged

< !--[if !supportLists]-->- <!--[endif]-->When you try to start the Application service for the first time
you will see errors like below

The issue comes because there are two .env files under /u01/E-BIZ/inst/apps/

Either rename the file OR A better way is to add following entry to your . bash_profile

App Server: APPSVIS_ebsapp.env


[oracle@ebsapps]# echo ". /u01/E-BIZ/apps/apps_st/appl/APPSVIS_ebsapp-s.env"
>> ~/.bash_profile

DB Server: VIS_ebsapp.env
[oracle@ebsdb]# echo ". /u01/E-BIZ/db/tech_st/11.2.0.2/VIS_ebsdb-s.env" >>
~/.bash_profile

Note Replace ebsdb/ebsapps with your respective hostname.

Previous-: Section 4 Configuring Application Tier Template


Posted 22nd January by Tauseef E. Ahmad

Labels: Apps Installation VM Template Oracle Applications EBS Installation