HP Cloud Map for Oracle Fusion

Middleware SOA Suite: Importing the

template

HP-UX Reference Architecture for Oracle Fusion Middleware

Technical white paper

Table of contents

Executive summary ............................................................................................................................... 2

Overview ............................................................................................................................................ 2

Prerequisites ........................................................................................................................................ 3

Resource pool requirements .................................................................................................................. 4 Storage pool requirements ................................................................................................................ 4 Networking requirements .................................................................................................................. 4 Server pool requirements .................................................................................................................. 4

HP Cloud Map for Oracle Fusion Middleware SOA Suite ......................................................................... 4 Download the HP Cloud Map for Oracle Fusion Middleware SOA Suite ................................................ 4 Import the template ........................................................................................................................... 6 Edit network configuration ............................................................................................................... 11 Edit server group configuration ........................................................................................................ 14 Edit storage configuration ............................................................................................................... 17

Importing the workflows ...................................................................................................................... 18

Review the template ........................................................................................................................... 28 Save and publish the template ......................................................................................................... 30

Additional required files ..................................................................................................................... 30 Copy XSL file to CMS ..................................................................................................................... 30 Create the service .......................................................................................................................... 31

Oracle SOA domain customization ...................................................................................................... 32

Summary .......................................................................................................................................... 33

For more information .......................................................................................................................... 34

2

Executive summary

For IT teams, infrastructure provisioning can be both time-consuming and resource-draining. Each

time a business unit, application owner or development team requests resources, a lengthy process

begins. IT experts have to capture system requirements, design the solution from scratch, and then

identify the resources that are currently available and those that need to be procured. HP Insight

Dynamics infrastructure orchestration enables your IT organization to provision infrastructure

consistently and automatically from pools of shared resources using a self-service portal. You can

rapidly provision resources ranging from a single virtual machine to complex multi-tier environments

with physical and virtual servers and storage systems.

Oracle Fusion Middleware (OFM) is Oracle’s complete family of application infrastructure products

that uses WebLogic, Oracle’s Java application server. The OFM product suite ranges from Service

Oriented Architecture (SOA) to enterprise portals, and is integrated with Oracle Applications and

technologies to speed implementation and lower the cost of management and change. This

comprehensive family of products is now even more seamlessly integrated to help you create, run,

and manage agile and intelligent business applications. Oracle’s complete SOA offering, Oracle

SOA Suite is an integrated, best-of-breed suite of products that helps you rapidly design and

assemble, deploy and manage, highly agile and adaptable business applications.

HP Cloud Maps were developed to accelerate the creation of a service catalog by providing a guide

for infrastructure and application provisioning and deployment. The HP Cloud Map for Oracle Fusion

Middleware SOA Suite includes a template and associated workflows which provision OFM SOA

Suite clusters automatically and quickly in a repeatable fashion. This document describes the process

to import the OFM SOA Suite templates into target systems and customize them for use. To review this

reference architecture, and for further information on the installation and configuration, check the

white paper Inside the HP Cloud Map for Oracle Fusion Middleware SOA Suite.

Target audience: This document is for IT managers, database and system administrators and

experienced users who wish to learn more about the capabilities of HP Insight Dynamics and how it

can be used to provision OFM SOA Suite clusters. Knowledge of the HP BladeSystem Matrix and the

underlying components will be helpful when reading this white paper. Please see the For more

information section at the end of this paper for links to additional information on these topic areas.

This white paper describes testing performed in August and October 2010.

Overview

The HP Cloud Map for Oracle Fusion Middleware SOA Suite provides the template, workflows and

scripts used to deploy a single cluster on one or two servers. System and other requirements for the

template and a discussion of the provisioning, igniting, and OFM SOA Suite installation process is

provided in Inside the HP Cloud Map for Oracle Fusion Middleware SOA Suite.

Note

HP Insight Dynamics infrastructure orchestration (HP IO) was previously

referred to as HP Insight Orchestration. Screen shots and technical

information throughout the remainder of this white paper will refer to the

product as Insight Orchestration.

3

Prerequisites

The instructions in this document assume you have already created your OFM SOA golden image.

