You are on page 1of 21

HP/EDS Hosting Services

WebWerks

Requirements Guide

HP/HP/EDS HS WebLogic Server 9.2


(WLS 9.2) on HPUX 11iv23 Itanium with
Serviceguard
Version 1.0

1 October 2009

GM/HP/EDS Confidential

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard

Change History
This document complies with the requirements of Content Standards for Requirements, version 3.08,
effective 30 March 2009. The QMS Web site version of this document is controlled. All other versions are
uncontrolled.
The following Change History table contains a record of changes made to this document:
Published /
Revised Date

Version #

1st October
2009

Draft

15th October
2009
26th October
2009

Draft
1.0

Document
Owner
SreeLatha
Chalasani
HP/EDS HS
Engineering
248-364-5819
Sreelatha.chal
asani@hp.com
Same as
above
Same as
above

Section / Nature of Change


Created Document

Included information about service guard


Included information about Web server even though it is
out of scope for the build.
Also made changes as per peer review comments

Statement of Confidentiality
This document contains information that is confidential and proprietary to HP/EDS. This information is made available
with the express understanding that it will be held in strict confidence and not disclosed, duplicated, or used, in whole or in
part, without written consent from the HP/EDS Legal department. Information can only be disclosed, duplicated, or
otherwise used in accordance with the nondisclosure agreement with HP/EDS. Additionally, this information shall be
limited to HP/EDS and GM persons having a need to know.
HP/EDS is a registered mark, and the HP/EDS logo is a trademark, of Electronic Data Systems Corporation. HP/EDS is
an equal opportunity employer and values the diversity of its people. Copyright 2014 Electronic Data Systems
Corporation. All rights reserved.
Product names referred to herein are trademarks of their respective companies. Many of the designations used by
manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in
this document, and the editorial staff was aware of a trademark claim, the designations have been printed in initial capital
letters.
Version 1.0

GM/HP/EDS Confidential

1 October 2009

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard

Contents
Introduction................................................................................................................................... 1
Contacts........................................................................................................................................................ 1
Scope / Proposed Solution............................................................................................................................1
General Data-Flow Description.................................................................................................................. 3

Requirements................................................................................................................................ 3
1.

Functional...............................................................................................Error! Bookmark not defined.

2.

Administrative / Back-End Access..........................................................................................................7

3.

Application Access................................................................................................................................. 7

4.

Application Testing.................................................................................................................................. 7

5.

Availability / Load Balancing...................................................................................................................7

6.

Backup and Restore............................................................................................................................... 8

7.

Batch Processes.................................................................................................................................... 8

8.

Conflicting Requirements....................................................................................................................... 8

9.

Control Tool............................................................................................................................................ 8

10. Disaster Recovery.................................................................................................................................. 8


11. Event Monitoring.................................................................................................................................... 8
12. Network.................................................................................................................................................. 8
13. Operating Environments......................................................................................................................... 9
14. Operational Readiness........................................................................................................................... 9
15. Remote Access.................................................................................................................................... 10
16. Reporting.............................................................................................................................................. 10
17. Security................................................................................................................................................. 10
18. Software Licensing............................................................................................................................... 10
19. Storage................................................................................................................................................. 11
20. Support and Administration................................................................................................................... 11
21. Timing and Cost.................................................................................................................................... 11
22. Volume and Expected Usage...............................................................................................................11
23. Additional Requirements....................................................................................................................... 11

Acceptance Criteria and Critical Success Factors..................................................................12


Assumptions............................................................................................................................... 13
Out of Scope............................................................................................................................................ 13

Constraints and Risks................................................................................................................ 14


Appendix A High Level Logical Architecture.........................................................................16
General Data-Flow Description................................................................................................................16

Version 1.0

GM/HP/EDS Confidential

1 October 2009 i

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard

This page is left intentionally blank.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 ii

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

