EDS Hosting Services

WebWerks

Requirements Guide

EDS HS WebLogic Server 9.2 (WLS 9.2)

Template
Version 1.2

17 March 2009

GM/EDS Confidential

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

Change History
This document complies with the requirements of Content Standards for Requirements, version 3.07,
effective 27 Feb 2006. 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 #

21 May2007

1.0

27 June 2007

1.1

17 March 2009

1.2

Document
Owner

Section / Nature of Change

Jessica Leja
EDS HS
Engineering
248-370-1618
jessica.leja@e
ds.com
Same as
above
same

Created Document

Updated based on TRB feedback

Updated Contacts section of guide, removed BEA
support information. Added Oracle support information
and SJSWS Engineer information.

Statement of Confidentiality
This document contains information that is confidential and proprietary to 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 EDS Legal department. Information can only be disclosed, duplicated, or otherwise
used in accordance with the nondisclosure agreement with EDS. Additionally, this information shall be limited to EDS and
GM persons having a need to know.
EDS is a registered mark, and the EDS logo is a trademark, of Electronic Data Systems Corporation. 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.1

GM/EDS Confidential

27 June 2007

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

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

Requirements................................................................................................................................ 4
1.

Functional............................................................................................................................................... 4

2.

Administrative / Back-End Access..........................................................................................................4

3.

Application Access................................................................................................................................. 5

4.

Application Testing.................................................................................................................................. 5

5.

Availability / Load Balancing...................................................................................................................5

6.

Backup and Restore............................................................................................................................... 6

7.

Batch Processes.................................................................................................................................... 6

8.

Conflicting Requirements....................................................................................................................... 6

9.

Control Tool............................................................................................................................................ 6

10. Disaster Recovery.................................................................................................................................. 6

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

Acceptance Criteria and Critical Success Factors..................................................................10

Assumptions............................................................................................................................... 11
Out of Scope............................................................................................................................................ 11

Constraints and Risks................................................................................................................ 12

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

Version 1.2

GM/EDS Confidential

17 March 2009 i

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

This page is left intentionally blank.

Version 1.2

GM/EDS Confidential

17 March 2009 ii

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

Introduction
The purpose of this document is to describe the functional and technical requirements for the EDS Hosting
Services WebLogic 9.2 Release build.
The intended audience for this document is the 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), and the WebLogic
NES* Proxy Plug-In products.
*BEA refers to the Proxy Plug-In for use with SUN Java System Web Server as the NES (Netscape
Enterprise Server) Proxy Plug-In.
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
Tim Marvin

Mark Shecter
Beth Van Egeren
Sheila Jakel

Jessica Leja
Yona
Shaposhnik
Oracle Support
Metalink

Version 1.2

Role(s)
General Motors Gold
Build Definition
Owner
EDS HS Program
Manager / Customer
EDS HS Architect
EDS HS Service
Line Project
Manager
EDS HS WebLogic
Lead Engineer
EDS HS Sun Java
System Web Server
Engineer
Oracle Support
Oracle Support

Organization /
Company

Phone
Number(s)

General Motors

(313) 667-4775

tim.marvin@gm.cot

EDS

(248) 364-5835

mark.shecter@eds.com

EDS
EDS

(248) 364-5849
(248) 754-2402

beth.vanegeren@eds.com
sheila.jakel@eds.com

EDS

(248) 370-1618

jessica.leja@eds.com

EDS

1-800-633-0738

Oracle
Oracle

(248) 364-5539

GM/EDS Confidential

Mail Address

yona.shaposhnik@eds.com
metalink.oracle.com

17 March 2009 1

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

Name
Dale Deloy

Role(s)
Oracle Support

I NTRODUCTION

Organization /
Company
Oracle

Phone
Number(s)
n/a

Mail Address
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 EDS HS WebLogic Server 9.2 build based on the General Motors WebLogic Server 9.2 Gold
Build. As dictated by the EDS HS Program Office security patches and maintenance pack upgrades will be
deployed as separate projects in an effort to maintain this build.
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 EDS HS infrastructure,
including the Sun Java System Web Server 6.1 and Oracle 10g database standard templates.
Information regarding migrating from the EDS HS WebLogic 8.1 standard build to the EDS HS WebLogic 9.2
standard build will be included in the scope of this project. For applications migrating from WLS 8.1 to WLS
9.2 it is likely application testing and possible application code changes will be required.
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.

The strategic direction for WebLogic Server at General Motors is Sun Solaris, specifically the GM Global
Sun Solaris 10 Zone Build. The Design and Operations Guide for this project will contain a statement similar
to the following: Any project that wants to deviate from deploying WebLogic on the GM Global Sun Solaris
10 Zone Build should first get approval from Mike Fitzgerel and/or Mark Hillman from General Motors. If that
approval is granted then the project will be responsible for any additional one-time changes to the template
for use on non GM Global Sun Solaris 10 Zone Build deployments and any additional on-going support
required.
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.

Version 1.2

GM/EDS Confidential

17 March 2009 2

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

Figure 1: Architecture Diagram