The file OFM_SOA_Golden_HPUX_image.jar needs to be created before using the HP IO template.

You must install WebLogic Server and OFM SOA Suite on another server and use Oracle’s cloning

tool to build this large file. Please see the For more information section at the end of this paper for

links to additional information on Oracle cloning.

The instructions also assume you have already set up your HP Virtual Connect (VC) infrastructure. You

will need to specify the network connection required for OFM SOA Suite in the template definition.

This template was tested initially using HP Insight Dynamics 6.0 and HP Integrity BL870c server

blades including QLogic QMH2462 4Gb FC HBAs in an HP BladeSystem c7000 enclosure with two

HP 1/10Gb Virtual Connect Ethernet modules and two Virtual Connect 4Gb 4-Port Fibre Channel

(FC) modules. Then later testing was done with the same configuration, except using HP Insight

Dynamics 6.2 and HP Integrity BL860c i2 servers (Intel® Itanium® 9300 series servers). You must

have enabled N_Port ID Virtualization (NPIV) during Insight Dynamics installation for automated

storage provisioning to work. The server where Insight Dynamics is installed is known as the Central

Management Server (CMS). To download HP BladeSystem firmware, go to

http://www.hp.com/go/matrixcompatibility.

Table 1 lists the firmware and software versions used during testing.

Table 1. Firmware and software levels

Component Version (tested in August 2010) Version (tested in October 2010)

Servers Tested HP Integrity BL870c HP Integrity BL860c i2

HP Onboard Administrator 2.60 3.11

HP Virtual Connect Manager 2.33 3.01

HP Integrated Lights-Out 3.06 (iLO 2) 01.01.02 (iLO 3)

QLogic Fiber Channel Adapter Driver: 1.09; Firmware: 4.00.90 Driver: 2.04; Firmware: 4.04.004

HP Insight Dynamics 6.0 6.2

4

Resource pool requirements

Storage pool requirements

The template uses a 100GB disk for boot storage. We will describe below how to customize the

template to support your requirements. In order for the template to deploy successfully, you will need

to pre-configure a storage pool entry of the following size:

100GB for boot (customizable: the HP-UX OS and OFM SOA Suite requires about 40GB)

Networking requirements

Standard requirements for an OFM SOA Suite installation requires network connectivity for

application access to the database server. You should set up your Virtual Connect network such that

your application servers can connect to the database instance using the network you specify when

you customize the OFM SOA Suite template.

Server pool requirements

Depending on the SOA user load in question, you will want to define server pools with appropriate

servers in them. This OFM SOA Suite template requires two servers. It is recommended to have 2GB

memory per CPU core and only one WebLogic instance for every 2-4 CPU cores in the server.

HP Cloud Map for Oracle Fusion Middleware SOA Suite

This section describes the process for importing and customizing the downloadable template and

workflows.

Download the HP Cloud Map for Oracle Fusion Middleware SOA Suite

Go to www.hp.com/go/cloudmaps. Download the HP Cloud Map for Oracle Fusion Middleware

SOA Suite to your desktop. This will be formatted as a zip file, so you should find an appropriate

directory and unzip the file. The file will contain:

Example files for HP Ignite-UX, which is used to install HP-UX

The HP IO template to be imported into HP Insight Dynamics infrastructure orchestration

Workflows to be imported into HP Operations Orchestration (OO)

XSL files to be installed on the HP Systems Insight Manager (HP SIM) server

5

All of these files and especially considerations in configuring the Ignite-UX server are documented in

Inside the HP Cloud Map for Oracle Fusion Middleware SOA Suite. The names of all of the files in the

cloud map, their description, and where to copy the files to are in Table 2.

Table 2. Oracle Fusion Middleware SOA Suite Cloud Map contents and where to copy files

OFM.xml sets up an admin server on one node and a managed server on the second node.

OFM-1node.xml just sets up an admin server. OFM.xml is used as a template that can be expanded

to have one admin server and a number of managed servers. OFM-1node.xml is used for a small

setup or to debug any initial configuration issues you may have.

Filename Description Copy To Server Instructions

