Configuring WebSphere Process Server Version 7.

0
for a Clustered Environment

A step by step guide including Business Process Choregrapher,

Business Space and IBM HTTP Server based on Linux and Oracle 11g

April 2010
© IBM Corporation, 2010

This edition applies to Version 7.0 of WebSphere Process Server including

the Business Space and the IBM HTTP Server.
 Disclaimer
This document is subject to change without notification and will not comprehensively
cover the issues encountered in any customer situation.

The information contained in this document has not been submitted to any formal IBM
test and is distributed AS IS.

For updates or newer releases please contact the service team.

The Team of Authors

This document is produced by the Business Process Choreographer team in Böblingen.

Michael Mann
IT Senior Specialist
WSS Business Process Solutions Test
IBM Software Group, Application and Integration Middleware Software,
Eduard Welte
Advisory IT Architect / Managing Consultant
IBM Software Group, Application and Integration Middleware Software
Wolfgang Steven
Advisory IT Architect / Managing Consultant
IBM Global Business Services, Enterprise Application Services
Marco Lezajic
IT Specialist
WebSphere BPM Suite Integration Quality Assurance Test
IBM Software Group, Application and Integration Middleware Software
Ekkehard Voesch
Business Process Management Test Architect
WebSphere BPM Suite Integration Quality Assurance Test
IBM Software Group, Application and Integration Middleware Software

Thanks for the contributions of the Business Process Choreographer test team and the
WSS BPM competence center.

i
 Preface
Scope
This document contains an overview of the tasks required for setting up a production
environment of a Business Process Management solution with a main focus on
WebSphere Process Server and in particular the Business Process Choreographer.
Additional Business Process Management components or products will be taken into
consideration, especially if interactions with the Process Choreographer are of interest.

This document introduces the topology of the chosen production environment and
describes the different tasks with a series of click-by-click instructions including the
installation, configuration and a verification for each main step.

The information provided in this document is related to a production environment

with several hosts and clusters. Please notice that a single server setup will be
significant less complex in terms of the WebSphere topology. Also the overall setup
of a remote database system is much more complex in production environment
than in a single server setup where a local database system might be used.

WebSphere Business Space and IBM HTTP Server might be added as optional
components to this production environment. They are part of the same cell and
represented in different, additional clusters or servers. IBM HTTP Server is required
for request distribution into cluster members. The related chapters can be skipped
if these components or products are not needed.

The installation and configuration of additional Business Process Management

components or products is not part of this documentation, but might be added in a
later version of this document.

The general concepts for building cells and clusters apply to the different releases,
but several details might have been added or changed between the different
releases. To make reading and understanding easier this document is related to
the following explicit releases:

• WebSphere Process Server V 7.0 (including Business Space)

• Oracle 11g Release 1 (11.1.0.6.0)
• IBM Tivoli Directory Server V 6.1

The used operating system for this documented setup is Red Hat Enterprise Linux.
In general other operating systems especially UNIX based systems will operate in
a similar way. From a configuration point of view there will be only minor
differences, for example the default path names might be different.

ii
Additional document sources being of interest

IBM WebSphere Business Process Management Version 7.0 information center

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp

Especially the sections for the following products are of interest

 IBM WebSphere Process Server 7.0

IBM Redbooks
http://www.redbooks.ibm.com/

There are numerous publications available for WebSphere Business Process

Management from which the following are of interest

• WebSphere Application Server V7 Administration and Configuration Guide

(SG24-7615)

• WebSphere Application Server V7: Administration Consoles and Commands

(REDP-4573)

• WebSphere Application Server V7: Concepts, Planning and Design

(SG24-7708)

• WebSphere Application Server V6.1: System Management and

Configuration (SG24-7304)

• WebSphere Application Server V6 System Management & Configuration

Handbook (SG24-6451)

• WebSphere Application Server Network Deployment V6: High Availability

Solutions (SG24-6688)

• WebSphere Business Process Management V6.2 Production Topologies

(SG24-7732)

• WebSphere Business Process Management V7.0 Production Topologies

(SG24-7831)
Note: This Redbook was as Draft available when this paper was published

iii
Summary of changes
This document is a logical successor of the document
WebSphere Process Server Version 6.2.0 Configuring The Process Choreographer
And Other BPM Components In A Clustered Environment
which can be found at
http://www-01.ibm.com/support/docview.wss?rs=2307&uid=swg27015273

The main differences or changes are:

• The Deployment Environment approach has been used instead of the

manual cluster creation.
• The transaction and compensation logs are configured on a shared network
drive, which is mandatory for an high availability setup.
• Due to changes in the WebSphere Process Server there is no longer a need
of manual changing the Oracle JDBC driver. The correct Oracle Java 1.6
driver is used from the beginning.
• The configuration of the RestService (MashupEndpoints/Custom Properties
instead of Proxy) is changed.
• For creating the necessary database scripts the new introduced
DBDesignGenerator is used.

iv
 Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries, or
both. These and other IBM trademarked terms are marked on their first occurrence in
this information with the appropriate symbol (® or ™), indicating US registered or
common law trademarks owned by IBM at the time this information was published.
Such trademarks may also be registered or common law trademarks in other
countries.
A current list of IBM trademarks is available on the Web at
http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines

Corporation in the United States, other countries, or both:

AIX® IMS™
AlphaBlox® Lotus®
alphaWorks® Redbooks®
DataPower® Redbooks (logo) ®
DB2 Universal Database™ Tivoli®
DB2® WebSphere®
developerWorks® Workplace™
HACMP™ Workplace Messaging®
IBM® z/OS®

v
 Trademarks

The following terms are trademarks of other companies:

Snapshot, and the NetApp logo are trademarks or registered trademarks of NetApp,
Inc. in the U.S. and other countries.
SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the
United States and other countries.
Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of
Oracle Corporation and/or its affiliates.
SAP NetWeaver, SAP, and SAP logos are trademarks or registered trademarks of SAP
AG in Germany and in several other countries.
EJB, Enterprise JavaBeans, J2EE, Java, JavaBeans, JavaServer, JDBC, JMX, JSP, JVM,
and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in
the United States, other countries, or both.
Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States,
other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of
others.

vi
 How to read this document
The intention of this document is to provide information which might be used to
facilitate the setup of a production environment. To get a better understanding further
documentation might be referenced.

This document contains numerous illustrations being formatted as follows.

• Graphical interactions
Typical interactions with the system are performed on screen (or panels) and a
description how to interact is much easier if pictures are used as outlined here

Title of the screen

1. Special related instructions – maybe several items are available.

They are marked with correspondend green bulleted numbers.
In addition sometimes related areas are marked with green rounded
rectangle.
2. The final instruction, e.g. press the Unpack button, is typically not
highlighted.

vii
• Interaction via the console
Mostly two types are of interest, one for the input requested on a console
window sometimes mentioned as command line input and a second for the
output provided on the console.
Console input (sometimes mentioned as command line input)

Console output
This might be several rows
In case of large lists important aspects are highlighted in this way

• Listings
Whenever a list of parameters is necessary to be discussed they will look like
this. Also file content will be formatted in this way. In case of large lists
highlighting might be added to put the focus on the major aspects.

Parameter1 = value1
Parameter2 = value2
Parameter3 = string1
etc

• Hyperlinks
For making it easier to find references hyperlinks are used and formatted like
the following link which leads to the IBM Redbooks homepage
http://www.redbooks.ibm.com/

• Notices
To emphasize information two types of formatted notices are used

Standard notice – typically used

Importand notice – used in special cases

viii
Table of Contents
Chapter 1 Introduction....................................................................................2
1.1 Planing the cell and cluster setup primer.....................................................3
1.1.1 Assign WebSphere components to the systems......................................3
1.1.2 Install the operating system and the prerequisites..................................4
1.1.3 Select the type of user directory for the cell...........................................4
1.1.4 Get the software packages..................................................................4
1.1.5 Summarize the values used during installation .....................................5
1.2 Planning the cell and cluster setup .............................................................6
1.2.1 Major components of a cell..................................................................6
1.2.2 WebSphere Process Server .................................................................8
1.2.3 WebSphere Business Monitor...............................................................8
1.2.4 Assign the cell and cluster components to the systems ...........................9
Chapter 2 Prerequisites and operating system installation...................................13
2.1 Install operating system..........................................................................13
2.2 Time server setup..................................................................................14
2.3 Select the type of user directory...............................................................15
2.4 Software packages.................................................................................15
2.5 Installation properties ............................................................................17
2.5.1 User IDs.........................................................................................17
2.5.2 Directory locations............................................................................17
2.5.3 Hostnames of the involved systems....................................................18
2.5.4 Naming of cluster components...........................................................18
Chapter 3 WebSphere Process Server cluster installation and configuration...........19
3.1 WebSphere Process Server cluster installation and configuration primer.........19
3.2 Installing WebSphere Process Server binaries ............................................19
3.3 Installing the Update Installer..................................................................30
3.4 Installing mandatory fixes........................................................................37
3.4.1 Install WAS mandatory iFixes.............................................................37
3.4.2 Install WPS mandatory iFixes.............................................................44
3.4.3 Install WPS Fix Pack 1.......................................................................54
3.5 Verify WebSphere Process Server binary installation....................................67
Chapter 4 Oracle binary installation.................................................................70
4.1 Oracle installation prerequisites................................................................70
4.1.1 Oracle operating system requirements................................................70
4.1.2 The Linux operating system user for Oracle.........................................78
4.1.3 Creating the directories for Oracle......................................................81
4.2 Installing the Oracle binaries....................................................................81
4.2.1 Creating the oraInst.loc File...............................................................82
4.2.2 Editing the response file template.......................................................83
4.2.3 Running Oracle Universal Installer using a response file.........................84
4.2.4 Installing the Oracle 11.1.0.7.0 patch set............................................85
Chapter 5 Oracle database configuration..........................................................87
5.1 Creating the Oracle listener using a Response File.......................................87
5.1.1 Verifying the created listener.............................................................88
5.2 Creating the WebSphere Process Server database ......................................89
5.3 Database listener configuration...............................................................117
5.4 Configuring database initialization parameters..........................................118

ix
 5.5 Oracle JDBC driver................................................................................120
Chapter 6 Creating Oracle users and tables.....................................................121
6.1 WebSphere Process Server tablespaces...................................................121
6.1.1 Predefined WPS tablespaces.............................................................121
6.1.2 Recommended user default tablespaces.............................................122
6.1.3 Create recommended tablespaces.....................................................123
6.2 WebSphere Process Server users and privileges........................................125
6.2.1 Needed WebSphere Process Server database users.............................125
6.2.2 WebSphere Process Server database user roles..................................126
6.2.3 WebSphere Process Server XA recovery user privileges.......................127
6.2.4 Create WPS users and assign needed privileges and roles....................130
6.2.5 WPS XA recovery user(s).................................................................134
6.3 WebSphere Process Server tables...........................................................137
6.3.1 Create CommonDB tables................................................................137
6.3.2 Create BPCDB tables.......................................................................139
6.3.3 Create BPC Explorer Reporting Function tables...................................142
6.3.4 Create Business Space tables...........................................................145
Chapter 7 Create deployment manager profile ................................................151
7.1 Create the profile..................................................................................151
7.2 Verification..........................................................................................152
7.3 Start and configure the deployment manager...........................................153
7.3.1 Create the authentication alias for XA recovery...................................154
7.3.2 Change the data source for Oracle 11g..............................................155
Chapter 8 Create custom profiles...................................................................158
8.1 Custom profile creation..........................................................................158
8.2 Verify the custom profile creation............................................................161
Chapter 9 Enable security ............................................................................164
9.1 Configure Federated Repository..............................................................164
9.2 Enable identity assertion........................................................................170
9.2.1 Enable inbound authentication..........................................................170
9.2.2 Enable outbound authentication........................................................171
9.3 Verification..........................................................................................172
Chapter 10 Create and configure the deployment environment..........................175
10.1 Create the deployment environment......................................................175
10.2 Configure deployment environment.......................................................187
10.2.1 Configure/verify authentication aliases.............................................187
10.2.2 Configure/verify bus security..........................................................188
10.2.3 Configure/verify JDBC providers......................................................192
10.2.4 Configure/verify data sources.........................................................194
10.2.5 Configure/verify SCA configuration..................................................198
10.2.6 Configure/verify CEI configuration...................................................200
10.2.7 Configure BPC Event Collector........................................................204
10.3 Configure/verify host names and corresponding port numbers..................208
10.4 Share transaction and recovery logs .....................................................211
Chapter 11 Create CEIDB tables....................................................................214
Chapter 12 Verify the deployment environment...............................................216
12.1 Verify messaging cluster .....................................................................216
12.1.1 Verify messaging cluster startup.....................................................216
12.1.2 Verify messaging cluster messaging table creation............................219

x
 12.2 Verify the support cluster ....................................................................221
12.3 Verify the application target (BPEL) cluster ............................................224
Chapter 13 Install and configure IBM HTTP Server v7.0....................................227
13.0.1 Install the IHS binaries..................................................................229
13.0.2 Configure SSL .............................................................................239
13.0.3 Add IHS to the WPS cell.................................................................244
13.0.4 Configure BFM and HTM REST endpoints..........................................257
Chapter 14 Verify application functionality......................................................260
14.0.1 Verify BPC Explorer and BPC Reporting functionality..........................260
14.0.2 Deploy the Claims Handling sample application.................................263
14.0.3 Run the Claims Handling sample application.....................................268
14.0.4 Verify the Business Space..............................................................273
Chapter 15 Appendix...................................................................................279
15.1 WPS How To......................................................................................279
15.1.1 Save changes and synchronize nodes..............................................279
15.1.2 Start/stop the deployment manager and the node agents..................281
15.2 IHS How To........................................................................................285
15.2.1 Starting and stopping the IBM HTTP server......................................285
15.3 Oracle How To....................................................................................286
15.3.1 Starting and stopping the database listener......................................286
15.3.2 Starting and stopping the database.................................................288
15.3.3 Starting and stopping the Oracle Enterprise Manager Console.............289
15.3.4 Resetting a user password in the Oracle database.............................290
15.3.5 Compute database statistics...........................................................291
15.3.6 Work with Redo Log Groups...........................................................292

xi
Part I Introduction

1
 Chapter 1 Introduction
This part of the document provides planning information. It is highly recommended to
plan the setup before starting with the installation and configuration. Careful planning
can avoid both the need to reset the involved systems or a complete restart of the
overall setup process.
The first part of this chapter (Planning the cell and cluster setup primer) provides a
brief overview of the prerequisite actions that need to be completed before starting
with the actual setup.
In the second part of this chapter (Planning the cell and cluster setup) a brief descrip-
tion of the major components for building a cell is provided followed by an overview of
how the components are assigned to the systems.
The term system is used in multiple different facets depending on the author, in-
dustry, functional area etc. In the IT world itself various interpretations also exist. A
common understanding does not really exist, but often the term system is a synonym
for a machine or a set of machines, e.g. a server or personal computer. Furthermore
the term system is used to specify a combination of machine and inclusive software
used to build a solution. From a usage perspective such solutions (systems including
software) are often referenced as service. An application server, especially the Web-
Sphere Process Server, might be understood as a system providing services.
Depending on the requirements related to performance and scalability the service can
be implemented on a single machine or it might be necessary to use a set of machines
where the term machine in this context is a server. On large machines, e.g. IBM
Power Systems, the overall power might be distributed in partitions where each parti-
tion will be referenced as an independent system. Another option might be to config-
ure the software multiple times on a single machine where it is usual to reference
each configuration as a system.
When multiple configurations of the WebSphere Process Server reside on the same
machine they are sometimes referenced as instance.
In this document the term system is used to define a machine where the WebSphere
Process Server is installed and configured.

2
 1.1 Planing the cell and cluster setup primer
The following list of tasks/subtasks should be completed in order to enable a
straightforward cell setup including clusters (A checklist can be found in Appendix ):

1.1.1 Assign WebSphere components to the systems

This task comprises multiple subtasks, including:

• Topology selection (performance, scalability)

• WebSphere Process Server software level selection (e.g. version 7.0.0.1)
• Database system selection, database tuning, and database distribution (e.g.
DB2 version 9.5 FP1, Oracle 11g Release 1)
• Number of systems, hardware and operating system
• Establish new systems (hardware) or reuse/adapt existing ones
• Provide hardware and operating system requirements
• Check conflicts when using existing systems (e.g. ports, applications, firewalls)
• Create a topology chart
• Plan hostnames (used during WebSphere Process Server configuration)

For further more detailed information related to concepts, architecture and back-
ground aspects please check the following documentation.

WebSphere Process Server V7.0 Information Center

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?
topic=/com.ibm.websphere.wps.doc/welcome_wps.html

WebSphere Business Process Management V7.0 Production Topologies

http://www.redbooks.ibm.com/redpieces/abstracts/sg247854.html?Open

3
 1.1.2 Install the operating system and the prerequisites
Depending on the customers business preferences one of the supported operating
systems may be used. In this document the systems used will be Linux systems. For a
detailed list of hardware and software prerequisites refer to the WebSphere Process
Server V7.0 Information Center.

A list of the minimum software and hardware required for WebSphere Process Server
Version 7.0 can be found here:
http://www.ibm.com/software/integration/wps/sysreqs/

Another important requirement is to ensure all involved systems are using a synchron-
ized time. Typically this will be achieved by a timeserver providing system time for all
systems.

1.1.3 Select the type of user directory for the cell

General options are: Federated repository, IBM Tivoli Directory Server (LDAP) or one
of the other supported custom registries. The federated repository enables the
support of multiple repositories which can be file-based, LDAP, database, and custom
registries.

In the various documents an additional option (local operating system) is mentioned,

but in a cell or clustered environment (which is the scope of this document) it is not
supported.
Select what fits your needs best. As most environments already maintain a user
directory which can be attached easily.

Note: If you intend to use the Business Space component it is mandatory to use
the federated repository.

1.1.4 Get the software packages

Obtain the required software packages of the desired product version and fix packs in
a format that fits your needs best (DVD, CD, zip-pkg …)

4
 1.1.5 Summarize the values used during installation
The following values are needed during the installation and configuration steps. You
need to plan them carefully before starting.

• Operating system user IDs and passwords

• Database user IDs and passwords
• Messaging user IDs and passwords
• WebSphere Process Server user IDs and passwords
• Directory locations for:
▪ Install sources
▪ Database system
▪ Database drivers
▪ WebSphere Process Server install directory
▪ Profile directories for deployment manager and custom nodes
• Hostnames of the involved systems
• Naming of cluster components
▪ Cell name
▪ Node names
▪ Profile names
▪ Database names

For more information related to “Naming considerations for profiles, nodes, hosts,
and cells” refer to the Information Center:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?
topic=/com.ibm.websphere.wps.doc/doc/cins_naming.html

5
 1.2 Planning the cell and cluster setup
With a cell setup planning is highly recommended since a cell setup is much more
complex compared to a single server setup. A single server contains all required
elements in one unit so that no communication between the different components
across systems is necessary. However with the scaling limitations of a single server,
and with more complex requirements a single server may not longer be sufficient. In
this case a cell with multiple server instances should be used.
Just adding more single servers will not fit all aspects. Especially synchronous
administration as well as controlled communication are not covered. This can be
achieved by using the WebSphere Application Server Network Deployment solution
which provides several additional capabilities. To understand this concept several basic
built-in components will be outlined.

1.2.1 Major components of a cell

Various elements are building a cell also referred as network deployment topology.

1.2.1.1 Cell
A WebSphere cell is a logical unit containing all elements being required for operation.
In other words it is a management domain for a distributed environment of elements
that are centrally managed and have access to shared resources in the cell. The key
elements are briefly described in the following paragraphs. In physical terms a
WebSphere cell typically involves multiple systems.

1.2.1.2 Node
A WebSphere node is an element within a cell which typically contains one or more
application servers. A managed node consists of a node agent managing the the node
and all application servers hosted on that node. An unmanaged node does not have a
node agent and will be used to administer the IBM HTTP server (also referred as
WebServer). A WebSphere node resides on a single host, but on a host it is possible
to configure multiple nodes having then multiple node agents.

1.2.1.3 Node Agent

A WebSphere node agent is an architectural component that enables the
deployment manager for the cell to remotely manage the node, its application
servers, and their applications. The node agent represents the node in the
management cell and keeps the configuration up-to-date.

1.2.1.4 Deployment Manager

A WebSphere deployment manager is a special application server whose only task is
the management and configuration of all elements in the cell in which it exists. The
deployment manager requires no node agent. The deployment manager runs a single
application, a Web-based configuration front-end known as the Integrated Solutions
Console or Administrative Console.
When J2EE™ applications are deployed within a cell, they are deployed to a server,
cluster or multiple instances of both being referred to as the deployment target.

6
 1.2.1.5 Application Server
A WebSphere application server hosts zero or more applications. An application server
instance can be configured as follows:
• Stand-alone application server
A stand-alone application server does not belong to a cell and runs its own
administrative console.
• Managed application server
A managed application server is part of a cell and is managed by a deployment
manager residing on a separate node. A managed application server is not part
of a cluster.
• Application server as member of a cluster
An application server that is a cluster member resides on a node belonging to a
cell, and is managed by a deployment manager residing on a separate node.
The application server is part of a cluster.

1.2.1.6 Cluster
A WebSphere cluster is a logical collection of application servers configured to
perform the same task as a team. The members of a cluster can be distributed across
one or more nodes in any configuration. Clusters are typically used for scalability,
workload and high availability aspects.

1.2.1.7 Service Integration Bus

A service integration bus supports applications using message-based and service-
oriented architectures. A bus is a group of interconnected servers and clusters that
have been added as members of the bus. Applications connect to a bus at one of the
messaging engines associated with its bus members.
A messaging engine is a server component that provides core messaging functionality
of a service integration bus. A messaging engine manages bus resources and provides
a connection point for applications.
Each messaging engine is associated with a server or a server cluster that has been
added as a member of a bus. When you add an application server or a server cluster
as a bus member, a messaging engine is automatically created for this new member.
If you add the same server as a member of multiple buses, the server is associated
with multiple messaging engines (one messaging engine for each bus). You can create
additional messaging engines for use with server clusters that are bus members, for
availability and scalability reasons. However, in its simplest form a single engine can
realize a bus.

1.2.1.8 Database
In a complex environment typically various data exist which need to be stored
persistently. Within WebSphere accessing a database is transparent. It will be
accessed via a JDBC implementation related to the used database system. All required
database variables like name, location, user, password, etc are collected in the data
source and are administered via the deployment manager. Within WebSphere Process
Server several components persist data. Depending on the overall database
convention used this results in several independent databases or in several database
schema managed all in one database.

7
 1.2.1.9 Profile
Each profile defines a separate run-time environment, with separate command files,
configuration files, log files, and so on. Profiles enable you to have more than one
runtime environment on a system, without having to install multiple copies of the
system files. In WebSphere there are three kinds of profiles:

• The stand-alone server profile

• The deployment manager profile
• The custom profile.
The profile management tool will be used to built one of these profile types. In a cell
the profile for the deployment manager is the first one followed by the custom
profiles. After a custom profile has been created it needs to become a known element
in the cell. This is achieved by federating the node into the cell. Please note that
typically profiles have a one to one relation ship to nodes.
When additional products like the WebSphere Process Server or the WebSphere
Business Monitor are installed, the profiles need to be augmented to be able to serve
the additional functions.

1.2.2 WebSphere Process Server