The NES WebLogic Plugin and WLS Application Server, including administration consoles, managed server
instances and Oracle database connectivity configuration are considered in scope for this project.

General Data-Flow Description

1.

Intranet (for example the GM Intranet, GMAC Intranet, OnStar network) and Extranet application users
and SiteScope transaction monitors are expected to access applications through the Sun Java System
Web Server NES WLS Plug-in. 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 Plugin to connect to
the WebLogic Server Managed Server Instances.

3.

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

4.

SiteScope and/or Wily Introscope monitors should be configured to access the WebLogic Admin and
managed server instances directly. A separate project exists to determine whether Wily Introscope can
or should be used to monitor. The use of Wily is not a requirement of the WLS 9.2 template project but
is noted here for informational purposes only at this time.

5.

The EDS HS Operations team, 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 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).
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 BEA WebLogic Server 9.2 deployments on Sun Solaris 10 SPARC sparse and/or full-root
(whole root) zones. Sun Solaris 10 SPARC Global Zones are allowed for use ONLY when the server is
dedicated to the application or application group and no other zones are hosted on the server. Instructions

Version 1.2

GM/EDS Confidential

17 March 2009 3

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

for installing WebLogic are not different when installing in a GM Global Build Solaris 10 SPARC global zone
vs. a full root or sparse zone.

Requirements
1. Functional
1.1

The EDS HS WebLogic Server 9.2 Template must adhere to the General Motors WebLogic Server
9.2 Gold Build Definition.

1.2

The WebLogic Server 9.2 deployment will be accessible from the non-SSL and SSL EDS HS
Standard Web Servers on both the Intranet and Extranet.

1.3

Automated installation scripts for:

1.3.1

Web plugin and application server pairs for a highly available clustered or non-clustered
configuration:

1.3.1.1 One or more physical web servers (each with 1 web server instance with the same site
shortname).
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 plugin to the highly available clustered or non-clustered configuration.

1.3.3

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

1.4

WLS Admin Console with ability to:

1.4.1

Promote code in ear or war format.

1.4.2

Add/Change/Delete database datasources.

1.4.3

View Log Files.

1.5
1.6
1.7
1.8

Instructions for using the installation scripts in an environment where an EDS HS Administration
Server does not exist.
Automated daily application server log roll-over.
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.
WLS performance tuning information will be included in the Operations Guide for this project.

1.9

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 in a WebLogic
domain will take place nightly.

1.10

Where a WebLogic domain is installed across multiple physical servers or zones provide an
administration instance configuration file synchronization validation process.

Version 1.2

GM/EDS Confidential

17 March 2009 4

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

2. Administrative / Back-End Access

2.1

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

2.2

Access for the EDS HS Operations Team, 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 EDS Hosting Services back end access should be implemented for use by the EDS
Operations and Engineering teams.

3. Application Access
3.1

Where available a Control Tool will be provided to allow the EDS HS Operations and Engineering
teams and Application Owners, or their designates in the application development sustain teams, on
the Intranet (for example the GM Intranet, GMAC Intranet, OnStar network) to review log files and
restart application server managed server instances.

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. EDS HS Operations and Engineering also have this access but
generally do not perform these tasks.

3.3

All application user access to WebLogic should be via the front-end Sun Java System Web Server.

3.4

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 failover and high availability tests for the WLS
infrastructure and its integration with Sun Java System Web Server and Oracle.

5. Availability / Load Balancing

5.1

Load balancing between the Managed Server instances in the cluster is required to be done via the
WebLogic load sharing internal routine encoded in the WebLogic Proxy Plugin.

5.2

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

5.3