doSOAinstall.sh Master shell script

run from HP IO to

install OFM SOA

Suite onto HP-UX

Copy to c:\tmp on CMS

FindPrimaryIPAddre

ssByLogicalServerID.

xsl

Get fully qualified

hostnames and IP

addresses

Copy to c:\Program Files\HP\Insight

Orchestration\conf\OO on CMS

ignite_example.tar Ignite-UX example

files described in the

“Ignite-UX server

setup” section in

Inside the HP Cloud

Map for Oracle

Fusion Middleware

SOA Suite.

Copy to Ignite-UX server in a scratch directory (for

example, in a subdirectory under /tmp or /var/tmp).

Execute: tar xfv ignite_example.tar

Then follow the instructions in the “Ignite-UX server

setup” section in Inside the HP Cloud Map for Oracle

Fusion Middleware SOA Suite as to what each file in

the tar ball is used for and copy the files to the

appropriate place as instructed.

installSOA.jar Files used to install

OFM SOA Suite

onto HP-UX

Copy to c:\tmp on CMS

OFM.xml HP IO template for 2

OFM nodes

Copy to c:\tmp on CMS for future HP IO template

import discussed in the Import the template section.

OFM-1node.xml HP IO template for 1

OFM node

Same instructions as OFM.xml.

OFMdoc.zip HP IO automated

documentation of

workflows

(Optional) Copy to c:\tmp on CMS and unzip in

subdirectory.

OFMWorkflow.zip Workflows to deploy

OFM SOA Suite

Unzip on CMS server in a directory under c:\tmp.

Make a note of where this is so you can import the

workflows in the future.

6

Import the template

From the Insight Orchestration Designer portal, select the “Import” button as shown in Figure 1.

Figure 1. Insight Orchestration Designer

7

The following dialog will be presented. You should find the file you downloaded and select it here

and press “Open”. This will import the template into HP IO. The “OFM” template shown in Figure 2 is

for two servers. “OFM-1node” is for one server.

Figure 2. Upload a template

8

Because the template defines networking, storage and bootable disk requirements, you will encounter

the following error upon import. This is normal; you will need to reconfigure the boot properties to

select a bootable disk on your system. This will be described later.

Figure 3. Reconcile imported template data

9

After import, you should see a template that looks like Figure 4. You will notice that the Validation

Status is showing errors. If you select the Show Issues button, it will highlight the areas requiring

attention.

Figure 4. Two server template

10

Figure 5 shows three errors that need attention highlighted in red. The first two errors are that the two

networks that were defined in the template do not exist on the target system, so you will need to

assign the networks to networks that exist on your site. The other error is that the server pool does not

exist in this installation. (Note: Although it is not highlighted in Figure 5, the bootable disk pool also

needs to be setup. Your installation will need to be modified to use a bootable disk on your site.) We

will now go through the steps required to address these issues.

Figure 5. Three server template validation errors

11

Edit network configuration

We will first address the networking configuration. Right click on the private network icon and select

“Edit Network Configuration”.

Figure 6. Edit the network configuration

12

This will bring up the network configuration dialog shown in Figure 7. In this dialog you will specify

which network should be used for deployments of this template on your site. Click the “Select a

specific network” radio button. This will display all of the networks configured on your site. Select the

network that you wish to use for this template. The deployment network must have only one Ignite-UX

server on it and no Insight Rapid Deployment (RDP, also called Insight Control server deployment)

servers, which are used to deploy Microsoft® Windows® or Linux.

Figure 7. Configuring the private deployment network

13

For the example in Figure 8, the Public-Vega network will be the network that your application servers

will use to connect to your database server. It cannot be the deployment network or the boot network.

Figure 8. Edit the network configuration for the public network after the private network.

As you can see, when you select the network, the details of this network are shown on the dialog,

including how many addresses are available in the address pool for this network.

14

Edit server group configuration

Next we will address the server configuration. Right click on the server icon and select “Edit Server

Group Configuration”.

Figure 9. Configuring the server group

15

Figure 10 shows the Configure Server Group attributes. You can modify the attributes to match the