The WebSphere Process Server is an SCA-compliant runtime element that provides
a fully converged, standards-based process engine that is underpinned by
WebSphere Application Server. Along with WebSphere Enterprise Service Bus,
it is a strategic product for integration and modernization of IT assets, including
core systems using SOA. Following the principles of SCA, there is a single
invocation model, a single data model, and a component-based framework.

The WebSphere Process Server can consist of a single server running on a single
machine, several independent servers running on multiple machines administered in a
cell (referred as managed servers), or it may consist of several servers combined to a
cluster running on several machines. Within a cell multiple clusters and multiple
managed servers are allowed and are referred as deployment targets.

1.2.3 WebSphere Business Monitor

The WebSphere Business Monitor is a CEI (Common Event Infrastructure) based
runtime element that provides business specific monitoring capabilities. Common Base
Events which can be emitted by various applications (i.e BPEL Processes running on
WebSphere Process Server) are consumed by monitor models. Based on defined met-
rics Key Performance Indicators (KPIs) and Visual Diagrams can be generated, viewed
and monitored within Business Space.

Like WebSphere Process Server WebSphere Business Monitor can consist of a single
server running on a single machine, several independent servers running on multiple
machines administered in a cell (referred as managed servers), or it may consist of
several servers combined to a cluster running on several machines. Within a cell
multiple clusters and multiple managed servers are allowed and are referred as

8
deployment targets.

1.2.4 Assign the cell and cluster components to the systems

In general numerous topologies are possible and a decision on the best solution
depends on the appropriate customer needs. In this document a topology is chosen
which has an average complexity and is suitable for showing the various configuration
steps.

The selected topology for the environment is a WebSphere Process Server cell. The
cell contains several clusters.

WPS clusters:

• Application Cluster (“Application Target Cluster”)

Contains the business process applications (i.e BPEL Processes).

• A separate Message Engine Cluster (“Messaging Cluster”)

Contains the messaging engines.

• Support Cluster
Contains the Common Event Infrastructure (CEI), the Business Process Explorer
and the Business Space.

9
The cluster environment is established on 3 dedicated physical machines, the
database on a separate fourth machine. As security is also required, an existing user
directory (IBM Tivoli Directory Server – in this document typically mentioned as LDAP)
is attached to the cluster. Both the database and the LDAP machine are not shown in
the picture below:

The setup is built on four dedicated machines, one hosting the database installation
(not show in the picture), the others hosting the deployment manager, the HTTP
Server and the WebSphere Process Server nodes building up the cell. In this topology
the messaging engines are separated from the applications. Therefore the messaging
will be done in a separate cluster, the “Messaging Cluster”. On a separate cluster
called “Application Target Cluster”, the BPE Container and the Task Container will be
installed to host all process applications in the future.
Last but not least the supporting functions provided by WebSphere Process Server
(like the Common Event Infrastructure, the Business Rules Manager, the BPC
Explorer, the BPC Event Collector and the Business Space) are installed in the third
cluster called “Support Cluster”. Both, the “Application Cluster” and the “Support
Cluster” will use the “Messaging Cluster” for all messaging purposes.

10
This document describes how to install and configure the outlined WebSphere Process
Server clusters. There is only one active messaging engine per bus in the cluster. The
other messaging engines are in stand-by mode, ready to become active if the
currently active messaging engine goes down. The following picture illustrates the
Messaging Cluster with the different messaging engines in active and standby state
(1-of-N policy).

11
PART II Preparation

12
 Chapter 2 Prerequisites and operating system
installation
2.1 Install operating system
In this document it is assumed that a pre-installed Red Hat Enterprise Linux system
can be used. Therefore the installation steps of the operating system are skipped.
Thus continue directly to check/provide the prerequisites:

Verify operating system level. Please note that this is only a sample and the output on
the actual used system might be different.

cat /etc/redhat-release

Red Hat Enterprise Linux Server release 5.4 (Tikanga)

cat /proc/version

Linux version 2.6.18-164.10.1.el5 ([email protected])

(gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Wed Dec 30 12:01:40
EST 2009

Check on all machines, that the WPS 7.0.0.1 required prerequisites are met. Do this
using the information provided here:

“Prerequisites for installing WebSphere Process Server“, Information Center:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.
websphere.wps.doc/doc/cins_install_prereqs.html
“Preparing Linux systems for installation“, Information Center:
http://publib.boulder.ibm.com/infocenter/wasinfo/fep/topic/com.ibm.webspher
e.installation.nd.doc/info/ae/ae/tins_linuxsetup.html

13
 2.2 Time server setup
To avoid conflicts in a production environment caused by date/time mismatch in a cell,
all machines running WebSphere components as well as the system hosting the
database system are set up to receive their system date and time from a time server:

1. Logon as root
(if you are not using the native system console ensure x11 forwarding is
enabled)
2. Start the graphical Configuration Tool /usr/bin/system-config-time
3. Select Tab "Network Time Protocol and set
4. Servers (primary, secondary, tertiary): 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org,
2.rhel.pool.ntp.org

Note: Alternately you may use other time servers.

5. Enable Network Time Protocol: selected

6. Click Ok.

14
 2.3 Select the type of user directory
To demonstrate how to use ldap an existing user directory server IBM Tivoli Directory
Server 6.1 will be used. To keep administration simple, security will be set up with a
single user ID “vmmuser” of group “FVTStaff”. Additional LDAP credentials are:

Property Value
Directory type Tivoli Directory Server Version 6.1
LDAP host ldap.boeblingen.de.ibm.com
Port 389
Server user ID vmmuser
Server user password ********
Server user group ou=StaffTest,cn=FVTStaff,o=ibm,c=us
Base distinguished name (DN) o=ibm, c=us
Bind distinguished name (User DN) cn=ldapuser,o=ibm,c=us
Bind password
Anonymous bind Allowed

A useful utility to explore a LDAP directory is:

LDAP Explorer Tool on Sourceforge (available for Windows and Linux)

http://sourceforge.net/projects/ldaptool/

2.4 Software packages

WebSphere Process Server V7.0.0.0 (GA CDs)

15
Use the installation CDs or download the following file from IBM Passport Advantage:

WebSphere Process Server V7.0 Linux X86 32Bit Multilingual (CZ580ML)

➢ CZ580ML.tar.gz

WPS and WAS Fixes (WPS v7.0.0 FixPack 1, WPS and WAS mandatory iFixes)
WPS v7 Fixpack 1 will be applied. The Fixpack can be downloaded here:
http://www-01.ibm.com/support/docview.wss?uid=swg24024941&rs=0&cs=utf-
8&context=SSQH9M&dc=D400&loc=en_US&lang=en&cc=US

WPS and WAS Mandatory iFixes can be downloaded here:

http://www-01.ibm.com/support/docview.wss?
rs=2346&context=SS7J6S&dc=D600&uid=swg21414253&loc=en_US&cs=UTF-
8&lang=en

For WPS the following iFixes are needed:

JR35038, JR35039, JR35041, JR35042
For WAS the following iFixes are needed:
PM01854, PM02219 ,PM02308,PM02588, PM01518, PM02961, PM02956, PK95991

Oracle 11g Release 1 (11.1.0.6.0)

Get the Oracle database installation media for example:
➢ linux.x64_11gR1_database_1013.zip

For the installation of the products the files have been copied to the local
directory /root/SWINST on each machine. (Hint: this could also be a shared
directory)

16
2.5 Installation properties
2.5.1 User IDs
To keep the setup simple, the same user IDs will be used for dedicated functions.

UserType Username Role

Linux User root Linux system user and WebSphere Process
Server functional user ID
Linux DB oracle Linux system user for the database
User installation
WPS User vmmuser Central user ID for WebSphere components
(including Administration), also SCA / JMS
userid and BPE/HTM Administration role
userid
LDAP User ldapuser Central user ID for the ldap directory server
in our case the server
ldap.boeblingen.de.ibm.com

2.5.2 Directory locations

Directory Brief description
/root/SWINST Location of install sources
(WebSphere Process Server,
fixpacks, Oracle, DB2, scripts,
etc)
/opt/oracle Oracle Product install directory
on
w70l3ora
/opt/oracle/driver Oracle JDBC driver directory on
w70l3dmg
w70l3n01
w70l3n02
/WPS70 WebSphere Product install
directory
on w70l3dmg
w70l3n01
w70l3n02
/WPS70/profiles/Dmgr01 Profile directory deployment
manager on w70l3dmg
/WPS70/profiles/Custom01 Profile directory WPS custom
profile
on w70l3n01
/WPS70/profiles/Custom02 Profile directory WPS custom
profile
on w70l3n02
/opt/ihs7 IBM HTTP Server install
directory on w70l3dmg

17
 Note: Depending on your local needs, these directory names might be different.

2.5.3 Hostnames of the involved systems

Hostname Brief description
W70L3DMG Deployment manager
W70L3DMG IBM HTTP Server
W70L3DMG Proxy Server
W70L3N01 WPS Node 1 in the cell
W70L3N02 WPS Node 2 in the cell
W70L3ORA Oracle Database System
HOBART IBM Tivoli Directory Server

Note: Depending on your local needs, the amount of used hosts might be
different.

2.5.4 Naming of cluster components

Name Brief description

Dmgr01 Profile name deployment manager (WPS-DMGR)
Custom01 Profile name of WPS custom node 01
(w70l3n01Node01)
Custom02 Profile name of WPS custom node 02
(w70l3n02Node02)
Cell01 Cell name
w70l3dmgCellManager01 Node name Deployment Manager
w70l3N01Node01 WPS Node name node 1
w70l3N02Node02 WPS Node name node 2
BPELCluster Cluster name BPEL cluster
SupportCluster Cluster name Support cluster
MECluster Cluster name Messaging Engine cluster
BPELCluster_Member0x Member name BPEL cluster
SupportCluster_Member0x Member name Support cluster
MECluster_Member0x Member name Messaging Engine cluster
w70l3dmg.boeblingen.de.ibm.com Hostname deployment manager, http server,
proxy server
w70l3n01.boeblingen.de.ibm.com Hostname WPS custom profile 1
w70l3n02.boeblingen.de.ibm.com Hostname WPS custom profile 2
w70l3ora.boeblingen.de.ibm.com Hostname for the Oracle database

18
 Chapter 3 WebSphere Process Server cluster
installation and configuration

3.1 WebSphere Process Server cluster installation and

configuration primer
On a high level, the following steps are necessary to create a clustered WebSphere
Process Server (WPS). They are described in detail in the following chapters:

➢ Product installation
 Installation of the WPS binaries (including available fix packs and all
mandatory iFixes for WPS and WAS)
 Installation of the database system and database creation
➢ WPS Product configuration
 Create WPS server deployment manager profile
 Create the WPS tablespaces. users and schema objects
 Create WPS custom profiles
 Federate the WPS custom nodes
 Enable security in the cell
➢ Cluster configuration
 Create and configure the deployment environment
 Configure shared transaction logs
 Create CEIDB tables
➢ Install and configure the IBM HTTP Server
 Install the IHS binaries
 Configure SSL
 Add IHS to the WPS cell
 Configure BFM and HTM REST endpoint
➢ Verifcation of the setup
 Install and configure a sample application
 Verify the BPC Explorer
 Verify the Business Space

3.2 Installing WebSphere Process Server binaries

NOTE: The steps shown here have to be executed on each node that is sup-
posed to contain WPS functionality; In this case this are the machines W70l3d-
mg, w70l3n01, w70l3n02. Make sure to execute this step as user root.

If you are installing from the product DVD, mount the DVD and change to the
mount_point directory. If you are installing from a downloaded image from Passport
Advantage extract the image and change to the extract directory.

19
There are two options on how to install the WPS binaries:

1. graphical wizard
2. silent mode

Note: Installing the WPS binaries in silent mode is not described within this
document

To start the installation with the graphical wizard, enter the following (if you are not
locally working on the machine, make sure X11 tunneling is activated and an X server
is running on your machine):
cd /<WPS70_CD_OR_EXTRACTION_ROOT>
./launchpad.sh

Now the graphical wizard starts...

The "WebSphere Process Server 7 Launchpad" panel is displayed:

1. Click New Installation

2. In "a. Specify the installation location" enter the WPS installation directory.
In our case "/WPS70"
3. Click Install WebSphere Application Server

20
A notice is displayed reminding you to close the IBM Installation Manager ap-
plication if open:

1. Click OK

On successful installation, a notice is displayed:

1. Click OK
2. The WebSphere Application Server installation is now complete.

21
Now install WebSphere Process Server on top of WebSphere Application Serv-
er:

1. Click Install WebSphere Process Server

22
The IBM Installation Manager application will start to install WebSphere Pro-
cess Server:

1. Click Next

23
1. Read and accept the licence agreement
2. Click Next

24
1. Click Next

25
1. Click Next

26
The WebSphere Process Server installation is now ready to start:

1. Click Install
2. The Installation starts

27
After successful installation the folowing dialog is displayed:

1. Select to not start "None"

2. Click Finish

28
 1. Close the Launchpad application by clicking Exit

We sucessfully installed WebSphere Process Server 7.0.0.0. Now we need to prepare

the system to install the mandatory iFixes.

29
 3.3 Installing the Update Installer

To install the WebSphere Application Server mandatory iFixes we need the IBM Up-
date Installer application. Get the latest Update Installer from:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020446

and extract it.

Note: The current version at the time of writing this document is v7.0.0.7

There are two options on how to install the Update Installer:

1. graphical wizard

2. silent mode

Note: Installing the Update Installer in silent mode is not described within this
document

Start the Installation Wizard for the Update Installer with the following command:
cd /UPDI_INSTALLER_EXTRACT_ROOT/UpdateInstaller
./install

30
The "Installation Wizard Welcome" panel is displayed:

1. Click Next .

31
The "Software License Agreement" panel is displayed:

1. Select “I accept both the IBM and the non-IBM terms”

2. Press Next .

32
The "System Prerequisite Check" panel is displayed:

1. Verify that the Status of the System Prerequisites Check is passed.

2. Press Next .

33
The "Installation directory" panel is displayed:

1. Enter the installation directory path.

2.Press Next .

34
The "Installation Summary" panel is displayed:

1. Verify that the Update Installer gets installed in the proper directory.

2.Press Next .

35
The "Installation Complete" panel is displayed after the installation has fin-
ished:

1. Check that the installation was successful.

2. De-Select "Launch IBM Update Installer on exit".

3. Press Finish .

36
 3.4 Installing mandatory fixes
Get the latest mandatory ifixes and fixpack (Fixpack 1) from:

WPS Fixpack 1 general information:

http://www-01.ibm.com/support/docview.wss?
uid=swg24024941&rs=0&cs=utf-
8&context=SSQH9M&dc=D400&loc=en_US&lang=en&cc=US

WPS Fixpack 1 files:

http://www-01.ibm.com/support/docview.wss?
rs=2307&uid=swg27017658#install

WPS and WAS iFixes:

http://www-01.ibm.com/support/docview.wss?
rs=2346&context=SS7J6S&dc=D600&uid=swg21414253&loc=en_US&cs=UTF-
8&lang=en

Note: The current fixpack at the time of writing this document is Fixpack 1
(v7.0.0.1)

3.4.1 Install WAS mandatory iFixes

NOTE: The steps shown here have to be executed on each node that is sup-
posed to contain WPS functionality; In this case this are the machines W70l3d-
mg, w70l3n01, w70l3n02.

Extract the WAS iFixes it into the Update Installer maintenance directory
{UpdateInstaller_Home}/maintenance.

Hint: extract the iFixes to a shared directory to reuse it across multiple

installations.

There are two options on how to apply the fixpack:

1. graphical wizard

2. silent mode

Note: Applying the WAS iFixes using the silent mode is not described within this
document.

37
Start the Update Installer with the following command:
cd /opt/IBM/WebSphere/UpdateInstaller/
./update.sh

The "Welcome to the IBM Update Installer for WebSphere Software wizard"
panel is displayed:

1.Press Next .

38
The "Product Selection" panel is displayed:

1. Enter the appropriate directory path.

2. Click Next .

39
The "Maintenance Operation Selection" panel is displayed:

1. Check that Radio-button "Install maintenance package" is selected

2. Click Next .

40
The "Maintenance Package Directory Selection" panel is displayed:

1. Check the Directory path, this shoud be the path where you placed the
downloaded fixes

2. Click Next .

41
The "Available Maintenance Packages to Install" panel is displayed:

1. Press "Select Recommended Updates"

2. Click Next .

42
The "Installation Summary" panel is displayed:

1. Click Next .

43
 The "Installation Complete" panel is displayed:

1. Verify that the ifixes have been installed successfully

2. Click Finish.

3.4.2 Install WPS mandatory iFixes

NOTE: The steps shown here have to be executed on each node that is sup-
posed to contain WPS functionality; In this case this are the machines W70l3d-
mg, w70l3n01, w70l3n02.

Extract the WPS iFixes it into common directory on the current machine. For
example:

{UpdateInstaller_Home}/maintenance.

44
 Hint: extract the iFixes to a shared directory to reuse it across multiple
installations.

The WPS iFixes are applied using the IBM Installation manager application. As
described on the page where you downloaded the mandatory iFixes, the WPS
iFixes can be installed either using the IBM repository in the internet or by
downloading and adding the fixes to the local IBM Installation Manager repository.
Here we will use the option 2: "Download the iFixes" because we have no internet
access from the machines on which we install WPS. Start the IBM Installation
Manager application with the following command:

cd /opt/IBM/InstallationManager/eclipse/
./launcher

The "IBM Installation Manager" application starts:

1.Click File --> Preferences.

45
The "Preferences" dialog is shown:

1.Click Repositores.
2.De-select the checkbox for the currently displayed repository (http://public.
Dhe...)

46
We now have to add the downloaded WPS iFix repositories as repository
locations. The following steps have to be repeated for each downloaded WPS
iFix repository:

1.Click Add Repository.

2. Select the "repository.config" file for each iFix repository and click OK

47
3.Repeat this step for all needed WPS iFixes.
4.Add also the shipped WPS repository located on the WPS CD or the
extracted binary installaton files. The "repository.config" you need to add as a
repository is located here:

<WPS70_CD_OR_EXTRACTION_ROOT>/repository/repository.config

When all WPS iFix repositories have been added, the "Preferences" dialog will
look something like this:

1.Click Test Connections to verify each added repository is successfully ad

ded.
2.Click Apply.
3.Click OK.

48
To apply the WPS iFixes on our WPS binaries open IBM Installation Manager if
not already open:

1.Click the Update Icon

49
1.Click Next

50
1.Click Next

51
1.Make sure all needed WPS iFixes are recognized and selected
2.Click Next

52
1.Click Update

53
 If WPS update was successfully, the following dialog is shown:

1.Click Finish
2.Close IBM Installation Manager

3.4.3 Install WPS Fix Pack 1

NOTE: The steps shown here have to be executed on each node that is sup-
posed to contain WPS functionality; In this case this are the machines W70l3d-
mg, w70l3n01, w70l3n02.

Extract the WPS Fix Pack 1 files it into common directory on the current machine. For
example:

{UpdateInstaller_Home}/maintenance.

Hint: extract the Fix Pack 1 files to a shared directory to reuse it across multiple
installations.

54
The WPS Fix Pack 1 is applied using the IBM Installation manager application. As
for the WPS iFixes we will install the Fix Pack 1 by adding the Fix Pack 1 repository
files to the IBM Installation Manager. Start the IBM Installation Manager application
with the following command:

cd /opt/IBM/InstallationManager/eclipse/
./launcher

The "IBM Installation Manager" application starts:

1.Click File --> Preferences.

55
The "Preferences" dialog is shown:

1.Click Repositores.

56
We now have to add the downloaded WPS Fix Pack 1 repositories as a
repository location:

1.Click Add Repository.

2.Select the first "repository.config" file for the WPS Fix Pack 1 repositories,
click OK
3.Repeat this step (just like applying the WPS iFixes earlier in the previous
chapter) for all needed repositories for WPS Fix Pack 1 (as of writing this
document this where the following:

sca.1.0.1.1.fp.zip
sca.1.0.import.zip
was.7.0.import.zip
wps.7001.repository.zip
xml.1.0.0.1.fp.zip
xml.1.0.import.zip

57
When all WPS Fix Pack 1 repositories have been added, the "Preferences"
dialog will look something like this:

1.Click Test Connections to verify each added repository is successfully ad-

ded.
2.Click Apply.
3.Click OK.

58
To apply the WPS Fix Pack 1 on our WPS binaries open IBM Installation
Manager if not already open:

1.Click the Update Icon

59
1.Click Next

60
1.Click Next

61
1.Click Next

62
1.Accept the licence agreement
2.Click Next

63
1.Click Next

64
1.Click Update

65
If WPS Fix Pack 1 update was successfully, the following dialog is shown:

1.Click Finish
2.Close IBM Installation Manager

66
 3.5 Verify WebSphere Process Server binary installation

NOTE: The steps shown here have to be executed on each node that is sup-
posed to contain WPS functionality; In this case this are the machines W70l3d-
mg, w70l3n01, w70l3n02.

Verify the success of the binary installation by examining the WebSphere Process
Server log files. If the last line of the file contains the word INSTCONFSUCCESS, the
selected WebSphere Process Server features were installed successfully.

The log file is located as follows:

/WPS70/logs/install/log.txt

The log file of each fix can be found under in directory:

/WPS70/logs/update/install/updatelog.txt

You can also use the Installation Verification Tool (IVT) to check if the binaries
have been installed correctly. See the information on how to do that here:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?
topic=/com.ibm.websphere.wps.doc/doc/tins_ivt.html

Also on each machine make a WPS version info check. To check the WPS version
execute the following command on each machine:

/WPS70/bin
./versionInfo.sh

This results in the following report. Check if the version numbers are compliant on
each machine:
--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time January 14, 2010 4:33:34 PM CET

Installation
--------------------------------------------------------------------------------
Product Directory /WPS70
Version Directory /WPS70/properties/version
DTD Directory /WPS70/properties/version/dtd
Log Directory /WPS70/logs
Backup Directory /WPS70/properties/version/nif/backup
TMP Directory /tmp

67
Product List
--------------------------------------------------------------------------------
XML installed
ND installed
WBI installed
SCA installed

Installed Product
--------------------------------------------------------------------------------
Name XML Feature Pack
Version 1.0.0.1
ID XML
Build Level cf010950.07
Build Date 12/19/09
Architecture Intel (32 bit)

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 7.0.0.7
ID ND
Build Level wps0946.04
Build Date 11/18/09
Architecture Intel (32 bit)

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Process Server
Version 7.0.0.1
ID WBI
Build Level of0950.17
Build Date 12/20/09
Architecture Intel (32 bit)

Installed Product
--------------------------------------------------------------------------------
Name SCA Feature Pack
Version 1.0.1.1
ID SCA
Build Level cf010950.08
Build Date 12/19/09
Architecture Intel (32 bit)

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

Hint: by issueing the command line parameter

"versionInfo.sh -maintenancePackages"
you get a detailed list which fixes are installed on the system.

68
Part III Database System

69
 Chapter 4 Oracle binary installation
This chapter covers the Oracle binary installation and its prerequisites on an Red Hat
Enterprise Linux Version 5 system.

4.1 Oracle installation prerequisites

This chapter describes all Linux OS and user prerequisites for the Oracle installation on
a Red Hat Enterprise Linux Version 5 system.
All information in the following sections were gathered from the Oracle® Database
Installation Guide 11g Release 1 (11.1) for Linux Part Number B32002-06:
http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/toc.htm

Before Oracle can be installed on a Linux operating system all requirements must be
met and all preparation tasks must be finished successfully.

4.1.1 Oracle operating system requirements

This section describes the operating system requirements for Oracle 11g. These
requirements will be checked during the Oracle installation process and marked as
failed or succeeded. If a prerequisite fails in the check go back to this chapter and
check the failed prerequisites. Continuing the installation with a failed prerequisite can
lead to a unrecoverable installation failure.

4.1.1.1 Required Linux packages for Oracle

An Oracle 11g installation requires several Linux software packages (RPMs) to be
installed on the RHEL5. Most of these packages have automatically been installed
during the actual Linux installation. However, to avoid potential problems at a later
point in time, it is recommended to check that the RPMs listed below are installed.
Note that these packages must be at least at the level of the listed version.

70
RPMs required for Oracle 11g on a RHEL5 64-bit system - note that on the 64bit
system, several software packages are required in both, the 32-bit and 64-bit
versions:

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12
glibc-2.5-12 (32 bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5-12 (32 bit)
libaio-0.3.106
libaio-0.3.106 (32 bit)
libaio-devel-0.3.106
libgcc-4.1.1
libgcc-4.1.1 (32 bit)
libstdc++-4.1.1
libstdc++-4.1.1 (32 bit)
libstdc++-devel 4.1.1
make-3.81
sysstat-7.0.0

Note: The listed packages without the additional (32 bit) mark are 64 bit ver-
sions.

71
 RPMs required for Oracle 11g on a RHEL5 32-bit system:

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3-61
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
glibc-2.5-12
glibc-common-2.5-12
glibc-devel-2.5-12
glibc-headers-2.5-12
gcc-4.1.1-52
gcc-c++-4.1.1-52
libaio-0.3.106
libaio-devel-0.3.106
libgcc-4.1.1-52
libstdc++-4.1.1
libstdc++-devel-4.1.1-52
make-3.81-1.1
sysstat-7.0.0
unixODBC-2.2.11
unixODBC-devel-2.2.11

To verify that the required software packages are installed, enter the following
command as user root:

rpm -qa |grep <package_name>

For example:
rpm -qa |grep binutils

To install the required software packages , enter the following command as user root:

rpm -ivh <package_name_version>

For example:
rpm -ivh binutils-2.17.50.0.6

72
 4.1.1.2 Linux kernel requirements
Oracle 11g requires a Linux kernel version of at least 2.6.18.

To verify the installed Linux kernel version on your Oracle DB host machine execute
the following command as user root:

uname -r

2.6.18-164.10.1.el5

4.1.1.3 Linux kernel parameters

The Linux kernel parameters listed below show the values required for the Oracle 11g
database. It is recommended to tune theses parameters for production environments.

For further information on tuning please refer to: Oracle® Database Performance
Tuning Guide 11g Release 1 (11.1) Part Number B28274-02:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28274/toc.htm

The following parameters and values are required as a minimum for the Oracle 11g
installation:

Kernel parameter Value Description

kernel.shmmax 0.5 x RAM size or shmmax is the maximum size
4GB – 1byte (depends of one shared memory
on which is lower) segment.
kernel.shmmni 4096 shmmni is the maximum
number of shared memory
segments
kernel.shmall 2097152 shmall specifies the
maximum number of shared
memory pages
(continued)

73
Kernel parameter Value Description
kernel.sem semmsl 250 semmsl is the maximum
number of semaphores per
semaphore set
semmns 32000 semmns is the the total
number of semaphores
semopm 100 semopm is the maximum
number of semaphore
operations that can be
performed per semop(2)
system call.
semmni 128 semmni is the maximum
number of semaphore sets in
the entire Linux system
fs.file-max 102696 file-max is the maximum of
file handles that the Linux
kernel will allocate
net.ipv4.ip_local_port_ran 1024 65000 ip_local_port_range defines
ge the local port range used by
TCP und UDP traffic to choose
the local port
net.core.rmem_default 4194304 rmem_default is the receive
socket buffer's default size
net.core.rmem_max 4194304 rmem_max is the receive
socket buffer's maximum size
net.core.wmem_default 262144 wmem_default is the send
socket buffer's default size
net.core.wmem_max 262144 wmem_max is the send
socket buffer's maximum size

Important: If the current system values are higher than the ones listed above,
it is recommended to leave them as they are.
This is not valid for the SHMMAX parameter which needs to be calculated.

74
To check the values issue the following command as user root:

/sbin/sysctl –a | grep <kernel_parameter>

For example:
/sbin/sysctl –a | grep kernel.shmmax

kernel.shmmax = 1892380672

To change the values, edit /etc/sysctl.conf as user root and modify this file as shown
below:

# -----------------------------------------------------------------
# Linux kernel parameter for Oracle 11g
# -----------------------------------------------------------------
kernel.shmmax = <add value here>
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 102696
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144

After completing the changes, activate them either by issuing the following command
as user root:

/sbin/sysctl –p

...
kernel.shmmax = <added value>
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
fs.file-max = 102696
...

or reboot the operating system.

75
 4.1.1.4 Memory requirements
Oracle 11g requires a minimum of 1GB RAM memory.

4.1.1.5 Disk space requirements

The following are the disk space requirements for installing Oracle Database 11g
Release 1.

4.1.1.5.1 Disk requirements in the /tmp directory

In the /tmp directory 400 MB of free disk space is needed.
To determine the amount of disk space available in the /tmp directory, enter the
following command:

df -k /tmp

If there is less than 400 MB of free disk space available in the /tmp directory, then
complete one of the following steps:
• Delete unnecessary files from the /tmp directory to meet the disk space
requirement.
• Set the TMP and TMPDIR environment variables when setting the oracle user's
environment (described in Linux operating system user for Oracle).
• Extend the file system that contains the /tmp directory. If necessary, contact
the system administrator for information about extending file systems.

4.1.1.5.2 Disk space requirements on the system

To determine the amount of free disk space on the system, enter the following
command:

df -k

Between 3.5 GB and 5 GB of disk space for the Oracle software, depending on the
installation type are needed. The following table describes the disk space requirements
for software files for each installation type:

Installation Type Requirement for Software Files (GB)

Enterprise Edition 4.35
Standard Edition 3.73
Custom (maximum) 4.54

76
The following table describes the disk space requirements for each installation type:

Installation Type Requirement for Datafiles Files (GB)

Enterprise Edition 1.68
Standard Edition 1.48
Custom (maximum) 2.14

Additional disk space, either on a file system or in an Automatic Storage Management

disk group, is required for the flash recovery area if you choose to configure
automated backups.

4.1.1.5.3 Disk space requirements for WebSphere Process Server

The Oracle database for WebSphere Process Server (WPS) needs between 4.0 GB and
5,5 GB additional disc space for the Oracle system data files and redo logs.
This disk space requirement can raise depending on the amount of Processes and
running process instances.
The following table describes the additional disc space requirements for the Oracle
system data files and redo logs:

Installation Type Additional Requirement for Datafiles Files (GB)

WPS stand-alone server ~ 4.00
WPS Cluster ~ 6.00

4.1.1.6 Swap Space requirements

Oracle 11g requires the following swap space size:

RAM size Swap space size

1GB – 2GB RAM 1.5 x the RAM size
2GB – 8GB RAM 1 x the RAM size
8GB RAM and higher 0.75 x the RAM size

To display the size of the configured swap space execute the following command as
user root:

fdisk -l | grep swap

/dev/sda 33 554 4192965 82 Linux swap / Solaris

77
 4.1.2 The Linux operating system user for Oracle
The Oracle 11g installation is usually performed using a Linux operating system user.
This user needs certain environment variable settings to make sure that the Oracle
database is set up and functions correctly. This section describes how to create such a
user for Oracle, and how to configure this user’s environment.

4.1.2.1 Creating the Linux operating system user for Oracle

The following local operating system groups and users are required to install an Oracle
database:

• The Oracle Inventory group (oinstall)

• The operating system database administrator group ( dba)
• The Oracle software owner/user (oracle)

Note: The group and user names are a recommendation from the Oracle Install-
ation Guide for Linux. We will follow the recommendation in this case.

To determine if these groups and users already exist, and if necessary, to create
them, follow the steps below.
To determine if the group oinstall exists, enter the following command as user
root:

grep oinstall /etc/group

If the output of this command contains the group name oinstall, then the group
already exists.

To determine if the group dba exists, enter the following command as user root:

grep dba /etc/group

If the output from this command contains the group name dba, then the group
already exists.

If you need to create these groups, enter the following commands as user root:

groupadd oinstall
groupadd dba

78
To determine if the user oracle exists and belongs to the correct groups, enter the
following command as user root:

id oracle

If the user oracle exists, this command will display information about the groups to
which the user belongs. The output should be similar to the following:

uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)

This indicates that oinstall is the primary group and dba is a secondary group. Some
hints and tips if you need to adapt your settings are described in the following.

If the oracle user exists, but its primary group is not oinstall or it is not a member of
the group dba, enter the following command as user root:

usermod -g oinstall -G dba oracle

If the user oracle does not exist, enter the following command as user root to create
it:

useradd -g oinstall -G dba oracle

This command creates the oracle user and specifies oinstall as the primary group
and dba as the secondary group.

Enter the following command to set the password of the oracle user:

passwd oracle

79
 4.1.2.2 Modifying the profile of user oracle
After creating the operating system user oracle, the user’s profile needs to be
changed. To do this, log in as user oracle and change or add the following entries in
/home/oracle/.bash_profile:

export ORACLE_BASE=/opt/oracle
export ORACLE_HOME=$ORACLE_BASE/11g
export ORACLE_PATH=$ORACLE_BASE/common/oracle/sql:.:$ORACLE_HOME/rdbms/ad-
min
export ORACLE_SID=ORCL

export PATH=.:${PATH}:$HOME/bin:$ORACLE_HOME/bin
export PATH=${PATH}:/usr/bin:/bin:/usr/bin/X11:/usr/local/bin
export PATH=${PATH}:$ORACLE_BASE/common/oracle/bin
export ORACLE_TERM=xterm
export TNS_ADMIN=$ORACLE_HOME/network/admin
export ORA_NLS10=$ORACLE_HOME/nls/data
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$ORACLE_HOME/oracm/lib
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/lib:/usr/lib:/usr/local/lib
export CLASSPATH=$ORACLE_HOME/JRE
export CLASSPATH=${CLASSPATH}:$ORACLE_HOME/jlib
export CLASSPATH=${CLASSPATH}:$ORACLE_HOME/rdbms/jlib
export CLASSPATH=${CLASSPATH}:$ORACLE_HOME/network/jlib
export THREADS_FLAG=native
export TEMP=/tmp
export TMPDIR=/tmp

The environment variables ORACLE_BASE and ORACLE_HOME can be adapted in

order to match a different Oracle installation directory.

Note: In this document the defaults are used for the environment variables OR-
ACLE_BASE and ORACLE_HOME. If other values are used the screens shown in
4.2 Installing the Oracle binaries will reflect those values instead of the defaults.

The environment variable ORACLE_SID defines the Oracle System ID for the
particular database on the system. Set this system variable to match the value that
will be used later in the database creation process.

80
 4.1.3 Creating the directories for Oracle
The Oracle user needs a base directory for the software binaries and the database
files. The user must have read and write rights in this directory.
Create this directory to match the path defined in the previous chapter in the system
variable ORACLE_BASE (e.g. /opt/oracle).

To create the Oracle base directory execute the following commands as user root:

mkdir -p /opt/oracle
chown -R oracle:oinstall /opt/oracle
chmod -R 775 /opt/oracle

4.2 Installing the Oracle binaries

This chapter describes the Oracle 11g binary installation on a Red Hat Enterprise Linux
5 (RHEL5) operating system. The Oracle binary installation will be performed in silent
mode using an response file. General information about how to install Oracle using a
response file can be found in the Oracle® Database Installation Guide 11g
Release 1 (11.1) for Linux Part Number B32002-06.

Before installing the binaries, make sure that the binaries for Oracle 11g have been
unzipped in the /tmp/db11106 directory or the Software CD/DVD is mounted in the
system.
In this example the unzipped variant will be used. Please refer to the Linux man-page
how to mount the CD/DVD and how to access the file on it.

Note: Make sure that you use Oracle 32-bit binaries on a 32-bit Linux system,
and Oracle 64-bit binaries on a 64-bit system.

The following are the general steps to install and configure Oracle products using Or-
acle Universal Installer in silent:
1. Create the oraInst.loc file.
2. Prepare a response file.
3. Run Oracle Universal Installer in silent mode (Software-only).
4. Run Oracle Patch Set in silent mode.
5. Run Net Configuration Assistant in silent mode
6. Run Database Configuration Assistant in silent mode.

These steps are described in the following sections.

81
 Note: The steps in the following sections imply that the user oracle is logged
in on the database host.

4.2.1 Creating the oraInst.loc File

This file specifies the location of the Oracle Inventory directory where Oracle Universal
Installer creates the inventory of Oracle products installed on the system.

Note: If Oracle software has been installed previously on the system, the
oraInst.loc file might already exist. If the file does exist, you do not need to cre-
ate a file.

To create the oraInst.loc file, follow these steps:

1. Switch user to root :

su - root

2. Change directory to /etc:

cd /etc/

3. Use a text editor to create the oraInst.loc file, containing the following
lines:
vi oraInst.loc

inventory_loc=$ORACLE_BASE/oraInventory
inst_group=oinstall

In this example, $ORACLE_BASE is the path of the Oracle base directory, for example,
/opt/oracle. Type in a absolute path for ORACLE_BASE, do not use variables.

4. Enter the following commands to set the appropriate owner, group, and
permissions on the oraInst.loc file:
chown oracle:oinstall oraInst.loc
chmod 664 oraInst.loc
exit

82
 4.2.2 Editing the response file template
Oracle provides response file templates for each product and installation type, and for
each configuration tool. These files are located at the {db_install_dir}/response
directory. In this example the response files are located in /tmp/db11106/response
and it will use the enterprise.rsp for the silent installation.
To modify the enterprise.rsp response file finish the following steps:

1. Open the response file in a text editor:

vi /tmp/db11106/response/enterprise.rsp

In addition to editing settings specific to the Oracle Database installation, check that
the FROM_LOCATION path is correct and points to the products.xml file in the stage
directory in the installation media. You may want to set this variable to point to an
absolute path, for example:

FROM_LOCATION="/directory_path/stage/products.xml"

Remember that sensitive information, such as passwords, can be specified at

the command line rather than within the response file. "How Response Files
Work?" explains this method. See Also: Oracle Universal Installer and OPatch
User's Guide for detailed information on creating response files

2. Follow the instructions in the file to edit it.

Note: Oracle Universal Installer or configuration assistant fails if the response

file is not configured correctly. Refer to "Silent-Mode Response File Error Hand-
ling" section for more information about troubleshooting a failed silent-mode in-
stallation.

Change the variables in the enterprise.rsp response file to the following values:

UNIX_GROUP_NAME="oinstall"
FROM_LOCATION="/tmp/db11106/stage/products.xml"
ORACLE_BASE="/opt/oracle"
ORACLE_HOME="/opt/oracle/11g"
ORACLE_HOME_NAME="OraDbHome1"
RESTART_SYSTEM=false
RESTART_REMOTE_SYSTEM=false
ORACLE_HOSTNAME="w70l3ora.boeblingen.de.ibm.com"
INSTALL_TYPE="EE"
s_nameForDBAGrp="dba"

83
 s_nameForOPERGrp="dba"
s_nameForASMGrp="oinstall"
n_configurationOption=3

4.2.3 Running Oracle Universal Installer using a

response file
The Oracle Universal Installer executable, runInstaller, provides several options. For
help information on the full set of these options, run the runInstaller command with
the -help option:
/tmp/db11106/runInstaller -help

The help information appears in a window after some time.

To run Oracle Universal Installer using a response file:

1. Complete the preinstallation tasks listed in 4.2.2 Editing the response file
template.

2. Log in as the Oracle software owner user (in this case oracle ).

3. To start Oracle Universal Installer in silent mode, enter the following com-
mand:
/tmp/db11106/runInstaller -silent -noconfig -responseFile /tmp/db11106/re-
sponse/enterprise.rsp

Note: Do not specify a relative path to the response file. If you specify a relat-
ive path, then the Oracle Universal Installer fails.

Wait until the installation is finished.

If any errors occur, refer to
Oracle® Database Installation Guide 11g Release 1 (11.1) for Linux
Part Number B32002-06:
http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/toc.htm

4. When the installation completes, log in as the root user and run the
root.sh script:
su - root
password:

84
 /opt/oracle/11g/root.sh

4.2.4 Installing the Oracle 11.1.0.7.0 patch set

This chapter describes the Oracle 11g patch set installation on a Red Hat Enterprise
Linux 5 (RHEL5) operating system. The Oracle patch set installation will be performed
in silent mode using an response file. In this case the Oracle patch set 11.1.0.7.0 will
be installed.

Note: The Oracle 11g (11.1.0.6.0) can be used for WebSphere Process Server
7.0. This step can be skipped if the Oracle Patch Set is not needed.

Finish the following steps to install the Oracle 11g Patch Set 11.1.0.7.0:

1. Download the Oracle 11g Patch Set 11.1.0.7.0 for Linux from the Oracle
Support Homepage (Metalink).
https://metalink.oracle.com/CSP/ui/index.html

Copy the downloaded patch set file to the database host. Make sure, that the oracle
user has
2. Unzip the downloaded Patch Set to /tmp/patch11107 .
Login on the database host as user oracle and unzip the downloaded patch set file.

3. Edit the response file template.

To edit the response file template execute the following command:
vi /tmp/patch11107/response/patchset.rsp

Change the variables in the patchset.rsp response file to the following values:

UNIX_GROUP_NAME="oinstall"
FROM_LOCATION="/tmp/patch11107/stage/products.xml"
ORACLE_HOME="/opt/oracle/11g"
ORACLE_HOME_NAME="OraDbHome1"
RESTART_SYSTEM=false
OUI_HOSTNAME="w70l3ora.boeblingen.de.ibm.com"
METALINK_USERNAME=""

4. Run the Oracle Universal Installer using the patchset.rsp response file:

85
Execute the following command to start the oracle universal installer:
/tmp/patch11107/runInstaller -silent -responseFile
/tmp/patch11107/response/patchset.rsp

5. When the installation completes, log in as the root user and run the
root.sh script:
su - root
password:
/opt/oracle/11g/root.sh

86
 Chapter 5 Oracle database configuration
5.1 Creating the Oracle listener using a Response File
To configure and start an Oracle Net listener on the system, configure naming meth-
ods, and configure Oracle Net service names run Net Configuration Assistant in silent
mode . To run Net Configuration Assistant in silent mode, edit a response file tem-
plate. Oracle provides a response file template named netca.rsp in the response dir-
ectory /tmp/db11106/response .
To run Net Configuration Assistant using a response file:

1. Open the response file in a text editor:

vi /tmp/db11106/response/netca.rsp

Change the variables in the netca.rsp response file to the following values:

SHOW_GUI=false

2. Log in as the Oracle software owner user (in this case oracle ).

3. Run the network configuration assistent using the netca.rsp response file:
Execute the following command to start the oracle universal installer:
/opt/oracle/11g/bin/netca /silent /responsefile /tmp/db11106/response/netca.rsp

Wait until the installation is finished.

If any errors occur, refer to
Oracle® Database Installation Guide 11g Release 1 (11.1) for Linux
Part Number B32002-06:
http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/toc.htm

87
 5.1.1 Verifying the created listener
To verify the created listener:

1. log in with a separate session as user oracle.

2. and execute the following command:

lsnrctl status

The output will be like:

LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 30-APR-2009 15:45:36

Copyright (c) 1991, 2008, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1523)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.7.0 -
Production
Start Date 30-APR-2009 15:45:30
Uptime 0 days 0 hr. 0 min. 5 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/11g/network/admin/listener.ora
Listener Log File
/opt/oracle/diag/tnslsnr/W6201L3O/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)
(HOST=W6201L3O.boeblingen.de.ibm.com)(PORT=1521)))
The listener supports no services
The command completed successfully

88
 5.2 Creating the WebSphere Process Server database
Start the database configuration assistant by executing the
/opt/oracle/11g/bin/dbca command as user oracle to create the WebSphere
Process Server database.

Note: When X11 content is forwarded to a Windows system using an outdated

X-Windows terminal emulators (or X Server)), the Oracle installation wizard
may be displayed incorrectly. It is highly recommended to use one of the latest
X Servers, for example the open source.Xming 6.9.0.23

For more information about Xming refer to

http://sourceforge.net/projects/xming.

The "Operations" panel is displayed:

1. Select "Create aDatabase"

2. Press the Next button.

89
The “Database Templates” panel is displayed:

1. By default there are three database templates. Select the “Custom Data-
base”.

2. Press the Next button.

90
The “Database Identification” panel is displayed:

1. Specify the “Global Database Name and the System ID (SID).

The “Global Database Name” usually consists of the SID followed by the data-
base domain.
The hostname of the database will be used as the database domain.
For example the database with the SID “ORCL” on host “hostname” would get
the Global Database Name “ORCL.hostname”

2. Press the Next button.

91
The “Management Options” panel is displayed:

1. Select “Configure Enterprise Manager” to add the Oracle Enterprise Reposit-

ory to the database.
It is recommended to choose this option unless Oracle Grid Control which is
the Oracle Enterprise Infrastructure for managing multiple databases is used.
This will make database monitoring and tuning in the future much more easier
and comfortable.

2. Press the Next button.

92
The “Database Credentials” panel is displayed:

1. Select “Use the Same Administrative Password for All Account” and type in
a preferred password.

2. Press the Next button.

93
The “Storage Options” panel is displayed:

The Oracle storage options:

File System is the simplest way and only a little slower as the other mechan-
isms.
Automatic Storage Management (ASM) is new since Oracle 10g. Using ASM
oracle accesses directly to the devices. In contrast to “Raw Devices” the disk
space is managed by oracle.
Raw Devices have the advantage, that Oracle accesses directly to the raw
partitions or volumes without having the operating system as indirection. The
administration is very extensive, because a raw device needs to be created
each datafile, control file, and log file that is planed to be created.

1. Select “File System” as the storage option.

2. Press the Next button.

94
The “Database File Locations” panel is displayed:

Oracle Database File Location options:

“Database File Locations from Template” gives the most control over the
location where the database files will be created.

Choosing “Common Location for All Database Files”, will create all data-
base files in the same directory.

The mechanism of "Oracle-Managed Files" means, that Oracle is creating all

database files in the database area. The database area is a simple directory.
All database files will be created in that directory. In contrast to the “Common
Location” Oracle assigns the name of the database files. This could be an ad-
vantage if a database file is often added to a tablespace. Simply the ta-
blespace and the size have to be specified. Selecting “Multiplex redo logs
and Control Files” stores a copy of all redo log files and a control file in the
Flash Recovery Area. This area was introduced with Oracle 10g.

1. Select “Use Database File Locations from Template”.

2. Press the Next button.

95
The "Recovery Configuration" panel is displayed:

Flash Recovery Area is not needed if archiving is disabled and/or redo logs and
control files are not multiplexed.

1. Deselect “Specify Flash Recovery Area”

2. Press the Next button.

96
The "Database Content" panel is displayed:

1. Deselect all database components except of “Enterprise Manager Reposit-

