ODAVP: How to get the "ready-to-use" Templates 9.1.4.4 to deploy JDE

Asset ID:	1-71-1902042.1
Update Date:	2017-05-30
Keywords:

Solution Type Technical Instruction Sure

Solution 1902042.1 : ODAVP: How to get the "ready-to-use" Templates 9.1.4.4 to deploy JDE

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 to 9.1 [Release 9.1]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance Software - Version 2.8.0.0 to 2.10.0.0
Information in this document applies to any platform.

Goal

The "Solution-in-a-box: Best practices for deploying JD Edwards EnterpriseOne on Oracle Database Appliance" whitepaper (March 2014 edition) is describing how to deploy JDE on ODA using (from edelivery):

Description	Release	Part Number	Update
Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.3.3 (6.0.0)	6.0.0.0.0	B74855-01	OCT-21-2013

Since June 2014 new JDE templates are available as part of

Description	Release	Part Number	Update
Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 (7.0.0)	7.0.0.0.0	B77598-01	JUN-04-2014

Thess new templates has been built in different way. This article will describe the new steps to get the "ready-to-use" templates.

Solution

How to get the ready to use Templates to deploy JDE

You can obtain the download files for the Oracle VM Templates for JD Edwards from the Oracle Software Cloud (https://edelivery.oracle.com). The following table lists all required download files for Oracle VM Templates for JD Edwards EnterpriseOne (7.0.0.0.0):

JDE Template Description	Part Number	Size (Bytes)
Oracle VM Templates for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - Configuration Utility and Manifest	V43875-01	14K
Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 Enterprise Server 1 of 2	V43852-01	1.8G
Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 Enterprise Server 2 of 2	V43853-01	1.5G
Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and Tools 9.1.4.4 - HTML Server (WebLogic Server 12.1.2.0)	V43854-01	1.7G
Oracle VM Template for JD Edwards EnterpriseOne 9.1.2 and tools 9.1.4.4 - Oracle Linux 5.8 System	V43861-01	398M

Working with JD Edwards OVM Tools (config.sh Configuration Script)

The 7.0.0.0.0 release of Oracle VM Templates for JD Edwards EnterpriseOne includes a set of tools to help with the configuration of the VM images in zip files that you downloaded as listed in the preceding section

1. Installing the JD Edwards OVM Tools

The JD Edwards OVM tools (called JDE_OVM) are included in the V43875-01.zip file. You should place this zip file on a work linux machine (you could use /cloudfs on ODA_BASE) with adequate disk space for this zip and the total of each image you intend to install. In order to use the JDE_OVM tools, you must have these packages installed:

dialog-1.0.20051107-1.2.2

You can get it from:

http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/getPackage/dialog-1.0.20051107-1.2.2.x86_64.rpm

and you can install it issuing the following command:

rpm -ivh dialog-1.0.20051107-1.2.2.x86_64.rpm

On a work machine on which you intend to install the JD Edwards OVM Tools and VM images:

1. Create a directory into which you will place the V43875-01.zip file which contains the JD Edwards OVM Tools. For example:

mkdir -p /cloudfs/OVS/configTest

Note: you need at least 150Gb of free filesystem space

2. Place the downloaded V43875-01-01.zip into the directory you created in the previous step.
3. Unzip the file using this command:

unzip V43875-01.zip

The unzip action should have created a directory named JDE_OVM.
4. Change directory to JDE_OVM, which should have been created in the previous step.

cd JDE_OVM

This directory should contain the following extracted files:
   ■ config.sh
   ■ Help.doc
   ■ jdedwards.conf
   ■ OVM7.mft
   ■ setup.sh

2. Creating the Directory Structure for the Oracle VM Templates for JD Edwards EnterpriseOne

You will run the setup.sh script to create an empty but complete directory structure that supports all the VM templates supported by the current release. As it executes the script reads the manifest file (*.mft) for the current release and informs you which Oracle eDelivery part number files go into each directory. This helps you to obtain the required image files for your implementation and place them in the appropriate directory so that can be further configured and deployed by the JDE_OVM tools. To create the directories for the Oracle VM Templates for JD Edwards EnterpriseOne, run this script:

setup.sh

This script creates directories for all the Oracle VM templates for JD Edwards EnterpriseOne, as shown in the right-most field in this example:

$ ls -l /cloudfs/OVS/configTest
total 68
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_AIS
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_BIP
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_DB
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_ENT
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_EXA
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_MBL
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_OVM
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_SM
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_SYS
drwxr-xr-x 2 oracle oinstall 4096 Jun 27 03:11 JDE_WEB
-rw-r--r-- 1 oracle oinstall 15034 Jun 27 03:10 V43875-01.zip

Although the setup.sh creates the complete directory structure (which is empty at this point), you only need to download and configure the templates that you intend to use in your installation. You should not delete the template directories that are created by the setup.sh script. These directories are shown in the graphic above and listed alphabetically here as well:
   ■ JDE_AIS
   ■ JDE_BIP
   ■ JDE_DB

As you are running on ODA, the database is a non-virtualized database, then you must delete the JDE_DB directory:

rm -fr /cloudfs/OVS/configTest/JDE_DB

the remaining folder are the following:
   ■ JDE_ENT
   ■ JDE_EXA
   ■ JDE_MBL
   ■ JDE_OVM
   ■ JDE_SM
   ■ JDE_SYS
   ■ JDE_WEB

This note is covering the scenario for which we are using the base JDE Templates only: JDE_ENT, JDE_SYS, JDE_WEB.

You should move the edelivery templates files into the right location:

- For JDE_ENT (into /cloudfs/OVS/configTest/JDE_ENT):

V43852-01.zip
V43853-01.zip

- For JDE_SYS (into /cloudfs/OVS/configTest/JDE_SYS):

V43861-01.zip

- For JDE_WEB (into /cloudfs/OVS/configTest/JDE_WEB):

V43854-01.zip

-->

3. Working with with the Configuration Script

You can use the config.sh configuration script to perform these functions:

Verify the correct files exist in the correct locations
Extract and merge multi-part files
Copy system images
Prompt for input of server names and IP address
Configure and pair the System and Application images

Run the config.sh script with the "-nodep" startup parameter:

# cd /cloudfs/OVS/configTest/JDE_OVM/
# ./config.sh -nodep

a. Manifest Check

The first function of config.sh is the Manifest Check, which first checks the contents of the OMV7.mft file. Next it checks for the existence of the required of the directory structure that was created when you ran the setup.sh script. Below is an example of a successful Manifest Check.

Note: The preceding example of Manifest Check shows the directory structure with a path containing /OVS/configTest. This is a variable value that depends on the structure you have defined for your installation.

The preceding screen example shows the Manifest Check process has completed successfully. You can determine that the entire process completed successfully when you see the Manifest:1 Done message at the bottom of the screen. Press the Enter key to continue with script processing.

Note:

if using Putty the dialog is not showing nice graphics but instead various ASCII special characters like in the following example:

Putty

you need to change Putty settings. When you launch PuTTY you're presented a dialogue. In that dialogue, if you choose the Window/Translation tab, you'll the able to choose the character encoding you could try in example: ISO-8859-1:1998 (Latin-1, West Europe)

b. Extract and Merge

After the Manifest Check, the config.sh script continues with the Extract and Merge functions. The following screen shows the starting of the Extract All function.

When the process is complete as indicated by the Extract All: Done message, press the Enter key to proceed to the next step in the configuration script process.

After the Extract and Merge completes, the config.sh script continues with the System Copy functions.

The above screen shot shows the start of the process to copy a system image file that is to be paired with each JD Edwards EnterpriseOne application image. In this example, the config.sh script previously determined that the only System image was for an x86 type system; therefore this is the image that it is copied. When the config.sh script displays the message Copy System: 0 Done, press the Enter key to continue.

c. Server Configuration

After the Copy System completes, the config.sh script continues with the Server Configuration functions, which include:

Server Name
IP Address
Additional Server Configuration

On JDEdwards EnterpriseOne, Server(s) To Be Configured, at a minimum, you must choose to configure Line Item 1, which is a combination servers called the Foundation Server. This combined server group includes the JD Edwards EnterpriseOne servers for the Database, Enterprise Server, and HTML Server. This is the minimum viable combination of servers for JD Edwards EnterpriseOne using Oracle VM Templates. The other line items in this list are for optional JD Edwards EnterpriseOne servers.

For this setup, you to will need to provide this information for each server in the Foundation System:

Server Name
Server IP Address
Starting Memory Size (in Megabytes)
Number of CPUs Allocated to the Server
Database Server Name
Net Mask, Gateway, Domain, and one DNS Server

Note as

Location of Database System Image: NULL
Virtual Database Machine Name : <empty>
Database 'root' account pasword : NULL
Memory Allocation for Database VM: N/A
# of Virtual CPU's for Database VM: N/A

this because the JDE database will be run from ODA_BASE and not in a Virtual Database Machine.

Use the Up Arrow and Down Arrow keys to highlight a row for which you want to enter a value. When you reach the bottom of the screen it will automatically scroll to show remaining Line Items. Once you have entered all required values, press the Enter key to proceed.

Note:
The entered values will be edited for syntax only. This mean if you enter a valid length server name but misspelled it, the value will still be accepted. At this point in the process the server name is not checked against a DNS server. The same is true of the IP address.

1. Set the JDE Database & JDE Enterprise VM info

- Virtual Database Machine Name --> this is the database SCAN (Single Client Acces Network) name

you can get the SCAN name from ODA_BASE as grid user issuing the following command

srvctl config scan

Example:
$ srvctl config scan
SCAN name: oda1-scan, Network: 1/10.214.120.0/255.255.252.0/eth1
SCAN VIP name: scan1, IP: /oda1-scan/10.214.121.224
SCAN VIP name: scan2, IP: /oda1-scan/10.214.121.223

- Database Server IP                    --> this is the database SCAN (Single Client Acces Network) IP (at the present we can use only one SCAN IP. This issue will be fixed on the next release)
- Database Service name                 --> this must be 'ovsorcl'
- Virtual Enterprise Machine Name       --> this will be the VM name but is used also as VM hostname
- Enterprise 'root' account password    --> this is the root OS account for the JDE Enterprise VM

2. Set JDE Enterprise VM & JDE web tier VM info

9_2

- Enterprise Server IP Address          --> JDE ENT vm ip address
- Memory Allocation for Enterprise VM   --> 12288
   The Memory allocation shown in this example is specified as 12288, which is measured in M bytes (therefore equals 12 GB).
- # of Virtual CPU's for Enterprise VM --> this is the VCPU number given to the JDE ENT VM
- Virtual HTML Machine Name           --> this will be the HTML VM name but is used also as VM hostname
- Memory Allocation for HTML VM         --> 8192
   The Memory allocation shown in this example is specified as 8192, which is measured in M bytes (therefore equals 8 GB).
- # of Virtual CPU's for HTML VM        --> this is the VCPU number given to the JDE HTML VM

3. Set the JDE Deployment Server & Netmask, Gateway, DNS info

10_4

- Deployment Server Name       --> this is the JDE Deployment Server hostname
- Deployment Server Location    --> Deployment Server Location (Note: blank char are not permitted at this time)
- Network Mask                  --> this is the netmask used by the JDE VM ENT/HTML
- Network Gateway               --> this is the gateway ip used by the JDE VM ENT/HTML
- Network Domain Name           --> this is the domain name used by the JDE VM ENT/HTML
- Network Domain IP Address   --> this is the DNS server ip used by the JDE VM ENT/HTML

4. Save the configuration

5. Check for settings errors

After you have entered values for all the Foundation Servers, the config.sh script performs Configuration Check Results for these servers.

The results are displayed as shown in the example below. This example shows that the first set of values have passed the validation checks performed by the config.sh script. This validation is for syntax only, and does not guarantee connectivity as no networking checks are performed at this point in the process. In the following example, the value 56% at the bottom of the screen indicates that more information is available for these results. Use the Down Arrow key to scroll down to the next page of results.

On Configuration Check Results, verify that the first set of parameters pass the check. This is indicated by [OK] results in the square brackets. Use the Up Arrow and Down Arrow keys to scroll through the complete set of results. The final results screen, indicating 100% complete, is shown below.

d- Build the "ready-to-use" templates

Once 'config.sh' has completed the configuration, you can build the JDE ready to use templates, doing the following steps:

1. Change to the JDE Enterprise Server VM directory

cd /cloudfs/OVS/configTest/JDE_ENT

2. Use this command to tar and zip the JD Edwards EnterpriseOne Foundation System

tar cvfz E1_ENT_VM.tgz E1_X86_SYS_914.img E1_ENT_DSK_914.img vm.cfg

3. Change to the JDE HTML Server VM directory

cd /cloudfs/OVS/configTest/JDE_WEB

4. Use this command to tar and zip the JD Edwards HTML Foundation System

tar cvfz E1_WEB_VM.tgz E1_X86_SYS_914.img E1_WB_DSK_914.img vm.cfg

Import the JDE ready-to-use Templates

As the JDE Enterprise Server and the JDE HTML Server "ready to use template" are now ready:

/cloudfs/OVS/configTest/JDE_ENT/E1_ENT_VM.tgz
/cloudfs/OVS/configTest/JDE_WEB/E1_WEB_VM.tgz

You can import them into ODA VP (Oracle Database Appliance Virtualized Platform),

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

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

example 1:
in the following example you have moved the "ready-to-use" template on ODA VP "dom0" under '/OVS/staging' folder

   # oakcli import vmtemplate E1_ENT -files /OVS/staging/E1_ENT_VM.tgz -repo jderepo -node 0
   # oakcli import vmtemplate E1_WEB -files /OVS/staging/E1_WEB_VM.tgz -repo jderepo -node 0

example 2:
in the following example you have the "ready-to-use" template available from an HTTP server

   # oakcli import vmtemplate E1_ENT -files http://192.168.1.200:8000/JDE_ENT/E1_ENT_VM.tgz -repo jderepo -node 0
   # oakcli import vmtemplate E1_WEB -files http://192.168.1.200:8000/JDE_WEB/E1_WEB_VM.tgz -repo jderepo -node 1

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 (this can from from ODA_BASE as well):

cd /cloudfs/OVS/configTest
python -m SimpleHTTPServer 8000

At this point you can continue the setup described by the "Solution-in-a-box: Best practices for deploying JD Edwards EnterpriseOne on Oracle Database Appliance" whitepaper (March 2014 edition), step 16.

Note as now the imported JDE VM are pre-configured:
   - root password
   - ip/netmask/gateway/dns
   - EOne_cfg.ksh has been executed automatically, you can skip the "Step 24: Configure JD Edwards EnterpriseOne VMs"

References

http://docs.oracle.com/cd/E24902_01/doc.91/e54942/toc.htm
<NOTE:1902046.1> - ODAVP: JDE Platform Pack installation is waiting for ever
<NOTE:1684316.1> - ODAVP: How to bring JDE Deployment Server on ODA Virtualized Platform
<NOTE:1435019.1> - ODA (Oracle Database Appliance): How To Setup ACFS Post Deploy
<NOTE:1437717.1> - ODA (Oracle Database Appliance): Expanding /cloudfs File System
http://www.oracle.com/technetwork/database/database-appliance/oda-jde-soln-in-a-box-technical-2120907.pdf

Attachments

This solution has no attachment