Inside the HP Cloud Map for Oracle

Fusion Middleware SOA Suite

HP-UX Reference Architecture for Oracle Fusion Middleware

Technical white paper

Table of contents

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

Overview ............................................................................................................................................ 3

Project boundaries ............................................................................................................................... 3

Contents of the HP Cloud Map for Oracle Fusion Middleware SOA Suite ................................................... 4

Ignite-UX server setup ........................................................................................................................... 4

Networks .......................................................................................................................................... 11

Shared storage pool entries ................................................................................................................ 12

HP IO template .................................................................................................................................. 14

HP Operations Orchestration (HP OO) workflow: SetupOFM .................................................................. 16 Files in installSOA.jar ..................................................................................................................... 17 Master shell script installer doSOAinstall.sh ....................................................................................... 18

Oracle SOA domain customization ...................................................................................................... 19

Summary .......................................................................................................................................... 20

For more information .......................................................................................................................... 21

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.

Normally, a customer must get the systems allocated and then do a host of manual steps. These

include installing the operating system, WebLogic Server, OFM software, and configuring the OFM

domain for the admin server and each application server in the WebLogic cluster. As a support pillar

to the HP Converged Infrastructure paradigm, all of this can be done automatically through HP Insight

Dynamics infrastructure orchestration. This paper showcases Service Oriented Architecture (SOA)

Suite as a representative example for automating deployment of any OFM product.

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 templates and associated workflows, which provision one or two

SOA instances automatically and quickly in a repeatable fashion.

The focus of this white paper is on the creation of the HP Ignite-UX server deployment for the OFM

SOA Suite template; details on the workflows which complete the installation and configuration of the

server; and the scripts which the workflows leverage. Instructions for importing the template are found

in HP Cloud Map for Oracle Fusion Middleware SOA Suite: Importing the template.

This white paper documents the HP Cloud Map for Oracle Fusion Middleware SOA Suite

downloadable from the HP Cloud Maps site at www.hp.com/go/cloudmaps. This Cloud Map

contains the following files:

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

The HP IO template1 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

This Cloud Map uses a specific environment to demonstrate the power of Insight Dynamics. It can be

used as a robust example to be customized to fit your specific needs.

Target audience: This document is for experienced IT database and system administrators and users

who wish to learn more about the capabilities of HP Insight Dynamics and how it can be used to

provision Oracle Fusion Middleware (OFM) or similar applications on HP Integrity servers running

HP-UX. Knowledge of the HP BladeSystem Matrix and the underlying components will be helpful when

reading this white paper. You should also have a basic understanding of Oracle Fusion Middleware

1 HP Insight Orchestration template, which is discussed in more detail on the following page.

3

(OFM). 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.

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.

Overview

This white paper describes the process of setting up an Ignite-UX server and then taking an installed

infrastructure orchestration server and customizing it to install the Oracle Fusion Middleware (OFM)

Service Oriented Architecture (SOA) Suite infrastructure software on one or two HP-UX servers.

This is a very detailed technical document that goes beyond the standard setup of infrastructure

orchestration on the Central Management Server (CMS). It describes the first time discovery of

infrastructure components, the process of placing servers in a pool, and the basics of how to setup

and use the Ignite-UX server. Please examine the For more information section at the end of this paper

for a number of reference manuals and URLs that will more thoroughly explain those tasks. This paper

will discuss the following:

1. A detailed description of the contents of the HP Cloud Map for Oracle Fusion Middleware SOA

Suite and the HP IO template that is a major high level component of the Cloud Map.

2. A detailed discussion of the Ignite-UX files included in the Cloud Map. There are specific files that

need to be configured on the Ignite-UX server for the ignite process to work smoothly. The main

difference between HP IO using Ignite-UX and the standard Ignite-UX process is that there is no

user interaction.

3. Network requirements. Two networks are used in this Cloud Map because HP IO needs the ignite

network to have only one Ignite-UX server or one x86 HP Insight Rapid Deployment (RDP, also

called Insight Control server deployment) server on that network and for that network to use the