ory”

2. Press the Standard Database Components button.

97
The "Standard Database Components" panel pops up:

1. Deselect all standard database components except of “Oracle JVM”.

2. Press the OK button.

The "Standard Database Components" is closed and the "Database Content"

panel gets the focus back:

1. Press the Next button.

98
The "Initialization Parameters" panel with open "Memory" tab is displayed:

The memory management parameters options are:

"Typical" defines one memory size for both the System Global Area (SGA)
and the Program Global Area (PGA) in one value and splits it automatically into
SGA and PGA.

"Custom" defines the SGA and PGA memory size separately. The SGA size
can not be set higher than defined in the kernel parameter kernel.shmmax.

1. Select “Custom” and type in the chosen SGA and PGA memory size.

2. Select the Sizing tab.

Note: When choosing the SGA and PGA size make sure, that the database host
has enough memory and will not start swapping. Swapping will extremely slow
the database.
Please also refer to the Oracle Installation Guide for Linux.

99
The "Initialization Parameters" panel with open "Sizing" tab is displayed:

On the “Sizing” tab increase the number of processes. This parameter limits
the number of parallel database connections if “Dedicated Server” is used as
connection mode. It depends on the BPEL application and the number of pro-
cess instances that are running in parallel.

1. Change the processes from 150 to 500 as first initial tuning action.

2. Select the Character Sets tab.

100
The "Initialization Parameters" panel with open "Character Sets" tab is dis-
played:

WebSphere Process Server needs a UTF8 database as a data store.

1. Select “Use Unicode (AL32UTF8)

2. Press the All Initialization Parameters button.

101
The "All Initialization Parameters" panel pops up:

1. Press the Show Advanced Parameters button.

2. Change the Parameters as shown in the Table on the next side.
3. Press the Close button.

102
 new
Parameter default Remark
value
OPEN_CURSORS 300 1000 Specifies the maximum number of open
cursors (context areas) a session can
have at once, and constrains the PL/SQL
cursor cache size which PL/SQL uses to
avoid reparsing statements re-executed
by a user. Set this value high enough to
prevent your applications from running
out of open cursors.
SESSION_CACHED_CURSORS 50 1000 Specifies the number of session cursors
to cache. When the same SQL statement
is parses several times, it’s session
cursor is moved into the session cursor
cache.
FAST_START_MTTR_TARGET 900 This parameter specifies the mean time
in seconds that the database should be
able to recover if a crash occurs.
Possible values are from 0 to 3600.

The "All Initialization Parameters" is closed and the "Initialization Parameters"

panel gets the focus back:

1. Select the Connection Mode tab.

103
The "Initialization Parameters" panel with open "Connection Mode" tab is dis-
played:

1. Verify that "Dedicated Server Mode" is selected.

2. Press the Next button.

104
The "Security Settings" panel is displayed:

1. Select “Keep the enhanced 11g default security settings”.

2. Press the Next button.

105
The "Automatic Maintenance Tasks" panel is displayed:

Oracle 11g has the possibility to run scheduled maintenance tasks like com-
pute statistics and table space advisor.

1. Select “Enable automatic maintenance tasks”.

2. Press the Next button.

106
The "Database Storage" panel is displayed:

The default size of the database files of the tablespaces is too small; increase
the sizes to the following values:
SYSAUX 500 MB
SYSTEM 700 MB
TEMP 200 MB
UNDOTBS1 1500 MB
USERS 150 MB

1. Select the tablespace SYSAUX.

107
1. Select the datafile.

2. Press on the Pencil icon to edit the datafile.

108
The "Edit Datafile" panel pops up:

1. Change the file size to the value above.

2. Make sure that “M Bytes” is selected.

3. Press the OK button to confirm and save the changes.

109
The "Edit Datafile" is closed and the "Database Storage" panel gets the focus
back:

1. Repeat the last steps for the SYSTEM, TEMP, UNDOTBS1 and USERS table
spaces to increase the size as listed above.

110
Specify the size and the location of the redo log files. The optimal size depends
on the database load. To increase the performance of the database increase
the size at least to 1500 MByte. All redo log files should have the same size.

1. Select the first Redo Log Group.

111
1. Insert the value 1500 in the file size field.

2. Make sure that “M Bytes” is selected.

3. Select the two other Redo Log Groups one after the other and repeat the
steps.

112
1. Press the Next button.

The "Creation Options" panel is displayed:

1. Press the Finish button.

113
The "Confirmation" panel pops up:

1. Verify the configured Oracle database options.

2. Press the OK button.

114
The "Database Configuration Assistant" starts:

Wait until the database creation is finished.

115
1. Press the Exit button.

116
 5.3 Database listener configuration
Login as user oracle. Goto the directory /opt/oracle/11g/network/admin and verify
the settings in the file listener.ora:
# listener.ora Network Configuration File:
/opt/oracle/11g/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <your_hostname>)(PORT = 1521))
)
)
)

Make the necessary adjustments for the installation path und hostname.

The Oracle 11g listener needs the entry of an SID_LIST_LISTENER in the listerner.ora
file. Add the following lines to the listener.ora file:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORCL)
(ORACLE_HOME = /opt/oracle/11g)
)
)

The Oracle listener will discover the database instance ORCL automatically after a time
period of about 1 minute.

The file tnsnames.ora located in the same directory has also to be checked. Add the
following lines to the tnsnames.ora file if a similar entry is missing:
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <your_hostname>)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ORCL)
)
)

Change <your_hostname> to the name of your Oracle database host.

117
Restart the listener after changing the files.

Note: The commands to start and stop the listener are listed in the Oracle
Appendix in this document.

5.4 Configuring database initialization parameters

During the creation of the database the right initialization parameters were already
set.

Note: Skip this chapter if a new database was created during the Oracle install-
ation process and continue with chapter 5.5.Oracle JDBC driver.

Modify the initialization parameters for a existing database to match the “new value”
size as in the table below:

new
Parameter default Remark
value
OPEN_CURSORS 300 1000 Specifies the maximum number of open
cursors (context areas) a session can
have at once, and constrains the PL/SQL
cursor cache size which PL/SQL uses to
avoid reparsing statements re-executed
by a user. Set this value high enough to
prevent your applications from running
out of open cursors.
SESSION_CACHED_CURSORS 50 1000 Specifies the number of session cursors
to cache. When the same SQL statement
is parses several times, it’s session
cursor is moved into the session cursor
cache.
FAST_START_MTTR_TARGET 900 This parameter specifies the mean time
in seconds that the database should be
able to recover if a crash occurs.
Possible values are from 0 to 3600.
PROCESSES 150 500 This parameter limits the number of
parallel database connections if you are
using “Dedicated Server” as connection
mode. It depends on the BPEL
application and the number of process
instances that are running in parallel.

118
To change the parameters connect to the database ORCL as SYSDBA and use the
ALTER SYSTEM command. The following script can be used to change the database
initialization parameters.

Create a file setWPSOraInitParameter.sql with an editor and paste in the lines

from below.

REM
************************************************************************
REM File: setWPSOraInitParameter.sql
REM Date: 2009-01-15
REM
REM Desc: Set the initial Oracle database parameter for WPS.
REM
REM Usage: Execute the sql script as user oracle on the database
host.
REM
************************************************************************

ALTER SYSTEM SET OPEN_CURSORS=1000 SCOPE = spfile;

ALTER SYSTEM SET SESSION_CACHED_CURSORS=1000 SCOPE = spfile;
ALTER SYSTEM SET FAST_START_MTTR_TARGET=900 SCOPE = spfile;
ALTER SYSTEM SET PROCESSES=500 SCOPE = spfile;

REM Commit work

COMMIT;
EXIT

Execute the setWPSOraInitParameter.sql by typing the following command as

user oracle:

sqlplus sys/<yourPassword>@ORCL AS SYSDBA @setWPSOraInitParameter.sql

Stop and restart the database after changing the initialization parameters.

Note: How to start and stop the database please refer to the Oracle Appendix.

119
 5.5 Oracle JDBC driver
This chapter describes where to find the needed Oracle JDBC drivers.

1. Create the directory /opt/oracle/driver on the Deployment manager host and on

each WPS host.

2. Locate the jdbc driver files in the directory “$ORACLE_HOME/jdbc/lib” on the host
where Oracle was installed.

Note: WPS 7.0 will use the oracle JDK 1.6 drivers (ojdbc6.jar).

3. Copy all files from the lib directory into the directory /opt/oracle/driver on the
Deployment manager host and on each WPS and WBM host.

Note: If a non-root WPS installation is done, make sure the driver directory is
readable by the used WPS os user.

120
 Chapter 6 Creating Oracle users and tables
This chapter describes the creation of the Oracle users, tablespaces and tables for
WebSphere Process Server.

6.1 WebSphere Process Server tablespaces

This section describes how to create the Oracle tablespaces needed by WPS. WPS
provides a set of scripts that can be used to create mandatory tablespaces. It is
recommended to add additional tablespaces for the message engines and the common
db.

A SQL script to create the recommended tablespaces can be found in the Section
6.1.3 Create recommended tablespaces.

6.1.1 Predefined WPS tablespaces

The following tablespaces are defined in WPS database scripts for Oracle.

Tablespace Name WPS data

AUDITLOG Business Process Choreographer
INSTANCE Business Process Choreographer
STAFFQRY Business Process Choreographer
TEMPLATE Business Process Choreographer
WORKITEM Business Process Choreographer
LOBTS Business Process Choreographer
INDEXTS Business Process Choreographer
SCHEDTS Business Process Choreographer
OBSVRTS Business Process Choreographer Reporting Function
OBSVRLOB Business Process Choreographer Reporting Function
OBSVRIDX Business Process Choreographer Reporting Function
BSPACE Business Space
{CEIUSER}_cei_ts_extended Common Event Infrastructure
{CEIUSER}_cei_ts_base Common Event Infrastructure
{CEIUSER}_cei_ts_temp Common Event Infrastructure
{CEIUSER}_cei_ts_catalog Common Event Infrastructure
6.1.2 Recommended user default tablespaces
The following tablespaces are recommendations for WPS data without tablespace
definitions in the WPS database scripts.

Tablespace Name Description

WPS_COMMON_TBS Tablespace for the WPS Common Database.
WPS_MEAPP_TBS Tablespace for the SCA Application Message Engine
datastore.
WPS_MESYS_TBS Tablespace for the SCA System Message Engine
datastore.
WPS_MECEI_TBS Tablespace for the Common Event Infrastructure
Message Engine datastore.
WPS_MEBPC_TBS Tablespace for the Business Process Choreographer
Message Engine datastore.

Note: The tablespace names are also only recommendations. Changing the ta-
blespace name can be done in the 01createRecWPSOraTablespaces.sql script. If
the tablespace names are changed, remember to change them also in the sec-
tion 6.2 WebSphere Process Server users and privileges.

122
 6.1.3 Create recommended tablespaces
You can use the following script to create the recommended tablespaces from Section
6.1.2 Recommended user default tablespaces.
Create a file 01createRecWPSOraTablespaces.sql with the editor of your choice
and paste in the lines from below:
REM *******************************************************************
REM File: 01createRecWPSOraTablespaces.sql
REM Date: 2010-01-14
REM
REM Desc: Create all recommended tablespaces for WPS
REM
REM Usage:
REM 1. Define datafile paths as needed.
REM 2. Execute the sql script as user oracle on the database host.
REM *******************************************************************

REM Define Oracle datafile paths for WPS

Define WPS_TbsPath = "/opt/oracle/oradata/ORCL"

REM Define Oracle datafile paths for the Message Engines

Define MEAPP_TbsPath = "/opt/oracle/oradata/ORCL"
Define MESYS_TbsPath = "/opt/oracle/oradata/ORCL"
Define MECEI_TbsPath = "/opt/oracle/oradata/ORCL"
Define MEBPC_TbsPath = "/opt/oracle/oradata/ORCL"

REM *******************************************************************
REM Create the Oracle tablespace for WPS
CREATE TABLESPACE WPS_COMMON_TBS DATAFILE '&WPS_TbsPath/WPS_COMMON.dbf'
SIZE 150 M REUSE AUTOEXTEND ON NEXT 10 M;

REM *******************************************************************
REM Create the Oracle tablespace for the Message Engines
CREATE TABLESPACE WPS_MEAPP_TBS DATAFILE '&MEAPP_TbsPath/WPS_MEAPP.dbf'
SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M;
CREATE TABLESPACE WPS_MESYS_TBS DATAFILE '&MESYS_TbsPath/WPS_MESYS.dbf'
SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M;
CREATE TABLESPACE WPS_MECEI_TBS DATAFILE '&MECEI_TbsPath/WPS_MECEI.dbf'
SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M;
CREATE TABLESPACE WPS_MEBPC_TBS DATAFILE '&MEBPC_TbsPath/WPS_MEBPC.dbf'
SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M;

REM Commit work

COMMIT;
EXIT

123
Execute the 01createRecWPSOraTablespaces.sql by typing the following
command as user oracle:

sqlplus sys/<yourPassword>@ORCL AS SYSDBA @01createRecWPSOraTa-

blespaces.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 4 10:31:17 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Produc-
tion
With the Partitioning option
old 1: CREATE TABLESPACE WPS_COMMON_TBS DATAFILE '&WPS_TbsPath/WPS_COM-
MON.dbf' SIZE 150 M REUSE AUTOEXTEND ON NEXT 10 M
new 1: CREATE TABLESPACE WPS_COMMON_TBS DATAFILE
'/opt/oracle/oradata/ORCL/WPS_COMMON.dbf' SIZE 150 M REUSE AUTOEXTEND ON
NEXT 10 M
Tablespace created.
old 1: CREATE TABLESPACE WPS_MEAPP_TBS DATAFILE '&MEAPP_TbsPath/WPS_ME-
APP.dbf' SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M
new 1: CREATE TABLESPACE WPS_MEAPP_TBS DATAFILE
'/opt/oracle/oradata/ORCL/WPS_MEAPP.dbf' SIZE 100 M REUSE AUTOEXTEND ON
NEXT 10 M
Tablespace created.
old 1: CREATE TABLESPACE WPS_MESYS_TBS DATAFILE
'&MESYS_TbsPath/WPS_MESYS.dbf' SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M
new 1: CREATE TABLESPACE WPS_MESYS_TBS DATAFILE
'/opt/oracle/oradata/ORCL/WPS_MESYS.dbf' SIZE 100 M REUSE AUTOEXTEND ON
NEXT 10 M
Tablespace created.
old 1: CREATE TABLESPACE WPS_MECEI_TBS DATAFILE '&MECEI_TbsPath/WPS_ME-
CEI.dbf' SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M
new 1: CREATE TABLESPACE WPS_MECEI_TBS DATAFILE
'/opt/oracle/oradata/ORCL/WPS_MECEI.dbf' SIZE 100 M REUSE AUTOEXTEND ON
NEXT 10 M
Tablespace created.
old 1: CREATE TABLESPACE WPS_MEBPC_TBS DATAFILE '&MEBPC_TbsPath/WPS_MEBP-
C.dbf' SIZE 100 M REUSE AUTOEXTEND ON NEXT 10 M
new 1: CREATE TABLESPACE WPS_MEBPC_TBS DATAFILE
'/opt/oracle/oradata/ORCL/WPS_MEBPC.dbf' SIZE 100 M REUSE AUTOEXTEND ON
NEXT 10 M
Tablespace created.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

124
 6.2 WebSphere Process Server users and privileges
This section describes the Oracle database users needed for WebSphere Process
Server. A common database role with all needed privileges is also described.

Scripts for creating the database users and the common role are also provided in a
sub-section.

6.2.1 Needed WebSphere Process Server database users

The following database users are needed for WebSphere Process Server:

DB user Description
WPS_COMMONDB Common DB user
WPS_BPCDB BPC DB user
WPS_BPCOBS Observer DB user
WPS_CEIDB Common Event Infrastructure DB user
WPS_BSPACE BusinessSpace DB user
WPS_SCAAPPMSG SCA application message engine DB user
WPS_SCASYSMSG SCA system message engine DB user
WPS_CEIMSG Common Event Infrastructure message engine DB user
WPS_BPCMSG Business process choreographer message engine DB user
WPS_RECOVERY Oracle DB user with XA recovery privileges. (Optional)

125
 6.2.2 WebSphere Process Server database user roles
The following privileges are needed for every WebSphere Process Server database
user:

Role Description
CONNECT Enables a user to connect to the database. Grant this
role to any user or application that needs database
access. If you create a user using Oracle Enterprise
Manager Database Control, this role is automatically
granted to the user.
RESOURCE Enables a user to create, modify, and delete certain
types of schema objects in the schema associated with
that user. Grant this role only to developers and to other
users that must create schema objects. This role grants
a subset of the create object system privileges. For
example, it grants the CREATE TABLE system privilege,
but does not grant the CREATE VIEW system privilege.
It grants only the following privileges: CREATE CLUSTER,
CREATE INDEXTYPE, CREATE OPERATOR, CREATE
PROCEDURE, CREATE SEQUENCE, CREATE TABLE,
CREATE TRIGGER, CREATE TYPE. In addition, this role
grants the UNLIMITED TABLESPACE system privilege,
which effectively assigns a space usage quota of
UNLIMITED on all tablespaces in which the user creates
schema objects.
UNLIMITED TABLESPACE Permits a user to use an unlimited amount of any
tablespace in the database, grant the user the
UNLIMITED TABLESPACE system privilege. This
overrides all explicit tablespace quotas for the user. If
you later revoke the privilege, then explicit quotas again
take effect. You can grant this privilege only to users,
not to roles.

Note: WPS provides a jar-file to measure time differences in the BPC Observer.
In order to make use of this java utility a specific jar file is needed within oracle
(bpcodbutil.jar). To use this jar file the Oracle database needs to give the
WPS_BPCOBS user an additional user privilege. For further information please
refer to the WPS infocenter and the technote below.

javauserpriv technote:
http://www.ibm.com/support/docview.wss?uid=swg21377372

126
The WPS BPC database user will need the following additional privilege when using
query tables or during migration from WPS versions 6.1.2.x and lower:

Role Description
CREATE VIEW Enables a user to create a view in his own user schema.

This system privilege is commented out in the create WPS users script.

6.2.3 WebSphere Process Server XA recovery user privileges

This section describes the privileges for XA recovery needed by the WPS users in an
Oracle 11g (11.1.0.6/7) database. To enable recovery a custom WPS recovery role is
defined which encapsulates the needed XA privileges. This custom role is then
assigned to each WPS user or to the WPS_RECOVERY user.

The following table lists the required privileges for XA recovery:

Privileges Description
SELECT ON DBA_PENDING_TRANSACTIONS Used for XA recovery.
SELECT ON PENDING_TRANS$ Used for XA recovery.
SELECT ON DBA_2PC_PENDING Used for XA recovery.
EXECUTE ON DBMS_XA Used to execute XA recovery action
in the Oracle database.

6.2.3.1 Create WPS custom WPS_RECOVERY role

Create a file 02reateWPSrecoveryRole.sql with the editor of your choice and paste
in the lines from below:

REM *******************************************************************
REM File: 02createWPSrecoveryRole.sql
REM Date: 2010-01-14
REM
REM Desc: Create Oracle user role for WPS
REM
REM Usage:
REM 1. Execute the sql script as user oracle on the database host.
REM *******************************************************************

REM Create custom recovery role for WPS

CREATE ROLE WPS_RECOVERY_ROLE;
GRANT SELECT ON SYS.DBA_PENDING_TRANSACTIONS TO WPS_RECOVERY_ROLE;
GRANT SELECT ON SYS.PENDING_TRANS$ TO WPS_RECOVERY_ROLE;

127
GRANT SELECT ON SYS.DBA_2PC_PENDING TO WPS_RECOVERY_ROLE;
GRANT EXECUTE ON SYS.DBMS_XA TO WPS_RECOVERY_ROLE;

REM Commit work

COMMIT;
EXIT

128
Execute the 02createWPSrecoveryRole.sql by typing the following commands as
user oracle:

sqlplus sys/<yourPassword>@ORCL AS SYSDBA @02createWPSrecoveryRole.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 10:39:07 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Produc-
tion
With the Partitioning option
Role created.
Grant succeeded.
Grant succeeded.
Grant succeeded.
Grant succeeded.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

129
 6.2.4 Create WPS users and assign needed privileges and
roles
This section describes how to create the needed WPS database users: Once the
users exist the previously created role is assigned.

DB user Description Role(s) Privilege(s)

WPS_COMMONDB Common DB user CONNECT, RESOURCE,
QUOTA UNLIMITED ON
WPS_COMMON_TBS
WPS_BPCDB BPC DB user CONNECT, CREATE VIEW,
RESOURCE, UNLIMITED
TABLESPACE
WPS_BPCOBS Observer DB user CONNECT, RESOURCE,
UNLIMITED TABLESPACE
WPS_CEIDB Common Event Will be created from the CEI
Infrastructure DB user will database script.
be created during the CEI
database script execution.
WPS_BSPACE BusinessSpace DB user CONNECT, RESOURCE,
UNLIMITED TABLESPACE
WPS_SCAAPPMSG SCA application message CONNECT, RESOURCE,
engine DB user QUOTA UNLIMITED ON
WPS_MEAPP_TBS
WPS_SCASYSMSG SCA system message CONNECT, RESOURCE,
engine DB user QUOTA UNLIMITED ON
WPS_MESYS_TBS
PS_CEIMSG Common Event CONNECT, RESOURCE,
Infrastructure message QUOTA UNLIMITED ON
engine DB user WPS_MECEI_TBS
WPS_BPCMSG Business process CONNECT, RESOURCE,
choreographer message QUOTA UNLIMITED ON
engine DB user WPS_MEBPC_TBS
WPS_RECOVERY Oracle DB user with XA CONNECT
recovery privileges. WPS_REC DBA_PENDING_TRANSACTIO
(Optional) OVERY NS, PENDING_TRANS$,
DBA_2PC_PENDING,
DBMS_XA

You can use the following script to create the WPS database users from section 6.2.1
Needed WebSphere Process Server database users and grant the needed privileges
and roles to the WPS database users from the sections above:

• 6.2.2 WebSphere Process Server database user roles

• 6.2.3 WebSphere Process Server XA recovery user privileges

Create a file 03createWPSOraUser.sql with the editor of your choice and paste in
the lines from below:
REM *******************************************************************
REM File: 03createWPSOraUser.sql

130
REM Date: 2010-01-14
REM
REM Desc: Create all Oracle database user for WPS
REM
REM Usage:
REM 1. Define db user names
REM 2. Define db user passwords for all WPS user
REM 3. Optional: Adjust default tablespaces.
REM 4. Execute the sql script as user oracle on the database host.
REM *******************************************************************

REM Create user for WPS common db

CREATE USER WPS_COMMONDB IDENTIFIED BY <PASSWORD> DEFAULT TABLESPACE
WPS_COMMON_TBS;
GRANT CONNECT TO WPS_COMMONDB;
GRANT RESOURCE TO WPS_COMMONDB;
ALTER USER WPS_COMMONDB QUOTA UNLIMITED on WPS_COMMON_TBS;

REM Create user for SCA application message engine

CREATE USER WPS_SCAAPPMSG IDENTIFIED BY <PASSWORD> DEFAULT TABLESPACE
WPS_MEAPP_TBS;
GRANT CONNECT TO WPS_SCAAPPMSG;
GRANT RESOURCE TO WPS_SCAAPPMSG;
ALTER USER WPS_SCAAPPMSG QUOTA UNLIMITED on WPS_MEAPP_TBS;