Introduction
The purpose of this document is to describe the functional and technical requirements for the HP/EDS
Hosting Services WebLogic 9.2 Release build.
The intended audience for this document is the HP/EDS Hosting Services engineering team and its
customers.
This document details the requirements for the BEA WebLogic Server 9.2 (single or multiple instances with
or without session failover), WebLogic Server Express 9.2 (single or multiple instances).
WebLogic Server is a J2EE application server: a platform for developing and deploying multitier distributed
enterprise applications. WLS centralizes application services such as business components and access to
backend enterprise systems. It uses technologies such as caching and connection pooling to improve
resource use and application performance. WebLogic Server implements Java 2 Enterprise Edition 1.4
(J2EE), the Java Enterprise standard.
BEA WebLogic Server 9.2 is a tested and certified Java 2 Enterprise Edition (J2EE) 1.4 compliant
application server (see http://java.sun.com/j2ee/1.4/docs/index.html for more information on J2EE 1.4).
J2EE is a set of coordinated specifications and practices that together enable solutions for developing,
deploying, and managing multitier server-centric applications. The J2EE platform consists of application
components (such as servlets, Java Server Pages (JSPs) and EJBs), containers (which provide run-time
support for the components), resource manager drivers (which implement network connectivity to an
external resources such as legacy systems) and a database. J2EE also includes standard services which
include Hyper Text Transfer Protocol (HTTP), Secure Hyper Text Transfer Protocol (HTTPS), Java
Transaction Architecture (JTA), Java Message Service (JMS), Java Naming and Directory Interface (JNDI),
Java Connector Architecture (JCA), Internet Inter-ORB Protocol (IIOP), Java Authentication and
Authorization Service (JAAS), Java Database Connectivity (JDBC), Simple Object Access Protocol (SOAP),
Extensible Markup Language (XML), Universal Description Discovery and Integration (UDDI) and Web
Services Description Language (WSDL).

Contacts
This section of the Requirements Guide identifies the contacts for this project, their roles, their phone
numbers, their email addresses and their organization and company names.
Name
SreeLatha
Chalasani
Jessica Leja

Allen Scott
Oracle Support
Metalink
Dale Deloy

Role(s)
HP/EDS HS
WebLogic Lead
Engineer
HP/EDS HS
WebLogic Lead
Engineer
Middleware
Oracle Support
Oracle Support
Oracle Support

Organization /
Company

Phone
Number(s)

Mail Address

HP

(248) 364-5819

Sreelatha.chalasani@hp.co
m

HP

(248) 754-7767

jessica.leja@hp.com

(248) 997-8508
1800-633-0738

Scott.allen@hp.com

Oracle
Oracle
Oracle

metalink.oracle.com
dale.deloy@oracle.com

Scope / Proposed Solution


The overall objective and goal of this project is to provide a template for deploying, operating and
maintaining an HP/EDS HS WebLogic Server 9.2 build based on the General Motors WebLogic Server 9.2
Gold Build to most extent, however GBD is not followed entirely and an exception is made to the standard
directory structures. As dictated by the HP/EDS HS Program Office security patches and maintenance pack
upgrades will be deployed as separate projects in an effort to maintain this build, due to change in the

Version 1.0

GM/HP/EDS Confidential

1 October 2009 1

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

standard directory structures quarterly patching builds cannot be leveraged as is, custom patching builds are
needed, even manual patching instructions might not be used as is due to difference in directory structures.
This solution will utilize, as much as possible, the existing network and hardware components of the current
application server components. This solution will also be integrated into the HP/EDS HS infrastructure;
including the Oracle 11g database standard templates however this build does not include integration with
Web Server.
Information regarding migrating from the HP/EDS HS WebLogic 8.1 standard build to the HP/EDS HS
WebLogic 9.2 standard build will not included in the scope of this project.
The main WebLogic features/functions that will be engineered as part of this release are listed here. Other
WLS functions may work but will not be engineered or tested as part of this project:

Deploying WAR and/or EAR files.

Serving servlets, JSPs, and EJBs.

Using the Oracle 10g thin driver to connect to the Oracle RAC or HA backend database.

The capability for application owners, or their designates in the application development sustain
teams, to add/change/delete data sources to allow for connectivity to the Oracle environment.

This build has been designed to adhere with WLS GBD 9.2 definition with a limited scope. This build is
specific to HP-UX Itanium 11.23 standard build on which WebLogic server 9.2 mp 3 can be deployed. The
requirements for this project include integration of WLS 9.2 with service guard 11.18 above and beyond
WLS 9.2 build itself. If required this build can be used to install WLS into a non standard directory structure
(standard directory structure to install WLS 92 is /usr/local/bea/wls92 and domain specific logs etc are stored
under /sites). The non standard directory structure that can be accommodated with this build is only to be
able to prefix /usr/local/bea or /sites with some other directory only. For e.g.
/wlsapppkg/usr/local/bea/wls92, /wlsapppkg/sites. Also several standard features such as integration with
Web server (by using WebLogic Plug-in), migration, control tool etc are out of the scope of this build.
The following diagram displays the components that are considered in scope for this project, BEA WebLogic
Server and other components that will interact with it.

Figure 1: Architecture Diagram


The WLS Application Server, including administration consoles, managed server instances and Oracle
database connectivity configuration are considered in scope for this project. WebLogic plug-in and
integration with Web Server are out of scope.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 2

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

General Data-Flow Description


1.

Intranet (for example the GM Intranet, GMAC Intranet, OnStar network) and extranet application users
and Site Scope transaction monitors are expected to access applications through the Sun Java System
Web Server NES WLS Plug-in. Even though the current solution does not include Web Server and the
plug-in the data flow is still expected to be via a Web server. It is expected that application users, with
the exception of the deployer ID, will not access the WLS built-in web server directly.

2.

The Sun Java System Web Server will use the BEA WLS WebLogic NSAPI Proxy Plug-in to connect to
the WebLogic Server Managed Server Instances. And instructions to install and configure a plug-in are
part of integration with Web Server and they are out of scope.

3.

WebLogic will use the Oracle 10g thin driver to connect to the backend Oracle servers where required.

4.

Site Scope monitors should be configured to access the WebLogic Admin and managed server
instances directly.

5.

The HP/EDS HS Operations team, HP/EDS HS Engineering team and application owner, or their
designates in the application development sustain teams, on the Intranet (for example the GM Intranet,
GMAC Intranet, OnStar network) will have access to the WLS Admin Consoles.

Each web server (or set of Highly Available HA web servers) will/may connect to one WebLogic domain
which is out of scope of this build.
The application servers are meant to be dedicated for application server infrastructure (i.e. not shared with
web, database, etc) running in an Intranet environment (fire-walled off from the Internet).
Although BEA WebLogic Server 9.2 is supported on many different platforms (please see http://edocs.bea.com/platform/suppconfigs/configs92/92_over/overview.html for more detailed information). This
template supports HPUX 11.23 Itanium.

32 bit binaries and 32 bit JDK


This WLS92 mp 3 HPUX 11.23 build will use 32 bit binaries & 32 bit JDK.

Requirements
1. Functional
Sequence. Number

Requirement

HPUX

1.1

Adherence to WSL 9.2


gold build standards.

1.2

The WebLogic Server


9.2 deployment will be
accessible from the nonSSL and SSL HP/EDS
HS Standard Web
Servers on both the
Intranet and Extranet
and by other
applications located in
the hosting environment.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 3

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

1.3
1.3.1

Automated installation
scripts for
Web plug-in and
application server
pairs for a highly
available clustered
or non-clustered
configuration. The
binary install scripts
should validate
/usr/local, /var/tmp
and /sites disk space
requirements before
copying any files to
the server where WLS
is to be installed. The
binary install scripts
should also validate
the existence of
/usr/local, /var/tmp
and /sites before
copying any files to
the server where WLS
is to be installed and
exit with the proper
error message.

X (Plug-in is out of
scope)

1.3.1.1

One or more
physical web
servers (each
with 1 web
server instance
with the same
site shortname

Not in scope

1.3.1.2

One or more
physical
application
servers (each
with at least 1
Managed Server
instance with the
same site
shortname in the
same WebLogic
domain).

1.3.2

Adding web plug-in to


the highly available
clustered or nonclustered web server
configuration

Out of scope

1.3.3

The installation
scripts for the
WebLogic domain
and additional
instances should
allow for a separate

Version 1.0

GM/HP/EDS Confidential

1 October 2009 4

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

site specific
configuration file to
be passed to the
installation script
1.3.4

1.4
1.4.1
1.4.2
1.4.3

Automated installation
script for adding a
Managed Server
instance to either of the
existing clustered or
non-clustered
configurations.

WLS Admin Console


with ability to:

Promote code in ear


or war format.
View Log Files.
Create JDBC system
resources.

1.5

OpsWare Enabled
Binary Installation

To Be Delivered at a
later date

1.6

OpsWare Enabled
Domain Installation

To Be Delivered at a
later date

1.7

OpsWare Enabled
Additional Instance
Installation.

To Be Delivered at a
later date

1.8

OpsWare Enabled
Additional Instance
Installation

To Be Delivered at a
later date

1.9

OpsWare Enabled Web


Server Plug-in
Installation.

To Be Delivered at a
later date

1.10

Automated daily
application server log
roll-over.

1.11

Instructions for using the


installation scripts in an
environment where an
HP/EDS HS
Administration Server
does not exist.

1.13

Version 1.0

A sample application
that performs session
failover will be deployed
to every WLS managed
server in a cluster in an
effort to provide the
ability to troubleshoot or
test failover capabilities.

GM/HP/EDS Confidential

1 October 2009 5

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

1.14

1.15

1.16

1.18

WLS performance tuning


information will be
included in the
Operations Guide for
this project.
Where a WebLogic
domain is installed
across multiple physical
servers or zones
synchronization of the
administration instance
configuration files
between the first and
second server
(preferably on different
hardware) in a
WebLogic domain will
take place nightly.
Provide a separate
document that contains
deployment
prerequisites that can be
easily shared with
other capabilities such
as the SA team, storage,
etc.
Include instructions to
remove WLS directories
for a failed binary, site,
additional instance or
plug-in installation.

1.19

Include instructions to
remove WLS temporary
directories for a failed
binary or site installation.

1.20

Include a force cleanup


flag in the WLS binary,
site installation,
additional instance and
plug-in installations to
remove WLS temporary
directories for a failed
installation.

To Be Delivered at a
later date

1.21

The install scripts must


work with a temporary
installer ID (not phreak)
with temporary trust

1.22

Migration Enabling
WLS92 to reuse WLS 81
ports

Not in scope

1.23

Admin instance failover

Out of scope

Version 1.0

GM/HP/EDS Confidential

1 October 2009 6

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

1.24

2.2

Integration with service


guard 11.18 via manual
failover. This requires
WLS9.2 mp3 to be
installed
with
in
ServiceGuard package
file system

2. Administrative / Back-End Access


2.1

The WLS installation includes an administration server that can be accessed remotely via a browser
by the HP/EDS HS Operations Team, the Application Owner, or their designates in the application
development sustain teams, and the HP/EDS HS Engineering Team. This access will be over the
front-end network.

2.2

Access for the HP/EDS HS Operations Team, HP/EDS HS Engineers and Application Owners, or
their designates in the application development sustain teams, to review log files (current and
archived) and restart application server clusters are required to be provided via the Control Tool
where available.

2.3

Standard HP/EDS Hosting Services back end access should be implemented for use by the
HP/EDS Operations and Engineering teams.

3. Application Access
3.1

Control tool is not available for this build.

3.2

Access to the WebLogic Administration Console will be provided to allow Application Owners, or
their designates in the application development sustain teams on the Intranet (for example the GM
Intranet, GMAC Intranet, OnStar network) to , promote code (EAR & WAR files), create datasources
and review current days log files. HP/EDS HS Operations and Engineering also have this access
but generally do not perform these tasks.

3.3

SiteScope transaction monitors are required to be configured to act as a real application user to
monitor the availability of the site.

4. Application Testing
4.1

Application Testing requirements should be documented, by the engineer assigned to the project or
the application owner, or their designates in the application development sustain teams, on a project
by project basis. This is out of scope for this project.

4.2

A sample application will be deployed to all clustered and non-clustered installations of WebLogic.
This sample application will be used to determine if the infrastructure was successfully installed and
working initially and after any patches or service pack upgrades are applied in the environment.

4.3

The Test Guide for this project will contain installation of binaries, domains and additional instances.

4.4

Testing in the release environment will include failover testing using service guard.

5. Availability / Load Balancing


5.1

Load balancing can be done at the application server level.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 7

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

5.2

Failover between the application servers for the standard highly available clustered configuration is
required to be supported.

5.3

High availability (using only manual failover package) using service guard.

6. Backup and Restore


6.1

The standard HP/EDS HS backup and restore procedures is required to be used to backup and
restore /usr/local and /sites at a minimum on the application servers unless otherwise stated in project
specific Requirements Guides.

7. Batch Processes
7.1

Automated daily application server log roll-over.

8. Conflicting Requirements
8.1

WLS 92 is required to be integrated with service guard; however the failover is not dependent upon
the status of WLS process. The failover of the package will be performed manually or it also
happens when a node fails.

8.2

WLS 92 will not be installed in the standard directory structure as per GBD which is /usr/local/bea. It
will be installed under <serviceguard-package>/usr/local/bea with related directories under
<serviceguard-package>/sites , <serviceguard-package>/ usr/local/gwh.

8.3

Web server integration is out of scope for the build but the client intends to have web server
eventually on their own.

9. Control Tool
9.1

Control tool is not available

10. Disaster Recovery


10.1

Standard HP/EDS HS Disaster Recovery is required to be used (typically the pre-production site will
serve as the disaster recovery site for the production site.) unless otherwise specified in project
specific Requirements Guides.

11. Event Monitoring


11.1

All Preproduction and Production WLS Managed Servers should have a SiteScope transaction
monitor deployed that assists the HP/EDS HS Operations Team in determining what layer of the
application (app or database) requires troubleshooting or restarting. This monitor should be
configured according to the standard SiteScope monitoring processes and procedures.

11.2

All Preproduction and Production WLS Administration Servers should have a SiteScope monitor
deployed.

11.3

Each application should have its own infrastructure monitor therefore there will be no overall SLA
monitor for WebLogic.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 8

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

11.4

Provide an OpsWare ATE MAPL for WebLogic Server 9.2 Binaries is required.

12. Network
12.1

All application servers in a domain are required to reside on the same network subnet.

12.2

All application servers in a domain are required to share a multicast ip address and port that is
unique to that cluster.

13. Operating Environments


Environment for this Guide

Y/N

HP/EDS HS Development environment


HP/EDS HS Pre-production environment
HP/EDS HS Production environment

13.1

Y
Y
Y

The General Motors WebLogic Server 9.2 Gold Build Definition includes both Solaris 10 and HP-UX
11i v2.3 Enterprise (EOE) Operating Environment. This requirement guide is for WebLogic 9.2 and
HPUX 11.23 Itanium; however HPUX build has limited scope. This template supports BEA WebLogic
Server 9.2 deployments on HPUX 11.23 Itanium.

14. Operational Readiness


14.1

14.2

Access to the WebLogic Administration Console is required to allow Application Owners, or their
designates in the application development sustain teams on the Intranet (for example the GM
Intranet, GMAC Intranet, OnStar network) to promote code (EAR & WAR files), create datasources
and review current days log files. HP/EDS HS Operations and Engineering also have this access
but generally do not perform these tasks.
The following is a list of some of the information that will be delivered in the Operations Guide for
this project. Please note, this is not intended to be an all-inclusive list:

Installation Instructions

De-Installation Instructions

How to Configure Oracle Connectivity, including usage of connect on reserve feature for HA if
necessary. Whether this feature is required for the WLS 9.2 to Oracle 11g configuration will be
determined during the design phase of this project

How to Update License Files

How to Start and Stop WLS Administration and Managed Servers

How to Deploy Applications

How to change the password

How to test functionality with a sample application

General Cluster Configuration Information

The amount of available disk and memory required to install WebLogic Server 9.2 Binaries

Version 1.0

GM/HP/EDS Confidential

1 October 2009 9

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

15. Remote Access


Remote Access Requirements
Type of Remote
Access

Security Level
Required

15.1

WLS
Administrati
on Console

Deployer

To allow application owners, or


their designates in the
application development
sustain teams, to deploy
ear/war files and create
connection pools and / or
datasources.

WLS Embedded LDAP ID

15.2

WLS
Administrati
on Console

Administrator

To allow system administrators


access to troubleshoot the
environment and make any
required configuration
changes.

WLS Embedded LDAP ID

15.3

WLS
Administrati
on Console

Monitor

To allow HP/EDS HS
Engineers access to
troubleshoot the environment.

WLS Embedded LDAP ID

Purpose

Description

16. Reporting
16.1

The WebLogic Admin Console can be used, by Application Owners or their designates in the
application development sustain teams, HP/EDS HS Engineers and the HP/EDS Operations team
on the GM or HP/EDS Network, to view real time statistics.

17. Security
17.1

The BEA WebLogic Administration Consoles are required to be secured with SSL. The General
Motors WebLogic Server 9.2 Gold Build requires use of the WebLogic Administration Port to provide
this functionality. Since this template/build must meet the requirements of the Gold Build the
Administration Port will be used in this build as well.

17.2

Application Owners, or their designates in the application development sustain teams, on the
Intranet (for example the GM Intranet, GMAC Intranet, OnStar network) require "Deployer" level
access to the WLS Administration Console to deploy their application code and database
datasources.

17.3

Each sites specific files and application code are required to be secured using standard UNIX user
and group id security.

17.4

The WebLogic template should not deploy any files that include clear text passwords.

17.5

ISP&P checklist and BEA TSS checklist neHP/EDS to be completed after running the scans.
However in GME there is no deviation process. TSS checklist for WLS can be found at
http://infosecurity.gm.com/tech/gcts/infosecurity/technical_services/index.html

Version 1.0

GM/HP/EDS Confidential

1 October 2009 10

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

18. Software Licensing


18.1

Software Licensing is the responsibility of the HP/EDS HS Program Office or the Application Owner.

19. Storage
19.1

HP/EDS HS standard Storage Area Network will be used for this project. If an application is required
to share files across multiple zones then the use of NAS is allowed but WLS binaries and the /sites
directory cannot be shared. Portions of the /sites directory that WebLogic is not deployed on can be
used for example /sites/shortname/site/common/<app specific dir>.

19.2

WLS may/may not be installed into a service guard package. If it is being installed into a service
guard package then there is a shared file system required. And an at least 1GB of space is required
for WebLogic binaries and 100MB of additional space is required for each managed server there
after. However since sites directory will also be under service guard package file system
application requirements should be taken into consideration for storage requirements.

20. Support and Administration


20.1

This project will use the standard offerings for support and administration.

20.2

The Operations Guide for this project will include:

20.2.1

Standard/recommended JAVA OPTIONS

20.2.2

A list of files deployed that contain an encrypted password (clear text passwords are not allowed
to be deployed)

20.2.3

A list of files that can or must not be shared with the application development team

20.2.4

Instructions for using the installation scripts in an environment where an HP/EDS HS


Administration Server does not exist

20.2.5

A recommendation for location of standard startup and shutdown classes

20.2.6

The location of patch files

21. Timing and Cost


21.1

The HPUX 11.23 binaries are expected to be installed in HP/EDS HS pre production environment
before December 2009.

22. Volume and Expected Usage


22.1

Volume and Expected Usage will be determined by the individual projects using this template.

23. Additional Requirements


23.1

There are no known additional requirements.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 11

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

Acceptance Criteria and Critical


Success Factors
Access to the WebLogic Administration Console is required to allow Application Owners, or their designates
in the application development sustain teams on the Intranet (for example the GM Intranet, GMAC Intranet,
OnStar network) to promote code (EAR & WAR files), create datasources and review current days log files.
HP/EDS HS Operations and Engineering also have this access but generally do not perform these tasks.
If necessary, updates to the HP/EDS HS Infrastructure and Application Standards Guide will be a deliverable
of this project.
All requirements in this guide are met, documented in the Operations Guide if necessary and documented
and successfully tested in the Test Guide if necessary.
The deployment scripts execute successfully.
The following is a list of some of the information that will be delivered in the Operations Guide for this
project. Please note, this is not intended to be an all-inclusive list:
Installation Instructions
How to Configure the Control Tool for WebLogic Server 9.2
De-Installation Instructions
How to Configure Oracle Connectivity
How to Update License Files
How to Start and Stop WebLogic Server Administration and Managed Servers
How to Deploy Applications to WebLogic Server
General Cluster Configuration Information
General WebLogic Server Troubleshooting Information
The Operations Guide for this project is reviewed, approved by the HP/EDS Operations team and published
to the Administration Web Site (http://admin.gweb.HP/EDS.com).
Binary and Site installation scripts are made available.
The Test Guide for this project will contain failover and high availability tests for the installing WLS 92
binaries, domains and adding additional instances.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 12

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

Assumptions

This template supports Java Applications, not iPlanet Application Server Applogics, C or CORBA
applications.

WLS will be monitored using SiteScope monitors and Serviceguard functionality will not include
monitoring of WLS process. The failover of Serviceguard package that contains WLS will be failed over
manually or only when the node fails.

The start and stop scripts provided by the WLS build will be used. Required permissions to use these
scripts will be provided. Since control tool is not available this is the only way start, stop and restarts can
happen. However delegating these permissions might be against to TSS compliance.

Security compliance deviations are out of scope of this project and it is presumed that any such
deviations will be responsibility of application team utilizing this build.

This build will be designed to be identical to existing standard Solaris 92 build. But there are many items
that are out scope of this build and in those cases this build will differ from Solaris 92 build. This build
has limited functionality as compared to the WLS92 GBD. When completed this build could be
leveraged by several applications where ever the limitations of this build are not an issue. Essentially
this build is not a point build entirely nor a standard build.

WebLogic is monitored via Site Scope and not by service guard.

Out of Scope
Any specific configuration required for the following are not included in this project. If any of these are
required for a project they will need to be reviewed by an engineer before being approved to be deployed
into the environment and the application owner, or their designates in the application development sustain
teams, will be responsible for any deployment instructions unless engineering has been engaged to do so.

Integration with Sun One or Java System Web Server version.

Integration with any Oracle version other than 11g. 10g driver will also be provided but 11g will be
configured with the build. If 10g needs to be used then the CLASSPATH etc will have to be
changed and those instructions will be provided in the operations guide. However 11g driver is
backward compatible.

The BEA Binary installation provides a database driver to connect to DB2 databases. If necessary
application teams can use this driver but HP/EDS HS will not validate or test functionality of this
driver

A solution for load balancing and/or routing requests directly to the application servers from an end
user

SiteScope and Wily Introscope design, configuration, installation, maintenance and support

Control Tool availability

Migration from WLS 81

Admin instance failover

Java Messaging Service (JMS)

Java Authentication and Authorization Service API (JAAS)

WebLogic Virtual Servers

Version 1.0

GM/HP/EDS Confidential

1 October 2009 13

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

Simple Network Monitoring Protocol (SNMP) capabilities

Mail

Tuxedo

Messaging Bridges (Bridges, JMS Bridge Destinations and General Bridge Destinations)

XML Registries

File T3 (high-speed, client-side access to native operating system files on the server using the
client API to extend the capabilities of java.io.InputSream and java.io.OutputStream)

Network Channels

Support for web services

Continental service guard engineering solution


Integration with service guard other than manual failover approach. WLS will not be monitored and
failover does not happen depending upon the status of WLS process. Instead the package can be
failed over manually or when the node fails.

Creating and maintaining users, groups, permissions, security policies (access control lists) and
roles in the WLS environment

Node Manager

Java Transaction Application Programming Interface API (JTA)

Java Cryptography Architecture (JCA)

The Design and Operations Guides will not include instructions or detail regarding how WebLogic
Server (WLS), infrastructure or applications should be configured to allow the use of Remote
Method Invocation (RMI), RMI over Internet Inter Object Request Broker (ORB) Protocol
(RMI/IIOP), Common Object Request Broker Architecture (CORBA) or Java Common Object Model
(JCOM), Simple Object Access Protocol (SOAP), Universal Description, Discovery and Integration
(UDDI) or Web Services Description Language (WSDL) to connect to the application servers.
Applications requiring this type of access will require additional engineering to make any specific
configuration changes, or firewall rules

Other services and-or drivers not mentioned here

Any WebLogic-provided drivers other then the Oracle 10g driver included in the WLS 9.2
installation

Constraints and Risks

Additional application server binaries may be installed on the same physical web and application
servers as the initial binary installation, although BEA does not recommend doing so.

All WLS instances in a cluster and domain must reside on the same network subnet. Although BEA
documentation states this is not a constraint of the product any longer it is a constraint in the General
Motors WebLogic Server 9.2 Gold Build and if necessary for a project will likely require additional
engineering to implement.

Machines used to host WLS domains must have permanently assigned IP addresses.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 14

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

All servers in a domain must run the same version of WLS. WLS clustered deployments must have a
clustering license from BEA.

Support of the actual migration of sites from one version of WebLogic to another will not be included in
this project.

WebLogic 9.2 will not be integrated with Sun One Web Server 6.0 or Oracle 9i as part of this project.
Due to change in the standard directory structure automatic patching delivered by HP/EDS hosting
quarterly cannot be utilized, custom patching will be needed every quarter.
Any customizations made after the build is deployed can pose implications to patching and if this is
done even custom patching may not be applicable. For example after deploying WLS HPUX 11.23
build, if Node Manager is installed and configured manually over the build custom patching may not
work. This is because custom patching will only take the change in directory structure into consideration
and not the addition of Node manager.

Version 1.0

GM/HP/EDS Confidential

1 October 2009 15

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

Appendix A High Level Logical


Architecture
For HPUX (current build scope)

Figure 2: Architecture Diagram


Application users are expected to access their applications through the Sun Java System Web Server and
WLS Proxy Plug-in which is not in scope for this build. It is not expected that application users will access
the WLS built-in web server directly.
The WebLogic Web Server Plug-in is not in scope for this build but WLS Application Server, including
Administration Consoles, Managed Server Instances and the Database Connectivity Configuration are
considered in scope for this project.

General Data-Flow Description


WebLogic Server Data Flow for HPUX:

Version 1.0

GM/HP/EDS Confidential

1 October 2009 16

Requirements Guide
HP/HP/EDS HS WebLogic Server 9.2 (WLS 9.2) on HPUX 11iv23 Itanium with Serviceguard
R EQUIREMENTS

1.

Internal and External application users and monitoring tools are expected to access applications
through the Sun Java System Web Server/WLS Plug-in which is not in scope for this build. It is not
expected that application users will access the WLS built-in web server directly.

2.

The Sun Java System Web Server will use the BEA WLS WebLogic NSAPI Proxy Plug-in to connect to
the WebLogic Server Managed Server Instances which is not in scope for this build.

3.

WebLogic will use the Oracle thin driver to connect to the backend Oracle servers where required.

4.

The hosting supplier will have access to the WLS Admin Consoles.

5.

Each web server (or set of Highly Available HA web servers) will connect to one WebLogic domain.

The application servers are meant to be dedicated for application server infrastructure (i.e. not shared with
web, database, etc) running in an Intranet environment (fire-walled off from the Internet)

Version 1.0

GM/HP/EDS Confidential

1 October 2009 17