server’s first NIC card (that is the highest priority card and slot).

4. Configuration of storage pool entries for system boot disks and linking that with the SAN storage

device.

5. How an HP Operations Orchestration (HP OO) workflow can be used to install large and complex

products like Oracle WebLogic Server and Oracle Fusion Middleware SOA infrastructure software

right after HP-UX installation and without user interaction.

6. Understanding the master shell script called by the HP OO workflow. The shell script is quite short

and calls two one line shell scripts to install WebLogic Server and OFM SOA Suite and then to

unpack the SOA domain.

Project boundaries

The following assumptions were made in the creation of this Cloud Map.

Oracle Fusion Middleware configuration:

The pre-built WebLogic domain contains an admin server and a SOA Cluster of multiple SOA

managed servers. SOA domains still need to be configured manually for each server and IP

addresses need to be setup in those configurations.

4

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

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

cloning tool to build this file that will be at least 2GB large. See the For more information section at

the end of this paper on how to perform Oracle cloning. Put OFM_SOA_Golden_HPUX_image.jar

in c:\tmp on the CMS.

Servers will not come up automatically in WebLogic Production mode. In development mode,

passwords can be stored in a file to bring up the servers automatically.

The admin console can be used to do a mass startup of all the SOA managed servers.

Database server:

The database server is pre-configured and setup prior to using this Cloud Map. At the time of this

publication, there are other papers discussing how to use HP IO to setup Oracle Real Application

Clusters (RAC) servers. For more information, see http://www.hp.com/go/cloudmaps.

Contents of the HP Cloud Map for Oracle Fusion

Middleware SOA Suite

The files referenced in this paper are shown in Table 1 below. Each of these files, and in some cases

sub files, will be described in more detail in this paper.

Table 1. HP Cloud Map for Oracle Fusion Middleware SOA Suite contents

Filename Description

ignite_example.tar Ignite-UX example files described in Ignite-UX server setup section

OFM.xml HP IO template for 2 OFM nodes

OFM-1node.xml HP IO template for 1 OFM node

OFMWorkflow.zip Workflows to deploy OFM SOA Suite

doSOAinstall.sh Master shell script run from HP IO to install OFM SOA Suite

onto HP-UX

installSOA.jar Files used to install OFM SOA Suite onto HP-UX

OFMdoc.zip HP IO automated documentation of workflows

Ignite-UX server setup

To be able to install HP-UX on an Integrity server through infrastructure orchestration, an Ignite-UX

server is required. The discussion here on Ignite-UX and using a DNS server through named(1M) is

just to show an example implementation and is not meant to replace documentation already provided

by HP. Please look through the For more information section at the end of the paper for more details

on finding documentation for named(1M). The following actions need to be performed:

1. Install the “IGNITE” bundle from an HP-UX distribution onto the Ignite-UX server. Note that version

C.7.9.260 or later is required to support HP-UX in the Insight Dynamics framework.

2. For HP IO to function properly, the servers must have their highest priority network card configured

for the ignite network. In addition, the Ignite-UX server must not share the deployment/boot