REM Create user for SCA system message engine

CREATE USER WPS_SCASYSMSG IDENTIFIED BY <PASSWORD> DEFAULT TABLESPACE
WPS_MESYS_TBS;
GRANT CONNECT TO WPS_SCASYSMSG;
GRANT RESOURCE TO WPS_SCASYSMSG;
ALTER USER WPS_SCASYSMSG QUOTA UNLIMITED on WPS_MESYS_TBS;

REM Create user for CEI message engine

CREATE USER WPS_CEIMSG IDENTIFIED BY <PASSWORD> DEFAULT TABLESPACE WPS_ME-
CEI_TBS;
GRANT CONNECT TO WPS_CEIMSG;
GRANT RESOURCE TO WPS_CEIMSG;
ALTER USER WPS_CEIMSG QUOTA UNLIMITED on WPS_MECEI_TBS;

REM Create user for BPC message engine

CREATE USER WPS_BPCMSG IDENTIFIED BY <PASSWORD> DEFAULT TABLESPACE WPS_ME-
BPC_TBS;
GRANT CONNECT TO WPS_BPCMSG;
GRANT RESOURCE TO WPS_BPCMSG;
ALTER USER WPS_BPCMSG QUOTA UNLIMITED on WPS_MEBPC_TBS;

REM Create user for BPC data

CREATE USER WPS_BPCDB IDENTIFIED BY <PASSWORD>;
GRANT CONNECT TO WPS_BPCDB;

131
 GRANT RESOURCE TO WPS_BPCDB;
GRANT UNLIMITED TABLESPACE TO WPS_BPCDB;
REM GRANT CREATE VIEW TO WPS_BPCDB;

REM Create user for BPC Observer data

CREATE USER WPS_BPCOBS IDENTIFIED BY <PASSWORD>;
GRANT CONNECT TO WPS_BPCOBS;
GRANT RESOURCE TO WPS_BPCOBS;
GRANT UNLIMITED TABLESPACE TO WPS_BPCOBS;

REM Create user for Business Space data

CREATE USER WPS_BSPACE IDENTIFIED BY <PASSWORD>;
GRANT CONNECT TO WPS_BSPACE;
GRANT RESOURCE TO WPS_BSPACE;
GRANT UNLIMITED TABLESPACE TO WPS_BSPACE;

REM Commit work

COMMIT;
EXIT

Execute the 03createWPSOraUser.sql by typing the following commands as user

oracle:
sqlplus sys/<yourPassword>@ORCL AS SYSDBA @03createWPSOraUser.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 10:52:39 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Produc-
tion
With the Partitioning option
User created.
Grant succeeded.
Grant succeeded.
User altered.
User created.
Grant succeeded.
Grant succeeded.
User altered.
User created.
Grant succeeded.
Grant succeeded.
User altered.
User created.
Grant succeeded.
Grant succeeded.
User altered.
User created.
Grant succeeded.
Grant succeeded.
User altered.
User created.
Grant succeeded.

132
Grant succeeded.
Grant succeeded.
User created.
Grant succeeded.
Grant succeeded.
Grant succeeded.
User created.
Grant succeeded.
Grant succeeded.
Grant succeeded.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

133
 6.2.5 WPS XA recovery user(s)
In order to use distributed transactions (XA) with Oracle several privileges are re-
quired (see also 6.2.3 WebSphere Process Server XA recovery user privileges) for the
connecting db user.

Two approaches exist:

1. Create a specific recovery user with the required recovery privileges.

Pro: The privileges are encapsulated in one place. Only one user has
the XA recovery privileges.
Cons: Each datasource have to be altered. The XA authentication alias
has to be set explicitly.

2. Grant all connecting db users (WPS users) the required recovery privileges.
Pro: The authentication alias settings within the datasources do not
need to be altered.
Cons: XA privileges are spread across all users which might be a
potential security issue.

Scripts will be provided for both approaches. However this document describes
the first approach (specific recovery user) in detail.

6.2.5.1 Create specific XA recovery user

Create a file 04createWPSrecoveryUser.sql with the editor of your choice and
paste in the lines from below:

REM *******************************************************************
REM File: 04createWPSrecoveryUser.sql
REM Date: 2010-01-14
REM
REM Desc: Create WPS recovery database user for WPS
REM
REM Usage:
REM 1. Define db user names
REM 2. Define db user passwords for WPS recovery user
REM 3. Execute the sql script as user oracle on the database host.
REM *******************************************************************

REM Create WPS recovery user

CREATE USER WPS_RECOVERY IDENTIFIED BY <PASSWORD>;
GRANT CONNECT TO WPS_RECOVERY;

134
 GRANT WPS_RECOVERY_ROLE TO WPS_RECOVERY;

REM Commit work

COMMIT;
EXIT

Execute the 04createWPSrecoveryUser.sql by typing the following commands as

user oracle:

sqlplus sys/<yourPassword>@ORCL AS SYSDBA @04createWPSrecoveryUser.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 10:52:39 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Produc-
tion
With the Partitioning option
User created.
Grant succeeded.
Grant succeeded.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

6.2.5.2 Grant all needed db users the XA recovery privileges

Create a file 04BgrantWPSallUsersRecoveryPrivileges.sql with the editor of your
choice and paste in the lines from below:

REM *******************************************************************
REM File: 04BgrantWPSallUSersRecoveryPrivileges.sql
REM Date: 2010-01-14
REM
REM Desc: Grant all Oracle database user the XA recovery privileges.
REM
REM Usage:
REM 1. Define db user names
REM 2. Execute the sql script as user oracle on the database host.
REM *******************************************************************

GRANT WPS_RECOVERY_ROLE TO WPS_COMMONDB;

GRANT WPS_RECOVERY_ROLE TO WPS_BPCDB;
GRANT WPS_RECOVERY_ROLE TO WPS_BPCOBS;

REM Commit work

COMMIT;

135
 EXIT

Execute the 04BgrantWPSallUsersRecoveryPrivileges.sql by typing the following

commands as user oracle:

sqlplus sys/<yourPassword>@ORCL AS SYSDBA @04BgrantWPSallUsersRecoveryP-

rivileges.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 10:52:39 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Produc-
tion
With the Partitioning option
Grant succeeded.
Grant succeeded.
Grant succeeded.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

136
 6.3 WebSphere Process Server tables
This chapter describes how to create the different WebSphere Process Server tables in
the Oracle database.

6.3.1 Create CommonDB tables

1. Navigate to the root folder (/) and create a folder dbDesignFiles on the
deployment manager host, in this case the host
w70l3dmg.boeblingen.de.ibm.com.
2. Switch to the created folder dbDesignFiles and execute the following command
as user root:

/WPS70/util/dbUtils/DbDesignGenerator.sh

WSVR0615W: The user.install.root system property is not set. Some product

classes might not be found.
[info] running DbDesignGenerator in interactive mode...
[info] Enter 'q' to quit without saving; '-' for back to previous menu;
'?' for help at any time.
[info] To accept the given default values, simply press the 'Enter' key.
[info] Please pick one of the following [design option(s)] :
(1)Create a database design for Standalone profile or Deployment Environ-
ment
(2)Create a database design for a single component (e.g. BPC, CEI etc)
(3)Edit an existing database design
(4)Generate database scripts from a database design
(5)exit [q]

Please enter the number for the design option : 2

[info] Please pick one of the following [component(s)] :

(1)bpc
(2)bpcreporting
(3)bspace
(4)cei
(5)commondb
(6)sibme

Please enter the number for the component :5

[info] Please pick one of the following [database type(s)] :

(1)DB2-distributed
(2)DB2-iSeries
(3)DB2-zOS-8
(4)DB2-zOS-9
(5)Derby-embedded
(6)Derby-networkServer
(7)Informix
(8)Oracle
(9)SQL Server

Please enter the number for the database type :8

[info] Please enter the values for the properties in the database objects
section.

137
Database name(SID)[default=WPRCSDB] :ORCL
Database User name[default=] :WPS_COMMONDB
Database schema[default=] :WPS_COMMONDB
System user name(this is required ONLY for creating the database as a part
of standalone profile creation.)[default=] :[Enter]
System password(this is required ONLY for creating the database as a part
of standalone profile creation.)[default=] :[Enter]
Database Location(this is required ONLY for creating the database as a
part of standalone profile creation.)[default=] :[Enter]

[info] You have completed database objects section properties needed for
database scripts generation.

To skip data source properties, enter 's'; or enter anything else to con-
tinue :s

[info] data source properties section is skipped.

generate database scripts? (y/n) [default=y] :

Please enter the output directory for CommonDB [default=Oracle-CommonDB] :

[info] The script(s) have been generated in /dbDesignFiles/Oracle-CommonDB

[info] thanks, quitting now …

# ll

total 12
-rw-r--r-- 1 root root 1346 Jan 15 14:29 CommonDB_Oracle.properties
-rw-r--r-- 1 root root 3521 Jan 15 14:29 dbDesignGenerator.log
drwxr-xr-x 2 root root 4096 Jan 15 14:29 Oracle-CommonDB

3. Create a directory on the Oracle database host, e.g. /home/oracle/commondb

4. Copy the Oracle-CommonDB directory and all files inside from the dbDesignFiles
directory to the created directory on the Oracle database host, in this case the
host w70l3ora.boeblingen.de.ibm.com.

5. Start the CommonDB scripts in the created directory on the Oracle host by ex-
ecuting the following command as user oracle:

# ./configCommonDB.sh

SQL*Plus: Release 11.1.0.7.0 - Production on Fri May 6 12:55:04 2009

Copyright (c) 1982, 2008, Oracle. All privileges reserved.

Enter Oracle Password: <password for WPS_CONNODB user>

Connected.
Table created.
Table altered.
Index created.
Table created.
Table altered.

138
 Index created.
Table created.
Table altered.
Index created.
Table created.
Table altered.
Index created.
...
Sequence created.
Sequence created.
Sequence created.
Sequence created.
Table created.
Table altered.
Table created.
Table created.
Table created.
Table created.
Table created.
1 row created.
Table created.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

6.3.2 Create BPCDB tables

1. Switch to the folder dbDesignFiles that was created in the previous chapter and
execute the following command as user root:

/WPS70/util/dbUtils/DbDesignGenerator.sh

[info] running DbDesignGenerator in interactive mode...

[info] Enter 'q' to quit without saving; '-' for back to previous menu;
'?' for help at any time.
[info] To accept the given default values, simply press the 'Enter' key.

[info] Please pick one of the following [design option(s)] :

(1)Create a database design for Standalone profile or Deployment

Environment
(2)Create a database design for a single component (e.g. BPC, CEI etc)
(3)Edit an existing database design
(4)Generate database scripts from a database design
(5)exit [q]

Please enter the number for the design option :2

[info] Please pick one of the following [component(s)] :

(1)bpc
(2)bpcreporting
(3)bspace
(4)cei

139
(5)commondb
(6)sibme

Please enter the number for the component :1

[info] Please pick one of the following [database type(s)] :

(1)DB2-distributed
(2)DB2-iSeries
(3)DB2-zOS-8
(4)DB2-zOS-9
(5)Derby
(6)Informix
(7)Oracle
(8)SQL Server

Please enter the number for the database type :7

[info] Please enter the values for the properties in the database objects
section.

[info] Please pick one of the following [scenario(s)] :

(1)Configuration
(2)Migration
(3)Removal

Please enter the number for the scenario [default=Configuration] :1

Database name (SID)[default=BPEDB] :ORCL

Database schema name / user (leave empty to use implicit schema)[default=]

:WPS_BPCDB
Password for database schema user[default=] :<password>
Use tablespaces (true/false)?[default=true] :
Tablespace directory (only needed when using tablespaces)[default=]
:/opt/oracle/oradata/ORCL
Tablespace for audit log items (leave default when not using tablespaces)
[default=AUDITLOG] :
Tablespace for indexes for all tables (leave default when not using
tablespaces)[default=INDEXTS] :
Tablespace for instance items (leave default when not using tablespaces)
[default=INSTANCE] :
Tablespace for large objects for all tables (leave default when not using
tablespaces)[default=LOBTS] :
Tablespace for scheduler items (leave default when not using tablespaces)
[default=SCHEDTS] :
Tablespace for staff query items (leave default when not using
tablespaces)[default=STAFFQRY] :
Tabplespace for template items (leave default when not using tablespaces)
[default=TEMPLATE] :

140
Tablespace for work item tables and indexes (leave default when not using
tablespaces)[default=WORKITEM] :

[info] You have completed database objects section properties needed for
database scripts generation.

To skip data source properties, enter 's'; or enter anything else to

continue :s

[info] data source properties section is skipped.

Please enter the output directory [default=/dbDesignFiles] :

Please enter the output filename [default=BPC_Oracle.properties] :

[info] The database design has been generated

in/dbDesignFiles/BPC_Oracle.properties

generate database scripts? (y/n) [default=y] :

Please enter the output directory for BPC [default=Oracle-BPC] :

[info] The script(s) have been generated in /dbDesignFiles/Oracle-BPC

[info] thanks, quitting now ...

# ll

-rw-r--r-- 1 root root 1892 Feb 26 10:38 BPC_Oracle.properties

-rw-r--r-- 1 root root 1346 Jan 15 14:29 CommonDB_Oracle.properties
-rw-r--r-- 1 root root 2999 Feb 26 10:38 dbDesignGenerator.log
drwxr-xr-x 2 root root 4096 Feb 26 10:38 Oracle-BPC
drwxr-xr-x 2 root root 4096 Jan 15 14:29 Oracle-CommonDB

2. Create a directory on the Oracle database host, e.g. /home/oracle/bpcdb

3. Copy the Oracle-BPC directory and all files inside from the dbDesignFiles
directory to the created directory on the Oracle database host, in this case the
host w70l3ora.boeblingen.de.ibm.com.

4. Start the BPCDB scripts in the created directory on the Oracle host by
executing the following command as user oracle:
sqlplus sys/<password>@ORCL AS SYSDBA @createTablespace.sql

141
 SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 26 10:58:47 2010

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace created.

Disconnected from Oracle Database 11g Enterprise Edition Release

11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

sqlplus sys/<password>@ORCL AS SYSDBA @createSchema.sql

...
Table created.
Table created.
Table created.
Index created.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0 - 64bit Production
With the Partitioning option

6.3.3 Create BPC Explorer Reporting Function tables

1. Switch to the folder dbDesignFiles that was created in the previous chapter and
execute the following command as user root:

/WPS70/util/dbUtils/DbDesignGenerator.sh

142
[info] running DbDesignGenerator in interactive mode...

[info] Enter 'q' to quit without saving; '-' for back to previous menu;
'?' for help at any time.
[info] To accept the given default values, simply press the 'Enter' key.

[info] Please pick one of the following [design option(s)] :

(1)Create a database design for Standalone profile or Deployment

Environment
(2)Create a database design for a single component (e.g. BPC, CEI etc)
(3)Edit an existing database design
(4)Generate database scripts from a database design
(5)exit [q]

Please enter the number for the design option :2

[info] Please pick one of the following [component(s)] :

(1)bpc
(2)bpcreporting
(3)bspace
(4)cei
(5)commondb
(6)sibme

Please enter the number for the component :2

[info] Please pick one of the following [database type(s)] :

(1)DB2-distributed
(2)DB2-iSeries
(3)DB2-zOS-8
(4)DB2-zOS-9
(5)Derby
(6)Oracle

Please enter the number for the database type :6

[info] Please enter the values for the properties in the database objects
section.

[info] Please pick one of the following [scenario(s)] :

(1)Configuration
(2)Removal

Please enter the number for the scenario [default=Configuration] :1

Database name (SID)[default=BPEDB] :ORCL
Database schema name / user (leave empty to use implicit schema)[default=]
:WPS_BPCOBS
Password for database schema user[default=] :<password>

143
Use tablespaces (true/false)?[default=true] :
Tablespace directory (only needed when using tablespaces)[default=]
:/opt/oracle/oradata/ORCL
Tablespace for Reporting function indexes (leave default when not using
tablespaces)[default=OBSVRIDX] :
Tablespace for Reporting function large objects (leave default when not
using tablespaces)[default=OBSVRLOB] :
Tablespace for Reporting function tables (leave default when not using
tablespaces)[default=OBSVRTS] :

[info] You have completed database objects section properties needed for
database scripts generation.

To skip data source properties, enter 's'; or enter anything else to

continue :s

[info] data source properties section is skipped.

Please enter the output directory [default=/dbDesignFiles] :

Please enter the output filename

[default=BPCReporting_Oracle.properties] :

[info] The database design has been generated

in/dbDesignFiles/BPCReporting_Oracle.properties

generate database scripts? (y/n) [default=y] :

Please enter the output directory for BPCReporting [default=Oracle-

BPCReporting] :

[info] The script(s) have been generated in /dbDesignFiles/Oracle-

BPCReporting
[info] thanks, quitting now ...

# ll

total 28
-rw-r--r-- 1 root root 1892 Feb 26 10:38 BPC_Oracle.properties
-rw-r--r-- 1 root root 1760 Feb 26 11:04 BPCReporting_Oracle.properties
-rw-r--r-- 1 root root 1346 Jan 15 14:29 CommonDB_Oracle.properties
-rw-r--r-- 1 root root 2544 Feb 26 11:04 dbDesignGenerator.log
drwxr-xr-x 2 root root 4096 Feb 26 10:38 Oracle-BPC
drwxr-xr-x 2 root root 4096 Feb 26 11:04 Oracle-BPCReporting
drwxr-xr-x 2 root root 4096 Jan 15 14:29 Oracle-CommonDB

2. Create a directory on the Oracle database host, e.g. /home/oracle/reportingdb

144
 3. Copy the Oracle-BPCReporting directory and all files inside from the
dbDesignFiles directory to the created directory on the Oracle database host, in
this case the host w70l3ora.boeblingen.de.ibm.com.

4. Start the BPCReportingDB scripts in the created directory on the Oracle

host by executing the following command as user oracle:
sqlplus sys/<password>@ORCL AS SYSDBA @createTablespace_Observer.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 26 11:11:35 2010

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

Tablespace created.

Tablespace created.

Tablespace created.

Disconnected from Oracle Database 11g Enterprise Edition Release

11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

sqlplus sys/<password>@ORCL AS SYSDBA @createSchema_Observer.sql

...
1 row created.
1 row created.
1 row created.
1 row created.
1 row created.
1 row created.
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.6.0 - 64bit Production
With the Partitioning option

6.3.4 Create Business Space tables

1. Switch to the folder dbDesignFiles that was created in the previous chapter and
execute the following command as user root:

/WPS70/util/dbUtils/DbDesignGenerator.sh

[info] running DbDesignGenerator in interactive mode...

145
[info] Enter 'q' to quit without saving; '-' for back to previous menu;
'?' for help at any time.
[info] To accept the given default values, simply press the 'Enter' key.

[info] Please pick one of the following [design option(s)] :

(1)Create a database design for Standalone profile or Deployment

Environment
(2)Create a database design for a single component (e.g. BPC, CEI etc)
(3)Edit an existing database design
(4)Generate database scripts from a database design
(5)exit [q]

Please enter the number for the design option :2

[info] Please pick one of the following [component(s)] :

(1)bpc
(2)bpcreporting
(3)bspace
(4)cei
(5)commondb
(6)sibme

Please enter the number for the component :3

[info] Please pick one of the following [database type(s)] :

(1)DB2-distributed
(2)DB2-iSeries
(3)DB2-zOS-8
(4)DB2-zOS-9
(5)Derby-embedded
(6)Derby-networkServer
(7)Oracle
(8)SQL Server

Please enter the number for the database type :7

[info] Please enter the values for the properties in the database objects
section.

Database name (SID)[default=BSPACE] :ORCL

Database user name[default=] :WPS_BSPACE
Database schema name (must match the user name)[default=WPS_BSPACE]
:WPS_BSPACE
Prefix for tablespace names (0-4 characters)[default=BSP] :
Directory or file name prefix for tablespace files[default=BSP]
:/opt/oracle/oradata/ORCL/

[info] You have completed database objects section properties needed for
database scripts generation.

146
To skip data source properties, enter 's'; or enter anything else to
continue :s

[info] data source properties section is skipped.

Please enter the output directory [default=/dbDesignFiles] :

Please enter the output filename [default=BSpace_Oracle.properties] :

[info] The database design has been generated

in/dbDesignFiles/BSpace_Oracle.properties

generate database scripts? (y/n) [default=y] :

Please enter the output directory for BSpace [default=Oracle-BSpace] :

[info] The script(s) have been generated in /dbDesignFiles/Oracle-BSpace

[warning] 1 potential problems are found in the scripts. They are

DB_PASSWORD @ line 35 in file createSchema.sql
[info] thanks, quitting now ...

# ll

total 36
-rw-r--r-- 1 root root 1892 Feb 26 10:38 BPC_Oracle.properties
-rw-r--r-- 1 root root 1760 Feb 26 11:04 BPCReporting_Oracle.properties
-rw-r--r-- 1 root root 1258 Feb 26 11:58 BSpace_Oracle.properties
-rw-r--r-- 1 root root 1346 Jan 15 14:29 CommonDB_Oracle.properties
-rw-r--r-- 1 root root 2193 Feb 26 11:58 dbDesignGenerator.log
drwxr-xr-x 2 root root 4096 Feb 26 10:38 Oracle-BPC
drwxr-xr-x 2 root root 4096 Feb 26 11:04 Oracle-BPCReporting
drwxr-xr-x 2 root root 4096 Feb 26 11:58 Oracle-BSpace
drwxr-xr-x 2 root root 4096 Jan 15 14:29 Oracle-CommonDB

2. Create a directory on the Oracle database host, e.g. /home/oracle/bspacedb

3. Copy the Oracle-BSpace directory and all files inside from the dbDesignFiles
directory to the created directory on the Oracle database host, in this case the
host w70l3ora.boeblingen.de.ibm.com.

4. Start the BSpace scripts in the created directory on the Oracle host by
executing the following command as user oracle:
sqlplus sys/<password>@ORCL AS SYSDBA @createTablespace.sql

147
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 26 12:08:28 2010

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

Tablespace created.

SQL> alter user WPS_BSPACE default tablespace BSPREGTABSPACE;

User altered.

SQL> commit;

Commit complete.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release

11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

sqlplus sys/<password>@ORCL AS SYSDBA @createTables_BusinessSpace.sql

SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 26 12:20:36 2010

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

Tablespace created.

User altered.

Table created.

Grant succeeded.

148
SQL> commit;

Commit complete.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release

11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

sqlplus sys/<password>@ORCL AS SYSDBA @createTable.sql

...

Index created.

Index created.

Index created.

Index created.

Index created.

Index created.

Index created.

Index created.

1 row created.

SQL> commit;

Commit complete.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release

11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

149
Part IV Profile Creation

150
 Chapter 7 Create deployment manager profile
7.1 Create the profile
The creation of the profile has to be executed on the deployment manager machine, in
this case the machine W70L3DMG. In our case this step was executed with root user
id. In a production system this step will be done as non-root user.
The first step in building up a WPS cell or cluster is creating a deployment manager
profile. The deployment manager is used to manage the whole cell later on. To create
a deployment manager profile there are two options:

- graphical creation via profile creation tool. (Only available on 32 -bit, on 64-bit
you must use the silent mode)
- silent creation (via response files, as described in this chapter)