hardware you have in your environment. On this dialog, you will see a red X on the Software tab.

Select that tab to fix software configuration.

Figure 10. Configuring the server group minimums

16

In Figure 11, the version of HP-UX operating system software must be configured. In addition, the

appropriate operating system software must be installed on the Ignite-UX server.

Figure 11. Configuring the Ignite-UX server operating system software to install

17

Edit storage configuration

Now we need to adjust the storage configuration to match what is available on your site. Right click

on the boot disk and select “Edit Storage Configuration”. The minimum SAN disk LUN size

acceptable is configured to be 100GB. In addition, the disk is SAN bootable and RAID 1. This is

customizable and you can change the size to fit your needs.

Figure 12. Edit the storage configuration.

Before moving to the next step, click on the Save icon to save all of your template changes.

18

Importing the workflows

Before you can complete the required changes to the template, you need to import the workflows that

are used in the template. Launch HP Operations Orchestration Studio either from the desktop icon or

from the Start menu and login as admin user and specify the password you used during Insight

Dynamics installation.

Select Repository and then Add Repository (see Figure 13).

Figure 13. Add Repository

19

Type in a Repository Name and select the location where you copied the repository files. The

example in Figure 14 shows a Repository Name of SetUpOFM. Click OK to open the repository

in Studio.

Figure 14. Add Repository Name

20

Click on Repository and then Set Target Repository and select your Default Public Repository.

Figure 15. Set Target Repository

21

Click on Repository again and then Publish source to Target – Preview. Click on the Apply icon

circled in green in Figure 16. Circled in red in the figure are the objects to be published.

Figure 16. Publish to Source Target – Preview

22

If desired enter a comment for the workflows added and click on OK.

Figure 17. Publish Comment

23

A confirmation message is displayed as shown in Figure 18. The workflows have been added to the

default repository.

Figure 18. Publish completed successfully

24

Click on Repository, then Open Repository and select Default Public Repository.

Figure 19. Open Default Repository

25

After the workflows are imported, they appear in the left pane. The workflow utilized by the template

is SetUpOFM, which appears under the OFM folder as shown in Figure 20.

Figure 20. Workflows for OFM template

26

Next we will add the System Properties that are required for the workflows. Expand the configuration

folder, then right click on System Properties and select New as shown in Figure 21.

Figure 21. Add System Property

Enter AdminUser for the System Property name and click on OK.

Figure 22. System administrator login and password

27

Specify the name of the AdminUser you want to create in the Property Value field. The example below

sets AdminUser to be Administrator.

Figure 23. Add System Property

Two more System Properties need to be added. Table 3 lists the required System Properties and

description. Following the method described above, create a new System Property for each property

listed in the table.

Table 3. System Properties required for SetUpOFM workflow

Property Description

AdminUser Administrative User for CMS Server. Usually Administrator for Windows

AdminPassword AdminUser’s password

RemoteCommandUser Administrative user for HP-UX server to install OFM SOA (usually root)

RemoteCommandPassword Password for RemoteCommandUser

You can now save your modifications and close Operations Orchestration.

28

Review the template

After the workflows are imported, return to Insight Orchestration Designer to review the workflows

associated with the template. Click on the Workflows button (circled in red in Figure 24) to display

the workflows.

Figure 24. Workflows for OFM SOA Suite template

29

The workflows associated with the template are shown in Figure 25.

Figure 25. Workflow Execution Points

The main workflow, SetUpOFM, is called at the end of the Create Service execution point. The

CaptureXML workflow is strictly for debugging. This workflow writes the XML to a file in the c:\tmp

folder of the CMS when the service is created. The generated XML can then be easily copied into

Operations Orchestration Studio for debugging. Verify the execution point for each workflow is

properly set in the template.

Table 4. Workflow Execution points

Workflow name Execution point

CaptureXML Create Service: Beginning

SetUpOFM Create Service: End

30

Save and publish the template

Now the template Validation Status should be green, so we can save and publish the template. Insert

comments in the Notes section that will help your users know when to choose this template, click on

the checkbox next to “Published”, and click on the Save icon to save the template.

