ODAVP: How to bring JDE Deployment Server on ODA Virtualized Platform

Asset ID:	1-71-1684316.1
Update Date:	2014-06-25
Keywords:

Solution Type Technical Instruction Sure

Solution 1684316.1 : ODAVP: How to bring JDE Deployment Server on ODA Virtualized Platform

Applies to:

Oracle Database Appliance Software - Version 2.8.0.0 and later
Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.

Goal

The Deployment Server for JD Edwards EnterpriseOne must reside on an Intel Pentium-based computer running Microsoft Windows. Optionally you can choose to install the Deployment Server into a virtual machine for Microsoft Windows. For non-production use with Oracle VM Templates, a Deployment Server is not required. You must have a Deployment Server in production environments or any environment in which you want to apply ESUs or perform Package Builds. The scope of this article is to explain how you could bring the Deployment Server on ODA VP (Oracle Database Appliance Virtualized Platform) keeping it running into a Guest Virtual Machine.

Solution

How to bring JDE Deployment Server on ODA Virtualized Platform

This article is discussing mainly two scenarios:

JDE Deployment Server to be installed on Ms Windows Guest VM created from an ISO image
JDE Deployment Server installed on Ms Windows Guest VM exported from VMWare vShere

In both cases the first step it's to crate a shared repository where the new Guest VM will be stored, you can issue the following command:

# oakcli create repo -h
Usage:
oakcli create repo <repo_name> -size <size> -dg <diskgroup>
where:
   repo                  - shared repo name
   -size                 - size of shared repo to be created
                           - Minimum Size : 500M or 1G
                           - Default unit is G
                           - size must be a whole number.
   -dg                   - Disk Group of shared repo
                           - [DATA | RECO]

example:
   oakcli create repo JDE_DEP -size 200 -dg DATA

The recommended size to store the Deployment Server for JD Edwards EnterpriseOne Guest VM should be at least 200Gb.

JDE Deployment Server to be installed on Ms Windows Guest VM created from an ISO image

1. Create a new Ms Windows Guest VM

Once the shared repo is available, you need to create a new Ms Windows Guest VM following the Document:1524138.1 - "ODAVP: How To Create a Fully-Virtualized Guests (HVM) from an OS ISO image"

2. Install the JDE Deployment Server

Having the new Ms Windows Guest VM up&running, you need to follow the steps reported on "Installing the Deployment Server" (JD Edwards EnterpriseOne Oracle VM Templates Express Installation Guide Tools)

JDE Deployment Server installed on Ms Windows Guest VM exported from VMWare vShere

1. Pre export steps

Uninstall vmware tools
Stop the VM
Make sure there are no snapshots on the vm

2. Export the JDE Deployment Server Guest from VMWAre vShere

Export the JDE Deployment Server Guest from VMWAre vShere using the Open Virtualization Format (OVF). Exporting as OVF a Ms Windows VM with one virtual disk, three files are created,
example:

MsWin2008.ovf           - VM configuration file
MsWin2008-disk1.vmdk    - VM virtual disk
MsWin2008.mf           - VM manifest file

You should review the manifest file (.mf) content verifying that is reporting the right entries:

$ cat MsWin2008.mf
SHA1(MsWin2008.ovf)= b10ad933062d36a435696be780be6288dc5f50f4
SHA1(MsWin2008-disk1.vmdk)= 3ddf3eec2e6af3d31e1c578d6af13c3f170a8c65

As reported on the manifest file above, you should have:
- one entry for the the .ovf file
- one entry for the virtual disk file MsWin2008-disk1.vmdk

If not expected entries are present, you should edit the manifest file making the correction. In the following example a wrong manifest file was created:

SHA1(Test1-disk1.vmdk.000000000)= ed63a930cbfc00ffac5b5614f12daf4d0b9b8b86
SHA1(Test1-disk1.vmdk)= ed63a930cbfc00ffac5b5614f12daf4d0b9b8b86

the right manifest file is

SHA1(Test1.ovf)= ed63a930cbfc00ffac5b5614f12daf4d0b9b8b86
SHA1(Test1-disk1.vmdk)= ed63a930cbfc00ffac5b5614f12daf4d0b9b8b86

Once the manifest file is fine you need to build the corresponding OVA file. You need to make a tar file where the VM configuration (.ovf) file is the first:

tar cvf MsWin2008.ova MsWin2008.ovf MsWin2008-disk1.vmdk MsWin2008.mf

3. Import the OVA VM template on ODA VP

You can now import the OVA created template from ODA_BASE into the shared repo issuing the following command

oakcli import vmtemplate <vmtemplatename> -assembly <image files> -repo <repo_name> [ -node <0|1> ]

example:
# oakcli import vmtemplate MsWin2008 -assembly /OVS/staging/MsWin2008.ova -repo JDE_DEP
# oakcli import vmtemplate MsWin2008 -assembly http://192.168.1.200:8000/MsWin2008.ova -repo JDE_DEP

Note:

see ODA documentation how Managing Virtual Machines on Oracle Database Appliance

TIP: If you have no proper http/server setup in the environment, the following single python command will start an HTTP server which will serve all files from the current directory and all subdirectories:

$ python -m SimpleHTTPServer 8000

4. Review the vm configuration file 'vm.cfg' (from ODA_BASE)

Once the template has been registered, review the VM configuration file (vm.cfg) stored under

/u01/app/sharedrepo/<repo name>/Templates/otml_<VM template name>/vm.cfg

ie:
/u01/app/sharedrepo/JDE_DEP/Templates/otml_MsWin2008/vm.cfg

# cat vm.cfg
vif = ['']
name = 'otml_MsWin2008'
builder = 'hvm'
vcpus = 2
memory = 4096
serial = 'pty'
disk = [u'file:/OVS/Repositories/odarepo1/Templates/otml_MsWin2008/6ee6ea13b3264f7a8e36ff5dfbd95015.img,xvda,w']
uuid = 'd001944ceebd42399a37a6bc140c309b'

- The option

vif = [''] should be changed to vif = [ 'type=ioemu,bridge=net1']

- You should add the entry

vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncunused=1' ]

The backend listens on IP 127.0.0.1 port 5900+N by default where N would be the domain ID. You can override both address and N (IP address 0.0.0.0 means dom0 IP)

vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncdisplay=10' ]

or bind the first unused port above 5900 (on dom0 ip address):

vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncunused=1' ]

or override the password

vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncpassword='MyPassword',vncunused=1' ]

5. Clone the new Guest

From ODA_BASE you can clone the new Guest VM issueing the following command:

oakcli clone vm <vm_name> -vm template-repo

# oakcli clone vm SRV-JDE_DEP -vmtemplate MsWin2008 -repo JDE_DEP

Cloned VM : SRV-JDE_DEP

Now you can manage/configure the new Guest VM from dom1 using oakcli (configure, show, start/stop)

# oakcli show vm SRV-JDE_DEP
....

# oakcli start vm SRV-JDE_DEP

Started VM : SRV-JDE_DEP

Note:

If the VMWare image you are using is a Windows OS and you got boot issue, this can likely be solved by disabling ACPI and the APIC in the guest.

acpi = 0
apic = 0

6. Download the PV drivers for windows and Install them

After the network has been configured for Windows VM, access the http://edelivery.oracle.com, down-load and install the Oracle PV drivers for Windows, you find them on:

Cloud Portal (Oracle Linux/VM)

Product Pack: Oracle VM
Platform X86 64bit
Oracle VM Media Pack should be the same version of the OVM running on ODA

Modify the VM configuration file and specify the netfront drivers
So far the “vm.cfg” file was configured to use the emulated drivers for Windows. Modify the vm.cfg configuration and vif option to use the netfront drivers instead of the ioemu drivers.

Make the following changes to the “vm.cfg” file:

vif = [ 'type=ioemu,bridge=net1']
To
vif = [ 'type=netfront,bridge=net1']

Make the network changes from ODA_Base (oakDom1) with the following “oakcli” command:

oakcli configure vm <vm_name> -network "['type=netfront,bridge=net1']"

ie:
# oakcli configure vm SRV-JDE_DEP -network "['type=netfront,bridge=net1']"

Restart the VM:

oakcli stop vm <vm_name> ; oakcli start <vm_name>

ie:
# oakcli stop vm SRV-JDE_DEP ; oakcli start SRV-JDE_DEP

Once the VM comes up, check the network settings and verify if the realtek driver is still enabled. If this is the case, disable the realtek driver and configure the Oracle VM PV driver, assign the correct IP address, netmask, gateway and the DNS information. At this stage of the installation and configuration, Windows VM is complete with a fully working copy of Windows.

ioemu vs netfront
If the virtual machine is a hardware virtualized machine (fully virtualized). You can configure the virtual interface (VIF) type to be either ioemu or netfront. The netfront driver is a paravirtualized driver which can be used with a Paravirtualized machine or with a hardware virtualized machine. The ioemu driver is a hardware virtualized driver and can only be used with a hardware virtualized machine. Both drivers contain the BIOS and device emulation code to support hardware virtualized machines. For hardware virtualized machines, the default is ioemu. For Paravirtualized machines, the default is netfront. After you configure the virtual interface type for one network interface card, i.e. all the network interface cards in the virtual machine will be set to the same type.

References

http://docs.oracle.com/cd/E24902_01/doc.91/e18836.pdf
<NOTE:1525105.1> - ODAVP: How to Manually Convert a VMware Guest Image for use with Oracle Database Appliance VP
http://docs.oracle.com/cd/E24902_01/doc.91/e54942.pdf
http://www.oracle.com/technetwork/database/database-appliance/oda-jde-soln-in-a-box-technical-2120907.pdf
<NOTE:1524138.1> - ODAVP: How To Create a Fully-Virtualized Guests (HVM) from an OS ISO image

Attachments

This solution has no attachment