You find more information on how to create a profile in both ways by inspecting the
information provided here:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.webs
phere.wps.doc/doc/tins_creating_profiles.html

The parameters we need for silently creating the Deployment Manager profile are
shown below:

create
profileName Dmgr01
profilePath /WPS70/profiles/Dmgr01
hostName w70l3dmg.boeblingen.de.ibm.com
cellName Cell01
nodeName w70l3dmgCellManager01
serverType DEPLOYMENT_MANAGER
ndtopology false
enableAdminSecurity true
adminUserName vmmuser
adminPassword <yourAdminUserPwd>
dbDesignEnabled true
dbDelayConfig true
enableService false
personalCertDN
cn=w70l3dmg.boeblingen.de.ibm.com\\,ou=Cell01\\,ou=w70l3dmgCellManager01\\
,o=IBM\\,c=US
signingCertDN cn=w70l3dmg.boeblingen.de.ibm.com\\,ou=Root
Certificate\\,ou=Cell01\\,ou=w70l3dmgCellManager01\\,o=IBM\\,c=US
personalCertValidityPeriod 1
wbidbDesign /dbDesignFiles/CommonDB_Oracle.properties
signingCertValidityPeriod 15

151
 keyStorePassword <yourKeyStorePwd>
templatePath /WPS70/profileTemplates/dmgr.wbiserver

In order to create the deployment manager profile silently a response file which
contains the configuration information for the deployment manager needs to be
created. Navigate to the root folder (/) and create a folder profileRespFiles. In that
folder create file and name it dmgrRespFile.txt. Add the entries from the previous
page to that file, replace the placeholders with the correct values and then save the
file.

Navigate to /WPS70/bin and execute:

./manageprofiles.sh -response /profileRespFiles/dmgrRespFile.txt

INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult

/WPS70/profiles/Dmgr01/logs/AboutThisProfile.txt for more information
about this profile.

7.2 Verification
1. List existing profiles with the following command:

cd /WPS70/bin
./manageprofiles.sh -listProfiles

[Dmgr01]

2. Check the following files for return code “INSTCONFSUCCESS”:

cd /WPS70/logs/manageprofiles
grep INSTCONFSUCCESS W6201L3MBPMDmgr_create.log

<message>Returning with return code: INSTCONFSUCCESS</message>

<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please
consult /WPS70/profiles/Dmgr01/logs/AboutThisProfile.txt for more
information about this profile.</message>
<message>Returning with return code: INSTCONFSUCCESS</message>

152
 7.3 Start and configure the deployment manager
This chapter describes how to start the deployment manager the first time and access
the admin console to configure database settings for Oracle 11g.

1. Start the deployment manager entering the following command in profile directory
<install_root>profiles/Dmgr01/bin:

On w70l3dmg:
cd /WPS70/profiles/Dmgr01/bin
./startManager.sh

ADMU0116I: Tool information is being logged in file

/WPS70/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is xxxxxx

2. Check the logs (especially the SystemOut.log) in location

<install_root>/profiles/Dmgr01/logs/dmgr for errors.

3. Open a web browser and type in: http://<hostname>:9060/admin

Hint: Check the SystemOut.log of the deployment manager process to find out
the correct port for the admin_host. In our scenario the deployment manager
hostname is w70l3dmg.boeblingen.de.ibm.com.

4. Login to the admin console with the user vmmuser .

153
 7.3.1 Create the authentication alias for XA recovery

This chapter describes how to create the authentication alias for XA recovery. Oracle
need a special userid for recovery. For that we need to create an authentication alias
and set them on the datasources.

In the admin console navigate to:

Security
-> Global security
-> Java Authentication and Authorization Service
-> J2C authentication data
-> New

The "New" form is displayed:

1. Enter the Alias "WPS_Recovery_Auth_Alias"

2. Enter the User ID "WPS_RECOVERY".

3. Enter the password to match the User ID.

4. Click OK

Save and synchronize the changes.

154
 Please refer to the Appendix "Save changes and synchronize Nodes" how to do
this.

7.3.2 Change the data source for Oracle 11g

In the admin console navigate to:

Resources
-> JDBC
-> Data sources

The "Data sources" page is displayed:

1. Click WBI_DataSource

155
The "WBI_DataSource" page is displayed:

1. Select "Oracle11g data store helper".

2. Select "<hostname>/WPS_Recovery_Auth_Alias" for the "Authentication

alias for XA recovery"

3. Click Ok

Save and synchronize the changes.

156
In the "Data sources" page:

1. Repeat the steps above with the "ESBLoggerMediationDataSource".

Save and synchronize the changes.

157
 Chapter 8 Create custom profiles
NOTE: This step has to be executed on the machines hosting the servers of this
cluster, in our case this are the machines w70l3n01 and w70l3n02. Make sure to
execute this step with root user id.

8.1 Custom profile creation

The next step in the setup of a cell/cluster is to create profiles on the other machines
which should host the servers that are later on created in the cell. To create a WPS
profile there are two options:

- graphical creation via profile creation tool (Only available on 32 -bit, on 64-bit
you must use the silent mode)
- silent creation (via response files, as you have seen it in the prior chapter for
the deployment manager profile)

You find more information on how to create a profile in both ways by inspecting the
information provided here:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.web-
sphere.wps.doc/doc/tins_creating_profiles.html

Use the following configuration parameters to create the profiles Custom01(on

w70l3n01) and Custom02 (on w70l3n02):

For w70l3n01 (response rile parameters):

create
profileName Custom01
profilePath /WPS70/profiles/Custom01
hostName w70l3n01.boeblingen.de.ibm.com
cellName w70l3n01Node01Cell
nodeName w70l3n01Node01
ndtopology false
personalCertDN
cn=w70l3n01.boeblingen.de.ibm.com\\,ou=w70l3n01Node01Cell\\,ou=w70l3n01Nod
e01\\,o=IBM\\,c=US
signingCertDN cn=w70l3n01.boeblingen.de.ibm.com\\,ou=Root
Certificate\\,ou=w70l3n01Node01Cell\\,ou=w70l3n01Node01\\,o=IBM\\,c=US
personalCertValidityPeriod 1
signingCertValidityPeriod 15
keyStorePassword fm07test
dbType Oracle
dbJDBCClasspath /opt/oracle/driver
templatePath /WPS70/profileTemplates/managed.wbiserver

For w70l3n02 (response rile parameters):

158
 create
profileName Custom02
profilePath /WPS70/profiles/Custom02
hostName w70l3n02.boeblingen.de.ibm.com
cellName w70l3n02Node02Cell
nodeName w70l3n02Node02
ndtopology false
personalCertDN
cn=w70l3n02.boeblingen.de.ibm.com\\,ou=w70l3n02Node02Cell\\,ou=w70l3n01Nod
e02\\,o=IBM\\,c=US
signingCertDN cn=w70l3n02.boeblingen.de.ibm.com\\,ou=Root
Certificate\\,ou=w70l3n02Node02Cell\\,ou=w70l3n01Node02\\,o=IBM\\,c=US
personalCertValidityPeriod 1
signingCertValidityPeriod 15
keyStorePassword fm07test
dbType Oracle
dbJDBCClasspath /opt/oracle/driver
templatePath /WPS70/profileTemplates/managed.wbiserver

In order to create the custom profiles silently a response file which contains the
configuration information needs to be created. Navigate to the root folder (/) of the
w70l3n01 and w70l3n02 machines and create a folder profileRespFiles. In that
folder create a file and name it Custom01RespFile.txt (w70l3n01) and
Custom02RespFile.txt (w70l3n02). Add the parameters from above to that files,
then save the files.

On w70l3n01 and w70l3n02 execute the manage profiles command with the proper
response file to create the two custom profiles Custom01 , Custom02:

root:

on w70l3n01:
/WPS70/bin/manageprofiles.sh -response /profileRespFiles/Custom01Resp-
File.txt

INSTCONFSUCCESS: Success: Profile Custom01 now exists. Please consult

/WPS70/profiles/Custom01/logs/AboutThisProfile.txt for more information
about this profile.

on w70l3n02:
/WPS70/bin/manageprofiles.sh -response /profileRespFiles/Custom02Resp-
file.txt

INSTCONFSUCCESS: Success: Profile Custom02 now exists. Please consult

/WPS70/profiles/Custom02/logs/AboutThisProfile.txt for more information
about this profile.

Make sure the Deployment Manager on w70l3dmg is up and running. Then federate
the Custom01 and Custom02 nodes to the deployment manager:
root:

159
on w70l3n01:
cd /WPS70/profiles/Custom01/bin/
./addNode.sh w70l3dmg.boeblingen.de.ibm.com -username vmmuser
-password <password>

if all goes right, you should see the following output:

ADMU0116I: Tool information is being logged in file
/WPS70/profiles/Custom01/logs/addNode.log
ADMU0128I: Starting tool with the Custom01 profile
CWPKI0308I: Adding signer alias "CN=w70l3dmg.boeblingen.de.ibm.c" to local
keystore "ClientDefaultTrustStore" with the following SHA
digest:
8B:85:8D:C9:06:FC:FD:0F:F8:94:E3:4F:96:98:99:9A:26:30:C2:0E
CWPKI0308I: Adding signer alias "datapower" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17
ADMU0001I: Begin federation of node w70l3n01Node01 with Deployment Manager
at
w70l3dmg.boeblingen.de.ibm.com:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
w70l3dmg.boeblingen.de.ibm.com:8879
...

ADMU0003I: Node w70l3n01Node01 has been successfully federated.

on w70l3n02:
cd /WPS70/profiles/Custom02/bin/
./addNode.sh w70l3dmg.boeblingen.de.ibm.com -username vmmuser
-password <password>

160
if all goes right here, too, you should see the following output:
ADMU0116I: Tool information is being logged in file
/WPS70/profiles/Custom02/logs/addNode.log
ADMU0128I: Starting tool with the Custom02 profile
CWPKI0308I: Adding signer alias "CN=w70l3dmg.boeblingen.de.ibm.c" to local
keystore "ClientDefaultTrustStore" with the following SHA
digest:
8B:85:8D:C9:06:FC:FD:0F:F8:94:E3:4F:96:98:99:9A:26:30:C2:0E
CWPKI0308I: Adding signer alias "datapower" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17
ADMU0001I: Begin federation of node w70l3n02Node02 with Deployment Manager
at
w70l3dmg.boeblingen.de.ibm.com:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
w70l3dmg.boeblingen.de.ibm.com:8879
...
ADMU0003I: Node w70l3n02Node02 has been successfully federated.

8.2 Verify the custom profile creation

1. List existing profiles with the following command:

on w70l3n01:
cd /WPS70/bin/
./manageprofiles.sh -listProfiles

[Custom01]

on w70l3n02:
cd /WPS70/bin/
./manageprofiles.sh -listProfiles

[Custom02]

2. Check the following files for return code “INSTCONFSUCCESS”:

on w70l3n01:
cd /WPS70/logs/manageprofiles
grep INSTCONFSUCCESS Custom01_create.log

<message>Returning with return code: INSTCONFSUCCESS</message>

<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>INSTCONFSUCCESS: Success: Profile Custom01 now exists. Please
consult /WPS70/profiles/Custom01/logs/AboutThisProfile.txt for more
information about this profile.</message>
<message>Returning with return code: INSTCONFSUCCESS</message>

on w70l3n02:

161
 cd /WPS70/logs/manageprofiles
grep INSTCONFSUCCESS Custom02_create.log

<message>Returning with return code: INSTCONFSUCCESS</message>

<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>Returning with return code: INSTCONFSUCCESS</message>
<message>INSTCONFSUCCESS: Success: Profile Custom02 now exists. Please
consult /WPS70/profiles/Custom02/logs/AboutThisProfile.txt for more
information about this profile.</message>
<message>Returning with return code: INSTCONFSUCCESS</message>

Unlike the deployment manager profile creation, the creation of a WPS profile does not
create a startable server. The servers are created later on when the clusters are
created.

On both machines (w70l3n01 and w70l3n02) check the nodeagent logs.

These logs are located in:
• /WPS70/profiles/Custom01/logs/nodeagent
• /WPS70/profiles/Custom02/logs/nodeagent

Check that they do not contain any errors.

Further check the following files for errors:
• /WPS70/profiles/Custom01/logs/addNode.log
• /WPS70/profiles/Custom02/logs/addNode.log

Login to the deployment manager admin console and navigate to:

System Administration
-> Node agents.

162
Then verify existence and status of the node agents, they should have status "green":

Now we are ready to configure security and create the clusters.

163
 Chapter 9 Enable security
9.1 Configure Federated Repository
This step can be performed at any time after the deployment manager is up and
running. The chosen point of time is right here, to find potential errors in security
settings at an early stage.

WebSphere Process Server offers two approaches to use a Directory Server like IBM
Tivoli Directory Server (LDAP). The first one is using a standalone LDAP repository and
the second one is using a federated repository which will be presented in this
document.

Login to administrative console and navigate to:

Security  Global Security

164
The "Global Security" page is displayed:

1. Make sure that "Enable administrative security" is selected.

2. Make sure that "Enable application security" is selected.

3. Select "Federated repositories" in the drop-down-box.

4. Click Configure

165
The "Federated repositories Configuration" page is displayed:

1. Click Add Base entry to Realm...

The "Repository reference Configuration" page is displayed:

1. Click Add Repository...

166
The "Repository reference New" page is displayed:

1. Type in the Repository identifier in ths case "ldap".

2. Select "IBM Tivoli Directory Server" from the drop-down-box.

3. Type in the Primary host name (in our case this is "hobart.boeblingen.de.ib-
m.com")

4. Click Ok

167
The "Repository reference Configuration" page is displayed again:

1. Type in the DN for the realm (in our case this is "o=ibm,c=us")

2. Type in the DN for the base entry (in our case this is "o=ibm,c=us").

3. Click Ok

168
The "Federated repositories Configuration" page is displayed:

1. Check that the new realm entry is displayed

2. Click Ok

Save changes and synchronize Nodes.

Please refer to the Appendix "Save changes and synchronize Nodes" how to do
this.

169
 9.2 Enable identity assertion
In a clustered environment, userids have to be propagated across servers in the cell.
To support this, we have to enable "Identity assertation".

9.2.1 Enable inbound authentication

In the admin console navigate to:
Security
-> Global Security
-> Authentication: RMI/IIOP security
-> CSIv2 inbound authentication.

The "CSIv2 inbound authentication" page is displayed:

1. Check "Identity assertion".

2. Type in "*" in "Trusted identities".

3. Click Ok

Save changes and synchronize Nodes.

170
 9.2.2 Enable outbound authentication
In the admin console navigate to:

Security
-> Global security
-> Authentication: RMI/IIOP security
-> CSIv2 outbound authentication

The "CSIv2 outbound authentication" page is displayed:

1. Select "Identity assertion" and "Use server trusted identity".

2. Click Ok

Save changes and synchronize Nodes.

171
 9.3 Verification
To verify the enabled security stop the node agents and the deployment manager and
start them again.

Please refer to the Appendix "Start/stop the deployment manager and the node
agents" on how to start and stop the node agents and the deployment manager.

Then open the administrative console in the browser. When starting the administration
console you are prompted for user ID and password.

http://w70l3dmg.boeblingen.de.ibm.com:9060/admin

The "Login" page is displayed:

1. Type in the "user ID" in this case "vmmuser".

2. Type in the chosen password.

3. Click Log In

In the admin console verify that all node agents are shown up and running. Try to
synchronize the nodes to check that secure communication is working well. In the
Admin Console navigate to:

System administration
 Nodes

172
 Execute a Full Resynchronize:

1. Click Full Resynchronize

2. Check that the 2 nodes are displayed and are in the synchronized state
after the resynchronize.

If you do not see all node agents, you were maybe too fast starting the admin
console. Logout and login to the console again and check again.

If they are still missing, check the appropriate log files on the machines for errors at
startup and registering with the deployment manager:

w70l3dmg: /WPS70/profiles/Dmgr01/logs/dmgr
w70l3n01: /WPS70/profiles/Custom01/logs/nodeagent
w70l3n02: /WPS70/profiles/Custom02/logs/nodeagent

173
Part V Basic Cluster (ND7)

174
 Chapter 10 Create and configure the deployment
environment
With the deployment environment (DE) we will use a powerful tools that helps us in
creating our WPS Cluster topology. The DE will create all needed clusters and servers
on the cluster for us. Also the messaging and Business Process Choreographer
components are configured. We could do this also "by hand", but with DE we are
much faster.

10.1 Create the deployment environment

In the admin console, navigate to:
Servers
-> Deployment Environments

The Deployment Environments are displayed

1. Click New..

175
The "Create new deployment environment" page is displayed:

1. Select "Create a deployment environment based on a pattern"

2. Specify the Deployment environment name "WAS70DE"

3. Select "Detailed: Show all steps"

4. Click New

176
The "Create new deployment environment" page is displayed:

1. Select "WPS"

2. Next

The "Create new deployment environment" page is displayed:

1. Select "Remote Messaging and Remote Support" (this is the pattern on

which our DE will be created)

2. Next

177
The "Create new deployment environment" page is displayed:

1. Select the 2 nodes on w70l3n01, w70l3n02

2. Next

178
The "Create new deployment environment" page is displayed:

1. Make sure for each cluster type, "1" member per cluster and node is con-
figured

2. Next

179
The "Create new deployment environment" page is displayed:

1. Just leave blank, we will configure this later.

2. Next

180
The "Create new deployment environment" page is displayed:

1. Just leave blank

2. Next

181
The "Create new deployment environment" page is displayed:

1. Fill in the proper database users, schema names and passwords. Make sure
the Provider type "Oracle" is selected and the server hostname is correct.

2. Next

182
The "Create new deployment environment" page is displayed:

1. Make sure "vmmuser" is configured, retype the correct password for vm-
muser for each of the 3 components.

2. Next

183
The "Create new deployment environment" page is displayed:

1. Make sure "vmmuser" is configured, retype the correct password for vm-
muser for each of the 3 authentication points.

2. Uncheck the "Enable e-mail service" box (if you need the e-mail service of
the Human Task Manager component, you can configure it later)

3. Next

184
The "Create new deployment environment" page is displayed:

1. Leave the defaults for the URLs of these WebAppllications

2. Next

185
The "Create new deployment environment" page is displayed:

1. Verify the configuration summary

2. Click Finish and Generate Environmen

3. Click Save Changes

186
 10.2 Configure deployment environment

NOTE: Before doing the steps below restart the complete cell (Deployment
manager, both nodes)

NOTE: If you do any of the corrections explained below, you have to synchron-
ize and restart the whole cell also to make the changes work.

10.2.1 Configure/verify authentication aliases

In the admin console, navigate to

Security
-> Global security
-> Java authentication and authorization service
-> J2C authentication data

Verify that all authentication aliases are properly configured:

187
 1. Verify that BPC_Auth_Alias, SCA_Auth_Alias and CommonEventInfra-
structureJMSAuthAlias are correctly set to "vmmuser"

2. Verify that the other userids are also correct

3. If you are not sure if a password for a userid is correct, you can click the
authentication alias to change/re-enter the password (Note: you have to re-
start the complete cell to make changes work)

Save and synchronize the configuration

10.2.2 Configure/verify bus security

In the admin console, navigate to

Service integration
-> Buses

188
Verify bus security:

1. Verify that on all buses security is "Enabled"

189
Open the security panel for each bus by clicking the "Enabled" link. (Shown
here BPC bus). The "Security for bus BPC.Cell01.Bus page is displayed:

1. Verify that the "Inter-engine authentication alias" is set to

"BPC_Auth_Alias".

2. Verify that the "Mediations authentication alias" is set to "BPC_Auth_Alias".

3. Click Apply if you made any changes.

4. Click Users and groups in the bus connector role . The authenticated
users/groups on this bus are shown:

190
5. Verify that user "vmmuser" and the group "Server" is shown in the list.

Repeat the steps above for the two SCA buses (SCA.APPLICATION.Cell01.Bus
and SCA.SYSTEM.Cell01.Bus).Use SCA_Auth_Alias as the authentication alias
for the SCA buses.

Repeat the steps above also for the CEI bus (CEI.Cell01.Bus). Use the Com-
monEventInfrastructureJMSAuthAlias as the authentication alias for the
CEI bus.

Save and synchronize the configuration

191
 10.2.3 Configure/verify JDBC providers

In the admin console, navigate to

Ressources
-> JDBC
-> JDBC providers

Verify JDBC providers existence:

1. Verify that the JDBC providers shown above have been created.

192
Verify each JDBC providers, to do this click on each JDBC provider to open its
configuration panel (Sample Support cluster JDBC provider):

1. Verify that the "Class path" to "$

{ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar".

2. Verify that the "Implementation class name" is set to "oracle.jdbc.xa.cli-

ent.OracleXADataSource"

3. Click Ok

4. Repeat these steps for the other 3 datasources.

Save and synchronize the configuration

193
 10.2.4 Configure/verify data sources

In the admin console, navigate to

Ressources
-> JDBC
-> Data sources

Verify data sources functionality:

1. Select all datasources

2. Click Test connection

194
 3. After the test, you should see success messages for each datasource on top
of the page:

If you see error messages, check the failing datasource. Maybe the
authentication alias is not set correctly, or the configured authentication alias is
not properly configured (wrong userid or password).

Now we have to enssure, that the BPC, CommonDB, BPC Reporting and ESB data
sources have set the correct Recovery alias (WPS_RECOVERY) created on the data-
base. Remember that on Oracle we need a special permitted user for doing recovery
actions and it's crucial to set this user as the recovery user for the data sources.
In the admin console, navigate to

Ressources
-> JDBC
-> Data sources

195
Select "Business Process Choreographer data source", the datasource detail
page is displayed:

1. Check that the "Oracle11g data store helper" is selected.

2. Select "<hostname>/WPS_Recovery_Auth_Alias" as the "Authentication

alias for XA recovery

3. Click Ok

196
Repeat this step also for the following data sources:
- Business Process Choreographer reporting function source
- ESBLoggerMediationDataSource
- WBI_DataSource
- Business Space data source

Save and synchronize the configuration

197
 10.2.5 Configure/verify SCA configuration

In the admin console, navigate to

Servers
-> Cluster
-> WebSphere application server clusters
-> WAS70DE.Messaging
-> Service Component Architecture

Verify SCA functionality:

1. Verify that "Support the Service Component Architecture components" is

enabled (checked)

2. Verify that the "Bus Member Location" is set to "Local"

3. Verify that System and Application Bus Member database configuration

parameters.

4. If you made any changes, click Ok

198
In the admin console, navigate to

Servers
-> Cluster
-> WebSphere application server clusters
-> WAS70DE.AppTarget
-> Service Component Architecture

Verify SCA functionality:

1. Verify that "Support the Service Component architecture components" is

enabled (checked)

2. Verify that the "Bus Member Location" is set to "Remote"

3. Verify that the remote bus member location points to the "WAS70DE.Mes-
saging" cluster

4. If you made any changes, click Ok

Save and synchronize the configuration

199
 10.2.6 Configure/verify CEI configuration
CEI is a set of modular event processing components that deliver functions such as
event transport, event-bus distribution, event persistence, event subscription, event
updates and event queries. The following block chart depicts the event flow from the
event source to the CEI event server shows the involved components. The next
chapters describe the setup of these components:

(Image Source: SW360 “WebSphere Process Server High Availability, Tuning and Administration” Course Exercises)

The ORCL database contains the tables for the following Buses:
- SCA.SYSTEM.Cell01.Bus - WPS_SCASYSMSG
- SCA.APPLICATION.Cell01.Bus - WPS_SCAAPPMSG
- CommonEventInfrastructure_Bus - WPS_CEIMSG

First we check if CEI has been configured on the Support cluster. In the admin
console, navigate to

Servers
-> Cluster
-> WebSphere application server clusters
-> WAS70DE.Support
-> Common Event Infrastructure
-> Common Event Infrastructure Server

200
Verify CEI configuration

1. Verify that "Enable the event infrastructure server" is enabled (checked)

2. Verify that the "Common Event Infrastructure Bus Member Location" is set
to "Remote"

3. If you made any changes, click Ok

201
The next step is to verify, that the AppTarget cluster uses the CEI configuration on the
Support cluster. In the admin console, navigate to

Servers
-> Cluster
-> WebSphere application server clusters
-> WAS70DE.AppTarget
-> Common Event Infrastructure
-> Common Event Infrastructure Destination

Verify CEI configuration

1. Verify that "Enable service at server startup" is enabled (checked)

2. Verify that the "Event Infrastructure emitter factory JNDI name" points to
the
"cell/clusters/WAS70DE.Support/com/ibm/events/configuration/emitter/De-
fault"

3. If you made any changes, click Ok

An application (event source) sends events to the event server though an emitter
object. The emitter factory is used to create emitter objects and to define their
behavior (e.g. asynchronous transmission). To configure this behavior, navigate to:

Service Integration
-> Common Event Infrastructure
-> Event Emitter Factories
-> Default Common Event Infrastructure emitter

202
The "Default Common Event Infrastructure emitter" page is displayed:

In the Event transmission box the selections have the following meaning:
Support event service transmission - Indicates whether events are sent
directly to the event service before control is returned to the event source.
Support JMS transmission - Indicates whether events are sent to a JMS
queue and control returned to the event source before the event is returned to
the event source.
Prefer event service transmission - The transmission mode you want to
use by default when sending event to the event service. Indicates whether
events are sent to a JMS queue and control returned to the event source be-
fore the event is returned to the event source.

1. Deselect "Support event service transmission" and click Ok .

Save and synchronize the configuration

203
 10.2.7 Configure BPC Event Collector
During the deployment environment configuration, the BPC Event Collector application
has already been installed. For verification purposes it is recommended to modify
some settings, so that Event verification is easier. To do that, log in to the deployment
manager host as user root and execute the following commands to setup the event
collector application:

cd /WPS70/ProcessChoreographer/config

IMPORTANT NOTE: As a default, the BPC Event Collector is configured to start

transforming events at a 500 events threshold. As this is suitable for a produc-
tion environment, it isn’t for a test environment. You can change this threshold
after verification back to 500 by executing the setupEventCollector.sh script
again.

./setupEventCollector.sh -username vmmuser -password xxxxxxx

WASX7209I: Connected to process "dmgr" on node w70l3dmgCellManager01 using

SOAP connector; The type of process is: DeploymentManager
---------------------------------------------------------
Welcome to the WebSphere Business Process Choreographer Event Collector
setup!
--------------------------------------------------------------------------
Logfile is '/WPS70/profiles/Dmgr01/logs/setupEventCollector.log'.
Initializing ...

Commands Menu

1) Prepare a database for the Event Collector and reporting function

2) Install the Event Collector application
3) Remove the Event Collector application and related objects
4) Change configuration settings of an installed Event Collector
5) Drop the database schema of the Event Collector and reporting
function
6) Administer reporting function related user-defined functions