Figure 26. Publish the updated template

Your users will now be able to select and deploy this template from the HP IO User Portal.

Additional required files

Copy XSL file to CMS

The workflows use Extended Scripting Language (XSL) files to extract key values from the service

model for use by HP-UX shell scripts. Table 5 lists the XSL files included with the HP Cloud Map for

Oracle Fusion Middleware SOA Suite. This file should be copied to the HP Systems Insight Manager

(HP SIM) server in the following location: c:\Program Files\HP\Insight Orchestration\conf\OO.

31

Table 5. XSL file

Filename Description

FindPrimaryIPAddressByLogicalServerId.xsl Get fully qualified hostnames and IP addresses

Create the service

Once the template edit is complete and the server and storage pools have been created, a service

can be created. In the Create Service window, enter a service name. The example in Figure 27 shows

a Hostname Completion string of “server”. Using a hostname completion string of server, the first

hostname that will be created is server01.

Figure 27. Create the service

32

If you wish to change the Lease End date, Email address, or Server Pool selection, click on the

Options button to make your modifications. (See Figure 28.)

Figure 28. Service options

Deployment of an OFM SOA Suite service begins after you click Submit. If all the required resources

are available, logical servers will be created and HP-UX will be installed to the boot LUN. After the

OS is deployed, the workflow runs and completes the installation by running a shell script. OFM SOA

Suite will be installed by this shell script utilizing Oracle’s apply clone functionality. The shell script

will also unpack the SOA domain.

Oracle SOA domain customization

After the service is completed, deploy a specific SOA application into the admin console, configure

the SOA domain for the specific environment, and then bring up the admin server and managed

server. See the WebLogic Server Administration Console in Figure 29.

33

Figure 29. WebLogic admin console shows that admin server and one managed server are up. The other managed servers are

reserved for expansion.

Summary

Built on the HP BladeSystem, BladeSystem Matrix is a Converged Infrastructure platform providing

pools of computer, storage and network resources that can be quickly deployed. The goals of Matrix

are to help accelerate provisioning, to optimize IT capacity across physical and virtual environments

and to ensure predictable delivery and service levels. This enables companies to address some of the

key datacenter pain points facing them today including rising costs, low utilization rates, and

inflexible environments.

With Matrix, powered by HP Insight Dynamics, application services can be quickly provisioned using

infrastructure orchestration templates. This enables IT organizations to develop service-driven,

standardized application deployment processes. The HP Cloud Map for Oracle Fusion Middleware

SOA Suite detailed in this paper provisions a two node OFM SOA cluster automatically and quickly

in a repeatable fashion.

For more information

HP BladeSystem Matrix http://www.hp.com/go/bladesystemmatrix

Matrix Cloud Map download site http://www.hp.com/go/cloudmaps

HP Insight Dynamics http://www.hp.com/go/insightdynamics

HP Insight Dynamics infrastructure orchestration

documentation

http://h18004.www1.hp.com/products/solutio

ns/insightdynamics/info-library.html

HP BladeSystem http://www.hp.com/go/bladesystem

Oracle Fusion Middleware http://www.oracle.com/us/products/middlewar

e/index.html

Oracle Cloning http://download.oracle.com/docs/cd/E15523_

01/core.1111/e10105/clone.htm

HP BladeSystem c-Class technical

documentation (planning, installing,

maintenance and troubleshooting,

functionality and value)

http://h71028.www7.hp.com/enterprise/cache

/316682-0-0-0-121.html

“HP StorageWorks SAN Design Reference

Guide” – best practices for SAN design

http://h20000.www2.hp.com/bc/docs/support

/SupportManual/c00403562/c00403562.pdf

Command View EVA overview and features http://h18006.www1.hp.com/products/storage

/software/cmdvieweva/index.html

Ignite-UX http://www.hp.com/go/ignite-ux

DNS server – named(1M) Logon to HP-UX system and do the following to get

man pages:

man named

man named.conf

To help us improve our documents, please provide feedback at

http://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html.

© Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries.

4AA3-1255ENW, Created September 2010; Updated November 2010, Rev. 2