Per BEA service pack upgrades for WebLogic 9.2 cannot be applied in high availability mode at this
time (case # 722284 on May 22, 2007).

Version 1.2

GM/EDS Confidential

17 March 2009 5

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

6. Backup and Restore

6.1

The standard 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

7.2

Automated daily application server log roll-over.

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 in a WebLogic
domain is required to take place nightly.

8. Conflicting Requirements
8.1

There are no known conflicting requirements.

9. Control Tool
9.1

Where available the Control Tool with ability to restart managed server instances, perform thread
dumps on managed server instances and view log files is required.

10. Disaster Recovery

10.1

Standard 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

Monitoring of the infrastructure should make use of a web page that executes a transaction through
the Sun Java System Web Server, WLS application server and the Oracle backend database. This
transaction is intended to be part of the application itself. All Preproduction and Production WLS
Managed Servers should have a SiteScope transaction monitor deployed that assists the EDS HS
Operations Team in determining what layer of the application (web, 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.

11.4

A separate project to engineer Wily Introscope monitors for WebLogic exists. The details of this
solution are not finalized as of the writing of this document. For details on the Wily Introscope
solution please reference the Requirements, Design and Operations Guide for that project.

11.5

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

Version 1.2

GM/EDS Confidential

17 March 2009 6

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

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
EDS HS Development environment
EDS HS Pre-production environment
EDS HS Production environment

13.1

Y/N
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 Solaris 10 WebLogic
9.2 only. An HP-UX WebLogic template may be added to this project or may become a separate
project at a later date. This template supports BEA WebLogic Server 9.2 deployments on Sun Solaris
10 SPARC sparse and/or full-root (whole root) zones. Sun Solaris 10 SPARC Global Zones are
allowed for use ONLY when the server is dedicated to the application or application group and no
other zones are hosted on the server. Instructions for installing WebLogic are not different when
installing in an EDS HS standard Solaris 10 SPARC Global Zone vs. a Full Root or Sparse Zone.

14. Operational Readiness

14.1

14.2

14.3

Where available a Control Tool is required be provided to allow the EDS HS Operations and
Engineering teams and Application Owners, or their designates in the application development
sustain teams, on the Intranet (for example the GM Intranet, GMAC Intranet, OnStar network) to
review log files and restart application server managed server instances.
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. 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 10g 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

Version 1.2

GM/EDS Confidential

17 March 2009 7

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

General Cluster Configuration Information

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

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 EDS HS Engineers

access to troubleshoot the
environment.

WLS Embedded LDAP ID

Purpose

Description

16. Reporting
16.1

Existing application Central Processing Unit (CPU) utilization routines and processes will be
integrated into and tested with the WLS build.

16.2

The WebLogic Admin Console can be used, by Application Owners or their designates in the
application development sustain teams, EDS HS Engineers and the EDS Operations team on the
GM or 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

A "view only" id is required for use by the EDS HS Engineering team for viewing the WLS domain
configuration via the WLS Administration Console.

17.4

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

17.5

The EDS HS Control tool and WLS deployment scripts is required to use ssh or secure agent (for
example, SSH is currently used on the GM Control Tool and an agent is used on the GMAC Control
Tool).

Version 1.2

GM/EDS Confidential

17 March 2009 8

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

17.6

Firewall rules are required between the Extranet Sun Java System Web Servers and the Intranet
WebLogic Servers. New firewall rules will be required for any new Sun Java System Web Servers
or dedicated WebLogic Servers as they are deployed in the environment.

17.7

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

18. Software Licensing

18.1

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

19. Storage
19.1

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

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 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 WLS 9.2 binaries are expected to be installed in the EDS HS Development Environment on the
shared application servers in early August 2007.

21.2

The WLS 9.2 binaries are expected to be installed in the EDS HS Pre-Production Environment on the
shared application servers in mid-August 2007.

21.3

The WLS 9.2 binaries are expected to be installed in the EDS HS Production Environment on the
shared application servers in late August 2007.

22. Volume and Expected Usage

22.1

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

Version 1.2

GM/EDS Confidential

17 March 2009 9

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

23. Additional Requirements

23.1

There are no known additional requirements.

Version 1.2

GM/EDS Confidential

17 March 2009 10

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

Acceptance Criteria and Critical

Success Factors
Where available a Control Tool is required to allow the EDS HS Operations and Engineering teams and
Application Owners, or their designates in the application development sustain teams, on the Intranet (for
example the GM Intranet, GMAC Intranet, OnStar network) to review log files and restart application server
managed server instances.
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.
EDS HS Operations and Engineering also have this access but generally do not perform these tasks.
If necessary, updates to the 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 EDS Operations team and published to
the Administration Web Site (http://admin.gweb.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 WLS infrastructure and
its integration with Sun Java System Web Server and Oracle.

Version 1.2

GM/EDS Confidential

17 March 2009 11

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

Assumptions

The scripted installation will allow shared web servers to access dedicated application servers.

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

A separate project exists to determine whether Wily Introscope can or should be used to monitor
WebLogic Server. The use of Wily is not a requirement of the WLS 9.2 template project but is noted
here for informational purposes only at this time.

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 other than 6.1

Integration with any Oracle version other than 10g

The BEA Binary installation provides a database driver to connect to DB2 databases. If necessary
application teams can use this driver but 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 will not have the capability to backout application versions

Java Messaging Service (JMS)

Java Authentication and Authorization Service API (JAAS)

WebLogic Virtual Servers

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

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

Node Manager

Version 1.2

GM/EDS Confidential

17 March 2009 12

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

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

A web server instance for a specific site can not connect to multiple clusters of application servers. For
example, the einventory web server can not connect to both the einventory and rims application servers
clusters.

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.

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.

Version 1.2

GM/EDS Confidential

17 March 2009 13

Requirements Guide
EDS HS WebLogic Server 9.2 (WLS 9.2) Template

I NTRODUCTION

Appendix A High Level Logical

Architecture

Figure 2: Architecture Diagram

Application users are expected to access their applications through the Sun Java System Web Server and
WLS Proxy Plugin. It is not expected that application users will access the WLS built-in web server directly.
The WebLogic Web Server Plugin and 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

1.

Internal and External application users and monitoring tools are expected to access applications
through the Sun Java System Web Server/WLS Plug-in. 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 Plugin to connect to
the WebLogic Server Managed Server Instances.

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.2

GM/EDS Confidential

17 March 2009 14