network with any other deployment servers (that is, x86 RDP (Rapid Deployment Pack). Because of

5

this, the scenario used in this paper had a private network for installation only (that is, 10.0.0.x

network) and a separate public network (156.153.x.y) to communicate with other servers. It is

possible to just use one network if there is only one Ignite-UX server on that network, no x86 RDP

server on that network, and the system to be ignited doesn’t need access to another network.

3. Just as the Ignite-UX server runs in silent mode for HP IO, likewise the ignite files in the Cloud Map

can be used to run in silent mode without using HP IO. In this way, if there is something wrong

with the ignite configuration, the administrator can unit test out the ignite process without using

HP IO.

4. After the HP-UX operating system depot is installed on the Ignite-UX server, the administrator must

register it. So if HP-UX 11i v3 March 2010 version is swcopy’ed to

/var/opt/ignite/depots/1003.1131, then the administrator must execute the following command:

“swreg -l depot /var/opt/ignite/depots/1003.1131”. Note that Ignite-UX can install

golden images for the operating system as was done in a similar way to install OFM SOA. For this

paper, Ignite-UX installs the operating system using the standard depot install method. In addition,

instead of using swcopy and swreg, you could use make_depots and make_config. Please look

through the For more information section at the end of this paper for more details.

5. For /etc/inetd.conf, uncomment the bootps, finger, and uucp lines so that the system can use

/etc/bootptab to boot the Ignite-UX server. “kill -1 <pid for inetd>” will get the inetd

process to re-read its configuration file.

6. For HP-UX 11i v3 servers, Ignite-UX servers must specify the clients directory in /etc/dfs/dfstab.

The format (on one line) is: /usr/sbin/share -F nfs -o anon=2,rw -d "" /var/opt/ignite/clients

7. After creating the dfstab entry, execute the command “shareall -F nfs”.

8. The firmware on the HP-UX server(s) that will be installed must be up to date for HP IO to ignite the

server without user input. For this demo, the HP Integrity BL870c system firmware needed to be at

least version 4.21 and the Extensible Firmware Interface (EFI) firmware needed to be at least

version 7.15. Compatible firmware for all components are available at

http://www.hp.com/go/matrixcompatibility. The system firmware files, installation instructions,

and release notes with detailed firmware version information can be obtained by selecting

Download drivers and software at www.hp.com/go/bizsupport. Be sure to read the Release

Notes for the firmware to ensure a successful update.

The following tables describe the files found in ignite_example.tar. The first set of files in Table 2 are

used to configure the ignite server. Some of the files are optional and some are work in process files.

Due to their non-permanent state, they are placed in /tmp. If used, their final destination will not be in

/tmp. The files described in Table 3 are in /etc and perform very different functions from each other.

The files described in Table 4 are in /etc/named.data that is used in conjunction with

/etc/named.conf to function as the DNS server (that is, machine name and domain name server

(DNS) lookup of Internet protocol (IP) addresses). The files in Table 5 tell the Ignite-UX server what

operating system software is downloadable and how to configure the SAN bootable root disks.

Table 2. Ignite-UX configuration files

Directory Filename Description

/tmp/ignite AUTO If this file is placed in /opt/ignite/boot, silent

ignition can be done without using HP IO. This

file may be carefully edited for other

parameters. /opt/ignite/boot/bin/auto_adm

may be used for further customization.

6

Directory Filename Description

ignite_boot.cfg Ignite-UX server parameters to put into IINSTALL

boot files under /opt/ignite/boot

subdirectories. IINSTALL files are used to boot

the system for the ignite process and need to

be configured properly.

update_etc_issue An example on how to customize the Ignite-UX

server to make the logon message non-generic.

This is not used in this demo, but there is a

commented line with this filename at the end of

/var/opt/ignite/data/config.local. If that line

is uncommented to execute update_etc_issue,

this file needs to be placed in

/var/opt/ignite/scripts to be executed during

the ignite process.

Execute “instl_adm –d” to see what parameters are being used for the current Ignite-UX server.

Use the current setup as compared to the example in “/tmp/ignite/ignite_boot.cfg” to set your

parameters. This file is commented and states the use of parameters within the file.

After comparing this file and current Ignite-UX server parameters, create your own

/tmp/ignite/my_ignite_boot.cfg.

Then run: “instl_adm –f /tmp/ignite/my_ignite_boot.cfg” to update

/opt/ignite/boot/…/IINSTALL files.

Table 3. /etc files used in ignite process

Directory Filename Description

/etc bootptab File that indicates that the server to be ignited

should boot from this Ignite-UX server. “ignite-

defaults” is all that is in the file initially. The

“newii01” section is an example of what will

be added to this file to ignite the server. “ha=”

is the MAC address of the network card it will

boot off of. “ip=” is the IP address of the server

to be ignited. “gw=” is the gateway, which is

the Ignite-UX server.

dhcptab Allows system to use DHCP for ignited server.

named.conf This file with /etc/named.data allows there to

be a DNS server for the Ignite-UX server private

network. Notice that it has a “forwarders”

clause where if it doesn’t find the IP address in

the DNS server for the private network, it will

then use the DNS server of the public

156.153.x.y network.

resolv.conf Points to the private DNS server 10.0.0.1,

which is also the Ignite-UX server.

7

Table 4. /etc/named.data files to be used in named(1M)

Directory Filename Description

/etc/named.data db.10 List of the systems in db.bench below, but in

reverse IP address order. So an IP address of

10.0.0.1 is listed as such: Ignore the “10” or

first number. That is excluded. Then write the

address in reverse number order after that for

the system or “1.0.0”. An IP address of

10.0.0.11 would be written “11.0.0” in this

file.

db.127.0.0 Used for localhost. Update this file to

correspond to the network used in

/etc/resolv.conf.

db.bench List of systems to put into the private network

including the Ignite-UX server and the HP IO

CMS server running Microsoft® Windows®.

db.cache Soft link to db.bench

The configuration needs to have DNS access and reversed DNS access for the Windows Central

Management Server (CMS), Ignite-UX server, and all of the servers to be ignited. After configuring

these files, run named(1M) to start the DNS server.

Table 5. Ignite configuration files in /var/opt/ignite

Directory Filename Description

/var/opt/ignite INDEX Soft link to data/INDEX

config.disk Ignite disk configuration

config.local Soft link to data/config.local

config.root_disk Delineates what kinds of root disks are allowed

/var/opt/ignite/data INDEX List of all of the depots loaded on the Ignite-UX server

config.local Master configuration for Ignite-UX server. Allows

administrator to run shell scripts for ignite

customization.

/var/opt/ignite/11.31 config.Mar10 How Ignite-UX should load HP-UX operating system

depot and which file sets are in the depot

8

Before proceeding with the first use of Ignite-UX through HP IO, there are a few steps that must

be done:

1. Root password must be entered in the First Time Wizard screen as shown in Figure 1.

2. The ignite server must be discovered into HP Systems Insight Manager (SIM). To accomplish this:

create a discovery task for the Ignite-UX server and discover the Ignite-UX server into SIM as a

managed node as shown in Figure 2. The circled IP address in the figure is that of the Ignite-UX

server or its console.

3. To configure the Ignite-UX server in your environment, run: “mxnodesecurity –a –p

dsc_ignite –c <username>:<password> -n <Ignite-UX server IP address>”.

The example in Figure 3 shows a correctly configured Ignite-UX server as displayed by the

“mxnodesecurity –l” command.

Figure 1. Ignite-UX Server First Time Wizard screen – root password required to be put into HP IO

9

Figure 2. HP IO Discovery screen. Ignite-UX server must be discovered.

Figure 3. Result of the mxnodesecurity –l command using the Command Prompt on the Central Management Server. The

dsc_ignite protocol must be entered for the Ignite-UX server.

10

Figure 4 shows an example run of the ignite process running by HP IO after the Ignite-UX server and

the HP IO Central Management Server (CMS) are fully configured. After the system has been

provisioned, the HP-UX server will be powered on and booted. The standard boot process ensues

followed by the screen below. The Ignite-UX server does not need user input as would be done in the

standard Ignite-UX process.

The warnings seen in Figure 4 below are standard Ignite-UX warnings. Since there are no errors, the

non-interactive Ignite-UX installation continues.

Figure 4. HP IO running Ignite-UX in silent mode – no user input needed

11

Networks

In this setup, two networks are used: one as a private net for deployment and the second is a public

LAN. There can only be one deployment network and one boot network, and as shown in Figure 5,

both have to be on the same network with the Ignite-UX server. Other environments may use just one

network, if it only has one Ignite-UX server on it and no x86 RDP server. For this demo, it was decided

to have a private Ignite-UX network and a public network that would be able to access other systems

outside of the systems used for this project.

If the public network is also a boot network (that is, both private and public networks are boot

networks), the wrong LAN MAC address may be written in /etc/bootptab thus making the system

ignite off the wrong network. By clicking on the “Networks” tab as shown in Figure 5, the network

address and network mask are shown for each network.

Figure 5. HP IO Network configuration

12

Shared storage pool entries

Setting up the shared storage pools correctly is necessary to set up SAN boot disks (that is, root disks)

for each of the HP-UX servers. For information on creating storage pool tags, see HP Insight

Virtualization Manager Software with Logical Server Management: User Guide.

Set the Storage Port World Wide Names (WWN) in Figure 8 to match the WWN at the bottom of

Figure 6. The storage volume sizes specified in the storage pool entry must exactly match the shared

disk sizes you defined in the HP IO template and the virtual disk size created in HP StorageWorks

Command View EVA (CV EVA). Compare the “Manage Server WWNs” section in the bottom of

Figure 6 with the “FC Adapter Port WWNs” in Figure 8. They must match exactly. In order to reach

the screen in Figure 8, go to the screen on presenting LUNs to a host in Figure 7 and select the

“Ports” tab.

Figure 6. Add shared storage pool entry– volume definitions

13

Figure 7. Command View EVA Host definition

Figure 8. Add Port WWN

14

HP IO template

The HP IO template is a representation of all of the major components managed by HP IO that need

to be pulled together to make the HP-UX server. Below is the HP IO template screen for two servers.

Figure 9. HP IO template screen for Oracle Fusion Middleware

15

Figure 10 is a closer look at the HP IO template. It says that two HP-UX 11i servers from the group

known as SvrGrp1 need a total of two FC-SAN boot disks from a group known as Disk1 (that is, one

disk per system). Each server also needs two networks, one on the Public-Vega network and one on

the Private_Encl_1 network.

Figure 10. HP IO template for Oracle Fusion Middleware

16

HP Operations Orchestration (HP OO) workflow:

SetupOFM

SetupOFM is the main workflow included with the Cloud Map. SetupOFM, shown in Figure 11, is

called when an OFM service is created.

Figure 11. SetupOFM workflow as seen from Operations Orchestration Studio on the Central Management Server (CMS)

SetupOFM workflow performs the following steps (match the items in the workflow above with the

items in parentheses in the list below):

1. (Find Primary Hostname IP Addresses) Parse the XML passed into the workflow. The workflow uses

the XSL files to extract server names and IP addresses.

2. (List Iterator) Iterate through each of the systems to be installed.

3. (Wait For SSH Available) – Wait for the HP-UX system to be ready to accept commands (that is,

ignited and booted up).

4. (Put #1) Transfer large OFM clone file to install WebLogic Server and OFM SOA Suite. The file is

copied from the CMS server to the HP-UX server that was just installed. This file is used to install

both products in a pre-configured way through Oracle’s cloning process. For this demo, the file

(OFM_SOA_Golden_HPUX_image.jar) is more than 2.2 GB and is not included in the Cloud

Map.

17

5. (Put #2) Transfer archive file installSOA.jar for other files and scripts used for OFM installation.

6. (Put #3) Transfer master installation shell script doSOAinstall.sh.

7. (SSH Command) Execute shell script doSOAinstall.sh on new system to silently install WebLogic

Server, install OFM SOA Suite, and unpack the SOA domain.

8. (Register Servers) After the HP-UX servers are up, the servers must be registered. This is done

automatically by the workflow and is not needed to be done manually.

Files in installSOA.jar

Table 6. Files in installSOA.jar

Filename Description

applyclone.sh Installs OFM SOA Suite and WebLogic Server by applying the clone

to a large 2.2GB flat file OFM_SOA_Golden_HPUX_image.jar

cloningclient.jar Jar file that is used by applyclone.sh

soadomain.jar Packed SOA domain to be unpacked during installation

unpackSOADomain.sh Script unpacks SOA domain

scripts/createClone.sh This file was used to create OFM_SOA_Golden_HPUX_image.jar after

WebLogic Server and OFM SOA Suite were installed on a server.

scripts/listclone.sh Lists the clone archive that was created

scripts/packSOADomain.sh Packs the SOA domain that will be unpacked by the

unpackSOADomain.sh

scripts/startInstall.sh Installs WebLogic Server from the original Oracle distribution jar file

18

Master shell script installer doSOAinstall.sh

The master shell script is shown in Figure 12 and is the only shell script called directly from the HP

OO workflow, SetupOFM. It is a short shell script called right after HP-UX installation that does basic

setup; it then calls two one line shell scripts to install WebLogic Server and OFM SOA Suite. Then it

calls another shell script to unpack the SOA domain.

Figure 12. Shell script

#!/bin/sh

cd /var/tmp

# When files are created, make them in 644 mode or 755 for executables.

umask 22

# Create user oracle with encrypted password FEXDHGhCd8pXA.

# Use another encrypted password as copied from /etc/passwd.

groupadd -g 500 dba

useradd -u 500 -g 500 -m -p FEXDHGhCd8pXA -s /usr/bin/ksh -c 'Oracle User' oracle

# OFM 11g will be installed in /usr/oracle and /var/tmp/SOA will be used as a temp workspace

mkdir /usr/oracle SOA

touch /etc/oraInst.loc

chown oracle:dba /usr/oracle /etc/oraInst.loc SOA

# /etc/oraInst.loc tells where Oracle's inventory is and the install group.

echo inventory_loc=/home/oracle/oraInventory > /etc/oraInst.loc

echo inst_group=dba >> /etc/oraInst.loc

mv OFM_SOA_Golden_HPUX_image.jar SOA

# Do the installation as the oracle user.

sh << EOT

#!/bin/sh

su oracle

export JAVA_HOME=/opt/java6

umask 22

set -x

cd SOA

/opt/java6/bin/jar xfv ../installSOA.jar

# install OFM 11g with WebLogic Server

sh ./applyClone.sh

# unpack the SOA Domain

sh ./unpackSOADomain.sh

EOT

19

Oracle SOA domain customization

After infrastructure orchestration has completed the installation of HP-UX and OFM SOA Suite, deploy

your specific SOA application into the admin console, configure the SOA domain per your specific

environment, and then bring up the admin server and managed server. See the WebLogic Server

Administration Console in Figure 13.

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

reserved for expansion.

20

Summary

With the HP BladeSystem Matrix, you can simplify and streamline building out a flexible and dynamic

Converged Infrastructure. HP BladeSystem Matrix is built with HP BladeSystem, HP Virtual Connect,

HP Insight Software, HP StorageWorks, and fulfillment capabilities (factory integration and onsite

services). HP Insight Dynamics infrastructure orchestration provides a mechanism for quickly

provisioning application services using pre-defined templates. These templates describe the resource

requirements of that application service. As part of the template, HP OO workflows can be attached

at various points in the execution flow. These workflows can be utilized to perform additional post

operating system installation and configuration tasks further automating the rollout and provisioning of

the various services in your organization.

This white paper describes the HP Cloud Map for Oracle Fusion Middleware SOA Suite infrastructure

software. The Cloud Map includes workflows and scripts that automate the installation and

configuration of OFM SOA Suite instances. Upon completion of the deployment, the OFM

administrator may customize the SOA domain to fit the end-user’s needs.

For more information on how to import the Oracle Fusion Middleware SOA Suite template and

workflows into your HP BladeSystem Matrix environment, please download the HP Cloud Map for

Oracle Fusion Middleware SOA Suite, HP Cloud Map for Oracle Fusion Middleware SOA Suite:

Importing the template, and additional documentation from the HP Cloud Maps download site at

www.hp.com/go/cloudmaps.

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/solutions

/insightdynamics/info-library.html

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

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

/index.html

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

1/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.

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