public.dhe.ibm.compublic.dhe.ibm.com/software/.../6.0.1/installation_guide_with_openp… · ibm...

IBM® OpenPages® GRC PlatformVersion 6 Modification 0 Release 1

Installation Guide with Repository

June 2011

ii

Copyright InformationLicensed Materials – Property of IBM

Copyright IBM Corporation 2003, 2011. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

No part of this book can be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission from IBM.

All questions pertaining to duplication or redistribution of this material and/or the software that it describes should be directed to:

IBM Corporation 201 Jones Road Waltham, MA 02451 U.S.A.

Open Source Software ListingA listing of all open source software used in the IBM® OpenPages® GRC Platform product can be found in the <OP_Home>|Notices|Notices.doc file, located in the root folder of your IBM IBM OpenPages GRC Platform installation (where <OP_Home> by default is c:\OpenPages or /opt/OpenPages).

IBM® OpenPages® GRC Platform

Release InformationSoftware Version: 6.0.1

Document Published: June 2011

Last Modified: September 6, 2011 15:53::06

Part Number: IN-601.02 (E)

Documentation UpdatesYou can download the latest revision of this document from the IBM information server at http://www.ibm.com/support/docview.wss?uid=swg27021291 .

http://www.ibm.com/support/docview.wss?uid=swg27021291

http://www.ibm.com/support/docview.wss?uid=swg27021291

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository iii

Contents

Chapter 1 Introduction

Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Who Should Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

About IBM OpenPages GRC Platform 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

About the OpenPages Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6About the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6About the OpenPages Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . 6About CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

About Cognos 8 Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . 7About the OpenPages Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . 7About the OpenPages Super Administrator . . . . . . . . . . . . . . . . . . . . . . . . 8About MultiCasting in the OpenPages Environment . . . . . . . . . . . . . . . . . . . 8

Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About Installation Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About Scaling the OpenPages Environment . . . . . . . . . . . . . . . . . . . . . . . . 9

About Vertical Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10About Horizontal Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About Scaling CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About Load-balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About OpenPages Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About OpenPages and Single Sign-on Solutions . . . . . . . . . . . . . . . . . . . . 12

Additional Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Prerequisites

Hardware Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Hardware Requirements - Application Server . . . . . . . . . . . . . . . . . . . . . . 16Network Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 17

Hardware Requirements -- Database Server . . . . . . . . . . . . . . . . . . . . . . 18Minimum Memory and Storage Requirements . . . . . . . . . . . . . . . . . 18Minimum Processor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 18Data Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Network Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 20

Hardware Requirements - Reporting Server . . . . . . . . . . . . . . . . . . . . . . . 21Network Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 22

Software Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Software to Be Installed Before the OpenPages Installation Process . . . . . . 23

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository iv

Software Installed During the OpenPages Installation Process . . . . . . . . . . 24Optional Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Software to Be Installed on OpenPages Client Systems . . . . . . . . . . . . . . . 25

Setting Up Required Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Create Users and Groups for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Create Users and Groups for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Creating Users and Groups on the Database Server . . . . . . . . . . . . . 26Creating Users and Groups on the Application Server . . . . . . . . . . . . 27Creating Users and Groups on the Reporting Server . . . . . . . . . . . . . 30

Preparing the OpenPages Application and Database Server . . . . . . . . . . . . . . . 32

Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Enabling DEP for Essential Windows Programs and Services . . . . . . . . . . . . 32VMWare Configuration Requirements — Windows Only . . . . . . . . . . . . . . . 33

Chapter 3 Getting Started

About the Media Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

How to Install OpenPages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Choosing the Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38About Installing OpenPages in a Windows/WebLogic Server

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About Installing OpenPages in an AIX/WebSphere Application Server

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Checklist for an OpenPages Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Additional Information for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Port Assignments and Servers List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Fixed Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Files Containing Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Dynamically Assigned Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Servers List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

About Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47OpenPages Environment Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47CommandCenter/Cognos Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 4 Installing the Database Software

About the Oracle Database Server Installation . . . . . . . . . . . . . . . . . . . . . . . . 50

Checklist for Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . 51

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Removing Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 52Copying the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Disabling Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Create AIX Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Set File Size of /tmp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Change the Temp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Creating the Oracle Installation Directory . . . . . . . . . . . . . . . . . . . . 54Check Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Validate the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Installing the Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Installing the Database Software in Interactive Mode . . . . . . . . . . . . . . . . 57Installing the Database Software in Silent Mode . . . . . . . . . . . . . . . . . . . . 59

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository v

About Non-default Instance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 62

Updating the PATH System Environment Variable . . . . . . . . . . . . . . . . . . . . . 63

Updating the PATH Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 5 Installing the OpenPages Application

About Installing the OpenPages Application . . . . . . . . . . . . . . . . . . . . . . . . . . 66

About OpenPages Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Checklist for Installing the OpenPages Application . . . . . . . . . . . . . . . . . . . . . 67

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Install the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . 68Copy the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Install the Oracle Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . 69Install the Application Server Software . . . . . . . . . . . . . . . . . . . . . . 69Set the Oracle Home Environment Variable . . . . . . . . . . . . . . . . . . . 69Verify that Servers are Running . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Disable Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Install Custom OpenPages Database Schema . . . . . . . . . . . . . . . . . 69Obtain Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Create AIX Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Set File Size of the /tmp Directory . . . . . . . . . . . . . . . . . . . . . . . . . 71Change the Temp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Create the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 72Disable WebSphere Application Server Global Security . . . . . . . . . . . 72Remove Installer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Installing the 64-bit Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Installing the 64-bit OpenPages Client in Interactive Mode . . . . . . . . . . . . 74Installing the 64-bit Oracle Client in Silent Mode . . . . . . . . . . . . . . . . . . . 77

Installing the OpenPages Application and Workflow Server . . . . . . . . . . . . . . . 79

Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Running the OpenPages and Workflow Server Installer . . . . . . . . . . . . . . . 80

Re-enabling Global Security – AIX only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Enabling Global Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Reinstalling After Incomplete Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 6 Installing Cognos and Content Store

About the Cognos Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Checklist for Installing Cognos and the Content Store . . . . . . . . . . . . . . . . . . . 97

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Install the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Copy the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Disable Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Remove Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Obtain Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Set File Size of /tmp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Change the Temp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Create the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . 100

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository vi

Create AIX Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Installing the 32-Bit Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Installing the 32-bit OpenPages Client in Interactive Mode . . . . . . . . . . . 101Installing the 32-bit Oracle Client in Silent Mode . . . . . . . . . . . . . . . . . . 103

Installing Cognos and the CommandCenter Database Schema . . . . . . . . . . . . 105

Installing Cognos and the Content Store . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring Your Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring an IIS 7.0 Web Server - Windows only . . . . . . . . . . . . . . . . . 110Configuring the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring the Apache Web Server on a Windows System . . . . . . . 114Configuring the Apache Web Server on an AIX System . . . . . . . . . . 115

Configuring Cognos 8 Go! Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring the Cognos 8 Dashboard Application . . . . . . . . . . . . . . . . . . 116

Testing the Cognos Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 7 Installing OpenPages CommandCenter

About the OpenPages CommandCenter Installation . . . . . . . . . . . . . . . . . . . 124

Checklist for Installing CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Disable Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Obtain Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Modifying the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 127Modifying the Environment Variables - Windows . . . . . . . . . . . . . . 127Modifying the Environment Variables - AIX . . . . . . . . . . . . . . . . . . 128

Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Set File Size of /tmp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Change the Temp Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Create the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . 129Create AIX Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Installing CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installing CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

CommandCenter Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Configuring Cognos Application Firewall . . . . . . . . . . . . . . . . . . . . . . . . . 135Adding Servers to the Cognos Safe List . . . . . . . . . . . . . . . . . . . . . 135

Configuring a Mail Server Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Starting the OpenPages Framework Model Generator Service . . . . . . . . . 136

Starting the Framework Model Generator . . . . . . . . . . . . . . . . . . . 136Optimizing CommandCenter Database Settings . . . . . . . . . . . . . . . . . . . 137

Modifying Cognos to Improve Database Performance . . . . . . . . . . . 137

Chapter 8 Performing Post-installation Tasks

Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Checklist for Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Tailoring the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Disabling Oracle Skip Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Tuning Memory for the Database Instance . . . . . . . . . . . . . . . . . . . . . . . 143

Memory Tuning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository vii

Tailoring the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Configuring the Database Connection Pool . . . . . . . . . . . . . . . . . . . . . . . 145Enabling the Same-User Access to OpenPages and Fujitsu Interstage

BPM — AIX only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Improving Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Increasing the Application Server Memory Requirements . . . . . . . . . . . . . 149

Increasing the WebLogic Server Memory Requirements — Windows only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Increasing the WebSphere Application Server Memory Require-ments — AIX only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Increasing the Paging File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Increasing the Oracle WebLogic Maximum Message Size . . . . . . . . . . . . . 152

Tailoring the OpenPages Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Enabling and Disabling LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Enabling LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Disabling LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Tailoring CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Creating the Reporting Schema and Framework . . . . . . . . . . . . . . . . . . . 157Changing the CommandCenter Host and Port Settings . . . . . . . . . . . . . . 158Securing Access to the CommandCenter Portal . . . . . . . . . . . . . . . . . . . 159

Starting OpenPages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Accessing OpenPages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Accessing OpenPages Using a Web Browser . . . . . . . . . . . . . . . . . . . . . . 163Accessing OpenPages Using an SSL Connection . . . . . . . . . . . . . . . . . . . 163

Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Applying the IBM OpenPages GRC Platform 6.0.1.1 Patch . . . . . . . . . . . . . . . 166

Chapter 9 Starting and Stopping OpenPages

Starting and Stopping OpenPages Application Servers . . . . . . . . . . . . . . . . . 168

About Services and Scripts Used by the OpenPages Application . . . . . . . . 168About Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168About AIX Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

About Starting Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170About First Time Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Determining Application Readiness . . . . . . . . . . . . . . . . . . . . . . . . 170

Starting OpenPages in a Windows Environment . . . . . . . . . . . . . . . . . . . 171Automatically Starting OpenPages Application Servers . . . . . . . . . . 171Starting All OpenPages Application Services Using a Script . . . . . . . 171Starting OpenPages Application Services Individually Using

Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Starting OpenPages in an AIX Environment . . . . . . . . . . . . . . . . . . . . . . 172

Starting All OpenPages Application Servers Using a Script . . . . . . . . 172Starting OpenPages Application Servers Individually Using

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172About Stopping Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Stopping OpenPages in a Windows Environment . . . . . . . . . . . . . . . . . . . 174

Automatically Stopping OpenPages Application Servers . . . . . . . . . . 174Stopping All OpenPages Application Services Using a Script . . . . . . . 174Stopping OpenPages Application Services Individually Using

Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Stopping OpenPages in an AIX Environment . . . . . . . . . . . . . . . . . . . . . 175

Stopping All OpenPages Application Servers Using a Script . . . . . . . 175Stopping OpenPages Application Servers Individually Using

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository viii

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Starting and Stopping the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . 177

About Services and Scripts Used by the Oracle Database . . . . . . . . . . . . 177About Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177About AIX Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Starting and Stopping the Database Server in a Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Starting and Stopping the Database Server in an AIX Environment . . . . . . 178

Starting and Stopping CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

About Services and Scripts Used by CommandCenter . . . . . . . . . . . . . . . 179About Windows Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179About AIX Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Starting and Stopping the CommandCenter Server . . . . . . . . . . . . . . . . . 179Using the IBM Cognos Configuration Tool to Start and Stop

the CommandCenter Server . . . . . . . . . . . . . . . . . . . . . . . 179Using the Windows Operating System to Start and Stop

CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Using the AIX Operating System to Start and Stop Com-

mandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Starting or Stopping the OpenPages Framework Model Generator

Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Using the Windows Operating System to Start and Stop the

Framework Model Generator . . . . . . . . . . . . . . . . . . . . . . . 181Using the AIX Operating System to Start and Stop the

Framework Model Generator . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 10 Uninstalling OpenPages

Removing the OpenPages Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Uninstalling OpenPages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Cleaning Up after the Removal Process . . . . . . . . . . . . . . . . . . . . . . . . . 184Uninstalling the Workflow Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Removing the 64-bit Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Removing the Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Uninstallng the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . 187Cleaning Up after the Removal Process . . . . . . . . . . . . . . . . . . . . . . . . . 188

Removing the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Remove the WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Remove the WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Removing CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Removing CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Removing the Cognos Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Removing the 32-bit Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Cleaning Up after the Removal Process . . . . . . . . . . . . . . . . . . . . . . . . . 192

Appendices

Appendix A Adding Cluster Members

Adding Vertical Cluster Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Adding Vertical Cluster Members to an Existing Installation in an Oracle WebLogic Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Task Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196About Using Parameters in Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 197

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository ix

Adding Vertical Cluster Members to an Existing Installation in an IBM WebSphere Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Task Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209About Using Parameters in Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 209

Adding Horizontal Cluster Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Verify that Servers are Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Adding New Horizontal Cluster Members . . . . . . . . . . . . . . . . . . . . . . . . 218

Appendix B Configuring Clustered Environments

About Clustered Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

About Load-balancing an OpenPages Web Server . . . . . . . . . . . . . . . . . . 220Sample Clustered OpenPages Environments . . . . . . . . . . . . . . . . . . . . . 221

Sample Windows/WebLogic Server Clustered Environment . . . . . . . 221Sample AIX/WebSphere Application Server Clustered Environment . . . .

222Sample Clustered CommandCenter Environment . . . . . . . . . . . . . . 223

Configuring a Clustered OpenPages Environment . . . . . . . . . . . . . . . . . . . . . 224

Raising the Oracle Connection Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Configuring OpenPages to Use a Domain Account . . . . . . . . . . . . . . . . . . 225Sharing a Network OpenPages Storage Directory . . . . . . . . . . . . . . . . . . 225

Configuring the Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Configuring the Apache Web Server as a Load Balancer in a Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Configuring the IBM HTTP Web Server as a Load Balancer in an AIX Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Load-balancing the OpenPages Reporting Server . . . . . . . . . . . . . . . . . . . . . 239

Configure Cognos Application Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . 239Adding Servers to the Cognos Safe List . . . . . . . . . . . . . . . . . . . . . 239

Comfigure Communication Between CommandCenter Servers . . . . . . . . . 240 Configuring the Primary CommandCenter Server . . . . . . . . . . . . . 240Configuring Secondary CommandCenter Servers . . . . . . . . . . . . . . 241

Configuring an Apache Load-balancer or Proxy Server . . . . . . . . . . . . . . 242Changing the CommandCenter Host and Port Settings in OpenPages . . . . 243Restarting CommandCenter Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Appendix C Configuring SSL

About Configuring SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

About the SSL Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Checklist for Configuring SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Configuring OpenPages for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Configuring OpenPages for SSL in a WebLogic Server Environment . . . . . 248Configuring OpenPages for SSL on a WebSphere Application Server . . . . . 261

Configuring CommandCenter for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Configuring an IIS Web Server for SSL — Windows only . . . . . . . . . . . . . 267Configuring an Apache Web Server for SSL — Windows and AIX . . . . . . . 271Edit OpenPages Properties Files — Windows and AIX . . . . . . . . . . . . . . . 273

Editing Properties Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Update Cognos Gateway URL's — Windows and AIX . . . . . . . . . . . . . . . . 274

Configuring Cognos for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Import the Root Certificate into Java Keystore — Windows and AIX . . . . . 275

Importing Root Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository x

Configuring a Load Balancer Running IBM HTTP Server . . . . . . . . . . . . . . 276Configuring a Load Balancer Running Apache Load Balancer . . . . . . . . . . 280

Appendix D Changing Default Port Numbers

About OpenPages Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Checklist for Changing Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Changing OpenPages Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Changing Port Numbers Used by OpenPages . . . . . . . . . . . . . . . . . . . . . 286Changing Ports for an WebLogic Environment . . . . . . . . . . . . . . . . 286Changing Ports for an WebSphere Application Server

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Appendix E Configuring OpenPages on One Machine

Configuring OpenPages on a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . 306

Configuring OpenPages to Operate on a Single Server . . . . . . . . . . . . . . 306Appendix F Integrating Single Sign-on with OpenPages

Configuring the OpenPages Application for Single Sign-on . . . . . . . . . . . . . . . 308

Configuring OpenPages for Single Sign-on . . . . . . . . . . . . . . . . . . . . . . . 308Disable OpenPages Single Sign-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Configuring the Reporting Server for a Single Sign-on System . . . . . . . . . . . . 313

Configuring Single Sign-on for a Reporting Server . . . . . . . . . . . . . . . . . 313Appendix G Creating the CommandCenter Database Schema

About Manually Installing the Content Store . . . . . . . . . . . . . . . . . . . . . . . . 316

Creating a Tablespace and User for the Content Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Modifying the Environment Variables - Windows . . . . . . . . . . . . . . 320Modifying the Environment Variables - AIX . . . . . . . . . . . . . . . . . . 321

Appendix H Manually Installing the Application Server

About Installing the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Checklist for Installing the Application Server Software . . . . . . . . . . . . . . . . . 333

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Obtain Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Create AIX Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Installing the Application Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Installing the WebLogic Server Software . . . . . . . . . . . . . . . . . . . . . . . . 335Installing the WebSphere Application Server Software . . . . . . . . . . . . . . 336

Installing the WebSphere Application Server V7.0 Fix Pack 13 . . . . . . . .338

Appendix I Installing the OpenPages Database Schema

About Installing the OpenPages Database Schema . . . . . . . . . . . . . . . . . . . . 340

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Additional AIX-Only Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Check the File Size of tmp Directory . . . . . . . . . . . . . . . . . . . . . . . 341Set Execution Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Create the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . 341

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository xi

Installing the 64-Bit Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Creating the Tablespace and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

About the Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Changing Database Object Names for ASM . . . . . . . . . . . . . . . . . . . . . . 343Creating the Tablespace and Users using Scripts . . . . . . . . . . . . . . . . . . 345

Appendix J Installing Client-Side Applications

Installing and Configuring Cognos 8 Go! Office — Windows only . . . . . . . . . . 350

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Installing Go! Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Installing Cognos Framework Manager — Windows only . . . . . . . . . . . . . . . . 352

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Installing Framework Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Configure Framework Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Appendix K SQL Files

SQL Files Used During a Fresh Installation . . . . . . . . . . . . . . . . . . . . . . . . . 356

Schema and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Stored Procedural Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Bootstrap Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Clean Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Appendix L Notices

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository xii

Contents

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository 1

1
Introduction
Welcome to the IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository. This chapter contains information on the following topics:

Change History on page 1 About this Guide on page 3 Who Should Use this Guide on page 5 About IBM OpenPages GRC Platform 6.0.1 on page 6 Planning Your Installation on page 9 Additional Reference Material on page 13

Change HistoryThis section lists content changes or corrections made to this book since its last publication. The Part # column in the following table corresponds to the “Part Number” listed in the documentation “Release Information” section on page ii. Content changes are cumulative and are reflected in the latest publication.

Note: The numbers in brackets after some entries, such as [1234], are for internal tracking use only.

Table 1-1: Documentation Change History

Part # Section and Page Change or Correction

IN-601.02 (E) • “Installing Cognos and Content Store” in Chapter 6 on page 95

Added steps to edit the httpd.conf file before restarting an Apache Web Server as required by Apache. [12717]

• “About MultiCasting in the OpenPages Environment” in Chapter 1 on page 8

Added more information on the multicast IP address requirement. [11979]

• “Configuring an IIS Web Server for SSL — Windows only” in Appendix C on page 267

Corrected example of keytool -certreq command for the sigalg parameter from -sigalg RSA to -sigalg SHA1withRSA.

• “Software to Be Installed Before the OpenPages Installation Process” in Chapter 2 on page 23

• “Software to Be Installed on OpenPages Client Systems” in Chapter 2 on page 25

Changed the supported version of Internet Explorer to: Microsoft® Internet Explorer version 6.0.2900 (SP2) or later (8.0 and later in Compatibility View mode)


IN-601.01 (E) • Appendix D “Changing Default Port Numbers” on page 283

Expanded information on how to change default ports [15200]

• “Hardware Prerequisites” in Chapter 2 on page 16

Updated the AIX requirements to more clearly indicate resources needed for multiple LPARs [15216]

Table 1-1: Documentation Change History (Continued)

Part # Section and Page Change or Correction

Chapter 1: Introduction


• • • • • • • • • •About this Guide

The IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository contains information for installing and configuring the OpenPages environment. Chapters 1 and 2 contain overview information on the OpenPages environment.

The software installation and configuration begins with Chapter 3 and proceeds through Chapter 9, with Chapter 10 containing information on uninstalling the OpenPages environment. The appendices contain information about specific OpenPages environments that may pertain to your environment.

When describing Windows installation procedures, this guide suggests using the command line to launch certain applications. Optionally, you can use Windows Explorer to launch these applications.

Specifically, the IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository contains the following chapters:

Chapter 1 “Introduction” on page 1

This chapter introduces the OpenPages environment. This chapter will help you understand the OpenPages environment and help you plan your OpenPages installation.

This chapter also describes the vertical and horizontal clustering scenarios supported by OpenPages. This chapter will help you plan your OpenPages environment.

Chapter 2 “Prerequisites” on page 15

This chapter describes the hardware and software prerequisites required for each system in the OpenPages environment.

Chapter 3 “Getting Started” on page 35

This chapter provides important information on installing the OpenPages environment and is where you would start when installing the OpenPages environment.

Chapter 4 “Installing the Database Software” on page 49

This chapter contains information on how to run the IBM OpenPages GRC Platform Installer for Repository to install and configure the Oracle database.

Chapter 5 “Installing the OpenPages Application” on page 65

This chapter explains how to install the OpenPages application software on either a cluster administrator or cluster member server.

Chapter 6 “Installing Cognos and Content Store” on page 95

This chapter explains how to install the Cognos applications that CommandCenter will leverage and how to configure Content Store, the CommandCenter database schema and users.

Chapter 7 “Installing OpenPages CommandCenter” on page 123

This chapter describes how to install CommandCenter and how to perform the required post-installation tasks.

Chapter 8 “Performing Post-installation Tasks” on page 139

This chapter describes how to perform required and optional post-installation procedures for the OpenPages application and CommandCenter. You must review this chapter to determine the appropriate post-installation steps for your environment.

Chapter 9 “Starting and Stopping OpenPages” on page 167

This chapter provides important information on how to start and stop the OpenPages services.



Chapter 10 “Uninstalling OpenPages” on page 183

This chapter describes how to uninstall OpenPages.

Appendix A “Adding Cluster Members” on page 195

This chapter describes how to add new instances of OpenPages after installation.

Appendix B “Configuring Clustered Environments” on page 219

This chapter describes how to configure load balancing in your OpenPages environment. If you plan to use a load-balanced environment, you must perform the procedures in this chapter.

Appendix C “Configuring SSL” on page 245

This chapter describes how to configure Single Sockets Layer (SSL) security for the OpenPages environment. If you plan to use OpenPages with SSL, you must perform the procedures in this chapter.

Appendix E “Configuring OpenPages on One Machine” on page 305

This chapter describes special configuration if the OpenPages application and CommandCenter are installed on a single server.

Appendix D “Changing Default Port Numbers” on page 283

This chapter describes how to change the default port numbers used by the IBM OpenPages GRC Platform installer. If you plan to change these default ports, you must perform the procedures in this chapter.

Appendix F “Integrating Single Sign-on with OpenPages” on page 307

This chapter describes how to integrate OpenPages into your organization’s single sign-on system. If you plan to add OpenPages into your local single sign-on environment, you must perform the procedures in this chapter.

Appendix G “Creating the CommandCenter Database Schema” on page 315

This chapter describes how to use the existing OpenPages database instance for Content Store. By default, OpenPages and CommandCenter uses separate instances. If you plan to use a single instance for both, you must perform the procedures in this chapter.

Appendix H “Manually Installing the Application Server” on page 331

This chapter describes how to install the WebLogic Server or WebSphere Application Server software. If you plan to install the application server software manually, you must perform the procedures in this chapter.

Appendix I “Installing the OpenPages Database Schema” on page 339

This chapter describes how to manually create the OpenPages Database Schema, a set of database users and a tablespace. If you plan to install the database schema manually, you must perform the procedures in this chapter.

Appendix J “Installing Client-Side Applications” on page 349

This chapter describes how to install the client-side applications that are included in the OpenPages installation kit.

Appendix K “SQL Files” on page 355

This chapter describes several SQL scripts that you can use during a typical OpenPages installation. You should review the information in this chapter for informational purposes.




• • • • • • • • • •Who Should Use this Guide

This document details the procedures for installing the components that comprise the IBM OpenPages GRC Platform 6.0.1 release.

This document is intended for use by OpenPages administrators. An administrator must have a background in operating systems administration, application server management, relational database management, systems security management, and other aspects of systems management.

Users must be familiar with running graphic interface installers, executing command-line scripts, accessing operating system administrative tools, editing text files, navigating local system and network directories, and other similar tasks.


About IBM OpenPages GRC Platform

• • • • • • • • • •6.0.1

This section contains general information about installing IBM OpenPages GRC Platform 6.0.1, including required and optional third-party software.

About the OpenPages RepositoryThe installation kit you purchased includes an installer program for the OpenPages Repository. The installer program installs the database server software and sets up the database instance for use with the OpenPages application. If your environment includes multiple server machines, the Repository installer program also includes the Oracle Client software for installation on these machines.

About the Oracle Database SoftwareThe IBM OpenPages GRC Platform requires that the Oracle database be installed before you begin installing the OpenPages application.

The installation kit contains tools to install the Oracle database and all required users and tablespaces.

IBM OpenPages GRC Platform 6.0.1 includes support for Oracle® Database 11g R2 Standard Edition and for locales in addition to the English locale.

About the OpenPages Application ServerOpenPages requires that WebLogic Server or WebSphere Application Server application server software already be installed prior to installing the OpenPages application.

Windows

If you are installing OpenPages in a Windows environment, you will use the Oracle WebLogic Server. You may have purchased WebLogic Server from IBM or from a third-party vendor.

If you purchased WebLogic Server from:

IBM. The installation kit includes an installer for WebLogic Server built into the application installer.

Another vendor. You must install the WebLogic Server on your system before you begin the OpenPages application installation process.

AIX

If you are installing IBM OpenPages GRC Platform in an AIX environment, you must install WebSphere Application Server on your system according to the vendor’s instructions before you begin the OpenPages application installation process. There is no option to purchase WebSphere Application Server from IBM. You must install WebSphere Application Server separately.



About CommandCenterCommandCenter™ is OpenPages’ suite of executive dashboards and reports designed to accelerate review and approval of governance, risk and compliance management (GRCM) information throughout the enterprise. CommandCenter enables business users to navigate through complex information easily by clicking on dashboard elements to drill-down through detailed sub-reports. When paired with OpenPages, CommandCenter can help businesses see exactly how their GRCM efforts are progressing.

Users with the proper permissions can access reports that are created and maintained in CommandCenter through the OpenPages user interface. In addition to the sample reports included with OpenPages, users can create new reports in CommandCenter and publish them into OpenPages. For details on creating and formatting new or ad hoc reports, see the appropriate Cognos documentation.

About Cognos 8 Business IntelligenceOpenPages supports IBM® Cognos® 8 Business Intelligence Server software to provide reporting capability.

The following Cognos applications are supported by OpenPages and can be installed using the IBM OpenPages GRC Platform Installer for Cognos:

Cognos 8 Business Intelligence (BI) Cognos 8 Software Development Kit (SDK) Cognos 8 Go! Dashboard Cognos 8 Go! Mobile

In addition, Windows users may install optional Cognos 8 applications such as Go! Office.

About the OpenPages Installation PackagesYour organization has purchased one of the following OpenPages installation packages:

Windows

• OpenPages with WebLogic Server. This package contains the installers for the Oracle database, the OpenPages database elements (the OpenPages repository), the OpenPages application, and CommandCenter. The IBM OpenPages GRC Platform Installer will also install the WebLogic Server software automatically.

• OpenPages without WebLogic Server. This package contains the installers for the Oracle database, the OpenPages database elements (the OpenPages repository), the OpenPages application, and CommandCenter. You must purchase the Oracle WebLogic Server software from a third-party vendor and install the software manually.

AIX

• OpenPages without WebSphere Application Server. This package contains the installers for the Oracle database, the OpenPages database elements (the OpenPages repository), the OpenPages application, and CommandCenter. You must purchase the WebSphere Application Server software from a third-party vendor and install the software manually.



About the OpenPages Super AdministratorOpenPages uses the concept of a Super Administrator account. A Super Administrator is a user that you define who has complete access to all objects, folders, role templates, and groups in the OpenPages system.

As part of the installation process a Super Administrator account will be set up automatically.

About MultiCasting in the OpenPages EnvironmentThe Fujitsu Interstage BPM software that will be automatically installed by OpenPages requires a multicast IP address to communicate with itself and with other aspects of the OpenPages environment.

In a clustered OpenPages environment with multiple IBPM instances, IBPM requires the multicast IP address to communicate with each instance.

In a single OpenPages environment with a single IBPM instance, IBPM requires the multicast IP address to communicate with itself.

There are multiple IBPM servers in a single environment and the multicast IP is used for JMS synchronization in the workflow.

You must obtain a multicast address before installing the OpenPages application.

Notes

The multicast IP address must be unique within the network address space. When installing on a secondary server in a horizontal environment, use the same

multicast IP address on all servers.



• • • • • • • • • •Planning Your Installation

When planning your IBM OpenPages GRC Platform environment, consider the following concepts.

“About Installation Configurations” on page 9 “About Scaling the OpenPages Environment” on page 9 “About Load-balancing” on page 12 “About OpenPages Database Schema” on page 12 “About OpenPages and Single Sign-on Solutions” on page 12

About Installation ConfigurationsPlan what type of installation will work best for your OpenPages environment.

For light loads such as a Development or Test environment (fewer than 50 concurrent users), a two-server setup should be sufficient, with one server hosting the OpenPages application and CommandCenter, and the second server hosting the Oracle database.

For moderate loads (fewer than 200 concurrent users), a three-server configuration is recommended, with one server for the OpenPages application, a second server for the CommandCenter, and a third server for the Oracle database.

For heavier user loads (more than 200 concurrent users), you have the option of scaling the OpenPages vertically and/or horizontally by adding additional instances of the OpenPages and CommandCenter applications.

Note: A server with both the OpenPages application and CommandCenter must be specifically configured after installation to use the correct Java version, as described in Appendix E “Configuring OpenPages on One Machine” on page 305.

About Scaling the OpenPages EnvironmentThe OpenPages application supports both vertical and horizontal scaling, as described in the figures below.

Scaling allows you to increase the number users in the system by adding additional instances of the OpenPages application.

When scaling, note that the OpenPages environment must have a cluster administrator machine. The cluster administrator machine consists of one admin server, which is used to configure resources on one or more managed servers. A managed server is a Java Virtual Machine (JVM) that hosts an instance of OpenPages.

For every OpenPages application server, there is also an OpenPages workflow server. The OpenPages workflow server is installed as part of the OpenPages application server installation.

For the purposes of this document, this pairing of an instance of the OpenPages application and a corresponding Workflow server is called a node.

Scaling either vertically or horizontally requires the use of a load-balancer to distribute the incoming requests across the nodes.



About Vertical ScalingVertical scaling involves configuring a single machine, called a cluster administrator, with an admin server and one or more managed servers, as illustrated below.

In a vertical cluster, there is one OpenPages instance that serves as the admin server, along with one or more managed servers.

This approach assumes you have sufficient memory and CPU power in a single environment to support the additional nodes.

Figure 1-1: Vertical Scaling in an OpenPages Environment



About Horizontal ScalingWhen the number of user requests that a vertical cluster can accommodate reaches a practical limit due to system memory and other hardware constraints, a second physical machine can be added, creating a horizontally-scaled environment.

In a horizontally-scaled environment, the cluster admininistrator hosts the admin server and one or more managed servers, while additional managed servers are hosted on separate physical servers, called cluster members.

Each cluster member can include another vertical cluster consisting of one or more managed servers, but no admin server, as illustrated below.

Figure 1-2: Horizontal Scaling in an OpenPages Environment

About Scaling CommandCenterCommandCenter leverages the IBM Cognos Business Intelligence application, which can also scale vertically or horizontally. Scaling CommandCenter involves increasing the number of processes that can handle requests and may involve configuring additional Cognos dispatchers.

Scaling the reporting server vertically within the same environment involves increasing the number of processes available to handle requests, and depending on the load, may involve configuring additional dispatchers.

Scaling the reporting server horizontally involves installing additional environments and registering the Cognos dispatchers so that the incoming requests will be distributed across the multiple environments.



About Load-balancingLoad balancing is a mechanism used to divide the load of incoming client requests across multiple application server machines so that the load on each machine is lessened. This configuration enables the OpenPages application to scale as the number of concurrent users rises. The redundancy of the application tier, combined with the redundant hardware, also provides a path to high-availability for OpenPages.

If you decide to use a load-balanced environment, see “Configuring Clustered Environments” on page 219.

About OpenPages Database SchemaThe OpenPages application requires a set of database users and a tablespace, called the OpenPages Database Schema. You install these database components automatically during the OpenPages application installation or manually using SQL scripts, based on your needs. Both the scripts and the installer create and configure all of the required elements.

During the OpenPages application installation, you will be prompted to install the OpenPages Database Schema. Select Yes to install the schema or No if you have already installed the schema.

If you choose to install the database components manually, see Appendix I “Installing the OpenPages Database Schema” on page 339.

About OpenPages and Single Sign-on SolutionsThe OpenPages application and CommandCenter can integrate with a number of single sign-on solutions, such as IBM’s Tivoli Access Manager (TAM) or CA SiteMinder.

If you decide to use a single sign-on strategy for the OpenPages application and/or CommandCenter, see Appendix F “Integrating Single Sign-on with OpenPages” on page 307.



• • • • • • • • • •Additional Reference Material

Additional references are available on the Installer Disc 1 DVD:

For information about OpenPages phrases and terminology, see the IBM OpenPages GRC Platform Administrators Guide.

For a more detailed explanation of the features and enhancements contained in this release, see the IBM OpenPages GRC Platform Release Notes.



2
Prerequisites
This chapter contains information on the following topics:

Hardware Prerequisites on page 16 Software Prerequisites on page 23 Setting Up Required Users and Groups on page 26 Preparing the OpenPages Application and Database Server on page 32


• • • • • • • • • •Hardware Prerequisites

This section outlines the minimum recommended hardware configurations for installing the IBM OpenPages GRC Platform software. A typical OpenPages environment requires three machines – an application server, a database server, and a reporting server. You may add servers to scale horizontally in a load balanced configuration.

Hardware Requirements - Application ServerThis section describes the minimum recommended hardware and software requirements for the 64-bit application server in a production environment.

OpenPages is designed to scale within your enterprise by adding nodes to your configuration. The tables below show the number of CPUs and memory required to support each node (where a node is one OpenPages application and one workflow server pairing). When more than one node is required to support your user population, you can add nodes to an existing machine or introducing another machine. A machine may be a physical piece of hardware or a virtual environment such as a VM or an LPAR (AIX). Using multiple nodes requires a load balanced configuration to distribute the incoming requests across the multiple nodes.

If you have a system that experiences exceptionally high numbers of concurrent users, you may require more robust hardware than the recommended guidelines indicate.

NotesThe hardware requirement tables below use the following conventions, in addition to any specific footnotes:

Count infrequent users as 1/50 of a user. For example, for 20,000 licensed users assume 400 concurrent users (20,000/50).

The concurrent users value assumes 25% of users on the system concurrently. The number of nodes listed represents the minimum number of application nodes

(OpenPages/worflow). Nodes may be installed within a single scalable environment, or distributed horizontally across multiple environments

The number of core processors represents the minimum number of core processors required, based on the higher end of the concurrent user range.

The minimum memory per node represents the minimum memory RAM / (PageFile) to allocate per node.

The minimum storage per node represents the minimum disk storage requirement to allocate per node. The storage space requirement includes sufficient space for installing the OpenPages and web server software.

WindowsThe following table lists the hardware requirements for a Windows-based application server.

Table 2-1: Hardware Requirements Application Server -- Windows

# of Users # of Concurrent Users

# of Nodes

Load Balanced?

Minimum # of Core

Processorsa

a. Calculations based on Intel® Xeon® CPU 5680 @ 3.3 GHz

Minimum Memory per Node

Minimum Storage per Node

up to 1600 up to 400 1 No 2 4GB/(6GB) 100GB

1601 to 3200 401 to 800 2 Yes 4 4GB/(6GB) 100GB

3201 to 4800 801 to 1200 3 Yes 4 4GB/(6GB) 100GB

4801 to 6400 1201 to 1600 4 Yes 6 4GB/(6GB) 100GB

6401 to 8000 1601 to 2000 5 Yes 6 4GB/(6GB) 100GB

8001 to 9600 2001 to 2400 6 Yes 8 4GB/(6GB) 100GB

9601 to 11200 2401 to 2800 7 Yes 8 4GB/(6GB) 100GB

Chapter 2: Prerequisites


AIX

The following table lists the hardware requirements for an AIX-based application server.

IMPORTANT! The IBM OpenPages GRC Platform requires a dedicated AIX LPAR and WebSphere Application Server environment. Sharing the OpenPages LPAR with other applications and WebSphere Application Server environments is not supported.

Network Bandwidth RequirementsThe following table shows the minimum bandwidth requirements for a Windows-based or AIX-based server.

Table 2-2: Hardware Requirements Application Server -- AIX

# of Named Users # Concurrent Active Users

# of Nodes

Load Balanced

Dedicated CPUs

per Node

Minimum Memory per Node

Minimum Storage per Node

Fewer than 100 1 to 25 1 No 1 8GB 100GB

101 to 200 26 to 50 1 No 2 8GB 100GB

201 to 400 51 to 100 1 No 3 8GB 100GB

401 to 800 101 to 200 1 No 4 12GB 100GB

801 to 1600 201 to 400 2 Yes 4 12GB 100GB

1601 to 3200 401 to 800 3 Yes 4 12GB 100GB

3201 to 4800 801 to 1200 4 Yes 4 12GB 100GB

4801 to 6400 1201 to 1600 5 Yes 4 12GB 100GB

6401 to 8000 1601 to 2000 6 Yes 4 12GB 100GB

8001 to 9600 2001 to 2400 7 Yes 4 12GB 100GB

9601 to 11200 2401 to 2800 8 Yes 4 12GB 100GB

Table 2-3: Bandwidth Requirements Application Server

# of Named Users # of Concurrent Active Users Bandwidth Requirements

800 200 35 Mbps

1600 400 70 Mbps

2400 600 105 Mbps

3200 800 140 Mbps

4000 1000 175 Mbps

4800 1200 210 Mbps

5600 1400 245 Mbps

6400 1600 280 Mbps

7200 1800 315 Mbps

8000 2000 350 Mbps

8800 2200 385 Mbps

9600 2400 420 Mbps

10400 2600 455 Mbps

11200 2800 490 Mbps



Hardware Requirements -- Database Server This section shows the recommended minimum hardware requirements for the 64-bit database server in a production environment, which requires the following:

64-bit operating system 64-bit Oracle RDBMS Expandable RAM Expandable RAID data storage

When considering hardware requirements, we recommend that you plan for the future and purchase hardware that is expandable and can support future database growth.

Although not required, OpenPages recommends a dedicated environment where the database server supports only the OpenPages application. Please see your OpenPages representative for assistance in determining your database size and needs.

Note: If the OpenPages database instance is running in a non-dedicated environment, the resources in the following tables must be allocated to the OpenPages database instance.

Minimum Memory and Storage RequirementsThe following table shows the recommended minimum memory and storage requirements for a Windows or AIX server, based on the size of the database.

Minimum Processor RequirementsThe following tables show the minimum processor requirements for a Windows or AIX server.

Notes

The hardware requirement tables below use the following conventions, in addition to any specific footnotes:


The number of concurrent users assumes 25% of the licensed users are using system concurrently.

The minimum number of core processors is calculated using the higher end of the concurrent user range, assuming 8 cores for the first 400 users plus 2 cores for each 100 additional concurrent users.

Table 2-4: Minimum Memory and Storage Requirements for a 64-bit Database

Projected database size Memory (RAM) RAID Data Storage

1 to 50 GB 8GB 100GB

51 to 100 GB 16GB 200GB

101 to 200 GB 32GB 400GB

201 to 400 GB 64GB 800GB

Greater than 400 GB 16% of the maximum DB size 2X database size




Windows

The requirements for a Windows database server are as follows.

AIX

The requirements for an AIX database server are as follows:

Table 2-5: Hardware Requirements: Database Server -- Windows

# of Named Users # of Concurrent Users Minimum # of core processorsa

a. The minimum core processor requirement is a dual-core Intel® Xeon® CPU 3.2 GHz.

1 to 200 1 to 50 2

201 to 400 51 to 100 4

401 to 800 101 to 200 4

801 to 1600 201 to 400 8

1601 to 3200 401 to 800 16

3201 to 4800 801 to 1200 24

4801 to 6400 1201 to 1600 32

6401 to 8000 1601 to 2000 40

8001 to 9600 2001 to 2400 48

9601 to 11200 2401 to 2800 56

Table 2-6: Hardware Requirements Database Server -- AIX

# of Named Users # of Concurrent Active Users # Dedicated CPUsa

a. These calculations are based on P550 POWER6 TL4 system.

1 to 200 1 to 50 6

201 to 400 51 to 100 6

401 to 800 101 to 200 6

801 to 1600 201 to 400 8

1601 to 3200 401 to 800 16

3201 to 4800 801 to 1200 24

4801 to 6400 1201 to 1600 32

6401 to 8000 1601 to 2000 40

8001 to 9600 2001 to 2400 48

9601 to 11200 2401 to 2800 56


Data Storage RequirementsFor data storage, we recommend a combination of RAID 1+0 (or 0+1) disks with at least 6 different drives. In typical RAID 1+0 or 0+1 configurations, approximately half (50%) of the drives would be used for mirroring the contents of the disks.

A RAID 5 architecture can also be used with at least 4 different drives. In RAID 5, typically one drive would be used for parity data.

Example: RAID 1+0 (or 0+1)

If the projected database size is 54 GB, based on this hardware specification, approximately 108 GB (54 GB * 2) of usable storage space would be required.

To achieve a usable storage capacity of approximately 108 GB, a total storage capacity of 216 GB (108 GB * 2) is needed as 50% of the available space would be used for mirroring.

To determine the individual capacity of each drive, divide the total storage capacity by the number of hard drives to determine the individual capacity of each drive. In this example, it would be 6x36-GB RAID 1+0 (216 GB/6 hard drives=36 GB per drive).

Example: RAID 5 or RAID 10

Using the same projected database size of 54 GB as in the previous example but with a RAID 5 architecture, to achieve a usable storage capacity of approximately 108 GB, a total storage capacity of approximately 144 GB (108 + 36) is needed, one drive being used for parity data.

In this example, it would be 4x36-GB RAID 5 drives (144 GB / 4 hard drives = 36 GB per drive).

Network Bandwidth RequirementsThe following table shows the minimum bandwidth requirements for a Windows-based or AIX-based server.

Table 2-7: Bandwidth Requirements Database Server


800 200 60 Mbps

1600 400 120 Mbps

2400 600 180 Mbps

3200 800 240 Mbps

4000 1000 300 Mbps

4800 1200 360 Mbps

5600 1400 420 Mbps

6400 1600 480 Mbps

7200 1800 540 Mbps

8000 2000 600 Mbps

8800 2200 660 Mbps

9600 2400 720 Mbps

10400 2600 780 Mbps

11200 2800 840 Mbps



Hardware Requirements - Reporting ServerThis section describes the recommended minimum hardware requirements for installing OpenPages CommandCenter on a reporting server.

IBM recommends installing CommandCenter on a separate server machine that meets the recommended minimum requirements in the following tables.

Notes

The hardware requirement tables below use the following conventions, in addition to any specific footnotes:


The number of concurrent users assumes 25% of the licensed users are using system concurrently.

The number of reporting servers listed represents the minimum number CommandCenter instances. Only one instance of CommandCenter should be installed on each server.

The number of processors required is based on the higher end of the concurrent user range.

The minimum memory per server represents the minimum memory RAM / (PageFile) to allocate per server.

The minimum storage per server represents the minimum disk storage requirement to allocate per server. The storage space requirement includes sufficient space for installing the CommandCenter software.

Windows

The following table lists the hardware requirements for a Windows-based reporting server.

Table 2-8: Hardware Requirements Reporting Server -- Windows

# Named of Users # Concurrent Active Users

# of Reporting Servers

Load Balanced?

# of Processors per Servera

a. Calculations based on Intel® Xeon® CPU 5680 @ 3.3 GHz

Minimum RAM per Server

Minimum Storage per Server

up to 1600 up to 400 1 No 2 8GB/(12GB) 100GB

1601 to 3200 401 to 800 1 No 4 16GB/(12GB) 100GB

3201 to 4800 801 to 1200 2 Yes 2 8GB/(12GB) 100GB

4801 to 6400 1201 to 1600 2 Yes 4 16GB/(12GB) 100GB

6401 to 8000 1601 to 2000 3 Yes 4 8GB/(12GB) 100GB

8001 to 9600 2001 to 2400 3 Yes 4 16GB/(12GB) 100GB

9601 to 11200 2401 to 2800 4 Yes 4 8GB/(12GB) 100GB



AIX

The following table lists the hardware requirements for an AIX-based reporting server.

Network Bandwidth RequirementsThe following table shows the minimum bandwidth requirements for a Windows-based or AIX-based server

Table 2-9: Hardware Requirements Reporting Server -- AIX

# of Named Users # Concurrent Active Users

# of Reporting Servers

Load Balanced

Dedicated CPUs per Server

Minimum Memory per Server

Minimum Storage per Server

Fewer than 100 1 to 25 1 No 1 8GB 100GB

101 to 200 26 to 50 1 No 2 8GB 100GB

201 to 400 51 to 100 1 No 3 8GB 100GB

401 to 800 101 to 200 1 No 4 12GB 100GB

801 to 1600 201 to 400 2 Yes 4 12GB 100GB

1601 to 3200 401 to 800 3 Yes 4 12GB 100GB

3201 to 4800 801 to 1200 4 Yes 4 12GB 100GB

4801 to 6400 1201 to 1600 5 Yes 4 12GB 100GB

6401 to 8000 1601 to 2000 6 Yes 4 12GB 100GB

8001 to 9600 2001 to 2400 7 Yes 4 12GB 100GB

9601 to 11200 2401 to 2800 8 Yes 4 12GB 100GB

Table 2-10: Bandwidth Requirements Reporting Server


800 200 25 Mbps

1600 400 50 Mbps

2400 600 75 Mbps

3200 800 100 Mbps

4000 1000 125 Mbps

4800 1200 150 Mbps

5600 1400 175 Mbps

6400 1600 200 Mbps

7200 1800 225 Mbps

8000 2000 250 Mbps

8800 2200 275 Mbps

9600 2400 300 Mbps

10400 2600 325 Mbps

11200 2800 350 Mbps



• • • • • • • • • •Software Prerequisites

This section details the third-party software that must be installed in the IBM OpenPages GRC Platform 6.0.1 environment before starting the installation. The section also details the software that will be installed during the installation process, either by the IBM OpenPages GRC Platform Installer or third-party installers. Several optional third-party applications that can be integrated into the OpenPages environment are also listed.

Software to Be Installed Before the OpenPages Installation ProcessThe following third-party software must be installed before beginning the OpenPages 6.0.1 installation.

Windows

In a Microsoft Windows/Oracle WebLogic Server environment install these components before starting the OpenPages installation:

Install on All Servers:

All servers in the OpenPages environment should have the following software installed before starting the OpenPages installation:

Microsoft® Windows Server™ 2008 R2 (64-bit operating system) Microsoft® Internet Explorer version 6.0.2900 (SP2) or later (8.0 and later in

Compatibility View mode) A file compression utility, such as WinZip A PDF reader (such as Adobe Acrobat)

Install on the Application Server(s):

In addition to the software listed above for all servers, the servers that host the OpenPages application should have the following software installed before starting the OpenPages installation

JDK 1.6 or greater, 64-bit (is a prerequisite only if you have not purchased WebLogic Server from OpenPages)

Oracle WebLogic Server 10.3.2 (is a prerequisite only if you have not purchased WebLogic Server from OpenPages) Note: The IBM OpenPages GRC Platform Installer requires that WebLogic Server be installed to a path with no spaces.

Install on the Reporting Server(s)

In addition to the software listed above for all servers, the servers that host CommandCenter should have the following software installed before starting the OpenPages installation:

Microsoft Internet Information Services (IIS) 7.0 -- or -- Apache HTTP Server™ 2.2.14 or greater

AIX

In an AIX/WebSphere environment install these components before starting the OpenPages 6.0.1 installation:

Install on All Servers:

All servers in the OpenPages environment should have the following software installed before starting the OpenPages installation:

IBM AIX® 6.1 (64-bit) A file compression utility, such the GNU tar utility (gtar) A PDF reader



Install on the Application Server(s):

In addition to the software listed above for all servers, the servers that host the OpenPages application should have the following software installed before starting the installation:

IBM WebSphere® Application Server (WAS) Network Deployment 7.0.0.13 JRE 1.4.1 (required for Interstage BPM software installation)

IMPORTANT! The IBM OpenPages GRC Platform requires a dedicated AIX LPAR and WebSphere Application Server environment. Sharing the OpenPages LPAR with other applications and WebSphere Application Server environments is not supported.

Install on the Reporting Server(s)

In addition to the software listed above for all servers, the servers that host the CommandCenter application should have the following software installed before starting the CommandCenter installation.

Apache HTTP Server™ 2.2.14 or greater

Note: The AIX default tar command may not be able to uncompress the contents of downloaded media pack image.

Software Installed During the OpenPages Installation ProcessThe following components will be installed during the OpenPages installation process in both the WebLogic Server and WebSphere Application Server environments. This installation guide gives full details for installing each of these applications.

Oracle Database Server Oracle 11G Release 2 (11.2.0.1) Standard Edition with October 2010 Critical Patch Update

Oracle Database Client 11g Release 2 (11.2.0.1) 64-bit with October 2010 Critical Patch Update (application server)

Oracle Database Client 11g Release 2 (11.2.0.1) 32-bit with October 2010 CPU Patch applied 32-bit (reporting server)

Oracle WebLogic Server 10.3.2 or greater (if you have purchased WebLogic Server from IBM)

OpenPages 6.0.1 Application Fujitsu Interstage® Business Process Manager (BPM) IBM Cognos® Business Intelligence 8.4.1 OpenPages 6.0.1 CommandCenter JRE 1.6 or greater

Optional Third-Party SoftwareOpenPages integrates with the following optional third-party software:

IBM® Cognos® 8 Go! Office, version 8.4.1 (Windows only) CA SiteMinder®, version 5.5 or greater (single sign-on application) VMWare® ESX versions 3.5.1 or 4.0 (virtualization platform) IBM® Tivoli® Access Manager (TAM) version 6.1 (user authentication, authorization and

Web SSO solution)

Note: SiteMinder is only supported on servers running an English language operating system.

For instructions on:

Configuring SiteMinder settings, see Appendix F “Configure the OpenPages Interface for Single Sign-on” on page 308.

Configuring VMWare, see “VMWare Configuration Requirements — Windows Only” on page 33.



Software to Be Installed on OpenPages Client SystemsAny system that will access the OpenPages application should have the following software installed:

A web browser, such as Microsoft Internet Explorer version 6.0.2900 (SP2) or later (8.0 and later in Compatibility View mode)

A PDF reader, such as Adobe Reader (version 7.0 or higher) for CommandCenter reporting functions

Microsoft Excel 2003 (or higher) for CommandCenter reporting functions Microsoft .NET Framework version 2.0 on clients where IBM Cognos 8 Go! Office will be

installed

Optionally, you may install any of the following on a Windows client machine:

IBM Cognos Go! Office (available on the OpenPages installation kit) IBM Cognos 8 BI Framework Manager (available on the OpenPages installation kit)



• • • • • • • • • •Setting Up Required Users and Groups

Before starting the installation, you must create specific users and user groups, as required by your operating system.

Create Users and Groups for WindowsThe user accounts used to install and configure the OpenPages environment must be members of the Power Users or Administrators groups. Users in either of these groups will be able to perform all actions required to install and configure IBM OpenPages GRC Platform.

Create Users and Groups for AIXThe users and groups must be created and configured by a user with SYSADMIN privileges and access to root. Please refer to Oracle® Database Installation Guide 11g Release 2 (11.2) for IBM AIX on POWER Systems (64-Bit) for specific information.

If you are installing a cluster environment, these users must be created on the cluster administrator server and on each cluster member.

IMPORTANT! During the OpenPages installation, you will need to manually create directories. If you plan to install OpenPages within the /opt directory using a non-root user, you will need to create these directories as root. A non-root user will likely not have permission to create directories under /opt.

Creating Users and Groups on the Database Server

The information in this topic applies only to AIX environments.

Create and configure the oinstall, dba, and oper groups and the oracle user on the server that will host the Oracle database.

Steps:

1. Log onto the database server as root.2. Open an AIX shell and enter the following command to create a group called oinstall.

This group is the primary group for the oracle user. This will be the inventory group.

mkgroup -A oinstall mkgroup -A dba

Note: The Oracle database requires these names be used for these groups.

3. Navigate to the /usr/sbin/ and enter the following command to create a user called oracle, assign the initial log in group (oinstall) and add the user to the dba group.

/usr/sbin/useradd -m -g oinstall -G dba oracle

Note: The Oracle database installer requires that this user be named oracle.

Table 2-11: Required Users and Groups for Database Server

User Assign to Groups Permissions Reason

oracle oinstall; dba

oinstall should be the primary group for this user.

User must have read, write, execute permission to:

• Oracle client install directory

This is required by Oracle database installer.



4. Change the password for the oracle user using the following command:

passwd oracle

5. Enter a new password at the New Password prompt.6. Configure the oracle user to limit the size of a file the user can create.

chuser fsize=<#> cpu=<#> data=<#> stack=<#> rss=<#> oracle

Where:

• fsize sets the largest file a user's process can create or extend• cpu sets the largest amount of system unit time (in seconds) that a user's process

can use• data sets the largest data segment for a user's process• stack sets the largest process stack segment for a user's process• rss sets the largest amount of physical memory a user's process can allocate

Note: Use a negative number to set the limits to unlimited to allow this user to copy the installation kit from the install media to a local system. These values can be changed later to better suit your environment.

Example

The following example sets the file size to unlimited for the current user:

chuser fsize=-1 cpu=-1 data=-1 stack=-1 rss=-1 oracle

Creating Users and Groups on the Application Server


You need to create two users and one group to install the Oracle Client, WebSphere Application Server, and the OpenPages application. You may create a separate user and group to install WebSphere Application Server.

Create and configure the oinstall group and the oracle user on the server that will host the OpenPages application, in order to install the Oracle client.

Table 2-12: Required Users and Groups for Application Server


oracle oinstall User must have read, write, execute permission to:


This is required by Oracle client installer.

wasuser WebSphere install User must have read, write, execute permission to:

• WebSphere install directory

Allows you to create a non-root user to install the WebSphere Application Server software. You may create a separate user and group or use opuser.



Steps:

1. Log onto the application server as root and open an AIX shell.2. Enter the following command to create a group called oinstall. This group is the

primary group for the oracle user.

mkgroup -A oinstall

Note: The Oracle Client installer requires that this group be named oinstall.

3. Navigate to the /usr/sbin/ and enter the following command to create a user called oracle and assign the user to the oinstall group. This user will be used to install Oracle client.

/usr/sbin/useradd -m -g oinstall oracle

Note: The Oracle Client installer requires that this user must be named oracle.

opuser staff security audit bincron (optional)WebSphere install group

staff should be the primary group for this user.




• Java JDK or JRE install directory

User must be able to run SQL*Plus commands.

• staff. This is a standard, default group that most users have as the primary group.

• cron. Optionally, add the user to this group to allow this user to execute cron jobs.

• security. Add the user to this group to allow the user to set user attributes.

• audit. Add the user to this group to allow the user to be audited or to perform audits.

• bin. Add the user to this group to allow access to tools in the bin directory, such as gunzip.

If WebSphere Application Server was installed by another user (not opuser), then opuser must be added to the WAS installer group.

Table 2-12: Required Users and Groups for Application Server




4. Configure the oracle user to limit the size of a file the user can create. Use a negative number for unlimited.


Where:

• fsize sets the largest file a user's process can create or extend• cpu sets the largest amount of system unit time (in seconds) that a user's process

can use• data sets the largest data segment for a user's process• stack sets the largest process stack segment for a user's process• rss sets the largest amount of physical memory a user's process can allocate


Example




passwd oracle

6. Enter a new password at the New Password prompt.7. Create a user to install the OpenPages application, such as opuser.

useradd -m <name>

8. Configure the opuser user to limit the size of a file the user can create. Use a negative number for unlimited.

chuser fsize=<#> <name>

9. Add the OpenPages user to the bin,security, and audit Oracle groups. Optionally, you can add the user to the cron group.

usermod -g staff -G bin,security,cron,audit opuser

10. Change the password for the OpenPages user using the following command:

passwd <name>

11. Enter a new password at the New Password prompt.



Creating Users and Groups on the Reporting Server


You need to create two users and one group to install the Oracle client and the CommandCenter application.

Create and configure the oinstall group and the oracle user on the server that will host the OpenPages application, in order to install the Oracle client.

Steps:

1. Log onto the application server as root and open an AIX shell.2. Enter the following command to create a group called oinstall. This group is the

primary group for the oracle user.

mkgroup -A oinstall

Note: The Oracle Client installer requires that this user be named oinstall.

3. Navigate to the /usr/sbin/ and enter the following command to create a user called oracle and assign the user to the oinstall group. This user will be used to install Oracle client.

/usr/sbin/useradd -m -g oinstall oracle

Note: The Oracle Client installer requires that this user must be named oracle.

Table 2-13: Required Users for Reporting Server


oracle oinstall User must have read, write, execute permission to:


oinstall

This is required by Oracle client installer.

opuser staff cron security audit bin

staff should be the primary group for this user.




• Cognos install directory

• Java JDK or JRE install directory

• Apache Web Server install directory

User must be able to run SQL*Plus commands.

• staff. This is a standard, default group to which most users have as the primary group.

• cron. Optionally, add the user to this group to allow this user to execute cron jobs.

• security. Add the user to this group to allow the user to set user attributes.

• audit. Add the user to this group to allow the user to be audited or to perform audits.

• bin. Add the user to this group to allow access to tools in the bin directory, such as gunzip.



4. Configure the oracle user to limit the size of a file the user can create. Use a negative number for unlimited.


Where:

• cpu sets the largest amount of system unit time (in seconds) that a user's process can use

• data sets the largest data segment for a user's process• stack sets the largest process stack segment for a user's process• rss sets the largest amount of physical memory a user's process can allocate


Example




passwd oracle

6. Enter a new password at the New Password prompt.7. Create a user to install the OpenPages application, such as opuser.

useradd -m <name>

8. Configure the opuser user to limit the size of a file the user can create. Use a negative number for unlimited.

chuser fsize=<#> <name>

9. Add the OpenPages user to the bin,security, and audit Oracle groups. Optionally, you can add the user to the cron group.

usermod -g staff -G bin,security,cron,audit opuser

10. Change the password for the OpenPages user using the following command:

passwd <name>

11. Enter a new password at the New Password prompt.



Preparing the OpenPages Application

• • • • • • • • • •and Database Server

Before beginning the installation, perform the following tasks on your cluster administrator server and cluster member server (if used).

Preparing the EnvironmentBefore starting the upgrade, ensure the following conditions are met on all of your servers.

Windows

Ensure that you have access to the Windows Registry via regedit. Ensure that there is network access to the server that will host the Oracle database. Enable Data Execution Prevention (DEP) in Microsoft Windows Server 2008 R2 for

essential Windows programs and services only (see below).

AIX

Ensure that there is network access to the server that will host the Oracle database. Set up the required users and groups using the appropriate permissions for installing

applications.

Enabling DEP for Essential Windows Programs and ServicesThe information in this topic applies only to Windows environments.

By default, Windows Server 2008 uses settings designed to prevent an application from executing unauthorized code. However, this setting can interfere with the OpenPages. During the software installation, you should configure DEP to allow the installers to work, as shown below.

To enable Data Execution Prevention (DEP) for essential Windows programs and services only, see the steps below.

Steps:

1. Log onto each server in the environment.2. Launch Windows Explorer.3. In the left side, right-click Computer and select Properties from the menu. 4. In the System Properties window, click the Advanced System Settings link. 5. On the Advanced tab, under the Performance heading, click the Settings button.6. In the Performance Options window, click the Data Execution Prevention tab, and

then select Turn on DEP for essential Windows programs and services only. 7. Click OK and then restart your system to enable the change.8. Repeat these steps in each server where you will be installing IBM OpenPages GRC

Platform.

When the installation of all software is complete, you can return the DEP to its previous setting, as necessary.



VMWare Configuration Requirements — Windows OnlyThe information in this topic applies only to Windows environments.

The VMWare performance on a Virtualized system is comparable to native hardware. You can use the hardware guidelines for the application server or rpeorting server for sizing VM requirements.

Notes

Virtualization of the database server is not supported. Cloning of OpenPages application server VMs is not supported.

Each VM server machine must meet these software requirements:

VMWare ESX Server version 3.5.1 or 4.0 VMWare Infrastructure Client version 4.0 Microsoft Windows 2008 R2



3
Getting Started
Use this chapter to begin the installation of the IBM OpenPages GRC Platform.

This chapter contains the following topics:

About the Media Pack on page 36 How to Install OpenPages on page 38 Additional Information for Installation on page 44


• • • • • • • • • •About the Media Pack

The IBM OpenPages GRC Platform media pack contains a number of DVDs, depending upon which features your organization purchased. The following table lists the DVDs in the media pack and describes the contents of each DVD.

Note: Throughout this guide, each DVD will be referred to by the Reference name listed in the table.

Table 3-1: Installer DVDs for OpenPages

DVD Reference Contains

Installer for Windows Disc 1 of 2 Installer Disc 1 • IBM OpenPages GRC Platform Installer• OpenPages installation configuration files,

which include database installation scripts. • Cognos 8 Go! Office installer• IBM Cognos Framework Manager installer• OpenPages Workflow Studio installer

Installer for Windows Disc 2 of 2 Installer Disc 2 • Installer for Cognos• Installer for CommandCenter

Installer for AIX Disc 1 of 2 Installer Disc 1 • IBM OpenPages GRC Platform Installer• OpenPages installation configuration files,

which include database installation scripts. • Cognos 8 Go! Office installer• IBM Cognos Framework Manager installer• OpenPages Workflow Studio installer

Installer for AIX Disc 2 of 2 Installer Disc 2 • Installer for Cognos• Installer for CommandCenter

Upgrade Pack for Version 6.0 Upgrade Pack • Upgrade utilities for migrating from Version 6.0 to Version 6.0.1

Version 6.0.1.1 Fix Pack Fix Pack • OpenPages 6.0.1.1 fix pack installer (which must be installed after the base 6.0.1 code is installed)

Documentation Documentation • OpenPages documentation

If your OpenPages product includes Oracle WebLogic Server, the following DVDs will be included in the media pack:

Installer with Application Server for Windows Disc 1 of 2

Installer Disc 1 • IBM OpenPages GRC Platform Installer (also installs WebLogic Server)

• OpenPages installation configuration files, which include database installation scripts.

• Cognos 8 Go! Office installer• IBM Cognos Framework Manager installer• OpenPages Workflow Studio installer

Installer with Application Server for Windows Disc 2 of 2

Installer Disc 2 • Installer for Cognos• Installer for CommandCenter

Chapter 3: Getting Started


If your OpenPages product includes Oracle Database, the following DVDs will be included in the media pack:

Repository Installer for Windows Disc 1 of 2

Repository Installer Disc 1

• Oracle database server and the OpenPages repository installer

• Oracle Client 64-bit installer

Repository Installer for Windows Disc 2 of 2



Repository Installer for AIX Disc 1 of 2


• Oracle database server and the OpenPages repository installer


Repository Installer for AIX Disc 2 of 2



If your OpenPages product includes modules, the following DVD will be included in the media pack:

Modules Modules • OpenPages module installer

Table 3-1: Installer DVDs for OpenPages

DVD Reference Contains



• • • • • • • • • •How to Install OpenPages

OpenPages works with a suite of third-party software packages, including the Oracle database, WebLogic Server or WebSphere Application Server server, and Cognos 8 Business Intelligence.

Although there are several paths to successfully install OpenPages, the sections below represent the recommended sequence.

Most OpenPages environments will use the same operating system on all machines, the database server(s), the application server(s), and the reporting server(s). The following sections provide an outline for installing the OpenPages application for each operating system.

Choosing the Installation Setup This section describes the different installation setups for installing OpenPages.

Two Machines. For light loads, such as a testing or staging environment, install the OpenPages application and CommandCenter on a machine where the WebLogic Server or WebSphere Application Server server is located. A second machine hosts the Oracle database server. This is not a recommended installation for a production environment.

Three Machines. For moderate loads, use a three-machine configuration: one database server, one application server, and one reporting server. Install the OpenPages application on a single machine with the WebLogic Server or WebSphere Application Server server software. The Oracle database server software and CommandCenter are each installed on a separate machine.

Multiple Machines. To scale for heavier user loads, you have the option of scaling the OpenPages vertically or horizontally by configuring additional nodes. Scaling either vertically or horizontally requires the use of a load balancer to distribute the incoming requests across the nodes.

Clustering is discussed in more detail in Appendix B “Configuring Clustered Environments” on page 219.



About Installing OpenPages in a Windows/WebLogic Server EnvironmentThe following procedure describes the order in which you perform tasks during the installation of the OpenPages environment on systems running Microsoft Windows. In a Windows-based environment, the application server will use the Oracle WebLogic Server.

Refer to the “Checklist for an OpenPages Installation” on page 43, if desired.

Task 1: Before Beginning the InstallationBefore starting to install the OpenPages environment:

1. Decide which type of OpenPages environment will meet your needs, either a single server or a cluster environment. See “Planning Your Installation” in Chapter 1 on page 9.

2. Ensure that your systems meet the required software and hardware prerequisites. See Chapter 2 “Prerequisites” on page 15.

Task 2: Installing the Database ServerOn the server that will host the Oracle database, perform the following tasks:

1. Use the IBM OpenPages GRC Platform Installer for Repository to install Oracle Database software and configure many required database elements. See Chapter 4 “Installing the Database Software” on page 49.

The OpenPages application installation kit installs the Oracle database and configures many required database elements.

Task 3: Installing the Application ServerThe tasks required to install the OpenPages application on a admin server or a managed server are the same. During the OpenPages application installation, you will configure the role for each server.

On each server that will host the OpenPages application, perform the following tasks:

1. Install the WebLogic Server on the application server machine. • If you purchased the WebLogic Server software from a third-party vendor, you will

need to manually install WebLogic Server before the OpenPages application. See Appendix H “Manually Installing the Application Server” on page 331.

• If you purchased the WebLogic Server from IBM, the software will be installed during the OpenPages application installation.

2. Install the Oracle Client and the OpenPages application. • Use the IBM OpenPages GRC Platform Installer for Repository to install the 64-bit

Oracle Client on the application server.3. Install the OpenPages application. The OpenPages application installer can load the

OpenPages Database Schema into the database. See “Installing the OpenPages Application” on page 65.

Note: You have the option of manually installing the OpenPages Database Schema. See “Installing the OpenPages Database Schema” on page 339 before installing the OpenPages application.



Task 4: Installing the Reporting ServerOn the reporting server that will host CommandCenter, perform the following tasks:

1. Use the IBM OpenPages GRC Platform Installer for Cognos to install the 32-bit Oracle Client on the reporting server.

2. Install the Cognos software and configure the Content Store database schema. See “Installing Cognos and Content Store” on page 95.

3. Configure your Web server. See “Configuring Your Web Server” on page 110. Or, allow the IBM OpenPages GRC Platform Installer for Cognos to configure the Web server.

4. Install the CommandCenter software. See “Installing CommandCenter” on page 130.

Note: You have the option of manually installing the CommandCenter database schema. See Appendix G “Creating the CommandCenter Database Schema” on page 315 before installing CommandCenter.

5. Perform CommandCenter post-install configurations. See “CommandCenter Post-Installation Steps” on page 135.

Task 5: Post-Installation TasksAfter installing the database, the OpenPages application, and CommandCenter, refer to the post-installation chapters to review the required and optional tasks:

1. Perform post-installation tasks for the OpenPages environment. See Chapter 8 “Performing Post-installation Tasks” on page 139.

2. If your OpenPages environment will be load balanced, see Appendix B “Configuring Clustered Environments” on page 219.

3. If your OpenPages environment uses Secure Sockets Layer (SSL) security, see Appendix C “Configuring SSL” on page 245.

4. If your OpenPages environment will be installed on a single system, see Appendix E “Configuring OpenPages on One Machine” on page 305.

5. If your organization uses a single sign-on solution, see Appendix F “Integrating Single Sign-on with OpenPages” on page 307 to integrate OpenPages.

Task 6: Apply the IBM OpenPages GRC Platform 6.0.1.1 PatchThe IBM OpenPages GRC Platform 6.0.1.1 patch is part of the 6.0.1 release.

Once you have updated your system to the IBM OpenPages GRC Platform 6.0.1 product, you must apply the 6.0.1.1 patch.

The IBM OpenPages GRC Platform 6.0.1.1 patch and instructions can be found in your installation media kit.



About Installing OpenPages in an AIX/WebSphere Application Server Environment

The following procedure describes the order in which you perform the tasks during the OpenPages installation on systems running AIX. In an AIX-based environment, the application server uses the WebSphere Application Server.

Refer to the “Checklist for an OpenPages Installation” on page 43, if desired.

Task 1: Before Beginning the InstallationBefore starting to install the OpenPages environment:

1. Decide which type of OpenPages environment will meet your needs, either a single server or a cluster environment. See “Planning Your Installation” in Chapter 1 on page 9.

2. Ensure that your systems meet the required software and hardware prerequisites. See Chapter 2 “Prerequisites” on page 15.

Task 2: Installing the Database ServerOn the server that will host the Oracle database, perform the following tasks:

1. Use the IBM OpenPages GRC Platform Installer for Repository to install Oracle Database software and configure many required database elements. See Chapter 4 “Installing the Database Software” on page 49.

The OpenPages application installation kit installs the Oracle database and configures many required database elements.

Task 3: Installing the Application ServerThe tasks required to install the OpenPages application on a cluster administrator or a cluster member are the same. During the OpenPages application installation, you will configure the role for each server.

On each server that will host the OpenPages application, perform the following tasks:

1. Install the WebSphere Application Server software on the application server machine. See Appendix H “Manually Installing the Application Server” on page 331.

2. Install the Oracle Client and the OpenPages application.• Use the IBM OpenPages GRC Platform Installer for Repository to install the 64-bit

Oracle Client on the application server. 3. Install the OpenPages application. The OpenPages application installer can load the

OpenPages Database Schema into the database. See “Installing the OpenPages Application” on page 65.

Note: You have the option of manually installing the OpenPages Database Schema. See “Installing the OpenPages Database Schema” on page 339 before installing the OpenPages application.

Task 4: Installing the Reporting ServerOn the reporting server that will host CommandCenter, you will perform the following tasks:

1. Use the IBM OpenPages GRC Platform Installer for Cognos to install the 32-bit Oracle Client on the same machine as the Oracle database server.

2. Install the Cognos software and configure the Content Store database schema. See Chapter 6 “Installing Cognos and Content Store” on page 95.

3. If you plan to manually install the CommandCenter database schema, see Appendix G “Creating the CommandCenter Database Schema” on page 315.

4. Configure your Web server. See “Configuring Your Web Server” on page 110. Or, allow the IBM OpenPages GRC Platform Installer for Cognos to configure the Web server.



5. Install the CommandCenter software. See “Installing CommandCenter” on page 130.

Note: You have the option of manually installing the CommandCenter database schema. See Appendix G “Creating the CommandCenter Database Schema” on page 315 before installing CommandCenter.

6. Perform CommandCenter post-install configurations. See “CommandCenter Post-Installation Steps” on page 135.

Task 5: Post-Installation TasksAfter installing the database, the OpenPages application, and CommandCenter, refer to the post-installation chapters to review the required and optional tasks:

1. Perform post-installation tasks for the OpenPages environment. See Chapter 8 “Performing Post-installation Tasks” on page 139.

2. If your OpenPages environment will be load balanced, see Appendix B “Configuring Clustered Environments” on page 219.

3. If your OpenPages environment uses Secure Sockets Layer (SSL) security, see Appendix C “Configuring SSL” on page 245.

4. If your OpenPages environment will be installed on a single system, see Appendix E “Configuring OpenPages on One Machine” on page 305.

5. If your organization uses a single sign-on solution, see Appendix F “Integrating Single Sign-on with OpenPages” on page 307 to integrate OpenPages.

Task 6: Apply the IBM OpenPages GRC Platform 6.0.1.1 Patch

This task is required.

The IBM OpenPages GRC Platform 6.0.1.1 patch is part of the 6.0.1 release.

Once you have installed the IBM OpenPages GRC Platform 6.0.1 product, you must apply the 6.0.1.1 patch.




Checklist for an OpenPages InstallationBefore you begin the installation process, print this checklist and complete the steps listed in Table 3-2 in the order shown.

Table 3-2: Checklist for a Cluster Administrator Installation

Task Checklist

1. 1. Perform the steps in “Getting Started” on page 35.

2. Perform the steps in “Installing the Database Software” on page 56.

3. If you have only one database installation on the machine, perform the steps in “Change the PATH variable as follows:” on page 63.

4. If you purchased WebLogic Server from another vendor or are using WebSphere Application Server, install the appropriate server software before installing the OpenPages application. See “Manually Installing the Application Server” on page 331, then continue with the checklist. If you purchased WebLogic Server from IBM, skip this task and go to the next step.

5. Have you decided to separately install the OpenPages Database manually using the wrapper script?

Yes: Perform the steps in “Installing the OpenPages Database Schema” on page 339, then continue with the checklist.

No: Go to the next step.

6. Install Oracle Client on the administration server machine. See “Installing the 64-bit Oracle Client” on page 74.

7. Install the OpenPages application on the application server machine. See “Installing the OpenPages Application and Workflow Server” on page 79.

8. Install the Cognos 8 Business Intelligence software on the reporting server machine. See “Installing Cognos and Content Store” on page 95.

9. Install Oracle Client on the reporting server. See “Installing the 32-Bit Oracle Client” on page 101.

10. Configure the Web server to allow CommandCenter pages to display. See “Configuring an IIS 7.0 Web Server - Windows only” on page 110.

11. Use the Cognos configuration tool to complete the Cognos 8 Go! Dashboard installation. See “Configuring Cognos 8 Go! Dashboard” on page 116.

12. Use the Cognos configuration tool to configure CommandCenter to access the database. See “Set Database Connection Properties for CommandCenter” on page 119.

13. Install CommandCenter on the reporting server machine. See “Installing OpenPages CommandCenter” on page 123.

14. Perform the post-installation steps in Chapter 8 “Performing Post-installation Tasks” on page 139.

15. Optional: Perform the steps in Appendix B “Configuring Clustered Environments” on page 219.

16. Optional: Perform the steps in Appendix C “Configuring SSL” on page 245.

17. Optional: Perform the steps in Appendix D “Changing Default Port Numbers” on page 283.

18. Optional: Perform the steps in Appendix F “Configure the Single Sign-on Logout Destination” on page 309.

19. Optional: Perform the steps in Appendix J “Installing Client-Side Applications” on page 349.



• • • • • • • • • •Additional Information for Installation

This section describes additional information that you may find helpful during or after the installation.

Port Assignments and Servers List An OpenPages deployment contains both dedicated ports and ports that are dynamically assigned for each installation.

These default ports can be changed after installation. See the Changing Default Port Numbers chapter.

Fixed Ports

Table 3-3 lists the fixed default port assignments used by the OpenPages installation.

Table 3-3: Default Fixed Port Assignments

Description Windows Port AIX Port

Database server

Oracle console application port 1158 1158

OpenPages database instance port 1522 1522

OpenPages application server (web server/workflow)

OpenPages admin server port (WebLogic/WebSphere port) 7001 9060

OpenPages admin server SSL port (WebLogic/WebSphere port) 7002 10110

OpenPages application port 7009 10108a

a. Any additional OpenPages installations will increment by 1, as in 10081, 10082, etc.

OpenPages application SSL port 7010 10111

Workflow admin server port (WebLogic port) 49901 9061

Workflow admin server SSL port (WebLogic port) 49902 9044

Workflow application port 49951 20108b

b. Any additional IBPM installations will increment by 1, as in 20081, 20082, etc.

Workflow application SSL port 49952 20111

CommandCenter server

CommandCenter port 80 80

Framework Generator port 8080 8080



Files Containing Port NumbersThe following tables list property files on the OpenPages admin server that contain the above port numbers.

Windows

AIX

Table 3-4: Files Containing Default Port Numbers -- Windows

Port File Parameter Name

OpenPages admin server port <OP_Home>\aurora\conf\ server.config.props

WC_adminhost

OpenPages admin server SSL port WC_adminhost_secure

OpenPages application port <OP_Home>\temp\aurora\conf\ OPSERVER_STATUS.txta

a. This file will contain the HTTP and HTTPS ports for all OpenPages application instances associated with the current admin server. Or, refer to the individual <server_name>-OpenPagesServer#-server.properties files.

WC_defaulthost

OpenPages application SSL port WC_defaulthost_secure

Workflow admin server port <OP_Home>\aurora\conf\ <server_name>-InterstageBPMCS#-server.properties.config.props

url.path.workflow. admin

OpenPages database instance port <Oracle_Home>\NETWORK\ADMIN\ tnsnames.ora

Framework Generator port <OP_Home>\aurora\conf\ aurora.properties

cognos.framework

CommandCenter port cognos.server

Table 3-5: Files Containing Default Port Numbers -- AIX

Port File Parameter Name

OpenPages admin server port <OP_Home>/temp/wasconfig/OpenPagesCell.dmgr.config.props

WC_adminhost

OpenPages admin server SSL port WC_adminhost_secure

OpenPages application port <OP_Home>/temp/wasconfig/OpenPagesCell.<server_name>-OPNode<#>Server<#>.config.props

WC_defaulthost

OpenPages application SSL port WC_defaulthost_secure

Workflow admin server port <OP_Home>/temp/wasconfig/IBPMCell.dmgr.config.props

WC_adminhost

Workflow admin server SSL port WC_adminhost_secure

Workflow application port <OP_Home>/temp/wasconfig/IBPMCell.<server_name>-OPNode<#> Server.config.props

WC_defaulthost

Workflow application SSL port WC_defaulthost_secure

Oracle database instance port <Oracle_Home>/NETWORK/ADMIN/tnsnames.ora

Framework Generator port <OP_Home>/aurora/conf/aurora.properties

cognos.framework

CommandCenter port cognos.server



Dynamically Assigned PortsPort numbers for OpenPages servers not listed, such as the IIS Web application server and OpenPages application managed servers, are assigned dynamically during installation.

After installation, you can view all port assignments in OpenPages property files.

Windows

<OP_Home>\aurora\conf\OPSERVER_STATUS.txt

AIX

<OP_Home>/temp/wasconfig/*.props

In an AIX environment, there are multiple OpenPages property files, each with a .props extension. The OpenPages application server and workflow server port information is found in:

OpenPagesCell.dmgr.config.props OpenPagesCell.<server_name>-OPNode<#>Server<#>.config.props IBPMCell.dmgr.config.props IBPMCell.<server_name>-IBPMNode<#>Server.config.props

On a cluster system, the OpenPagesCell.<server_name>-OPNode1Server1.config.props file and IBPMCell.<server_name>-IBPMNode1Server.config.props file contain port information for that managed server only. If there were a second managed server within the same machine (vertical cluster), the port information would appear in OpenPagesCell.<server_name>-OPNode1Server2.config.props and IBPMCell.<server_name>-IBPMNode2Server.config.props, and so on.

In a horizontal cluster, the managed server numbering in the .props file name restarts at 1 for each cluster member machine.

Servers ListAfter installation, you can view the list of server host names in the following files.

Windows

The servers are in the same property file as the port numbers, for example: <OP_Home>\aurora\conf\OPSERVER_STATUS.txt.AIX

OpenPagesCell.servers.list.txt IBPMCell.servers.list.txt



About Log Files

The installation programs write errors and other information to the following log files.

OpenPages Environment LogsThe following logs provide information on the OpenPages installation.

OpenPages applicationThe following logs are created during the OpenPages installation.

Database installer. Logs related to the database installer are created in the <Oracle_Data_Home>\ia\server112_se_x64 directory.

• OpenPages_Oracle_Embedded_Install_InstallLog.log• OpenPages_OEI_Install_Debug.log

Oracle Client. Logs related to the Oracle Client installation are created in the <Oracle_Data_Home>\ia\server112_se_x64 directory.

• OpenPages_Oracle_Embedded_Install_InstallLog.log• OpenPages_OEI_Install_Debug.log

OpenPages application. Logs related to the OpenPages application installation are created in <OP_Home>\logs directory.

• OpenPages_60_InstallLog.log• openpages_installer_debug.log• OpenPages_embedded_bea_install_debug.log

Workflow serverLogs related to successfully processed IBPM trigger notification files are located in the <OP_Home>\logs directory.

• ibpm_module_installer_debug.log• IBPM_Installer_MM_InstallLog.log

Application server WebLogic Server. Logs related to the WebLogic Server installer are located in the

<OP_Home>\logs directory.• IBPM_Installer_MM_InstallLog.log

WebSphere Application Server. Logs related to the WebSphere Application Server installer are located in the <OP_Home>/temp/wasconfig/ directory.



CommandCenter/Cognos LogsThe following logs provide information on the Cognos and CommandCenter installations.

CommandCenter applicationLogs related to the CommandCenter installation are created in the <OP_Home>|commandcenter|logs directory.

OpenPages_6.0_CommandCenter_InstallLog.log OpenPages_6.0_CommandCenter_Installer_Error.log OpenPages_6.0_CommandCenter_Installer_Debug.log OpenPages_6.0_CommandCenter_debug.log OpenPages_CommandCenter_ScriptActions_Debug.log OpenPages_CommandCenter_ScriptActions_Errors.log

Cognos applicationsLogs related to the Cognos software installations are created in the <OP_Home>\Cognos\logs\ directory.

OpenPages_6.0_Cognos_InstallLog.log OpenPages_6.0_Cognos_Installer_Error.log OpenPages_6.0_Cognos_Installer_Debug.log OpenPages_6.0_Cognos_debug.log



4
Installing the Database Software
The OpenPages Repository installation program installs the Oracle Database 11g R2 Server software and creates the Oracle database instance.


Checklist for Installing the Oracle Database Software on page 51 Before You Begin on page 52 Installing the Database Software on page 56 Updating the PATH System Environment Variable on page 63


About the Oracle Database Server

• • • • • • • • • •Installation

Because you purchased the Oracle database from IBM, you can use the IBM OpenPages GRC Platform Installer for Repository to install the Oracle Database 11g R2 Server software and create the OpenPages database instance.

Before you begin, confirm that you have the hardware and software prerequisites described in “Hardware Prerequisites” on page 16 and “Software Prerequisites” on page 23.

After using the OpenPages Repository installation program to install the Oracle Database server and create your OpenPages database instance, you must install an Oracle Client on all application server machines.

The IBM OpenPages GRC Platform Installer for Repository performs the following tasks:

Installing the Oracle Database 11g R2 Server software Adding an Oracle Listener Creating the Oracle database instance Adding a Local Net Service Name

Because you purchased the Oracle database from IBM, you can use the IBM OpenPages GRC Platform Installer for Repository to install the Oracle Database 11g R2 Server software and create the OpenPages database instance.

Before you begin, confirm that you have the hardware and software prerequisites described in “Hardware Prerequisites” on page 16 and “Software Prerequisites” on page 23.

After using the OpenPages Repository installation program to install the Oracle Database server and create your OpenPages database instance, you must install an Oracle Client on all application server machines.

The IBM OpenPages GRC Platform Installer for Repository performs the following tasks:

Installing the Oracle Database 11g R2 Server software Adding an Oracle Listener Creating the Oracle database instance Adding a Local Net Service Name

Chapter 4: Installing the Database Software


Checklist for Installing the Oracle

• • • • • • • • • •Database Software

Use the following checklist to guide you through installing the OpenPages Repository. Each task below has several steps.

Table 4-1: Checklist for Oracle Installation

Task Checklist

1. Review the information in “Before You Begin” on page 52.

2. Perform the required prerequisites as described. See “Pre-requisites” on page 52.

3. AIX-only: Perform the required prerequisites for AIX environments. See “Additional AIX-Only Prerequisites” on page 53.

4. Use the OpenPages Embedded Installer to install the Oracle database software. See “Installing the Database Software” on page 56.

5. Add the Oracle software installation directory to the PATH environment variable. See “Updating the PATH System Environment Variable” on page 63.



• • • • • • • • • •Before You Begin

Before you install the OpenPages Repository, make sure your system and environment meet the required prerequisites, as discussed in Chapter 2 “Prerequisites” on page 13.

Also perform the tasks in this section.

Note: For AIX installations, also have the names of the Oracle users created for the OpenPages installation process. See “Setting Up Required Users and Groups” on page 25.

Pre-requisitesBefore you begin, confirm that you have the software and hardware prerequisites described in Chapter 2 “Prerequisites” on page 13.

Removing Environment Variables


Before running the installer:

1. Verify that the following system environment variables are NOT defined, as required for Oracle 11g:

• ORACLE_BASE• ORACLE_HOME• PERL5LIB• TNS_ADMIN

Note: If any of the above variables is defined, you must remove the variable and reboot the system before starting the installation.

2. Remove the Oracle path from the PATH environment variable, if present.3. Make note of the location of the TMP environment variable.

Copying the Installation Files

This task is optional.

Before starting the Oracle database install, you should copy the installer kit files from the IBM OpenPages GRC Platform media pack to the local system to improve performance.

Steps:

1. Log on to your database server as a user with administrative privileges.

Note: For AIX installs, use oracle user you created for the OpenPages installation.

2. Launch a Command Prompt window (using the Run as Administrator option) or AIX shell as the oracle user you created for the OpenPages installation.

3. Copy the following directory from the Repository Installer Disc 1 DVD or network share location to the local system:

Windows

OP_6.0.1_Embedded_DVD_1

AIX

OP_6.0_Non_Embedded_DVD_1

Note: For AIX, make sure you have full rights to the local installation directory.




Disabling Anti-Virus


If an anti-virus package is running on the application server, for faster installation times, you may disable the anti-virus software before running the database installation.

Additional AIX-Only PrerequisitesThis task is required.

If you are installing onto an AIX environment, make sure your system and environment meet these additional required prerequisites.

Ensure that the following operating system filesets are installed and committed, as required for Oracle 11g R2:

Create AIX Passwords


Make sure you have created the required users and groups for AIX. See “Create Users and Groups for AIX” on page 25.

Set File Size of /tmp Directory


Ensure that the /tmp directory on the 6.0.1 database server is set to a minimum size of 4GB.

Change the Temp Directory


By default, the /tmp directory is configured as the TEMP directory. You can change the TEMP directory by adding the following variables to the .profile of the user performing the installation.

Steps:

1. Log on the 6.0.1 application server as the non-root user that will install the OpenPages application.

2. Use the following commands to change the TEMP directory:

export IATEMPDIR=<temp_directory> export TEMP=<temp_directory> export TMP=<temp_directory> export TMPDIR=<temp_directory> export TEMPDIR=<temp_directory>

where <temp_directory> is the path to the TEMP directory.

Example

export IATEMPDIR=/opt/temp export TEMP=/opt/temp export TMP=/opt/temp export TMPDIR=/opt/temp export TEMPDIR=/opt/temp

• bos.adt.base • bos.adt.lib • bos.adt.libm

• bos.perf.perfstat • bos.perf.libperfstat • bos.perf.protocols

• rsct.basic.rte • rsct.compat.clients.rte • xIC.aix61.rte


Creating the Oracle Installation Directory


Before installing the OpenPages Repository, create the directory where the software will be installed.

Steps

1. Log on to your 6.0.1 database server as a non-root user with administrative privileges.2. In an AIX shell enter the following commands:

mkdir -p <Software_directory> chown -R oracle:install <Software_directory>

Where:

<Software_directory> is the Oracle installation directory.

Example

mkdir -p /usr/oracle chown -R oracle:oinstall /usr/oracle

3. Use the following command to configure oracle and oinstall as users:

chown -R oracle:oinstall /opt/oei/Oracle11gR2

The installation directory, all its parent directories, and all its subdirectories must have 775 permissions during the installation. The permission can be set in the operating system or using a file system access control list.

Check Prerequisites


Before running the Installer for Repository, you must run the rootpre.sh script that loads the kernels extension required for the installations.

Note: You must run the script as the root user.

Steps:

1. Log on to your database server as a user with administrative privileges.2. Launch an AIX shell and navigate to the \OEI_Server_Client_64bit\data directory

within the installation kit files you copied, for example:

/opt/OEI_11GR2_DVD_1/OEI_Server_Client_64bit/data

Where: <Installer_Home> is the path to the installation kit directory.

3. Run the prerequisite checker as follows:

./rootpre.sh

Note: For AIX installs, you must run the rootpre.sh as the root user.

The script displays information on the console. When the script is finished, a log file is created in the /tmp folder named rootpre.out_yy-mm-dd.hh:mi:ss.



Validate the Environment


Before running the Open Pages Repository installer, you can run the ./preinstchk.sh script that will check that your system meets all system prerequisites.

Notes

You must run the script as the root user. Ensure that JDK/JRE 1.6 is installed on the server.

Steps:

1. Log on to your database server as the root user.2. Launch an AIX shell and navigate to the \OEI_Server_Client_64bit\data directory

within the installation kit files you copied, for example:

/opt/OEI_11GR2_DVD_1/OEI_Server_Client_64bit/data

Where: <Installer_Home> is the path to the installation kit directory.

3. Run the prerequisite checker as follows:

./preinstchk.sh

Note: For AIX installs, you must run the ./preinstchk.sh script as the root user.

When the script is finished, if any prerequisites are missing, they will be listed in the location specified in the preinstchk.properties file.



• • • • • • • • • •Installing the Database Software

The following sections describe how to use the IBM OpenPages GRC Platform Installer for Repository to install and configure the database software, using either of two modes, interactive mode or silent mode.

• Interactive Mode. The interactive mode uses graphic screens to collect the information required for installing the various components.

• Silent Mode. The silent mode uses information entered into a parameter (or response) file. You use command line prompts to initiate the installation scripts, which take the required information from the parameter file.

Note: The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installer will fail. You will need to refer to log files to determine the exact cause of the failure.

See “Installing the Database Software in Interactive Mode” on page 57 or “Installing the Database Software in Silent Mode” on page 59.



Installing the Database Software in Interactive ModeThe following steps describe how to run the IBM OpenPages GRC Platform Installer for Repository, openpages_oei.exe, to install the Oracle database software and OpenPages Database Schema using the interactive graphical interface installer screens.

Notes:

• Verify that the ORACLE_BASE, ORACLE_HOME, and TNS_ADMIN system environment variables are NOT defined, as described in “Before You Begin” above.

• If you are running the interactive mode installer on an AIX server, you must run the installer in graphical mode using an application such as X Windows.

Steps:

1. Log on to the 6.0.1 database server as a user with administrative privileges.

Note: For AIX installs, use the oracle user you created for the OpenPages installation.


Note: For AIX installs, you must run the installer in graphical mode using an application such as X Windows.

3. Navigate to the following location within the installer kit files you copied from the Repository Installer Disc 1 DVD:

OEI_Server_Client_64bit_Win\Disk1\InstData\VM

4. Launch the Installer for Repository using the following command:

Windows

openpages_oei.exe

AIX

./openpages_oei.bin -i swing

Where -i swing launches graphic mode

5. On the Welcome screen, click Next.6. On the License Agreement screen:

a. Review and accept the license agreement.b. Click Next.

7. On the Installation Information screen:a. Provide information about the database installation. The following table provides a

description of these fields:

b. Click Next.

Field Description

Installation Information

Select Server to install the database server.

Oracle Software Installation Location

Enter a location where the database server software is to be installed. This will be <ORACLE_HOME>.

Windows Enter the drive letter followed by a colon, such as C:

AIX Enter the location, such as /opt/OEI/Oracle.



8. On the Database Instance Information screen:a. Type the information to set up the connection to the database. The following table

provides a description of these fields.

b. Click Next.9. Create passwords for the listed users.

10. On the Pre-Installation Summary screen:a. Review your selections. Click Previous to return to an earlier screen to make any

required changes.b. When satisfied, click Install to begin the install process.

The installation takes approximately 30 minutes.

11. Click Done to exit the installer when it finishes.

You now have Oracle 11g R2 installed and a database instance created.

12. To confirm that the installation was successful, access the Oracle Enterprise Manager login page at:

https://<Server_Name>:1158/em

Where: <Server_Name> is the name of your database server and 1158 is the database instance port. The database server host name can be found in the tnsnames file on the database server, located under <Oracle_Home>\software\NETWORK\ADMIN.

Field Description

Database Instance Installation Location

Enter a location where the database data is to be installed. This will be <ORACLE_DATA_HOME>.

Windows Enter the drive letter followed by a colon, such as C:.


Database Instance Name

Enter the Service ID (SID) to assign for the OpenPages database instance. By default, this value is OP.

Database Instance Port

Enter the port number to assign to the database instance that was installed on the database server. By default, this port is 1522.

Field Description

SYSTEM Enter a password to assign to the SYSTEM user (This is the Oracle Superuser.)

SYS Enter a password to assign to the SYS user.

DBSNMP Enter a password for the Oracle Intelligent Agent.

SYSMAN Enter a password for the default Enterprise Manager Super Administrator.



Installing the Database Software in Silent ModeThis section provides instructions for installing the Oracle database software in silent mode.

Silent installation of the database is accomplished by supplying the installer with values from a parameter file, instead of providing answers interactively through graphical interface screens. When running the command from a command line, the -i silent flag launches the installer in silent mode and installs the database with no graphic output using the parameter file specified with -f.

IMPORTANT!

• The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installer will fail. You will need to refer to log files to determine the exact cause of the failure.

• Verify that the ORACLE_BASE, ORACLE_HOME, and TNS_ADMIN system environment variables are NOT defined, as described in “Before You Begin” above.

• Windows-only: In the Windows environment, the silent installer does not display a progress bar. After starting the installer, the system returns the command prompt. You would need to launch Windows Task Manager to ensure that the installer is still running.

Task 1: Edit the Parameter FileThe following steps describe how to edit the parameter file to include the information required by the installer.

Steps:

1. Log on to the 6.0.1 database server as a user with administrative privileges.





4. Edit the parameter file:a. Open the ServerInstaller.properties file in a text editor (such as, WordPad in

Windows, VI or Emacs in AIX). b. Modify the parameters listed in the following table:

Parameter Description

Installation type Enter 1 to install the server software:• INSTALL_ORACLE_SERVER=1


Enter the Windows drive or AIX directory where the database server software will be installed. For example:

Windows SERVER_SOFTWARE_INSTALL_DRIVE=C:

AIX SERVER_SOFTWARE_INSTALL_DRIVE=/opt/oei/oracle

Note: For Windows, the colon is required.

Database Instance Port Enter the port number to be used for the database instance. The port must be between 1024 and 65535. For example:

DB_INSTANCE_PORT=1522



5. Save and close the ServerInstaller.properties file.

Database Instance Installation Location

Enter the drive or directory where the database server software will be installed. For example:

WindowsDB_INSTANCE_INSTALL_DRIVE=C:

AIXDB_INSTANCE_INSTALL_DRIVE=/opt/oei/oracle

Note: For AIX, this directory must exist.

Database Instance Name Enter the name of the OpenPages database instance. By default, this is OP. The name must follow the standard guidelines for a database instance name:

• The only characters allowed are the alphanumeric characters (A-Z or a-z and 0-9), the underscore (_), the dollar sign ($), and the hash character (#);

• the first character of the instance name must be A-Z (or a-z);

• the instance name is limited to 8 characters.

Database User Passwords Enter passwords for the listed users. Make sure you scroll down on the screen to fill in all of the necessary fields. The database users are:

• SYSTEM (This is the Oracle superuser.)• SYS • DBSNMP• SYSMAN

The passwords for the database users must follow these rules:

• The maximum length of the password cannot exceed 30 characters;

• the only characters allowed are the alphanumeric characters (A-Z or a-z and 0-9), the underscore (_), the dollar sign ($), and the hash character (#);

• the first character of the instance name must be A-Z (or a-z) or 0-9.

Keep the list of passwords handy; you will need them during the OpenPages application installation.




Task 2: Run the Installer1. On to the 6.0.1 database server, navigate to the following location within the installer

kit files you copied from the Repository Installer Disc 1 DVD:


2. Run the installer using the silent parameter to launch in silent mode.

Windows

openpages_oei.exe -i silent

AIX

openpages_oei.bin -i silent -f ServerInstaller.properties

Where:

-i silent launches silent mode

-f ServerInstaller.properties specifies the properties file to use

3. Refer to the <OP_Home>\logs\OpenPages_60_install.log to determine if the install was successful.

The install log will display a line similar to the following:

Summary Installation Successful

If the installation fails, troubleshoot the failed installation as follows:

a. Open the install log file:

Windows

c:\openpages_data\repository\ia\server112_ac_x64\ OpenPagesOracleEmbeddedInstall_InstallLog.log

AIX

/opt/openpages_data/repository/ia/server112_ac_x64/OpenPagesOracleEmbeddedInstall_InstallLog.log

b. Carefully review the saved text file.c. If you cannot resolve the reported errors, forward the file to OpenPages

representative.

Note: In some rare cases, the installation may hang on the database creation step. If this occurs, it is usually the result of conflicting or incompatible JRE/JDK versions being installed on the same box.



About Non-default Instance ParametersNote that the newly created Oracle instance will have the following parameters set to non-default values.

Table 4-2: Oracle Instance Parameters Set by Installer

Parameter Name Value Default

compatible 11.2.0.0

nls_length_semantics CHAR

Note: CHAR is required for localization.

BYTE

open_cursors 300

optimizer_features_enable 11.2.0.0

optimizer_index_caching 100 0

optimizer_index_cost_adj 1 100

optimizer_mode FIRST_ROWS ALL_ROWS

optimizer_secure_view_merging FALSE

processes 250

sessions 280

pga_aggregate_target 134217728

sga_target 402653184



Updating the PATH System Environment

• • • • • • • • • •Variable

This section describes how to change the PATH environment variable for systems with only one Oracle database installation.

IMPORTANT! Only change the PATH variable if this is the only database installation on this machine.

Updating the PATH VariableUse the following steps to update the PATH variable on the database server.

Steps:

1. Log on to the 6.0.1 database server as a user with administrative privileges.2. Change the PATH variable as follows:

Windows

a. Right-click the Computer icon and select the Properties option.b. In the System Properties dialog box, choose the Advanced System Settings link.c. Click the Environment Variables button.d. Under System Variables, select the PATH variable and click Edit.e. In the Edit System Variable dialog box, add the path to ORACLE_HOME to the

beginning of the PATH, by default:

C:\openpages_data\repository\server112_se_x64\software\bin;

f. Click OK to exit the dialog box.g. Click OK to exit the dialog box.

AIX

Execute the following commands to set the PATH variable, using the appropriate paths (the example assumes the Oracle software is installed in the default location):

a. Set the ORACLE_HOME environment variable on the application server, by default:export ORACLE_HOME=/opt/oracle/openpages_data/repository/server112_se_x64/software

b. Add the $ORACLE_HOME/bin path to the PATH environment variable. For example:export PATH=$ORACLE_HOME/bin:$PATH

c. Refresh the profile by closing and re-opening the AIX shell or run the following command:cd / . .profile



5
Installing the OpenPages Application
This chapter explains how to install the OpenPages application software on either an admin server or managed server.

This chapter consists of the following topics:

About Installing the OpenPages Application on page 66 Checklist for Installing the OpenPages Application on page 67 Before You Begin on page 68 Installing the 64-bit Oracle Client on page 74 Installing the OpenPages Application and Workflow Server on page 79 Re-enabling Global Security – AIX only on page 92 Reinstalling After Incomplete Install on page 93


About Installing the OpenPages

• • • • • • • • • •Application

The OpenPages application installer program installs the following components:

OpenPages application OpenPages workflow server and notification components OpenPages Database Schema (optional) WebLogic Server (if purchased from IBM)

About OpenPages Database SchemaThe OpenPages application requires a set of database users and a tablespace, called the OpenPages Database Schema. You install these database components automatically during the OpenPages application installation or manually using SQL scripts, based on your needs. Both the scripts and the installer create and configure all of the required elements.

During the OpenPages application installation, you will be prompted to install the OpenPages Database Schema. Select Yes to install the schema or No if you have already installed the schema.

Chapter 5: Installing the OpenPages Application


Checklist for Installing the OpenPages

• • • • • • • • • •Application

Use the following checklist to guide you through installing the OpenPages application. Each task below has several steps. For load-balanced environments, each task must be performed on the admin server and each managed server unless otherwise indicated in the steps in this chapter.

Table 5-1: Checklist for Installing OpenPages Application

Task Checklist


2. Install the Oracle Client software. See “Installing the 64-bit Oracle Client” on page 74.

3. Set environment variables. See “Setting the Environment Variables” on page 80.

4. Install the OpenPages application. See “Installing the OpenPages Application and Workflow Server” on page 79.




Before starting the OpenPages application installation process, make sure you perform the following tasks.

PrerequisitesMake sure the server where you are installing the OpenPages application meets the prerequisites listed in Chapter 2 “Prerequisites” on page 13.

Install the Oracle Database Software


The Oracle Database 11g R2 must be installed on the database server before you can install the OpenPages application.

Copy the Installation Files


Before starting the OpenPages application and Oracle Client install, you should copy the installer kit files from the IBM OpenPages GRC Platform media pack to the local system to improve performance.

Steps:

1. Log on to your application server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as the oracle user you created for the OpenPages installation.3. Copy the OEI_Server_Client_64bit directory from the Repository Installer Disc 1

DVD or network share location to the local system.4. Copy the OpenPages installer directory from the Installer Disc 1 DVD:

Windows

OP_6.0.1_Embedded_Installer -- or --

OP_6.0.1_Non_Embedded_DVD_1

AIX

OP_6.0.1_Non_Embedded_Installer




Install the Oracle Client Software


You must install the Oracle Client 64-bit on all application servers where the OpenPages application will be installed. See “Installing the 64-bit Oracle Client” on page 74.

Install the Application Server Software


You must have installed either Oracle WebLogic Server (Windows) or the IBM WebSphere Application Server software (AIX) before you can install the OpenPages application.

If you purchased WebLogic Server from IBM, the IBM OpenPages GRC Platform Installer will install WebLogic Server. If not, you will need to manually install WebLogic Server or WebSphere Application Server before proceeding. See Appendix H “Manually Installing the Application Server” on page 317.

Note: The IBM OpenPages GRC Platform Installer will create its own WebLogic Server profiles and will install into a WebLogic Server environment with pre-defined profiles. You do not need to create WebLogic Server profiles or edit any existing profiles.

Set the Oracle Home Environment Variable


After installing the Oracle client, set the ORACLE_HOME environment variable on the 6.0.1 application server using the instructions in “Setting the Environment Variables” on page 80.

Verify that Servers are Running


If installing OpenPages onto a cluster member server (a non-admin server), make sure that all OpenPages and workflow services (including the database service) on the cluster administrator server are running before performing the install. Having the services running allows the installer to validate user input.

Disable Anti-Virus


If an anti-virus package is running on the 6.0.1 application server, for faster installation times, you may disable the anti-virus software before running the OpenPages installation.

Install Custom OpenPages Database Schema


You have the option to load your own custom configuration data, instead of the default OpenPages Database Schema. You can install the OpenPages application before loading the custom data, but you must have loaded the data before running the OpenPages application itself.

To load your own custom configuration data, contact your OpenPages representative for instructions.



Obtain Installation InformationPlease have the following additional information about server machine types, server roles, host names, ports, and miscellaneous data available:

Whether this is an OpenPages admin server or managed server installation Whether this will be an admin server or one or more managed servers

During the OpenPages installation, you will be asked for the following information. You should have this information available before starting.

The current location of:• Oracle database Home (Oracle_Home)• Oracle data Home• WebSphere Application Server application directory or WebLogic Server

application directory, if installed The location where the following will be installed:

• Directory where all software components in OpenPages application installation will be installed

• OpenPages application server files directory• OpenPages workflow server files directory• OpenPages storage location for files/forms associated with OpenPages objects• Backup and restore locations for OpenPages database and application setting• WebSphere Application Server application directory or WebLogic Server

application directory (if WebLogic Server is not already installed)

Note: This installer creates several new directories for these component, if these directories do not exist. For an AIX environment, make sure the user has proper permission to create all required folders.

The IBM OpenPages GRC Platform Installer creates the following from information entered into the installer fields. You should have the values available before running the installer:

OpenPages admin server host name, port, and SSL port OpenPages workflow server admin port, and SSL port Port used by OpenPages to connect to the Framework Generator Multicast address for the OpenPages workflow server (Optional) Fully qualified domain name of a mail server for OpenPages workflow server

notifications, plus e-mail sender information

The IBM OpenPages GRC Platform Installer requires the existing information, based on the information you entered during the Oracle database installation. You should have the appropriate values available before running the installer:

Oracle database server host name and port OpenPages database instance name and service ID (SID) TNS alias name

The IBM OpenPages GRC Platform Installer requires the following information. You should have the appropriate values available before running the installer:

Host name of the system where CommandCenter will be installed and the port number that will be used(

Location to install the WebLogic Server, if purchased from IBM

Have the current passwords for the following accounts:

Oracle DB system account Oracle DB SYS account

Obtain passwords for the following accounts, which will be created during the install:

OpenPages admin server OpenPages workflow database OpenPages Super Administrator



Additional AIX-Only PrerequisitesThe information in this topic applies only to AIX environments.

If you are installing onto an AIX server, make sure your system and environment meet these additional required prerequisites.




Set File Size of the /tmp Directory






Steps:





Example




Create the Installation Directory


Run the following command as the root user to create and change the ownership of the folder where the WebSphere Application Server is to be installed, such as /opt/OEI/Oracle.

Steps

1. Log onto the database server as root.2. Open an AIX shell. 3. If the WebSphere Application Server installation directory does not exist, enter the

following command to create the directory:

mkdir -p <SOFTWARE_INSTALLATION_DIRVE>

4. Enter the following command to change ownership of the directory:

chown -R opuser:oinstall <Location of SOFTWARE_INSTALL_DRIVE>

Example

mkdir -p /opt/OEI/Oracle chown –R opuser:oinstall /opt/OEI/Oracle

Disable WebSphere Application Server Global Security


If you configured WebSphere Application Server global administration security in the IBM WebSphere Integrated Solutions Console, you must temporarily disable global security on both the OpenPages application and workflow servers before installing the OpenPages application.

Use the following steps to disable WebSphere Application Server global administration security:

Steps:

1. Open a browser window.2. Disable WAS global security for the OpenPages application:

a. Open a Web browser and point to the following address:

http://<server_name>:<port>/ibm/console

Where: <server_name> is the name of the OpenPages admin server and <port> is the OpenPages admin port, by default 9060.

b. Log on to the IBM WebSphere Integrated Solutions Console as a server administrator with the proper permissions.

c. Expand Security in the left pane and click Global security.d. In the Global security pane, under Administrative security, clear the Enable

administrative security option:e. When finished, click Apply.

3. Disable WAS global security for the workflow admin server.a. Open a Web browser and point to the following address:

http://<server_name>:9061/ibm/console

Where: <server_name> is the name of the WebSphere Application Server <port> is the default WebSphere Application Server admin port. By default, 9061.

b. Expand Security in the left pane and click Global security.c. In the Global security pane, under Administrative security, clear the Enable

administrative security option:d. When finished, click Apply.



Remove Installer Files

This task is required If the WebSphere Application Server installation was performed by a root user.

If the WebSphere Application Server installation was performed by a root user, you need to manually remove some installer files and directories before installing OpenPages as a non-root user.

Steps:

1. Log on the application server where WebSphere Application Server was installed as root 2. Navigate to the home directory of the user that installed WebSphere Application Server.3. Remove the following files and directories, if present:

• .com.registry • .InstallAnywhere • InstallShield • .InstallShield

4. Navigate to the /usr/lib/objrepos directory.5. Rename the vpd.properties file.



• • • • • • • • • •Installing the 64-bit Oracle Client

Depending on your environment, you may have to install the Oracle Client software on multiple application server machines to connect to Oracle database. Oracle Client provides drivers, networking components, and tools that enable you to remotely administer the database.

The Oracle Client can be installed in either of two modes, interactive mode or silent mode.

• Interactive Mode. Interactive mode uses graphic screens to collect the information required for installing the various components. See “Installing the 64-bit OpenPages Client in Interactive Mode” on page 74.

• Silent Mode. In silent mode, you enter required information in a parameter (or response) file. You use command line prompts to initiate the installation, which take the required information from the parameter file. See “Installing the 64-bit Oracle Client in Silent Mode” on page 77.

The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installer will fail. You will need to refer to log files to determine the exact cause of the failure.

Installing the 64-bit OpenPages Client in Interactive ModeThe following steps describe how to run the IBM OpenPages GRC Platform Installer for Repository, openpages_oei.exe, to install the Oracle Client using the graphic installer screens.

Notes

• If you are running the interactive mode installer on an AIX server, you must run the installer in graphical mode using an application such as X Windows or VNC.

• The interactive installer creates the installer.properties file, which you can use to install the Oracle Client on other servers using the silent installation mode, discussed in the following section.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges.



Note: For AIX installs, you must run the installer in graphical mode using an application such as X Windows.





4. Launch the Installer for Repository using the following command:

Windows

openpages_oei.exe

AIX

./openpages_oei.bin -i swing

Where -i swing launches graphic mode

5. On the Welcome screen, click Next.6. On the Installation Information screen:

a. Type the information about the database installation. The following table provides a description of these fields:

7. On the Oracle Software Installation Location screen: a. Enter the drive where the client software is to be installed. The following table


b. Click Next.

Field Description

Installation Information

Select Client to install the Oracle Client.


Enter a location where the database server software will be installed. This will be <ORACLE_HOME>.

Windows Enter the drive letter followed by a colon, such as C:


Field Description Default Value

Oracle Client Software Installation Location

Enter the drive where the client software is to be installed.

WindowsEnter the drive letter followed by a colon. By default, this value is C:.

AIXEnter the installation folder you created earlier.



8. On the Database Instance Information screen:a. Enter the information to set up the connection to the database. The following table


b. Click Next.9. On the Summary screen:

a. Review your selections. Click Previous to return to an earlier screen to make any required changes.

b. When satisfied, click Install to begin the upgrade process.10. Click Done to exit the installer when it finishes. 11. Repeat these steps for each server that requires the Oracle Client software.


Database Host Name

Enter the fully qualified network identifier for the Oracle server machine. The host name can be found in the tnsnames.ora file.

Database Instance Name

Enter the Service ID (SID) of the OpenPages database instance. By default, this value is OP.

Database Instance Port Number

Enter the port number for the database instance that was installed on the database server. By default, this port is 1522.



Installing the 64-bit Oracle Client in Silent ModeThis section provides instructions for using the set of batch scripts to install the Oracle Client in silent mode.

Silent installation of the Oracle Client is accomplished by supplying the installer with values from a parameter file (or response file) instead of providing answers through graphical interface screens. When running the command from a command line, the -silent flag launches the installer in silent mode and installs the Oracle Client with no graphic output.

IMPORTANT! The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installer will fail. You will need to refer to log files to determine the exact cause of the failure.

Task 1: Edit the Properties FileThe following steps describe how to edit the parameter file to include the information required by the installer.

Steps:






4. Edit the ClientInstaller.properties:a. Open the ClientInstaller.properties file in a text editor (such as, WordPad in


5. Save and close the ServerInstaller.properties file.


Installation type Enter 1 to install the Oracle Client:• INSTALL_ORACLE_CLIENT=1

Oracle Software Installation Drive The Windows drive or AIX directory where the Oracle client software will be installed. For example:

Windows SERVER_SOFTWARE_INSTALL_DRIVE=C:

AIX SERVER_SOFTWARE_INSTALL_DRIVE=/opt/oracle

Notes: For Windows, the colon is required. For AIX, use the folder you created above.

Database Instance Port The port number used for the OpenPages database instance. For example: DB_INSTANCE_PORT=1529

Database Information The address of the Oracle database and the name of the OpenPages database instance. For example:

DB_HOSTNAME=10.128.28.104DB_INSTANCE_NAME=OP



Task 2: Run the Installer1. Run the batch file:

Windows

openpages_oei.exe -i silent -f clientinstaller.properties

AIX

openpages_oei.bin -i silent -f clientinstall.properties

Where:

-i silent launches silent mode

-f clientinstall.properties specifies the properties file to use

2. If the installation fails, the following message is displayed:Install failed. Exit Code [<error code>]

Troubleshoot the failed installation as follows:

a. Open the install log file:

Windows

c:\openpages_data\repository\ia\client112_ac_x64\ OpenPages_OEI_Install_Install_Debug.log

AIX

/opt/openpages_data/repository/ia/client112_ac_x64/OpenPages_OEI_Install_Install_Debug.log


representative.

Note: In some rare cases, the installation may hang on the database creation step. If this occurs, it is usually the result of conflicting or incompatible JRE/JDK versions being installed on the same system.



Installing the OpenPages Application

• • • • • • • • • •and Workflow Server

The tasks in this section provide instructions for installing the new OpenPages application, workflow server, and WebLogic Server (if purchased from IBM) onto a admin server and/or managed server using the IBM OpenPages GRC Platform Installer.

Some of these tasks are specific to a admin server or managed server installation, which will be noted in the text.

Use the following table to determine the type of application server installation you should perform.

Notes

If you quit the installation procedure before the installer finishes, you may have temporary files located in the temporary folder. Remove these temporary files manually.

See “Re-enabling Global Security – AIX only” on page 92.

Table 5-2: Installing Cluster Administrator and Cluster Member Servers

Perform this type of installation... If the server is...

Admin Server installation • Intended to be used as the administrative server for the OpenPages environment.

Notes In a clustered environment, there is only one admin server

and all other application servers are managed servers. If you are using LDAP authentication, you must include LDAP

connection information in a properly configured tnsnames.ora file on the application server so OpenPages can connect to the database.

Managed Server installation An additional server in a cluster environment, not intended for administration.

Note: You must install the OpenPages application on the admin server before you can install the managed servers in your configuration.

Have the following information about your admin server server:• Server host name• Server admin user name and password• Server admin SSL and non-SSL port numbers



Setting the Environment VariablesThis task applies to both the admin server and managed server installations.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges and full access to the local server drives.

Note: For AIX installs, log in as a non-root user, such as the user you created for the OpenPages installation, for example: opuser.

2. Set the following environment variables.

Windows

a. Set the ORACLE_HOME environment variable on the application server to point to the Oracle Client home as follows:

set ORACLE_HOME=C:\openpages_data\repository\client112_ac_x64 \software

Note: If the OpenPages application server and database server are on the same machine enter the path to the Oracle Server home, by default:

C:\openpages_data\repository\server112_se_x64\software

b. Add the path to ORACLE_HOME to the PATH environment variable, by default:

C:\openpages_data\repository\client112_se_x64\software\bin

AIX

a. Set the ORACLE_HOME environment variable on the application server to point to the Oracle Client home as follows:

export ORACLE_HOME=/opt/oracle/openpages_data/repository/client112_ac_x64/software

Note: If the OpenPages application server and database server are on the same machine, enter the path to the Oracle Server application, by default:

/opt/oracle/openpages_data/repository/server112_se_x64/software

b. Add the $ORACLE_HOME/bin path to the PATH environment variable. For example:export PATH=$ORACLE_HOME/bin:$PATH

c. Refresh the profile by closing and re-opening the AIX shell or run the following command:cd / . .profile

Running the OpenPages and Workflow Server InstallerUse the following steps to install the OpenPages and Workflow application server software using the IBM OpenPages GRC Platform Installer. Perform each task on each OpenPages application server, whether an admin server or a managed server, unless otherwise specified.

Task 1: Run the InstallerSteps:


Note: For AIX installs, log in as a non-root user, such as the user you created for the reporting server installation, for example: opuser.

2. Launch a Command Prompt window (using the Run as Administrator option) or launch an AIX shell as a non-root user with administrative privileges.



3. Navigate to the following location within the installer kit files you copied from the Installer Disc 1 DVD:

OP_6.0.1_Embedded_Installer\Disk1\InstData\VM or OP_6.0.1_Non_Embedded_Installer\Disk1\InstData\VM

Note: To launch the installer in AIX, you must use a graphical application such as X Windows or VNC as a non-root user with administrative privileges.

4. Run the OpenPages application installer.

Windows

To launch the installer, type opinstall.exe and press Return.

AIX

Type ./opinstall.bin and press Return.

5. On the Welcome screen, click Next. 6. On the Installation Information screen:

a. Click New Installation.b. Specify the installation folder where all OpenPages software components will be

installed, by default:

Windows

C:\OpenPages

AIX

/opt/OpenPages

c. Click Next. d. Click Yes to create the folder, if it does not exist.

Task 2: Define Application Server InformationSteps:

1. On the Application Server Information screen:a. Specify the location information where the WebLogic Server or WebSphere

Application Server was installed manaully or will be installed, as appropriate.

If you are installing WebLogic Server purchased from IBM, enter the location where the WebLogic software will be installed and the location of the JDK 1.6 files.

The following table provides descriptions and default values for this screen.


Middleware Home Folder

AIXField not displayed or required.

Enter the path name where you installed the WebLogic Server manually. or where the WebLogic Server will be installed by the IBM OpenPages GRC Platform Installer.

C:\oracle\middleware

WindowsWebLogic Server Folder

AIXWebSphere Server Folder

Enter the path name for WebLogic Server or WebSphere Application Server application server.

Note: This field does not appear for the OpenPages with WebLogic embedded installer.

ExamplesWindowsC:\oracle\middleware\wlserver_10.3

AIX/opt/IBM/WebSphere/AppServer



b. At the Will this machine administer the cluster? prompt:

c. In the How many cluster members do you want to configure on this machine field, specify the number of OpenPages managed servers that will be installed on this server (at least one). The specified number of managed servers will be installed in addition to an admin server (if you selected Yes above).

d. Click Next.e. Go to the following screen:

Windows Define OpenPages Admin Server Information — Windows only

AIX Define OpenPages Workflow Server Information and E-mail Notifications

Task 3: Define OpenPages Admin Server Information — Windows onlyNote: This screen appears only for Windows installations.

Steps:

1. On the OpenPages Administration Server Information screen:

a. Enter connection, user, and password information for the OpenPages admin server. The following table provides descriptions and default values for this screen.

Java Home Folder

Note: This field does not appear for the OpenPages with WebLogic embedded installer.

Enter the location where the Java (JDK 1.6) was installed.

WindowsC:\Java

AIX/opt/IBM/WebSphere/AppServer/java

Select If the current installation is for...

Yes The admin serverNote: Your installation can have only one admin server and it must reside only on the cluster administrator server. Therefore, do not click Yes if this installation is for a cluster member server.

No A managed serverNote: Your installation can have multiple managed servers on both cluster administrator and cluster member servers.


Admin Server Host Name

Note: This field does not display if you are configuring an admin server.

Enter the name of the OpenPages admin server.

Admin Port Number Enter the port number used internally to access the OpenPages admin server.

7001

Admin SSL Port Number

Enter the port number used internally to access the OpenPages admin server through a secure SSL connection.

7002




b. Click Next.

Task 4: Define OpenPages Workflow Server Information and E-mail NotificationsNote: This screen appears for all installations.

Steps:

1. On the OpenPages Workflow Server Information screen:a. Verify existing or enter new path, port, and address information for the OpenPages

workflow server. The following table provides descriptions and default values for this screen.

Admin Server User Name

Enter the OpenPages admin server user name.

Note: If you are installing a cluster member, ensure that the Weblogic user name and password are the same as used on the cluster admin. If you enter a different password, the installation will fail.

Windowsweblogic

Admin Server Password

Enter the OpenPages admin server password.

Note: This password must consist of at least 8 alphanumeric characters, starting with a letter and containing at least one number.Exampleweblogic1


Enter the installation folder for the Workflow server

Enter the path name for OpenPages workflow server

WindowsC:\Fujitsu\InterstageBPM

AIX /opt/Fujitsu/InterstageBPM

Admin Port Number

AIX Field not displayed or required.

Enter the OpenPages workflow server admin port number.

Windows49901

AIX9061

SSL Port Number

AIX Field not displayed or required.

Enter workflow server Secure Sockets Layer (SSL) port number.

Windows49902

AIX9044

Multicast Address Enter the OpenPages workflow server multicast IP address. Do not use 224.0.0.0.

IMPORTANT! The multicast IP address

must be unique within the network address space.

When installing on a secondary server in a horizontal environment, use the same multicast IP address on all servers.




b. Type the information to access the mail server for workflow notifications and the OpenPages OPBackup utility, as described in the following table.

c. Click Next.d. Click Yes to create the folder, if it does not exist.

Task 5: Choose Whether To Install the OpenPages Database Schema

This task applies to the cluster administrator server installations only.

Steps:

1. On the OpenPages Database Schema screen:a. Choose whether you want the installer to configure the OpenPages Database

Schema and user accounts.

IMPORTANT! If you select No, you must have already installed the OpenPages Database Schema using the SQL wrapper scripts contained in your OpenPages installation kit. If you have not completed the database configuration, you will not be able to complete the current installation.

b. Click Next.2. Go to “ Define OpenPages Database Connection Information” on page 1.


Mail Server Enter the mail server to use for OpenPages workflow notifications.

yourserver.yourdomain.com

E-mail User Name

Enter display name of the E-mail Sender Address. Enter a name with no spaces.

sysadmin

From Address Enter the reply-to e-mail address used for sending messages from the workflow notification service.

[email protected]

Option Description

Yes Install the OpenPages Database Schema and users as part of the OpenPages application installation.

No Does not install the OpenPages Database Schema.

You have already manually installed the OpenPages Database Schema.



Task 6: Define OpenPages Database Connection InformationSteps:

1. On the Database Connection Information screen, type the information to access the OpenPages database instance that was already created. The following table provides descriptions and default values for this screen.


Enter the path to the Oracle Home Folder on this Machine

Note: This field displays only if you are installing the OpenPages Database Schema.

Enter the Oracle database home directory on the local server. This is <ORACLE_HOME>

Examples

Windows

C:\openpages_data\repository\ client112_ac_x64\software

AIX/opt/oracle/openpages_data/ repository/client112_ac_x64/ software

Note: If your database and application servers are on the same machine, this is the Oracle server directory for the current machine (server112_se_x64).

This value is taken from the environment variable you set on the system.

Database Host Name Enter the name of the Oracle database server machine.

Port Number Enter the port number of the Oracle database server machine.

This is the database instance port number, and must be the same number you entered during the Oracle software installation.

Note: The number can be located in the tnsnames file, located at: <ORACLE_HOME>/software/NETWORK/ADMIN directory.

Database Identifier Select the method for identifying the OpenPages database instance, either SID or Service Name and enter the SID or Service Name in the field.

Use the same name as used during OpenPages repository installation.

For Oracle RAC installations, always use the Service Name.

Note: The name can be located in the tnsnames file, located at: <ORACLE_HOME>/software/NETWORK/ADMIN directory.

TNS Alias Name Enter the TNS (Transparent Network Substrate) alias name. The TNS alias is the name by which an Oracle database instance is known on a network.

Use the same name as used during OpenPages repository installation.



2. Click Next.3. Click Yes to create the folder, if it does not exist.

Note: The installer uses a JDBC driver to connect to the database instance using the SID or service name specified in the current screen (Database User Information). Also, the installer uses the Oracle Client to verify the TNS alias name. If the installer cannot connect to the database, an error message appears, listing the error. Return to the Database Connection Information screen to correct the problem.

Task 7: Define OpenPages Database User InformationIf you are installing the OpenPages Database Schema, perform steps a and b. If you are not installing the schema, skip to step b.

Steps:

1. On the Database User Information screen:

IThe installer attempts to access the specific database instance using the information specified during the install. If the installer cannot access the specified instance, an error message appears. Return to the Database User Information screen and/or Database Connection Information screen to correct the problem.

Task 8: Select a Currency


Select the base currency used as the basis for an exchange rate conversion. If you have other environments, such as a test environment, development environment, or user acceptance testing environment, you should set the currency to the same value in each environment.

Note: This screen appears only if you chose to configure the OpenPages Database Schema.

Steps:

1. On the Base Currency Code screen: a. Choose the base currency you want to use in the OpenPages application.

IMPORTANT! You cannot change the base currency after installation.

b. Click Next.

Enter the Oracle Datafile Folder on the Database Server

Note: This field displays only if you are installing the OpenPages Database Schema.

Enter the Oracle data Home directory on database server. This is the location where Oracle data will be stored.

Examples

WindowsC:\openpages_data\repository\ database112_se_x64\oradata\<SID>

AIXopt/openpages_data/repository\database112_se_x64/oradata/<SID>


Base Currency Code Base currency is the currency used as the basis for an exchange rate conversion.




Task 9: Define OpenPages Storage and Configuration InformationSteps:

1. In the Storage and Configuration screen:a. Type the location where attached files and forms associated with OpenPages

objects are stored as well as the backup/restore directory for OpenPages database and application settings. You can also use this screen to provide user access in OpenPages to standard CommandCenter reports. Note that, for new managed server installations, only the backup/restore directory information is required. The following table provides descriptions and default values for this screen.

Note: In a load-balanced environment, the OpenPages Storage Location direction must be in the same location on the Admin server and on each managed server.

b. Click Next.c. Click OK to create the folder(s), if it does not exist.


OpenPages Storage Location

Note: Field not displayed or required for a new managed server installation.

Enter the directory where attached files and forms associated with OpenPages objects are stored.

You can also specify a valid UNC path to the shared storage directory.

Windows example: \\your-server-name\openpages_storage

AIX example: //your-server-name/openpages_storage

Windows

C:\OpenPages\ openpages-storage

AIX

/opt/OpenPages/ openpages-storage

OpenPages Backup/Restore Location

Enter the directory where the Backup/Restore utility places the files it creates when backing up and restoring the OpenPages database and application settings.

Windows

C:\OpenPages\ openpages-backup-restore

AIX

/opt/OpenPages/ openpages-backup-restore

Do you want to load OpenPages Configuration Data

Note: Field not displayed or required for a new managed server installation.

Select Yes to enable user access to standard CommandCenter reports.

IMPORTANT! Selecting No will cause OpenPages to not work as expected. The No option is for internal OpenPages use only.

Yes



Task 10: Define OpenPages User Information


Steps:

1. On the OpenPages Administrator Information screen:

a. Enter the user name to create for the OpenPages application Super Administrator.

Note: If you created the OpenPages Database Schema manually using the SQL wrapper scripts, enter the Super Administrator password that you defined previously. The table provides descriptions and default values for this screen.

b. Click Next.

Task 11: Define CommandCenter InformationSteps:

1. On the CommandCenter Information screen:a. Type the following information that you will use when installing CommandCenter.

The table provides descriptions and default values for this screen. These values can be modified in the aurora.properties file after the installation.

Note: The installer does not verify the information entered, so CommandCenter does not need to be installed at this time.

b. Click Next.


Administrator User Name Enter the user name for the OpenPages application Super Administrator.

OpenPagesAdministrator

Administrator Password Enter the password for the Super Administrator user account defined above.


Host Name Enter the machine name of the CommandCenter server.

Port Number Enter the port number used by OpenPages to communicate with CommandCenter.

80

URL Context Root Enter the context root where CommandCenter is deployed.

cognos8

Framework Generator Port Number

Enter the port number used by OpenPages to connect to the Framework Generator

8080



Task 12: Begin InstallationSteps:

1. On the Confirm Installation Data screen:a. Review your selections.b. When you are satisfied, click Install to begin the installation of both the OpenPages

application software and the workflow server; otherwise, use Previous to go back and change information.

The installation takes approximately 30 - 45 minutes in a Windows environment or 90 minutes in an AIX environment.

2. On the Install Complete screen, click Done to finish the installation.3. If you installed a managed server (you selected No to the Will this machine

administer the cluster? prompt)in a Windows enviroment, proceed to the following task.

After the OpenPages application is complete, install the Cognos tools using the instructions in Chapter 6 “Installing Cognos and Content Store” on page 89.

Then, follow the instructions in “Performing Post-installation Tasks” on page 131.

Note: If you do not see the message “OpenPages 6.0 has been successfully installed” on the Install Complete screen, contact OpenPages representative.

IMPORTANT! Do not reboot the server machine before you complete the post-installation.

Task 13: Create a boot.properties file for WebLogic Server -- Windows only

The information in this topic applies only to Windows environments.

If you installed an OpenPages instance on a cluster member server (you selected No at the Will this machine administer the cluster? prompt) in a Windows enviroment, you must manaully start the OpenPages and workflow services using the command prompt the first time, rather than using the Windows Services tool.

Note: If you are installing OpenPages on the Admin server, you can skip this step.

Using the command prompt to start these services will automatically create a boot.properties file, which allows the service to start without requiring a user name and password to be entered. After starting manually the first time, you can use Windows Services or the command prompt to start the OpenPages and workflow services, as needed.

For each OpenPages and workflow instance that is:

a managed server on a cluster member server (not on the Admin server) in a Windows environment

use the following steps to create the boot.properties file for that instance:

Steps:

1. Log on to the 6.0.1 managed server as a user with Administrator privileges.2. Launch a Command Prompt window (using the Run as Administrator option).3. Start the OpenPages service(s) using the command line:

a. Navigate to the following directory:

<OP_Home>\OpenPagesDomain\bin

Where <OP_Home> represents the installation location of the OpenPages application. By default: C:\OpenPages



b. Run the following command for each OpenPages instance on this system:

startOPServer.cmd <host-name>-OpenPagesServer<#>

Where: <host-name> is the name of the server. <#> is the number of the managed server.

Example startOPServer.cmd managedserver01-OpenPagesServer1 startOPServer.cmd managedserver01-OpenPagesServer2

Note: If you do not know the name of the OpenPages instance(s) on this system, navigate to the following directory:

<OP_Home>\OpenPagesDomain\servers

Each instance on the curent system will have its own directory.

c. At the prompt, enter the WebLogic Server administrator user name and password.d. When the command is complete, you can check that the boot.properties file has

been created in the <OP_Home>\OpenPagesDomain\ directory. The user name and password will be present in the file and encrypted.

4. Start the workflow service using the command line:a. Navigate to the following directory:

<Workflow_Home>\IBPMDomain\bin

Where <Workflow_Home> is the directory where Fujitsu Interstage BPM is installed, by default /opt/Fujitsu/InterstageBPM

b. Run the following command for each workflow instance on this system:

startIBPMServer.cmd <host-name>-InterstageBPMCS<#>

Where: <host-name> is the name of the server. <#> is the number of the managed server.

Example startIBPMServer.cmd managedserver01-InterstageBPMCS1 startIBPMServer.cmd managedserver01-InterstageBPMCS2

Note: If you do not know the name of the workflow instance(s) on this system, navigate to the following directory:

<Workflow_Home>\IBPMDomain\servers

Each instance on the curent system will have its own directory.

c. At the prompt, enter the Oracle WebLogic administrator user name and password.d. When the command is complete, you can check that the boot.properties file has

been created in the <Workflow_Home>\IBPMDomain\ directory. The user name and password will be present in the file and encrypted.



• • • • • • • • • •Re-enabling Global Security – AIX only


If you disabled WebSphere Application Server global administration security in the IBM WebSphere Integrated Solutions Console, you can re-enable it on both the OpenPages application and workflow servers after installing the OpenPages application.

Enabling Global SecurityUse the following steps to enable WebSphere Application Server global administration security:

Steps:

1. Open a browser window.2. Enable WAS global security for the OpenPages application:

a. Open a Web browser and point to the following address:


Where: <server_name> is the name of the OpenPages admin server and <port> is the OpenPages admin port, by default 9060.

b. Log on to the IBM WebSphere Integrated Solutions Console as a server administrator with the proper permissions, by default:

c. Expand Security in the left pane and click Global security.d. In the Global security pane, under Administrative security, select the Enable

administrative security option:e. When finished, click Apply.

3. Enable WAS global security for the OpenPages admin server.a. Open a Web browser and point to the following address:


Where: <server_name> is the name of the WebSphere Application Server <port> is the default WebSphere Application Server admin port. By default, 9061.

b. Expand Security in the left pane and click Global security.c. In the Global security pane, under Administrative security, select the Enable

administrative security option:d. When finished, click Apply.

4. Restart all OpenPages servers.



• • • • • • • • • •Reinstalling After Incomplete Install


If the OpenPages installer does not complete, there may be files and directories remaining that will prevent the installer from running again. If the uninstall utility is not present in the <OP_Home>\OpenPagesUninstall directory, you must manually remove these files.

You must also remove references to OpenPages and the workflow server (IBPM) from the profileRegistry.xml file, which is a list of WebSphere profiles and profile configuration data.

The file should contain be two listings for the deployment manager: OpenPagesDmgr and IBPMDmgr, and a listing for each node, for example: <server_name>-OPNode1, <server_name>-IBPMNode1, <server_name>-OPNode2, <server_name>-IBPMNode2.

Use the following steps to remove remaining files after an unfinished OpenPages installer.

Steps:

1. Log on to the 6.0.1 application server as a non-root user with administrative privileges and full access to the local server drives.

2. Launch an AIX shell.3. Remove the <OP_Home> directory.

a. Navigate to the <OP_Home> directory.b. Recursively remove the directory.

4. Uninstall the workflow server. a. Navigate to the <Workflow_Home>/_uninst/ directory.

Where <Workflow_Home> is the directory where Fujitsu Interstage BPM is installed, by default /opt/Fujitsu/InterstageBPM.

b. Execute the uninstall.sh command.5. Remove any entries for OpenPages and IBPM (workflow server) in the

profileRegistry.xml file.a. Navigate to the <WAS_Home>/properties directory.

Where <WAS_Home> is the directory where WebSphere is installed, by default /opt/IBM/WebSphere/AppServer/.

b. Open the profileRegistry.xml file in a text editor.c. Remove any lines that contain references to OpenPages or IBPM, for example:

<profile isDefault="false" isDefault="true" name="OpenPagesDmgr" path="/usr/OpenPages/profiles/OpenPagesDmgr" template="/usr/IBM/WebSphere/AppServer/profileTemplates/management"><augmentor template="/usr/IBM/WebSphere/AppServer/profileTemplates/dmgr"/>

<profile isDefault="false" isDefault="false" name="op-aix61-02.swg.usma.ibm.com-IBPMNode1" path="/usr/Fujitsu/InterstageBPM/profiles/op-aix61-02.swg.usma.ibm.com-IBPMNode1" template="/usr/IBM/WebSphere/AppServer/profileTemplates/managed"/>

d. Save and close the file.6. Log off the root user from the 6.0.1 application server.

Once these files are removed and the profileRegistry.xml file is returned to its prior state, you can attempt to reinstall the OpenPages applicaiton.

For information on removing the workflow server, see “Uninstalling the Workflow Server” in Chapter 10 on page 177.



6
Installing Cognos and Content Store
This chapter explains how to install the Cognos applications that CommandCenter will leverage and how to create the CommandCenter database schema and users.


About the Cognos Installation on page 96 Checklist for Installing Cognos and the Content Store on page 97 Before You Begin on page 98 Installing the 32-Bit Oracle Client on page 101 Installing Cognos and the CommandCenter Database Schema on page 105 Configuring Your Web Server on page 110 Configuring Cognos 8 Go! Dashboard on page 116 Set Database Connection Properties for CommandCenter on page 119 Testing the Cognos Installation on page 122


• • • • • • • • • •About the Cognos Installation

The Cognos applications are installed on the same server where CommandCenter will be installed, called the reporting server.

For light loads, with fewer than 50 concurrent users, Cognos and CommandCenter may be installed on the same server as the OpenPages application.

If you plan to allow more users, Cognos and CommandCenter should be installed on a separate server or multiple servers. The IBM OpenPages GRC Platform operates at peak performance when installed on multiple servers (a database server, an application server, and a reporting server),

This section contains information about the IBM OpenPages GRC Platform Installer for Cognos, which installs the following software on a Windows or AIX platform:

IBM Cognos 8 Business Intelligence (version 8.4.1)• Cognos 8 SDK• Cognos 8 BI Fixpack 2 and Cognos 8 SDK Fixpack 1• Cognos 8 BI Server Component Updater 8.4.104.13

IBM Cognos 8 Go! Dashboard IBM Cognos 8 Go! Mobile

This chapter also describes how to configure the Web server on the reporting server.

Chapter 6: Installing Cognos and Content Store


Checklist for Installing Cognos and the

• • • • • • • • • •Content Store

Use the following checklist to guide you through installing the Cognos application, creating the CommandCenter database schema, and configuring the web server for CommandCenter. Each task below has several steps.

Table 6-1: Checklist for Installing CommandCenter

Task Checklist


2. Install Oracle Client. See “Installing the 32-Bit Oracle Client” on page 101.

3. Install the Cognos 8 BI software, optionally create the CommandCenter database schema, and optionally configure the Apache Web Server using the OpenPages Cognos Installer. See “Installing Cognos and the CommandCenter Database Schema” on page 105.

4. Optionally, you may manually create the database instance. See Appendix G, “Creating the CommandCenter Database Schema” on page 301.

5. Configure your Web server:• See “Configuring an IIS 7.0 Web Server - Windows only” on page 110. • See “Configuring the Apache Web Server on an AIX System” on page 115.

6. Test the Cognos 8 Configuration. See “Testing the Cognos Installation” on page 122.




Before starting the Cognos application installation process, make sure you perform the following tasks.

PrerequisitesMake sure the server where you are installing the Cognos application meets the prerequisites listed in Chapter 2 “Prerequisites” on page 15.

Install the Web Server


Ensure that a Web server software is already installed on the server:

Windows

For a reporting server on the Windows platform, see either:

Microsoft Internet Information Services (IIS)® 7.0 Apache WebServer™ 2.2

AIX

For a reporting server on the AIX platform, see:

Apache WebServer™ 2.2

Copy the Installation Files


Before starting the Cognos application and Oracle Client install, you should copy the installer kit files from the IBM OpenPages GRC Platform media pack to the local system to improve performance.

Steps:

1. Log on to your database server as a user with administrative privileges.

Note: For AIX installs, log in as a non-root user, such as the user you created for the OpenPages installation, for example: opuser.


3. Copy the OEI_Server_Client_32bit directory from the Repository Installer Disc 2 DVD or network share location to the local system.

4. Copy the Cognos and CommandCenter installer directories from the Installer Disc 2 DVD:

OP_6.0.1_CommandCenter


Disable Anti-Virus


If an anti-virus package is running on the 6.0.1 reporting server, for faster installation times, you may disable the anti-virus software before running the OpenPages installation.



Remove Environment Variables


Before running the installer, verify that the JAVA_HOME system environment variable is not defined, as required for the Cognos installation. Also, make sure the Java home path is not present in the PATH environment variable.

If JAVA_HOME is defined, you must remove the variable and/or remove Java from PATH and reboot the system before starting the installation.

Obtain Installation Information


During the Cognos application installation, you will be asked for the following information. You should have this information available before starting.

Determine the following locations, which will be created by the installer:

Oracle client installation folder location Cognos application installation folder location Cognos user name and password Cognos 8 Framework Model output folder location

Obtain the following values, which were previously created:

OpenPages database host name OpenPages database port OpenPages database alias OpenPages database SID or Service Name OpenPages superuser name OpenPages superuser password Java installation folder location

Additional AIX-Only PrerequisitesIf you are installing onto an AIX server, make sure your system and environment meet these additional required prerequisites.







Steps:







Example




Run the following command as the root user to create and change the ownership of the folder where the Cognos application is to be installed, such as /opt/OpenPages/Cognos.

Steps

1. Log onto the reporting server as root.2. Open an AIX shell. 3. If the CommandCenter installation directory does not exist, enter the following

command to create the directory:

mkdir -p <SOFTWARE_DIRVE>


chown -R <user>:<group> <SOFTWARE_DRIVE>

Example

mkdir -p /opt/OpenPages/Cognos chown –R opuser:staff /opt/OpenPages/Cognos






• • • • • • • • • •Installing the 32-Bit Oracle Client

You need to install the 32-bit version of Oracle Client on the server that will host CommandCenter. Oracle Client provides drivers, networking components, and tools that enable CommandCenter to remotely connect to the database.

The Oracle Client can be installed in either of two modes: interactive mode or silent mode.

• Interactive Mode. Interactive mode uses graphic screens to collect the information required for installing the various components. See “Installing the 32-bit OpenPages Client in Interactive Mode” on page 101.

• Silent Mode. In silent mode, you enter required information in a parameter (or response) file. You use command line prompts to start the installer, which takes the required information from the parameter file. See “Installing the 32-bit Oracle Client in Silent Mode” on page 103.

The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installer will fail. You will need to refer to log files to determine the exact cause of the failure.

Installing the 32-bit OpenPages Client in Interactive ModeThe following steps describe how to run the IBM OpenPages GRC Platform Installer for Repository, openpages_oei.exe, to install the 32-bit Oracle Client using the graphic installer screens.

Notes

• If you are running the interactive mode installer on an AIX server, you must run the installer in graphical mode using an application such as X Windows or VNC.

• The interactive installer creates the installer.properties file, which you can use to install the Oracle Client on other servers using the silent installation mode, discussed in the following section.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.



3. Navigate to the following location within the OEI_Server_Client_32bit directory that you copied:

\Disk1\InstData\VM

4. Launch the installer using the following command:

Windows openpages_oei.exe

AIX ./openpages_oei.bin -i swing

Where -i swing launches graphical mode

5. On the Welcome screen, click Next.



6. In the Oracle Software Installation Location screen: a. Enter the drive where the client software is to be installed. The following table


b. Click Next.7. On the Database Instance Information screen:

a. Enter the information to set up the connection to the database. The following table provides a description of these fields.

b. Click Next.8. On the Summary screen:

a. Review your selections. Click Previous to return to an earlier screen to make any required changes.

b. When satisfied, click Install to begin the upgrade process.9. Click Done to exit the installer when it finishes. 10. Repeat these steps for each reporting server where you will be installing the

CommandCenter software.


Oracle Client Software Installation Location

Enter the drive where the client software is to be installed.

WindowsEnter the drive letter followed by a colon. By default, this value is C:.

AIXEnter the folder you created earlier. This folder must exist.


Database Host Name Enter the fully qualified network identifier for the Oracle server machine. The host name can be found in the tnsnames.ora file.

Database Instance Name Enter the Service ID (SID) of the OpenPages database instance. By default, this value is OP. The host name can be found in the tnsnames.ora file.

Database Instance Port Number Enter the port number for the database instance that was installed on the database server. By default, 1522.



Installing the 32-bit Oracle Client in Silent ModeThis section provides instructions for using a set of batch scripts to install the Oracle Client in silent mode.

Silent installation of the Oracle Client is accomplished by supplying the installer with values from a parameter file (or response file) instead of providing answers through graphical interface screens. When running the command from a command line, the -silent flag launches the installer in silent mode and installs the Oracle Client with no graphic output.

IMPORTANT! The silent mode installer does not perform any verification of values entered in the parameter file. If the parameter information you provide in the file is incorrect, incomplete, or contains other problems, the installation will fail. You will need to refer to log files to determine the exact cause of the failure.

Task 1: Edit the Properties FileThe following steps describe how to edit the parameter file to include the information required by the installer.

Steps:

1. Log on to 6.0.1 reporting server as a user with administrative privileges.


Launch a Command Prompt window (using the Run as Administrator option) or AIX shell as the oracle user you created for the OpenPages installation.

2. Navigate to the following location within the OEI_Server_Client_32bit directory that you copied:

\Disk1\InstData\VM

3. Edit the ClientInstaller.properties:a. Open the ClientInstaller.properties file in a text editor (such as WordPad in



Installation type Type 1 to install the Oracle client:• INSTALL_ORACLE_CLIENT=1

Oracle Software Installation Drive The Windows drive or AIX directory where the Oracle client software will be installed. For example:

Windows

SERVER_SOFTWARE_INSTALL_DRIVE=C:

AIX

SERVER_SOFTWARE_INSTALL_DRIVE=/opt/oracle

Notes: For Windows, the colon is required. For AIX, use the folder you created above.

Database Instance Port The port number used for the OpenPages database instance. For example:

DB_INSTANCE_PORT=1522

Database Information The address of the Oracle database and the name of the OpenPages database instance. For example:

DB_HOSTNAME=10.128.28.104

DB_INSTANCE_NAME=OP



Task 2: Run the Installer1. Run the batch file:

Windows

openpages_oei.exe -i silent -f clientinstaller.properties

AIX

openpages_oei.bin -i silent -f clientinstall.properties

If the installation fails, the following message is displayed:

Install failed. Exit Code [<error code>]

2. Troubleshoot the failed installation as follows:a. Open the install log file:

Windows

c:\openpages_data\repository\ia\client112_ac_x64\ OpenPages_OEI_Install_Install_Debug.log

AIX

/opt/openpages_data/repository/ia/client112_ac_x64\ OpenPages_OEI_Install_Install_Debug.log


representative.

Note: In some rare cases, the installation may hang on the database creation step. If this occurs, it is usually the result of conflicting or incompatible JRE/JDK versions being installed on the same system.



Installing Cognos and the

• • • • • • • • • •CommandCenter Database Schema

The IBM OpenPages GRC Platform Installer for Cognos can be used to install and configure the Cognos software used with CommandCenter, configure the Apache HTTP Server for use with CommandCenter, and create a CommandCenter database schema and user (called Content Store) within the OpenPages database instance.

The OpenPages Cognos Installer installs the following Cognos 8 applications:

Business Intelligence Software Development Kit Fix packs for BI and SDK Go! Dashboard Go! Mobile

The installer automatically creates the CommandCenter database schema.

Note: You have the option to to manually create the CommandCenter database schema using scripts included in the installation kit, before running the Installer for Cognos. See Appendix G, “Creating the CommandCenter Database Schema” on page 315.

After the Cognos software is installed and the CommandCenter installation is complete, there are a number of tasks you must perform in order to configure Go! Dashboard. See “Configuring Cognos 8 Go! Dashboard” on page 116.

Installing Cognos and the Content StoreTo install the Cognos software, create the Content Store database schema, and configure the Apache Web Server, follow these steps.

IMPORTANT! Make sure the JAVA_HOME environment variable is not set.

Steps:


Note: For AIX installs, use a non-root user, such as the user you created for the OpenPages installation, opuser.

Task 1: Launch the Installer1. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as a non-root user with administrative privileges.2. Copy the OP_6.0.1_CommandCenter directory from the Installer Disc 1 DVD or

network share location to the local system.


3. Navigate to the following location within the install directory:

OP_6.0.1_CommandCenter\IBM_Cognos\Disk1\InstData\VM



4. Start the IBM OpenPages GRC Platform Installer for Cognos using one of the two following commands, as appropriate:

Windows

CognosSetup.exe

AIX

./CognosSetup.bin

Note: User must have Execute permission to run CognosSetup.bin.


Task 2: Specify Installation Information1. On the Installation Information screen:

a. Enter the information to set up the connection to the database. The following table provides a description of these fields.

b. Click Next.

Task 3: Install the CommandCenter Database Schema1. On the Cognos Database Schema screen:

a. Choose whether you want the installer to configure the CommandCenter Database Schema and user accounts.

IMPORTANT! If you select No, you must have already created the CommandCenter Database Schema and user accounts. If you want to install the schema manually, but have not, quit the installation.,

b. Click Next.


Cognos Installation Folder

Enter the location where the Cognos 8 BI files will be installed.

WindowsC:\OpenPages\Cognos

AIX/opt/OpenPages/Cognos

Oracle 32-bit Client Installation Folder

Enter the location where the Oracle Client has been installed.

WindowsC:\openpages_data\repository client112_ac_x86\software

AIXopt/openpages_data/repository/client112_ac_x86/software

Option Description

Yes Create the Content Store database schema and user accounts for CommandCenter.

No Do not create a separate database schema and users. Select this option only if you have already created the CommandCenter database schema.



Task 4: Specify Database Information1. On the Cognos Database Information screen:

a. Enter the database information that Cognos needs to access the database.

b. Click Next. The installer verifies the database information, ensuring that it can properly connect to the database.

Field Name Description Default Value

Database Host Name Enter the name of the server that will host the CommandCenter database.

Database Port Enter the port that will be used to access the CommandCenter database server.

Alias Name

Note: This field will not appear if you are not installing the CommandCenter Database Schema.

Enter the database name that will be used for the CommandCenter database instance.

Database Identifier Select the method for identifying the CommandCenter database instance, either SID or Service Name and enter the SID or Service Name in the field.

Note: For Oracle RAC installations, always use Service Name.

Database Datafile Location


Enter the Oracle data home directory on the database server. This is the location where Oracle data will be stored.

Examples

WindowsC:\openpages_data\ database112_se_x64\oradata\OP

AIXopt/openpages_data/database112_se_x64\oradata\OP

Cognos User Name Enter a user name to create the Cognos account for the CommandCenter Database Schema.

Note: If you previously created the CommandCenter Database Schema, enter the Cognos user name you created for that instance.

cognos

Cognos Password Enter a password to be used with the Cognos username defined above.

System User Name


Enter the Oracle system account user name.

If you do not have access to the system user account, any database user that has administrative privileges can be entered for the purposes of this installation.

system

System Password


The password for the System Username defined above.



Task 5: Configure the Web Server1. On the Apache Web Server Information screen:

a. If the Apache Web Server is installed on the reporting server, choose whether you want the installer to configure the Apache Web Server for use with CommandCenter.• Note: If you are using Microsoft IIS, select No. You must manually configure

IIS as described in this chapter.

b. Click Next.

Task 6: Install the Cognos Software and CommandCenter Database Schema1. On the Confirm Installation Data screen:

a. Review your selections.b. When you are satisfied, click Install to begin the installation; otherwise, use

Previous to go back and change information.

The installation takes approximately 25 minutes in a Windows environment or 45 minutes in an AIX environment, but may take longer depending upon your environment.

2. On the Install Complete screen, click Done to finish the installation.

Note: The log files for the IBM OpenPages GRC Platform Installer for Cognos are located in the top level of the Cognos Home location in the Log directory. For example:

Windows

c:/cognos/logs

AIX

opt\cognos\logs

Task 7: Restart the Apache Web ServerIf your reporting server is using the Apache Web Server, and you used the IBM OpenPages GRC Platform Installer for Cognos to configure Apache, restart the Apache Web Server. Before you can restart Apache, you need to make sure the headers_module will be loaded.

1. On the 6.0.1 reporting server launch a Command Prompt window (using the Run as Administrator option) or AIX shell as a non-root user with administrative privileges.

2. Make sure that the headers_module will be loaded by uncommenting the line for the headers_module in the httpd.conf file.a. Navigate to the <Apache_Home>\conf\ directory. b. Open the httpd.conf file, in a text editor (such as Notepad or vi).c. Uncomment the following line, by removing the # if present.

LoadModule headers_module modules/mod_headers.so

d. Close and save the file.3. Restart the Apache Web Server.

Option Description

Yes Configure the Apache Web Server for use with CommandCenter.

If you select Yes, enter the path to the Apache installation location in the Apache WebServer Installation Folder field.

No Do not configure the Apache Web Server.

You must manually configure the IIS or Apache Web Server.



Windows

Restart the Apache2.2 service though the Window Services or using the Window Start menu, by default: Start | All Programs | Apache HTTP Server 2.2 | Control Apache Server | Restart

AIX

Use the following commands:

<Apache_Home>/bin/apachectl stop <Apache_Home>/bin/apachectl start

Where <Apache_Home> is the Web server home directory.

Task 8: Perform Post Installation TasksAfter the OpenPages Cognos Installer is finished, perform the following tasks as appropriate:

1. If the reporting server is running on Microsoft IIS, or you did not allow the installer to configure your AIX web server, you must manually configure the web server, see “Configuring an IIS 7.0 Web Server - Windows only” on page 110.

2. Configure the Go! Dashboard application which was installed by the Installer for Cognos for use with CommandCenter. See “Configuring Cognos 8 Go! Dashboard” on page 116.



• • • • • • • • • •Configuring Your Web Server

In order to use the HTML Web pages generated by CommandCenter reports, you must create and configure three virtual directories on all Web servers:To create these directories and configure your web server, follow the steps below, based on your type of web server.

For Web servers running IIS (on Windows only), see “Configuring an IIS 7.0 Web Server - Windows only” on page 110.

For Web servers running Apache (on Windows or AIX), see “Configuring the Apache Web Server on an AIX System” on page 115.

Note: If you used the Installer for Cognos to configure your web server, skip this step and proceed with “Configuring Cognos 8 Go! Dashboard” on page 116.

Configuring an IIS 7.0 Web Server - Windows onlyThe information in this topic applies only to Windows environments.

If your Web server is a Windows Server 2008 with IIS 7.0, you must configure ISAPI and CGI to allow CommandCenter pages to load.

Note: The following instructions are specific to Windows Server 2008 with IIS 7.0. If you are using a different operating system or IIS version, the steps to perform these tasks may be different.

Task 1: Launch IIS 7.0 Security IIS 7.0 on a Windows Server 2008 server has security features that, by default, prohibit files with Web Service extensions (cgi) from executing. As a result, Cognos files with Web Service extensions are unable to run. To modify IIS 7.0 security features so that Cognos files with Web Service extensions can execute properly, you must enable IIS to allow CGI.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges. 2. Launch the Windows Internet Information Services Manager, by clicking the Start

menu, then selecting Administrative Tools | Internet Information Services Manager.

3. In the left pane of the Internet Information Services Manager, select the application server you want to configure.

4. In the Features view, locate the ISAPI and CGI Restrictions icon. If the ISAPI and CGI Restrictions icon does not appear, continue with “Enabling ISAPI and CGI Extensions”. If the icon is present, skip to “Modifying IIS 7.0 Security” below.



Task 2: Enabling ISAPI and CGI ExtensionsThe ISAPI and CGI Restrictions required to configure IIS may does not appear by default. If the icon is not present, you need to create a role in the Windows Server Manager using the following steps.

Steps:

1. On the 6.0.1 reporting server, launch the Windows Server Manager, by clicking the Start menu, then selecting Administrative Tools | Server Manager.

2. On the left side, right-click Roles and select Add Roles.3. In the Add Role Services wizard, click Next on the Before You Begin screen.4. On the Select Server Roles screen:

a. Select WebServer (IIS).b. Click Next.

5. In the Add Server Roles screen:a. Under Application Development, select CGI, ISAPI Extensions, and ISAPI

filters. b. Click Next.

6. On the Confirm Installation Selections screen:a. Click Install.b. When the installation is complete, click Close.

Task 3: Modifying IIS 7.0 Security To enable IIS to allow CGI use the following steps.

Steps:

1. In the Features view of the Internet Information Services Manager, double-click the ISAPI and CGI Restrictions icon.

2. In the Actions pane, select Add.3. In the Add ISAPI or CGI Restriction dialog box, click the browse button (...). 4. In the ISAPI and CGI Restrictions pop-up, do the following:

a. Change the File Type filter from .dll to All Files.b. Enter the path to the cognos.cgi file or use the browse button to locate the file,

which is located in the cgi-bin directory of the Cognos_Home location. c. Enter a description for the restriction, such as Cognos-CGI.d. Select the Allow extension path to execute option.e. Click OK.

Task 4: Setting Up Web Server Virtual DirectoriesTo set up Web server virtual directories, do the following.

Steps:

1. Launch the Windows Internet Information Services Manager, by clicking the Start menu, then selecting Administrative Tools | Internet Services Manager.

2. From the Internet Services Manager, do the following:a. Expand the tree for the server you want to configure, and then expand Default

Web Site.b. Right-click Default Web Site and select Add Virtual Directory from the menu.



3. In the Add Virtual Directory screen, create the cognos8 virtual directory as follows:a. In the Alias field, enter the name cognos8.b. In the Physical Path field, click the Browse button or enter the path to the

webcontent directory under Cognos_Home.

If you used the IBM OpenPages GRC Platform Installer for Cognos, the default path is: c:\OpenPages\Cognos\cognos\c8\webcontent

c. Click OK.4. Right-click the cognos8 virtual directory that you created and select Add Virtual

Directory from the menu. 5. In the Add Virtual Directory screen, create a cgi-bin virtual sub-directory as follows

a. In the Alias field, type the name cgi-bin.b. In the Physical Path field, use the Browse button or type the path to the cgi-bin

directory under Cognos_Home.

If you used the IBM OpenPages GRC Platform Installer for Cognos, the default path is: c:\OpenPages\Cognos\cognos\c8\cgi-bin

c. Click OK.6. Right-click the cognos8 virtual directory that you created in Step 3 and select Add

Virtual Directory from the menu. 7. In the Add Virtual Directory screen, create a help virtual sub-directory as follows:

a. In the Alias field, type the name help.b. In the Physical Path field, use the Browse button or type the path to the

webcontent\documentation directory under Cognos_Home.

If you used the IBM OpenPages GRC Platform Installer for Cognos, the default path is: c:\OpenPages\Cognos\cognos\c8\webcontent\documentation

c. Click OK.8. In the Connections pane,

a. Select the cgi-bin virtual directoryb. Double-click Handler Mappings in the right pane.

9. In the Actions pane click Add Module Mapping, then: a. In the Request Path field, enter *.cgi.b. In the Module list, select CgiModule. c. Enter a name, such as Cognos-CGI. d. Click OK.

10. Close the Windows Internet Information Services Manager.

Task 5: Edit the web.config FileIn order for Cognos Administration to function properly, the module mapping added above needs to be edited manually in the web.config and/or applicationhost.config file

You may have one or both of these files. If you have both the web.config and the applicationHost.config file, this entry must appear in both files.

Steps:

1. Launch a Command Prompt window (using the Run as Administrator option) and navigate to C:\Windows\System32\inetsrv\config\applicationHost.config.

2. If present, open the applicationHost.config file in a text editor. If not present, skip to Step 6.

3. Locate the following entry:

<add name="Cognos-CGI" path= "cognos.cgi" verb="*" modules="CgiModule" resourceType="Unspecified" />



4. Add allowPathInfo="true" to end of the line:

<add name="Cognos-CGI" path= "cognos.cgi" verb="*" modules="CgiModule" resourceType="Unspecified" allowPathInfo="true" />

5. Save and close the text editor.6. Navigate to:

<Cognos_Home>\cgi-bin

7. If present, open the web.config file in a text editor. If not present, you are done.8. Locate the following entry:

<add name="Cognos-CGI" path= "*.cgi" verb="*" modules="CgiModule" resourceType="Unspecified" />

9. Add allowPathInfo='true' to end of the line:

<add name="Cognos-CGI" path= "*.cgi" verb="*" modules="CgiModule" resourceType="Unspecified" allowPathInfo="true" />

10. Save and close the text editor.



Configuring the Apache Web Server If you decided to not allow the IBM OpenPages GRC Platform Installer for Cognos to configure the Apache Web server, use the following steps to manually configure Apache as a gateway to IBM Cognos 8. See:

“Configuring the Apache Web Server on a Windows System” below “Configuring the Apache Web Server on an AIX System” on page 115

Configuring the Apache Web Server on a Windows System


If your reporting server is on the Windows platform, use the following steps to manually configure Apache.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option) and

navigate to the <Apache_Home>\conf\ directory. 3. Make a backup copy of the httpd.conf file and rename the file as:

httpd.conf.original.4. Open the httpd.conf file, in a text editor (such as Notepad). 5. Un-comment and edit following line to point towards the Cognos server, for example:

#ServerName commandcenter.openpages.com:80

6. Add these lines to the end of the httpd.conf file to point to the following directories created during the Cognos install, where Cognos_Home is the path to the Cognos installation directory:

ScriptAlias \cognos8\cgi-bin "<Cognos_Home>\cgi-bin" <Directory "<Cognos_Home>\cgi-bin"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All </Directory>

Alias \cognos8\help "<Cognos_Home>\webcontent\documentation" <Directory "<Cognos_Home>\webcontent\documentation"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All

</Directory> Alias \cognos8 "<Cognos_Home>\webcontent" <Directory "<Cognos_Home>\webcontent"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All </Directory>

7. Restart the Apache2.2 service though the Window Services or using the Window Start menu, by default: Start | All Programs | Apache HTTP Server 2.2 | Control Apache Server | Restart



Configuring the Apache Web Server on an AIX System


If your reporting server is on the AIX platform, use the following steps to manually configure Apache.

Steps:

1. Log on to the 6.0.1 reporting server as a non-root user with administrative privileges.2. Navigate to the /opt/pware/conf directory.3. Make a backup copy of the httpd.conf file and rename the file as:

httpd.conf.original.4. Open the httpd.conf file, in a text editor (such as VI or Emacs). 5. Un-comment and edit following line to point towards the Cognos server, for example:

#ServerName commandcenter.openpages.com:80:80

6. Add these lines to the end of the httpd.conf file to point to the following directories created during the Cognos install, where <Cognos_Home> is the path to the Cognos installation directory:

ScriptAlias /cognos8/cgi-bin "<Cognos_Home>/cgi-bin" <Directory "<Cognos_Home>/cgi-bin"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All </Directory>

Alias /cognos8/help "<Cognos_Home>/webcontent/documentation" <Directory "<Cognos_Home>/webcontent/documentation"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All </Directory>

Alias /cognos8 "<Cognos_Home>/webcontent" <Directory "<Cognos_Home>/webcontent"> Options FollowSymLinks AllowOverride FileInfo Order Allow,Deny Allow from All </Directory>

7. Use the following commands to restart the Apache Web Server:

<Apache_Home>/bin/apachectl stop

<Apache_Home>/bin/apachectl start

Where <Apache_Home> is the Web server home directory.



• • • • • • • • • •Configuring Cognos 8 Go! Dashboard


You must perform the following tasks to configure the IBM Cognos 8 Go! Dashboard application for use with CommandCenter:

“Configuring the Cognos 8 Dashboard Application” below “Specifying the Gateway URI for Go! Dashboard” “Configure Access to Dashboard” “Starting the IBM Cognos 8 Go! Dashboard Service”

Configuring the Cognos 8 Dashboard ApplicationUse the following tasks to configure Cognos 8 Dashboard for use with OpenPages.

Task 1: Starting the Cognos ServiceAfter running the IBM OpenPages GRC Platform Installer for Cognos, you must manually start the Cognos service.

Use the following steps to start the Cognos service.

Steps:


Note: For AIX installs, you log in as a non-root user.

2. Start IBM Cognos Configuration: a. Launch a Command Prompt window (using the Run as Administrator option) or

AIX shell.b. Navigate to the following directory:

<COGNOS_HOME>/bin64

c. Execute the following command:

Windows

cogconfig.bat

AIX

./cogconfig.sh

3. If this is the first time that Cognos Configuration will started, click the Save icon (or from the File menu, click Save) to ensure that the Cognos password is properly encrypted before starting.

4. Start the IBM Cognos 8 service by clicking Actions | Start. (It may take several minutes for the service to start the first time.) If the Start option is not available, the service has already started.

Note: IBM Cognos Configuration may pause while starting the Cognos service if you have not configured a mail server. Click OK in the dialog box that displays, then click Continue.



Task 2: Specifying the Gateway URI for Go! DashboardA gateway URI must be specified to enable communication for Cognos 8 service requests sent by a Web server gateway and Go! Dashboard.

Steps:

1. On to the 6.0.1 reporting server, open a Web browser and point the browser to the following address (It may take a few minutes for the Web page to open):

http://<server_name>/cognos8

Where: <server_name> is the name of the Web server machine that contains the Cognos virtual directory and cognos8 is the name of that virtual directory.

2. Launch IBM Cognos Administration:• If the CommandCenter splash page appears, click the Administer IBM

Cognos Content link.• If the IBM Cognos Connection page appears, click Launch then select IBM

Cognos Administration.3. On the Configuration tab, click Dispatchers and Services.4. Click the Set properties - Configuration icon at the top right of the page.5. On the Settings tab, click the Edit link next to Advanced Settings.6. In the Parameter column, enter the parameter name:

WEB.GATEWAY_URI

7. In the Value column, enter the gateway address for IBM Cognos 8 Go! Dashboard in the following format:

http://{Gateway_URI}/gdb/cognos/dashboard/html

Where:

{Gateway_URI} is the value specified for the Gateway URI in IBM Cognos Configuration (Local Configuration | Environment) for the reporting server. The value is case sensitive and must not mix host names with IP addresses.

For example:

http://ReportServer:80/cognos8/cgi-bin/cognos.cgi/gdb/cognos/dashboard/html

8. Click OK.9. On the Set properties page, click OK.10. Wait a minute for the changes to be applied.

The changes are automatically applied; you do not have to restart the dispatcher in IBM Cognos Administration.



Task 3: Configure Access to DashboardAfter configuring the dispatcher and gateway URI, modify user access permission to Dashboard.

1. On to the 6.0.1 reporting server, open a Web browser and point the browser to the following address:


Where: <server_name> is the name of the Web server machine that contains the Cognos virtual directory and cognos8 is the name of that virtual directory.



Cognos Administration.3. On the Security tab, click Capabilities.4. Locate IBM Cognos 8 Go! Dashboard in the list and select Set Properties from the

Actions menu. 5. On the Permissions tab, select Override the access permission acquired from

the parent entry.6. In the list of groups, select Everyone. 7. Under Grant, select Read, Write, Execute, and Traverse to give these permissions. 8. Click OK to exit the Set Properties screen.

Task 4: Starting the IBM Cognos 8 Go! Dashboard ServiceUse these steps to manually start the Go! Dashboard service on the CommandCenter machine.

On a Windows system, the Go! Dashboard service is configured by default to start automatically when Windows starts. In AIX, you must configure the process as a daemon to have Go! Dashboard process start automatically using your operating system documentation.

Windows

For a Windows environment, use the following steps.

Steps:

1. On to the 6.0.1 reporting server, open a Command Prompt window (using the Run as Administrator option) and navigate to:

<COGNOS_HOME>\dashboard\bin

2. To start the service immediately, type:

startup.bat

Note: A Tomcat window will display. Do not close this window while you are working with Go! Dashboard.

A new service, IBM Cognos 8 Go! Dashboard, is now available in Windows Services.

AIX

For an AIX environment, use the following steps.

Steps:

1. On to the 6.0.1 reporting server, open an AIX shell and navigate to:

<go_dashboard_location>/dashboard/bin



2. Set your JAVA_HOME environment variable to point to your Java 1.6 JRE.

export JAVA_HOME=path_to_java1.6_jre or JAVA_HOME=path_to_java1.6_jre; export JAVA_HOME

3. Manually start the Go! Dashboard service.

./startup.sh

Once you have completed the Go! Dashboard configuration, you can configure startup.sh to run as a daemon.

Task 5: Set Database Connection Properties for CommandCenterAfter installing the Cognos software, you must configure Cognos to access the database. Using the Cognos tools, you must delete the connection to the CommandCenter database instance in the Cognos application and replace it with a new connection to CommandCenter and specify the connection settings.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. On the CommandCenter server, start the IBM Cognos Configuration application as a

user with administrative privileges.3. Start IBM Cognos Configuration:

a. Launch a Command Prompt window (using the Run as Administrator option) or AIX shell.

b. Navigate to the following directory:

<COGNOS_HOME>/bin64


Windows

cogconfig.bat

AIX

./cogconfig.sh

4. Expand the tree for Data Access | Content Manager.5. Remove the current database connection and add a new connection using the following

steps, based on your type of Oracle: a single Oracle database or an Oracle RAC database.

Single Oracle Database

For Oracle databases (non-RAC), use the following steps:

a. Right-click cognos8 and select Delete from the menu.b. Create the new Content Store by right-clicking Content Manager and selecting

New resource | Database.c. In the New Database window, do the following:

d. Click OK.

In this field... Do this...

Name Enter a descriptive name for the resource. It does not have to match the database identifier.

Type Click the arrow and select Oracle Database from the list.



e. In the fields on the right of the IBM Cognos Configuration dialog box, click each of the following fields and enter the information for the database instance you are connecting to.

f. Click File | Save to save your changes.

Oracle RAC

For Oracle RAC databases, use the following steps:



d. Click OK.e. In the fields on the right of the IBM Cognos Configuration dialog box, click each of

the following fields and enter the information for the database instance you are connecting to.

For this field... Do this...

Database server and port number

Enter the name of the database server and the listener port used for the database instance.

User ID and password Click the value field and then click the pencil icon.

In the Value - User ID and password field, enter the appropriate values for the Cognos user you created for the content store database.

If you used the IBM OpenPages GRC Platform Installer for Cognos, the default user is cognos.

Service name Enter the SID for the database instance.



Type Click the arrow and select Oracle Database (Advanced) from the list.




User ID and password Click the value field and then click the Edit icon.

In the Value - User ID and password field, type the appropriate values for the Cognos user you created for the content store database.




6. Click File | Save to save your changes.

Database specifier Enter a database specifier string in the following format with no carriage returns:(description=(address=(host=<server_name>) (protocol=tcp)(port=<port>) (connect_data(service_name=<service_name>)))

Where:• server_name is the name of the RAC database

server.• port is the listener port used by the RAC

database server.• service_name is the service name of database

instance.This information is available in the tnsnames.ora file located by default at:<ORACLE_HOME>\network\admin

Example(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = RAC1)(PORT = 1522)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = OPdata)))




• • • • • • • • • •Testing the Cognos Installation

You can test your Cognos 8 reporting installation and configuration by starting the Cognos 8 Service using IBM Cognos Configuration and then opening Cognos Connection, the Cognos Web portal. On Windows, the Cognos 8 Service is configured to start automatically by default.

Note: Make sure the OpenPages services are running before you test Cognos Connection. See the “Starting and Stopping OpenPages” chapter

Use the following steps to verify that Cognos was installed properly.

Steps:





<COGNOS_HOME>/bin64c. Execute the following command:

Windows cogconfig.bat

AIX ./cogconfig.sh

3. Start the IBM Cognos 8 service by clicking Actions | Start. If the Start option is not available, the service has already started.

Note: IBM Cognos Configuration may pause while starting the Cognos service if you have not configured a mail server. Click OK in the dialog box that displays, then click Continue.

4. After Cognos is started, open a Web browser.5. Type the following address:

http://<hostname>/cognos8

Where: <host_name> is the name of the Web server machine that contains the Cognos virtual directory and cognos8 is the name of that virtual directory.

If the IBM Cognos Connection page appears, the installation and configuration were successful.



Cognos Administration.7. Click the New Dashboard icon in the tool bar.

If an IBM Cognos 8 Go! Dashboard blank dashboard canvas appears, you have successfully installed the product.



7
Installing OpenPages CommandCenter
This chapter explains how to install OpenPages CommandCenter on the reporting server. It also describes some post-install steps that can be performed to improve performance.


“About the OpenPages CommandCenter Installation” on page 124 “Checklist for Installing CommandCenter” on page 125 “Before You Begin” on page 126 “Installing CommandCenter” on page 130 “CommandCenter Post-Installation Steps” on page 135


About the OpenPages

• • • • • • • • • •CommandCenter Installation

After installing the Cognos 8 Business Intelligence software, you install the OpenPages CommandCenter software which integrates with the OpenPages application. After integrating CommandCenter, you can generate reports that use the hierarchy of OpenPages compliance objects and can report on the metadata attached to those objects.

This chapter describes how to install the CommandCenter software and describes post-installation steps to perform on the reporting server.

Note: The CommandCenter installer will change the name of the Cognos service to CommandCenter.

Chapter 7: Installing OpenPages CommandCenter


• • • • • • • • • •Checklist for Installing CommandCenter

Use the following checklist to guide you through installing CommandCenter. Each task below has several steps.

Table 7-1: Checklist for Installing CommandCenter

Task Checklist


2. Launch the OpenPages CommandCenter installer. See “Installing CommandCenter” on page 130.

3. Perform CommandCenter post-installation steps. See “ CommandCenter Post-Installation Steps” on page 135.




Before starting the IBM OpenPages GRC Platform Installer for CommandCenter, verify your system requirements as described in Chapter 2 “Prerequisites” on page 15.

PrerequisitesVerify that you have installed the Cognos BI software, as described in Chapter 6 “Installing Cognos and Content Store” on page 95. Make sure that the Cognos service is started.

Disable Anti-Virus


If an anti-virus package is running on the 6.0.1 reporting server, for faster installation times, you may disable the anti-virus software before running the OpenPages installation.

Obtain Installation Information


During the CommandCenter installation, you will be asked for the following information. You should have this information available before starting.

Determine the following locations, which will be created by the installer:

CommandCenter installation folder location Cognos 8 Framework Model output folder location

Obtain the following values before installing:

CommandCenter URL Cognos 8 Framework Generator port number

Obtain the following values, which were previously created:

Cognos 8 Reporting installation folder location Cognos user name and password Location of the exported data files Oracle client installation folder location OpenPages database host name OpenPages database port OpenPages database alias OpenPages database SID OpenPages superuser name OpenPages superuser password OpenPages application server name OpenPages Application cluster administrator and cluster member server ports OpenPages application server user name OpenPages application server user password OpenPages backup/restore directory SSL port (if using SSL) e-mail server, user name, address for sender



Modifying the Environment Variables Set the following environment variables in Windows or AIX on the reporting server.

Modifying the Environment Variables - WindowsSet the environment variables on a Windows-based reporting server, as follows:

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Launch Windows Explorer.3. Right-click Computer and select Properties from the menu.4. Click the Advanced system settings link. 5. In the System Properties dialog, click the Environment Variables button.6. Add the JAVA_HOME environment variable:

a. Click the New button.b. In the New System Variable window, enter JAVA_HOME in the Name field.c. Enter full path to the environment variable is configured to point to the installation

location of your Java Runtime Environment (JRE).d. Click OK.

7. Add the COGNOS_HOME environment variable:a. Click the New button.b. In the New System Variable window, enter COGNOS_HOME in the Name field.c. Enter full path to the environment variable is configured to point to the installation

location of Cognos 8.d. Click OK.

8. Add the ORACLE_HOME environment variable:a. Click the New button.b. In the New System Variable window, enter ORACLE_HOME in the Name field.c. Enter full path to the ORACLE_HOME directory, by default:

C:\openpages_data\repository\client112_ac_x86\software

Note: If you install the OpenPages application and CommandCenter on the same server, enter the location to the 32-bit Oracle Client.

d. Click OK.9. If the TNS_ADMIN variable does not exist, create the variable:

a. Click the New button.b. In the New System Variable window, enter TNS_ADMIN in the Name field.c. Enter full path to the tnsnames.ora file, which is usually located in the

<Oracle_Home>\network\admin directory.d. Click OK.

10. Set the NLS_LANG environment variable to the database character set configured during the database install, by default AMERICAN_AMERICA.AL32UTF8. a. Click the New button.b. In the New System Variable window, enter NLS_LANG in the Name field.c. Enter database character set specified during the database install. d. Click OK.

11. Add JAVA_HOME and ORACLE_HOME to the PATH variable: a. Select the PATH variable and click Edit.b. In the Edit System Variable window, add %JAVA_HOME%/bin and %ORACLE_HOME%/

bin.c. Click OK.

12. Click OK to save the changes and close the window.



Modifying the Environment Variables - AIXSet the environment variables on an AIX-based reporting server, as follows:

Steps:

1. Log onto the 6.0.1 reporting sever machine as a non-root user with administrative privileges.

2. Execute the following command to determine which executable are in the PATH:

java -version

If the PATH variable exists, the version of the Java executable appears. If you get a Java error: Command not found, the path is not set.

3. Execute the following commands to set the environment variables, using the appropriate paths:export JAVA_HOME=/opt/local/jdk1.6.0/bin

export COGNOS_HOME=/opt/cognos/cognos8


export TNS_ADMIN=$ORACLE_HOME/network/admin

export LIBPATH=$COGNOS_HOME/bin64:$COGNOS_HOME/bin:$ORACLE_HOME/lib

export NLS_LANG=AMERICAN_AMERICA.AL32UTF8

PATH=$ORACLE_HOME/bin:$JAVA_HOME/bin:$PATH

Where:

• JRE_HOME is the location of the JRE home directory, by default /opt/local/jdk1.6.0/bin.

• COGNOS_HOME is the location of the Cognos bin directory.• ORACLE_HOME is the Oracle data home.• TNS_HOME is the location of the tnsnames.ora file• NLS_LANG is the database character set specified during the database install.

Note: If you install the OpenPages application and CommandCenter on the same server, ORACLE_HOME must point to the 32-bit Oracle Client.

4. Refresh the profile by closing and re-opening the AIX shell or run the following command:

cd / . .profile










Steps:





Example




Run the following command as the root user to create and change the ownership of the folder where CommandCenter will be installed, such as /opt/OpenPages/CommandCenter.

Steps

1. Log onto the reporting server as root.2. Open an AIX shell. 3. If the CommandCenter installation directory does not exist, enter the following

command to create the directory:

mkdir -p <SOFTWARE_DIRVE>


chown -R <user>:<group> <SOFTWARE_DRIVE>

Example mkdir -p /opt/OpenPages/CommandCenter chown –R opuser:staff /opt/OpenPages/CommandCenter

Create AIX PasswordsMake sure you have created the required users and groups for AIX. See “Create Users and Groups for AIX” on page 26.



• • • • • • • • • •Installing CommandCenter

The IBM OpenPages GRC Platform Installer for CommandCenter will lead you through the installation process for CommandCenter. Once the install is complete, make sure you perform the necessary post-install steps detailed in this chapter.

Installing CommandCenterUse the following steps to install OpenPages CommandCenter using the IBM OpenPages GRC Platform Installer for CommandCenter.

Note: Close all application windows before running the CommandCenter install program.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges and full access to the local server drives.

Note: For an AIX environment, the user should be a non-root user, such as the user you created for the reporting server installation, such as opuser.

Task 1: Launch the Installer1. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell.2. Navigate to the following location within the CommandCenter install directory.You may

have already copied this directory when installing Cognos:

Windows

OP_6.0.1_CommandCenter\OpenPages_CommandCenter\Disk1\InstData\Windows\VM

AIX

OP_6.0.1_CommandCenter\OpenPages_CommandCenter\Disk1\InstData\AIX\VM

3. Start the IBM OpenPages GRC Platform Installer for CommandCenter using one of the two following commands, as appropriate:

Windows

CommandCenterSetup.exe

AIX

./CommandCenterSetup.bin

Note: The user must have Execute permission to run CommandCenterSetup.bin.




Task 2: Specify Installation Information1. On the Installation Information screen:

a. Specify the type of installation, the CommandCenter install folder, Cognos install folder, and the Oracle client install folder.

b. Click Next.

Task 3: Specify Database Information1. On the OpenPages Database Information screen:

a. Specify the information needed to connect to your OpenPages database.


Type of Installation Select New Installation for a clean installation of CommandCenter.

New Installation

CommandCenter Installation Folder

Enter the path to where the CommandCenter components will be installed. Or click Choose to browse to the directory.

WindowsC:\OpenPages\CommandCenter AIX /opt/OpenPages/CommandCenter

Cognos Installation Folder

Enter the path to where the Cognos 8 components were installed. Or click Choose to browse to the directory.

Windows C:\Program Files (x86)\cognos\c8_64 AIX /opt/cognos/cognos8_64

Oracle 32-bit Client Installation Folder

Enter the path to where the Oracle Client was installed. Or click Choose to browse to the directory.

Windows C:\openpages_data\repository\ client112_ac_x86\softwareAIX /opt/openpages_data/repository/client112_ac_x86\software

CommandCenter URL Enter the URL to be used for CommandCenter.

http://<server_name>:80/cognos8

For an SSL environment, enter:https://<server_name>:80/cognos8


Database Host Name Enter the name of the server that hosts the OpenPages database.

Database Port Enter the port used to access the OpenPages database.

Note: Make sure this is the same port as used by the OpenPages application.

Alias Name Enter the TNS alias name of the OpenPages database instance on the CommandCenter server machine.

Database Identifier Select the method for identifying the CommandCenter database instance, either SID or Service Name and enter the SID or Service Name in the field.

Note: For Oracle RAC installations, always use Service Name.

OpenPages User Name Enter the user name that CommandCenter uses to access the database instance.

openpages



b. Click Next.

Task 4: Configure the Connection to the OpenPages Application1. On the OpenPages Server Information screen:

a. Specify the information CommandCenter needs to connect to the OpenPages application.

b. Click Next.

OpenPages Password Enter the password for the OpenPages user account entered above.


Application Server Host Name Enter the IP address or machine name of the OpenPages application server to which CommandCenter will connect.

• If this is the first CommandCenter server, enter the IP address or machine name of the OpenPages cluster administrator.

• If this is a secondary CommandCenter server, enter the IP address of the OpenPages cluster member application server to which CommandCenter will connect.

Application Server Port Enter the port number used to access the OpenPages application. This should be SSL port number if you select the SSL option.

Note: If this is a secondary CommandCenter server, enter the port of the OpenPages cluster member to which CommandCenter will connect. The port number for cluster member are dynamically assigned during installation, and is available in the ObjectManager.properties file on that OpenPages server.

Application User Name Enter the user name that CommandCenter will use to access the OpenPages application.

OpenPagesAdministrator

Application Password Enter the password for the user account entered above.

Is SSL configured for the OpenPages Server?

Select Yes if CommandCenter must use an SSL connection to the OpenPages application. Select No if an SSL connection is not required.

If you select Yes, make sure you enter the SSL port in the Application Server Port field above. The SSL port is listed in the following log:

Windows<OP_Home>\temp\aurora\conf\ OPSERVER_STATUS.txt

AIX<OP_Home>/temp/wasconfig/<OpenPages_Node_Name>.config.props




Task 5: Specify Reporting Framework Model Folder and Port

1. On the Reporting Framework Information screen:a. Specify the following information needed to configure the Framework Generator

service.

b. Click Next.

Task 6: Specify CommandCenter Backup and Restore Information1. On the Backup & Restore Information - 1 of 2 screen:

a. Specify the database and Cognos information that CommandCenter needs to configure the CommandCenter backup and restore utility.

b. Click Next.


Framework Output Folder Enter the directory path to where the Framework Model will be placed.

The default value uses the CommandCenter Installation Folder specified above.

Windows C:\CommandCenter\ FrameworkGeneration\output

AIX /opt/OpenPages/CommandCenter/FrameworkGeneration/output

Framework Port Enter the port number used to access the Framework Generator server.

8080


Database Alias Name Enter the name of the CommandCenter database instance on the database server machine.

Cognos User Name Enter the Cognos account user name. cognos

Cognos Password Enter the password for the Cognos username defined above.



2. On the Backup & Restore Information - 2 of 2 screen:a. Specify the email information for the CommandCenter to send backup/restore

notifications and the directory to store backed-up data.

b. Click Next.

Task 7: Install the CommandCenter Application1. On the Confirm Installation Data screen:

a. Review your selections. b. When satisfied, click Install to begin the install process.

The CommandCenter installation takes approximately 25 minutes to complete, but may take longer depending upon your environment.

2. On the Install Complete screen, click Done to complete the install.

IMPORTANT! If you start CommandCenter before generating the reporting schema, you will see the following error message: HTTP: 403 - Forbidden: Access to the specified resource has been forbidden. Follow the steps in “Creating the Reporting Schema and Framework” on page 157 to generate reporting schema and remove this warning message.


Mail Server Enter a mail server to use for OpenPages workflow notifications.

yourserver.yourdomain.com

E-mail User Name Enter the displayed name of the E-mail Sender Address.

sysadmin

From Address Enter the e-mail address used for sending messages from the workflow notification service.

[email protected]

OpenPages Backup/Restore Location

Enter the directory where the Backup/Restore utility places the files it creates when backing up and restoring the CommandCenter database and application settings.

The default value uses the CommandCenter Installation Folder specified above.

Examples

WindowsC:\CommandCenter\openpages_cc_ backup_restore

AIX/opt/CommandCenter/openpages_cc_backup_restore

Specify the location where the CommandCenter migration zip file was extracted

Enter the directory where you extracted the Zip file created during the CommandCenter database migration.

WindowsC:\

AIX/opt/



• • • • • • • • • •CommandCenter Post-Installation Steps

After installing CommandCenter, perform each of the following tasks. All tasks in this section are required, unless otherwise specified.

Configuring Cognos Application FirewallThis task is required.

The IBM OpenPages GRC Platform Installer for CommandCenter enables the Cognos Application Firewall (CAF) by default. Use the IBM Cognos Configuration tool to add any associated OpenPages application servers, which will be considered “safe” for use by the Cognos software.

Adding Servers to the Cognos Safe ListUse the following steps enable CAF and add servers to the list of safe domain names.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Start IBM Cognos Configuration:


b. Navigate to the following directory: <COGNOS_HOME>/bin64

c. Execute the following command:Windows cogconfig.bat

AIX ./cogconfig.sh

3. In the Explorer pane, locate IBM Cognos Application Firewall in the tree structure (Local Configuration > Security > IBM Cognos Application Firewall).

4. In the Properties pane, click the Valid domain names or hosts field and click the pencil icon that appears.

5. In the Valid domain or hosts dialog box that appears, click Add.6. Enter the names of all OpenPages application servers.7. Click OK when you have added all of the appropriate servers.8. Save the configuration and restart the Cognos service. If you are using Windows

Services to restart the Cognos service, the service will be listed as CommandCenter.



Configuring a Mail Server AccountThis task is optional.

If you want to configure a mail server so application users can send CommandCenter reports by e-mail, you must configure mail server settings on every computer where CommandCenter is installed. You do this by configuring the Notification settings in the Cognos Configuration application.

The details for configuring Notification settings are in the “Specify a Connection to a Mail Server Account” topic in the IBM Cognos 8 Business Intelligence Installation and Configuration Guide 8.4.1 available on the Cognos Web site (http://www.ibm.com).

Starting the OpenPages Framework Model Generator ServiceThis task is required.

Before creating the reporting schema and updating the reporting framework you need to start the Framework Manager service, which relies on the Apache Tomcat software.

Starting the Framework Model GeneratorUse the following steps to start the Framework Manager service.

Steps

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Make sure that the OpenPages Framework Model Generator service is started.

Windows

Use Windows Services and make sure that the OpenPages Framework Model Generator service has started.

AIX

Open an AIX shell as a user with administrative privileges and navigate to the following directory:

/opt/OpenPages/CommandCenter/apache-tomcat-6.0.26/bin - or -

/opt/OpenPages/CommandCenter/apache-tomcat/bin

Enter the following command: ./startup.sh



Optimizing CommandCenter Database SettingsThis task is required.

You can optimize the performance of the database for all CommandCenter report format types by modifying Open session commands entry within Cognos on each CommandCenter installation:

Modifying Cognos to Improve Database PerformanceUse the following steps to modify Cognos to improve CommandCenter performance.

Steps:

1. Open an Internet Explorer browser window and point the browser to the following URL (if you are using port 80 for CommandCenter):


Where: <server_name> is the name of the reporting server and cognos8 is the name of the virtual directory created for CommandCenter.

2. Launch IBM Cognos Administration:a. If the Cognos splash page appears, click the Administer IBM Cognos Content

link. b. If the IBM Cognos Connection page appears, click Launch then select IBM Cognos

Administration.3. On the Configuration tab, click Data Source Connections from the list in the left

pane. This page may be active by default.4. Click the More... link next to OpenPages DataSource.5. On the Perform an action - OpenPages DataSource screen, click the Set properties

link.6. On the Set properties - OpenPages DataSource screen:

a. Select the Connection tab.b. Click Set... next to Open session commands.

7. On the Set the commands - Open session commands screen:a. Paste the following block of XML into the XML database commands field:

<commandBlock><commands><sqlCommand><sql>begin OP_SESSION_MGR.SET_ACTOR_ID_PRIVATE (#$account.parameters.openPagesUserId#);end;</sql></sqlCommand></commands></commandBlock>

b. Click OK to save your changes.



8
Performing Post-installation Tasks
After you finish installing all the components for IBM OpenPages GRC Platform, there are several tasks you can perform to control access to and to improve the performance of the OpenPages environment.

The following topics are contained in this chapter:

Installation Summary on page 140 Checklist for Post-installation Tasks on page 141 Tailoring the Database Server on page 143 Tailoring the Application Server on page 145 Tailoring CommandCenter on page 157 Starting OpenPages on page 162 Accessing OpenPages on page 163 Validating the Installation on page 164 Applying the IBM OpenPages GRC Platform 6.0.1.1 Patch on page 166


• • • • • • • • • •Installation Summary

At this point in the installation process your servers have the following software installed and configured:

Database server:

Oracle Database 11g R2 A database instance A folder with the same name as the SID of your OpenPages database instance, under

the openpages_data\repository\database10203\oradata directory. (This folder is created when the database instance is created.)

Admin server:

Oracle WebLogic Server version 10.3.2/IBM WebSphere® Application Server (WAS) Network Deployment 7.0.0.13

Oracle Client 11g R2 64-bit OpenPages Version 6.0.1

Managed server (if you have a clustered environment):

Oracle WebLogic Server version 10.3.2/IBM WebSphere® Application Server (WAS) Network Deployment 7.0.0.13

Oracle Client 11g R2 64-bit OpenPages Version 6.0.1

CommandCenter (Reporting) server:

OpenPages CommandCenter Version 6.0.1 Cognos 8.0 Business Intelligence Oracle Client 11g R2 32-bit

Chapter 8: Performing Post-installation Tasks


• • • • • • • • • •Checklist for Post-installation Tasks

Use this checklist when you perform post-installation tasks.

Table 8-1: Checklist for Post-Installation Tasks

Task Action

Post-install steps for the database server

1. Disable Oracle Skip Scan. See “Disabling Oracle Skip Scan” on page 143.

Required

2. Allocate memory for the database instance. See “Tuning Memory for the Database Instance” on page 143.

Recommended

Post-install steps for the Application Server

1. AIX-only. Configure the WebSphere Application Server to allow a user to log into the OpenPages application and the Fujitsu Interstage BPM console concurrently. See “Enabling the Same-User Access to OpenPages and Fujitsu Interstage BPM — AIX only” on page 146.

Required

2. Improve concurrency for use with multiple administrators. See “Improving Concurrency” on page 147.

Required

3. Increase WebLogic Server memory allocations. See “Increasing the WebLogic Server Memory Requirements — Windows only” on page 149.

Recommended

4. Increase the size of the paging file. See “Increasing the Paging File Size” on page 151.

Recommended

Post-install steps for the CommandCenter

1. Create a reporting schema and then update the reporting framework from the OpenPages application. See “Creating the Reporting Schema and Framework” on page 157.

Required

2. Change the CommandCenter host and port settings. See “Changing the CommandCenter Host and Port Settings” on page 158.

Required

3. Secure access to CommandCenter. See “Securing Access to the CommandCenter Portal” on page 159.

Optional



Post-install steps for the OpenPages environment

1. Install the OpenPages 6.0.1.1 patch. See “Applying the IBM OpenPages GRC Platform 6.0.1.1 Patch” on page 166.

Required

2. Validate that OpenPages is working as expected. See “Validating the Installation” on page 164.

Recommended

3. Add additional OpenPages application servers. See Appendix A “Adding Cluster Members” on page 195.

Required if scaling your OpenPages environment.

4. Load-balance OpenPages and CommandCenter. See Appendix B “Configuring Clustered Environments” on page 219.

Required for scaled environments

5. Configure OpenPages and CommandCenter for SSL. Appendix C “Configuring SSL” on page 245.

Required if implementing SSL

6. Configure OpenPages and CommandCenter to function if installed on the same server. Appendix E “Configuring OpenPages on One Machine” on page 305.

Required if OpenPages and CommandCenter are on the same server

7. Configure single sign-on settings. See Appendix F “Integrating Single Sign-on with OpenPages” on page 307.

Required if using single sign-on

Table 8-1: Checklist for Post-Installation Tasks

Task Action



• • • • • • • • • •Tailoring the Database Server

Oracle database tuning involves the following tasks.

Disabling Oracle Skip ScanThis task is required.

The Oracle skip scan feature was introduced in Oracle 9i. Skip scanning lets a composite index be split logically into smaller subindexes. In skip scanning, the initial column of the composite index is not specified in the query. In other words, it is skipped. For larger databases with data that is changed frequently, skip scanning can be less efficient than a range scan.

Use the following SQL command to disable the Oracle skip scan, which can improve the performance of your system

1. Log on to a machine with SQL*Plus and access to the database server. 2. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as a user with administrative privileges.

Note: For AIX installs, use a non-root, such as the user you created for the OpenPages installation, opuser

3. Log on to SQL*Plus using the following command.

sqlplus sys/<sys_password>@<SID> as sysdba

Where <SID> is the OpenPages database instance.

4. At the SQL prompt, type the following command:

alter session set "_optimizer_skip_scan_enabled"=FALSE

5. When the command is completed, logout from SQLPlus

Tuning Memory for the Database InstanceThis task is recommended.

If your application is running in a heavy-load environment, after installing OpenPages, we recommend that you allocate as much memory as possible to Oracle for a database instance.

Memory Tuning GuidelinesThe following table provides general guidelines for memory allocation on a system with 4 GB or more of RAM.

Table 8-2: Memory Tuning Guidelines

For this... Allocate...

Operating system 1 - 4 GB of physical RAM

SGA Size 75% of remaining physical RAM to the SGA_TARGET parameter.

Minimum allocation: 2048 MB (or 2 GB)

PGA Size 25% of remaining physical RAM to the PGA_AGGREGATE_TARGET parameter.

Minimum allocation: 1024 MB (or 1 GB)



Example 1 - Machine with 4 GB of RAM

If a machine has 4 GB of physical RAM, 1 GB would be available for the Windows OS after meeting the minimum SGA (2 GB) and PGA (1 GB) memory allocation requirements for a single database instance.

Example 2 - Machine with 8 GB of RAM

If a machine has 8 GB of physical RAM and you want 2 GB available for the Windows OS, then 6 GB would remain for allocation to Oracle. Using the guidelines outlined in the table, the remaining 6 GB could be allocated to a single database instance as follows:

• SGA: 4608 MB (or 4.5 GB, which is 75% of 6 GB)• PGA: 1536 MB (or 1.5 GB, which is 25% of 6 GB)

Example 3 - Machine with Multiple Database Instances

Note: If you are planning to run multiple database instances on the same machine, you should adjust memory correspondingly, so that all the concurrently running instances fit into the available physical RAM to avoid swapping to disk.

For example, to run the OpenPages Repository and CommandCenter Repository services on the same machine with 8 GB of RAM, the memory allocation strategy could be as follows:

• 1 GB of RAM for the OS• The remaining 7GB of RAM could be split between the OpenPages Repository and

CommandCenter Repository as follows:- OpenPages Repository instance: 3 GB SGA + 1.5 GB PGA- CommandCenter Repository instance: 1.5 GB SGA + 1 GB PGA



• • • • • • • • • • Tailoring the Application Server

Unless otherwise indicated, most of the tasks listed in this section are recommended.

Configuring the Database Connection PoolThis task is required.

The OpenPages and workflow servers each has a pool of JDBC connections which can be used by applications when connecting to the database. You should configure the number of available connections in the pool based on the number of users. These connections are returned to the connection pool when the application disconnects from the database.

Use the following steps to set the size of the database connection pool on the OpenPages and workflow servers.

Steps:

Windows

1. Open a Web browser.2. Navigate to the Oracle WebLogic Administration Console for the OpenPages server:

http://<server_name>:<port>/console

where <server_name> is the name of the OpenPages application server and <port> is the WebLogic Server port assigned during installation, by default 7001.

Note: Do not use localhost.

3. Use the WebLogic Administration Console to configure the connection pool:a. Log in to the WebLogic Administration Console as with an administrator account. b. Expand the Services tree in the Domain Structure section and click JDBC.c. Click the Lock & Edit button in the Change Center to make the settings available

for editing.d. On the Summary of Services page, click Data Sources.e. On the Summary of JDBC Data Sources page, click OpenPages Data Source.f. On the Settings for OpenPages Data Source page, click the General tab, then

the Connection Pool tab.g. Enter a value in the Initial Capacity and Maximum Capacity fields, by default

75. For an upgrade, enter the value set in your previous system.h. Click Save.i. When done, click the Activate Changes button in the Change Center to

implement the changes.j. Log out of the Oracle WebLogic Administration Console.k. Navigate to the Oracle WebLogic Administration Console for the workflow server:


where <server_name> is the name of the workflow application server and <port> is the WebLogic Server port assigned during installation, by default 49901.


4. Repeat these steps to configure the database connection pool for the workflow server.

AIX

1. Open a Web browser.



2. Navigate to the IBM Integrated Solutions Console for the OpenPages server.

http://<hostname>:<port>/ibm/console/

where <server_name> is the name of the OpenPages application server and <port> is the WebSphere Application Server port assigned during installation, by default 9060.


3. Expand the tree for Resources | JDBC in the left panel of the Integrated Solutions Console.

4. Click the Data sources link in the list.5. On the Data Sources page, click the data source.6. On the <data source> page, under Additional Properties, click Connection Pool

Properties link.7. On the Connection Pools page:

a. Enter a value for the Maximum connections (by default 75) and Minimum connections (by default 1) fields. For an upgrade, enter the value set in your previous system.

b. Click Apply. c. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration. d. Click OK to exit.

8. Log out of the Integrated Solutions Console.9. Navigate to Integrated Solutions Console for the workflow server

http://<hostname>:<port>/ibm/console/

where <server_name> is the name of the workflow application server and <port> is the WebSphere Application Server port assigned during installation, by default 9061.


10. Repeat these steps to configure the database connection pool for the workflow server.

Enabling the Same-User Access to OpenPages and Fujitsu Interstage BPM — AIX only


By default, the WebSphere application server does not allow a single user to log into the OpenPages application and the Fujitsu Interstage BPM console concurrently. To allow a user to log into both applications, perform the following steps:

For the OpenPages application:

1. Open a Web browser.2. Navigate to the IBM Integrated Solutions Console for the OpenPages server.

http://<server_name>:<port>/ibm/console/

where <server_name> is the name of the OpenPages application server and <port> is the WebSphere Application Server port assigned during the installation, by default 9060.


3. Expand the tree for Servers | Server Types in the left panel of the Integrated Solutions Console.

4. Click the WebSphere application servers link in the list.



5. On the Application servers page, perform the following steps for each OpenPages server listed:a. Click the application server you want to configure. b. On the <OpenPages-server-name> page, click the Configuration tab, if it is

not the active tab.c. Under Container Settings, expand Web Container Settings and then click on

Web container link. d. On the Web Container page, click Session management. e. Under Session tracking mechanism, click the Enable cookies link.f. On the Cookies page, enter opsosa in the Cookie name field. g. Click Apply. h. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration. i. Click OK to exit.

For the Fujitsu Interstage BPM console:

1. Open a Web browser.2. Navigate to http://<server_name>:<port>/ibm/console/. 3. Expand the tree for Servers | Server Types in the left panel of the Integrated

Solutions Console.4. Click the WebSphere application servers link in the list.5. On the Application servers page, perform the following steps for each OpenPages

server listed:a. On the <OpenPages-server-name> page, click the Configuration tab, if it is

not the active tab.b. Under Container Settings, expand Web Container Settings and then click on

Web container link. c. On the Web Container page, click Session management. d. Under Session tracking mechanism, click the Enable cookies link.e. On the Cookies page, enter opibpm in the Cookie name field. f. Click Apply. g. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration. h. Click OK to exit.

Improving ConcurrencyThis task is required.

A concurrency conflict can result in the following error message: “Operation failed, security settings are being concurrently modified by another administrator. Please try again later.”

To help avoid concurrency errors caused when two administrators attempt to concurrently modify settings, you must run the SQL script enable-session-sleep.sql to grant Execute permission to an Oracle username.

Steps:

1. On a computer that has SQL*Plus and access to the database server, log on as a user with SYSDBA permissions.

2. Launch a Command Prompt window (using the Run as Administrator option) or AIX shell as a user with administrative privileges.



3. Copy the INSTALL_SCRIPTS directory from the Installer Disc 1 DVD or on your network share location to the local system.a. Navigate to the following folder:

OP_6.0.1_Configuration\Database

b. Copy the INSTALL_SCRIPTS directory to the local system.

Note: For AIX, make sure you have full rights to the local installation directory and the files in the directory.

4. Navigate to the INSTALL SCRIPTS directory.5. Execute the SQL script named enable-session-sleep.sql in that directory.

On a command line, use the following syntax to pass the appropriate parameters:

sqlplus /nolog @sql-wrapper enable-session-sleep.sql <log_file_name> <connect_identifier> <sysdba_user_name> <sysdba_user_password> <schema_owner_name>

The script displays a message if the process completes properly.

6. If the script does not execute properly, check the log files for error messages:

Example

sqlplus /nolog @sql-wrapper enable-session-sleep.sql enable-session-sleep.log opx10g sys manager openpages


<log_file> The name and location of the log file created by the script.

<connect_identifier> Identify the connection to the database, for example System Identifier (SID) for the database, or TNS alias

<sysdba_user_name> Database administrator user name

<sysdba_user_password Password for the database administrator user account

<schema_owner_name> Schema owner user name



Increasing the Application Server Memory RequirementsThese tasks are recommended.

Use the following procedures to improve system performance by increasing memory allocation on the application servers. See either:

“Increasing the WebLogic Server Memory Requirements — Windows only” on page 149 “Increasing the WebSphere Application Server Memory Requirements — AIX only” on

page 150

Increasing the WebLogic Server Memory Requirements — Windows onlyIf your application is running on a high-end system, you should increase the memory allocation for the WebLogic Server.

Increasing Memory Allocation for WebLogic Server


Use the following steps to increase the memory allocation for WebLogic Server.

Steps:1. Log on to the 6.0.1 application server as a user with Administrator privileges.2. Launch a Command Prompt window (using the Run as Administrator option) and

type regedit at the prompt to open the Registry Editor..3. Navigate to the following registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\4. Locate the following services

• InterstageBPMAdminServer• InterstageBPMCS#• OpenPagesAdminServer• OpenPagesServer#

5. For each of these services, complete the following steps:a. Navigate to the Parameters sub-folder. b. Double-click the CmdLine parameter.c. Replace the -Xmx value with the value -Xmx1536m. For example:

-server -Xms256m -Xmx1536m6. Exit the regedit program and close the Command Prompt window.

Note: In a clustered environment, increase the memory of each WebLogic Server instance.

Increasing Memory Allocation for WebLogic Server Command Line Files


Use the following steps to increase memory allocation for WebLogic Server command line files.

Steps:1. On the 6.0.1 application server. 2. Navigate to the <OP_Home>\OpenPagesDomain\bin folder, by default:

c:\OpenPages\OpenPagesDomain\bin. 3. Locate the following WebLogic Server command files in the folder:

• startWebLogic.cmd • startOPServer.cmd

4. For each WebLogic Server command file listed in Step 3, do the following:a. Open the file using a text editor.b. Replace the -Xmx value with the value -Xmx1536m. For example:

-Xms256m -Xmx1536mc. Save your changes to the file.



Increasing the WebSphere Application Server Memory Requirements — AIX onlyIf your application is running on a high-end system, after installing OpenPages, it is recommended that you increase the memory for the WebSphere Application Server.

Configuring In-Memory Session Count


The Maximum In-Memory Session Count configures the number of distinct sessions saved in memory.

Allowing too few sessions in memory could prevent users from accessing the system. Allowing too many sessions could use resources unnecessarily. The number of in-memory sessions should be consistent with the number of concurrent users.

Use the following steps to set the number of in-memory sessions allowed.

Steps:

1. Open a browser window.2. Log on to the IBM WebSphere Integrated Solutions Console as a server administrator

with the proper permissions, by default:


Where:

<server_name> is the name of the application server

<port> is the port number associated with the application server (for example, 9060).

3. Expand the tree for Servers | Server Types in the left panel of the Integrated Solutions Console.

4. Click the WebSphere application servers link in the list.5. On the Application servers page, click the name of the application server you want to

configure.6. On the Application servers | OpenPages-server-name page, click the

Configuration tab. 7. Under Session Management, click Web Container Settings | Web Container. 8. On the Web Container page, click Session Management.9. Enter a value in the Maximum in-memory session count field based on the number

of licensed users, the default value is 1000. You should configure one session for each licensed user.

10. Click OK.11. On the Web Container page, click Save directly to the master configuration.



Increasing the Paging File SizeThis task is recommended.

The recommended values for increasing the paging files size on machines with a 4 GB of RAM the paging file should be set to 8 GB.

Windows

Steps:

1. Click the Start button, select Run and type sysdm.cpl. Press Enter.2. Click the Advanced tab, then click the Settings button in the Performance section.3. In the Performance Options dialog box, click the Advanced tab, and then click the

Change button in the Virtual Memory section.4. Find the list of drives and select the drive that contains your paging file. By default, this

drive will be C: and will contain all of your Windows system files as well.

Note: If necessary, clear the Automatically manage page file size for all drives option.

5. Under Paging File Size, select Custom Size.6. Reset both the Initial Size and Maximum Size values to higher values as needed. 7. Click the Set button.8. Click OK to close the three open dialog boxes.

AIX

Use the chps -s command to increase the size of a paging space.

The chps command changes the attributes of a paging space. The PagingSpace parameter specifies the name of the paging space to be changed.

chps -s LogicalPartitions <PagingSpace_Name>

Where:

-s LogicalPartitions specifies the number of logical partitions to add.

<PagingSpace_Name> is the name of the paging space. View the current paging space and drives using the lsps -a command.

Example

The following example adds four logical partitions to the pgspce paging space

chps -s 4 pgspce



Increasing the Oracle WebLogic Maximum Message SizeThe information in this topic applies only to Windows environments.

The workflow server may send log messages that exceed the default size configured for the WebLogic Server. A workflow message that exceeds the maximum size could cause the workflow service to stop working. To avoid this, you can increase the WebLogic Server maximum message using the following steps.

Steps:

1. Verify that the workflow InterstageBPMAdminServer service is running.2. Open a browser window and log on to the Oracle WebLogic Server Administration

Console as a user with administrative privileges.

By default, the URL is http://<host_name>:49901/console

Where <host_name> is the name of the workflow server where Oracle WebLogic is installed.

3. In the Change Center pane of the Console, click Lock & Edit (if not already selected).4. Expand the Environment tree in the Domain Structure pane and click Servers.5. On the Summary of Servers page, do the following:

a. Click the Configuration tab (if not already selected).b. In the Servers table listing, click the name of a workflow server. For example:

<host_name>-InterstageBPMCS<#>

Where:

<host_name> is the name of the workflow server. <#> is the number of the server.

6. On the Settings for <Host_Name-InterstageBPMCS#> page for the selected server, do the following:a. Click the Protocols tab.b. Under the General tab, navigate to the Maximum Message Size setting.c. In the Maximum Message Size box, increase the byte value to 2000000000. d. Click Save.

7. If you have additional workflow managed servers, repeat Steps 5 and 6 to increase the maximum message size for each Interstage BPM managed server in your environment.

8. When finished, click the Activate Changes button in the Change Center to implement the changes.

9. Log out of the Oracle WebLogic Server Administration Console (no restarting of services is required).



• • • • • • • • • • Tailoring the OpenPages Application

Perform the following tasks, as needed, on your OpenPages application server.

Enabling and Disabling LDAPThese tasks are required if you are incorporating OpenPages into your LDAP environment.

The LDAP configuration file, aurora_auth.config, contains three modules, Openpages, OpenpagesIP and OpenpagesAD. The module named Openpages determines if LDAP is enabled.

If you use LDAP authentication, use the following steps to enable LDAP. See the OpenPages Administrators Guide for more information about using LDAP with OpenPages.

Enabling LDAPUse the following steps to disable LDAP on the primary server and on any secondary servers if you have a load-balanced system.

Steps:

1. Log on to the OpenPages 6.0.1 application server as a user with administrative privileges.

2. Use your LDAP Directory Server (either Microsoft Active Directory or Sun One Directory Server) to add any user that will need access to the OpenPages application or OpenPages environment must be added to the LDAP authentication server.

Make sure to refer to your LDAP Directory Server documentation for the steps required to add OpenPages users to the LDAP server.

3. Log onto the OpenPages application and create the user with same name.4. Stop all OpenPages services. See the “Starting and Stopping OpenPages” chapter.5. Launch a Command Prompt window (using the Run as Administrator option) and

navigate to the directory where you copied the aurora_auth.config file above.

Windows

c:\openpages\aurora\conf

AIX

/opt/openpages/aurora/conf

6. Open the LDAP configuration file, aurora_auth.config, in a text editor (such as Windows Notepad or VI).

The file contains three modules, Openpages, OpenpagesIP and OpenpagesAD. The Openpages module determines if LDAP is enabled.



7. Change the name of the current Openpages module to something different, such as Openpages_default.

From: Openpages { com.openpages.aurora.service.security.namespace.AuroraLoginModule required debug=false; };

to:

Openpages_default { com.openpages.aurora.service.security.namespace.AuroraLoginModule required debug=false; };

8. Depending on the LDAP server you intend to use: • If you are using a Microsoft Active Directory server, change the OpenpagesAD

module name to Openpages.• If you are using a Sun One Directory Server, change the OpenpagesIP module

name to Openpages.9. Specify the correct values for the following properties in the appropriate module:

• provider.url - Change to the IP address and port number of the LDAP authentication server, in the <protocol>://<ip_address>:<port> format.

• security.search.user.dn - Change to the fully qualified name of an administrative user on the LDAP server.

• security.search.user.credentials - Change to the password for the specified user.

• base.dn - The top level of the LDAP directory tree structure (Domain Name) on the LDAP server. If the users to be authenticated are located in multiple locations within your Active Directory structure, you will need to list all of the locations explicitly by using the distinguished names of the locations, each separated by a semi-colon.

• user.attr.id - the attribute name of the user identifier, typically a common name (CN), uid, or sAMAccountName.

Example

Openpages_default { com.openpages.aurora.service.security.namespace.AuroraLoginModule required debug=false; };

Openpages { com.openpages.aurora.service.security.namespace.LDAPLoginModule required debug=false provider.url="ldap://10.128.25.150:389" security.authentication="simple" security.search.user.dn="CN=Administrator,CN=Users,DC=LDAPTesting,DC=local" security.search.user.credentials="openpages" base.dn="CN=Users,DC=LDAPTesting,DC=local" user.attr.id="CN" ; };

10. Save and close the file. 11. Log onto the OpenPages application and change the OpenPages Administrator password

to openpages.12. Restart all OpenPages services as shown in the “Starting and Stopping OpenPages”

chapter.13. Log in to the OpenPages application as the user created in the LDAP Directory Server.



Disabling LDAPIf you use LDAP authentication, you can disable it using the steps in this section.

When LDAP was enabled on your system, the default Openpages module was re-named and either OpenpagesIP and OpenpagesAD was changed to Openpages. To disable LDAP, change the name of the current Openpages module and change the name of the default Openpages module back to Openpages.

Use the following general steps to disable LDAP on the primary server and on any secondary servers if you have a load-balanced system.

Steps:

1. Log on to the application server as a user with administrative privileges. 2. Stop all OpenPages services as shown in Chapter 12 “Starting and Stopping

OpenPages” on page 237.3. Launch a Command Prompt window as a user with administrative privileges and

navigate to the directory that contains the WebLogic Server installation media. by default:

Windows


AIX


4. Open the file aurora_auth.config in a text editor (such as Windows Notebook).5. Change the name of the default Openpages module back to Openpages, for example,

change: Openpages_default { com.openpages.aurora.service.security.namespace.AuroraLoginModule required debug=false; };

to: Openpages { com.openpages.aurora.service.security.namespace.AuroraLoginModule required debug=false; };



6. Change the name of the current Openpages module to something different. For example, change:

From: Openpages { com.openpages.aurora.service.security.namespace.LDAPLoginModule required debug=false provider.url="ldap://192.168.0.165:389" security.authentication="simple" security.search.user.dn="CN=Administrator, CN=Users,DC=LDAPTesting,DC=local" security.search.user.credentials="openpages" base.dn="CN=Users,DC=LDAPTesting,DC=local" user.attr.id="sAMAccountName" ; };

to: OpenpagesAD { com.openpages.aurora.service.security.namespace.LDAPLoginModule required debug=false provider.url="ldap://192.168.0.165:389" security.authentication="simple" security.search.user.dn="CN=Administrator, CN=Users,DC=LDAPTesting,DC=local" security.search.user.credentials="openpages" base.dn="CN=Users,DC=LDAPTesting,DC=local" user.attr.id="sAMAccountName" ; };

7. Save and close the file.



• • • • • • • • • •Tailoring CommandCenter

Creating the Reporting Schema and FrameworkThis task is required.

IMPORTANT! If you are using CommandCenter in a horizontal cluster environment, there are certain post-installation steps you must complete before enabling the default reports. See the Load Balancing chapter for instructions.

To enable the default CommandCenter reports, you must first create a reporting schema and then update the reporting framework from the OpenPages application.

Steps:

1. Navigate to the following URL in an Internet Explorer browser:

http://<openpages_server>:<port>/openpages

Where: <openpages_server> is the name or address of the machine hosting the OpenPages application, and <port> is the server port. For information on viewing port assignments see “Port Assignments and Servers List” on page 44.

2. Log on to the OpenPages application interface as a user with administrative privileges.3. If you have not created a reporting schema in OpenPages, perform the following steps:

a. From the top of any page in the application, click the System Admin Mode link to switch from Disabled to Enabled to activate System Administration Mode (SAM).

b. From the menu bar, click Administration and select Reporting Schema.c. Click Create Reporting Schema to create the reporting schema.d. After the create operation finishes, click the System Admin Mode to switch from

Enabled to Disabled to de-activate SAM.4. From the menu bar, click Administration | Reporting Framework | Generation.

5. On the Reporting Framework Operations page, click Update. 6. In the Reporting Framework Generation window, do the following:

a. Under Framework Generation, select the Framework Model and Labels options (and any additional options you want) for generation in the Reporting Framework V6 relational data model.

b. Click Submit to begin the update procedure.

You are returned to the Reporting Framework Operations page with the new task listed in the Reporting Framework Operations table.

7. To view the progress of the update, click Refresh. The Percent Complete column on the Reporting Framework Operations table will update the percentage of completion.

When complete (which can take 30 minutes or more), the reporting framework is updated.



Changing the CommandCenter Host and Port Settings This task is required.

Use the following steps to modify the CommandCenter server name and port settings.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges.2. Open an Internet browser window and navigate to the OpenPages application:


3. Log in to the OpenPages application as a user with administrative privileges. 4. Perform the following steps:

a. Under Administration, select Settings.b. Expand the OpenPages | Platform | Reporting Schema | Object URL

Generator folder hierarchy.c. Click the Host setting to open its detail page.d. In the Value field, update the setting to point to the OpenPages server.

IMPORTANT! If you will be using this CommandCenter installation in a load-balanced environment, type the fully-qualified domain name of the server used for load balancing OpenPages. You may also need to change the port.

5. Stop OpenPages services. (for details, see “Starting and Stopping OpenPages” for details on the proper way to shut down OpenPages services.)

6. On the application server, navigate to the <OP_Home>\aurora\conf directory.7. Open the aurora.properties file in a text editor and do the following:

a. Change the cognos.framework.refresh.servlet=http\://localhost\:8080/crf-refresher property strings to replace localhost\:8080 with the reporting server name and port number, for example:

cognos.framework.refresh.servlet=http\://ccserver\:8080/crf-refresher

b. Change the cognos.server=http\://localhost:80/cognos8/cgi-bin/cognos.cgi property strings to replace localhost:80 with the reporting server name and port number, for example:

cognos.server=http\://ccserver:80/cognos8/cgi-bin/cognos.cgi

c. To the logout.url.cognos= property, add the following value:Windowshttp\://<CommandCenter-server-name>\: <CommandCenter-port>/cognos8/cgi-bincognos.cgi? b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

AIXhttp\://<CommandCenter-server-name>\: <CommandCenter-port>/cognos8\cgibin\cognos.cgi? b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

Where: <CommandCenter-server-name> is the CommandCenter server.<CommandCenter-port> is the port number the CommandCenter service listens on.

Examples

logout.url.cognos=http\://ccserver\:8080/cognos8/cgi-bincognos.cgi? b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

8. Save your changes and exit the editor.



Securing Access to the CommandCenter PortalThis task is optional.

You can restrict which user groups are allowed to modify CommandCenter reports.

Use the following instructions to allow a group, in this example the OPAdministrators group, to update, add, and delete reports, and to restrict other users from changing settings within the CommandCenter portal.

Note: OpenPages standard (out-of-the-box) reports could be overwritten during an upgrade. If you want to modify OpenPages standard reports, we strongly recommend that you copy the reports to your own folder structure where you can then modify and control access to these reports.

Task 1: Create a CommandCenter Group in OpenPages with Administrator Permissions

Steps:

1. From a browser window, log on to the OpenPages application user interface as a user with administrative privileges.

2. Create a group in the OpenPages application to which you want to give CommandCenter administrative rights or use an existing group (such as, ‘OPAdministrators’).

Note: For information on creating groups, see the “Creating a New Organizational Group” section in the IBM OpenPages GRC Platform Administrators Guide.

Task 2: Restrict User Access to Administrative Functions Within the Cognos PortalSteps:

1. From a browser window, log on to the CommandCenter portal as a user with administrative privileges (for example, OpenPagesAdministrator)

By default, the URL is:

http://localhost/cognos8 (if you are using port 80 for CommandCenter)

2. Launch the IBM Cognos Administration page:• If the CommandCenter splash page appears, click the Administer IBM Cognos

Content link. • If the IBM Cognos Connection page appears, click Launch then select IBM Cognos

Administration.3. On the Security tab, click the Cognos link in the Directory list.4. On the Directory > Cognos page:

a. Locate the ‘System Administrators’ group in the list.b. Click the More link in the same row as the System Administrators group.

5. Under Available Actions on the Perform an Action page, click the Set members link.

6. On the Members tab of the Set Properties page, click the Add link.7. On the Select entries (Navigate) page, do the following:

a. Click the OpenPagesSecurityRealm link to find the OpenPages group or role to access CommandCenter administrative functions.

b. Select a group. For example, OPAdministrators.c. Click the green arrow to add the role and then click OK.



8. On the Members tab of the Set Properties page, remove the ‘Everyone’ group from accessing the administrative functions as follows:a. Select the ‘Everyone’ group.b. Click the Remove link.

Note: There is no confirmation prompt.

c. Click OK to save your changes.

Task 3: Restrict Access to OpenPages Reports in Public FoldersSteps:

1. On the IBM Cognos Connection page, click the Public Folders tab.2. On the Public Folders page, click the More link in the same row as the OpenPages

folder for which you want to restrict access (for example, OPENPAGES_REPORTS_V6).3. Under Available actions, click the Set properties link.4. On the Set properties page, select the Permissions tab and do the following:

a. If not already selected, select the box to ‘Override the access permissions acquired from the parent entry.'

b. Click the Add link (located near the bottom of the page).5. In the Select entries (Navigate) window, click the Cognos link, and do the following:

a. Select the group to be added (for example, System Administrators).b. Click the green arrow to add the role.c. When finished, click OK.

6. On the Permissions tab of the Set Properties page, do the following:a. Select the box next to the newly added group (for example, System

Administrators).b. Grant the group Read, Write, Set Policy, and Traverse permissions.c. Remove the Write and Set Policy permissions from the other groups.d. Click OK to save your changes.

Now, if a user logs on to CommandCenter with a user name that is not in, for example, the OPAdministrator group, and the user tries to delete, change, or save a report, for example, in the OPENPAGES_REPORTS_V6 package, an error message is displayed to the user.

7. Continue to the next task.

Task 4: Restrict End Users From Running Report Studio and Query Studio but Still Run OpenPages Reports

Follow the steps in this task to restrict user access from within the Cognos portal to run Report Studio and Query Studio tools to modify CommandCenter reports.

Steps:

1. If not already logged on to the CommandCenter portal, log on to the CommandCenter portal as a user with administrative privileges (for example, OpenPagesAdministrator) and launch the IBM Cognos Administration page:• If the CommandCenter splash page appears, click the Administer IBM Cognos

Content link. • If the IBM Cognos Connection page appears, click Launch then select IBM Cognos

Administration.2. Select the Security tab, and click the Cognos link in the Directory list.3. On the Directory > Cognos page, click the More link in the same row as the ‘Authors’

role.4. On the Perform an action page, under Available Actions, click the Set members

link.5. On the Members tab of the Set properties page, click the Add link.



6. On the Select entries (Navigate) page, do the following:a. Click the OpenPagesSecurityRealm link.b. Select the group you want (for example, OPAdministrators).c. Click the green arrow to add the group and then click OK.

7. On the Members tab of the Set Properties page:a. Select the Everyone group b. Click Remove.c. Click OK to save the changes.

8. Repeat Steps 2 - 6 for the Query User role.9. When finished, return to the IBM Cognos Administration page and select the

Security tab.10. On the Security tab, click the Capabilities link, and do the following:

a. Click the Report Studio link. b. Click the Actions arrow next to HTML Items in Report and select Set

properties.11. On the Set properties - HTML Items in Report page, do the following:

a. Select the Permissions tab.b. If not already selected, select the box to Override the access permissions

acquired from the parent entry.' 12. In the list on the Permissions tab, select the Everyone group and grant the group

Execute and Traverse permissions. Click OK to save the changes.

Note: If the Everyone group is not listed, then add it to the list as follows:

a. Click the Add link.b. On the Select entries (Navigate) window, click the Cognos link.c. Select the Everyone group.d. Click the green arrow to add the role.e. When finished, click OK. f. Select the Everyone group and grant the group Execute and Traverse

permissions.g. Click OK to save the changes.

13. Return to the Security tab and do the following:a. Click the Capabilities link again.b. Click the Report Studio link. c. Click the Actions arrow next to Create/Delete and select Set properties.

14. On the Set properties - Create/Delete page, do the following: a. Select the Permissions tab.b. If not already selected, select the box to ‘Override the access permissions acquired

from the parent entry.'c. Remove the ‘Everyone’ group, if it is listed there.d. Add the ‘System Administrators’ group with Read, Write, Set Policy, and Traverse

permissions.e. Click OK to save the changes.

After making the changes defined in this section, when a user logs on to CommandCenter, unless the user is a member of a group with proper authorization, the user cannot modify reports but can still run out-of-the-box reports.



• • • • • • • • • •Starting OpenPages

After the post-installation tasks are complete, you can start the OpenPages services and access the OpenPages application using a web browser.

See Chapter 9 “Starting and Stopping OpenPages” on page 167 for important information on starting OpenPages.

IMPORTANT!

You must start the OpenPagesAdminServer service (Windows) or run the OpenPages startManager script (AIX) first and then the other services/scripts as described in the following procedures.

If you are running OpenPages in a load-balanced environment, you must start the server on the cluster administrator first before starting any cluster members.



• • • • • • • • • •Accessing OpenPages

Accessing OpenPages Using a Web BrowserTo view the application login screen for your OpenPages installation (using the default settings in the installation procedure), type the following URL into an Internet Explorer browser:


Where: <openpages_server> is the name or address of the machine hosting the OpenPages application, and port is the server port. For information on viewing port assignments see “Port Assignments and Servers List” on page 44.

Accessing OpenPages Using an SSL Connection To access the OpenPages application using an SSL connection, you must have an SSL digital certificate in order to use SSL with OpenPages. Refer to Appendix C “Configuring SSL” on page 245 for information on configuring SSL.

Once configured, type the following URL into your Web browser:

https://<openpages_server>:<port>/openpages

Where: <openpages_server> is the name or address of the machine hosting the OpenPages application, and port is the server SSL port.

Note: The port number shown above is the default value for a secondary application server SSL port. If you supplied different values during the installation, use them instead.



• • • • • • • • • •Validating the Installation

After installing the OpenPages application, use the following checklist to validate that the installation is working as expected. These validation tasks should be performed whether the installation was successful or not.

Table 8-3: Post-Installation Validation Checklist

Task Guidance

1. Review all installation logs for errors. For all log file locations and names, see “About Log Files” on page 47.

2. Verify that a backup copy of the system was made after installing.

If a backup was not performed, create a backup of your system by executing the OPBackup command from <drive>:\openpages\aurora\bin.

Verify that a ZIP file was created with the correct timestamp as part of the file name. The file can be found in the <OP_Home>\openpages-backup-restore directory (default folder).

For details on using the Backup utility, see the IBM OpenPages GRC Platform Administrators Guide.

3. Confirm that the Framework Manager service is started.

For details see, “Starting the OpenPages Framework Model Generator Service” on page 136.

4. Confirm that the Reporting Schema and Framework generated successfully.

For details see, “Creating the Reporting Schema and Framework” on page 157.

5. Confirm that base reports are functioning as expected.

Log on to the OpenPages application and run the ‘All Documentation' CommandCenter report.

6. If SSO was enabled, validate that user accounts can access the environment.

Test the logon by logging on to the OpenPages application with an SSO user account.

7. Confirm that sample attachments can be uploaded and downloaded.

Log on to the OpenPages application and upload and download a file attachment to an object.

8. Verify that links in reports reference the correct server address and use the proper web URL parameters.

Execute a report that lists OpenPages object data via links. Select a link and confirm that the target object is rendered successfully in the OpenPages interface.

9. For clustered environments - Validate that all servers can upload and download attachments.

Test upload and download of files from both primary and secondary application servers.

10. For Load-balanced environments - Confirm backup scheduling, ensuring that services on secondary servers are stopped prior to primary server backup, and that services are started post 7001 (port) availability on the primary server.

Verify backup scheduling and process times on both primary and secondary servers.

11. Validate that the CommandCenter portal can be accessed.

Access http://<server_name>/cognos8 (by default) from a client system and confirm logon to the portal.

12. Confirm that the script enable-session-sleep.sql was run.

For details, see “Improving Concurrency” on page 147.



13. After a backup is taken, confirm that object data can be created.

Log on to the OpenPages application and create sample Entity, Process, and Risk objects. These sample objects should subsequently be deleted, or the backup used to restore object data.

Table 8-3: Post-Installation Validation Checklist (Continued)

Task Guidance



Applying the IBM OpenPages GRC

• • • • • • • • • •Platform 6.0.1.1 Patch


The IBM OpenPages GRC Platform 6.0.1.1 patch is part of the 6.0.1 release.

Once you have installed the IBM OpenPages GRC Platform 6.0.1 product, you must apply the 6.0.1.1 patch.




9
Starting and Stopping OpenPages
This section discusses how and when to start and stop the IBM OpenPages GRC Platform servers using Windows services or AIX scripts.


Starting and Stopping OpenPages Application Servers on page 168 Starting and Stopping OpenPages Application Servers on page 168 Starting and Stopping the Database Server on page 177 Starting and Stopping CommandCenter on page 179


Starting and Stopping OpenPages

• • • • • • • • • •Application Servers

About Services and Scripts Used by the OpenPages ApplicationThe OpenPages application runs only if all of the services are started and all of the services for all supporting applications are running.

About Windows ServicesThe following table lists Windows services associated with the OpenPages application and workflow servers.

Table 9-1: OpenPages and Fujitsu Interstage BPM Services on Windows

Service Name Description

OpenPagesAdminServer Starts or stops the OpenPages Admin service.

Note: In a horizontal-cluster environment, cluster members do not have an OpenPages Admin service.

OpenPagesServer# Starts or stops an OpenPages managed server.

Where: # represents the number of the managed server.In a cluster environment, the number for each managed server increments by one.

InterstageBPMAdminServer Starts or stops the Fujitsu Interstage BPM Deployment Manager service.

InterstageBPMCS# Starts or stops the Fujitsu Interstage BPM application server.

Where: # represents the number of the managed server. In a cluster environment, the number for each managed server increments by one.

Chapter 9: Starting and Stopping OpenPages


About AIX ScriptsIn the AIX environment, OpenPages includes a number of scripts to initiate and launch the OpenPages application environment.

Note: These scripts can be run individually or you can use wrapper scripts to start and stop OpenPages.

The following table lists the scripts required to start and stop the OpenPages application.

Table 9-2: OpenPages and Fujitsu Interstage BPM Scripts on AIX

Script Name Description

Fujitsu Interstage BPM:

startManager.sh Starts the Fujitsu Interstage BPM Deployment Manager.

startNode.sh Starts the Fujitsu Interstage BPM node agent.

startServer.sh Starts the Fujitsu Interstage BPM application server.

stopManager.sh Stops the Fujitsu Interstage BPM Deployment Manager.

stopNode.sh Stops the Fujitsu Interstage BPM node agent.

stopServer.sh Stops the Fujitsu Interstage BPM application server.

OpenPages Application:

startManager.sh Starts the OpenPages Deployment Manager.

startNode.sh Starts the OpenPages node agent.

startServer.sh Starts the OpenPages application server.

stopManager.sh Stops the OpenPages Deployment Manager.

stopNode.sh Stops the OpenPages node agent.

stopServer.sh Stops the OpenPages application server.

Scripts for Both Applications:

startAllServers.sh Starts all OpenPages and Fujitsu Interstage BPM services in the correct sequence.

stopAllServers.sh Stops all OpenPages and Fujitsu Interstage BPM services in the correct sequence.



About Starting Application Servers This section describes how to start the OpenPages application in both a Windows and AIX environment.

In a Windows environment, the services required to start the OpenPages application servers can be configured to start automatically.

In an AIX environment, you need to manually run scripts to start the OpenPages application servers.

IMPORTANT!

You must start the OpenPagesAdminServer service (Windows) or run the OpenPages startManager script (AIX) first and then the other services/scripts as described in the following procedures.

If you are running OpenPages in a load-balanced environment, you must start the server on the cluster administrator first before starting any cluster members.

About First Time Start UpThe first time you start the OpenPages server, it must precompile all of the included JSPs. This initialization process of the environment can take up to several minutes to complete. This only applies to the very first time OpenPages starts after installation. Future startups take much less time.

Determining Application ReadinessTo determine whether the application is ready to be accessed after starting up servers, do the following.

Steps:

1. Open the log file specified in the following table.

Where:

<OP_Home> represents the installation location of the OpenPages application.

<host_name> is the name of the server.

<#> is the number of the server.

2. Scroll to the bottom of the log file and look for a message stating that the web application server is “running in Production Mode”. If this line appears, the server is running in production mode and the application is ready to be accessed.

If this... Navigate to this folder... View this log file...

Windows <OP_Home>\OpenPagesDomain\servers\<host_name>-OpenPagesServer1\logs

<host_name>-OpenPagesServer<#>.log

AIX <OP_Home>/profiles/OpenPagesDmgr/logs/dmgr

startServer.log



Starting OpenPages in a Windows EnvironmentIn a Windows environment, all OpenPages and Fujitsu Interstage BPM services can be configured to start automatically or you can start the services manually, as described in this section.

If you need to start or restart the OpenPages application, you must start the services or scripts in the proper sequence using one of the following three methods.

Automatically Starting OpenPages Application Servers


By default, all OpenPages and Fujitsu Interstage BPM services are configured as Manual, (will not start upon reboot).

You can configure all OpenPages and Fujitsu Interstage BPM services to Automatic through Windows Services to start upon booting, or use scripts on each server to start the services upon reboot.

When you reboot the server, all OpenPages and Fujitsu Interstage BPM services will start.

Starting All OpenPages Application Services Using a Script


The StartAllServers.cmd script included with OpenPages will start all OpenPages and Fujitsu Interstage BPM services in the proper sequence.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Open a Command Prompt window (using the Run as Administrator option) and do

the following: a. Navigate to the <OP_Home>\bin directory.

Where: <OP_Home> is the installation location of the OpenPages application. By default, this is: c:\OpenPages.

b. Run the following command to start the OpenPages and Fujitsu Interstage BPM services:

StartAllServers.cmd

When all services have been started, the Command Prompt window closes.

Starting OpenPages Application Services Individually Using Windows Services


In the Windows environment you start the OpenPages application by starting the required OpenPages and Fujitsu Interstage BPM services.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Click the Windows Start menu and select All Programs.3. From the Administrative Tools list, select Services.4. Start the OpenPagesAdminServer service, if present.

Note: A cluster member does not run the OpenPagesAdminServer service.



5. Start the OpenPagesServer# service. Where: # represents the number of the managed server.

Note: If there is more than one managed server on the current system, you must start the service (OpenPagesServer#) for each managed server in sequence before proceeding to the Fujitsu Interstage BPM services.

6. Start the InterstageBPMAdminServer service, if present.

Note: A cluster member does not run the InterstageBPMAdminServer service.

7. Start the InterstageBPMCS# service. Where: # represents the number of the managed server.

As services are starting, Windows Services may indicate that the services have started, but background OpenPages processes may still be running. It may take a few minutes for the OpenPages service to be operational.

Starting OpenPages in an AIX EnvironmentIn AIX, all OpenPages and Fujitsu Interstage BPM services can be started using a single script or you can start the services manually, as described in this section.

Starting All OpenPages Application Servers Using a Script


The startAllServers.sh script included with OpenPages will start all OpenPages and Fujitsu Interstage BPM services in the proper sequence.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Open an AIX shell window and do the following:

a. Navigate to the <OP_Home>/bin directory.

Where: <OP_Home> is the installation location of the OpenPages application. By default, this is: /opt/OpenPages.

b. Run the following script to start the OpenPages and Fujitsu Interstage BPM services:

./startAllServers.sh

Starting OpenPages Application Servers Individually Using Scripts


Use the following steps to start the OpenPages and Fujitsu Interstage BPM services manually. In the AIX environment, you run a set of scripts to start the OpenPages application.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Use an AIX shell to navigate to the <OP_Home>/profiles/OpenPagesDmgr/bin

directory.3. Enter the following command to launch a script that starts the OpenPages Deployment

Manager:

./startManager.sh

4. After the script completes successfully, navigate to the <OP_Home>/profiles/OpenPagesNode1/bin directory.



5. Enter the following commands, in the order specified, to launch scripts that start the OpenPages Node Agent and the OpenPages application server:

./startNode.sh

./startServer.sh OPNode#Server#

Where: OPNode# is the node that the current server is in and Server# is the number of the server within that node. Example: OPNode1Server1.

Note: If there is more than one managed server on the current system, you must run the start script (./startServer.sh OPNode#Server#) for each managed server in sequence before proceeding to the Fujitsu Interstage BPM scripts.

6. After the script completes successfully, navigate to the {app_server_root}/Profiles/IBPMDmgr/bin directory.

7. Enter the following command to launch a script that starts the IBPM Deployment Manager:

./startManager.sh

8. After the script completes successfully, navigate to the {app_server_root}/profiles/IBPMNode1/bin directory.

9. Enter the following commands, in the order specified, to launch scripts that start the IBPM Node Agent and the IBPM application server:

./startNode.sh

./startServer.sh IBPMNode#server

Where: IBPMNode# is the node that the current server is in. Do not specify a server number as only one server should exist for each Fujitsu Interstage BPM node. Example: IBPMNode1server.

When the scripts complete successfully, the OpenPages application is properly started.



About Stopping Application ServersThis section describes how to stop the OpenPages application server in both the Windows and AIX environment.

Stopping the application server prevents the OpenPages application from being accessed.

IMPORTANT!

You must stop the InterstageBPMCS# service(s) (Windows) or run the Fujitsu Interstage BPM stopServer.sh script (AIX) first and then the other services or scripts as described in the following procedures. Otherwise, you risk losing data or corrupting the installation.

If you are running OpenPages in a load-balanced environment, you must stop the server on each cluster member first before stopping the cluster administrator.

Stopping OpenPages in a Windows EnvironmentIn a Windows environment, all OpenPages and Fujitsu Interstage BPM services can be configured to stop automatically or you can stop the services manually, using one of the following three methods.

Automatically Stopping OpenPages Application Servers


Windows automatically and gracefully stops the OpenPages application when a server shuts down.

Stopping All OpenPages Application Services Using a Script


The StopAllServers.cmd script included with OpenPages will stop all OpenPages and Fujitsu Interstage BPM services in the proper sequence.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option). 3. Navigate to the <OpenPages_Home>/bin directory.4. Enter the following command to launch a script that starts the OpenPages and Fujitsu

Interstage BPM services:

StopAllServers.cmd

When all services have been stopped, the Command Prompt window closes.

Stopping OpenPages Application Services Individually Using Windows Services


You can stop the OpenPages application without shutting down or rebooting the machine. Use the following steps to stop OpenPages services manually.

IMPORTANT! Stopping the OpenPages Admin service before stopping each managed server will cause the OpenPages application to stop on all servers. This could result in the loss of data and other problems.

In the Windows environment, you stop the OpenPages application by stopping the required OpenPages and Fujitsu Interstage BPM services.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Click the Windows Start menu and select All Programs.



3. From the Administrative Tools list, select Services.4. Stop the InterstageBPMCS# service.

Where: # represents the number of the managed server.5. Stop the InterstageBPMAdminServer service, if present.

Note: A cluster member machine does not run the InterstageBPMAdminServer service.

6. Stop the OpenPagesServer# service. Where: # represents the number of the managed server.

Note: If there is more than one managed server on the current system, you must stop the service (OpenPagesServer#) for each managed server before stopping the OpenPagesAdminServer service. The managed servers can be stopped in any order.

7. Stop the OpenPagesAdminServer service, if present.

Note: A cluster member machine does not run the OpenPagesAdminServer service.

When the services are stopped successfully, the OpenPages application is properly shut down.

Stopping OpenPages in an AIX EnvironmentIn an AIX environment, all OpenPages and Fujitsu Interstage BPM services can be stopped using a single script or you can stop the services manually, as described in this section.

Stopping All OpenPages Application Servers Using a Script


The stopAllServers.sh script included with OpenPages will stop all OpenPages and Fujitsu Interstage BPM services in the proper sequence.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Use an AIX shell to navigate to the <OpenPages_Home>/bin directory.3. Enter the following command to launch a script that starts the OpenPages and Fujitsu

Interstage BPM services:

./stopAllServers.sh

Stopping OpenPages Application Servers Individually Using Scripts


In the AIX environment, you run a set of scripts to stop the OpenPages application.

Steps:

1. Log on to the OpenPages application server as a user with administrative privileges.2. Navigate to the {app_server_root}/profiles/IBPMNode1/bin directory.3. Enter the following commands, in the order specified, to launch scripts that stop the

IBPM application server and the IBPM Node Agent.

./stopServer.sh IBPMNode#Server

./stopNode.sh

Where: # is the node number that the current server is in. A server number is not required as only one server should exist for each Fujitsu Interstage BPM node.

4. After the scripts complete successfully, navigate to the {app_server_root}/profiles/IBPMDmgr/bin directory.



5. Enter the following command to launch a script that stops the IBPM Deployment Manager:

./stopManager.sh

6. After the script completes successfully, navigate to the <OpenPages_Home>/profiles/OpenPagesNode1/bin directory.

7. Enter the following commands, in the order specified, to launch a script that stops the OpenPages application server and the OpenPages Node Agent.

./stopServer.sh OPNode#server#

./stopNode.sh

Where: OPNode# is the node that the current server is in and Server# is the number of the server within that node. Example: OPNode1Server1.

If there is more than one managed server on the current system, you must run the stop server script (./stopServer.sh OPNode#server#) for each managed server before running the stop node agent script (./stopNode.sh). The managed servers can be stopped in any order.

8. After the scripts complete successfully, navigate to the <OpenPages_Home>/profiles/OpenPagesDmgr/bin directory.

9. Enter the following command to launch a script that stops the OpenPages Deployment Manager:

./stopManager.sh

When the script completes successfully, the OpenPages application is properly shut down.



Starting and Stopping the Database

• • • • • • • • • •Server

This section describes how to stop, start or restart the database server in both the Windows and AIX environment.

About Services and Scripts Used by the Oracle DatabaseThe Oracle database instance can be started or stopped using Windows services or an OpenPages script.

About Windows ServicesThe following table lists Windows services associated with the Oracle database instance.

About AIX ScriptsIn the AIX environment, OpenPages includes the ./oprepository.sh script to initiate and launch the OpenPages Oracle database instance.

Starting and Stopping the Database Server in a Windows EnvironmentThe information in this topic applies only to Windows environments.

Use the following steps to start or stop database services using Windows Services.

Steps:

1. Log on to the database server as a user with administrative privileges.2. Click the Windows Start menu and select All Programs.3. From the Administrative Tools list, select Services.4. For each database service listed in the above table, do the following:

Table 9-3: OpenPages Oracle Services on Windows


OracleOPXRepos_server112_se_x64TNS ListenerOPX600011GEMx64se

Runs the Oracle Database listener service, which connects the user to the Oracle Database instance.

OracleService<SID> Used to start and stop the Oracle Database instance.

Where: <SID> represents the database instance identifier.

If you want to... Then do this...

Start the server Right-click the service name and select Start.

Stop the server Right-click the service name and select Stop.



Starting and Stopping the Database Server in an AIX EnvironmentThe information in this topic applies only to AIX environments.

Steps:

1. Log on to the database server as a user with administrative privileges.2. In a shell window, navigate to the following directory:

<Oracle_Home>/openpages_data/repository/server112_se_x64/software

Where:

<Oracle_Home> is the installation location of the Oracle database directory. By default, this is /opt/oracle.

3. Execute the following command:

./oprepository.sh <tnsalias_name> <listener_name> <sysdba_password> <argument_value>

Where:

<tnsalias_name> is the TNS alias of the database service.

<listener_name> is the listener service.

<sysdba_password> is the password for the database sys user.

<argument_value> is the argument value that is passed to the database server.

Valid argument values are:

start shutdown abort restart

Example

The following example starts the database server.

./oprepository.sh AIX61 OPX61GEM openpages start



• • • • • • • • • •Starting and Stopping CommandCenter

This section describes how to start or stop the CommandCenter server and the OpenPages Framework Model Generator service in both the Windows and AIX environments. Use any of the following methods.

Note that the IBM Cognos Configuration tool will display the status of the start-up, which can be helpful with troubleshooting, if necessary.

About Services and Scripts Used by CommandCenterCommandCenter can be started or stopped using Windows services or an OpenPages script.

About Windows ServicesThe following table lists Windows services associated with CommandCenter.

About AIX ScriptsIn the AIX environment, CommandCenter can be started or stopped using a ./startup.sh or ./shutdown.sh script.

Starting and Stopping the CommandCenter Server Use one of the following procedures, as appropriate, to start or stop the CommandCenter server.

Using the IBM Cognos Configuration Tool to Start and Stop the CommandCenter Server

This task applies to Windows and AIX environments.

Use the following steps to start the CommandCenter service.

IMPORTANT! If you are running CommandCenter in a load-balanced environment, you must stop the CommandCenter service on all secondary CommandCenter servers before stopping the CommandCenter service on the primary CommandCenter server. Otherwise, you risk losing data or corrupting the installation.

Steps:

1. Log on to the reporting server as a user with administrative privileges.2. Start the IBM Cognos Configuration tool as follows:

a. Open a Command Prompt window (using the Run as Administrator option) or AIX shell and navigate to the <Cognos_Home>|bin64 or <Cognos_Home>|bin directory.

Table 9-4: OpenPages CommandCenter Services on Windows


CommandCenter Runs the IBM Cognos service.

OpenPages Framework Model Generator Runs the service that generates the reporting framework in IBM Cognos.

Where: <Cognos_Home> represents the installation location of the Cognos application. By default, this is:



b. Execute one of the following commands to open the tool:

3. Do one of the following:

Using the Windows Operating System to Start and Stop CommandCenterUse the following steps to start or stop the CommandCenter service in a Windows environment using Windows Services.

Steps:

1. Log on to the reporting server as a user with administrative privileges.2. Click the Windows Start menu and select All Programs.3. From the Administrative Tools list, select Services.4. Do one of the following:

Using the AIX Operating System to Start and Stop CommandCenterUse the following steps to start or stop the CommandCenter server in an AIX environment using command-line scripts.

Steps:

1. Log on to the reporting server as a non-root user with administrative privileges.2. Launch an AIX shell and navigate to the bin directory as follows:

<Cognos_Home>/bin

Where: <Cognos_Home> is the installation location of the Cognos application. By default, this is: /opt/OpenPages/Cognos/cognos/cognos8/configuration


Windows C:\OpenPages\Cognos\cognos\c8

AIX /opt/OpenPages/Cognos/cognos/cognos8

Windows cogconfig.bat

AIX ./cogconfig.sh

To do this... Then...

Start the server Click Actions | Start. (It may take several minutes for the service to start the first time.) If the Start option is not available, the server has already started.

Note: The start-up may pause if you have not configured a mail server. Click OK in the dialog box that displays, then click Continue.

Stop the server Click Actions | Stop.


Start the server Right-click the CommandCenter service and select Start.

Stop the server Right-click the CommandCenter service and select Stop.


Start the server Enter the following command: ./startup.sh

Stop the server Enter the following command: ./shutdown.sh



Starting or Stopping the OpenPages Framework Model Generator ServiceUse one of the following procedures, as appropriate for your operating system, to start or stop the OpenPages Framework Model Generator Service.

Using the Windows Operating System to Start and Stop the Framework Model Generator

Use the following steps to start or stop the Framework Model Generator Service in a Windows environment using Windows Services.

Steps:

1. Log on to the reporting server as a user with administrative privileges.2. Click the Windows Start menu and select All Programs.3. From the Administrative Tools list, select Services.4. Do one of the following:

Using the AIX Operating System to Start and Stop the Framework Model GeneratorUse the following steps to start or stop the Framework Model Generator Service in an AIX environment using command-line scripts.

Steps:

1. Log on to the reporting server as a non-root user with administrative privileges.2. Open an AIX shell as a user with administrative privileges and navigate to the following

directory:

<CommandCenter_Home>/apache-tomcat-6.0.26/bin -- or --

<CommandCenter_Home>/apache-tomcat/bin

Where <CommandCenter_Home> is the installation location of the CommandCenter. By default, this is: /opt/OpenPages/CommandCenter.



Start the server Right-click the OpenPages Framework Model Generator service and select Start.

Stop the server Right-click the OpenPages Framework Model Generator service and select Stop.


Start the server Enter the following command: ./startup.sh

Stop the server Enter the following command: ./shutdown.sh



10
Uninstalling OpenPages
This chapter contains instructions for uninstalling all, or parts, of the IBM OpenPages GRC Platform.

Use the OpenPages and CommandCenter uninstaller programs to remove the either OpenPages application and its related software or CommandCenter. For third party software, use the uninstall instructions that came with your kit.


“Removing the OpenPages Application” on page 184 “Removing the Database Software” on page 187 “Removing the Application Server” on page 189 “Removing CommandCenter” on page 190


• • • • • • • • • •Removing the OpenPages Application

To remove the OpenPages application use the following procedure.

IMPORTANT! If you installed the OpenPages application server and/or CommandCenter server on the same machine as the database, then you must first remove the database before removing any server components.

Note: Removing the OpenPages software does not affect the data contained in the Oracle database instance. To erase your OpenPages data, you must delete the contents of the database instance manually using the IBM OpenPages GRC Platform Installer for Repository uninstall program.

After the uninstall process is complete, a number of folders, including the following two folders containing OpenPages data, remain on the application server:

OpenPages storage folder (by default, c:\openpages-storage or opt/OpenPages/openpages-storage)

the OpenPages\logs folder

If you purchased WebLogic Server from OpenPages, WebLogic Server is also removed when you uninstall the OpenPages application.

Uninstalling OpenPages Use the following steps to remove the OpenPages application on each server:

Steps:


Note: For AIX installs, you log in as a non-root user, such as the user you created for the OpenPages installation, such as opuser.

2. Stop all OpenPages servers.3. Uninstall OpenPages as follows:

Windows

a. Open an Explorer window and navigate to the <OP_Home>\OpenPagesUninstall directory.

b. Right-click the OpenPagesUninstall.exe program and select Run as Administrator.

c. Click Yes when prompted to start the uninstall.

AIX

a. Open an AIX shell and navigate to the <OP_Home>/OpenPagesUninstall directory.b. Execute the OpenPagesUninstall command.

4. When the uninstall process is finished, reboot your machine to fully complete the uninstall.

Cleaning Up after the Removal ProcessUninstalling the OpenPages application may not remove all of the files and folder structures that are part of the OpenPages installation. You must manually remove the remaining folders and files, such as the <OP_Home> directory and the openpages-storage directory.

Note: A removal log file, OpenPages_uninstaller.log, is created in the <OP_Home>\logs directory.

Chapter 10: Uninstalling OpenPages


Uninstalling the Workflow ServerThe OpenPagesUninstall.exe application will remove the workflow server during the OpenPages uninstall.

If, for some reason, OpenPages does not fully install, you can use the workflow server uninstall application to remove the workflow server.

Note: If OpenPages does not fully install, you may need to remove the workflow server software before attempting to re-install OpenPages.

Use the following steps to remove the workflow server:

Steps:


Note: For AIX installs, you log in as a non-root user, such as the user you created for the OpenPages installation, such as opuser.

2. Uninstall the workflow server as follows:

Windows

a. Locate the workflow server uninstall program using the Window Start menu, by default: Start | All Programs | Interstage Business Process Manager | Uninstall.

b. Right-click Uninstall and select Run as Administrator.c. Click Yes when prompted to start the uninstall.

AIX

a. Open an AIX shell and navigate to the <Workflow_Home>/_uninst/ directory.


b. Execute the uninstall.sh command.3. When the uninstall process is finished, reboot your machine to fully complete the

uninstall.



Removing the 64-bit Oracle ClientTo remove the OpenPages Client use the following procedure.

If you are running the interactive mode installer on an AIX server, you must run the installer in graphical mode using an application such as X Windows.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as a user with administrative privileges.3. Navigate to the following directory within <ORACLE_HOME>:

openpages_data|repository|ia|client112_ac_X64| UninstallIBM_OpenPages_GRC_Platform\

Examples

Windows

C:\openpages_data\repository\ia\client112_ac_X64\ UninstallIBM_OpenPages_GRC_Platform\

AIX

/opt/oracle/openpages_data/repository/ia/client112_ac_X64/UninstallIBM_OpenPages_GRC_Platform\

4. Uninstall the OpenPages Repository as follows:

Windows

c. Right-click UninstallIBM_OpenPages_GRC_Platform.exe and select Run as Administrator.

d. Click Yes when prompted to start the uninstall.

AIX

a. Launch a graphical mode application such as X Windows.b. Execute the following command:

UninstallIBM_OpenPages_GRC_Platform.bin -home <Oracle_Home>

c. Click Yes when prompted to start the uninstall.5. Follow the uninstaller prompts:

a. Specify the database listeners to de-configure or press Enter to de-configure the listener shown in the prompt.

b. Specify the database names to de-configure or press Enter to de-configure the instance shown in the prompt.

c. Specify the type of database or press Enter to select the database type shown in the prompt.

d. Specify the diagnostic database destination to de-configure or press Enter to de-configure the destination shown in the prompt.

e. Specify the database storage type (ASM or FS) and or press Enter (no default value specified).

f. Review the de-installation summary and press Y to uninstall.6. Reboot your machine to fully complete the uninstall.



• • • • • • • • • •Removing the Database Software

To remove the IBM OpenPages GRC Platform Installer for Repository (including the server software, the listener, and the database instance) use the following procedure.

IMPORTANT! The Installer for Repository uses InstallAnywhere technology. InstallAnywhere places a file on the system for storing IA product data, called .com.zerog.registryl.xml. You need to remove this file before you can uninstall the OpenPages repository.

Uninstallng the Oracle Database SoftwareUse the following steps to uninstall the Oracle Database software.


Steps:

1. Log on to the 6.0.1 database server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as a user with administrative privileges.3. Remove the .com.zerog.registry.xml file

Windows

a. Navigate to the following directory:

C:\Program Files\Zero G Registry

b. Determine if the .com.zerog.registry.xml file is present.c. If present, remove the file. If not present, continue with the uninstall.

AIX

a. Navigate to the user home directory.b. Determine if the .com.zerog.registry.xml file is present.c. If present, remove the file. If not present, navigate to the /var directory.d. Determine if the .com.zerog.registry.xml file is present.e. If present, remove the file. If not present, continue with the uninstall.

4. Navigate to the following directory within <ORACLE_HOME>:

openpages_data|repository|ia|server112_se_X64| UninstallIBM_OpenPages_GRC_Platform\

Examples

Windows

C:\openpages_data\repository\ia\ server112_se_X64\ UninstallIBM_OpenPages_GRC_Platform\

AIX

/opt/oracle/openpages_data/repository/ia/server112_se_X64/UninstallIBM_OpenPages_GRC_Platform\




Windows

a. Right-click UninstallIBM_OpenPages_GRC_Platform.exe and select Run as Administrator.

b. Click Yes when prompted to start the uninstall.

AIX


UUninstallIBM_OpenPages_GRC_Platform.bin -home <Oracle_Home>








Cleaning Up after the Removal ProcessUninstalling the OpenPages application may not remove all of the files and folder structures that are part of the OpenPages installation.

You must manually remove the remaining folders and files, such as the Oracle Central Inventory directory, by default:

Windows

C:\Program Files\Oracle\Inventory

AIX

/home/oracle/oraInventory

Note: A removal log file, OpenPages_uninstaller.log, is created in the <OP_Home>\logs directory.



• • • • • • • • • •Removing the Application Server

OpenPages supports either Oracle WebLogic Server or IBM WebSphere, depending upon the operating system used by the application server machine.

Remove the WebSphereBecause WebSphere was purchased from a third-party vendor, you must manually remove WebSphere from your application server. Use the instructions from the software vendor’s installation kit to remove WebSphere.

Remove the WebLogic ServerWebLogic Server may be purchased from either OpenPages or from a third-party vendor.

If you purchased WebLogic Server from:

OpenPages, Inc. - WebLogic Server is removed when you uninstall the OpenPages application.

Another vendor - WebLogic Server must be manually removed following the instructions in the WebLogic Server user documentation.



• • • • • • • • • •Removing CommandCenter

To remove the CommandCenter and Cognos applications use the following procedures.

IMPORTANT! If you installed the OpenPages application server and/or CommandCenter server on the same machine as the database, then you must first remove the database before removing any server components.

Removing CommandCenterTo use the CommandCenter uninstall program, follow these steps.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Uninstall OpenPages as follows:

Windows

a. Open an Explorer window and navigate to the Uninstall_OpenPages_CommandCenter directory in the CommandCenter installation directory (CC_Home), by default:

OpenPages\CommandCenter\Uninstall_OpenPages_CommandCenter

b. Right-click the Uninstall_OpenPages_6_0_1_0_CommandCenter.exe program and select Run as Administrator.


AIX

a. Open an AIX shell and navigate to the Uninstall_OpenPages_CommandCenter directory in the CommandCenter installation directory (CC_Home), by default:

/opt/OpenPages/CommandCenter/Uninstall_OpenPages_CommandCenter

b. Execute the Uninstall_OpenPages_6_0_1_0_CommandCenter command.3. Reboot your machine to fully complete the uninstall.



Removing the Cognos SoftwareUninstall the Cognos software using the OpenPages Cognos uninstall program, following these steps.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Uninstall OpenPages as follows:

Windows

a. Open an Explorer window and navigate to the Uninstall_OpenPages_CommandCenter directory in the Cognos installation directory, by default:

OpenPages\Cognos\Uninstall_OpenPages_Cognos

b. Right-click the Uninstall_OpenPages_Cognos.exe program and select Run as Administrator.


AIX

a. Open an AIX shell and navigate to the Uninstall_OpenPages_Cognos directory in the Cognos installation directory, by default:

/opt/OpenPages/Cognos/Uninstall_OpenPages_Cognos

b. Execute the Uninstall_OpenPages_Cognos command.3. Reboot your machine to fully complete the uninstall.

Removing the 32-bit Oracle ClientTo remove the OpenPages Client use the following procedure.


Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option) or AIX

shell as a user with administrative privileges.



3. Navigate to the following directory within <ORACLE_HOME>:

openpages_data\repository\ia\client112_ac_X86\ UninstallIBM_OpenPages_GRC_Platform\

Examples

Windows C:\openpages_data\repository\ia\client112_ac_X86\ UninstallIBM_OpenPages_GRC_Platform\

AIX /opt/oracle/openpages_data/repository/ia/client112_ac_X86/UninstallIBM_OpenPages_GRC_Platform\


Windows

c. Right-click UninstallIBM_OpenPages_GRC_Platform.exe and select Run as Administrator.

d. Click Yes when prompted to start the uninstall.

AIX


UninstallIBM_OpenPages_GRC_Platform.bin -home <Oracle_Home>








Cleaning Up after the Removal ProcessUninstalling the CommandCenter and Cognos applications may not remove all of the files and folder structures that are part of the installation. You must manually remove the remaining folders and files, such as home directories and the Java instances used by CommandCenter and Cognos.



Appendices

The following appendices address specific installation scenarios. Consult the following chapters as required:

Appendix A “Adding Cluster Members” on page 195

Refer to this chapter if you need to add additional OpenPages application servers after installing the OpenPages environment.

Appendix B “Configuring Clustered Environments” on page 219

Refer to this chapter for information on configuring OpenPages and CommandCenter in a load-balanced environment.

Appendix C “Configuring SSL” on page 245

Refer to this chapter if you need to integrate OpenPages or CommandCenter into an SSL environment.

Appendix D “Changing Default Port Numbers” on page 283

Refer to this chapter if you need to change the default port numbers used by the IBM OpenPages GRC Platform installer.

Appendix E “Configuring OpenPages on One Machine” on page 305

Refer to this chapter if the all elements of the OpenPages environment (database, OpenPages application, and CommandCenter) are installed on a single server.

Appendix F “Integrating Single Sign-on with OpenPages” on page 307

Refer to this chapter if you need to integrate OpenPages or CommandCenter into an existing single sign-on environment.

Appendix G “Creating the CommandCenter Database Schema” on page 315

Refer to this chapter if you want to configure the CommandCenter database schema (Content Store) manually.

Appendix H “Manually Installing the Application Server” on page 331

Refer to this chapter if you want to install application server software into the IBM OpenPages GRC Platform manually.

Appendix I “Installing the OpenPages Database Schema” on page 339

Refer to this appendix if you want to manually create the OpenPages Database Schema.

Appendix J “Installing Client-Side Applications” on page 349

Refer to this appendix to install the client-side applications that are included in the OpenPages installation kit.

Appendix K “SQL Files” on page 355

Refer to this chapter for information on the SQL scripts used during this installation.


A
Adding Cluster Members
During the IBM OpenPages GRC Platform installation, you had the opportunity to install a single OpenPages admin server and multiple managed servers.

After the OpenPages install is complete, if you need to add additional OpenPages application servers, use the steps in this chapter.


Adding Vertical Cluster Members on page 196 Adding Horizontal Cluster Members on page 218


• • • • • • • • • •Adding Vertical Cluster Members

IMPORTANT! Before you begin the tasks described in this section, it is assumed that you have successfully installed IBM OpenPages GRC Platform 6.0.1.1 or higher and that the temp directory created during the installation still exists

This section describes how to add an OpenPages application and workflow managed server to an existing cluster in the following environments:

WebLogic Server. See “Adding Vertical Cluster Members to an Existing Installation in an Oracle WebLogic Environment” below

WebSphere Application Server. See “Adding Vertical Cluster Members to an Existing Installation in an IBM WebSphere Environment” on page 209

Adding Vertical Cluster Members to an Existing Installation in an Oracle WebLogic Environment

The information in this topic applies only to IBM OpenPages GRC Platform 6.0.1.1 in an Oracle WebLogic environment.

This section describes how to add an OpenPages application and workflow managed server to an existing IBM OpenPages GRC Platform 6.0.1.1 installation running in an Oracle WebLogic environment.

PrerequisiteBefore you begin the tasks described in this section, it is assumed that you have successfully applied the IBM OpenPages GRC Platform 6.0.1.1 patch to your existing 6.0.1 installation and that the temp directory created during the 6.0.1 installation still exists.

Task OverviewThe following tasks outline the process for adding a vertical cluster member:

Task 1: Update Values in the OpenPages Property Files on page 198 Task 2: Update the Oracle WebLogic Administrator Password Value in the OpenPages

Script Files on page 199 Task 3: Create the OpenPages Application Managed Server Instance on page 200 Task 4: Mask Passwords in the OpenPages Script Files on page 201 Task 5: Configure the IBPM Workflow Console on page 201 Task 6: Update Values in the Workflow Properties Files on page 202 Task 7: Update the Oracle WebLogic Administrator Password Value in the Workflow

Script Files on page 204 Task 8: Create the Workflow Managed Server Instance on page 206 Task 9: Mask Passwords in the Workflow Script Files on page 207 Task 10: Update the Start/Stop Server Command Files on page 207 Task 11: Update the Unregister Services Command File and Restart Services on

page 208

IMPORTANT! You must perform all of the tasks in this section for each managed server instance (OpenPages application/workflow server pair) that you want to add.

Appendix A: Adding Cluster Members


About Using Parameters in TasksThe tasks described in this section require that you supply values for certain common parameters. You must enter these parameter values consistently across all of the tasks.

Example

Let’s say a property or code statement requires the name of the machine on which you are adding the cluster member. That value is represented by the <server_name> parameter. If the name of the machine on which you are adding the cluster member is OP_Host, then you must enter OP_Host whenever you are asked to provide the value for <server_name>.

These parameters are summarized in the following table.

Table A-1: Parameters for Adding Cluster Members in Oracle WebLogic

Property Description

<drive>:<Workflow_Home_Path> The drive letter and installation path of the Fujitsu Interstage BPM server.

Default: C:\Fujitsu\InterstageBPM

<admin_host_name> The host name of the administrative server.

<server_name> The host name of the machine on which you are adding the managed server instance.

Example: OP_Host

<server#> The number of the managed server you are adding to the cluster.

Example: If you currently have one managed server on OP_Host, this parameter value would be 2.

<op_admin_port#> The HTTP port number of the OpenPages administrative server.

Example: 7001 (Windows/WebLogic), 9060 (AIX/WebSphere).

<ibpm_admin_port#> The HTTP port number of the workflow administrative server.

Example: 49901 (Windows/WebLogic), 9061 (AIX/WebSphere).

<new_OpenPages_http_port#> The HTTP port number of the managed application server you are adding to the cluster.

Example: If you currently have one managed application server on OP_Host with port number 7009, this parameter value would be 7011.

<new_OpenPages_https_port#> The HTTP secure port number of the managed application server you are adding to the cluster.

Example: If you currently have one managed application server on OP_Host with secure port number 7010, this parameter value would be 7012.

<new_IBPM_http_port#> The HTTP port number of the managed workflow server you are adding to the cluster.

Example: If you currently have one managed workflow server on OP_Host with port number 49951, this parameter value would be 49953.



Task 1: Update Values in the OpenPages Property FilesUse the following instructions to modify and update values in these property files: server.properties and sosa.properties files.

Note: <OP_Home> in the file path represents the installation location of the OpenPages application. The default path for a Windows installation is c:\OpenPages.

Task A: Modify Values in the OpenPages Server Properties File (server.properties)Steps:

1. Navigate to the <OP_Home>\aurora\conf directory and do the following.a. Create a copy of the following property file:

<server_name>-OpenPagesServer1-server.properties

b. Rename the copy of the file to:

<server_name>-OpenPagesServer<server#>-server.properties

2. Open the renamed file in a text editor and do the following:a. Verify that the correct value for <server_name> is used throughout the file.b. Change all occurrences of port number 7009 to the HTTP port number of the

OpenPages managed application server you are adding (for example, 7011).c. Update the parameter values for the following properties:

• workflow.client.props.path=<drive>\:\\<Workflow_Home_Path>\\client\\ server_name>-InterstageBPMCS<server#>-iFlowClient.properties

• url.path.workflow.admin=http\://<server_name>\:<new_IBPM_http_port#>/ibpmconsole

• jms.topic.CacheTopic=<server_name>-OpenPagesServer<server#>-CacheSyncPubTopic

d. When finished, save the file.

Task B: Modify Values in the Sosa Property File (sosa.properties)Steps:

1. In the <OP_Home>\aurora\conf directory, do the following:a. Create a copy of the following property file:

<server_name>-OpenPagesServer1-sosa.properties


<server_name>-OpenPagesServer<server#>-sosa.properties

2. Open the renamed file in a text editor and update the parameter values for the following property:

<new_IBPM_https_port#> The HTTP secure port number of the managed workflow server you are adding to the cluster.

Example: If you currently have one managed workflow server on OP_Host with secure port number 49952, this parameter value would be 49954.

<opworkflow_DB_username> The OpenPages workflow user name for accessing the workflow database.

<opworkflow_DB_password> The OpenPages workflow password for accessing the workflow database.

Table A-1: Parameters for Adding Cluster Members in Oracle WebLogic

Property Description



application.url.path=http\://<server_name>\:<new_OpenPages_http_port#> /openpages

3. When finished, save the file.

Task 2: Update the Oracle WebLogic Administrator Password Value in the OpenPages Script Files

Use the following instructions to update the Oracle WebLogic password value in these script files: create_managed_server.bat, create_op_internal_jms_bridge.bat, and create_op_ibpm_jms_bridges_op.bat files.

Notes

<OP_Home> in the file path represents the installation location of the OpenPages application. The default path for a Windows installation is c:\OpenPages.

The password values that you type will be in plain text. After the member has been added to the cluster, you will have to manually mask these values with asterisks (***). For details, see Task 4 on page 201.

Task A: Modify the Password Value in the ‘create_managed_server.bat’ FileSteps:

1. Navigate to the <OP_Home>\temp\scripts directory.2. Open the create_managed_server.bat file in a text editor of your choice.3. Update the Oracle WebLogic administrator password for the following line in the script:

java weblogic.WLST <OP_Home>\temp\scripts\create_managed_server.py %ADMIN_SERVER_HOSTNAME%:<op_admin_port#> <weblogic_admin_username> <weblogic_admin_password> %SERVER_INSTANCE% <admin_host_name> %SERVER_INSTANCE_PORT% %SERVER_INSTANCE_SECURE_PORT%

Where:

<weblogic_admin_password> is the password of the Oracle WebLogic administrator account.


Task B: Modify the Password Value in the ‘create_op_internal_jms_bridge.bat’ FileSteps:

1. In the <OP_Home>\temp\scripts directory, open the create_op_internal_jms_bridge.bat file in a text editor of your choice.

2. Update the Oracle WebLogic administrator password for the following line in the script:

call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\create_internal_jms_bridge.py %ADMIN_SERVER_HOSTNAME%:<op_admin_port#> <weblogic_admin_username> <weblogic_admin_password> %SERVER_INSTANCE% <admin_host_name> %SERVER_INSTANCE_PORT%

Where:



Task C: Modify the Password Value in the ‘create_op_ibpm_jms_bridges_op.bat’ FileSteps:



1. In the <OP_Home>\temp\scripts directory, open the create_op_ibpm_jms_bridges_op.bat file in a text editor of your choice.


call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\create_op_ibpm_bridge.py %ADMIN_SERVER_HOSTNAME%:<op_admin_port#> <weblogic_admin_username> <weblogic_admin_password> %SERVER_INSTANCE% <admin_host_name> %SERVER_INSTANCE_PORT% %IBPM_INSTANCE_PORT%

Where:



Task 3: Create the OpenPages Application Managed Server InstanceTo create the new OpenPages application managed server instance, use the following steps.

Note: <OP_Home> in the file path represents the installation location of the OpenPages application. The default path for a Windows installation is c:\OpenPages.

Steps:

1. Start the OpenPagesAdminServer service.2. At a Windows command prompt, navigate to the following directory:

<OP_Home>\temp\scripts

3. From the \scripts directory, run the following .bat files with the updated values:a. create_managed_server.bat <server_name>-OpenPagesServer<server#>

<new_OpenPages_http_port#> <new_OpenPages_https_port#> b. create_op_internal_jms_bridge.bat <server_name>-

OpenPagesServer<server#> <new_OpenPages_http_port#> <new_OpenPages_https_port#>

c. create_op_ibpm_jms_bridges_op.bat <server_name>-OpenPagesServer<server#> <new_OpenPages_http_port#> <new_OpenPages_https_port#> <new_IBPM_http_port#>

4. Navigate to the <OP_Home>\bin directory. 5. From the \bin directory, run the following command file to register the OpenPages

services:

RegisterOPWindowsServices.cmd <server_name>-OpenPagesServer<server#> OpenPagesServer<server#> http://<server_name>:<op_admin_port#>



Task 4: Mask Passwords in the OpenPages Script FilesFor security purposes, use the following steps to manually mask the plain text <weblogic_admin_password> that you entered in the OpenPages script files in Task 2 on page 199.

Note: <OP_Home> in the file path represents the installation location of the OpenPages application. The default path for an AIX installation is /opt/OpenPages.

Steps:

1. Navigate to the <OP_Home>\temp\scripts directory.2. Open the following .bat files in a text editor:

• create_managed_server.bat• create_op_internal_jms_bridge.bat• create_op_ibpm_jms_bridges_op.bat

3. For each .bat file, do the following.a. Locate the plain text password value for the <weblogic_admin_password>

parameter in the file.b. Use asterisks (***) to overwrite the plain text password value for the

<weblogic_admin_password> parameter. c. When finished, save the file.

Task 5: Configure the IBPM Workflow Console The create_ibpm_dirs.bat file creates the ibpmconsole directory under the <OP_Home> directory and extracts the contents of ibpmconsole.war into the ibpmconsole directory.

To update and run the .bat file, use the following steps.

Note: <Workflow_Home> in the file path represents the installation location of the Fujitsu Interstage BPM server. The default path for a Windows installation is c:\Fujitsu\InterstageBPM.

Steps:

1. Create the ibpmconsole directory within <OP_Home> as follows: a. Navigate to the <Workflow_Home>\server\deployment directory.b. Extract the contents of ibpmconsole.war to the <OP_Home>\ibpmconsole directory.

2. Navigate to the <OP_Home>\temp\scripts directory.3. Open the create_ibpm_dirs.bat file in a text editor of your choice.4. Modify the following ‘set’ parameters in the file:

a. Before changing the parameters, record the current values of the set count and set srvnum parameters.

b. Change the current values to the following values: • set count=1• set srvnum=<server#> (for example, set srvnum=2)



5. For each ‘copy’ statement in the file that begins with:

copy <OP_Home>\temp\ibpm\

modify the path to include the \patch directory as follows:

copy <OP_Home>\patch\temp\ibpm\

Example

The path in the following ‘copy’ statement in the file would change from:

copy <OP_Home>\temp\ibpm\notify_parent.xsd <Workflow_Home>\console_src\%IBPM_SERVER_PREFIX%%srvnum%\ibpmconsole

to this:

copy <OP_Home>\patch\temp\ibpm\notify_parent.xsd <Workflow_Home>\console_src\%IBPM_SERVER_PREFIX%%srvnum%\ibpmconsole

6. Save the changes to the file. 7. Run the create_ibpm_dirs.bat file.8. Edit the create_ibpm_dirs.bat file to revert the changes made in the second step to

the original values, and save the file.

Task 6: Update Values in the Workflow Properties FilesTo update the ibpm.properties, iFlowClient.properties, console.conf, and server.properties files, use the following steps.

Note: <Workflow_Home> in the file path represents the installation location of the Fujitsu Interstage BPM server. The default path for a Windows installation is c:\Fujitsu\InterstageBPM.

Task A: Modify Values in the IBPM Property File (ibpm.properties) Steps:

1. Navigate to the following directory:

<Workflow_Home>\server\deployment\WLS-Cluster<server_name>- InterstageBPMCS1

2. Copy the ibpm.properties file to:

<Workflow_Home>\server\deployment\WLS-Cluster<server_name>- InterstageBPMCS<server#>

3. Open the copied file in a text editor and do the following:a. Update the parameter values for the following properties:

• ServerLogFile=<drive>\:/<Workflow_Home_Path>/server/instance/default/logs/<server_name>-InterstageBPMCS<server#>.log

• NamingProviderURL=t3\://<server_name>\:<new_IBPM_http_port#>• ServerName=<server_name>-InterstageBPMCS<server#>• ServerBaseURL=http\://<server_name>\:<new_IBPM_http_port#>/

ibpmconsole/• JMSNamingProviderURL=t3\://<server_name>\:<new_IBPM_http_port#>• ServerEmailBaseURL=http\://<server_name>\:<new_IBPM_http_port#>/

ibpmconsole/System/b. When finished, save the file.



Task B: Modify the Import Properties Batch FileSteps:


<Workflow_Home>\server\deployment\WLS-Cluster<server_name>-InterstageBPMCS1

2. Copy the following files:• importProperties.bat • setIBPMEnv.cmd files

into this directory:

<Workflow_Home>\server\deployment\WLS-Cluster<server_name>-InterstageBPMCS<server#>

3. Open the copied setIBPMEnv.cmd file in a text editor and do the following:a. Update the parameter values for the following property:

set SERVERNAME=<server_name>-InterstageBPMCS<server#>

b. When finished, save the file.4. Open the copied importProperties.bat file in a text editor and do the following:

a. Update the parameter values on the following code line:

call <Workflow_Home>\server\deployment\WLS-Cluster<server_name>-InterstageBPMCS<server#>\setIBPMEnv.cmd

b. When finished, save the file.

Task C: Modify Values in the iFlow Client Property File (iFlowClient.properties)Steps:

1. Navigate to the <Workflow_Home>\client directory and do the following:a. Create a copy of the following property file:

<server_name>-InterstageBPMCS1-iFlowClient.properties


<server_name>-InterstageBPMCS<server#>-iFlowClient.properties

2. Open the renamed file in a text editor and do the following:a. Update the parameter values for the following properties:

• JMSNamingProviderURL=t3\://<server_name>\:<new_IBPM_http_port#>• NamingProviderURL=t3\://<server_name>\:<new_IBPM_http_port#>


Task D: Modify Values in the IBPM Console Configuration File (console.conf)Steps:


<Workflow_Home>\console_src\<server_name>-InterstageBPMCS1\ibpmconsole

2. Copy the console.conf file to:

<Workflow_Home>\console_src\<server_name>- InterstageBPMCS<server#>\ibpmconsole



3. Open the console.conf file in a text editor and update the parameter value for the following property:

NamingProviderURL=t3://<server_name>:<new_IBPM_http_port#>


Task E: Modify Values in the Workflow IBPM Server Property File (server.properties)Steps:

1. Navigate to the <OP_Home>\aurora\conf directory and do the following:a. Create a copy of the following property file:

<server_name>-InterstageBPMCS1-server.properties


<server_name>-InterstageBPMCS<server#>-server.properties

2. Open the renamed file in a text editor and do the following:a. Update the parameter values for the following properties:

• workflow.client.props.path=<drive>\:\\<Workflow_Home_Path>\\ InterstageBPM\\client\\ <server_name>-InterstageBPMCS<server#>-iFlowClient.properties

• jms.topic.CacheTopic=<server_name>-InterstageBPMCS<server#>-CacheSyncPubTopic

b. Change all occurrences of the following port numbers:• Replace 7009 with <new_OpenPages_http_port#>• Replace 49951 with <new_IBPM_http_port#>

Task 7: Update the Oracle WebLogic Administrator Password Value in the Workflow Script Files

Use the following instructions to update the Oracle WebLogic password value in these script files: create_ibpm_managed_server.bat, deploy_ibpm_console.bat, create_ibpm_internal_jms_bridge.bat, and create_op_ibpm_jms_bridges_ibpm.bat files.

Notes


The password values that you type will be in plain text. After the member has been added to the cluster, you will have to manually mask these values with asterisks (***). For details, see Task 9 on page 207.

Task A: Modify the Password Value in the ‘create_ibpm_managed_server.bat’ FileSteps:

1. Navigate to the <OP_Home>\temp\scripts directory.2. Open the create_ibpm_managed_server.bat file in a text editor of your choice.




call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\create_ibpm_managed_server.py %SERVER_INSTANCE% %SERVER_INSTANCE_PORT% <Workflow_Home>\IBPMDomain IBPMDomain <weblogic_admin_username> <weblogic_admin_password> %ADMIN_SERVER_HOSTNAME% <ibpm_admin_port#> 1 %SERVER_INSTANCE_SECURE_PORT%

Where:



Task B: Modify the Password Value in the ‘deploy_ibpm_console.bat’ FileSteps:

1. In the <OP_Home>\temp\scripts directory, open the deploy_ibpm_console.bat file in a text editor of your choice.


call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\deploy_ibpm_console_war.py %ADMIN_SERVER_HOSTNAME%:<ibpm_admin_port#> <weblogic_admin_username> <weblogic_admin_password> <Workflow_Home> %SERVER_INSTANCE%

Where:



Task C: Modify the Password Value in the ‘create_ibpm_internal_jms_bridge.bat’ FileSteps:

1. In the <OP_Home>\temp\scripts directory, open the create_ibpm_internal_jms_bridge.bat file in a text editor of your choice.


call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\create_internal_jms_bridge.py %ADMIN_SERVER_HOSTNAME%:<ibpm_admin_port#> <weblogic_admin_username> <weblogic_admin_password> %SERVER_INSTANCE% <server_name> %SERVER_INSTANCE_PORT%

Where:





Task D: Modify the Password Value in the ‘create_op_ibpm_jms_bridges_ibpm.bat’ FileSteps:

1. In the <OP_Home>\temp\scripts directory, open the create_op_ibpm_jms_bridges_ibpm.bat file in a text editor of your choice.


call <OP_Home>\temp\scripts\WLST.bat <OP_Home>\temp\scripts\create_op_ibpm_bridge.py %ADMIN_SERVER_HOSTNAME%:<ibpm_admin_port#> <weblogic_admin_username> <weblogic_admin_password> %SERVER_INSTANCE% <server_name> %SERVER_INSTANCE_PORT% %OP_INSTANCE_PORT%

Where:



Task 8: Create the Workflow Managed Server InstanceTo create the new workflow managed server instance, use the following steps.

Notes


<Workflow_Home> in the file path represents the installation location of the Fujitsu Interstage BPM server. The default path for a Windows installation is c:\Fujitsu\InterstageBPM.

Steps:

1. Start the InterstageBPMAdminServer service.2. At a Windows command prompt, navigate to the following directory:

<OP_Home>\temp\scripts

3. From the \scripts directory, run the following .bat files with the updated values as follows:a. create_ibpm_managed_server.bat <server_name>-

InterstageBPMCS<server#> <new_IBPM_http_port#> <new_IBPM_https_port#>b. deploy_ibpm_console.bat <server_name>-InterstageBPMCS<server#>c. create_ibpm_internal_jms_bridge.bat <server_name>-

InterstageBPMCS<server#> <new_IBPM_http_port#> <new_IBPM_https_port#>d. create_op_ibpm_jms_bridges_ibpm.bat <server_name>-

InterstageBPMCS<server#> <new_IBPM_http_port#> <new_IBPM_https_port#> <new_OpenPages_http_port#>

4. Navigate to the <OP_Home>\bin directory.5. From the \bin directory, run the following command file to register workflow services:

RegisterIBPMWindowsServices.cmd <server_name>-InterstageBPMCS<server#> InterstageBPMCS<server#> http://<admin_host_name>:<ibpm_admin_port#>

6. Navigate to the <Workflow_Home>\server\deployment\WLS-Cluster<server_name>-InterstageBPMCS<server#> directory and run the following command file with the updated parameter values:

importProperties.bat <Workflow_Home>\server\deployment\ WLS-Cluster<server_name>-InterstageBPMCS<server#>\ibpm.properties <opworkflow_DB_username> <opworkflow_DB_password>



Task 9: Mask Passwords in the Workflow Script FilesFor security purposes, use the following steps to manually mask the plain text <weblogic_admin_password> that you entered in the workflow script files in Task 7 on page 204.


Steps:

1. Navigate to the <OP_Home>\temp\scripts directory.2. Open the following .bat files in a text editor:

• create_ibpm_managed_server.bat• deploy_ibpm_console.bat • create_ibpm_internal_jms_bridge.bat • create_op_ibpm_jms_bridges_ibpm.bat

3. For each .bat file, do the following.a. Locate the plain text password value for the <weblogic_admin_password>

parameter in the file.b. Use asterisks (***) to overwrite the plain text password value for the

<weblogic_admin_password> parameter. 4. When finished, save the file.

Task 10: Update the Start/Stop Server Command FilesTo add information about the new managed server instance to the start and stop server command files, use the following steps.

Task A: Modify the Start Server Command FileSteps:

1. Navigate to the <OP_Home>\bin directory.2. Open the StartAllServers.cmd file in a text editor.3. After the block of start server code for the highest numbered OpenPagesServer#

managed server instance in the file, do the following.a. Add the following lines of code:

sc start "OpenPagesServer<server#>" call pauseForServerToStart.cmd %HOST_NAME% %OP_ADMIN_PORT% <server_name>-OpenPagesServer<server#> %SERVER_CHECK_MAX_WAIT_COUNT% if "%ERRORLEVEL%" NEQ "0" ( echo. echo Unable to connect to OpenPages Managed server. echo. )

b. Update the parameter values in the lines that you added.4. After the block of start server code for the highest numbered InterstageBPMCSServer#


sc start "InterstageBPMCS<server#>" call pauseForServerToStart.cmd %HOST_NAME% %IBPM_ADMIN_PORT% <server_name>-InterstageBPMCS<server#> %SERVER_CHECK_MAX_WAIT_COUNT% if "%ERRORLEVEL%" NEQ "0" ( echo. echo Unable to connect to IBPM Managed server. echo. )

b. Update the parameter values in the lines that you added.




Task B: Modify the Stop Server Command FileSteps:

1. In the <OP_Home>\bin directory, open the StopAllServers.cmd file in a text editor.2. Before the block of stop server code for the highest numbered OpenPagesServer#


sc stop "OpenPagesServer<server#>" call pauseForServerToStop.cmd %HOST_NAME% %OP_ADMIN_PORT% <server_name>-OpenPagesServer<server#> %SERVER_CHECK_MAX_WAIT_COUNT% if "%ERRORLEVEL%" NEQ "0" ( echo. echo Unable to shutdown OpenPages Managed server. echo. )

b. Update the parameter values in the lines that you added.3. Before the block of stop code for the highest numbered InterstageBPMCSServer#


sc stop "InterstageBPMCS<server#>" call pauseForServerToStop.cmd %HOST_NAME% %IBPM_ADMIN_PORT% <server_name>-InterstageBPMCS<server#> %SERVER_CHECK_MAX_WAIT_COUNT% if "%ERRORLEVEL%" NEQ "0" ( echo. echo Unable to shutdown IBPM Managed server. echo. )

b. Update the parameter values in the lines that you added.4. When finished, save the file.

Task 11: Update the Unregister Services Command File and Restart ServicesTo add information about the new managed server instance to the unregister Windows services command file, use the following steps.

Steps:

1. In the <OP_Home>\bin directory, open the UnRegisterAllServices.cmd file in a text editor.

2. Add the following line after the unregister code line for the highest numbered OpenPagesServer# managed server instance in the file:

call UnRegisterOPWindowsServices.cmd "OpenPagesServer<server#>"

Update the parameter in the line that you added.

3. Add the following line after the unregister code line for the highest numbered InterstageBPMCSServer# managed server instance in the file:

call UnRegisterOPWindowsServices.cmd "InterstageBPMCS<server#>"

Update the parameter in the line that you added.

4. Restart all services.



Adding Vertical Cluster Members to an Existing Installation in an IBM WebSphere Environment

The information in this topic applies only to IBM OpenPages GRC Platform in an IBM WebSphere environment.

This section describes how to add an OpenPages application and workflow managed server to an existing IBM OpenPages GRC Platform 6.0.1.1 installation running in an IBM WebSphere environment.

IMPORTANT! The IBM OpenPages GRC Platform requires a dedicated AIX LPAR and IBM WebSphere environment. Sharing the OpenPages LPAR with other applications and IBM WebSphere environments is not supported.

PrerequisiteBefore you begin the tasks described in this section, it is assumed that you have successfully applied the IBM OpenPages GRC Platform 6.0.1.1 patch to your existing 6.0.1 installation and that the temp directory created during the 6.0.1 installation still exists.

Task OverviewThe following tasks outline the process for adding a vertical cluster member:

Task 1: Update Values in the OpenPages Property Files on page 198 Task 2: Modify and Run the Workflow Scripts on page 211 Task 3: Update Values in Property Files on page 212 Task 4: Update the Start/Stop Server Scripts on page 216 Task 5: Mask Passwords in the Install Property File and Restart Services on page 217

IMPORTANT!

You must perform all of the tasks in this section for each managed server instance (OpenPages application/workflow server pair) that you want to add.

You must log on as the opuser to perform these tasks.

About Using Parameters in TasksThe tasks described in this section require that you supply values for certain common parameters. You must enter these parameter values consistently across all of the tasks.

Example

Let’s say a property or code statement requires the name of the machine on which you are adding the cluster member. That value is represented by the <server_name> parameter. If the name of the machine on which you are adding the cluster member is aix_OP_Host, then you must enter aix_OP_Host whenever you are asked to provide the value for <server_name>.

These parameters are summarized in the table below.

Table A-2: Parameters for Adding Cluster Members in IBM WebSphere


<Workflow_Home> The directory where Fujitsu Interstage BPM is installed.

Default: /opt/Fujitsu/InterstageBPM

<server_name> The host name of the machine on which you are adding the managed server instance.

Example: aix_OP_Host



<server#> The number of the managed server you are adding to the cluster.

Example: If you currently have one managed server on aix_OP_Host, this parameter value would be 2.

<OpenPages_bootstrap_port#> The value of the BOOTSTRAP_ADDRESS setting in the following property file:

<OP_Home>/temp/wasconfig/OpenPagesCell.<server_name>-OPNode1Server<server#>.config.props

Example: 10101

<OpenPages_default_server_port#> The value of the WC_defaulthost setting in the following property file:

<OP_Home>/temp/wasconfig/OpenPagesCell.<server_name>-OPNode1Server<server#>.config.props

Example: 10108

<IBPM_bootstrap_port#> The value of the BOOTSTRAP_ADDRESS setting in the following property file:

<OP_Home>/temp/wasconfig/IBPMCell.<server_name>-IBPMNode<server#>Server.config.props

Example: 20101

<IBPM_default_server_port#> The value of the WC_defaulthost setting in the following property file:

<OP_Home>/temp/wasconfig/IBPMCell.<server_name>-IBPMNode<server#>Server.config.props

Example: 20111

<opadmin_WAS_username> If IBM WebSphere global security is configured, the OpenPages administrator user name for accessing the IBM WebSphere Integrated Solutions Console.

<opadmin_WAS_password> If IBM WebSphere global security is configured, the OpenPages administrator password for accessing the IBM WebSphere Integrated Solutions Console.

Default: openpages

<opworkflow_DB_username> The OpenPages workflow user name for accessing the workflow database.

<opworkflow_DB_password> The OpenPages workflow password for accessing the workflow database.

Table A-2: Parameters for Adding Cluster Members in IBM WebSphere




Task 1: Create the OpenPages Application and Workflow Managed Server Instances

To create the new OpenPages application and workflow managed server instances, use the following steps.


Steps:

1. Make sure that the following services are running: • OpenPagesDmgr • OPNode1• IBPMDmgr

2. Navigate to the <OP_Home>/temp/perlinstall directory.3. Open the install.properties file in a text editor, and do the following.

a. Type the password values for the following properties:

Note: The password values that you type will be in plain text. After all tasks are complete and the member has been added to the cluster, you will have to manually mask these values with asterisks (***). For details, see Task 5 on page 217.

• ADMIN_USERNAME=<opadmin_WAS_username>

Note: If IBM WebSphere global security is enabled, update accordingly. Otherwise, leave blank.

• ADMIN_PASSWORD=<opadmin_WAS_password>

Note: If IBM WebSphere global security is enabled, update accordingly. Otherwise, leave blank.

• OP_JDBC_PASSWORD=<OpenPages_DB_User_Password>• IBPM_JDBC_PASSWORD=<Workflow_DB_User_Password>

b. When finished, save the file.4. At a shell prompt, run the following perl scripts in sequence with the updated values

for these parameters:a. perl addOPServer.pl <server_name>-OPNode1 <server_name>-

OPNode1Server<server#>b. perl createIBPMNode.pl <server_name>-IBPMNode<server#>c. perl addIBPMServer.pl <server_name>-IBPMNode<server#> <server_name>-

IBPMNode<server#>Server <server_name>-OPNode1Server<server#>d. perl createIBPMJmsResourcesInOP.pl <server_name>-

OPNode1Server<server#> <server_name>-IBPMNode<server#>Server

Task 2: Modify and Run the Workflow ScriptsThis task provides instructions for modifying and running the createIBPMDirectories.sh and createIBPMPropertyFiles.sh scripts.


Steps:

1. In the <OP_Home>/temp/perlinstall directory, open the following script files in a text editor of your choice:• createIBPMDirectories.sh • createIBPMPropertyFiles.sh



2. For the createIBPMDirectories.sh script file ONLY — for each ‘cp’ statement in the file that begins with:

cp $OP_INSTALL_DIR/temp/ibpm

modify the path to include the /patch directory as follows:

cp $OP_INSTALL_DIR/patch/temp/ibpm

Example

The path in the following ‘cp’ statement in the file would change from:

cp $OP_INSTALL_DIR/temp/ibpm/JavaActionDef.xml $NODE_CONSOLE_DIR/apps/System/web/Config

to this:

cp $OP_INSTALL_DIR/patch/temp/ibpm/JavaActionDef.xml $NODE_CONSOLE_DIR/apps/System/web/Config

3. For each script file, make the following changes:a. Comment out the following while loop statements using the # sign, as shown:

#while [ $COUNT -lt $NO_OF_SERVERS ]

#do

#done

b. Change the expression count from +1 to the number of the member you are adding to the cluster:

from this: COUNT=‘expr $COUNT + 1‘

to this: COUNT=‘expr <server#>‘

4. When finished, save the two script files.5. At a shell prompt, run each script as follows:

a. sh createIBPMDirectories.shb. sh createIBPMPropertyFiles.sh

6. Edit the two scripts to revert the changes made in the second step to their original state and save the files.

Task 3: Update Values in Property FilesUse the following instructions to modify and update values in these files: server.properties, sosa.properties, ibpm.properties, iFlowClient.properties, and console.conf files.


Task A: Modify Values in the OpenPages Server Properties File (server.properties)Steps:

1. Navigate to the <OP_Home>/aurora/conf directory and do the following.a. Create a copy of the following property file:

<server_name>-OPNode1Server1-server.properties


<server_name>-OPNode1Server<server#>-server.properties



2. Open the renamed file in a text editor and do the following:a. Verify that the correct value for <server_name> is used throughout the file.b. Change all occurrences of the bootstrap port number for OPNode1Server1 to the

<OpenPages_bootstrap_port#> value of the new cluster member.

Note: Bootstrap port numbers can be found in the following file:

<OP_Home>/temp/wasconfig/OpenPagesCell.<server_name> -OPNode1Server<server#>.config.props

c. Update the parameter values for the following properties:• workflow.client.props.path=<Workflow_Home>/client/

<server_name>-IBPMNode<server#>Server-iFlowClient.properties• url.path.openpages=http\://

<server_name>\:<OpenPages_default_server_port#>/openpages• url.path.workflow.admin=http\://

<server_name>\:<IBPM_default_server_port#>/ibpmconsole• webclient.http.server.port=<OpenPages_default_server_port#>

d. When finished, save the file.

Task B: Modify Values in the Sosa Property File (sosa.properties)Steps:

1. In the <OP_Home>/aurora/conf directory, do the following:a. Create a copy of the following property file:

<server_name>-OPNode1Server1-sosa.properties


<server_name>-OPNode1Server<server#>-sosa.properties

2. Open the renamed file in a text editor and update the parameter values for the following properties:

• openpages.service.port=<OpenPages_bootstrap_port#>• application.url.path=http\://

<server_name>\:<OpenPages_default_server_port#>/openpages3. When finished, save the file.

Task C: Modify Values in the Workflow IBPM Server Property File (server.properties)Steps:

1. In the <OP_Home>/aurora/conf directory, do the following:a. Create a copy of the following property file:

<server_name>-IBPMNode1Server-server.properties


<server_name>-IBPMNode<server#>Server-server.properties

2. Open the renamed file in a text editor and do the following:a. Change all occurrences of the workflow bootstrap port number for

IBPMNode1Server to the <IBPM_bootstrap_port#> value of the new cluster member.


<OP_Home>/temp/wasconfig/IBPMCell.<server_name> -IBPMNode<server#>Server.config.props



b. Update the parameter values for the following properties:• jta.providerurl=iiop\://<server_name>\:<IBPM_bootstrap_port#>• jms.providerurl=iiop\://<server_name>\:<IBPM_bootstrap_port#>• workflow.client.props.path=<Workflow_Home>/client/<server_name>

-IBPMNode<server#>Server-iFlowClient.properties• url.path.workflow.admin=http\://

<server_name>\:<IBPM_default_server_port#>/ibpmconsole• url.path.openpages=http\://

<server_name>\:<OpenPages_default_server_port#>/openpages• webclient.http.server.port=<OpenPages_default_server_port#>


Task D: Modify Values in the iFlow Client Property File (iFlowClient.properties)Steps:

1. Navigate to the <Workflow_Home>/client directory and do the following:a. Create a copy of the following property file:

<server_name>-IBPMNode1Server-iFlowClient.properties file


<server_name>-IBPMNode<server#>Server-iFlowClient.properties

2. Open the renamed file in a text editor and do the following:a. Change all occurrences of the workflow bootstrap port number for

IBPMNode1Server to the <IBPM_bootstrap_port#> value of the new cluster member.


<OP_Home>/temp/wasconfig/IBPMCell.<server_name> -IBPMNode<server#>Server.config.props


Task E: Modify Values in the IBPM Console Configuration File (console.conf)Steps:


<Workflow_Home>/profiles/<server_name>-IBPMNode1/installedApps/IBPMCell/fujitsu-console-ear.ear/ibpmconsole.war

2. Copy the console.conf file to the following directory:

<Workflow_Home>/profiles/<server_name>-IBPMNode<server#>/installedApps/IBPMCell/fujitsu-console-ear.ear/ibpmconsole.war

3. Open the copied file in a text editor and update the parameter value for the following property:

NamingProviderURL=t3://<server_name>:<IBPM_bootstrap_port#>




Task F: Modify Values in the IBPM Property File (ibpm.properties) and Run the Import Properties Script

Steps:


<Workflow_Home>/server/deployment/WAS-Cluster<server_name>-IBPMNode<server#>Server

2. Open the ibpm.properties file in a text editor and do the following.a. Update the parameter values for the following properties:

• NamingProviderURL=iiop\://<server_name>\:<IBPM_bootstrap_port#>• JMSNamingProviderURL=iiop\://

<server_name>\:<IBPM_bootstrap_port#>• ServerHost=<server_name>• ServerLogFile=<Workflow_Home>/server/instance/default/logs/

<server_name>-IBPMNode<server#>Server.log • ServerInCluster=true • ServerBaseURL=http\://<server_name>\:<IBPM_default_server_port#>/

ibpmconsole/ • ServerEmailBaseURL=http\://

<server_name>\:<IBPM_default_server_port#>/ibpmconsole/System/ b. If the following ServerName property:

• Does not exist in the file, then add it to the end of the file. • Exists in the file, then update the parameter values.

ServerName=<server_name>-IBPMNode<server#>Server

c. When finished, save and close the file.3. In the same directory, run the importProperties.sh script as follows:

sh importProperties.sh

Note: If an error message for logging.properties displays while the script is running, it is not significant and can be ignored.

Task G: Run Patch Scripts to Update Server Configuration To update the new cluster member with the updated configuration on the OpenPages and workflow servers, run the updateOPPatch.pl and updateIBPMPatch.pl perl scripts as follows.

Steps:


<OP_Home>/patch/temp/applications/perlinstall

2. At a shell prompt, run the updateOPPatch.pl perl script on a single line to update the OpenPages server as follows:

perl updateOPPatch.pl <server_name>-OPNode1 <server_name>-OPNode1Server<server#>

3. At a shell prompt, run the updateIBPMPatch.pl script on a single line to update the workflow server as follows:

perl updateIBPMPatch.pl <server_name>-IBPMNode<server#> <server_name>-IBPMNode<server#>Server



Task 4: Update the Start/Stop Server ScriptsTo add information about the new managed server instance to the start and stop server scripts, use the following steps.

Task A: Modify the Start Server ScriptSteps:

1. Navigate to the <OP_Home>/bin directory.2. Open the startAllServers.sh script in a text editor.3. After the line of startServer.sh code for the highest numbered OPNode1Server#

managed server instance in the file, do the following.a. Add the following line of code:

$WAS_HOME/bin/startServer.sh <server_name>-OPNode1Server<server#>

b. Update the parameter values in the line that you added.4. After the block of start server code for the highest numbered IBPMNode# managed

server instance in the file, do the following.a. Add the following lines of code:

. $IBPM_PROFILES_HOME/<server_name>- IBPMNode<server#>/bin/setupCmdLine.sh # Starting the node $WAS_HOME/bin/startNode.sh # Starting all the server specified $WAS_HOME/bin/startServer.sh <server_name>-IBPMNode<server#>Server


Task B: Modify the Stop Server ScriptSteps:

1. In the <OP_Home>/bin directory, open the stopAllServers.sh script in a text editor.2. Before the line of stopServer.sh code for the highest numbered OPNode1Server#

managed server instance in the file, do the following.a. Add the following line of code:

$WAS_HOME/bin/stopServer.sh <server_name>-OPNode1Server<server#>

b. Update the parameter values in the line that you added.3. Before the block of stop server code for the highest numbered IBPMNode# managed

server instance in the file, do the following.a. Add the following lines of code:

. $IBPM_PROFILES_HOME/<server_name>- IBPMNode<server#>/bin/setupCmdLine.sh # Stopping the node $WAS_HOME/bin/stopNode.sh # Stopping all the server specified $WAS_HOME/bin/stopServer.sh <server_name>-IBPMNode<server#>Server




Task 5: Mask Passwords in the Install Property File and Restart ServicesFor security purposes, use the following steps to manually mask the plain text passwords that you entered in the install.properties files from Task 1.


Steps:

1. Navigate to the <OP_Home>/temp/perlinstall directory.2. Open the install.properties file in a text editor, and do the following.

a. Use asterisks (***) to overwrite the plain text password values for the following properties. The overwritten password values will look similar to the following:• ADMIN_PASSWORD=*****• OP_JDBC_PASSWORD=*****• IBPM_JDBC_PASSWORD=*****

b. When finished, save the file.3. Restart all services.



• • • • • • • • • •Adding Horizontal Cluster Members

This section describes how to add additional OpenPages application and workflow instances onto an existing OpenPages cluster member.

Verify that Servers are RunningIf installing OpenPages onto a cluster member server (a non-admin server), make sure that all OpenPages and workflow services (including the database service) on the cluster administrator server are running before performing the install. Having the services running allows the installer to validate user input.

Adding New Horizontal Cluster MembersThis section describes how to add a new OpenPages application and workflow non-administrative managed server to an existing IBM OpenPages GRC Platform 6.0.1 installation in a horizontal clustered environment.

Steps:

1. Install IBM OpenPages GRC Platform 6.0.1 on the machine you want to add as a member to your horizontal cluster.

2. Apply the IBM OpenPages GRC Platform 6.0.1.1 patch to the new member of your horizontal cluster.

3. If you are adding the non-administrative server for the first time, make sure you configure the domain account and share the network OpenPages storage directory.

4. Depending on your environment, follow the instructions in one of the following topics to add a non-administrative server to a second or third machine in your horizontal clustered environment:

“Adding Vertical Cluster Members to an Existing Installation in an Oracle WebLogic Environment” on page 196

“Adding Vertical Cluster Members to an Existing Installation in an IBM WebSphere Environment” on page 209

Note: For more information on configuring domain accounts and the OpenPages storage directory, see Appendix B “Configuring Clustered Environments” on page 219.



B
Configuring Clustered Environments
All tasks in this section are recommended, but not required for IBM OpenPages GRC Platform cluster environments.


About Clustered Environments on page 220 Configuring a Clustered OpenPages Environment on page 224 Configuring the Load Balancer on page 229 Load-balancing the OpenPages Reporting Server on page 239


• • • • • • • • • •About Clustered Environments

The OpenPages environment can be expanded to accommodate additional users by adding extra software instances, called nodes, to your current environment. A node in OpenPages is defined as an instance of the OpenPages application server along with a corresponding instance of the workflow server.

These extra nodes can be added within a single OpenPages application server (vertical clustering) or by adding additional application server machines (horizontal scaling).

Vertical scaling involves configuring additional nodes of the software within an existing machine. This approach assumes you have sufficient memory and CPU power in a single environment to support the additional nodes.

Horizontal scaling is accomplished by adding machines to your configuration to host additional nodes.

Scaling either vertically or horizontally requires the use of a load-balancer to distribute the incoming requests across the nodes.

CommandCenter, the OpenPages reporting server, leverages the IBM Cognos Business Intelligence, which can also be clustered vertically or horizontally.

Scaling the reporting server vertically within the same environment involves increasing the number of processes available to handle requests, and depending on the load, may involve configuring additional dispatchers.

Scaling the reporting server horizontally involves installing additional environments and registering the Cognos dispatchers so that the incoming requests will be distributed across the multiple environments.

To create a clustered OpenPages environment, you should install and configure each OpenPages and CommandCenter instance as if it were a stand-alone system, then follow the instructions in this chapter to configure each system for load balancing.

See:

“Configuring a Clustered OpenPages Environment” on page 224 “Configuring the Load Balancer” on page 229 “Load-balancing the OpenPages Reporting Server” on page 239

About Load-balancing an OpenPages Web ServerOpenPages leverages the J2EE clustering model which allows an application to scale through the addition of additional nodes. Each node runs on a different port. A load-balancer must be installed and configured to distribute incoming requests across the different nodes.

Your organization may deploy any type of hardware-based or software-based load-balancer, but the load balancer must support:

session affinity and port-based URL routing

The load balancer can be installed on the OpenPages application server or on an external system.

For reference, the instructions in the following sections describe how to configure an Apache Web Server for load-balancing in a WebLogic Server installation and an IBM HTTP Web Server on a WebSphere Application Server. See:

“Configuring the Apache Web Server as a Load Balancer in a Windows Environment” on page 229

“Configuring the IBM HTTP Web Server as a Load Balancer in an AIX Environment” on page 233

“Tailor the Load Balancer” on page 238

Appendix B: Configuring Clustered Environments


Sample Clustered OpenPages Environments The following examples, Figure B-1 and Figure B-2, are examples of typical clustered OpenPages environments for reference purposes. Your network topology may differ.

Sample Windows/WebLogic Server Clustered EnvironmentFigure B-1 illustrates a typical clustered environment on the Windows/WebLogic Server platform. This example shows a four-node application server installation, with two physical machines, each containing two nodes. The environment also includes a two-node reporting server installation consisting of two physical machines, each with one node.

Figure B-1: Sample Load Balanced Windows/WebLogic Server Environment

In this example, an Apache Web server handles load-balancing among the four OpenPages nodes and a single reporting server node.



Sample AIX/WebSphere Application Server Clustered EnvironmentFigure B-2 illustrates a typical clustered environment on the AIX/WebSphere Application Server platform. This example shows a four-node application server installation, with two physical machines, each containing two nodes. The environment also includes a two-node reporting server installation consisting of two physical machines, each with one node.

Figure B-2: Sample Load Balanced AIX/WebSphere Application Server Environment

In this example, a IBM HTTP Web Server handles load-balancing among the four OpenPages nodes and a single reporting server node.



Sample Clustered CommandCenter EnvironmentEach of the clustered environments shown in Figure B-1 and Figure B-2 above includes a two-node reporting server installation consisting of two physical machines, each with one CommandCenter node. One reporting server is configured as the primary server, which handles incoming requests and load-balancing.

The IBM Cognos 8 Business Intelligence software installed on the reporting server handles load-balancing between the two reporting server nodes.

For information on configuring load balancing for the reporting servers, see “Load-balancing the OpenPages Reporting Server” on page 239.



Configuring a Clustered OpenPages

• • • • • • • • • •Environment

Perform the following tasks on all OpenPages application servers, Windows or AIX.

Raising the Oracle Connection LimitThis task is required.

Use the following steps to increase the number of users who can connect to the database instance.

Steps:

1. Log on to the 6.0.1 database server as a user with administrative privileges.2. Launch a Web browser and navigate to the following address to start the Oracle

Enterprise Manager console:

https://<server_name>:1158/em

3. Login to the Oracle Enterprise Manager console using sys/<password>@sysdba format.a. Enter sys in the User Name field.b. Enter the password for the sys user.c. Select SYSDBA from the Connect As list.

4. On the Oracle Enterprise Manager Home page, click the Server tab.5. Under Database Configuration, click Initialization Parameters.6. On the Initialization Parameters page, click the SPFile tab.7. Locate the Processes parameter. If necessary, use the search function by entering

Processes in the Name field and clicking Go.8. Enter a value in the Processes field.

In a clustered environment, for best performance allocate sufficient processes for each OpenPages application instance, each corresponding Fujitsu Interstage BPM instance, and each corresponding CommandCenter instance. For a two-node OpenPages environment, we recommend:

• OpenPages -- configure 75 processes for each OpenPages instance• workflow -- configure 35 processes for each associated workflow server• CommandCenter -- configure 80 processes for each CommandCenter instance• database overhead -- configure 60 processes for database connection overhead

and background processes

By default, this setting is 250 processes (and 280 sessions) for a two-node OpenPages environment. If you have two or more application servers, you will need to raise the number of processes appropriately.

9. Click Apply. You are prompted to restart the server. 10. Select Immediate to restart the server.



Configuring OpenPages to Use a Domain AccountThis task is required.

In a clustered environment, the OpenPages application services access a fileshare, so the account that launches the services must have the proper fileshare permissions.

Windows

By default, Windows services run under the LocalSystem account, which cannot access a shared drive on another machine. If you are using a horizontal cluster, you must configure the OpenPages application services on all application servers to run under a domain account that has permission to access the shared drive.

The OpenPages application services that must have the proper fileshare permissions are:

OpenPagesAdminServer OpenPagesServer# IBPMAdminServer InterstageBPMCS#

Steps:

1. Log on to each 6.0.1 application server as a user with administrative privileges.2. Open the Services control panel.3. Stop the OpenPages services.4. For each OpenPages application service, do the following:

a. Right-click the service name and select Properties from the shortcut menu.b. In the Properties dialog box, click the Log On tab.c. Select the This account option.d. Type a domain, account name, and password for at least one users that will have

access to the shared drive. e. Click OK to continue.

AIX

For clustered OpenPages environments running on the AIX platform, configure the same user name and password on all systems, and all fileshare permissions should be the same. Also, if you are using a network file share (NFS) ensure that users have read/write access to the fileshare when mounting.

Sharing a Network OpenPages Storage DirectoryThis task is required for systems that meet the stated conditions.

The OpenPages application installation included a pointer to the OpenPages storage location, a directory where attached files and forms associated with OpenPages objects are stored.

If you pointed to a location on the local machine, you need to change the pointer to a shared network storage location. You can use the update-storage script included in the OpenPages installation media to change the storage directory used by the OpenPages application to a shared directory on the same or another server.

If you entered a shared network storage location when installing the OpenPages application, you can skip this step.

Windows

Steps:

1. Log on to a managed 6.0.1 application server where you want to make the change as a user with administrative privileges and full access to the local server drives.

2. Log on to a machine with SQL*Plus and access to the database server.



3. Launch a Command Prompt window (using the Run as Administrator option).4. Copy the OP_6.0.1_Configuration directory from the Installer Disc 1 DVD or on

your network share location to the local system.a. Navigate to the following folder:




5. Navigate to the INSTALL SCRIPTS directory on the local system.6. Execute the following command to launch the update-storage script:

sqlplus /nolog @sql-wrapper update-storage <log_file_name> <TNS_alias_name> <OpenPages_schema_owner_name> <OpenPages_schema_owner_password> <storage_type> <storage_server_name> <machine_name> <OpenPages_storage_platform> <sharename>

The following table lists the command line parameters that must be passed to the SQL wrapper script.

Example

sqlplus /nolog @sql-wrapper.sql update-storage c:\temp\update-storage-output.log qevm04 openpages openpages UNC qe-vm05 qe-vm04 windows openpages-storage

Parameter Definition

log_file_name The path name of the log file created by the script. • If a path is not specified, the log file is created in the

current working directory. • If a log with the same name exists in the same

location, the log will be overwritten by the script.

TNS_alias_name The database connection identifier, such as TNS alias name.

OpenPages_schema_owner_name The name of the OpenPages user, created during the OpenPages application install (openpages by default).

OpenPages_schema_owner_password The password of the OpenPages user.

storage_type The type of storage, enter either LFS for Local File System, or UNC for Universal Naming Convention or Uniform Naming Convention.

storage_server_name The name of the server where the OpenPages Storage is located.

machine_name The name of the cluster administrator machine.

OpenPages_storage_platform The operating system on the server where the OpenPages storage is located. Enter Windows or UNIX.

sharename The name of the shared OpenPages storage directory or the mount point (by default, openpages-storage).



AIX

Steps:

1. Mount the storage folder on the admin server to the non-admin server with the following steps.a. Log on to the OpenPages managed server as the root user or a user the System

group.b. Launch an AIX shell.c. Navigate to the /etc directory.d. Open the hosts file in a text editor and add the port and name of each OpenPages

managed server.e. Save and close the hosts file.f. Create a new file with the name exports in the /etc folder.

mkdir -m -755 exports

Note: Make sure you have full rights to the local installation directory.

g. Open the exports file in a text editor and add the full path to the storage folder.

Example

/opt/OpenPages/openpages-storage

h. Export all file systems named in /etc/exports using the following command:

exportfs -a

The exportfs command maintains the current table of exported file systems for NFS in the /var/lib/nfs/etc file.

i. Restart the NFS server using the following commands:

stopsrc -g nfs startsrc -g nfs

The NFS server processes requests from the NFS clients.

j. Check that the openpages-storage folder is exported and ready to be mounted using following command:

showmount -e

The openpages-storage folder should be listed.

2. Mount the storage directory from the admin server on the managed server as follows.a. Log on to the OpenPages managed server as the root user or a user the System

group.b. Launch an AIX shell as a user with administrative privileges.c. Navigate to the /etc directory.d. Open the hosts file in a text editor and add the port and name of each OpenPages

managed server.e. Save and close the hosts file.f. Create a new file with the name exports in the /etc folder.

mkdir -755 exports

g. Open the exports file in a text editor and add the full path to the storage folder.

Example

/opt/OpenPages/openpages-storage



h. Execute the following command to mount the storage folder:

mount <nfsservername> <mountpoint>

Where:

• <nfsservername> is the name of the OpenPages admin server and the pathname of the openpages-storage directory on the admin server.

• <mountpoint> is the name and path of the openpages-storage directory on the managed server.

Example

mount aix61-1-5.openpages.com:/usr/OpenPages/openpages-storage /usr/OpenPages/openpages-storage

3. Use the update-storage script included in the OpenPages installation media to change the storage directory used by the OpenPages application to a shared directory on the application server, as shown above:

sqlplus /nolog @sql-wrapper update-storage <log_file_name> <TNS_alias_name> <OpenPages_schema_owner_name> <OpenPages_schema_owner_password> <storage_type> <storage_server_name> <machine_name> <OpenPages_storage_platform> <sharename>

Examples

sqlplus /nolog @sql-wrapper.sql update-storage /opt/temp/update-storage-output.log qevm04 openpages openpages LFS qe-vm05 qe-vm04 UNIX /opt/OpenPages/openpages-storage



• • • • • • • • • •Configuring the Load Balancer

The following sections show how to configure a load balancer, where an external server is used for load balancing. See either section, as appropriate:

“Configuring the Apache Web Server as a Load Balancer in a Windows Environment” below

“Configuring the IBM HTTP Web Server as a Load Balancer in an AIX Environment”

Configuring the Apache Web Server as a Load Balancer in a Windows Environment

The following example shows a typical configuration for load balancing an OpenPages environment on Windows using the Apache Web Server.

The following example assumes that load balancing is performed by an Apache Web Server on a separate load-balancing server.

Task 1: Configure Property Files on the Load BalancerYou must configure the Apache Web Server to redirect traffic to the OpenPages or workflow server, based on cookies installed on a client system.

Steps

1. Log on to load-balancing server as a user with administrative privileges. 2. Launch a Command Prompt window (using the Run as Administrator option).3. Navigate to the <Apache_Home>\conf\ directory.4. Open the httpd.conf file (the Apache configuration file)

a. Add or uncomment the following lines to load the following modules:

LoadModule negotiation_module modules/mod_negotiation.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule status_module modules/mod_status.so LoadModule weblogic_module modules/mod_wl_22.so

b. Modify the parameter setting ServerName to point to the host name where you installed the Apache Web Server, as follows:

Change ServerName=MYSERVERNAME.DOMAIN.COM to ServerName=<op-load-balancer.domain.com>

Where <Lop-load-balancer.domain.com> is the fully-qualified domain name of the load balance server.

c. Modify the parameter setting ServerRoot to point to the base directory where you installed the Apache Web Server (uncomment the parameter, if necessary), by default:

ServerRoot=C:/Program Files/Apache Software Foundation/Apache2.2



d. Modify all of the Directory tags so the path points to the directory location of the Apache server installation, and then add the setting “Allow from all” to the tag attributes (if not present), as follows:

<Directory "C:/Apache2.2/htdocs"> Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory>

e. At the end of the httpd.conf file, add the following entries, which configure Apache to forward requests to the WebLogic Server.

Where:

<SERVER>.<DOMAIN>.COM:<port> is the actual server name and application port hosting the application nodes.

WebLogicPort is the admin server port for OpenPages or Workflow Server.

For the <Location /opws> and <Location /openpages> entries, include all OpenPages application nodes in the cluster.

For the <Location /ibpmweblogicconsole> entries include all workflow nodes in the cluster.

Note: The example below assumes a two-node installation with the first node at port 7001, and the second port at 7011.

<Location /console> SetHandler weblogic-handler MaxPostSize 0 WLLogFile logs/weblogic_console.log WebLogicHost <SERVER>.<DOMAIN>.COM WebLogicPort 7001 </Location>

<Location /opws> WLCookieName opapp SetHandler weblogic-handler MaxPostSize 0 KeepAliveEnabled ON KeepAliveSecs 15 WLLogFile logs/openpages_webservices.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

<Location /openpages> WLCookieName opapp SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile /logs/openpages.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

<Location /ibpmconsole> WLCookieName opibpm SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile logs/ibpmconsole.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

<Location /ibpmweblogicconsole> SetHandler weblogic-handler



MaxPostSize 0 WLLogFile logs/ibpmweblogic_console.log WebLogicHost <SERVER>.<DOMAIN>.COM WebLogicPort 49901 </Location>

f. Add the following parameter and setting to enable monitoring and status of the load balancer:

ExtendedStatus On

g. Set the location tags for server-status and server-info to enable monitoring and status of the load balancer. For example,

<Location /server-status> SetHandler server-status Order Deny,Allow Deny from all Allow from all </Location>

<Location /server-info> SetHandler server-info Order Deny,Allow Deny from all Allow from all </Location>

5. Save and close the httpd.conf file.

Task 2: Configure Property Files for Each OpenPages InstanceYou must edit the server properties file on each OpenPages cluster member to point to the load balancer using the following steps.

Where: <op-load-balancer.domain.com> is the fully qualified domain name of the load balancer. ibpmconsole and openpages are the <Location /> values set in the httpd.conf file above.

Steps

1. Log on to the OpenPages cluster member, as a user with administrative privileges. 2. Launch a Command Prompt window (using the Run as Administrator option).3. Navigate to the following directory: <OP_Home>\aurora\conf.4. Open the aurora.properties file in a text editor, such as WordPad.

a. Edit the application.url.path lines to point to the fully-qualified domain name of the load balancer For example:

application.url.path=http\://<op-load-balancer.domain.com>\:<port>/openpages

b. Save and close the aurora.properties file.5. Open each <server_name>-OpenPagesServer#-server.properties file in a text

editor, such as WordPad. a. Edit the url.path lines to point to the fully-qualified domain name of the load

balancer. For example:

url.path.workflow.admin=http\://<op-load-balancer.domain.com>\:<port>/ibpmconsole url.path.openpages=http\://<op-load-balancer.domain.com>\:<port>/openpages

b. Save and close each server.properties file.6. Open each <server_name>-OpenPagesServer#-sosa.properties file in a text editor,

such as WordPad. a. Edit the Application.url.path lines to point to the fully-qualified domain name of

the load balancer. For example:

application.url.path=https\://<op-load-balancer.domain.com>\:<port>/openpages



b. Save and close each server.properties file.7. Open each <server_name>-InterstageBPMCS#-server.properties file in a text




b. Save and close each server.properties file.8. Start Apache in a console window using the Windows Start menu. This will open a

console window and start the Apache Web Server running inside it. Closing this console window will terminate the Apache Web Server.

Task 3: Tailor the Load BalancerFor databases with a large dataset, some OpenPages reports may time out before completion. If you experience problems with reports timing out, you can adjust the keep alive time.

TimeOut. The number of seconds Apache will wait to receive a GET request. between receipt of TCP packets on a POST or PUT request and between ACKs on transmissions of TCP packets in responses.

KeepAliveSecs. The number of seconds that idle connections between the plug-in and WebLogic Server are kept open.

KeepAliveTimeout. The number of seconds Apache will wait for a subsequent request before closing the connection.

Note: Use care when changing the keepalive time out value. A high value may cause performance problems if the higher time out causes server processes to wait for idle clients.

To change the time out values, use the following steps.

Steps

1. Log on to load-balancing Web server as a user with administrative privileges. 2. Launch a Command Prompt window. 3. Change the KeepAliveSecs parameter in the httpd.conf file as follows:

a. Navigate to the <Apache_Home>\conf\ directory.b. Open the httpd.conf file (the Apache configuration file).c. Add the TimeOut parameter with a sufficient value to prevent time out errors, for

example:

TimeOut 1800

d. Change the KeepAliveTimeout parameter to a higher value, for example:

KeepAliveTimeout 1800

e. Locate the <Location /opws> parameter you added above and change the KeepAliveSecs parameter to a higher value, for example:

<Location /opws> WLCookieName opapp SetHandler weblogic-handler MaxPostSize 0 KeepAliveEnabled ON KeepAliveSecs 1800 WLLogFile logs/openpages_webservices.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

f. Save and close the file. 4. Restart Apache in a console window using the Windows Start menu.



Configuring the IBM HTTP Web Server as a Load Balancer in an AIX Environment

The following example shows a typical configuration for load balancing an OpenPages environment on AIX using the IBM HTTP Web Server.

The following example assumes that load balancing is performed by the IBM HTTP Web Server on a separate load-balancing server.

Task 1: Copy the WAS Proxy Module into IHSLoad the mod_was_ap22_http.so module onto the load balancer.

Steps

1. Log on to the load-balancing server as a user with administrative privileges. 2. Launch an AIX shell as a non-root user with administrative privileges.3. Copy the OP_6.0.1_Configuration directory from the Installer Disc 1 DVD or on

your network share location to the local system and navigate to the following folder:

OP_6.0.1_Configuration\IHS_Load_Balancing

4. Copy the mod_was_ap22_http.so module to the IBM HTTP Web Server modules directory, by default:

/usr/IBM/HTTPServer/modules/

Note: Make sure you have full rights to the local installation directory and the files in the directory.

Task 2: Create the Web Server Instances on the Application Web ServerThis topic describes how to install the Web server instances on the machine where you installed WebSphere Application Server.

Use the following steps to create the Web server instances for the OpenPages application and for the workflow server.

Steps:

1. Log on to the application server as a non-root user with administrative privileges.2. Open a web browser and point to the following address:


Where: <server_name> is the name of the OpenPages admin server and 9060 is the default WebSphere Application Server admin port.

3. Click Servers | Server Types | Web Servers. 4. On the Web Servers page, click New to create a new web server instance for the

OpenPages application. 5. On the Select a node for the Web server page:

a. Select the application server from the Select node list.b. Enter opapp in the Server name field.c. Select IBM HTTP Server from the Type list.d. Click Next.

6. On the Select a Web server template page:a. Select the IHS template.b. Click Next.



7. On the Enter the properties for the new Web server page:a. Type the Web server port in the Port field.b. Type the location where the IBM HTTP Web Server software was installed in the

Web server installation location field.c. Type the location where the plug-in will be created in the Plug-in installation

location field.d. Select All from the Application mapping list.e. Click Next.

8. On the Confirm new Web server page:a. Review the settings for the new Web server. b. Click Finish.

9. In the Messages box that appears at the top of the page, click Save to commit the changes to the master configuration.

10. Create a new wen server instance for the Workflow server:a. In the web browser and point to the following address:


Where: <server_name> is the name of the OpenPages admin server and 9060 is the default WebSphere Application Server admin port.

b. Use the steps above to create a new web server instance, using ibpmapp the Server name.

Task 3: Generate the Plug-In FilesWeb server plug-ins enable IHS to communicate requests for dynamic content, such as servlets, to the application server. You need to manually create the web server plug-in for each web server instance (one for the OpenPages application and one for the workflow server). A configuration file (plugin-cfg.xml) is also generated for each plug-in.

Use the following steps to create the Web server instances for the OpenPages application and for the workflow server.

Steps:

1. Log on to the OpenPages admin server as a non-root user with administrative privileges.

2. Create the plugin for the OpenPages server instance:a. Open a Web browser and point to the following address:


Where: <server_name> is the name of the OpenPages admin server and 9060 is the default OpenPages admin port.

b. Click Servers | Server Types | Web Servers. c. Select the OpenPages server instance you created and click Generate Plugin. The

Generate Plugin button becomes active after you select an instance.

The plugin is created and saved to the $IHS_HOME/Plugins/config/<webserver_name>/ directory.

Where <webserver_name> is the OpenPages server instance you created.

3. Create the plugin for the workflow server instance:a. Open a Web browser and point to the following address:


Where: <server_name> is the name of the WebSphere Application Server and 9061 is the default WebSphere Application Server admin port.

b. Click Servers | Server Types | Web Servers.



c. Select the workflow server instance you created and click Generate Plugin. The Generate Plugin button becomes active after you select an instance.

The plugin is created and saved to the $IHS_HOME/Plugins/config/ibpmweb/app/<webserver_name>/

Where <webserver_name> is the workflow server instance you created.

4. Copy both plugin files to the load-balancing server.

IMPORTANT! If you will be configuring the environment for SSL, perform the steps in the “Configuring SSL” chapter before configuring the plugin-cfg.xml file.

Task 4: Merge the Plug-In FilesIn order for load balancing to work correctly for both the OpenPages and workflow servers, the individual plugin-cfg.xml files need to be merged as follows.

1. Log on to the load-balancing server as a non-root user with administrative privileges.2. Create a new text file. This will be the merged file.3. Open the plugin-cfg.xml files for the OpenPages and Workflow servers.4. Copy the <Config> root element from either plugin-cfg.xml file and paste into the new

file.

IMPORTANT! There should be only one <Config> element in merged file.

5. Copy the <Log> element from either of the two merging files, and modify the name, if required, and paste into the new file.

6. Copy all the <VirtualHostGroup> elements from both files and paste into the new file. The VirtualHostGroup name must be unique; There should be only one <VirtualHostGroup> with all ports using default_host.

7. Copy all <ServerCluster> elements from both the files and paste into the new file. Make the names unique if necessary.

The Server Name must be unique across all clusters.

8. In the <Transport> element, the keyring and stashfile properties should use the same location for all the application servers in the merged file.

9. Copy all the <URIGroup> elements from both files and paste into the new file. Make the names unique if necessary.

10. Copy all the <Route> elements from both files and paste into the new file. Apply any changes that you have made to the names of VirtualHostGroup, ServerCluster or URIGroup.

11. Save the new file using a name such as plugin-cfg-merged.xml.12. Navigate to the IBM HTTP Web Server configuration file, httpd.conf, by default:

/usr/IBM/HTTPServer/conf/httpd.conf

13. Add or modify the following line to point to the new, merged plugin file:

WebSpherePluginConfig /usr/IBM/HTTPServer/Plugins/config/OP/ plugin-cfg-merged.xml

Where plugin-cfg-merged.xml is the name of the merged plug-in file.

14. Ensure that the IgnoreAffinityRequests parameter in the <ServerCluster> section is set to False:

IgnoreAffinityRequests="true"




Task 5: Configure Property Files on the Load BalancerThe following example shows how to configure an OpenPages environment that uses the IBM HTTP Web Server for load balancing.

Perform the following tasks on the load balancer.

Steps

1. On the load-balancing Web server, launch an AIX shell and navigate to:.

/usr/IBM/HTTPServer/modules/

Note: Make sure you have full rights to the local installation directory and the files in the directory.

2. Open merged plug-in file (plugin-cfg-merged.xml) in a text editor and make the following changes:a. Change the parameter setting IgnoreAffinityRequests to true. For example,

IgnoreAffinityRequests=true

b. Change the ServerIOTimeout parameter for all servers to a value that allows sufficient time for the OpenPages application to respond to request from a client, for example 3600 seconds. The default is 60 seconds

Name="OPNode1_OPNode1Server1" ServerIOTimeout="3600" Name="OPNode2_OPNode2Server1" ServerIOTimeout="3600" Name="OPNode2_OPNode2Server2" ServerIOTimeout="3600" Name="IBPMNode1_IBPMNode1Server1" ServerIOTimeout="3600"

c. Change the cookie name to allow users to access the IBPM console and OpenPages simultaneously. For OpenPages change the cookie name to opsosa. For IBPM, change the name to opibpm in each of the following Uri groups.

<UriGroup Name="default_host_OpenPagesCluster_URIs"> <Uri AffinityCookie="opsosa" AffinityURLIdentifier="opsosa" Name="/opws/*"/> <UriGroup Name="default_host_IBPMCluster_URIs"> <Uri AffinityCookie="opibpm" AffinityURLIdentifier="opibpm" Name="/ibpmconsole/PortletWrapper/*"/>

3. Save and close the file.4. Navigate to the IBM HTTP Web Server configuration file, httpd.conf, by default:


5. Open httpd.conf in a text editor and make the following changes:a. Add or uncomment the following lines to load the following modules

LoadModule negotiation_module modules/mod_negotiation.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule status_module modules/mod_status.so LoadModule was_ap22_module modules/mod_was_ap22_http.so

b. Modify the parameter setting ServerName to point to the host name where you installed the IBM HTTP Web Server. For example,

ServerName=MYSERVERNAME.DOMAIN.COM

c. Modify the parameter setting ServerRoot to point to the base directory where you installed the Apache Web Server. For example,

ServerRoot=/usr/IBM/HTTPServer/htdocs



d. Modify all of the Directory parameters to add the setting Allow from all to the attributes. For example,

<Directory> Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory>

e. Uncomment the parameter ExtendedStatus and set the value to On. For example:

ExtendedStatus On

f. Set the location tags for server-status and server-info. For example,




Task 6: Configure Property Files for Each OpenPages InstanceYou must edit the server properties file on each OpenPages cluster member to point to the load balancer using the following steps.

Steps

1. Log on to the OpenPages cluster member, as a non-root user with administrative privileges.

2. Launch an AIX shell3. Navigate to the following directory: <OP_Home>/aurora/conf.4. Open the aurora.properties file in a text editor, such as vi.

a. Edit the application.url.path lines to point to the fully-qualified domain name of the load balancer For example:

application.url.path=http\://<op-load-balancer.domain.com>\:<port>/openpages

b. Save and close the aurora.properties file.5. Open each <server_name>-OpenPagesServer#-server.properties file in a text




b. Save and close each server.properties file.6. Open each <server_name>-OpenPagesServer#-sosa.properties file in a text editor,

such as vi. a. Edit the Application.url.path lines to point to the fully-qualified domain name of

the load balancer. For example:

application.url.path=https\://<op-load-balancer.domain.com>\:<port>/openpages

b. Save and close each server.properties file.



7. Open each <server_name>-InterstageBPMCS#-server.properties file in a text editor, such as vi. a. Edit the url.path lines to point to the fully-qualified domain name of the load



b. Save and close each server.properties file.8. Restart the IBM HTTP Web Server.

Task 7: Tailor the Load BalancerFor databases with a large dataset, some OpenPages reports may time out before completion. If you experience problems with reports timing out, you can adjust the keepalive time.

TimeOut. The number of seconds Apache will wait to receive a GET request. between receipt of TCP packets on a POST or PUT request and between ACKs on transmissions of TCP packets in responses.

KeepAliveTimeout. The number of seconds Apache will wait for a subsequent request before closing the connection.

Note: Use care when changing the keepalive time out value. A high value may cause performance problems if the higher time out causes server processes to wait for idle clients.

To change the time out values, use the following steps:

Steps

1. Log on to load-balancing Web server as a non-root user with administrative privileges. 2. Launch an AIX shell as a user with administrative privileges.

Note: Use a non-root, such as the user you created for the OpenPages installation, opuser.

3. Configure the time out values the httpd.conf file as follows:a. Navigate to the IBM HTTP Web Server configuration file, httpd.conf, by default:


b. Open httpd.conf in a text editor.c. Change the KeepAliveTimeout parameter to a higher value, for example:

KeepAliveTimeout 1800

d. Add the TimeOut parameter with the same value, for example:

TimeOut 1800

e. Save and close the file. f. Restart the IBM HTTP Web Server.



Load-balancing the OpenPages

• • • • • • • • • •Reporting Server

CommandCenter leverages the IBM Cognos software, which can scale horizontally. Scaling CommandCenter vertically within the same environment involves increasing the number of processes available to handle requests, and depending on the load, may involve configuring additional dispatchers. Scaling CommandCenter horizontally involves installing additional environments and registering the Cognos dispatchers so that the incoming requests will be distributed across the multiple environments.

The number of dispatchers you will need is dependent upon a number of factors, including the operating system (Windows or AIX), the system resources available, the number of users that will be using the system, and other such factors. Please refer to Cognos documentation for specific information on configuring dispatchers for your environment, such as IBM Cognos 8 Business Intelligence Architecture and Deployment Guide, available on the IBM Web site.

Note: This section describes how to configure a second CommandCenter instance in your OpenPages environment. To add more than two instances, contact OpenPages representative.

Configure Cognos Application FirewallThis task is required.

The IBM OpenPages GRC Platform Installer for CommandCenter enables the Cognos Application Firewall (CAF) by default. Use the IBM Cognos Configuration tool to add any associated OpenPages application servers, which will be considered “safe” for use by the Cognos software.

IMPORTANT! If CommandCenter is used in a clustered environment, perform these steps on the primary CommandCenter server.

Adding Servers to the Cognos Safe ListUse the following steps enable CAF and add servers to the list of safe domain names.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Start IBM Cognos Configuration:


b. Navigate to the following directory: <COGNOS_HOME>/bin64

c. Execute the following command:Windows cogconfig.bat

AIX ./cogconfig.sh

3. In the Explorer pane, locate IBM Cognos Application Firewall in the tree structure (Local Configuration > Security > IBM Cognos Application Firewall).

4. In the Properties pane, click the Valid domain names or hosts field and click the pencil icon that appears.

5. In the Valid domain or hosts dialog box that appears, click Add.6. Enter the names of all OpenPages application servers.7. Click OK when you have added all of the appropriate servers.



8. Save the configuration and restart the Cognos service. If you are using Windows Services to restart the Cognos service, the service will be listed as CommandCenter.

Comfigure Communication Between CommandCenter ServersIf you install CommandCenter on more than one computer, you must configure environment properties so that the distributed installations can communicate with each other:

The primary CommandCenter server must be configured as the “default active” server. All CommandCenter servers must know the location of the Content Store database. All CommandCenter servers must know the location of the other CommandCenter

servers. All CommandCenter servers must use the same cryptographic settings. All CommandCenter servers must have their system clock synchronized.

Configuring the Primary CommandCenter ServerIn a clustered environment, one CommandCenter server acts as the primary server and one or more CommandCenter server(s) act as the secondary server. The primary server may also be called the default active server.

Use the following steps to configure the primary CommandCenter server.

Steps:

1. Ensure that CommandCenter is not running on any server. 2. Start IBM Cognos Configuration on the reporting server that you want to designate as

the primary CommandCenter installation.

Tip: We recommend that you use the computer with the highest processor speed for the default active server.

3. In the Explorer pane, click Environment.4. In the Environment - Group Properties pane:

a. Click Gateway URI.b. In the Value field, change the localhost portion of the URL to the name of the

primary CommandCenter computer.5. In the Environment - Group Properties pane:

a. Click Dispatcher URI for Gateway.b. Click the pencil icon edit button next to the Value box to open the Value - Content

Manager URIs dialog box. c. In the Current Values list, change the localhost portion of the URL to the name

of the primary CommandCenter computer.d. For each additional CommandCenter computer, click the Add button.e. Change the localhost portion of the URL to the name of each additional

CommandCenter computer.f. Click OK.

6. In the Environment - Group Properties pane:a. Click Content Manager URIs.b. Click the pencil icon edit button next to the Value box to open the Value - Content




7. In the Explorer pane, under Security, click Cryptography.



8. In the Properties pane, under CSK settings:a. Ensure that Store symmetric key locally? is set to True. The key store must be

created on the default active CommandCenter computer.b. Set Store symmetric key locally? to True.

9. From the File menu, select Save.10. From the Actions menu, click Start.

As soon as CommandCenter starts, this computer becomes the default active CommandCenter computer.

Configuring Secondary CommandCenter ServersYou must complete this procedure for each secondary CommandCenter server.

Steps:

1. Ensure that CommandCenter is running on the primary CommandCenter server.2. Start IBM Cognos Configuration on the reporting server that will become a secondary

CommandCenter server.3. In the Explorer pane, click Environment.4. In the Environment - Group Properties pane:

a. Click Gateway URI.b. In the Value field, change the localhost portion of the URL to the name of the

primary CommandCenter computer.5. In the Environment - Group Properties pane:

a. Click Dispatcher URI for Gateway.b. Click the pencil icon edit button next to the Value box to open the Value - Content




6. In the Environment - Group Properties pane:a. Click Content Manager URIs.b. Click the pencil icon edit button next to the Value box to open the Value - Content




7. In the Explorer pane, under Security, click Cryptography.8. In the Properties pane, under CSK settings, set Store symmetric key locally? to

False.

Note: The key store is created on the primary CommandCenter computer. There can be only one key store in a load-balanced CommandCenter installation.

9. In the Explorer window, under Security, Cryptography, click Cognos, the default cryptographic provider.



10. Under the Certificate Authority settings property group:a. Set the Password property to match what you configured on the primary

CommandCenter server.b. Ensure that all other cryptographic settings match what you configured on the

primary CommandCenter computer.11. In the Explorer window, under Data Access, Content Manager, click Content Store

and ensure that the values for all of the properties match the primary CommandCenter computer.

12. From the File menu, select Save.13. From the Actions menu, click Start.

Configuring an Apache Load-balancer or Proxy ServerIf you are using an external proxy server for load balancing, you must add a proxy redirection directive (ProxyPass) to the httpd.conf file on the proxy server. Requests would be sent to the proxy server, which will redirect the request to the server specified in the httpd.conf file.

Steps:

1. Log on to the load-balancing server as a user with administrative privileges. 2. Launch a Command Prompt window (using the Run as Administrator option) or an

AIX shell.3. Navigate to the <Apache_Home>\conf\ directory.4. Open the httpd.conf file (the Apache configuration file) and add the following lines:

<Location /cognos8/> ProxyPass http://<reporting_server>/cognos8/ SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 </Location>

Where:

<reporting_server> is the name of the primary CommandCenter server.

/cognos8/ is the Cognos virtual directory

5. IMPORTANT! You must include the trailing forward slash in the ProxyPass directive, /cognos8/.


Example

<Location /cognos8/> ProxyPass http://perf-2008-dual5/c8/ SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 </Location>

7. Restart the CommandCenter servers. See “Changing the CommandCenter Host and Port Settings in OpenPages” on page 243.



Changing the CommandCenter Host and Port Settings in OpenPagesThis task is required.

If your OpenPages environment is

Use the following steps to modify the CommandCenter server name and port settings.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges.2. Open an Internet browser window and navigate to the OpenPages application:


3. Log in to the OpenPages application as a user with administrative privileges. 4. Perform the following steps:

a. Under Administration, select Settings.b. Expand the OpenPages | Platform | Reporting Schema | Object URL

Generator folder hierarchy.c. Click the Host setting to open its detail page.d. In the Value field, update the setting to point to the OpenPages server.

IMPORTANT! If you will be using this CommandCenter installation in a load-balanced environment, type the fully-qualified domain name of the server used for load balancing OpenPages. You may also need to change the port.

Restarting CommandCenter ServersAfter you configured all of the load-balanced CommandCenter servers, restart the CommandCenter servers, see “Starting and Stopping CommandCenter” on page 179.



C
Configuring SSL
This appendix describes how to configure your IBM OpenPages GRC Platform for use in an SSL (HTTPS) environment.

SSL (Secure Sockets Layer) establishes an encrypted link between the OpenPages application server and a user accessing the OpenPages through a browser. The encryption ensures that all data passed between the application server and a browser remains private.


About Configuring SSL on page 246 Checklist for Configuring SSL on page 247 Configuring OpenPages for SSL on page 248 Configuring OpenPages for SSL on a WebSphere Application Server on page 261 Configuring CommandCenter for SSL on page 267 Configuring a Load Balancer Running IBM HTTP Server on page 276


• • • • • • • • • •About Configuring SSL

SSL (Secure Sockets Layer) establishes an encrypted link between the OpenPages application server and a user accessing the OpenPages through a browser. The encryption ensures that all data passed between the application server and a browser remains private.

Configuring your application server for SSL requires creating cryptographic keys, then submitting the keys, with basic details to identify your organization, to a Certification Authority, who validates the details and issues a signed SSL Certificate for greater protection.

In general, configuring SSL on the OpenPages application server is different depending upon the platform. For a Windows/WebLogic Server environment, you can use Keytool to perform the tasks required; for an AIX/WebSphere Application Server environment, you can use the IBM Management Interface. For CommandCenter, you can use OpenSSL.

There are many different ways you can implement SSL in the OpenPages environment.

Configure SSL on a load balancer. If all HTTP traffic to and from the OpenPages environment passes through a load balancer, you can configure the load balancer to accept only SSL traffic and terminate the SSL connection on the load balancer. That server would pass the traffic through to OpenPages as non-SSL.

Configure SSL on the OpenPages application server(s) and/or a CommandCenter server(s). You can configure the OpenPages application server and/or a CommandCenter server to accept only SSL traffic.

Configure SSL on the OpenPages servers and the load balancer. You can configure the OpenPages environment to require SSL traffic between all systems by configuring SSL on the load balancer, all OpenPages nodes (on the cluster administrator and all cluster member) and all CommandCenter nodes.

About the SSL ProcessWhen you activate SSL on your web server, you start by creating a cryptographic key pair (a Private Key and a Public Key) and a file called a keystore where these keys will be stored. When creating the keys, you provide information about the identity of your company. Your web server then creates the two keys.

To validate the Public key, you send the key in a Certificate Signing Request (CSR) to a Certification Authority (CA), or you may act as the CA and self-sign the keys. The Certification Authority validates your details and issues an SSL Certificate containing the public key and your company information.

When an OpenPages user wants to access your OpenPages web server using a browser, the web server sends the certificate (with the private key) to that user. The user can verify that the certificate was issued by a trusted party (the CA).

The browser then uses your public key to encrypt all data to your web server. Your web server decrypts the data using its private key and encrypts all data it sends back to the user, which is then decrypted by the user’s browser.

All messages between the user and your web server will be encrypted using your key pair. Because only you have the Private key, only your web browser is able to decrypt the messages into your server.

Appendix C: Configuring SSL


• • • • • • • • • •Checklist for Configuring SSL

Use the following checklist to guide you through configuring SSL in your OpenPages environment. Each task below has several steps.

Table C-1: Checklist for Installing CommandCenter

Task Checklist

1. Configure SSL on the OpenPages application server:• Configure SSL in a WebLogic Server environment. See “Configuring OpenPages for SSL” on

page 248.• Configure SSL in a WebSphere Application Server environment. See “Configuring

OpenPages for SSL on a WebSphere Application Server” on page 261.

2. Configure SSL on the CommandCenter reporting server. See “Configuring CommandCenter for SSL” on page 267.

3. Configure SSL on the load balancer. See “Configuring a Load Balancer Running IBM HTTP Server” on page 276.



• • • • • • • • • •Configuring OpenPages for SSL

Perform the following tasks to configure the system for SSL, based on your application server softeware.

Configuring OpenPages for SSL in a WebLogic Server Environment Perform the following tasks to configure the OpenPages application and WebLogic Server for SSL.

“Generate a Keystore and Key Pair” on page 248 “Generate a Certificate Signing Request (CSR) File” on page 249 “Submit CSR to CA for Approval” on page 250 “Import Root and Signed Server Certificate(s)” on page 250 “Import the Root Certificate for Java” on page 251 “Install Required CA Certificates Using a Web Browser” on page 251 “Edit OpenPages Properties Files” on page 252 “Configure the Application Server” on page 253 “Configure a Clustered Environment for SSL” on page 255 “Enable and Disable Secure Session Cookies” on page 260

Task 1: Generate a Keystore and Key PairThis task is required and should be performed on the cluster administrator server.

The keytool command generates the required public and private key pair and stores both keys in a file called a keystore.

Use the following steps to generate the key pair and specify the keystore.

Steps:

1. Log on to the 6.0.1 cluster administrator server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option).3. Use the set PATH command to add the path to the directory where Java Keytool

program is located, by default: set PATH=<JAVA_HOME>\bin;%PATH%

4. Use the keytool command to generate the SSL key pair and keystore using the following command: keytool -genkey -keyalg <algortihm> -alias <keypair_name> -keypass <keypair_password> -keystore <keystore_name> -storepass <keystore_password> -validity <number_days>

Where:

• genkey generates the key pair (public and private key).• keyalg specifies the algorithm to use for the key pair. Either RSA or DSA.• alias is a unique identifying string for the key pair.• keypass specifies a password to access the key pair.• keystore is the name of the file where the key pair is stored.• storepass specifies a password to access the keystore.• validity specifies the number of days before the certificate expires.

Note: The key pair password (keypass) and the keystore password (storepass) can be the same value.



Example

The following command creates a key pair named opkeystore using the RSA format and stores the key pair in a file named opkeystore. The key pair password will be Kpassword and the keystore password will be Spassword.

keytool -genkey -keyalg RSA -alias opkeystore -keypass Kpassword -keystore opkeystore -storepass Spassword -validity 365

5. At the prompt, enter the keystore password you created above for the keystore:

Enter keystore password: Spassword

6. At the prompt, enter the following dname information as appropriate:

commonName (cn) organizationUnit (ou) organization (o) localityName (l) stateName (s) country (c)

where cn, ou, l, s, and c values are X.500 Distinguished Names.

7. At the prompt, confirm the dname information. Enter Yes if correct or No to re-enter.8. At the prompt, enter the password you created above for the key pair.

Enter key password for <keypair_name> Kpassword

This command creates the keystore named opkeystore.jks in the specified directory.

Task 2: Generate a Certificate Signing Request (CSR) FileThis task is required and should be performed on the cluster administrator server.

If you require an authorized certificate from a commonly-trusted third-party certificate authority, you can use the keytool command to generate the required certificate signing request.

Steps:

1. In the OpenPagesDomain directory on the cluster administrator, use the keytool command to generate a certificate signing request using the following command:

keytool -certreq -alias <keypair_name> -keystore <keystore_name> -sigalg <algoritm> -file <file_name>

Where:

• certreq generates the request.• alias is a unique identifying string for the key pair.• keystore is the name of the file where the key pair is stored.• keyalg specifies the algorithm to use for the key pair. Use the same algorithm

as used with keytool -genkey above.• sigalg specifies the algorithm to use for the key pair. Either RSA or DSA.• file specifies the name of the file to store the request.• validity specifies the number of days before the certificate expires.

Example

The following command creates a certificate request for the keypair opkeystore in the opkeystore.jks keystore using the SHA1withRSA algorithm. The request will be stored in a file named ca_cert_request.csr.

keytool -certreq -alias opkeystore -keystore opkeystore.jks -sigalg SHA1withRSA -file ca_cert_request.csr



2. At the prompt, enter the keystore password you created above for the keystore:

Enter keystore password: Spassword

3. At the prompt, enter the password you created above for the key pair:

Enter key password for <opkeystore> Kpassword

This command generates a certificate signing request you submit to a commonly trusted Certificate Authority using instructions from the CA.

Task 3: Submit CSR to CA for ApprovalSubmit your CSR file to an appropriate Certification Authority (CA). Follow the instructions provided by the CA.

Download the approved root and CA certificates to a local directory, such as the OpenPagesDomain directory. Make sure the certificates are named to distinguish the root from the CA certificate.

Task 4: Import Root and Signed Server Certificate(s)This task is required and should be performed on the cluster administrator and all cluster

member systems.

You must install a root certificate and a server certificate from a commonly trusted third-party certificate authority on each application server. You may also need to install an intermediate certificate on each application server.

The root certificate is certificate that contains the public key and has been verified by the CA. Your web server will send the root certificate to browsers trying to access that web server.

The server certificate is the certificate returned to you from the CA, based on the certificate request you generated.

You can use the keytool command to import the root and server certificates into the OpenPages environment.

Note: You need to import the root certificate for the CA before the server certificate can be imported.

Steps:

1. Log on to each OpenPages 6.0.1 server as a user with administrative privileges.2. Launch a Command Prompt window (using the Run as Administrator option).3. Navigate to the OpenPagesDomain directory in <OP_Home>, by default:

C:\<OP_Home>\OpenPagesDomain

4. Use the Keytool command within the OpenPagesDomain directory to import the root certificate using the following command:

keytool -import -alias <certificate_name> -trustcacerts -file <file_name> -keystore <keystore_name>

Where:

• import imports the certificate.• alias is the name of the certificate.• file specifies the name of the file to store the certificate.• keystore is the keystore associated with the certificate.

Example

The example imports the rootca certificate into the trustedcafilename.cer file.

keytool -import -alias rootca -trustcacerts -file trustedcafilename.cer -keystore opkeystore.jks



5. Use the Keytool command within the OpenPagesDomain directory to import the server certificate (.cer) or certificate chain (.p7b) using the following command: keytool -import -alias opkeystore -trustcacerts -file servercert.cer -keystore opkeystore.jks

6. Enter the password for the keystore.7. Enter Yes to trust the certificate.

Task 5: Import the Root Certificate for JavaThis task is required and should be performed on the cluster administrator and all cluster

member systems.

Use the keytool command to import the root and server certificates into the Java environment.

1. In the Command Prompt window, of the current system, navigate to the JAVA_HOME directory within the OpenPages Java install directory:

C:\<OP_Home>\Java\jdk1.6.0_20\jre\lib\security

2. Use the Keytool command to import the root certificate using the following command: keytool -import -alias <certificate_name> -trustcacerts -file <file_name> -keystore <keystore_name>

Where:

• import imports the certificate.• alias is the name of the certificate.• file specifies the name of the file to store the certificate.• keystore is the keystore associated with the certificatre.

Example

The following example imports the rootca certificate into the trustedcafilename.cer file. keytool -import -alias rootca -trustcacerts -file trustedcafilename.cer -keystore cacerts

3. Enter the password for the certificate, by default changeit.4. Enter Yes to trust the certificate.

Note: If you are using self-signed certificates (not issued by a known CA) for OpenPages and CommandCenter, you must import the self-signed root certificate from any CommandCenter server connected to the current OpenPages server. Use the Java keytool command to import the certificates into the <OP_Home>\jre\lib\security directory.


Task 6: Install Required CA Certificates Using a Web BrowserThis task is required and should be performed on the cluster administrator and all cluster

member systems. Also perform this step on any client systems that will access OpenPages.

Once you configure the web server for SSL, you must also configure any web browsers that will access that web server by importing the root certificate into the browser keystore. The following example is for Microsoft Internet Explorer.

Steps:

1. On any system that needs to access the OpenPages environment, open a Web browser.2. Click Tools | Internet Options.3. Click the Content tab, then click the Certificates button. 4. Click the Trusted Root Certification Authority tab, then click the Import button to

launch the Certificate Import Wizard.



5. On the Certificate Import Wizard Welcome screen, click Next.6. On the File to Import screen:

a. Enter the path to the root certificate, as follows: C:\<OP_Home>\OpenPagesDomain\root-certificate.cer

b. Click Next. 7. On the Certificate Store screen:

a. Select Place all certificates in the following store. b. The Trusted Root Certification Authorities should appear in the Select

Certificate Store field. If not, click Browse to select. c. Click Next.

8. On the Completing the Certificate Import Wizard screen, review the settings and click Finish.

Task 7: Edit OpenPages Properties FilesThis task is required and should be performed on the cluster administrator and all cluster

member systems.

After configuring the web server to require SSL, you need to edit OpenPages properties files to require browsers to use HTTPS protocol and the OpenPages SSL ports.

Steps:

1. Log on to each OpenPages 6.0.1 server as a user with administrative privileges.2. Open Command Prompt window (using the Run as Administrator option).3. Navigate to the following directory:

<OP_Home>\aurora\conf

4. Open the aurora.properties in a text editor, such as WordPad.5. Edit the following lines to change the http to https and update the port number:

application.url.path=http\://<server_name>\:<port>/openpages

cognos.server=http\://<server_name>\:<port>/cognos8/cgi-bin/cognos.cgi

logout.url.cognos=http\://<server_name>\:<port>/cognos8/cgi-bin cognos.cgi?b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

Note: In a load balanced environment, application.url.path value will be the fully-qualified domain name of the load balancer and port.

Example

Change: application.url.path=http\://OP601server\:7009/openpages cognos.server=http\://CC601server\:80/cognos8/cgi-bin/cognos.cgi logout.url.cognos=http\://CC601server\:80/cognos8/cgi-bin cognos.cgi?b_action\=xts.run&m\=portal logoff.xts&h_CAM_action\=logoff

to: application.url.path=https\://OP601server\:7010/openpages cognos.server=https\://CC601server\:80/cognos8/cgi-bin/cognos.cgi logout.url.cognos=https\://CC601server\:<port>/cognos8/cgi-bin/ cognos.cgi?b_action\=xts.run&m\=portal logoff.xts&h_CAM_action\=logoff




7. Open the sosa.properties in a text editor, such as WordPad.8. Edit the following lines to change the http to https and update the port number:

application.url.path= http://<server>:\<port>

Example

Change application.url.path=http\://qe-vm04\:7009/openpages to application.url.path=https\://qe-vm04\:7010/openpages

Note: In a load balanced environment, this value will be the fully-qualified domain name of the load balancer and port.

9. Save and close the file.10. Open each <server_name>-OPNode#Server#-server.properties in a text editor, such

as WordPad or vi.a. Edit the following lines to change the http to https and update the port number:

url.path.workflow.admin=http\://<server>:<port> url.path.openpages=http\://<server>:<port>

Example

Change url.path.workflow.admin=http\://qe-vm04\:49951/ibpmconsole to url.path.workflow.admin=https\://qe-vm04\:49952/ibpmconsole


b. Save and close the file.11. Open each <server_name>-IBPMNode#Server#-server.properties in a text editor,

such as WordPad or vi.a. Edit the following lines to change the http to https and update the port number:

url.path.workflow.admin=http\://<server>:<port> url.path.openpages=http\://<server>:<port>

Example

Change url.path.workflow.admin=http\://qe-vm04\:49951/ibpmconsole to url.path.workflow.admin=https\://qe-vm04\:49952/ibpmconsole


b. Save and close the file.

Task 8: Configure the Application ServerThis task is required and should be performed on the cluster administrator and all cluster

member systems.

All OpenPages application servers should be configured to use the opkeystore.jks keystore created in the previous section. By default, the application server contains default keystores which should not be used in a production environment. You can use the Oracle WebLogic Server Administrative Console to configure WebLogic Server to use only the opkeystore.jks keystore.

Steps:

1. On the current system, open a web browser.2. Navigate to the Oracle WebLogic Administration Console:


where <server_name> is the name of the application server and <port> is the WebLogic Server port assigned during installation, by default 7001.

3. Log in to the WebLogic Administration Console as with an administrator account. 4. Expand the Environment tree in the Domain Structure section and click Servers.



5. Click the Lock & Edit button in the Change Center to make the settings available for editing.

6. On the Summary of Servers page, click the server you want to configure.7. On the Settings for {Server_Name} page, click the Configuration tab.8. On the General tab, make sure that the SSL Listen Port Enabled option is selected

and the correct listener port is listed (7002 by default) in the SSL Listen Port field.9. On the Configuration tab, click the Keystores tab.10. On the Keystores tab, select Custom Identity and Custom Trust in the Keystores

list.11. Under Identity, enter the following:

12. Under Trust, enter the following:

13. Click Save.14. On the SSL tab, select Keystores from the Identity and Trust Locations list. 15. Set the following values:

16. Click Save.17. Repeat this process for each server you want to access through SSL.

Field Description

Custom Identity Keystore Type the path to the opkeystore.jks keystore.

C:\<OP_Home>\OpenPagesDomain\ opkeystore.jks

Custom Identity Keystore Type Type JKS for keystore type.

Custom Identity Keystore Passphrase Type the keystore password, for example: Spassword.

Confirm Custom Identity Keystore Passphrase

Re-type Spassword.

Field Description

Custom Trust Keystore Type the path to the opkeystore.jks keystore, by default:

C:\<OP_Home>\OpenPagesDomain\ opkeystore.jks

Custom Trust Keystore Type Type the type of keystore. Enter JKS.

Custom Trust Keystore Passphrase

Type the keystore password, for example: Spassword.

Confirm Custom Trust Keystore Passphrase

Re-type Spassword.

Field Description

Private Key Alias Enter the private key alias you entered when generating the certificate signing request, by default opkeystore.

Private Key Passphrase Type the private key password you entered when generating the certificate signing request, by default Kpassword.



18. Optionally, you may ensure that hostname verification is active. Hostname verification, active by default, ensures the host name in the URL to which the client connects matches the host name in the digital certificate. Check the status as follows:a. In the WebLogic Administration Console, click Home.b. Expand the Environment tree in the Domain Structure section and click

Servers.c. On the Summary of Servers page, click the server you want to configure.d. On the SSL tab, click Advanced.e. The BEA Hostname Verifier is the default behavior. If this behavior is selected, the

host name in the certificate must match the actual host name.f. Repeat these steps for each server.

19. When done configuring all servers, click the Activate Changes button in the Change Center to implement the changes.

Task 9: Configure a Clustered Environment for SSLIf your OpenPages environment uses an Apache-based load balancer to pass traffic to OpenPages, you must add new parameters to the httpd.conf file and change some existing parameters.

The following steps configure an Apache-based load balancer:

Steps:

1. Log on to load-balancing Web server as a user with administrative privileges. 2. Stop the Apache Web Server, if running.3. Launch a Command Prompt window (using the Run as Administrator option).4. Copy the <WL_Home>\server\plugin\win\32\mod_wl_22.so file to the

<Apache_Home>\modules directory.

Example

copy C:\Oracle\Middleware\wlserver_10.3\server\plugin\win\32\mod_wl_22.so “C:\Program Files\Apache Software Foundation\Apache2.2\conf”

5. Navigate to the <Apache_Home>\conf\ directory.6. Open the httpd.conf file (the Apache configuration file) and locate the parameters

added to the end of the file for SSL. See an example of all of these parameters below.a. Add the following parameters before the first <Location /> parameter.

<IfModule ssl_module> SSLRandomSeed startup builtin SSLRandomSeed connect builtin </IfModule>

<Location /> SetHandler weblogic-handler SecureProxy ON </Location>

b. In the <Location /> parameter, add the path to the trusted CA certificate file as shown in bold, for example: "C:\OPKeystore\rootca.cer".

<Location /> SetHandler weblogic-handler SecureProxy ON TrustedCAFile <Path_to_Certificate> </Location>

c. In the <Location /console> parameter, change the WebLogic Server port to the WebLogic SSL port as shown in bold, for example 7010.

<Location /console> SetHandler weblogic-handler



MaxPostSize 0 WLLogFile logs/weblogic_console.log WebLogicHost <SERVER>.<DOMAIN>.COM WebLogicPort <SSL_PORT> </Location>

Note: This parameter was added during the cluster configuration, described in the “Configuring Clustered Environments” chapter.

d. Change all instances of the WebLogicCluster port to the WebLogic Server SSL port as shown in bold.

<Location /opws> WLCookieName opapp SetHandler weblogic-handler MaxPostSize 0 KeepAliveEnabled ON KeepAliveSecs 1800 WLLogFile logs/openpages_webservices.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<SSL_PORT>,<SERVER>.<DOMAIN>.COM:<SSL_PORT> </Location>

<Location /openpages> WLCookieName opapp SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile /logs/openpages.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<SSL_PORT>,<SERVER>.<DOMAIN>.COM:<SSL_PORT> </Location>

<Location /ibpmconsole> WLCookieName opibpm SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile logs/ibpmconsole.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<SSL_PORT>,<SERVER>.<DOMAIN>.COM:<SSL_PORT> </Location>

Note: These parameters were added during the cluster configuration, described in the “Configuring Clustered Environments” chapter

e. In the <Location /ibpmweblogicconsole> parameter, change the WebLogic port to the WebLogic SSL port as shown in bold.

<Location /ibpmweblogicconsole> SetHandler weblogic-handler MaxPostSize 0 WLLogFile logs/ibpmweblogic_console.log WebLogicHost <SERVER>.<DOMAIN>.COM WebLogicPort 49902 </Location>

Note: This parameter was added during the cluster configuration, described in the “Configuring Clustered Environments” chapter

f. Save and close the httpd.conf file.



7. Restart the Apache Web Server using the Windows Start menu, for example: Start | All Programs | Apache HTTP Server 2.2 | Control Apache Server | Restart.

This will open a console window and start the Apache Web Server running inside it. Closing this console window will terminate the Apache Web Server.

Example

The following is an example of the modified parameters in the httpd.conf file on a load-balanced web server in an SSL environment, based changes described in the steps above.


<Location /> SetHandler weblogic-handler SecureProxy ON TrustedCAFile "C:\OPKeystore\rootca.cer" </Location>



<Location /console> SetHandler weblogic-handler MaxPostSize 0 WLLogFile logs/weblogic_console.log WebLogicHost qe-vm11.openpages.com WebLogicPort 7002 </Location>

<Location /opws> WLCookieName opapp SetHandler weblogic-handler MaxPostSize 0 KeepAliveEnabled ON KeepAliveSecs 1800 WLLogFile logs/openpages_webservices.log WebLogicCluster qe-vm11.openpages.com:7010,qe-vm11.openpages.com:7012, qe-vm14.openpages.com:7010,qe-vm14.openpages.com:7012 </Location>

<Location /openpages> WLCookieName opapp SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WebLogicCluster qe-vm11.openpages.com:7010,qe-vm11.openpages.com:7012, qe-vm14.openpages.com:7010,qe-vm14.openpages.com:7012 </Location>



<Location /ibpmconsole> WLCookieName opibpm SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile logs/ibpmconsole.log WebLogicCluster qe-vm11.openpages.com:49952,qe-vm11.openpages.com:49954,qe-vm14.openpages.com:49952, qe-vm14.openpages.com:49954 </Location>

<Location /ibpmweblogicconsole> SetHandler weblogic-handler MaxPostSize 0 WLLogFile logs/ibpmweblogic_console.log WebLogicHost qe-vm11.openpages.com WebLogicPort 49902 </Location>



Task 10: Enable and Disable Secure Session CookiesA secure session cookie tells the browser to only send the session cookie back over an encrypted HTTPS connection. This ensures that the cookie identifier is secure and should only be used with OpenPages when using HTTPS connections. When this feature is enabled, session cookies over an HTTP connection no longer work.

To enable or disable secure session cookies on the Oracle WebLogic application server, you must modify the weblogic.xml file in the \sosa\WEB-INF and \openpages\WEB-INF directories on all application servers in your environment as follows.

Steps:

1. Navigate to the weblogic.xml file in the \sosa\WEB-INF directory as follows: <OP_HOME>\applications\op-apps\sosa\WEB-INF

Where: <OP_HOME> is the installation location of the OpenPages application.

2. Make a back up copy of the weblogic.xml file by copying it to a safe location.3. Edit the weblogic.xml file as follows:

a. Open the weblogic.xml file in a text editor of your choice.b. Do one of the following:

<session-param> <param-name>CookieSecure</param-name> <param-value>true</param-value> </session-param> <session-param> <param-name>URLRewritingEnabled</param-name> <param-value>false</param-value> </session-param>

c. Save and close the file.4. Repeat Steps 2 and 3 for the weblogic.xml file located in the \openpages\WEB-INF

directory as follows:

<OP_HOME>\applications\op-apps\openpages\WEB-INF

5. If you have a clustered environment, repeat steps 1 through 4 on all application servers in your cluster.

To do this... Under the <session-descriptor> element, do this...

Enable secure session cookies Add the following code

Disable secure session cookies Remove the following code



Configuring OpenPages for SSL on a WebSphere Application ServerPerform the following tasks to prepare your OpenPages application and WebSphere Application Server for SSL:

“Verify WebSphere Application Server Configured for SSL” on page 261 “Verify SSL Ports to Virtual Hosts Configured” on page 262 “Create the Keystore” on page 262 “Generate a Certificate Signing Request (CSR) File” on page 263 “Submit the CSR to CA for Approval” on page 263 “Import Signed CA Certificates” on page 263 “Import the CA Certificate for Java” on page 264 “Configure the SSL for OpenPages” on page 265 “Enable and Disable Secure Session Cookies” on page 265

Task 1: Verify WebSphere Application Server Configured for SSL

This task is required and should be performed on the cluster administrator system.

WebSphere Application Server uses the concept of transport chains (multiple transport channels) to handle web traffic. Use the IBM WebSphere Administration Console to make sure the Web Container Transport Chains are configured for SSL.

Steps:

1. Log on to 6.0.1 cluster administrator server as a user with administrative privileges.2. Navigate to the IBM WebSphere Administration Console:


where <server_name> is the name of the application server and <port> is the WebSphere Application Server port assigned during the WebSphere Application Server installation (9060 by default).

3. Log in to the IBM WebSphere Administration Console as with an administrator account. 4. Expand the tree for Servers | Server Types | WebSphere Application servers in

the left panel.5. In the Application servers list, click the server you want to configure.6. Under Container Settings, click the Web Container Settings | Web Container

Transport Chains.7. For the WCInboundDefaultSecure chain (the chain used for incoming SSL traffic),

ensure that the Enabled field states Enabled and the SSL Enabled field states Enabled. If not:a. Click the WCInboundDefaultSecure resource.b. On the General Properties tab, select Enable to enable the resource.

8. Click Save to save your changes.



Task 2: Verify SSL Ports to Virtual Hosts ConfiguredThis task is required and should be performed on the cluster administrator system.

The IBM OpenPages GRC Platform Installer added the OpenPages SSL ports added to the list of host aliases in the IBM WebSphere Administration Console. Check that all the appropriate ports were added. If you have four OpenPages nodes and four workflow nodes, there should be ports for all eight nodes.

Steps:

1. In the IBM WebSphere Administration Console, on the cluster administrator, expand the tree for Environment | Virtual Hosts in the left panel.

2. Select default_host.3. On the Host Aliases page, check the SSL ports listed. These ports were added by the

IBM OpenPages GRC Platform Installer. Determine if any SSL ports are needed. If you have four OpenPages nodes and four workflow nodes, you will need to enter all eight nodes.

For example, if the OpenPages and workflow application SSL ports are not listed, add port 10111 for the OpenPages application or port 20111 for the workflow application.

For information on locating port numbers, see “Port Assignments and Servers List” in Chapter 3 on page 44.

Note: OpenPages and workflow server admin consoles run on different port numbers, by default: 9060 and 9061 respectively

4. If any SSL ports are absent, click New.5. On the Configuration page, enter the port number in the Port field and optionally

enter a name in the Host Name field. 6. Click OK. 7. On the Host Aliases page, click Save.

Task 3: Create the KeystoreThis task is required and should be performed on the cluster administrator system.

Use the IBM WebSphere Administration Console to create the required public and private key pair and store both keys in a file called a keystore.

Steps:

1. In the IBM WebSphere Administration Console, on the cluster administrator, expand the tree for Security | SSL certificate and key management in the left panel.

2. On the SSL certificate and key management page, click the Key stores and certificates link in the Related Items list.

3. On the SSL Certificates and key management page, click New.4. On the Key store and certificates page, enter the following values:

• Name. Enter OPKeystore for the name for the keystore.• Management scope. Select (cell):OpenPagesCell.• Path. Enter a path in <OP_Home> where the keystore will be created, such as /

opt/OpenPages/Keystore.• Password. Enter a password for the keystore, by default Spassword.• Type. Select JKS.

5. Click Apply.



Task 4: Generate a Certificate Signing Request (CSR) FileThis task is required and should be performed on the cluster administrator system.

If you require an authorized certificate from a commonly-trusted third-party certificate authority, you can use the IBM WebSphere Administration Console to generate the required certificate signing request.

Steps:

1. In the IBM WebSphere Administration Console, on the cluster administrator, open the Key store and certificates page.

2. Click Personal certificate requests in the Additional Properties list to create a certificate request. The list becomes active after you click Apply.

3. On the Personal certificates requests page, click New.4. Enter the following values:

• Name. Enter a name for the certificate request, for example ServerCertificateRequest.cer.

• Key label. Enter a label for the certificate, for example, use the server name.• Common name. Enter a name for the certificate and any other identifying

information.5. Click Apply and OK. 6. Click Save.

Task 5: Submit the CSR to CA for ApprovalSubmit your CSR file to an appropriate Certification Authority (CA). Follow the instructions provided by the CA.

Download the approved root and CA certificates to a local directory. Make sure the certificates are named to distinguish the root from the CA certificate.

Task 6: Import Signed CA CertificatesThis task is required and should be performed on the cluster administrator and all cluster

member systems.

You must install a root certificate and a server certificate from a commonly trusted third-party certificate authority on each application server. You may also need to install an intermediate certificate on each application server. You can use the IBM WebSphere Administration Console to import these certificates.

Steps:

1. Log on to each OpenPages 6.0.1 server as a user with administrative privileges.2. Launch a Web browser and navigate to the IBM WebSphere Administration Console:


where <server_name> is the name of the application server and <port> is the WebSphere Application Server port assigned during the WebSphere Application Server installation (9060 by default).

3. Log in to the IBM WebSphere Administration Console as with an administrator account. 4. Expand the tree for Security | SSL certificate and key management in the left

panel.5. On the SSL certificate and key management page, click the Key stores and

certificates link in the Related Items list.6. In the Application servers list, click the server you want to configure.7. Under Additional Properties, select Signer certificates.8. On the Signer Certificate page, click Add.



9. On the General Properties page, enter the following values:• Alias. Enter the name used to identify the Root CA certificate in the keystore.• File name. Enter the full path to the Root CA certificate.• Data type. Select Base64-encoded ASCII data from the list.

10. Click Apply and OK. 11. Click Save.12. Repeat these steps to import the server certificate.

Task 7: Import the CA Certificate for JavaThis task is required and should be performed on the cluster administrator and all cluster

member systems.

Use keytool to import the CA certificate into the Java JRE environment.

Steps:

1. Log on to each OpenPages 6.0.1 server as a user with administrative privileges.2. Launch an AIX shell.3. Navigate to the following directory within the OpenPages Java install directory:

<WebSphere_Home>/Java/jdk1.6.0_20/jre/lib/security

4. Use the Keytool command to import the root certificate using the following command:


Where:

• import imports the certificate.• alias is the name of the certificate.• file specifies the name of the file to store the certificate.• keystore is the keystore associated with the certificate.

Example

The following example imports the rootca certificate into the trustedcafilename.cer file.

keytool -import -alias rootca -trustcacerts -file trustedcafilename.cer -keystore cacerts

5. Enter the password for the certificate, by default changeit.6. Enter Yes to trust the certificate.

Note: If you are using self-signed certificates (not issued by a known CA) for OpenPages and CommandCenter, you must import the self-signed root certificate from any CommandCenter server connected to the current OpenPages server. Use the Java keytool command to import the certificates into the <OP_Home>/jre/lib/security directory.




Task 8: Configure the SSL for OpenPagesThis task is required and should be performed on the cluster administrator system.

The WebSphere Application Server server should be configured to use the opkeystore.jks keystore. You can use the IBM Console Web Application to configure WebSphere Application Server to use only the opkeystore.jks keystore.

Steps:

1. Log on to 6.0.1 server cluster administrator server as a user with administrative privileges.

2. In the IBM WebSphere Administration Console, expand the tree for Security | SSL certificate and key management in the left panel.

3. On the SSL certificate and key management page, click the SSL Configurations link in the Related Items list.

4. On the SSL Configurations page, click CellDefaultSSLSettings. 5. On the General Properties page, set the following values:

• Trust store name. Select opkeystore.jks• Key store name. Select opkeystore.jks• Management scope. Select (cell):OpenPagesCell.

6. Click Get certificate aliases.7. Click Apply and OK.8. On the SSL configurations page, select NodeDefaultSSLSettings.9. On the General Properties page, set the following values:

• Trust store name. Select opkeystore.jks• Key store name. Select opkeystore.jks

Task 9: Enable and Disable Secure Session CookiesA secure session cookie tells the browser to only send the session cookie back over an encrypted HTTPS connection. This ensures that the cookie identifier is secure and should only be used with OpenPages when using HTTPS connections. When this feature is enabled, session cookies over an HTTP connection no longer work.


To enable or disable secure session cookies on the WebSphere application server, you must enable or disable the Restrict cookies to HTTPS sessions setting on all application servers in your environment as follows.

Steps:

1. Open a browser window and log on to the IBM WebSphere Integrated Solutions Console as a server administrator with the proper permissions.

By default, the URL is http://<server_name>:<port>/ibm/console

Where:

<server_name> is the name of the application server

<port> is the port number associated with the application server (for example, 9060).

2. In the left panel of the Integrated Solutions Console, do the following:a. Expand the tree for Servers | Server Types.b. Click the WebSphere application servers link in the list.

3. In the list on the Application servers page, click the name of the application server you want to configure.

4. On the Application servers > OpenPages-server-name page, click the Configuration tab.



5. Under the Container Settings heading on the Configuration tab, click the Session management link.

6. On the Application servers > OpenPages-server-name > Session management page, do the following:a. Verify that the Enable cookies setting is selected. If not selected, select the check

box to enable the link for the setting.b. Click the Enable cookies link.c. On the Application servers > OpenPages-server-name > Session

management > Cookies page, configure the Restrict cookies to HTTPS sessions setting as follows:

7. When finished, click Apply.8. Repeat Steps 5-8 for all available application servers.

To do this... Then do this...

Enable secure session cookies Select the Restrict cookies to HTTPS sessions check box.

Disable secure session cookies Clear the Restrict cookies to HTTPS sessions check box.



• • • • • • • • • •Configuring CommandCenter for SSL

The following steps to configure CommandCenter to use Secure Socket Layer (SSL) transactions to communicate with the OpenPages application.

In a standard CommandCenter environment, all traffic to and from CommandCenter passes through a web server. You can configure the web server to require SSL, which passes the authenticated messages to CommandCenter.

Based on your web server, IIS or Apache, perform the following procedures to configure SSL on your web server.

“Configuring an IIS Web Server for SSL — Windows only” on page 267 “Configuring an Apache Web Server for SSL — Windows and AIX” on page 271 “Edit OpenPages Properties Files — Windows and AIX” on page 273 “Update Cognos Gateway URL's — Windows and AIX” on page 274 “Import the Root Certificate into Java Keystore — Windows and AIX” on page 275

Note: Make sure that JRE 1.6 or greater is installed on the reporting servers.

Configuring an IIS Web Server for SSL — Windows onlyThe information in this topic applies only to Windows environments.

Perform these tasks for the web server on any reporting server that will handle external CommandCenter traffic.

“Add Certificate Snap-In to IIS” “Generate Key Pair and Request” “Submit CSR to CA for Approval” “Import the Root Certificate” “Add SSL Binding for IIS”

Task 1: Add Certificate Snap-In to IISThis task is required and should be perfomed on the primary CommandCenter system

and all secondary CommandCenter systems.

IIS requires a certificates snap-in in order to work with certificates.

Steps:

1. Log on to each CommandCenter server as a user with administrative privileges. 2. Launch the Microsoft Management Console (MMC) as follows:

a. Click the Windows Start menu.b. Type mmc in the Search Programs and Files field and press Enter.

3. In the MMC dialog box, click File | Add/Remove Snap-Ins.4. In the Available snap-ins list, double-click Certificates.5. In the Certificates Snap-ins dialog box:

a. Select Computer account.b. Click Next.

6. In the Select Computer dialog box:a. Select Local Computer.b. Click Finish.

7. Click OK to close the dialog box.



Task 2: Generate Key Pair and RequestThis task is required and should be perfomed on the primary CommandCenter system.


1. Log on to the primary CommandCenter server as a user with administrative privileges.2. In the MMC dialog box on the reporting server, expand the Certificates tree and select

Personal.3. In the Actions panel, right-click the Certificates icon and select All Tasks | Advanced

Options | Create Custom Request. 4. In the Certificate Enrollment dialog box, click Next.5. On the Select Certificate Enrollment Policy pane:

a. Select Proceed without enrollment policy. b. Click Next.

6. On the Custom request pane:a. Accept the default values (CNG key and PKCS#10).b. Click Next.

7. In the Certificate Information pane:a. Click the Details icon.b. Click the Properties button that appears.

8. In the Certificate Properties dialog box, click the Subject tab to supply details for the certificate Distinguished Name. Specify at least a common name and organization value.a. Select Common Name in the Type list and enter a value for the certificate

common name.b. Click Add.c. Select Organization in the Type list and enter a value for the certificate common

name.d. Click Add.

9. Click the Private Key tab and perform the following:a. Click the arrow next to Key Options.b. Select the Make private key exportable.c. Click the arrow next to Select Hash Algorithm.d. Select sha1 from the Hash Algorithm list.e. Click OK.

10. In the Certificate Information pane, click Next.11. In the Certificate Enrollment pane:

a. Click Browse.b. In the Save as dialog box, enter a name for the certificate request file in the File

name field. Use a .csr extension.c. Select All Files from the Save as type list.d. Click the Save button.

12. Click Finish.13. Close the Microsoft Management Console.


Download the approved root and server certificates to a local directory. Make sure the certificates are named to distinguish the root from the server certificate.



Task 4: Import the Root CertificateThis task is required and should be perfomed on the primary CommandCenter system


Import the root certificate into IIS

Steps:

1. Log on to each CommandCenter server as a user with administrative privileges. 2. Launch the Microsoft Management Console (MMC) as follows:

a. Click the Windows Start menu.b. Type mmc in the Search Programs and Files field and press Enter.

3. In the MMC dialog box, click File | Add/Remove Snap-Ins.4. In the Available snap-ins list, double-click Certificates.5. In the Certificates Snap-ins dialog box,

a. Select Computer account.b. Click Next.

6. In the Select Computer dialog box:a. Select Local Computer.b. Click Finish.

7. Click OK to close the dialog box.8. In the MMC dialog box, expand the Certificates tree and select Trusted Root

Certification Authorities.9. In the Actions panel, right-click the Certificates icon and select All Tasks | Import. 10. In the Certificate Import Wizard, click Next.11. On the File to Import pane:

a. Click Browse to locate the CA certificate.b. Click Next.

12. On the Certificate Store pane:a. Select Place all certificates in the following store.b. Select Trusted Root Certification Authorities from the list.c. Click Next.

13. On the Completing the Certificate Import Wizard screen, click Finish.14. Repeat these steps to import any intermediate certificates required by your CA.

Note: If you are using self-signed certificates (not issued by a known CA) for OpenPages and CommandCenter, you must import the OpenPages self-signed root certificate from any OpenPages server connected to the current CommandCenter server. Use the Java keytool command to import the certificates into the <OpenPages_Home>\Cognos\cognos\c8\bin64\jre\1.5.0\lib\security directory.




Task 5: Add SSL Binding for IISThis task is required and should be perfomed on the primary CommandCenter system and

all secondary CommandCenter systems.

Use the following steps to bind the root certificate to the web server.

1. On the CommandCenter server, launch the Windows Internet Information Services Manager, by clicking the Start menu, then selecting Administrative Tools | Internet Information Services Manager.a. Expand the tree for the server you want to configure and select Sites.b. In the Sites pane, select the Web site you want to configure.c. In the Action panel, select Bindings.d. In the Site Bindings dialog box, select HTTPS.e. Click Edit.

2. In the Edit Site Binding dialog box:a. Select the server certificate imported in previous step in the SSL Certificates list,

do not select the self-signed server certificate. b. Click OK.

3. In the Site Bindings dialog box, click Close.4. Close the Internet Information Services Manager.

At this point, the IIS web server has been fully configured for IIS. Next, you must configure CommandCenter to use the OpenPages HTTPS address and SSL port. See “Edit OpenPages Properties Files — Windows and AIX” on page 273.



Configuring an Apache Web Server for SSL — Windows and AIXThe information in this topic applies only to AIX and Windows environments.

Perform these steps for the web server on any reporting server that will handle external CommandCenter traffic.

“Generate Key Pair and Request” “Submit CSR to CA for Approval” “Import the CA Certificates” “Install the CommandCenter Certificate into OpenPages”

Task 1: Generate Key Pair and RequestThis task is required and should be perfomed on the primary CommandCenter system.


Steps:

1. Log on to the reporting server as a user with administrative privileges.

Note: Log in as a non-root user, such as the user you created for the OpenPages installation, for example: opuser.

2. Open an AIX shell.3. Navigate to the \bin directory in the web server home directory to use as the keystore.4. Enter the following command to generate a certificate request:5. Windows

openssl req -new -sha1 -newkey rsa:1024 -config %APACHE_HOME%\conf\openssl.cnf -nodes -keyout server_pkey.key -out certreq.csr

AIX

openssl req -new -sha1 -newkey rsa:1024 -config $APACHE_HOME\conf\openssl.cnf -nodes -keyout server_pkey.key -out certreq.csr

6. Open the httpd.conf file using a text editor such as Notepad or vi.7. Uncomment following line in the file.-

LoadModule ssl_module modules/mod_ssl.so Secure (SSL/TLS) connections Include conf/extra/httpd-ssl.conf






Task 3: Import the Root CertificateThis task is required and should be perfomed on the primary CommandCenter system and

all secondary CommandCenter systems.

Import the root certoificate into Apache.

Steps:



2. Open Command Prompt window (in Administrator mode) or an AIX shell.3. Navigate to the <Apache_Home>/conf/extra directory.4. Open the http-ssl.conf file in a text editor.5. Under Server Certificate:

a. Uncomment the SSLCertificateFile parameter.b. Enter the path to the PEM encoded certificate.

6. Under Server Private Key: a. Uncomment the SSLCertificateKeyFile parameter.b. Enter the path to the keyfile on this server.

7. Under Certificate Authority (CA): a. Uncomment the SSLCACertificateFile parameter.b. Enter the path to the root certificate.c. Save and close the file.

Note: If you are using self-signed certificates (not issued by a known CA) for OpenPages and CommandCenter, you must import the OpenPages self-signed root certificate from any OpenPages server connected to the current CommandCenter server. Use the Java keytool command to import the certificates into the following directories:

<OpenPages_Home>/Cognos/cognos/c8/bin64/jre/1.5.0/lib/security

<OpenPages_Home>/Cognos/cognos/c8/bin/jre/1.5.0/lib/security




Task 4: Import the Server CertificateThis task is required and should be perfomed on the primary CommandCenter system


Import the server certificate from the CA into Apache.

Steps:



2. Open Command Prompt window (in Administrator mode) or an AIX shell.3. Navigate to the <Apache_Home>/conf/extra directory.4. Open the http-ssl.conf file in a text editor.5. Under Server Certificate:


6. Under Server Private Key: a. Uncomment the SSLCertificateKeyFile parameter.b. Enter the path to the keyfile on this server.


At this point, the IIS web server has been fully configured for IIS. Next, you must configure CommandCenter to use the OpenPages HTTPS address and SSL port. See “Edit OpenPages Properties Files — Windows and AIX” on page 273.

Edit OpenPages Properties Files — Windows and AIXThis task is required and should be performed on the primary CommandCenter system


If OpenPages is configured to require SSL, you must configure CommandCenter to use the OpenPages HTTPS address and SSL port.

Editing Properties FilesUse the following steps to modify CommandCenter properties files for SSL.

Steps:

1. Log on to each CommandCenter server as a user with administrative privileges.

Note: For AIX installs, you log in as a non-root user, such as the user you created for the OpenPages installation, for example: opuser.


3. Navigate to the following directory.

Windows

C:\<Cognos_Home>\Configuration

AIX

/opt/<Cognos_Home>/Configuration

4. Open the OpenPagesSecurityProvider_OpenPagesSecurityRealm.properties in a text editor, such as WordPad or vi.



5. Edit the following line to replace http with https and change the <port> to the SSL port: Openpages.application.url= http://…<port>/openpages

Update Cognos Gateway URL's — Windows and AIXThis task is required and should be performed on the primary CommandCenter system


You must configure Cognos software to use the OpenPages HTTPS address and SSL port.

Configuring Cognos for SSLUse the following steps to modify Cognos for SSL.

Steps:

1. On the CommandCenter server, start IBM Cognos Configuration: a. In the Command Prompt window or AIX shell, navigate to the following directory:

<COGNOS_HOME>/bin64

b. Execute the following command:

Windows

cogconfig.bat

AIX

./cogconfig.sh

2. In the Explorer pane, click Environment3. In the Properties pane, 4. Change the Controller URI for Gateway URI value to replace http with https and

change the <port> to the SSL port.5. Click File | Save to save the changes.



Import the Root Certificate into Java Keystore — Windows and AIXThis task is required and should be performed on the primary CommandCenter system


You must import the root certificate into the Java environment.

Importing Root CertificatesUse the following steps to import the root certificate into CommandCenter.

Steps:

1. On the CommandCenter server, launch a Command Prompt window (using the Run as Administrator option) or AIX shell as a user with administrative privileges.

2. Navigate to the following folders. Import the certificate into both of the following:

Windows:

C:\<Cognos_Home>\bin\jre\1.5.0\lib\security C:\<Cognos_Home>\bin_64\jre\1.5.0\lib\security

AIX:

/opt/cognos/c8/bin/jre/1.5.0/lib/security /opt/cognos/c8/bin_64/jre/1.5.0/lib/security

3. Type the following command to import the CommandCenter server certificate into the OpenPages Certificate Store:

Windows:

..\..\bin\keytool -import -trustcacerts -alias <file_name> -file <full_path> -keystore cacerts -file <full path>

AIX:

../../bin/keytool -import -trustcacerts -alias <file_name> -file <full_path> -keystore cacerts

Where:

<file_name> is the name of the CA certificate file without the path and file extension

<full_path> is the complete path and file name of the CA certificate file

Example

c:\bea\jdk142_11\bin\keytool -import -trustcacerts -alias cc -file c:\cc.cert -keystore cacerts

4. Use changeit as the password.5. Answer Yes to Trust certificate?

Your CommandCenter application has been successfully configured for use with HTTPS and OpenPages User Authentication.



Configuring a Load Balancer Running IBM HTTP ServerTo configure SSL on an AIX-based load-balancing server running IBM HTTP Server (IHS) in an IBM OpenPages GRC Platform 6.0.1 environment, follow the steps in this section.

Use the following steps to configure a load balancer for SSL.

Task 1: Generate a Keystore and Key PairThis task is required and should be performed on the load balance server.

If you are using IBM HTTP Server as your web server, generate a key pair using the iKeyman tool.

Steps:

1. Log on to the load balance server as a user with administrative privileges. 2. Launch iKeyMan by running the following command:

<IHS_root>/bin/ikeyman

Where <IHS_root> is the location of the IHS, by default: /usr/IBM/HTTPServer/

3. Create the keystore file to store the key pair.a. Select Key Database File > New.b. In the dialog box that appears, select CMS from the Key database type list.c. Enter a file name for the new key database file in the File Name field.d. In the Location field, enter the location where you want to store the keystore file,

for example:

usr/IBM/HTTPServer/bin

e. Click OK.f. In the Password Prompt dialog box that appears, enter a password for the

keystore. Re-enter the password to confirm. This password will be required to open the keystore in iKeyman.

g. Select Stash password to file to create an stash (.sth) file, which encrypts and stores the keystore password and/or assign an expiration time to the password, which will require the password to be changed periodically.

h. Click OK.



Task 2: Generate a Certificate Signing Request (CSR) FileThis task is required and should be performed on the load balance server.

If you require an authorized certificate from a commonly-trusted third-party certificate authority, you can use the iKeyman utility to generate the required certificate signing request.

Steps:



Where <IHS_root> is the location of the IBM HTTP Server installation, by default: /usr/IBM/HTTPServer/

3. In the iKeyman tool, open the keystore you created above:a. Select Key Database File > Open.b. Specify the type of keystore, by default CMS.c. Enter the name and path to the keystore in the File Name and Location fields, or

click Browse to locate the keystore (the File Name and Location fields auto-fill). d. Click OK.e. In the Password Prompt dialog box, enter the password for the keystore.f. Click OK.

4. Generate the certificate request for the open keystore:a. Select Create > New Certificate Request.b. In the Create New Key and Certificate Request dialog box that appears,

provide an identifier for the certificate (alias) in the Key Label field.c. Select a key length for the certificate in the Key Size list. The key size determines

the strength of the encryption. d. Select an algorithm to apply to the certificate from the Signature Algorithm list. e. Provide dname information to identify the certificate. Enter the values as

appropriate for the following: commonName organization organizationUnit localityName stateName country

f. Click OK to generate the request. A certificate request in the .arm format will be created and saved to the specified location.

Task 3: Submit CSR to CA for ApprovalThis task is required.

Submit your CSR file to an appropriate Certification Authority (CA) or you can act as your own CA. Follow the instructions provided by the CA.

Download the approved root and CA certificates to a local directory. Make sure the certificates are named to distinguish the root from the CA certificate.



Task 4: Import Root and Signed Server CertificatesThis task is required and should be performed on the load balance server.

You must install a signed CA certificate from a commonly trusted third-party certificate authority or self-signed certificates in both the keystore you created and the keystore used by IBM HTTP Server (plugin-key.kdb). You must also install a server certificate into the keystore you created.

Steps:



Where <IHS_root> is the location of the IHS, by default: /usr/IBM/HTTPServer/

3. In the iKeyman tool, open the keystore you created above:a. Select Key Database File > Open.b. Specify the type of keystore, by default CMS.c. Enter the name and path to the keystore in the File Name and Location fields, or

click Browse to locate the keystore (the File Name and Location fields auto-fill). d. Click OK.e. In the Password Prompt dialog box, enter the password for the keystore.f. Click OK.

4. Import the signed CA certificate as follows:a. Select Signer Certificates in the Key database content list.b. Click the Add button.c. In the Open window, enter the name and path to the keystore in the File Name

and Location fields, or click Browse to locate the keystore. d. Click OK.e. In the Enter a Label dialog box that appears, enter a name for the certificate in

the Enter a label for the certificate field.5. Select Key Database File > Close to close this key database.6. In the iKeyman tool, open the plugin-key.kdb keystore:

a. Select Key Database File > Open.b. Specify the type of keystore, by default CMS.c. Enter the name and path to the keystore in the File Name and Location fields, or

click Browse to locate the keystore.

The plugin-key.kdb keystore is located in the following directory, by default: <IHS root>/Plugins/config/<server_name>/plugin-key.kdb

Where <server_name> is the name of the load balancing server.

d. Click OK.e. In the Password Prompt dialog box, enter the password for the keystore, by

default: WebASf. Click OK.

7. Select Signer Certificates in the Key database content list.8. Click the Add button.9. In the Add CA's Certificate from a file window, enter the following information:

a. Select Base64-encoded ASCII data in the Data type list.b. Enter the name and path to the keystore in the File Name and Location fields, or

click Browse to locate the keystore (the File Name and Location fields auto-fill). c. Click OK.d. In the Enter a Label dialog box that appears, enter a name for the certificate in

the Enter a label for the certificate field.e. Click OK.



Task 5: Edit the httpd.conf FileThis task is required and should be performed on the load balance server.

Steps:

1. On the load balance server, launch a Command Prompt window (using the Run as Administrator option) or AIX shell as a user with administrative privileges.


<IHS root>/conf

3. Open the httpd.conf file using a text editor such as Notepad or vi.4. Uncomment following line in the file.

LoadModule was_app22_module modules/mod_was_ap22_http.so LoadModule negotiation_module module8s/mod_negotiation.so

5. Uncomment the following lines the file. Add any lines that are not present:

Listen 443 <VirtualHost *:443> ServerName <server_name> SSLEnable SSLProtocolDisable SSLv2 SSLClientAuth None <Directory /> Options FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory> </VirtualHost> SSLDisable KeyFile <IHS_root>/<keystore_name>.kdb

Where:

<IHS_root> is the location of the keystore, by default:/usr/IBM/HTTPServer/

<keystore_name> is the name of the keystore you created above.

6. Add the following line, pointing to the WebSphere Application Server Plugin Configuration:

WebSpherePluginConfig <IHS root>/Plugins/config/<server_name>/plugin-cfg.xml

Where <server_name> is the name of the load balancing server.

7. Save and close the httpd.conf file. 8. Restart the IBM HTTP Server to apply the changes.



Configuring a Load Balancer Running Apache Load BalancerThe information in this topic applies only to Windows environments.

Perform these steps for the web server on any reporting server that will handle external CommandCenter traffic.

“Generate Key Pair and Request” “Submit CSR to CA for Approval” “Import the CA Certificates” “Install the CommandCenter Certificate into OpenPages”

Task 1: Generate Key Pair and RequestUse the following steps to generate the key pair and specify the keystore.

Steps:

1. Log on to the load-balancing server as a non-root user with administrative privileges. 2. Open Command Prompt window (using the Run as Administrator option). 3. Navigate to the \bin directory in the web server home directory to use as the keystore.4. Enter the following command to generate a certificate request:

Windows

openssl req -new -sha1 -newkey rsa:1024 -config %APACHE_HOME%\conf\openssl.cnf -nodes -keyout server_pkey.key -out certreq.csr

AIX

openssl req -new -sha1 -newkey rsa:1024 -config $APACHE_HOME\conf\openssl.cnf -nodes -keyout server_pkey.key -out certreq.csr

5. Open the httpd.conf file using a text editor such as Notepad or vi.6. Uncomment following line in the file.-

LoadModule ssl_module modules/mod_ssl.so Secure (SSL/TLS) connections Include conf/extra/httpd-ssl.conf






Task 3: Import the Root Certificate(s)Import the root certificate into Apache.

Steps:

1. Log on to the load-balancing server as a non-root user with administrative privileges. 2. Open Command Prompt window (in Administrator mode).3. Navigate to the <Apache_Home>/conf/extra directory.4. Open the http-ssl.conf file in a text editor.5. Under Server Certificate:


6. Under Server Private Key: a. Uncomment the SSLCertificateKeyFile parameter.b. Enter the path to the key file on this server.


Task 4: Edit the httpd.conf FileThis task is required and should be performed on the load balance server.

1. Log on to load-balancing Web server as a user with administrative privileges. 2. Stop the Apache Web Server, if running.3. Launch a Command Prompt window (using the Run as Administrator option).4. Copy the <WL_Home>\server\plugin\win\32\mod_wl_22.so file to the

<Apache_Home>\modules directory.

Example

copy C:\Oracle\Middleware\wlserver_10.3\server\plugin\win\32\mod_wl_22.so “C:\Program Files\Apache Software Foundation\Apache2.2\conf”

5. Navigate to the <Apache_Home>\conf\ directory.6. Open the httpd.conf file (the Apache configuration file) and locate the parameters

added to the end of the file for SSL. See an example of all of these parameters below.a. Add the following parameters before the first <Location /> parameter.


<Location /> SetHandler weblogic-handler SecureProxy ON </Location>

b. In the <Location /> parameter, add the path to the trusted CA certificate file as shown in bold, for example: "C:\OPKeystore\rootca.cer".

<Location /> SetHandler weblogic-handler SecureProxy ON TrustedCAFile <Path_to_Certificate> </Location>



D
Changing Default Port Numbers

This chapter describes how to change the default port numbers used by the IBM OpenPages GRC Platform installer.


About OpenPages Default Ports on page 284 Changing OpenPages Ports on page 286


• • • • • • • • • •About OpenPages Default Ports

The IBM OpenPages GRC Platform installer sets several default ports during installation, such as the ports for the OpenPages server and the workflow server.

For example, in the event of a port conflict, where another application is using these port ranges, after installing IBM OpenPages GRC Platform, you can change the OpenPages ports to a different port range.

In the case of a port conflict, we recommend that you change all of the OpenPages application and workflow (IBPM) server ports to a new range by following the instructions in this section.

IMPORTANT!

Do not change the port number for the OpenPages administrative server or the workflow administrative server. By default, the OpenPages administrative ports for Windows/WebLogic Server are 7001 and 49901, repectively. For AIX/WebSphere Application Server the administrative ports are 9060 and 9061.

To modify port numbers on other application servers in a cluster, you must repeat the following tasks on each cluster member.

Appendix D: Changing Default Port Numbers


• • • • • • • • • •Checklist for Changing Ports

Use the following checklist to guide you through changing port numbers for OpenPages application and workflow servers. Each task below has several steps.

Table D-1: Checklist for Changing Port Numbers

Task Checklist

1. Make sure the port or range or ports you want to use is available. See “Check Port Number Availability” on page 286.

2. Use the WebLogic Server or WebSphere Application Server to change the ports within the application server. See “Checklist for Changing Ports” on page 285.

3. Log onto the application server and change port numbers in specific OpenPages property files. See “Update Port Values in OpenPages Property Files” on page 296.

4. Log onto the application server and change port numbers in specific workflow property files. See “Update Port Values in the Workflow Server Property Files” on page 299.

5. Update port values in a script that call several OpenPages tasks. See “Update Port Values in RunTool.sh script (RunTool.sh) — AIX only” on page 302.

6. Run a script to update port values in the database. See “Update Port Values in the Database” on page 302.

7. Update the OpenPages and workflow server port numbers used by CommandCenter. See “Update Port Values on the Reporting Server” on page 303.

8. Restart the OpenPages and workflow services. See “Restart Services” on page 303.

9. Update the OpenPages and workflow server port numbers used by CommandCenter reports. See “Update the Reporting Schema and Framework” on page 303.



• • • • • • • • • •Changing OpenPages Ports

The process of changing ports in OpenPages involves modifying the port numbers in the web server console application, editing OpenPages property files, and updating ports in the OpenPages database.

Changing Port Numbers Used by OpenPagesUse the following steps to change port numbers for OpenPages application and workflow servers.

Task 1: Check Port Number AvailabilityBefore changing the port numbers, make sure that the new ports you are going to use are available.

To determine if another application is using a specific port, log onto the application server where you need to change the port. Open a command or shell window and execute the following command:

Windows

netstat -an | findstr "<port number>"

AIX

netstat -an | grep <port_number>

Task 2: Change Port Values for OpenPages and Workflow ServersTo change the default application ports assigned during installation, launch the appropriate application server console (WebLogic Server for Windows or WebSphere Application Server for AIX) and change the ports within the application server.

Because the locations where you need to specify updated port numbers differ based on which port(s) you change, review each task below to make sure you changed the port in all required locations.

Depending on your environment, use the instructions in one of the following topics to change port values in the application web server console:

“Changing Ports for an Oracle WebLogic Server Environment” on page 1 “Changing Ports for an IBM WebSphere Application Server Environment” on page 1

Changing Ports for an WebLogic Environment

The information in this topic applies only to WebLogic environments.

If your OpenPages environment uses an WebLogic Server, use these steps to complete Task 2.

Task A: Change Port Numbers for the Application ServerUse the following steps to change the port number for the OpenPages application, for example you could change the default 7001 to port 443.

Steps:

1. Open a browser window and log on to the Oracle WebLogic Server Administration Console for OpenPages as a user with administrative privileges.

By default, the URL is http://<server_name>:7001/console



Where:

<server_name> is the name of the server where WebLogic Server is installed and 7001 is the default OpenPages admin port.

2. In the Change Center pane of the Console, click Lock & Edit (if not already selected).3. Change the port numbers for the OpenPages application server as follows:

a. In the Domain Structure pane, expand the Environment tree and click Servers.b. On the Summary of Servers page, click the Configuration tab (if not already

selected).c. In the Servers table listing, click the name of the application server for which you

want to change port numbers. For example:

<server_name>-OpenPagesServer<#>

Where:

<server_name> is the name of the application server.


d. On the Settings for <Host_Name> page for the selected server, on the General tab, change the value in the following fields:

Listen Port - the port used by the OpenPages application. By default, this port is 7009.

SSL Listen Port - the SSL port used by the OpenPages application. By default, this port is 7010.

e. Click Save.f. Repeat Steps a-e as needed to change default ports on other cluster members.

Task B: Configure the Ports for the Messaging Bridge Between the OpenPages Application Server and the Workflow Server

After changing the OpenPages application port number, you must update the port numbers for the WebLogic messaging bridge on the OpenPages server, which allows the OpenPages server to send and receive JMS messages from the workflow server.

Steps:

1. In the Domain Structure pane, expand the Services tree, then Messaging and click Bridges.

2. In the Bridges table listing on the Summary of Messaging Bridges page, locate the server for which you need to change:a. In the Name column, locate the server for which you need to change the port.

There are two listings in the table for each OpenPages instance. Each server bridge needs to be updated.

Example

The following two entries reference OpenPages instance 1 on server server01:

server01-OpenPagesServer1-OP2IBPMBridge server01-OpenPagesServer1-OP2InternalBridge

b. In the Source Bridge Destination column, click the IBPMBridgeSource entry for the application server you want to configure.

Example:

The following references the source port for the bridge to the workflow server for OpenPages instance 1 on server01:

server01-OpenPagesServer1-OP2IBPMBridgeSource



3. On the Settings for <Host_Name>-OP2IBPMBridgeSource page, change the OpenPages listen port:a. Change the port value in the Connection URL field to the listen port used by the

OpenPages application. By default, this port is 7009. b. Click Save. c. Click the browser Back button or click the Summary of Messaging Bridges link

at the top of the page to return to the Summary of Messaging Bridges page.4. In the Source Bridge Destination column, click the InternalBridgeSource entry for

the application server you want to configure.

Example: server01-OpenPagesServer1-OPInternalBridgeSource

5. On the Settings for <Host_Name>-OPInternalBridgeSource page, do the following:a. Change the port value in the Connection URL field to the listen port used by the


at the top of the page to return to the Summary of Messaging Bridges page.6. In the Target Bridge Destination column, click the InternalBridgeTarget entry for

the application server you want to configure.

Example: server01-OpenPagesServer1-OPInternalBridgeTarget

7. On the Settings for <Host_Name>-OPInternalBridgeTarget page, do the following:a. Change the port value in the Connection URL field to the listen port used by the


at the top of the page to return to the Summary of Messaging Bridges page.8. Repeat Steps 1-7 as needed to change default ports on other cluster members.9. Click the Activate Changes button in the Change Center to implement the changes.

Task C: Configure the Ports for the Messaging Bridge Between the Workflow Server and the OpenPages Application Server

After changing the OpenPages application port number, you must update the port numbers for the WebLogic messaging bridge on the workflow server, which allows the workflow server to send and receive JMS messages from the OpenPages server.

Steps:

1. Open a browser window and log on to the Oracle WebLogic Server Administration Console for the workflow server as a user with administrative privileges.

By default, the URL is http://<server_name>:49901/console

Where <server_name> is the name of the server where workflow server is installed and 49901 is the workflow admin port.

2. In the Change Center pane of the Console, click Lock & Edit (if not already selected).3. In the Domain Structure pane, expand the Services tree then Messaging in the left

pane and click Bridges.



4. In the Bridges table listing on the Summary of Messaging Bridges page, do the following: a. Locate the server for which you need to change the port in the Name column.

There are two listings in the table for each workflow server instance.

Example

The following two entries reference workflow server instance 1 on server server01:

server01-InterstageBPMCS1-OP2IBPMBridge server01-InterstageBPMCS1-OP2InternalBridge

b. In the Source Bridge Target column, click the OP2IBPMBridgeTarget entry for the application server you want to configure.

Example: server01-InterstageBPMCS1-OP2IBPMBridgeTarget

c. On the Settings for <Host_Name>-OP2IBPMBridgeSource page, change the port value in the Connection URL field to the OpenPages application port. By default, this port is 7009.

t3://server01:7009

d. Click Save.5. Click the Activate Changes button in the Change Center to implement the changes.6. Continue to “ Update Port Values in OpenPages Property Files” on page 1.

Changing Ports for an WebSphere Application Server Environment

The information in this topic applies only to WebSphere environments.

By default, the OpenPages application on the WebSphere Application Server uses the port range 10101-10120, and workflow (IBPM) server uses the port range 20101-20120.

If your IBM OpenPages GRC Platform environment uses an WebSphere Application Server, use these steps to complete Task 2 for the OpenPages application server and the workflow server.

Task A: Stop the OpenPages and Workflow Application ServersBefore changing the ports, make sure that all managed OpenPages application servers and all managed workflow servers are stopped. Only the OpenPages admin and workflow admin servers must be running.

IMPORTANT! If you are changing the OpenPages and/or workflow port numbers because of port conflict issues, you do not need to stop the OpenPages and/or workflow servers. Skip Task A (this task) and go to “ Update OpenPages Application Server Port Numbers” on page 1. DO NOT use the stopAllServers.sh or stopServer.sh scripts, as the scripts will attempt to stop any other applications associated with OpenPages ports.

If there are no port conflicts, use the following instructions to stop individual OpenPages and workflow application servers.

Steps:

1. Log on to the admin server as a user with administrator privileges.2. To stop an OpenPages application server, do the following:

a. Open an AIX shell and navigate to the <OP_Home>/profiles/<host_name>-OPNode1/bin directory.

Where: <OP_Home> represents the installation location of the OpenPages application, by default:

Windows C:\OpenPages

AIX /opt/OpenPages



b. Enter the commands as follows to stop each OpenPages application server and workflow application server for which you want to change the port numbers:

./stopServer.sh <host_name>-OPNode1Server<#>

Where <#> is the number of the OpenPages application server.

3. To stop a workflow server, do the following: a. In the AIX shell, navigate to the <Workflow_Home>/profiles/

<host_name>-IBPMNode<#>/bin directory. b. Enter the command as follows to stop the workflow server that you want to change

the port numbers:

./stopServer.sh <server_name>-IBPMNode<#>Server

Where <#> is the number of workflow application server.

Task B: Update OpenPages Application Server Port NumbersUse the following steps to change the default port numbers on an OpenPages application server.

Steps:

1. Open a browser window and navigate to the following address to launch IBM WebSphere Integrated Solutions Console for the OpenPages application, by default:


Where:

<server_name> is the name of the server where the IBM WebSphere Application Server is installed and 9060 is the default OpenPages application port.

2. Log on to the IBM WebSphere Integrated Solutions Console as a user with administrative privileges.

3. Expand Servers then Server Types in the left pane and click the WebSphere application servers link.

4. In the list on the Application servers page, click the name of the application server for which you want to change port numbers. For example:

<server_name>-OPNode1Server<#>

Where:

<server_name> is the name of the application server.


5. On the Application servers><server-name> page for the selected server, under the Communications heading, click the Ports link.

6. On the Ports page for the selected server, click the link to the port that you want to change.

Note: When changing ports, we recommend you change all the ports shown on the Ports page for each server and maintain all ports in a specific range.

7. On the <port type> page for the selected port, do the following:a. Enter a new port number in the Port field.

Note: Before changing the port numbers, make sure that the new ports you are going to use are available using an appropriate tool on the selected server, such as the netstat -an | grep <port_number> command.

b. Click Apply.c. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.8. Repeat Steps 4-7 as needed to change other ports on the selected server.



9. If you changed the OpenPages application port (by default, 10108) and/or OpenPages application SSL port (by default, 10111), update the port numbers in the default OpenPages application virtual hosts created by the WebSphere Application Server as follows:a. In the left pane of the IBM WebSphere Integrated Solutions Console, expand

Environment then click Virtual Hosts.b. In the list on the Virtual Hosts page, click default_host.c. On the Virtual Hosts > default_host page, under the Additional Properties

heading, click Host Aliases.d. On the Host Aliases page, click the appropriate * link to update the OpenPages

application (WC_defaulthost) port you changed above. The port numbers listed are the previous port numbers for each port.

For example, if the application port for the OpenPages instance you changed was 10108, click the * in the same row as 10108.

e. On the Configuration tab, enter the new port number in the Port field.f. Click Apply.g. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.h. On the Host Aliases page, click * to select the OpenPages application

(WC_defaulthost_secure) SSL port, by default 10111. The port numbers listed are the previous port numbers for each port.

i. On the Configuration tab, enter the new port number in the Port field.j. Click Apply.k. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.

Task C: Update Workflow Server Port NumbersUse the following steps to change the default port numbers on workflow application servers.

Steps:

1. Open a browser window and navigate to the following address to launch IBM WebSphere Integrated Solutions Console for the workflow server, by default:


Where:

<server_name> is the name of the server where the IBM WebSphere Application Server is installed and 9061 is the default workflow server admin port.

2. Log on to the IBM WebSphere Integrated Solutions Console as a user with administrative privileges.

3. Expand Servers then Server Types in the left pane and click the WebSphere application servers link.

4. In the list on the Application servers page, click the name of the application server you want to configure. For example:

<server_name>-IBPMNode<#>Server

where <server_name> is the name of the application server and <#> is the number of the node or server.

5. On the Application servers><IBPM-server-name> page for the selected server, under the Communications heading, click the Ports link.



6. On the Ports page for the selected server, click the link to the port that you want to change.

Note: When changing ports, we recommend you change all the ports shown on the Ports page for each server and maintain all ports in a specific range.

7. On the <port type> page for the selected port, do the following:a. Enter a new port number in the Port field.

IMPORTANT! Before changing the port numbers, make sure that the new ports you are going to use are available using an appropriate tool on the selected server, such as the netstat -an | grep <port_number> command.

b. Click Apply.c. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.8. Repeat Steps 4-7 as needed to change other ports on the selected server.9. If you changed the workflow application port (by default, 20108) and/or workflow

application SSL port (by default, 20111), update the port numbers in the default workflow application virtual hosts created by the WebSphere Application Server as follows:a. In the left pane of the IBM WebSphere Integrated Solutions Console, expand

Environment then click Virtual Hosts.b. In the list on the Virtual Hosts page, click default_host.c. On the default_host page, under the Additional Properties heading, click Host

Aliases.d. On the Host Aliases page, click the appropriate * link to update the workflow

application (WC_defaulthost) port you changed above. The port numbers listed are the previous port numbers for each port.

For example, if the application port for the workflow instance you changed was 20108, click the * in the same row as 20108.

e. On the Configuration page, enter the new port number in the Port field.f. Click Apply.g. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.h. On the Host Aliases page, click * to select the workflow application

(WC_defaulthost_secure) SSL port, by default 20111. The port numbers listed are the previous port numbers for each port.

i. On the Configuration page, enter the new port number in the Port field.j. Click Apply.k. In the Messages box that appears at the top of the page, click Save to commit the


Task D: Update Ports to the Java Messaging ServiceIf you changed the WebSphere Service Integration Bus (SIB) messaging service endpoint port for the OpenPages application server (by default, 10115) and/or the workflow server (by default, 20115), you need to change other settings within the OpenPages application server and the workflow server.

If you did not change the SIB Endpoint Address, skip to Task 3.

The WebSphere Application Server uses the Java Message Service (JMS) to enable Java clients and applications to create, send, receive, and read asynchronous requests.



There are a number of JMS settings that need to be updated with the new port numbers for the OpenPages application server and the workflow server.

Steps:

1. On the IBM WebSphere Integrated Solutions Console for the OpenPages application (http://<server_name>:9060/ibm/console), update the OpenPages topic connection factories with the new port number(s) set above.

A topic connection factory is used by the WebSphere Application Server to send messages between Java clients within your environment.

a. Expand Resources then JMS in the left pane and click the Topic Connection Factories link.

b. In the list on the Topic connection factories page, click the OPTCF link.c. Under General Properties, locate the Provider endpoints field in the Connections

group.d. Update the port number in the Provider endpoints field for the WebSphere SIB

messaging service with the new SIB endpoint address for the OpenPages server: <serrver_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.

If necessary, refer to the Application servers > <server_name>-OPNode1Server# > Ports page for the current OpenPages SIB Endpoint Address port.

e. Click Apply.f. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.2. Update the OpenPages activation specifications with the new port number(s) set above.

A JMS activation provides configuration necessary for WebSphere Application Server to retrieve messages.

a. Expand Resources then JMS in the left pane and click the Activation specifications link.

b. In the list on the Activation Specifications page, click NotificationTopic.c. Under General Properties, locate the Provider endpoints field in the Destination

group.d. Update the port number in the Provider endpoints field to the new port workflow

number: <server_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.

If necessary, log onto the IBM WebSphere Integrated Solutions Console for the workflow server and refer to the Application servers > <server_name>-OPNode1Server# > Ports page for the current workflow SIB Endpoint Address port.


changes to the master configuration.g. In the list on the Activation Specifications page, click SQNotificationTopic and

repeat the steps above to the new port workflow number.3. Log out of the IBM WebSphere Integrated Solutions Console for the OpenPages server.4. On the IBM WebSphere Integrated Solutions Console for the workflow server (by

default, http://<server_name>:9061/ibm/console), update the workflow server queue connection endpoints with the new application port number(s) set above.

A JMS queue connection factory is used with WebSphere MQ as a messaging provider.

a. Expand Resources then JMS in the left pane and click the Queue Connection Factories link.

b. In the list on the Queue connection factories page, click the IAnalyticsConnectionFactory link.

c. Under General Properties, locate the Provider endpoints field in the Connections group.



d. Update the port number in the Provider endpoints field to the new workflow port number: <host_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.


changes to the master configuration.5. Update the workflow server topic connection endpoints with the new port number(s)

set above. a. In the Resources > JMS tree in the left pane, click the Topic Connection

Factories link.b. In the list on the Topic connection factories page, click the OPTCF link.c. Under General Properties, locate the Provider endpoints field in the Connections

group.d. Update the port number in the Provider endpoints field to use the new SIB

endpoint address value for the OpenPages server: <host_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.


changes to the master configuration.g. In the list on the Topic connection factories page, click the iFlowDistFactory

link.h. Under General Properties, locate the Provider endpoints field in the Connections

group.i. Update the port number in the Provider endpoints field to use the new SIB

endpoint address value for the workflow server: <host_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.

j. In the Messages box that appears at the top of the page, click Save to commit the changes to the master configuration.

k. In the list on the Topic connection factories page, click the iFlowFactory link and repeat the steps above to change the workflow SIB endpoint address.

6. Update the workflow server activation specifications with the new port number(s) set above.

A JMS activation provides configuration necessary for WebSphere Application Server to retrieve messages.

a. In the Resources > JMS tree in the left pane, click the Activation specifications link.

b. In the list on the Activation Specifications page, click CacheSyncBridgeTopicAS for the server which you changed the SIB port.

c. Under General Properties, locate the Provider endpoints field in the Destination group.

d. Update the port number in the Provider endpoints field to the new OpenPages SIB port number: <server_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.


changes to the master configuration.g. In the list on the Activation Specifications page, click RepositoryTopicAS for

the server which you changed the SIB port.h. Under General Properties, locate the Provider endpoints field in the Destination

group.i. Update the port number in the Provider endpoints field to the new OpenPages

SIB port number: <server_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.

j. Click Apply.k. In the Messages box that appears at the top of the page, click Save to commit the




l. In the list on the Activation Specifications page, click SiteGeneratorTopicAS for the server which you changed the SIB port.

m. Under General Properties, locate the Provider endpoints field in the Destination group.

n. Update the port number in the Provider endpoints field to the new OpenPages SIB port number: <host_name>:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging.

o. Click Apply.p. In the Messages box that appears at the top of the page, click Save to commit the

changes to the master configuration.7. Continue to “ Update Port Values in OpenPages Property Files” on page 1.

Task 3: Update Port Values in OpenPages Property FilesThe information in this topic applies to both WebLogic and WebSphere environments.

If you changed the OpenPages bootstrap port (7009/10101), the OpenPages application port (7009/10108), and/or the workflow server application port (49951/20108), you must manually change the port values in the following properties files for the OpenPages application server for which you changed the ports: aurora.properties, -sosa.properties, and -server.properties.

If you did not change any of these ports, skip to Task 4.

Note: Default port numbers in this section are listed in parenthesis in (Windows/AIX) format.

Task A: Update Port Values in the Aurora Property File (aurora.properties)Steps:

1. Log on to the OpenPages admin server associated with the application server for which you changed ports as a user with administrator privileges.

2. Open a Command Prompt window (using the Run as Administrator option) or AIX shell window and navigate to the <OP_Home>|aurora|conf directory.

Where: <OP_Home> represents the installation location of the OpenPages application, by default:

Windows C:\OpenPages

AIX /opt/OpenPages

3. Locate the aurora.properties file in the conf directory and open the file in a text editor of your choice.a. If you changed the OpenPages application port number (7009/10108) update the

port in the following property:

application.url.path=

Example

The following example shows the application.url.path= parameter for a Windows server named server01. You must change the 7009 to the new port number.

application.url.path=http\://server01\:7009



b. If you changed the OpenPages bootstrap port number (7009/10101) update the port in the following property:

url.service.port=

Example

The following example shows the url.service.rule parameter for an AIX server named server01. You must change the 10101 to the new port number.

url.service.port=10101

c. When finished, save and close the file.

Task B: Update Port Values in the OpenPages Sosa Property File (-sosa.properties)Steps:

1. In the Command Prompt window or AIX shell window, remain in the <OP_Home>|aurora|conf directory.

2. Locate the -sosa.properties file(s) for the application server(s) for which you changed ports and make a backup copy of the file. File names have the following format:

<server_name>-OPNode1Server<#>-sosa.properties

Where:

<server_name> is the name of the OpenPages application host server.


3. Open the selected -sosa.properties in a text editor of your choice and do the following:a. If you changed the OpenPages application port number (by default, 7009/10108)

update the port in the following property:

application.url.path=

Example

The following example shows the application.url.path= parameter for a Windows server named server01. You must change the 7009 to the new port number.

application.url.path=http\://server01\:7009

b. If you changed the OpenPages bootstrap port number (by default, 7009/10101) update the port in the following property:

openpages.service.port=

Example

The following example shows the openpages.service.port= parameter for an AIX server named server01. You must change the 10101 to the new port number.

openpages.service.port=10101

c. When finished, save and close the file.

Task C: Update Port Values in the OpenPages Server Property File (-server.properties)Steps:




2. Locate the -server.properties file for the application server for which you changed ports and make a backup copy of the file. File names have the following format:

Windows

<server_name>-OpenPagesServer<#>-server.properties

AIX

<server_name>-OPNode1Server<#>-server.properties

Where:

<server_name> is the name of the OpenPages application host server.


3. Open the selected application -server.properties file in a text editor of your choice and do the following:a. If you changed the OpenPages bootstrap port number (by default, 7009/10101)

update the following properties with the new OpenPages bootstrap port:

url.service.rule= security.providerurl= url.service.port= url.service.workflow= jta.providerurl= url.service.security= jms.providerurl= url.service.repository= url.service.transformation= url.repositoryService= url.service.sitegenerator= service.client.providerurl= url.service.clientapi= url.path.workflow.admin=

Examples

The following example shows the url.service.rule parameter for server01. You must change the 7009 to the new port number.

url.service.rule=http\://server01\:7009

The following example shows the url.path.workflow.admin= parameter for server01. You must change the 20108 to the new port number.

url.path.workflow.admin==http\://server01\:20108

b. If you changed the OpenPages application port number (by default, 7009/10108) update the following properties with the new OpenPages application port:

url.path.openpages= webclient.http.server.port=

c. If you changed the workflow application port number (by default, 49951/20108) update the following property with the new workflow application port:

url.path.workflow.admin=

d. Save and close the file.



Task 4: Update Port Values in the Workflow Server Property FilesThe information in this topic applies to both WebLogic and WebSphere environments.

If you changed the OpenPages bootstrap port (7009/10101), the OpenPages application port (7009/10108), workflow bootstrap port (49951/20101), and/or the workflow server application port (49951/20108), you must manually change the port values in the following properties files for the workflow application server for which you changed the ports.

If you did not change any of these ports, skip to Task 5.

Note: Default port numbers in this section are listed in parenthesis in (Windows/AIX) format.

Task A: Update Port Values in the Server Properties Files (-server.properties)If you changed the OpenPages bootstrap port, OpenPages application port, and/or workflow application port, you need to update the ports in the server properties file for which you changed the port(s).

Steps:


2. Locate the -server.properties file for the selected workflow server and make a backup copy of the file. File names have the following format:

Windows: <server_name>-InterstageBPMCS<#>-server.properties

AIX: <server_name>-IBPMNode<#>Server-server.properties

Where:

<server_name> is the name of the workflow host server.

<#> is the number of the node or server.

3. Open the selected workflow -server.properties file in a text editor of your choice and do the following:a. If you changed the OpenPages bootstrap port (7009/10101) update the following

properties with the new OpenPages bootstrap port:

url.service.rule= security.providerurl= url.service.port= url.service.workflow= url.service.security= url.service.repository= url.service.transformation= url.service.sitegenerator= url.repositoryService= service.client.providerurl= url.service.clientapi= url.path.workflow.admin=

Examples

The following example shows the url.service.rule parameter for server01. You must change the 7009 to the new port number.


The following example shows the url.path.workflow.admin= parameter for server01. You must change the 20108 to the new port number.

url.path.workflow.admin==http\://server01\:20108



b. If you changed the workflow server bootstrap port (49951/20101) update the following properties with the new workflow bootstrap port:

jta.providerurl= jms.providerurl=

c. If you changed the OpenPages application port (7009/10108) update the following properties with the new OpenPages application port:

url.path.openpages= webclient.http.server.port=

d. If you changed the workflow application port (49951/20108) update the following property with the new workflow application port:

url.path.workflow.admin=

e. Save and close the file.

Task B: Update Port Values in the iFlowClient Property Files (-iFlowClient.properties)If you changed the workflow bootstrap port (49951/20101), you need to update the ports in the iFlowClient.properties file for the server for which you changed the port.

Steps:

1. In the Command Prompt window or AIX shell, navigate to the following directory:

<Workflow_Home>/client


2. Locate the -iFlowClient.properties file for the workflow server for which you changed ports and make a backup copy of the file. File names have the following format:

Windows <server_name>-InterstageBPMCS<#>-iFlowClient.properties

AIX <server_name>-IBPMNode<#>Server-iFlowClient.properties

Where:

<server_name> is the name of the workflow host server.

<#> is the number of the node and server.

3. Open the server -iFlowClient.properties file in a text editor of your choice and do the following:a. Update the following properties with the new workflow server bootstrap port:

JMSNamingProviderURL= NamingProviderURL=


Task C: Update Port Values in the IBPM console configuration file (console.conf)If you changed the workflow bootstrap port, you need to update the ports in the console.conf file for the server for which you changed the port.

Steps:


<Workflow_Home>\profiles\<server_name>-IBPMNode<#>\installedApps\ IBPMCell\fujitsu-console-ear.ear\ibpmconsole.war directory.

2. Open the console.conf file in a text editor of your choice and do the following:a. Update the following property with the new workflow server bootstrap port:

NamingProviderURL =




Task D: Update the ibpm.properties File for Cluster MembersIf you changed the workflow bootstrap port (49951/20101) and/or the workflow application port (49951/20108), you need to update the ports in the ibpm.properties file for the server for which you changed the port(s).

Steps:


<Workflow_Home>/server/deployment/WAS-Cluster<host_name>-IBPMNode<#>Server

Where <Workflow_Home> is the directory where Fujitsu Interstage BPM is installed, by default:

Windows c:\Fujitsu\InterstageBPM

AIX /opt/Fujitsu/InterstageBPM

2. Open the ibpm.properties file in a text editor of your choice and do the following:a. If you changed the workflow server bootstrap port (by default, it is 49951/20101)

update the following properties with the new workflow server bootstrap port:

NamingProviderURL= JMSNamingProviderURL=

b. If you changed the workflow server admin port (by default, it is 49951/20108) update the following properties with the new workflow server application port:

ServerBaseURL= ServerEmailBaseURL=

c. Save and close the file.3. Before executing importProperties.sh, make sure that the user performing the

installation has the permission to execute the script.

If the user does not have the permission to execute importProperties.sh, enter the following command:

chmod 755 importProperties.sh

4. Execute the Import Properties Script script:

Windows importProperties.bat

AIX ./importProperties.sh

Note: A message regarding the logging.properties file may appear while the script is running. You may disregard the message.

Task E: Update ObjectManager properties file (ObjectManager.properties)If you changed the OpenPages bootstrap port (7009/10101), you need to update the ports in the ObjectManager properties file for which you changed the port.

Steps:


<OP_Home>/bin



2. Open the ObjectManager.properties file in a text editor of your choice and do the following:a. Update the following property with the new OpenPages bootstrap port:

openpages.service.port=b. Save and close the file.

Task 5: Update Port Values in RunTool.sh script (RunTool.sh) — AIX onlyThe information in this topic applies only to WebSphere environments.

If you changed the OpenPages bootstrap port, you need to update the ports used by the RunTool.sh script. The RunTool.sh script is used by multiple OpenPages background tasks.

If you did not change any of these ports or have a Windows/WebLogic Server environment, skip to Task 6.

1. In the AIX shell, navigate to the following directory: <OP_Home>/bin

2. Open the RunTool.sh file in a text editor of your choice and do the following:a. If the launchClient.sh command contains the following parameters:

-CCBootstrapHost=<server_name> -CCBootstrapPort=<openpages_bootstrap_port>

Make sure the -CCBootstrapPort value is using the new OpenPages bootstrap port. If these parameters are not present, skip this task.

Examples

If the parameters are present: launchClient.sh -JVMOptions "$JVMOPTIONS" "$OPENPAGES_HOME/applications/opappstools.ear" -CCBootstrapHost=OPAdminServer -CCBootstrapPort=30101 -CCjar=opappstool-$TOOL_NAME.jar "$@"

If the parameters are not present: launchClient.sh -JVMOptions "$JVMOPTIONS" "$OPENPAGES_HOME/applications/opappstools.ear"-CCjar=opappstool-$TOOL_NAME.jar "$@"


Task 6: Update Port Values in the DatabaseThe information in this topic applies to both WebLogic and WebSphere environments.

If you updated any of the default OpenPages ports, you must update the port value(s) in the REGISTRY_ENTRIES table in the OpenPages database as follows.

Steps:

1. Log on to a machine with SQL*Plus and access to the database server.2. Run the following SQL commands to update the port number in the REGISTRY_ENTRIES

table:

update registryentries set value='<new_port_number>' where path='/OpenPages/Platform/Reporting Schema/Object URL Generator/Port'; commit;

where <new_port_number> is the new OpenPages application server port number.

3. When the commands are complete, log out of SQL*Plus.



Task 7: Update Port Values on the Reporting ServerThe information in this topic applies to both WebLogic and WebSphere environments.

If you changed the OpenPages application port number (7009/10108), you must update the associated CommandCenter instance with the new port number

Steps:

1. Log onto the reporting server as a user with administrator privileges.2. Open a Command Prompt window (using the Run as Administrator option) or AIX

shell window and navigate to the <Cognos_Home>|configuration directory.

Where:

<Cognos_Home> represents the installation location of the Cognos application. By default:

Windows C:\OpenPages\Cognos\cognos\c8\configuration

AIX /opt/OpenPages/Cognos/cognos/c8/configuration

3. Locate the OpenPagesSecurityProvider_OpenPagesSecurityRealm.properties file and make a backup copy of the file.

4. Open the OpenPagesSecurityProvider_OpenPagesSecurityRealm.properties file in a text editor of your choice and do the following:a. Replace the existing OpenPages application port number (7009/10108) update the

following property with the new OpenPages application port number:

openpages.application.url=

Example

The following example shows the openpages.application.url= parameter for an AIX reporting server named server01. You must change the 10108 to the new port number.


b. When finished, save and close the file.

Task 8: Restart ServicesThe information in this topic applies to both WebLogic and WebSphere environments.

After completing the port changes, restart the OpenPages and workflow services.

For more details, see Chapter 9 “Starting and Stopping OpenPages” on page 167.

Task 9: Update the Reporting Schema and FrameworkThe information in this topic applies to both WebLogic and WebSphere environments.

After services are restarted, you must re-create the reporting schema and regenerate the Reporting Framework V6 so that the port change is reflected in any redirects of CommandCenter reports.

For more details, see “Creating the Reporting Schema and Framework” in Chapter 8 on page 157.



E
Configuring OpenPages on One Machine

This chapter describes how to configure an IBM OpenPages GRC Platform on a single server.

This chapter contains the following topic:

Configuring OpenPages on a Single Server on page 306


Configuring OpenPages on a Single

• • • • • • • • • •Server

While the IBM OpenPages GRC Platform operates at peak performance when installed on multiple servers (a database server, an application server, and a reporting server), you may install the entire IBM OpenPages GRC Platform on a single machine (such as for pre-deployment testing).

If the entire OpenPages environment is installed on a single machine, you will need to install two versions of Oracle Client on that machine (one 32-bit and one 64-bit). You need two versions because the OpenPages application requires the 64-bit Oracle Client and the Cognos software integrated with CommandCenter requires the 32-bit Oracle Client. In this circumstance, you must configure the system to ensure that the proper Oracle Client is used by each application.

Configuring OpenPages to Operate on a Single ServerAfter installing the Oracle database, 32-bit Oracle Client, and the Cognos 8 software, use the following steps to configure the system to work with both versions of Cognos.

Steps

1. Log on to the 6.0.1 CommandCenter server as a user with administrative privileges.2. Ensure that the ORACLE_HOME environment variable references the 32-bit Oracle

Client.

Examples

Windows c:\openpages_data\repository\client112_ac_x86\software

AIX opt/openpages_data/repository/client112_ac_x86/software

3. Edit the PATH variable to add %ORACLE_HOME%\bin (Windows) or %ORACLE_HOME%/bin (AIX).

4. Remove the TNS_ADMIN variable, if set. 5. Launch a Command Prompt window or AIX shell and navigate to the following

directory:

<OP_Home>\CommandCenter\framework\conf\

6. Open the framework.properties file in a text editor and ensure the oracle.client.path value contains the path to 32-bit client bin directory.

Examples

Windows oracle.client.path=C\:/openpages_data/repository/client112_ac_x86/software/bin

AIX oracle.client.path=/opt/openpages_data/repository/client112_ac_x86/software/bin

7. Save and close the file.8. Restart the CommandCenter service.

Appendix E: Configuring OpenPages on One Machine


F
Integrating Single Sign-on with OpenPages
OpenPages can integrate into a number of single sign-on solutions, such as CA SiteMinder. The information in this section explains how to configure IBM OpenPages GRC Platform for use with one of these systems. Follow the vendor’s installation instructions for your single sign-on application software.


“Configuring the OpenPages Application for Single Sign-on” on page 308 “Configuring the Reporting Server for a Single Sign-on System” on page 313


Configuring the OpenPages

• • • • • • • • • •Application for Single Sign-on

If your environment uses a single sign-on process, you must configure OpenPages to operate in that process.

Configuring OpenPages for Single Sign-onUse the following tasks to configure your OpenPages system to integrate with a single sign-on system.

Task 1: Configure the OpenPages Interface for Single Sign-onYou can integrate a single sign-on system with OpenPages by configuring the following settings within the OpenPages application interface.

Steps:

1. Start the OpenPages services (if not already started).2. Log on to the OpenPages application interface as a user with administrative privileges.

By default use port 7009 for Windows or 10108 for AIX.3. Under Administration, select Settings. 4. Set the value of the Show Hidden Settings setting to true (this will display all hidden

settings) as follows:a. Expand the OpenPages | Applications | Common | Configuration folder

hierarchy.b. Click the Show Hidden Settings setting to open its detail page.c. In the Value field on the setting detail page, change the value to true (the default

value is false).d. Click Save.

5. Set the value of the Session Attribute and Username Attribute settings as follows:a. Expand the OpenPages | Platform | Security | Single Sign On |

Implementations | Header-based folder hierarchy.b. Click the Class Name setting to open its detail page. c. In the Value field on the setting detail page, enter

com.openpages.singlesignon.HTTPHeaderBasedModule.d. Click the Session Attribute setting to open its detail page.e. In the Value field on the setting detail page, modify the value to match the session

attribute for your single sign-on system.

Examples

• Using SiteMinder 6.0, the value of the Session Attribute parameter is SMSERVERSESSIONID.

• Using Tivoli Access Manager 6.1, the value of the Session Attribute parameter is iv_creds.

f. Click Save.g. Click the Username Attribute setting to open its detail page.

Appendix F: Integrating Single Sign-on with OpenPages


h. In the Value field on the setting detail page, modify the value to match the user name attribute for your single sign-on system.

Examples

• Using SiteMinder 6.0, the value of the Username Attribute is SMUSER.• Using Tivoli Access Manager 6.1, the value of the Username Attribute is iv_user.

i. Click Save.6. Enable single sign-on as follows:

a. Expand the OpenPages | Platform | Security | Single Sign On folder hierarchy.b. Click the OP setting to open its detail page. c. In the Value field on the setting detail page, set the value to true.d. Click Save.e. Click the SOX setting to open its detail page and repeat Steps c - d.

7. Reset the value in the Show Hidden Settings setting (from Step 4) to false.

Task 2: Configure the Single Sign-on Logout DestinationLogging out of the OpenPages application does not automatically log the user out of a single sign-on system. If the user uses the Back button of the browser to re-enter the OpenPages application, the user’s session will be recreated for them based on the still-valid third-party credentials.

In order to securely log out from the OpenPages application and the single sign-on system, the logout invalidates the single sign-on session. Use the steps below to redirect the user to a specific HTML page outside of the session.

Steps:

1. Log on to the OpenPages application interface as a user with administrative privileges. By default use port 7009 for Windows or 10108 for AIX.

2. Under Administration, select Settings. 3. Expand the OpenPages | Platform | Security folder hierarchy.4. Click the Logout URL setting to open its detail page.5. In the Value box, type a fully qualified URL.6. Click Save.

Task 3: Configure the Application Server for Single Sign-on — Windows onlyThe information in this topic applies only to Windows environments that are using an

Apache-based load balancer.

In addition to confiuring the OpenPages application for SSO, you need to configure some settings within the application server to ensure that specific files do not go through the SSO application.

When an authenticated user attempts to click on a job remediation link, OpenPages will authenticate the user. However, when OpenPages is connected to a single sign-on application, that application can block the authentication request and the remediation link will not function.

The application server must be configured to route two Java servelets, opLogin and securityHelper, directly to the OpenPages backend functions for proper internal authentication.



Use the following steps to configure the application server to properly route these servlets.

Steps:


Note: For AIX installs, use the opuser user you created for the OpenPages installation.

2. Launch a Command Prompt window (using the Run as Administrator option) or AIX shell as the opuser user you created for the OpenPages installation.

3. Navigate to the <Apache_Home>\conf\ directory.4. Open the httpd.conf file (the Apache configuration file) in a text editor.

Note: In an SSL environment, edit the httpd-ssl.conf file.

5. Add the following lines to the file to create a path to route the opLogin and securityHelper servlets to the OpenPages without traversing the single sign-on application:

<Proxy balancer://backend> BalanceMember <http://<server_name>.openpages.com:<port> route=1 BalanceMember <http://<server_name>.openpages.com:<port> route=2 Order Allow,Deny Allow from all </Proxy> ProxyPass /openpages/opLogin balancer://backend/openpages/opLogin ProxyPass /openpages/securityHelper balancer://backend/openpages/securityHelper

Note: In an SSL environment, enter the SSL address (https://) and port.

Example

<Proxy balancer://backend> BalanceMember <http://qe-vm07.openpages.com:7009> route=1 BalanceMember <http://qe-vm07.openpages.com:7011> route=2 Order Allow,Deny Allow from all </Proxy> ProxyPass /openpages/opLogin balancer://backend/openpages/opLogin ProxyPass /openpages/securityHelper balancer://backend/openpages/securityHelper

6. Add the following lines to the file to ensure that traffic to the OpenPages log in page will be routed the single sign-on application:

<Proxy balancer://cluster> BalanceMember <http://<server_name>.openpages.com:<port> route=1 Order Allow,Deny Allow from all </Proxy> ProxyPass /openpages/ balancer://cluster/openpages/ stickysession=opapp|opapp ProxyPass /ibpmconsole/ balancer://cluster/ibpmconsole/ stickysession=JSESSIONID|jsessionid ProxyPass /ibpm/ balancer://cluster/ibpm/ stickysession=JSESSIONID|jsessionid

Note: In an SSL environment, enter the SSL address (https://) and port.



7. Remove any references to /openpages and /ibpmconsole from the file. For example, remove the following sections that were added during the configuration of a cluster environment:<Location /openpages> WLCookieName opapp SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile /logs/openpages.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

<Location /ibpmconsole> WLCookieName opibpm SetHandler weblogic-handler DynamicServerList ON MaxPostSize 0 WLLogFile logs/ibpmconsole.log WebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT> </Location>

Note: Do not remove the <Location /ibpmweblogicconsole> parameter:

<Location /ibpmweblogicconsole> SetHandler weblogic-handler MaxPostSize 0 WLLogFile logs/ibpmweblogic_console.log WebLogicHost <SERVER>.<DOMAIN>.COM WebLogicPort 49901 </Location>


Windows


AIX


9. Open the aurora.properties file and make sure that application.url.path is pointing to the OpenPages application server, as follows, where <server_name> is the name of the application server and <port> is the OpenPages port:

application.url.path=http\://<server_name>.openpages.com\:<OpenPages_port>/openpages

Notes

In an SSL environment, enter the SSL address (https://) and port. In a load balanced environment, enter the fully-qualified domain name of the load

balancer.10. Save and close the file.11. Open the server.properties file and make sure that the following paths are pointing

to the OpenPages application server and workflow server, as follows, where <server_name> is the name of the application server and <port> is the OpenPages application port or workflow admin port:

url.path.openpages=http\://<server_name>\:<OpenPages_port>/openpages url.path.workflow.admin=http\://<server_name>\:<IBPM_port>/ibpmconsole

Notes


balancer.12. Save and close the file.



13. Open the sosa.properties file and make sure that the application.url.path is pointing to the OpenPages application server, as follows, where <server_name> is the name of the application server and <port> is the OpenPages port:

application.url.path=http\://<server_name>\:<port>/openpages

Notes


balancer.14. Save and close the file.

Disable OpenPages Single Sign-on This task is required.

Use the following steps to disable single sign-on for the OpenPages application.

Steps:

1. Launch a web browser and navigate to the current OpenPages application.2. Log on as a user with administrative permissions.3. From the Administration menu, select Settings. 4. In all versions, disable single sign-on as follows:

a. Expand the OpenPages | Platform | Security | Single Sign On folder hierarchy.b. Click the OP setting to open its detail page. c. In the Value field on the setting detail page, set the value to false.d. Click Save.e. Click the SOX setting to open its detail page.f. In the Value field on the setting detail page, set the value to false.g. Click Save.



Configuring the Reporting Server for a

• • • • • • • • • •Single Sign-on System

If you are using a single sign-on system such as CA SiteMinder with the OpenPages application, you must load an updated redirect JSP so that reports will function properly.

This can be done by loading it through the ObjectManager tool using the CommandCenter-integration-op-config.xml file. The file is located on the OpenPages installation DVDs in the installer kit.

Configuring Single Sign-on for a Reporting ServerUse the following steps to configure the CommandCenter reporting server in a SSO environment.

Steps

1. Log on to a machine with SQL*Plus and access to the 6.0.1 database server.

Note: For AIX installs, log on as a non-root user.



3. Copy the OP_6.0.1_Configuration directory from the Installer Disc 1 DVD or on your network share location to the local system.a. Navigate to the following folder:

OP_6.0.1_Configuration\loader-data\

b. Copy the commandcenter directory to the local system.


4. Navigate to the <OP_Home>/bin directory.5. Run the following command:

ObjectManager load config OpenPagesAdministrator <password> <path-to-loader-file> CommandCenter-integration



G
Creating the CommandCenter Database Schema
This chapter describes how to use the existing OpenPages database instance for Content Store.


About Manually Installing the Content Store on page 316 Creating a Tablespace and User for the Content Store on page 317


About Manually Installing the Content

• • • • • • • • • •Store

CommandCenter uses a database structure, called the Content Store, to store, organize, and retrieve information about the queries and reports you create.

The Cognos installer will automatically create the database schema and users for the Content Store. Optionally, you can manually create the schema for the Content Store in the existing OpenPages instance.

If you want to create a new database instance for Content Store, use the Oracle Database Configuration Assistant to create the instance, then use the following procedure to create the schema.

Note: For best performance, CommandCenter and OpenPages should have separate database instances. However, for a smaller deployment or a test environment, a single database instance can be used.

To manually create the Content Store, perform the following tasks on the reporting server:

1. Install Oracle Client on the reporting server.

See “Installing the 32-Bit Oracle Client” in Chapter 6 on page 101.

2. Install the Cognos software using the OpenPages Cognos Installer. Select No when asked whether you want the installer to configure the CommandCenter Database Schema and user accounts.

See “Installing Cognos and the Content Store” in Chapter 6 on page 105.

3. Create a new Content Store user and the Content Store tablespace.

See “Creating a Tablespace and User for the Content Store” on page 317

4. Set environment variables in Windows or AIX on the server machine.

See “Modify Environment Variables” on page 320.

5. Configure the Oracle Client to use the appropriate character set.

See “Configure the Database to Support Multilingual Reports” on page 325.

6. Configure CommandCenter to access the database.

See “Set Database Connection Properties for CommandCenter” on page 323.

7. Create the database instance for CommandCenter.

See “Manually Create the Content Store” on page 326.

IMPORTANT! To configure CommandCenter to use the OpenPages database instance, point the CommandCenter installer to the OpenPages database instance.

Appendix G: Creating the CommandCenter Database Schema


Creating a Tablespace and User for

• • • • • • • • • •the Content Store

You must create a new Content Store user and the Content Store tablespace. This user must be able to create, alter, and drop tables, triggers, views, procedures, and sequences, and have the CONNECT and RESOURCE roles.

Use the following tasks to create the CommandCenter datastore instance and user.

Task 1: Change a Datafile Name for ASMThis task is optional.

The IBM OpenPages GRC Platform hard-codes the names and locations of tablespaces, data directories, and data files in the CommandCenter database. In some cases, these hard-coded values may conflict with internal systems, practices, or IT policies.

If you are running an ASM database and need to change the default name of the data files in the CommandCenter database, a site DBA or OpenPages representative must update the crndbcreate.sql script with the site-specific ASM information before using the script to create the tablespace.

IMPORTANT! Do not change the tablespace name through the crndbcreate.sql script. The installer validates the tablespace name and will not proceed if the name is different from the default.

Steps

1. Log on to a system as a user with Administrator privileges. You can use any system with access to SQL*Plus that can connect to the database server.


Note: For AIX installs, use a non-root, such as the user you created for the OpenPages installation, opuser.



b. Copy the COGNOS directory to the local system.


4. Navigate to the COGNOS directory on the local system.5. Open the crndbcreate.sql script in a text editor such as WordPad or vi



6. Modify the SQL script under SPOOL &log_file_name as appropriate for your ASM environment, using the following syntax:

create tablespace &tablespace_name datafile <'&dbf_location/&tablespace_name..dbf'> size 512 M reuse autoextend on next 128 M maxsize 1024 M;

Where:

<&dbf_location/&tablespace_name..db> is the location and name of the data file.

Examples

The following SQL syntax creates a data file called OPdatafile in the Oracle data home location. The tablespace will be managed locally.

create tablespace &tablespace_name datafile <'&&3/OPdatafile.dbf'> size 512 M reuse autoextend on next 128 M maxsize 1024 M;

Where:

where &&3 will use the datafile_storage_location parameter entered with the crndbcreate.sql command (Oracle data home) for the datafile location and OPdatafile.dbf is the name of the data file


Task 2: Run the Database Creation ScriptTo create a CommandCenter database user, use SQL*Plus to execute the script crndbcreate.sql. This file is found on the OpenPages installation DVDs, as described in the steps below.

IMPORTANT! Ensure that the ORACLE_HOME variable is set and that ORACLE_HOME is in the PATH variable.

Steps:


Note: For AIX installs, log in as a non-root user.

2. Launch a Command Prompt window (using the Run as Administrator option) or AIX shell as a user with Administrative privileges.



OP_6.0.1_Configuration\Database\

b. Copy the COGNOS directory to the local system.


4. Navigate to the COGNOS directory.5. Log on to SQL*Plus using the following command.

sqlplus sys/<sys_password>@<SID> as sysdba

Note: To create the new tablespace in the OpenPages database instance, enter the SID of the OpenPages database. Or, to create the tablespace in the CommandCenter database instance (Content Store), enter the SID of the CommandCenter database.



6. At the SQL prompt, type the following command, as described in the following table:

@crndbcreate.sql <cognos8_user> <cognos8_password> <oracle_data_home> <tablespace_name> <cognos8.log>


cognos8_user Create a new user name for the Content Store database, such as cognos.

cognos8_password Enter a password for this new Content Store user.

oracle_data_home Enter the path to the Oracle data home directory on the database server, by default:

Windows

C:\openpages_data\repository\database_ac_x64\oradata\<SID>

AIX

/opt/oracle/openpages_data/repository/database112_se_x64/oradata/<SID>

tablespace_name Name of the exported tablespace, by default crn.

cognos8.log Log file for error and status messages.



Task 3: Modify Environment VariablesSet the following environment variables in Windows or AIX on the reporting server.

Modifying the Environment Variables - WindowsSet the environment variables on a Windows-based reporting server, as follows:

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. Launch Windows Explorer.3. Right-click Computer and select Properties from the menu.4. Click the Advanced system settings link. 5. In the System Properties dialog, click the Environment Variables button.6. Add the JAVA_HOME environment variable:

a. Click the New button.b. In the New System Variable window, enter JAVA_HOME in the Name field.c. Enter full path to the environment variable is configured to point to the installation

location of your Java Runtime Environment (JRE).d. Click OK.

7. Add the COGNOS_HOME environment variable:a. Click the New button.b. In the New System Variable window, enter COGNOS_HOME in the Name field.c. Enter full path to the environment variable is configured to point to the installation

location of Cognos 8.d. Click OK.

8. Add the ORACLE_HOME environment variable:a. Click the New button.b. In the New System Variable window, enter ORACLE_HOME in the Name field.c. Enter full path to the ORACLE_HOME directory, by default:

C:\openpages_data\repository\client112_ac_x86\software

Note: If you install the OpenPages application and CommandCenter on the same server, enter the location to the 32-bit Oracle Client.

d. Click OK.9. If the TNS_ADMIN variable does not exist, create the variable:

a. Click the New button.b. In the New System Variable window, enter TNS_ADMIN in the Name field.c. Enter full path to the tnsnames.ora file, which is usually located in the

<Oracle_Home>\network\admin directory.d. Click OK.

10. Set the NLS_LANG environment variable to the database character set configured during the database install, by default AMERICAN_AMERICA.AL32UTF8. a. Click the New button.b. In the New System Variable window, enter NLS_LANG in the Name field.c. Enter database character set specified during the database install. d. Click OK.

11. Add JAVA_HOME and ORACLE_HOME to the PATH variable: a. Select the PATH variable and click Edit.b. In the Edit System Variable window, add %JAVA_HOME%/bin and %ORACLE_HOME%/

bin.c. Click OK.

12. Click OK to save the changes and close the window.



Modifying the Environment Variables - AIXSet the environment variables on an AIX-based reporting server, as follows:

Steps:

1. Log onto the 6.0.1 reporting sever machine as a non-root user with administrative privileges.

2. Execute the following command to determine which executable are in the PATH:

java -version

If the PATH variable exists, the version of the Java executable appears. If you get a Java error: Command not found, the path is not set.

3. Execute the following commands to set the environment variables, using the appropriate paths:export JAVA_HOME=/opt/local/jdk1.6.0/bin

export COGNOS_HOME=/opt/cognos/cognos8


export TNS_ADMIN=$ORACLE_HOME/network/admin

export LIBPATH=$COGNOS_HOME/bin64:$COGNOS_HOME/bin:$ORACLE_HOME/lib


PATH=$ORACLE_HOME/bin:$JAVA_HOME/bin:$PATH

Where:

• JRE_HOME is the location of the JRE home directory, by default /opt/local/jdk1.6.0/bin.

• COGNOS_HOME is the location of the Cognos bin directory.• ORACLE_HOME is the Oracle data home.• TNS_HOME is the location of the tnsnames.ora file• NLS_LANG is the database character set specified during the database install.

Note: If you install the OpenPages application and CommandCenter on the same server, ORACLE_HOME must point to the 32-bit Oracle Client.

4. Refresh the profile by closing and re-opening the AIX shell or run the following command:

cd / . .profile

Task 4: Install Oracle 32-bit Client LibrariesCognos 8.4.1 requires 32-bit Oracle client libraries even if Cognos is running on a 64-bit OS. The Oracle 32-bit libraries are available in the ojdbc5.jar file, which was installed on the local server during the Oracle Client installation. You must install the ojdbc5.jar file into the Cognos environment on any client machine in order for Cognos to properly connect to the Oracle database.

Steps:

1. If the 6.0.1 CommandCenter server is running, stop the service.

Windows

a. Use the Windows Start menu to launch the IBM Cognos Configuration Tool. Right-click and select Run as Administrator.

b. Locate CommandCenter in the tree structure (Local Configuration > Environment > IBM Cognos 8 Service > IBM Cognos 8).

c. Right-click CommandCenter and click Stop.



d. Close the Cognos Configuration Tool.

AIX

a. Launch an AIX shell and navigate to the <COGNOS_HOME>/bin64 directory.b. Type the following command

./cogconfig.sh -stop

2. Copy the ojdbc5.jar from the OpenPages Repository directories to the Cognos directories:

Windows

Use Windows Explorer or the Command Prompt to copy ojdbc5.jar from: <ORACLE_HOME>\jdbc\lib to:

<COGNOS_HOME>\webapps\p2pd\WEB-INF\lib

AIX

Use the copy command to copy ojdbc5.jar from:

cp $ORACLE_HOME/jdbc/lib/ojdbc5.jar <COGNOS_HOME>/webapps/p2pd/WEB-INF/lib/ojdbc5.jar

3. Launch the Cognos Configuration tool as Administrator.4. Click the Save button. Saving the configuration will reload all the libraries, including

ojdbc5.jar.5. Test the connection to the Oracle database.

a. Locate IBM Cognos 8 in the tree structure (Local Configuration > Data Access > Content Manager > Content Store).

b. Right-click the Database Name and click Test. Cognos should report a successful connection.

6. Start the Cognos server.c. Locate CommandCenter in the tree structure (Local Configuration >

Environment > IBM Cognos 8 Service > IBM Cognos 8).d. Right-click CommandCenter and click Start.

Task 5: Set Database Connection Properties for CommandCenterAfter installing the Cognos software, you must configure Cognos to access the database. Using the Cognos tools, you must delete the connection to the CommandCenter database instance in the Cognos application and replace it with a new connection to CommandCenter and specify the connection settings.

Steps:

1. Log on to the 6.0.1 reporting server as a user with administrative privileges.2. On the CommandCenter server, start the IBM Cognos Configuration application as a

user with administrative privileges.3. Start IBM Cognos Configuration:


b. Navigate to the following directory:

<COGNOS_HOME>/bin64




Windows

cogconfig.bat

AIX

./cogconfig.sh

4. Expand the tree for Data Access | Content Manager.5. Remove the current database connection and add a new connection using the following

steps, based on your type of Oracle: a single Oracle database or an Oracle RAC database.

Single Oracle Database

For Oracle databases (non-RAC), use the following steps:





f. Click File | Save to save your changes.

Oracle RAC

For Oracle RAC databases, use the following steps:


New resource | Database.



Type Click the arrow and select Oracle Database from the list.




User ID and password Click the value field and then click the pencil icon.

In the Value - User ID and password field, enter the appropriate values for the Cognos user you created for the content store database.


Service name Enter the SID for the database instance.



c. In the New Database window, do the following:



6. Click File | Save to save your changes.

Task 6: Configure the Database to Support Multilingual ReportsThis task is required.

CommandCenter uses Tier 2 (OCI) JDBC drivers to connect to the Oracle database. If you want reports to display data in multiple languages, you need to configure the Oracle Client to use the appropriate character set.



Type Click the arrow and select Oracle Database (Advanced) from the list.




User ID and password Click the value field and then click the Edit icon.

In the Value - User ID and password field, type the appropriate values for the Cognos user you created for the content store database.


Database specifier Enter a database specifier string in the following format with no carriage returns:(description=(address=(host=<server_name>) (protocol=tcp)(port=<port>) (connect_data(service_name=<service_name>)))

Where:• server_name is the name of the RAC database

server.• port is the listener port used by the RAC

database server.• service_name is the service name of database

instance.This information is available in the tnsnames.ora file located by default at:<ORACLE_HOME>\network\admin

Example(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = RAC1)(PORT = 1522)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = OPdata)))



In order to do this, you must set the registry key NLS_LANG. In order to properly display multi-lingual text, the <CHARACTER_SET> portion of the NLS_LANG registry key must be set to AL32UTF8. For example, AMERICAN_AMERICA.AL32UTF8. Consult your Oracle administrator for the proper settings for <LANGUAGE> and <TERRITORY>.

Use the following steps to set the NLS environment variable appropriately for your environment.

Steps:



2. Set the NLS_LANG environment variable using the following command:

Windows

set NLS_LANG=AMERICAN_AMERICA.AL32UTF8

AIX

a. Enter the following line, if missing, in the .profile file in the root / folderb. Export NLS_LANG=AMERICAN_AMERICA.AL32UTF8 using the following command.


c. Execute .profile to get the NLS_LANG set in your shell window.d. Refresh the profile by closing and re-opening the AIX shell or by running the

following command:

cd / . .profile

Task 7: Manually Create the Content Store You can manually create a database schema for CommandCenter using the following steps.

Steps:

1. Log on to your 6.0.1 database server as a user with administrative privileges.2. Launch the Database Configuration Assistant, using one of the following methods:

If you purchased Oracle from... Then...

OpenPages, Inc. a. Open a Command Prompt window or AIX shell as a user with Administrative privileges.

b. Navigate to one of the following folders:

Windows openpages_data\repository\server112_se_x64\software\BIN

AIX /opt/oracle/openpages_data/repository/server112_se_x64/software/bin

c. Type dbca to launch the Database Configuration Assistant.

a vendor other than OpenPages, Inc.

a. Open a Command Prompt window or AIX shell as a user with Administrative privileges.

b. Navigate to one of the following folders:

Windows <Oracle_Home>\bin

AIX <Oracle_Home>/bin

c. Type dbca to launch the Net Configuration Assistant.



3. On the Welcome Screen, click Next to begin the database configuration.4. On the Operations screen:

a. Select Create a Database.b. Click Next.

5. On the Database Templates screen:a. Select Custom Database.b. Click Next.

6. On the Database Identification screen:a. Type the Global Database Identifier, for example, CS. The Oracle System Identifier

(SID) will automatically match the GDI.b. Click Next.

7. On the Management Options screen:a. Select the Configure Enterprise Manager check box.b. Select Configure Database Control for local management. c. Consult your DBA to determine whether you should enable E-mail Notifications and

Daily Backups. d. Click Next.

8. On the Database Credentials screen:a. Set the passwords for the default Oracle accounts. b. Click Next.

9. On the Network Configuration screen:a. Select Register this database with all the listeners.b. Click Next.

10. On the Database File Locations screen, do the following:a. Select File System for the Storage Type. b. Select the location for the database files as follows:

c. Optionally, click the File Location Variables button to display the current settings for the database template you have chosen. Click OK when you are done.

d. Click Next.11. On the Recovery Configuration screen:

a. Clear all check boxes.b. Click Next.

12. On the Database Content screen:a. Clear all check boxes except the Enterprise Manager Repository check box.b. Click Standard Database Components.c. Clear all check boxes.

Note: An Oracle message appears when you deselect the Oracle DB XML component. You may click OK and disregard this message. The Oracle components affected by clearing this option are not used by the OpenPages environment.

d. Click OK to close the dialog.e. Click Next.

If you want to... Select this option...

Use the same drive that the Oracle Home directory is located.

Use Database File Locations from Template

Place the files on a different drive or in another alternative location.

Use Common Location for All Database Files, and then type the desired location for the database files.



13. On the Initialization Parameters screen there are multiple tabs to modify:a. On the Memory tab, click the Custom option and then set the following options:

• Memory Management to Automatic Shared Memory Management. • SGA Size field to 1024 MB• PGA Size field to 768 MB

b. On the Sizing tab, set the following options:• Block Size to 8192 bytes • Processes to 250 processes

c. On the Character Sets tab:• Select the Use Unicode (AL32UTF8) option.• Set the National Character Set option to AL16UTF16 - Unicode UTF-16

Universal character set.

Note: You must create your database with the AL32UTF8 character set.

d. On the Connection Mode tab, select the Dedicated Server Mode option.14. Click the All Initialization Parameters button.

a. Enter the following custom settings:

b. Click the Show Advanced Parameters button.c. Enter the following custom settings:

d. When you have made the above changes, click Close.e. Click Next.

15. On the Database Storage screen:a. Review and modify (if necessary) the database storage parameters. b. Click Next.

16. On the Creation Options screen:a. Select the Create Database check box. b. Click Finish.

17. On the Configuration screen:a. Review all your settings.b. Click Finish to begin the database creation process.

Parameter Name Value

compatible 11.2.0.0

nls_length_semantics CHAR

Note: CHAR is required for localization.

open_cursors 300

processes 250

sessions 280

Parameter Name Value

optimizer_index_caching 100

optimizer_index_cost_adj 1

optimizer_mode FIRST_ROWS



Task 8: Modify the Instance Initialization ParametersAfter you create the instance, modify the Instance Initialization parameter using SQL*Plus.

To modify the parameter, use the following SQL*Plus commands in Windows or AIX, substituting your own values for the placeholder variables:

Steps:

1. Launch a Command Prompt window or AIX shell2. Log into SQL*Plus using the following command:

sqlplus system/<system_password>@<TNS_alias> as sysdba

Where:

system is the Oracle system user.

<system_password> is the password for the Oracle system user.

<TNS_alias> is the database alias name for the CommandCenter database instance.

3. Modify the initialization parameter using the following command.

alter system set optimizer_secure_view_merging=false scope=both commit;



H
Manually Installing the Application Server
This procedure is optional.

This chapter describes how to install application server software into the IBM OpenPages GRC Platform.


About Installing the Application Server on page 332 Checklist for Installing the Application Server Software on page 333 Before You Begin on page 334 Installing the Application Server Software on page 335


• • • • • • • • • •About Installing the Application Server

The OpenPages environment requires the installation of Web server software, either the Oracle WebLogic Server 10.3.2 or the IBM WebSphere Application Server 7.0.0.13 before installing the OpenPages application.

Note: If you purchased WebLogic Server as part of OpenPages (the OpenPages Embedded Installer), then the application server software is automatically installed during the OpenPages application installation and you can skip this chapter.

For customers who purchased the application server software from another vendor, this chapter details how to perform a WebLogic Server or WebSphere Application Server installation for use with the OpenPages application.

Use the instructions from the software vendor’s installation kit and follow the instructions in this chapter to install the application server manually before you begin the OpenPages application installation.

Operating System Application Server

Windows Oracle WebLogic Server 10.3.2

IBM AIX IBM WebSphere Application Server (WebSphere Application Server) 7.0.0.13

Appendix H: Manually Installing the Application Server


Checklist for Installing the Application

• • • • • • • • • •Server Software

Use the following checklist to guide you through installing the WebLogic Server or WebSphere Application Server software. Each task below has several steps. For horizontal cluster configurations, assume that each task must be performed on both the cluster administrator and cluster member servers unless indicated otherwise in the checklist.

Table H-1: Checklist for Installing the Web Sever

Task Checklist

Review the information in “Before You Begin” on page 334.

WindowsInstall the Oracle WebLogic Server 10.3.2 software. See “Installing the WebLogic Server Software” on page 335.

AIXInstall the WebSphere Application Server version 7.0.0.13 software. See See “Installing the WebSphere Application Server Software” on page 336.

a. Install the WebSphere Application Server fix pack. See “Installing the WebSphere Application Server V7.0 Fix Pack 13” on page 338.




Before starting the WebLogic Server or WebSphere Application Server server installation process, make sure you perform the following tasks.

PrerequisitesBefore starting the WebLogic Server or WebSphere Application Server server installation, verify your system requirements. See Chapter 2 “Prerequisites” on page 15.

Obtain InformationHave the following information available:

Location for the WebLogic Server or WebSphere Application Server software installation location


Create AIX PasswordsMake sure you have created the required users and groups for AIX. See “Create Users and Groups for AIX” on page 26.



Installing the Application Server

• • • • • • • • • •Software

Use the following procedures to install the applicaiton server software.

Installing the WebLogic Server SoftwareThe information in this topic applies only to Windows environments.

In a Windows environment, use the command line to install WebLogic Server. The WebLogic Server installer is available in 64-bit (wls1033_generic.jar) or 32-bit (wls1032_generic.jar). Use the following steps to install WebLogic Server on each application server.

Steps:

1. Log on to the 6.0.1 application server as a user with administrative privileges. 2. Launch a Command Prompt window (using the Run as Administrator option) and

navigate to the directory that contains the WebLogic Server installation media.3. Run the installer for 64-bit systems (wls1033_generic.jar) from your WebLogic

Server installation media, using the following command:

java -jar wls1033_generic.jar

4. On the Welcome screen, click Next to continue.5. On the Create New Middleware Home screen:

a. Select a location for the WebLogic Server middleware home directory or use an existing home directory.

b. Click Next to continue. 6. On the Register for Security Updates screen:

a. Optionally register for Oracle updates. b. Click Next to continue.

7. On the Choose Installation Type screen: a. Select Custom. b. Click Next to continue.

8. On the Choose Products and Components screen:a. Ensure that all components are selected, except for Server Example. b. Click Next to continue.

9. On the JDK Selection screen:a. Select one or more Java Development Kits to install or click Browse to locate an

exiting JDK (1.6.0_05 or greater). b. Click Next to continue.

10. On the Choose a Product Installation Directory screen:a. Select a location for the WebLogic Server installation directory.b. Click Next to continue.

Note: Take note of the installation directory; you will need this information later. This location will be referenced during the OpenPages installation procedures as <WL_HOME>, by default: c:\Oracle\Middleware\wlserver_10.3).

11. On the Install Windows Service screen:a. Select No to not install a node at this time. b. Click Next to continue.



12. On the Installation Summary screen:a. Review your selections. b. When you are satisfied, click Next to begin the installation; otherwise, use Back to

go back and change information.13. Click Next to begin the installation.14. After the installation finishes, clear the Run Quickstart option and click Done to exit

the installer.

Installing the WebSphere Application Server SoftwareThe information in this topic applies only to AIX environments.

Use the following steps to install WebSphere Application Server on each application server.

During the installation, if you are installing as a non-root user, you may see a message indicating that the installation directory must have been created by root. If you created this directory as root, you can disregard this message.

Steps:

1. Log on to the 6.0.1 application server as a non-root user with administrative privileges. You can use WebSphere Application Server user which you created earlier.

2. Launch an AIX shell as root, then create a directory for the installation files in an appropriate location, such as /opt/opuser/WebSphere.

mkdir /opt/opuser/WebSphere

3. Launch an AIX shell as the non-root user, then select a umask that allows the owner to read/write to the files, and allows others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users, a umask of 002 or 022 could be used, depending on whether or not the users share the group.

To set the umask setting to 022, issue the following command:

umask 022

4. Ensure that you have 755 access to all directories where you download and install the software.

5. Access the root directory of your installation image on your hard disk, or insert the WebSphere Application Server installation disk into the disk drive.

6. Start the installation of a product image with the install command.

./install

The installation wizard initializes and then displays the Welcome panel.

7. On the Welcome screen, click Next to continue.8. On the License Agreement screen, select I accept both the IBM and the non-IBM terms

to agree to the license agreement. Click Next to continue.9. On the Systems Prerequisite Check screen, confirm that your operating system is

supported and that you have installed all necessary patches. Click Next to continue.• If the wizard detects a previous installation, the Product-Detection screen is

displayed. • If the wizard does not detect a previous installation, go to the next step.



10. On the Optional Features Installation screen:a. Optionally, select the features you want to install. The following table provides

descriptions and default values for this screen.

b. Click Next to continue.11. On the Installation Directory screen:

a. Specify the destination of the installation root directory, such as /opt/IBM/WebSphere/AppServer.

The installation root directory is the location for product files or system files.

Take note of the installation directory; you will need this information later. This location will be referenced during the OpenPages installation procedures as <WL_HOME>. If <WL_HOME> is referenced during an installation, it is referring to the product installation directory (for example, c:\Oracle\Middleware\wlserver_10.3).

Note: Do not use spaces in the name of the installation directory. These spaces are not supported.

b. Click Next to continue.12. On the WebSphere Application Server Environments screen:

a. Select None. b. Click Next to continue. A message asking if you want to proceed without creating a

profile displays.c. Click Yes in the warning. When you install OpenPages, that installer will create a

profile for the WebSphere Application Server.13. On the Repository for Centralized Installation Managers screen:

a. Select Create a repository for Centralized Installation Managers. The following fields appear.

b. Select the Populate the repository with this installation package.c. Enter the location for the repository or accept the default.d. Click Next to continue.

14. On the Installation Summary screen:a. Review your selections. b. Click Verify my permissions to perform this installation.c. When you are satisfied, click Next. The WebSphere Application Server performs

tests to verify permissions.d. If successful, click Next to begin the installation.

15. In the Installation Results screen, verify the installation.16. You may also check the installation log file, {app_server_root}/logs/install/

log.txt to verify that there were no file system or other unusual errors while installing. 17. Click Finish to close the installation wizard.

Field Description Required?

Install the sample applications Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.

Not recommended

Install non-English language packages for the administrative console

Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.

Optional

Install non-English language packages for the application server runtime environment

Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

Optional



Installing the WebSphere Application Server V7.0 Fix Pack 13You must obtain and install the 7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX.

Note: The administrative user that launches the Update Installer program must be able to run the slibclean command. If not, log in as a root user and execute the slibclean before running the Update Installer.

On the application server where WebSphere Application Server is installed:

1. Log on to the 6.0.1 application server as the same user that installed the WebSphere Application Server.

2. If running, stop the WebSphere Application Server process and any related processes. For example, execute the following command:

stopServer

3. Launch an AIX shell as root, then create a directory for the installation files in an appropriate location, for example:

mkdir /opt/opuser/WebSphere/WebSphere_Update

4. Download the WebSphere Application Server 7.0.0.13 Update Installer package for AIX from the IBM Web site, or other source, into the new directory.

5. Extract the Update Installer package tar file.6. Launch an AIX shell as the non-root user, such as opuser, which you created for the

OpenPages installation. 7. Navigate to the /opt/opuser/WebSphere/WebSphere_Update/UpdateInstaller

subdirectory.8. Launch the Update Installer using the following command:

./install

9. Navigate to the installation root directory specified during the new install, for example:

/opt/IBM/WebSphere/WebSphere_Update/UpdateInstaller

10. Launch the Update Installer using the following command:

./update.sh

The Update Installer uses the same screens as the new installer.



I
Installing the OpenPages Database Schema

This procedure is optional.

This chapter describes how to create the OpenPages Database Schema, a set of database users and a tablespace. Use the steps in this chapter if you want to manually create the OpenPages Database Schema.

If you want to allow the OpenPages application installer to create the database schema, skip this chapter and see Chapter 5 “Installing the OpenPages Application” on page 65.


About Installing the OpenPages Database Schema on page 340 Before You Begin on page 341 Installing the 64-Bit Oracle Client on page 342 Changing Database Object Names for ASM on page 343 Verify Default Definition Values on page 345 Create the Database Components on page 346


About Installing the OpenPages

• • • • • • • • • •Database Schema

The IBM OpenPages GRC Platform requires that you create the OpenPages Database Schema, a set of database users and a tablespace. The OpenPages installation kit contains SQL wrapper scripts that create the required users and tablespace.

These scripts work the same in both Windows and AIX environments.

Note: You have the option to create the OpenPages Database Schema automatically using the OpenPages application installer.

Depending on your particular environment, the table below outlines both methods you can use to install the OpenPages Database Schema.

If you want to install the OpenPages Database Schema... Then...

As part of the OpenPages application instal-lation, using the OpenPages application installer

Skip this chapter and go to “Installing the OpenPages Application” on page 65.

As a manual process using the SQL wrap-per scripts included in your installation kit

See “Create the Database Components” on page 346 in this chapter.

Appendix I: Installing the OpenPages Database Schema



Before you create the OpenPages Database Schema, make sure your system and environment meet the required prerequisites, as discussed in Chapter 2 “Prerequisites” on page 15.

Have the following information available:

Workflow user name Workflow user password TNS name alias System user name System user password OpenPages super administrator user name (See “Planning Your Installation” on page 9.) OpenPages super administrator password


Check the File Size of tmp Directory


The installer uses the tmp directory to store temporary files during the installation. The tmp directory on the database server must be a minimum size of 4GB.

The /tmp directory is located within the root directory.

Set Execution Permissions


In an AIX environment, set execute permission on the files/directories in the installation kit. After you copy the install kit files, launch an AIX shell and navigate to the parent of that directory. Type:

chmod -R 755 <Directory_Name>, then press Return.



Run the following command as the root user to create and change the ownership of the folder where Oracle Client will be installed, such as /opt/OEI/Oracle.

Steps

1. Log onto the database server as root.2. Open an AIX shell and enter the following command:

mkdir -p <SOFTWARE_DIRVE> chown -R opuser:staff <SOFTWARE_DRIVE>

Example

mkdir -p /opt/OEI/Oracle chown –R opuser:staff /opt/OEI/Oracle



• • • • • • • • • •Installing the 64-Bit Oracle Client

You need to install the 64-bit Oracle Client on the application server using the instructions in Chapter 5 “Installing the OpenPages Application” on page 65 in order to allow OpenPages to contact the Oracle database. Oracle Client provides drivers, networking components, and tools that enable OpenPages to remotely connect to the database.



• • • • • • • • • •Creating the Tablespace and Users

This section contains directions for manually creating the necessary OpenPages database structures using the SQL wrapper script provided by IBM.

Note: The Oracle 11g R2 database must be installed before you can install the OpenPages database component.

You can also use the SQL wrapper script to properly execute a number of other scripts provided by IBM for the upgrade or modification of the database.

About the ScriptsTo create the OpenPages application tablespace and users, you will run a SQL wrapper script, which calls other script.

The SQL wrapper (database-install.sql) runs the necessary SQL scripts in the correct order, and provides the proper parameters for the manual installation, upgrade, or modification of the database.

The wrapper script contains certain default definition values that cannot be passed on the command line and can only be modified in the file, such as the OpenPages administrator user account, base currency denomination and the location of the OpenPages storage folder.

Note: Base currency is the currency used as the basis for an exchange rate conversion.

IMPORTANT! You cannot change the base currency after installation.

op-app-global-env.sql. The custom environment script is called by the wrapper script and defines the Super Administrator user account. The user account values in this script should be verified as well.

Modify the default values in two scripts to ensure the proper parameters are used (as described on the following page).

Changing Database Object Names for ASMThis procedure is optional.

The IBM OpenPages GRC Platform hard-codes the names and locations of tablespaces, data directories, and data files in the OpenPages database. In some cases, these hard-coded values may conflict with internal systems, practices, or IT policies.

For example, the installers create a data file named aurora.dbf. The aurora.dbf data file is designed to hold all OpenPages data. Oracle Automatic Storage Management (ASM) allows you to use SQL statements to change the name of the data file.

For an ASM database, to change the name of the data file in the OpenPages database a site DBA or OpenPages representative must update the scripts used to create the tablespace.

create-opx-tablespaces.sql. This SQL script creates tablespaces for OpenPages application tables.

ibpm-ts-and-schema-owner.sql. This PL/SQL script creates tablespaces for IBPM application tables.

Each of these scripts is called by the database-install.sql script and must be modified before running the database-install.sql script.

IMPORTANT! Do not change the tablespace name through these scripts. The installer validates the tablespace name and will not proceed if the name is different from the default.



To modify the data file name, use the following steps.

Steps

1. Log on to a system as a user with Administrator privileges. You can use any system with access to SQL*Plus that can connect to the database server.







4. Navigate to the INSTALL SCRIPTS directory on the local system.5. Open the create-opx-tablespaces.sql script in a text editor such as WordPad or vi.6. Modify the SQL script under permanent storage, protected by logging, dedicated

temporary tablespace and/or temporary storage, no logging protection as appropriate for your ASM environment, using the following syntax:

CREATE TABLESPACE iflowdb DATAFILE <'&dbf_location/&tablespace_name.dbf'> SIZE 25M REUSE AUTOEXTEND ON NEXT 25M MAXSIZE UNLIMITED ONLINE EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K';

Where:

<&dbf_location/&tablespace_name..db> is the location and name of the data file.

7. Save and close the file.8. Open the ibpm-ts-and-schema-owner.sql script in a text editor such as WordPad or

vi.9. Modify the SQL script under ReCreate the tablespace and RECREATE THE USER as

appropriate for your ASM environment, using same syntax as above.10. Save and close the file.

Examples

The following SQL syntax creates a tablespace with a data file called OPdatafile in the Oracle data home location. The tablespace will be managed locally.

CREATE TABLESPACE iflowdb DATAFILE <'&&10/OPdatafile.dbf'> SIZE 25M REUSE AUTOEXTEND ON NEXT 25M MAXSIZE UNLIMITED ONLINE EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K';

where &&10 will use the datafile_storage_location parameter entered with the database-install.sql command (Oracle data home) for the data file location and OPdatafile.dbf is the name of the data file.

The following SQL syntax creates a temporary tablespace with a data file in disk group disk_group_1. The tablespace will be managed locally.

CREATE TEMPORARY TABLESPACE OPDATA_TEMP TEMPFILE '+disk_group_1' SIZE 2G EXTENT MANAGEMENT LOCAL;

where disk_group_1 is the name of the disk group.



Creating the Tablespace and Users using ScriptsThis section contains directions for running the database-install.sql script to manually create a database instance for OpenPages.

You can execute the SQL scripts from any computer that has SQL*Plus installed and access to the database server. This script requires SYSDBA privileges to run.

Before running any wrapper scripts, you should verify and modify, as necessary, the default definition values in the following scripts. These scripts work the same in both Windows and AIX environments.

To execute the SQL wrapper script, follow these steps.

Steps:

1. Log on to the 6.0.1 cluster administrator machine as a user with administrative privileges.

Note: For AIX installs, log in as a non-root user.







4. Navigate to the INSTALL SCRIPTS directory on the local system.

Task 1: Verify Default Definition Values1. Open the wrapper script sql-wrapper.sql in a text editor and modify the values as

necessary for the following definitions:

Windows

• define opx_base_currency_iso_code='USD'• define opx_dflt_stor_srv_root='C:\openpages-storage'

AIX

• define opx_base_currency_iso_code='USD'• define opx_dflt_stor_srv_root='/opt/openpages-storage'

Do not change the define opx_op_admin_name or define opx_op_admin_pwd definitions.

Example

By default, the base currency is set to USD. If you use Euros as your base currency, you would change the default ISO currency code from ‘USD’ to ‘EUR’ as follows:

define opx_base_currency_iso_code='EUR'




3. From the INSTALL_SCRIPTS directory, open the custom environment script op-app-global-env.sql in a text editor and modify the following default values as necessary for the Super Administrator:• define super_admin_username='OpenPagesAdministrator'• define super_admin_password='OpenPagesAdministrator'


Task 2: Create the Database Components1. Run the database-install.sql wrapper script using the following syntax:

sqlplus /nolog @database-install.sql database-install.sql <log_file> <oracle_tns_alias> <dba_user> <dba_password> <workflow_user> <workflow_password> <op_user> <op_password> <datafile_storage_location>

The following table lists the parameters that must be passed to the SQL wrapper script.


log_file The name of the log file that the script will create and write information to.

Example: logfile.txt

oracle_tns_alias The database alias for the OpenPages database instance, as set during the Oracle database installation.

If necessary, you can retrieve this alias from the tnsnames.ora file.

Example: OP

dba_user The Oracle system user name.

If you do not have access to the system user account, then any database user that has administrative privileges will work for the purposes of the installation.

Example: system

dba_password The password for the Oracle system account defined above.

Example: openpages

workflow_user The workflow database user name.

OpenPages uses this account to create and access the workflow database, and to manage workflow-related transactions.

Example: opworkflow

workflow_password The password for the workflow database user account defined above.

Example: opworkflow

op_user The user name used by OpenPages to create and access the OpenPages database instance.

Example: openpages

op_password The password for the OpenPages database user account defined above.

Example: openpages



Example

The following sample code shows the SQL*Plus command line with the example values (taken from the above table) for the variables.

Windows

sqlplus /nolog @sql-wrapper.sql database-install logfile.txt OP system openpages opworkflow opworkflow openpages openpages C:\openpages_data\repository\database112_se_x64\oradata\OP

AIX

sqlplus /nolog @sql-wrapper.sql database-install logfile.txt OP system openpages opworkflow opworkflow openpages openpages /opt/openpages_data/repository/database112_se_x64/oradata/OP

After the SQL script finishes, the OpenPages Database Schema is created, and a log file is placed in the directory where you ran the SQL script. The name of the log file matches the value of the log_file parameter you entered for the command.

If you experience problems running this script, you can use the init-db-cleanup command to remove the database components added by the script, allowing you to run the script again into a clean database environment, using these parameters as defined in the table above.

sqlplus /nolog @sql-wrapper.sql init-db-cleanup.sql <log_file> <oracle_tns_alias> <dba_user> <dba_password> <workflow_user> <op_user>

datafile_storage_location The location of the Oracle data directory on the database server. The location of this directory was set during the Oracle installation process.

IMPORTANT! Enter the path using the conventions required by the operating system of the database server (either Windows or AIX).

Example:• if the database server is running Windows, enter

C:\openpages_data\repository\ database112_se_x64\oradata\OP

• If the database server is running AIX, enter /opt/openpages_data/repository/ database112_se_x64/oradata/OP




J
Installing Client-Side Applications
This appendix describes how to install the client-side applications that are included in the IBM OpenPages GRC Platform installation kit.


Installing and Configuring Cognos 8 Go! Office — Windows only on page 350 Installing Cognos Framework Manager — Windows only on page 352

The install kit also includes an installer for OpenPages Workflow Studio, which is documented in the Workflow Studio Installation Guide on the Installer Disc 1 DVD in the OP_6.0.1_Documentation\documentation\ directory.


Installing and Configuring Cognos 8 Go!

• • • • • • • • • •Office — Windows only


IBM Cognos Go! Office is a client-side application that can be installed on the reporting server or on another computer that can connect to the reporting server.

Pre-requisitesIBM Cognos 8 Go! Office requires Microsoft .NET Framework version 2.0 be installed on client systems before the installation.

Installing Go! OfficeThe information in this topic applies only to Windows environments.

Use the following steps to install IBM Cognos Go! Office.

Steps

1. Log on to your 6.0.1 reporting server as a user with administrative privileges.2. Ensure the CommandCenter service is stopped.3. Launch a Command Prompt window (using the Run as Administrator option).4. Copy the OP_6.0.1_Standalone_Clients directory from the Installer Disc 1 DVD or

on your network share location to the local system.a. Navigate to the following folder:

OP_6.0.1_Standalone_Clients

b. Copy the IBM Cognos 8 Go! Office directory to the local system.5. Navigate to the IBM Cognos 8 Go! Office\bin directory.6. Launch the installer:

Type issetup.exe.

7. On the Welcome screen:a. Select the language to use for the installation (English is the default).b. Click Next.

8. On the IBM License Agreement screena. Accept the License Agreement on the next screen. b. Click Next to continue.

9. On the Installation Location screen:a. Type a location for the Cognos 8 Mobile files.

Note: Use the same installation location for Framework Manager that you used for Cognos 8 BI. Such as:

C:\OpenPages\Cognos\cognos\c8

b. Click Next to continue.

Appendix J: Installing Client-Side Applications


10. On the Component Selection screen:a. Select all components. b. Click Next to continue.

11. On the Shortcut Folder screen:a. Type a folder for the Dashboard shortcut. b. Select Make the Shortcuts Visible to All Users. c. Click Next to continue.

12. On the Installation Summary screen:a. Review your choices. b. Click Next to install Cognos 8 Go! Mobile.

13. When the installation is complete, click Finish.



Installing Cognos Framework Manager

• • • • • • • • • •— Windows only


After Cognos BI is installed, install Cognos 8 Framework Manager, the Cognos metadata modeling component. Framework Manager is a client-side application that can be installed on the reporting server or on another computer that can connect to the reporting server.

IMPORTANT! Cognos 8 Framework Manager can be installed only on a Windows system.

Pre-requisitesBefore installing Framework Manager on a client system ensure that Oracle Client 32-bit software is installed on that client.

Installing Framework ManagerThe information in this topic applies only to Windows environments.

Steps:

1. Log on to the 6.0.1 reporting server or client system as a user with administrative privileges.

2. Launch a Command Prompt window (using the Run as Administrator option).3. Copy the OP_6.0.1_Standalone_Clients directory from the Installer Disc 1 DVD or

on your network share location to the local system.a. Navigate to the following folder:

OP_6.0.1_Standalone_Clients

b. Copy the OP_6.0.1_Standalone_Clients/IBM_Cognos_Framework_Manager/win32 directory to the local system.

4. Navigate to the OP_6.0.1_Standalone_Clients/IBM_Cognos_Framework_Manager/win32\Win32 directory.

5. Launch the installer by typing issetup.exe.6. On the Welcome screen:

a. Select the language to use for the installation (English is the default).b. Click Next.

7. On the License Agreement screen:a. Review and accept the license agreement. b. Click Next.

8. On the Installation Location screen:a. Type a location for the Framework Manager files.

If installing on the reporting server, install Framework Manager to a different directory as Cognos. For example:

C:\OpenPages\Cognos\cognos\FrameworkManager

b. Click Next. c. If the directory does not exist, on the Installation Location warning screen, click

Yes to create the directory.



9. On the Component Selection screen:a. Select the components you want to install.b. Click Next.

10. On the Shortcut Folder screen:a. Type a folder for the Framework Manager shortcut.

If installing on the reporting server, enter a different name for the Framework Manager. For example: IBM Cognos 8 Framework Manager

b. Select the option Make the shortcuts visible to all users. c. Click Next.

11. On the Installation Summary screen:a. Review your selections. Click Back to return to an earlier screen to make any

required changes.b. Click Next.

12. When done, click Finish.

Note: To launch Framework Manager, you will need valid credentials for the reporting server (user name/password).

Configure Framework ManagerThe information in this topic applies only to Windows environments.

After installing Framework Manager, perform the following configurations.

Task 1: Set the Oracle Home Location.Ensure that <Oracle_Home> is pointing to the Oracle Client 32-bit instance.

1. Log on to the system where you installed Framework Manager as a user with administrative privileges.

2. In Windows Explorer, right-click the Computer icon and select the Properties option.3. In the System Properties dialog box, choose the Advanced System Settings link.4. Click the Environment Variables button.5. Locate the Oracle_Home variable and ensure that it points to the 32-bit client.

C:\openpages_data\repository\server112_ac_x86\software

Task 2: Specify the Reporting ServerConfigure the dispatcher and gateway URI to point to the appropriate reporting server. Framework Manager uses these URIs to connect to the reporting server.

Steps:

1. Log on to the system where you installed Framework Manager as a user with administrative privileges.



<COGNOS_HOME>/bin64


cogconfig.bat



3. In the Explorer pane, click Environment4. In the Properties pane, change the Gateway URI value to replace localhost with

name of reporting server.5. Change the Dispatcher URI for external applications value to replace localhost

with name of reporting server.6. Save the configuration.



K
SQL Files
This appendix contains a partial listing of the SQL scripts included with the IBM OpenPages GRC Platform install kit.

The following tables contain the name of the SQL script, a short summary of the script’s function, and the user name of the executor of the script.


• • • • • • • • • •SQL Files Used During a Fresh Installation

Schema and Storage

Table K-1: Schema and Storage Files

File name Run as Comments

database-install.sql DBA Wrapper script that creates application and workflow tablespaces, creates schema owners, creates schema objects, loads bootstrap data and collects statistics

init-db-create.sql DBA The same as the above

create-opx-tablespaces.sql DBA Creates application tablespaces

create-opx-schema-owner.sql DBA Create application schema owner

AuroraDBCreate.sql Application user Creates tables, indexes and constraints in application schema

AuroraDBViews.sql Application user Creates views in application schema

iFlow.sql DBA Creates workflow user schema, tablespaces and database objects

uniform-grants.sql DBA Grants required rights to the application and workflow schema owners

dba_integrate_iflow.sql DBA Creates synonyms for the workflow-related database objects in the application schema

collect-schema-stats.sql Schema owner Collects missing and updates stale statistics on a schema level

enable-session-sleep.sql DBA Grants access to DBMS_LOCK package in order to enable DB Session Sleep functionality

no-op.sql Application user Reserved for future use

add-archive-storage-server.sql Application user Adds new archive storage server

sysdba-xa-grants.sql SYSDBA Grants to the workflow and OpenPages schema owners specific privileges required to use XA transaction management.

sysdba-create-xa-views.sql SYSDBA Creates dictionary objects that are required to support XA distributed transaction processing.

Appendix K: SQL Files


Stored Procedural Code

Bootstrap Data

Table K-2: Stored File Procedure

File Name or Pattern Run As Comments

AuroraProcCreate.sql Application user Wrapper script that loads stored procedural code into application schema and creates the required Oracle jobs in the application schema

auto-collect-wfx-stats.sql Workflow user Creates stored procedure and Oracle job for automatic statistics collection in the workflow schema

pks_*.sql N/A Application schema package declarations

pkb_*.sql N/A Application schema package definitions

tps_*.sql N/A Application schema type declarations

tpb_STRING_AGG_TYPE.sql N/A Application schema trigger definitions

trg_*.sql N/A Application schema trigger definitions

fn_STRAGG.sql Application schema trigger definitions

Table K-3: Bootstrap Data Files


AuroraDBLoad.sql Application user Loads initial data into application schema.

load_PROCESS_TYPES.sql N/A Executed from AuroraDBLoad.sql

load_ERROR_MESSAGES.sql N/A Executed from AuroraDBLoad.sql

load_REGISTRY_ENTRIES.sql N/A Executed from AuroraDBLoad.sql

load_REPORTING_SCHEMA.sql N/A Executed from AuroraDBLoad.sql

load_RPS_RESERVED_WORDS.sql N/A Executed from AuroraDBLoad.sql

load_CURRENCY_CODES.sql N/A Executed from AuroraDBLoad.sql

load_SYSTEM_BUNDLES.sql N/A Executed from AuroraDBLoad.sql

load_BOOTSTRAP.sql N/A Executed from AuroraDBLoad.sql

load_ENUMERATIONS_global.sql N/A Executed from AuroraDBLoad.sql

load_OP_APP_BOOTSTRAP.sql Application user Executed from load_OP_APP_DATA.sql

load_OP_APP_DATA.sql Application user Used for fresh installations only



Workflow

Clean Up

Table K-4: Workflow Files


ibpm-create-procedures.sql DBA

ibpm-create-tables.sql DBA

ibpm-create-views.sql DBA

ibpm-data-load DBA

ibpm-set-properties.sql DBA

ibpm-ts-and-schema-owner.sql DBA Drops and recreates the IBMP schema owner and tablespaces.

Table K-5: Clean Up Files


init-db-cleanup.sql DBA Wrapper script that drops application and workflow schema owners and tablespaces. Intended to be used on test systems only.

init-db-user.sql DBA Drops and recreates application and workflow schema owners without loading bootstrap data. Intended to be used on test systems only.

dropuser.sql DBA Drops user schema, can optionally terminate open user sessions.

drop-opx-tablespaces.sql DBA Drops application tablespaces

drop-wf-tablespaces.sql DBA Drops workflow tablespaces

AuroraDBDelete.sql Application user, workflow user

Removes all the database objects from user schema. Intended for manual restore operations.



Miscellaneous

Table K-6: Miscellaneous Files


sql-wrapper.sql N/A Generic wrapper script that sets SQL*Plus run-time environment and logging

Analyze-Object-Type-Relations-9i.sql Application user Analyzes unused relationships, executed from runlooptest.sql

Analyze-Object-Type-Relations.sql Application user Analyzes unused relationships, executed from runlooptest.sql

op-app-global-env.sql Application user Defines Super Administrator credentials

run-loop-test.sql Application user Checks Oracle version and invokes analysis of relationships between object types



L
Notices
This appendix lists official notices.


• • • • • • • • • •Notices

This information was developed for products and services offered in the U.S.A.

IBM® may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents.

You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling:

(i) the exchange of information between independently created programs and other programs (including this one) and

Appendix L: Notices


(ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

201 Jones Road

Waltham, MA 02451

U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written.

These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Appendix L: Notices


Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both.

IBM

IBM logo

AIX

Cognos

OpenPages

ReportNet

WebSphere

Adobe, Acrobat, Flash and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

CCH is a registered trademark of Wolters Kluwer, and TeamMate EWP is a trademark of CCH, a Wolters Kluwer business.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Interstage is a trademark of Fujitsu Limited. Portions of this guide were reused or adapted from the Interstage Business Process Manager User Guide with written permission from Fujitsu, Inc.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation and/or its affiliates.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Appendix L: Notices

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository I

Index

Symbols

A

About

Oracle Database with OpenPages Repository50

access-web-browser 163

add

cluster members 195horizontal cluster member 218WebLogic cluster member 196WebLogic Server cluster member 195WebSphere cluster member 209

add WebSphere Application Server cluster mem-ber 195

admin server 9, 11

AIX

configuring web server for 114create install directory 53, 54, 71, 99, 128,

341filesets and 53installing OpenPages, about 39, 41set TMP file size 53, 71, 99, 128, 341set use permissions 341set user permissions 341starting services 180, 181

AL32UTF8 character set 328

anti-virus

disabling 53, 69, 98, 126Apache web server

configuring 114load-balancing (Windows) 229, 233

Ind

application readiness 170

application server

about 6adding after install 195assigned port 46configuring for Cognos 135, 239default port 44hardware requirements 16increase memory requirements 149, 150installed software 24installing on AIX 41installing on Windows 39load balancing and 220paging file size and 151port logs 45post-install tasks 145scaling and 220single sign-on and 308software prerequisites 23SSL configuration (AIX) 261SSL configuration (Windows) 246, 248web server and 332

B

backup/restore paths 87

base currency

setting 87, 343bos.adt.base AIX fileset 53

bos.adt.lib AIX fileset 53

bos.adt.libm AIX fileset 53

bos.perf.libperfstat AIX fileset 53

bos.perf.perfstat AIX fileset 53

bos.perf.protocols AIX fileset 53

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository II

C

certificate request

generating 263certificates

CommandCenter 267generating request for 249, 277importing 250, 263, 278importing into Java 264, 275secondary CommandCenter 242

CGI

allowing 110cgi-bin virtual directory 110

checklist

cluster administrator installation 43Cognos installation 97CommandCenter installation 125database installation 51OpenPages application installation 67post-installation 141SSL configuration 247, 285WebLogic installation 333WebSphere installation 333

cleanup-after-remove 188, 192

client software. See database client

client systems

installed software 24prerequisites 23

cluster

vertical for IBM WebSphere 209vertical for Oracle WebLogic 196

cluster administrator. See clustered environment.

clustered environment

about 220add member to 195admin server 9, 11administrator machine 9configure for SSL 255configuring 224example of CommandCenter 223example of OpenPages (AIX) 222example of OpenPages (Windows) 221load balancing and 12, 220, 239managed server 9, 11member machine 11member systems, adding 195

Ind

Cognos

Installer for Cognos 105Cognos 8 Business Intelligence Server. See Cog-

nos software.

Cognos 8 SDK. See Cognos software

Cognos Framework Manager 352

Cognos software

about 105checklist for installing 97Cognos service, starting 116database connection properties 119, 323Framework Manager installation 352Go! Office installation 350install 105post-install tasks 109pre-requisites for 98testing 122

cognos8 virtual directory 110

CommandCenter

See also Content Storeabout 7CGI files, allowing 110checklist for installing 125clustered example 223Cognos and 7configuring mail server account 136configuring Web server 110connection information 88database settings and 137e-mail account for 136hardware prerequisites 21hardware requirements 21host setting 158, 243installing 130Open Session commands 137optimization settings 137port setting 158, 243port settings, changing 158, 243post-installation tasks 135, 157pre-requisites for 98, 126reports, creating 157scaling and 11, 220SSL configurationCognos software

SSL configuration 267testing 122virtual directories, creating 110

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository III

CommandCenter database schema. See Content Store.

CommandCenter reports 157

default 157enabling 157

concurrency conflict 147

configuring

secondary CommandCenter server 241Content Store

create manually 315create tablespace for 317create user for 317creating manuallydatabase connection properties 119, 323tablespace, create 317user, create 317

creating 157

CSR

generating 249, 263, 277currency, base 343

D

database

about 6database client

about 32-bit 101about 64-bit 74CommandCenter, installing 101, 103installing on CommandCenter 101, 103interactive mode 57silent mode 59, 77

database home location. See ORACLE_HOME

database instance

installing 63database listener

installing 63database schema

about 12, 66installing 340prerequisites 341wrapper scripts and 343, 345

database server

assigned port 46checklist for install 51connecting OpenPages to 85

Ind

connection to 119, 323creating a database instance 328default port 44Enterprise Manager, starting 58hardware requirements 18installed software 24installing on AIX 41installing on Windows 39instance, installing 63listener, installing 63manually create users and tablespaces for

OpenPages 345net service name, adding 63optimize for CommandCenter 137port logs 45post-install tasks for 143pre-requisites 52prerequisites 23tuning memory 143

DEP 32

E

e-mail

setting for CommandCenter 136embedded OpenPages

about 7enabling DEP 32

Enterprise Manager, starting 58

environment variable

updating PATH 63environment variables

removing 52, 99setting 80

F

Framework Manager

starting 136Fujitsu Interstage BPM

multicasting and 8G

GNU tar 23

Go! Dashboard. See Cognos software

Go! Mobile. See Cognos software

groups 26

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository IV

H

hardware

application server requirements 16CommandCenter requirements 21database server 18database server (AIX) 19database server (Windows) 19database server requirements 18reporting server requirements 21

horizontal cluster, add member to 218

horizontal scaling

about 220example of 11

I

IBM Cognos 8 Business Intelligence. See Cognos software

IBM HTTP Web Server

load-balancing (AIX) 233IBPMAdminServer

domain accounts, and 225IIS

CGI files, allowing 110configuring 110

increasing the paging files size 151

installation 80

32-bit client 10164-bit client 74assigned ports 46Content Store, and 119, 323default ports 44DEP and 32disabling anti-virus 53, 69, 98, 126OpenPages application, and 79overview 38port logs 45post-installation tasks, AIX 42post-installation tasks, Windows 40removing environment variables 52, 99set user permissions 341setting environment variables 80tmp file and 53, 71, 99, 128, 341wrapper scripts and 343, 345

installation packages 7installation path

Ind

checklist for CommandCenter 97, 125, 247, 285

installation screens

BEA WebLogic Information 81Installer for Cognos 105

installing

workflow server 80Instance initialization parameters

for CommandCenter 329integrate-sso-with-op 307

interactive mode

database client and 74database client and CommandCenter 101database software and 57

InterstageBPMCS#

domain accounts, and 225J

Java

importing certificates into 264, 275Java Virtual Machine (JVM) 9JAVA_HOME

removing 99K

keystore

generating 246, 248, 262L

LDAP

disable 155listener

installing 63load-balanced environments 12

Domain Accounts, and 225load-balancing

about 220, 239application server configuration 220configuring 229, 309raising the Oracle connection limit 224reporting server configuration 239

log files 47

about 47location of 47

M

managed server 9, 11

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository V

memory allocation

increase for WebLogic 149increase for WebSphere 150on database server 143

Multicasting

about 8multi-lingual text 325

multiple CommandCenter servers 240

multiple server configuration 38

N

net service name

instanceadding 63

non-embedded OpenPages

about 7O

OEI_11GR2_DVD_1 37

OEI_11GR2_DVD_2 37

OP_6.0.1_Embedded_DVD_1 36

OP_6.0.1_Embedded_DVD_2 36

OP_6.0.1_Non_Embedded_DVD_1 36

OP_6.0.1_Non_Embedded_DVD_2 36

OPAdminWLS 174

op-app-global-env.sql 345

OpenPages

add new instance 195application server about 6assigned ports 46cluster member, add 195clustered example (AIX) 222clustered example (Windows) 221database and 6default ports 44default ports, change 286install database schema 340install process 38installation configurations 9installation packages 7installing on one server 305load balancing and 12multicasting and 8planning for 9port logs 45

Ind

requires servers 38scaling and 9, 220

OpenPages Administrator Guide 13

OpenPages application

adding after install 195allowing multiple users 147allowing workflow user to access 146anti-virus, disabling 69base currency, setting 87checklist for installing 67CommandCenter information, configuring 88concurrency conflict 147database connection, configuring 85database users, configuring 87directory settings, configuring 85installation, about 39installing 79, 80OpenPages configuration data, and 85post-install tasks 145prerequisites for 68, 98single sign-on and 308specifying installation directory 81SSL configuration 246, 248standard data, loading 88storage and backup/restore paths 87Super Administrator information, configuring

88workflow server information, configuring 83workflow user, configuring 87wrapper script to create OpenPages schema

345OpenPages application server. See application

server.

OpenPages CommandCenter. See Command Cen-ter.

OpenPages Database Schema. See database serv-er

OpenPages database. See database server.

OpenPages embedded

about 7OpenPages Installation Guide

about 1audience for 5organization of 3who should use 5

OpenPages non-embedded

about 7

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository VI

OpenPages Repository

about 6OpenPages server. See application server

OpenPages services

starting (AIX) 180, 181OpenPages Super Administrator 88

OpenPages workflow server. See workflow server.

OpenPagesAdminServer

domain accounts, and 225OpenPagesServer#

domain accounts, and 225Oracle Client 342

Oracle Client. See database client

Oracle database server. See database server

Oracle Enterprise Manager, starting 58

Oracle home location. See ORACLE_HOME

ORACLE_BASE

removing 52ORACLE_DATA_HOME

creating 57ORACLE_HOME 75

creating 57definition of 85removing 52set in PATH 63setting 80setting for OpenPages application 69

P

paging file size

increasing on application server 151increasing on reporting server 151

PATH variable

JAVA_HOME, removing 99modifying for installation 52, 80, 99ORACLE_BASE, removing 52ORACLE_HOME, adding to 63, 80ORACLE_HOME, removing 52PERL5LIB, removing 52TNS_ADMIN, removing 52

PERL5LIB

removing 52port assignments

assigned 46

Ind

default 44logs of 45

port-based URL routing 220

ports

change default 286CommandCenter 44dynamically assigned 46fixed 44Framework Generator 44OpenPages admin server 44OpenPages admin server SSL 44OpenPages application 44OpenPages application SSL 44OpenPages database instance 44Oracle console 44workflow admin server 44workflow admin server SSL 44workflow application 44workflow application SSL 44

post-installation

application server and 145checklist for install 141Cognos software and 109CommandCenter tasks 135, 157database server and 143

prerequisites

application server 18client systems 23CommandCenter server 21OpenPages application 68, 98OpenPages application server 16OpenPages server 18software 23

Primary application server

Cognos Framework Manager 352primary CommandCenter server 240

R

reporting framework 157

reporting schema

creating 157reporting server

assigned port 46default port 44installed software 24installing on AIX 41

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository VII

installing on Windows 40load balancing and 239paging file size and 151port logs 45port settings, changing 158, 243pre-requisites 98, 99, 126prerequisites 23scaling and 220SSL configuration 267

reports

multiple language 325restore/backup paths 87

rsct.basic.rte AIX fileset 53

rsct.compat.clients.rte AIX fileset 53

S

scaling

about 9, 220CommandCenter and 11horizontal example 11vertical example 10

secondary CommandCenter servers 241

secure session cookies

disabling 265enabling 265WebLogic 260WebSphere 265

Secure Sockets Layer. See SSL.

Security 110, 111

servers list 46

service name, adding 63

session affinity 220

setting up users and groups 26

sharing network storage 225

silent mode

database client and 77, 103database software and 59

single sign-on. See SSO.

single-sever configuration 305

software

optional 24required 23

sql-wrapper.sql

about 343, 345

Ind

SSL

about 246application server configuration (AIX) 261application server configuration (Windows)

246, 248checklist for configuring 247, 285clustered environments and 255creating keystore 262generating certificate request 249, 263, 277generating keystore 262importing certificates 250, 263, 278importing certificates into Java 264, 275installing a certificate on CommandCenter 267OpenPages configuration 246, 248reporting server configuration 267with OpenPages 163workflow server configuration keytool com-

mand 246, 248SSO

OpenPages configuration 308standalone clients

installing 349, 361start OpenPages 170

automatically 171manually 171

starting

CommandCenter servers 243OpenPages 163OpenPages the first time 170OpenPages with Web browser 163

stopping

OpenPages automatically 174OpenPages manually 174

storage paths 87

stored procedures 357

Super Administrator

about 8T

third-party software

optional 24required 23

three server configuration 38

TNS_ADMIN

removing 52two server configuration 38

ex

IBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository VIII

U

update-storage script 225

users 26

set permissions for 341V

vertical scaling

about 220example of 10

virtual directories 110

W

web server

about installing 332configuring 110configuring for CommandCenter 110installing WebLogic 335installing WebSphere Application Server 336pre-requisites for 334virtual directories 111

WebLogic Server

about 6checklist for install 333default ports, change 286increase memory requirements for 149installing 335setting secure session cookies 260SSL configuration 246, 248See also application server

WebSphere

setting secure session cookies 265WebSphere Application Server

about 6default ports, change 286increase memory requirements for 150installing 336See also application server

WebSphere Server

checklist for install 333SSL configuration 261

Windows

configuring web server 110DEP and 32installing OpenPages, about 39

WinZip 23

workflow server

Ind

allowing OpenPages user to access 146installing 80settings for 83SSL configuration 246, 248

wrapper script

modify values 345parameters 226, 346running 345

wrapper scripts

configuring 345X

xIC.aix61.rte AIX fileset 53

ex

End ofIBM OpenPages GRC Platform 6.0.1 Installation Guide with Repository

public.dhe.ibm.compublic.dhe.ibm.com/software/.../6.0.1/installation_guide_with_openp… · ibm...

Documents