0) Exit Menu

Your selection: 4

==> Change configuration settings of an installed Event Collector

Select the deployment target where the application is installed:

1) Cluster 'WAS70DE.AppTarget'
2) Cluster 'WAS70DE.Messageing'
3) Cluster 'WAS70DE.Support'
0) Exit Menu

Your selection: [1] 3

==> Cluster 'WAS70DE.Support'

204
Retrieving the application configuration settings of application
'BPCECollector_WAS70DE.Support' ...

Enter the number of the configuration parameter you want to

change/display:
1) BPCEventTransformerEventCount
2) BPCEventTransformerMaxWaitTime
3) BPCEventTransformerToleranceTime
4) ObserverCreateTables
5) ObserverSchemaName
0) Exit Menu

Your selection: 1

Edit a configuration parameter.

Configuration parameter: BPCEventTransformerEventCount

Description: The number of events after which the Event
Collector sends a notification to the
Transformer.
Data type: Integer
Unit: Events
Current value is: '500'

Enter a new value. Press 'Enter' to exit.

Your selection: 20

==> Value for 'BPCEventTransformerEventCount' set to '20'.

Enter the number of the configuration parameter you want to

change/display:

1) BPCEventTransformerEventCount
2) BPCEventTransformerMaxWaitTime
3) BPCEventTransformerToleranceTime
4) ObserverCreateTables
5) ObserverSchemaName
0) Exit Menu

Your selection: 2

Edit a configuration parameter.

Configuration parameter: BPCEventTransformerMaxWaitTime

Description: Time in minutes after the Transformer is
notified
although the number of events is not reached.
Data type: Integer
Unit: Minutes
Current value is: '10'

Enter a new value. Press 'Enter' to exit.

Your selection: 1

==> Value for 'BPCEventTransformerMaxWaitTime' set to '1'.

Enter the number of the configuration parameter you want to

change/display:

205
 1) BPCEventTransformerEventCount
2) BPCEventTransformerMaxWaitTime
3) BPCEventTransformerToleranceTime
4) ObserverCreateTables
5) ObserverSchemaName
0) Exit Menu

Your selection: 3

Edit a configuration parameter.

Configuration parameter: BPCEventTransformerToleranceTime

Description: Time in minutes while the Transformer ignores
the
events in the database.
Data type: Integer
Unit: Minutes
Current value is: '10'

Enter a new value. Press 'Enter' to exit.

Your selection: 1

==> Value for 'BPCEventTransformerToleranceTime' set to '1'.

Enter the number of the configuration parameter you want to

change/display:

1) BPCEventTransformerEventCount
2) BPCEventTransformerMaxWaitTime
3) BPCEventTransformerToleranceTime
4) ObserverCreateTables
5) ObserverSchemaName
0) Exit Menu

Your selection: 0

Do you want to save the changes?

y) yes
n) no

Your selection: [y] y

==> yes
Updating the application configuration settings ...

Note: To activate the changes, you must restart the application

BPCECollector_SupportCluster.
Information: Please run the node synchronization (run syncNode.bat|.sh) to
activate the changes.

Commands Menu

1) Prepare a database for the Event Collector and reporting function

2) Install the Event Collector application
3) Remove the Event Collector application and related objects
4) Change configuration settings of an installed Event Collector
5) Drop the database schema of the Event Collector and reporting
function
6) Administer reporting function related user-defined functions
0) Exit Menu

206
Your selection: 0

==> Exit Menu

207
 10.3 Configure/verify host names and corresponding port
numbers
NOTE: Please note that the ports shown here may vary on your system.

First we check the host aliases for the Support cluster members. To check it navigate
to:

Servers
-> Server Types
-> WebSphere application server types
-> WAS70DE.Support.w70l3n01Node01.0
-> Communications
-> Ports

The "Ports" page is displayed:

1. Remember the ports for "WC_defaulthost" and "WC_defaulthost_secure"

2. These ports need to be added to the host alias list for each node.

208
In the admin console navigate to:
Environment
-> Virtual hosts
-> default host
-> Host aliases

If not already configured, create the following host aliases for the Support cluster
members:

Hostname: Port:
w70l3n01.boeblingen.de.ibm.com 9081 (WC_defaulthost)
w70l3n02.boeblingen.de.ibm.com 9081 (WC_defaulthost)
w70l3n01.boeblingen.de.ibm.com 9444 (WC_defaulthost_secure)
w70l3n02.boeblingen.de.ibm.com 9444 (WC_defaulthost_secure)

Note: To add an host alias click "New", specify hostname and port, then click
"OK"

We have to do the same for the AppTarget cluster. Navigate to:

Servers
-> Server Types
-> WebSphere application server types
-> WAS70DE.AppTarget.w70l3n01Node01.0
-> Communications
-> Ports

Write down the 2 ports like you did it for the Support cluster members.

209
If not already configured, create the following host aliases for the AppTarget cluster
members:

Hostname: Port:
w70l3n01.boeblingen.de.ibm.com 9080 (WC_defaulthost)
w70l3n02.boeblingen.de.ibm.com 9080 (WC_defaulthost)
w70l3n01.boeblingen.de.ibm.com 9443 (WC_defaulthost_secure)
w70l3n02.boeblingen.de.ibm.com 9443 (WC_defaulthost_secure)

Save and synchronize the configuration

210
 10.4 Share transaction and recovery logs
In order to enable proper failover handling the transaction and the recovery log of
each cluster member needs to to be shared. Sharing means that the log files can be
commonly accessed by each node/cluster member. This can be achieved by putting
the logs on a shared network drive.
Navigate to:

Servers
-> Server Types
-> WebSphere application server types
-> WAS70DE.AppTarget.w70l3n01Node01.0
-> Container Settings
-> Container Services
-> Transaction Service

The Transaction service settings are displayed:

1. Enter
/<shared_drive>/tranlogs/WAS70DE.AppTarget.w70l3n01Node01.0

Note: Make sure that folder tranlogs already exists on your shared drive.

211
Repeat the previous step for the remaining cluster members:

Cluster member Tranlog path

WAS70DE.AppTarget.w70l3n02Node02.0 /
<shared_drive>/tranlogs/WAS70DE.AppT
arget.w70l3n02Node02.0
WAS70DE.Messaging.w70l3n01Node01.0 /
<shared_drive>/tranlogs/WAS70DE.Messa
ging.w70l3n01Node01.0
WAS70DE.Messaging.w70l3n02Node02.0 /
<shared_drive>/tranlogs/WAS70DE.Messa
ging.w70l3n02Node02.0
WAS70DE.Support.w70l3n01Node01.0 /
<shared_drive>/tranlogs/WAS70DE.Supp
ort.w70l3n01Node01.0
WAS70DE.Support.w70l3n02Node02.0 /
<shared_drive>/tranlogs/WAS70DE.Supp
ort.w70l3n02Node02.0

212
Navigate to:

Servers
-> Server Types
-> WebSphere application server types
-> WAS70DE.AppTarget.w70l3n01Node01.0
-> Container Settings
-> Container Services
-> Compensation Service

The Compensation service settings are displayed:

1. Enter
/<shared_drive>/recoverylogs/WAS70DE.AppTarget.w70l3n01Node0
1.0

Note: Make sure that folder recoverylogs already exists on your shared drive.

Repeat the previous step for the remaining application cluster member:

Cluster member Recoverylog path

WAS70DE.AppTarget.w70l3n02Node02.0 /
<shared_drive>/recoverylogs/WAS70DE.A
ppTarget.w70l3n02Node02.0

213
 Chapter 11 Create CEIDB tables
The CEIDB database scripts were created during the configuration of the deployment
environment in the dircetory
/WPS70/profiles/Dmgr01/databases/event/WAS70DE.Support/dbscripts/oracle.

1. Create a directory on the Oracle database host, e.g. /home/oracle/ceidb

2. Copy the CEIDB files from the directory above to the created directory on the
Oracle database host, in this case the host w70l3ora.boeblingen.de.ibm.com.

3. Start the CEIDB scripts in the created directory on the Oracle host by executing
the following command as user oracle:
# ./cr_event_oracle.sh

Enter the password for the schema user WPS_CEIDB to be created in the
database.

Retype the password for the schema user WPS_CEIDB to be created in the
database.

Enter the user id for a user that has SYSDBA privileges in the Oracle
database (normally SYS).

sys

Enter the password for the user sys that has SYSDBA privileges in the Or-
acle database. Type none if no password.

Enter the Oracle database name or System Identifier (SID) [ORCL]

ORCL

Enter the ORACLE_HOME []

/opt/oracle/11g

...

1 row created.

1 row created.

1 row created.

1 row created.

1 row created.
1 row created.

1 row created.

Commit complete.

sqlplus xxxxxx @cr_stored_procedure.ora

Procedure created.

Commit complete.

215
 Chapter 12 Verify the deployment environment
12.1 Verify messaging cluster
12.1.1 Verify messaging cluster startup
In the admin console, navigate to:

Servers
-> Clusters
-> WebSphere application server clusters

Start the created messaging cluster:

1. Select WAS70DE.Messaging

2. Click Start

3. Wait until the Status is dark green (Started)

216
Check log file SystemOut.log for WAS70DE.Messaging in directory:

on w70l3n01:
<install_root>/profiles/Custom01/logs/WAS70DE.Messaging.w70l3n01Node01.0

on w70l3n02:
<install_root>/profiles/Custom01/logs/WAS70DE.Messaging.w70l3n02Node02.0

for errors. The following messages should appear in the log files (on one node all
messaging engines (SCA.SYSTEM, SCA.APPLICATION, BPC, CEI) should be "Started",
on the other "Joined"):

So on one messaging cluster member you should see this:

[3/3/10 11:04:21:857 CET] 00000010 SibMessage I

[SCA.SYSTEM.Cell01.Bus:WAS70DE.Messaging.000-SCA.SYSTEM.Cell01.Bus]
CWSID0016I: Messaging engine WAS70DE.Messaging.000-SCA.SYSTEM.Cell01.Bus
is in state Joined.
[3/3/10 11:04:21:859 CET] 00000011 SibMessage I
[BPC.Cell01.Bus:WAS70DE.Messaging.000-BPC.Cell01.Bus] CWSID0016I: Mes-
saging engine WAS70DE.Messaging.000-BPC.Cell01.Bus is in state Joined.
[3/3/10 11:04:21:861 CET] 00000011 SibMessage I [SCA.APPLICATION.-
Cell01.Bus:WAS70DE.Messaging.000-SCA.APPLICATION.Cell01.Bus] CWSID0016I:
Messaging engine WAS70DE.Messaging.000-SCA.APPLICATION.Cell01.Bus is in
state Joined.
[3/3/10 11:04:21:863 CET] 00000010 SibMessage I
[CEI.Cell01.BUS:WAS70DE.Messaging.000-CEI.Cell01.BUS] CWSID0016I: Mes-
saging engine WAS70DE.Messaging.000-CEI.Cell01.BUS is in state Joined.

On the other you should see this:

[3/3/10 11:04:32:736 CET] 00000015 SibMessage I [SCA.APPLICATION.-
Cell01.Bus:WAS70DE.Messaging.000-SCA.APPLICATION.Cell01.Bus] CWSID0016I:
Messaging engine WAS70DE.Messaging.000-SCA.APPLICATION.Cell01.Bus is in
state Started.
[3/3/10 11:04:32:738 CET] 00000016 SibMessage I
[CEI.Cell01.BUS:WAS70DE.Messaging.000-CEI.Cell01.BUS] CWSID0016I: Mes-
saging engine WAS70DE.Messaging.000-CEI.Cell01.BUS is in state Started.
[3/3/10 11:04:32:740 CET] 00000017 SibMessage I
[SCA.SYSTEM.Cell01.Bus:WAS70DE.Messaging.000-SCA.SYSTEM.Cell01.Bus]
CWSID0016I: Messaging engine WAS70DE.Messaging.000-SCA.SYSTEM.Cell01.Bus
is in state Started.
[3/3/10 11:04:32:743 CET] 00000018 SibMessage I
[BPC.Cell01.Bus:WAS70DE.Messaging.000-BPC.Cell01.Bus] CWSID0016I: Mes-
saging engine WAS70DE.Messaging.000-BPC.Cell01.Bus is in state Started.

217
Note: You can ignore the following error messages on all clusters (if they
appear in your configuration):
00000000 TrustAssociat E SECJ0384E: Trust Association Init Error.
The Trust Association interceptor implementation
com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus
initialization failed. The error status/exception is -1. If you
receive this error message in association with a trust association
interceptor that you are not using, you can ignore this message.
...
00000000 TrustAssociat E
com.ibm.ws.security.spnego.TrustAssociationInterceptorImpl
initialize CWSPN0009E: SPNEGO Trust Association Interceptor
configuration is not valid. Failure condition:
com.ibm.ws.security.spnego.isEnabled JVM property is false or not
set, no further processing will be done.. If you are not using the
SPNEGO TAI, you can ignore this message.

218
 12.1.2 Verify messaging cluster messaging table creation
During the cluster startup, the tables for the messaging engines for SCA should have
been created. To verify that, check in the ORCL database, that new tables have been
created in the users WPS_SCAAPPMSG and WPS_SCASYSMSG.

To verify the table creation in the ORCL database execute the following commands as
user oracle on the database host in this case the w6201l3o.boeblingen.de.ibm.com
for the application ME datastore:

sqlplus WPS_SCAAPPMSG/<password>@ORCL

SQL*Plus: Release 11.1.0.7.0 - Production on Tue May 5 16:09:39 2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

SQL>select table_name from user_tables;

TABLE_NAME
------------------------------
SIBXACTS
SIBKEYS
SIB002
SIB001
SIB000
SIBLISTING
SIBCLASSMAP
SIBOWNER
SIBOWNERO
9 rows selected.

and for the system ME datastore:

sqlplus WPS_SCASYSMSG/<password>@ORCL

SQL*Plus: Release 11.1.0.7.0 - Production on Tue May 5 16:12:12 2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

219
SQL>select table_name from user_tables;

TABLE_NAME
------------------------------
SIBXACTS
SIBKEYS
SIB002
SIB001
SIB000
SIBLISTING
SIBCLASSMAP
SIBOWNER
SIBOWNERO
9 rows selected.

220
 12.2 Verify the support cluster

NOTE: Make sure the messaging cluster is already started before executing this
step.

In the admin console, navigate to

Servers
-> Clusters
-> WebSphere application server clusters

Start the created support cluster:

1. Select WAS70DE.Support

2. Click Start

3. Wait until the Status is dark green (Started)

221
Check logs file SystemOut.log for the support cluster members in directory:

on w70l3n01:

<install_root>/profiles/Custom01/logs/WAS70DE.Support.w70l3n01Node01.0/

on w70l3n02:
<install_root>/profiles/Custom02/logs/WAS70DE.Support.w70l3n02Node02.0/

for errors.

Now check that all applications on the support cluster have been started successfully.
To do that navigate to

Applications
-> Application Types
-> WebSphere enterprise applications

222
Verify that the following applications are started:

1. Verify that all applications ending with ".Support" are started successful.

223
 12.3 Verify the application target (BPEL) cluster

NOTE: Make sure the messaging and support cluster are already started before
executing this step.

In the admin console, navigate to

Servers
-> Clusters
-> WebSphere application server clusters

Start the created application target cluster:

1. Select WAS70DE.AppTarget

2. Click Start

3. Wait until the Status is dark green (Started)

224
Check logs file SystemOut.log for the application target cluster members in
directory:

on w70l3n01:

<install_root>/profiles/Custom01/logs/WAS70DE.AppTarget.w70l3n01Node01.0/

on w70l3n02:
<install_root>/profiles/Custom02/logs/WAS70DE.AppTarget.w70l3n02Node02.0/

for errors.

Now check that all applications on the application target cluster have been started
successfully. To do that navigate to

Applications
-> Application Types
-> WebSphere enterprise applications

225
Verify that all applications are now successfully started:

226
 Chapter 13 Install and configure IBM HTTP Server
v7.0
This section describes how to install and configure IBM HTTP Server v7.0 (IHS) within
a clustered environment. Based on the HTTP server Plug-in HTTP and REST requests
are routed to any available cluster member. In case an active cluster member fails
subsequent requests are automatically routed to another active cluster member.
Configuring high availability of the HTTP server is beyond the scope the this
document.

1. A HTTP request for a defined web resource arrives at the HTTP server. Based on the
HTTP Plug-In and a selection algorithm (round robin or random) the request is routed
to any available cluster member. The cluster member chosen handles the request.

227
2. In case the cluster members which served the incoming request fails subsequent
requests are routed to the remaining cluster member.

228
 13.0.1 Install the IHS binaries
As user root log in to the deployment manager host and install the IHS binaries by
executing the following command:
cd /<IHSV7_BINARY_ROOT>
./install

The “Welcome” panel is displayed:

1. Press Next

229
The "Software License Agreement" panel is displayed:

1. Select “I accept both the IBM and the non IBM terms” to accept the license
agreement.

2. Press Next .

230
The “System Prerequisties Check” panel is displayed:

2. Press Next .

231
The "Product installation location" panel is displayed:

1. Specify the “Product installation directory" (/opt/ihs7).

2. Press Next .

232
The "Port Values Assignment" panel is displayed:

1. Specify the HTTP port (80).

2. Specify the HTTP Administration Port (8008).

3. Press Next .

233
The “HTTP Admininstration Server Authentication” panel is displayed:

1. Select “Create a user ID for IBM HTTP Server administration

server authentication”

2. Specify a user ID (ihsadmin).

3. Specify a password (ihsadmin).

4. Confirm the password (ihsadmin).

5. Press Next .

234
The “Setup HTTP Server Administration Server” panel is displayed:

1. Select “Setup IBM HTTP Server administration server to administer IBM

HTTP Server”.

2. Select “'Create a unique user ID and group for IBM HTTP Server
administration files”.

3. Specify a user ID (ihsadmin).

4. Enter a group (ihsgroup).

5. Press Next .

235
The “IBM HTTP Server Plug-in for IBM WebSphere Application Server” panel is
displayed:

1. Select “Install the IBM HTTP Server Plug-in for IBM WebSphere Application
Server”.

2. Specify the Web sever definition (httpserver).

3. Specify the host name of the application server (host name of the
deployment manager).

4. Press Next .

236
The “Installation summary” panel is displayed:

1. Press Next . The installation of IHS starts.

237
After IHS has been installed a status panel is displayed:

1. Press Finish .

238
13.0.2 Configure SSL
Execute following command:
cd /<IHS_INSTALL_ROOT>/bin
./ikeyman

The ikeyman utility starts:

Select Key Database File / New .

239
The key file creation window is displayed:

1. Specify CMS as key database type.

2. Specify a file name (ihskey.kdb).

3. Specify the location (/opt/ihs7).

4. Press OK .

The password prompt is displayed:

1. Specify a password (ihspw).

2. Confirm the password (ihspw).

3. Select “Stash password to a file”.

4. Press OK .

240
The ikeyman utility main window is displayed again:

1. Press New Self-Signed .

241
 The Self-Signed Certificate configuration panel is displayed:

1. Specify a Key Label (ihscert).

2. Confirm a validity period (1000).

3. Press OK .

The certificate is displayed in the list of Personal Certificates. Shut down the ikeyman
utility.

242
1. Open httpd.conf (located in <IHS_INSTALL_ROOT>/conf).
Locate the following lines and remove the leading #. Also the key file setting needs to
reference the key file which has been created in the previous step.
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
Listen 443
<VirtualHost *:443>
SSLEnable
SSLProtocolDisable SSLv2
</VirtualHost>
KeyFile /opt/ihs7/ihskey.kdb (Note: this is the key file that has been
created in the previous step)

2. Save and close httpd.conf

3. Execute following command:

cd /<IHS_INSTALL_ROOT>/bin
./apachectl start

4. Open a browser, enter https://<DMGR_HOST>:443 and accept the certificate

request. IHS should be up and runing:

5. Execute following command:

cd /<IHS_INSTALL_ROOT>/bin
./apachectl stop

243
 13.0.3 Add IHS to the WPS cell
The HTTP Server will be defined on an unmanaged node. The advantage of having an
unmanaged node is that the HTTP administrative server can be configured and
utilized. This enables the operator to start and start the IBM HTTP server from within
the integration solutions console (assumed the administrative server is running).
Navigate to:
Administration
-> Nodes

1. Press Add Node.

A page is displayed where the node type has to be selected:

1. Select “Unmanaged node”.

2. Press Next .

244
Specify the basic settings for the unmanaged node:

1. Specify the Name of the unmanaged node (ihsNode).

2. Specify the Host Name the unmanaged node is supposed to be defined on

(w70l3dmg.boeblingen.de.ibm.com).

3. Specify the Platform Type (Linux)

4 Press Apply , then Save. Synchronize the configuration.

245
Navigate to
Servers
-> Server Types
-> Web servers

1. Press New

246
Specify the basic settings of the HTTP Server:

1. Specify the node (ihsnode). (Note: This is the unmanaged node which was
specified in the previous step).

2. Specify the HTTP server name (httpserver). (Note: This name needs to corres-
pond to the name of the web server definition which was specified during the in-
stallation of IHS).

3. Specify HTTP server type (IBM HTTP Server).

4.Press Next

247
Specify the web server template (There is only on pre-selected template):

2.Press Next

248
Specify the web server properties:

1. Specify the Port (443).

2. Specify the Web server installation location (/opt/ihs7).

3. Specify the Plug-in installation location (/opt/ihs7/Plugins).

4. By default all applications will be mapped to the Web Server

5. Specify the HTTP Administration Server port (8008). (Note: this needs to cor-
respond to the port which was specified during the installation of the HTTP Admin-
istration Server).

249
6. Specify the username of the HTTP Administration Server administrator (ihsad-
min). (Note: this needs to correspond to the username which was specified during
the installation of the HTTP Administration Server).

7. Specify the password of the administrator of of the HTTP Administration Server

(ihsadmin). (Note: this needs to correspond to the password which was specified
during the installation of the HTTP Administration Server).

8. Confirm the password of the administrator of of the HTTP Administration Server

(ihsadmin). (Note: this needs to correspond to the password which was specified
during the installation of the HTTP Administration Server).

9.Press Next and then Finish. Save and Synchronize the configuration.

The newly created HTTP server appears in the list of available web servers (Note:
the server is stopped).

250
In order to be able to start and and stop the server from within the integration solutions
console the corresponding HTTP Administration Server needs to be started.
Execute following command:
cd /<IHS_INSTALL_ROOT>/bin
./adminctl start

./adminctl start: admin http started

Navigate to
Servers
-> Server Types
-> Web servers

1. Select the new created HTTP server (httpserver).

2. Press Start. The HTTP server should start successfully.

3. Press Stop. The HTTP server should stop successfully.

251
Stay at “Servers → Server Types → Web servers”

1. Tick the checkbox next to “httpserver”.

2. Press Generate Plug-in.

Stay at “Servers → Server Types → Web servers”

1. Again, tick the checkbox next to “httpserver”.

2. Press Propagate Plug-in.

252
Stay at “Servers → Server Types → Web servers”

1. Select “httpserver”.

Take a look at “Additional Properties”

1. Select Plug-in properties.

253
2. Press Copy to Web server key store directory.

3. Press OK and then Save and Synchronize the configuration.

254
Navigate to
Servers
-> Server Types
-> Web servers

1. Tick the checkbox next to “httpserver”.

2. Press Start. The HTTP server should start successfully.

255
The Web Applications should now be accessible through the HTTP Server.

BPC Explorer:
https://w70l3dmg.boeblingen.de.ibm.com:443/bpc/faces/pages/Login.jsp

Business Space:
https://w70l3dmg.boeblingen.de.ibm.com:443/bpc/faces/pages/Login.jsp

Business Rules Manager:

https://w70l3dmg.boeblingen.de.ibm.com:443/br/Login.jsp

256
13.0.4 Configure BFM and HTM REST endpoints
Navigate to:
Resources
-> Resource Environment
-> Resource Environment Providers

1. Select “Mashups Endpoints”

1. Select “Custom properties”

257
Locate following resources:
resource value
{com.ibm.bpm}BFM.url https://w70l3n01.boeblingen.de.ibm.com:
9443/rest/bpm/bfm/
{com.ibm.bpm}HTM.url https://w70l3n01.boeblingen.de.ibm.com:
9443/rest/bpm/htm/

Change both values as follows::

resource value
{com.ibm.bpm}BFM.url /rest/bpm/bfm/
{com.ibm.bpm}HTM.url /rest/bpm/htm/

This can be achieved by selecting the resource and changing the value:

After both resources have been changed save and synchronize the configuration.

258
Part VII Cell Verification

259
 Chapter 14 Verify application functionality

Note: Make sure the complete cell with all clusters is started

14.0.1 Verify BPC Explorer and BPC Reporting functionality

The Business Process Choreographer Explorer reporting function (also known as BPC
Observer in pre 6.2 releases) uses the Common Event Infrastructure (CEI) to collect
events that are emitted by WebSphere® Process Server. You can either use a number
of predefined reports or define your own reports to get an overview of the number of
processes, activities, or other aggregate data. You can also get information about
specific processes or activities.
The Business Process Choreographer Explorer reporting function is based on two J2EE
enterprise applications, which are shown in the following figure:

➢ The event collector application reads event information from the CEI bus and
stores it in the event collector table in the reporting database.
➢ The reporting database is a set of database tables that store the event data.
➢ Periodically the event transformer is triggered, which transforms the raw event
data into a format that is suitable for queries from the Business Process
Choreographer Explorer reporting function.
➢ The Business Process Choreographer Explorer reporting function generates the
reports and performs other actions that the user can initiate using the graphical
user interface (GUI).

260
 ➢ You can use the GUI to generate your reports. You can also store and retrieve
reports that you have defined.
➢ A cleanup utility can be used to remove records from the observer database,
which can help to improve the performance.
The following constraints apply if you want to configure Business Process
Choreographer Explorer reporting function in a network deployment environment.
• CEI must be configured in your cell.
• As illustrated in the previous figure, the Business Process Choreographer event
collector must be configured on a deployment target where the CEI Event
server is configured. If the CEI Event server is configured on a different cluster
than Business Process Choreographer, you must configure the Business Process
Choreographer event collector on a deployment target where the CEI Event
server is configured. The Business Process Choreographer Explorer reporting
function application does not need to be installed on the same machine as the
event collector.
During the deployment environment configuration the BPC Explorer with the BPC
reporting functionality, as well as the BPC Event Collector application has already been
installed and configured properly. Both applications have been installed on the Support
cluster.

Open the BPC Explorer:

https://w70l3dmg.boeblingen.de.ibm.com/bpc/faces/pages/Login.jsp

Login as:

User ID: vmmuser

Password: <password>

261
The BPC Explorer application opens:

1. Verify that the "vmmuser" is the logged in user

2. Switch between the "Views" and "Reports" tab

3. In the "Reports" tab click "Lists -> Processes", add some time to the "To:"
date and click continue. You should get an empty list.

4. In the "Views" tab click "All versions". You should also see an empty list.

5. Click "Logout"

NOTE: If you get any errors or problems, check the System.Out log files on
the clusters WAS70DE.Support and WAS70DE.AppTarget for hints.

262
 14.0.2 Deploy the Claims Handling sample application
For an advanced verification of the configuration, download the ClaimsHandling
Sample application from the "Business Process Management Samples" page:

http://publib.boulder.ibm.com/bpcsamp/index.html?
scenarios&scenarios/claimsHandling.html

Navigate to the download section and make sure to download the application for a
clustered environment, that is ClaimsHandlingApp_cluster ear and
ClaimsHandlingJSPApp_cluster ear.

Open the WebSphere Process Server Admin Console to install both ears Navigate to:

Applications
-> Application Types
-> WebSphere Enterprise Applications

1. Press Install

263
2. Select “Local file system” and browse to the ClaimsHandlingApp_cluster
ear file

3. Press Next

264
4. Select “Fast Path”

5. Press Next

6. On the first panel (Step 1: Select installation options) leave the default
settings and press Next.

265
7. Select “WebSphere:cell=Cell01,cluster=WAS70DE.AppTarget”

8. Tick the box next to “ClaimsHandlingWeb”

9. Press Apply. “ClaimsHandlingWeb” should now be mapped to the

application cluster

10. Press Next then Finish. Save and Synchronize the configuration.

Repeat the previous steps to install the ClaimsHandlingJSPApp_cluster ear

file as well. The installation steps are identical except that the module
contained within the ear (ClaimsHandlingCustomJSP) needs to be mapped
to the Support Cluster.

266
Start both applications. To do that navigate (in the AdminConsole) to:

Applications
-> Application Types
-> WebSphere enterprise applications

The deployed applications on the cell are shown:

1. Select ClaimsHandlingApp and ClaimsHandlingJSPApp_cluster

and press Start. Wait until both applications are started (indicated by a
green arrow).

267
14.0.3 Run the Claims Handling sample application

Open the BPC Explorer again:

https://w70l3dmg.boeblingen.de.ibm.com/bpc/faces/pages/Login.jsp

BPC Explorer is opened. The next steps will verify if BPC API, REST API and re-
mote artifact loading is working correctly:

1. Click "Process Templates" --> "Currently Valid". You should now see the
"ClaimsHandlingProcess" in the list:

2. Select the "ClaimsHandlingProcess" and press Start Instance to create an

instance of this process template. The "Process Input Message" window is
shown:

268
3. Specify a "Process Name" and some input data for "customerNo" (123) and
"claimRecord" (456). Then press Submit

4. In the following screen, select the "ClaimsHandlingProcess" and press In-

stances. Now the "Process instances for process templates" view is displayed,
showing your started process instance:

5. Select your process instance and press View Process State. The "Process
State View" should be opened showing the process model of the ClaimsHand-
ling Process:

269
6. Verify that the "CheckClaim" activity (this is a HumanTask) is highlighted
in green (indicating that the process has currently navigated to this activity).

270
7. In the "View" tab click "Task Instances" --> "My To-dos". A task named
"CheckClaim" in state "ready" should be shown now:

8. Select the task and press Work On

9. Select “Compensate” and press Complete. The task disappears from the
“My To-dos” list.

271
10. In the "View" tab click "Process Instances" --> "Administered By Me". The
instance “myProcessName” is now in state “Finished”.

11. Tick the checkbox next to “myProcessName” and press Delete. The in-
stance disappears from the Process Instances list.

272
14.0.4 Verify the Business Space
Open the Business Space:

https://w70l3dmg.boeblingen.de.ibm.com/mum/resources/bootstrap/login.jsp

As global security is enabled a user ID and password is required for log-on:

1. Login with User ID: "vmmuser" and appropriate password. The Busi-
nessSpace start page should be shown.

273
2. After Login, verify that the "vmmuser" is the logged in user (on the top
right)

3. To check if BusinessSpace is working click "Manage Spaces", a window will

open. Here click "Create Space".

4. A new window is opened. Specify a "Space name", select a "Space style"

and a "Space icon". Create the new space using a “Blank” template.

5. Press Save , then Done

274
6. On the BusinessSpace start page now click "Go to spaces". The previously
create BusinessSpace should be shown in the list. Select your created Busi-
nessSpace from the list:

275
7. The created (empty) Business Space is displayed. Press Edit Page, the page
(Page 1) will open. In the upper left corner select “Human Task Management
(9)” from the drop down list.

8. Drag both the “Processes List” and the “My Teams's Tasks” widget on the
page. Afterwards, the page should look like this:

276
9. In the upper right corner press Save, then Finish Editing. Since no process
instance is currently active no data is displayed in both widgets. To change
this, open the BPC Explorer again and start another instance of the Claims
Handling process as you did in the previous chapter. Once an instance exists,
refresh both widgets (in the upper right corner of each widget press the small
arrow, in the context menu select “Refresh”).

10. As both widgets get refreshed they display the process data. The “Pro-
cesses List” widget displays the active instance of the Claims Handling process
(Status: in progress), the “My Team's Tasks” widget the Check Claim task that
is currently pending (Status: Available).

11. Once you complete the task within the BPC Explorer (thus finishing the
process instance) refresh the widgets again. The Status of the process in-
stance is now “Finished” , the status of the Check Claim task is in status
“Complete”. Once you delete the finished process instance within the BPC Ex-
plorer and refresh the widgets again, the process and task information disap-
pears.

277
Part VIII Appendix

278
Chapter 15 Appendix
15.1 WPS How To
15.1.1 Save changes and synchronize nodes
The "Save changes" section is displayed on top of a page:

1. Click Review

The "Save" page is displayed:

1. Select "Synchronize changes with Nodes".

2. Click Save

279
The "Synchronize changes with Nodes" page is displayed:

1. Verify that synchronization is complete.

2. Click OK

280
 15.1.2 Start/stop the deployment manager and the node agents
This section describes how to stop and start the node agents and the deployment
manager. Deployment manager and node agents are the parts of the cell.

15.1.2.1 Stop the deployment manager and the node agents

Before restarting the entire cell all Clusters in the cell must be stopped.

In the admin console navigate to:

System administration
-> Node agents

The "Node agents" page is displayed:

1. Select all running node agents.

2. Click Stop

281
In the admin console navigate to:
System administration
-> Deployment manager

The "Deployment manager" page is displayed:

1. Click Stop

The "Stopping Server" page is displayed:

Click Ok

282
You can also stop the node agents and the deployment manager by executing the
following commands as user root on the several hosts:

1. On all custom profile node hosts:

cd /<install_root>/profiles/<profile_name>/bin
./stopNode.sh -username vmmuser -password <password>

ADMU0116I: Tool information is being logged in file

/<install_root>/profiles/<profile_name>/logs/nodeagent/stopServer.log
ADMU0128I: Starting tool with the <profile_name> profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server nodeagent stop completed.

2. On the deployment manager host:

cd /<install_root>/profiles/<profile_name>/bin
./stopManager.sh -username vmmuser -password <password>

ADMU0116I: Tool information is being logged in file

/<install_root>/profiles/<profile_name>/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the <profile_name> profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.

283
 15.1.2.2 Start the deployment manager and the node agents
To start the deployment manager and the node agents execute the following
commands as user root on the several hosts:

1. On the deployment manager host:

cd /<install_root>/profiles/<profile_name>/bin
./startManager.sh

ADMU0116I: Tool information is being logged in file

/<install_root>/profiles/<profile_name>/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the <profile_name> profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 8941

2. On all node hosts:

cd /<install_root>/profiles/<profile_name>/bin
./startNode.sh

ADMU0116I: Tool information is being logged in file

/<install_root>/profiles/<profile_name>/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the <profile_name> profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 7000

284
 15.2 IHS How To
15.2.1 Starting and stopping the IBM HTTP server

To start the http serverexecute the following commands as user root on the http
host:

cd /<install_root>/bin
./apachectl start

To stop the http serverexecute the following commands as user root on the http host:

cd /<install_root>/bin
./apachectl stop

285
 15.3 Oracle How To
15.3.1 Starting and stopping the database listener
This chapter describes now to manage the Oracle database listener.

15.3.1.1 Starting the database listener

Login the database system as user oracle and execute the following command:
lsnrctl start
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 05-DEC-2008
19:45:06

Copyright (c) 1991, 2007, Oracle. All rights reserved.

Starting /opt/oracle/11g/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.1.0.6.0 - Production

System parameter file is /opt/oracle/11g/network/admin/listener.ora
Log messages written to
/opt/oracle/diag/tnslsnr/fmtc7175/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)
(HOST=fmtc7175.boeblingen.de.ibm.com)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)
(KEY=EXTPROC1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
(HOST=<your_hostname>)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.6.0 -
Production
Start Date 05-DEC-2008 19:45:06
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/11g/network/admin/listener.ora
Listener Log File
/opt/oracle/diag/tnslsnr/fmtc7175/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<your_hostname>)
(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The command completed successfully

Note: The Oracle Listener needs about 1 minute to discover all services.
Trying to connect to a database before all services are discovered will
lead to an ORA error.

286
15.3.1.2 Stopping the database listener
Login the database system as user oracle and execute the following command:
lsnrctl stop
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 05-DEC-2008
19:46:30

Copyright (c) 1991, 2007, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
(HOST=<your_hostname>)(PORT=1521)))
The command completed successfully

15.3.1.3 Displaying the database listener status

Login the database system as user oracle and execute the following command:
lsnrctl status
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 05-DEC-2008
19:49:55

Copyright (c) 1991, 2007, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
(HOST=<your_hostname>)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.6.0 -
Production
Start Date 05-DEC-2008 19:49:13
Uptime 0 days 0 hr. 0 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/11g/network/admin/listener.ora
Listener Log File
/opt/oracle/diag/tnslsnr/fmtc7175/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<your_hostname>)
(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "ORCL.<your_hostname>" has 1 instance(s).
Instance "ORCL", status READY, has 1 handler(s) for this
service...
Service "ORCL_XPT.<your_hostname>" has 1 instance(s).
Instance "ORCL", status READY, has 1 handler(s) for this
service...
The command completed successfully

287
 15.3.2 Starting and stopping the database
This chapter describes how to start and stop the oracle database ORCL.

15.3.2.1 Starting the database

To start the database ORCL execute the following commands as user oracle:
sqlplus sys/<password>@<oracle_sid> AS SYSDBA

SQL*Plus: Release 11.1.0.7.0 - Production on Thu Jan 29 15:07:23

2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to an idle instance.

SQL>startup
ORACLE instance started.

Total System Global Area <xxxxxx> bytes

Fixed Size <xxxxxx> bytes
Variable Size <xxxxxx> bytes
Database Buffers <xxxxxx> bytes
Redo Buffers <xxxxxx> bytes
Database mounted.
Database opened.

15.3.2.2 Stopping the database

To stop the database ORCL execute the following commands as user oracle:
sqlplus sys/<yourPassword>@<oracle_sid> AS SYSDBA

SQL*Plus: Release 11.1.0.7.0 - Production on Thu Jan 29 15:00:08

2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning option

SQL>shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

288
 15.3.3 Starting and stopping the Oracle Enterprise Manager
Console
This chapter describes how to manage the Oracle Enterprise Manager Console (OEM)
and how to access the OEM website.

15.3.3.1 Starting the Oracle Enterprise Manager

To start the Oracle Enterprise Manager Console execute the following command as
user oracle:
emctl start dbcosole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.7.0
Copyright (c) 1996, 2008 Oracle Corporation. All rights reserved.
https://<hostname>:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 11g Database
Control .............. started.
------------------------------------------------------------------
Logs are generated in directory
/opt/oracle/11g/W62L3ORA.boeblingen.de.ibm.com_ORCL/sysman/log

15.3.3.2 Stopping the Oracle Enterprise Manager

To stop the Oracle Enterprise Manager Console execute the following command as
user oracle:
emctl stop dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.7.0
Copyright (c) 1996, 2008 Oracle Corporation. All rights reserved.
https://<hostname>:1158/em/console/aboutApplication
Stopping Oracle Enterprise Manager 11g Database Control ...
... Stopped.

15.3.3.3 Displaying the Oracle Enterprise Manager status

emctl status dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.7.0
Copyright (c) 1996, 2008 Oracle Corporation. All rights reserved.
https://<hostname>:1158/em/console/aboutApplication
Oracle Enterprise Manager 11g is running.
------------------------------------------------------------------
Logs are generated in directory /opt/oracle/11g/W62L3ORA.boeblin-
gen.de.ibm.com_ORCL/sysman/log

15.3.3.4 Accessing the Oracle Enterprise Manager

To access the Oracle Enterprise Manager type the following url in the web browser:
https://<hostname>:1158/em

The port can differ and may be found in the file

$ORACLE_HOME/install/portlist.ini.

289
 15.3.4 Resetting a user password in the Oracle database
There is sometimes a need to reset the password for a database user in the Oracle
database.
To reset the password of a database user execute the following commands as user
oracle:
# sqlplus / AS SYSDBA

SQL*Plus: Release 11.1.0.7.0 - Production on Wed Jul 22 09:16:52 2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

SQL> ALTER USER <username> IDENTIFIED BY <password>;

SQL>

e.G. resetting the password for the database user "sys":

SQL> ALTER USER SYS IDENTIFIED BY <password>;

SQL>

290
 15.3.5 Compute database statistics
15.3.5.1 Prepare the database
Execute script
sqlplus sys/<password>@<oracle_sid> AS SYSDBA
@$ORACLE_HOME/rdbms/admin/dbmsstat.sql;

to create the dbms_stats packages in the database.

Note: The dbms_stats packages are normally created during the database
creation.

15.3.5.2 Gather the database statistics

To gather statistics log in with
sqlplus sys/<password>@<oracle_sid> AS SYSDBA

and start the function:

execute dbms_stats.Gather_database_stats;

291
 15.3.6 Work with Redo Log Groups
15.3.6.1 Sizing the Redo Log Groups
The size of the redo log files depends on the database load. The 750 MB of the Oracle
database chapter are only a rule of thumb. It may be, that greater redo log files are
needed.

If a redo log file is full, the database switches to the next redo log file in a round robin
manner. On every log switch the database generates a checkpoint. This is very IO
extensive. So too small log files are downgrading the database performance.

With Oracle 10g a sizing advisor was introduced. A precondition of this advisor is that
the database is on load.

A important parameter of this method is the parameter FAST_START_MTTR_TARGET.

This is the mean time that the database should be able to recover if a database crash
occurs. This parameter is specified in seconds and possible values are between 0 and
3600.

The result of the following SQL statement is the advice for the size in MB of the redo
log files:

SQL> SELECT OPTIMAL_LOGFILE_SIZE FROM V$INSTANCE_RECOVERY;

You have to execute the statement as user “SYS“ and the role “SYSDBA”.

Therefore connect to the database executing the following command as user oracle:
# sqlplus sys/<password>@<oracle_sid> AS SYSDBA

SQL*Plus: Release 11.1.0.7.0 - Production on Wed Jul 22 09:16:52 2009

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options

SQL> SELECT OPTIMAL_LOGFILE_SIZE FROM V$INSTANCE_RECOVERY;

OPTIMAL_LOGFILE_SIZE
--------------------
nnnn

292
 15.3.6.2 Changing the redo log size
The size of a redo log file cannot be changed. You have to delete it and recreate it
with the right size.
Oracle uses the redo log files in a round robin order. So if you have three redo log
files, one is active and two are inactive. You are able to drop a logfile member with the
following command:

ALTER DATABASE DROP LOGFILE MEMBER

‘/opt/oracle/oradata/<DBNAME>/redo01.log’;

In this command you have to change the name and location of the redo log file. When
a redo log member is dropped from the database, the operating system file is not
deleted from disk. Rather, the control files of the associated database are updated to
drop the member from the database structure. After dropping a redo log file, make
sure that the drop completed successfully, and then use the appropriate operating
system command to delete the dropped redo log file.

To drop a member of an active group, you must first force a log switch.
To force a log switch, you must have the ALTER SYSTEM privilege:

ALTER SYSTEM SWITCH LOGFILE;

Ta add a new logfile member use:

ALTER DATABASE ADD LOGFILE MEMBER
‘/opt/oracle/oradata/<DBNAME>/redo01.log’ SIZE <new_log_size>M TO GROUP
<your_group>;

293