IBM OpenPages GRC Platform Version 6.2.1: Installation...

IBM OpenPages GRC PlatformVersion 6.2.1

Installation Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 153.

Product Information

This document applies to IBM OpenPages GRC Platform Version 6.2.1 and may also apply to subsequent releases.

Licensed Materials - Property of IBM Corporation.

© Copyright IBM Corporation, 2003, 2013.

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

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. IBM OpenPages GRC Platform components . . . . . . . . . . . . . . . 1Server topology and installation configurations . . . . . . . . . . . . . . . . . . . . . . . . 1

Vertical and horizontal scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Load balancing configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Clustered OpenPages environments . . . . . . . . . . . . . . . . . . . . . . . . . . 4

The OpenPages repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Oracle database software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Application server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5OpenPages workflow server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Cognos Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Content store database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Installation planning . . . . . . . . . . . . . . . . . . . . . . . . . 7Software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisite software for all servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisite software for the database server. . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisite software for application servers . . . . . . . . . . . . . . . . . . . . . . . . 8Prerequisite software for reporting servers . . . . . . . . . . . . . . . . . . . . . . . . 9Prerequisite software for OpenPages client computers . . . . . . . . . . . . . . . . . . . . 9

VMWare configuration requirements on Windows computers . . . . . . . . . . . . . . . . . . . 9

Chapter 3. Preparing your system for installation . . . . . . . . . . . . . . . . . 11The Super Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Users and groups for installations on Windows operating systems . . . . . . . . . . . . . . . . . 12Users and user groups for installation on AIX computers . . . . . . . . . . . . . . . . . . . . 12

Creating users and groups on the database server for AIX installations . . . . . . . . . . . . . . 12Creating users and groups on the application servers for AIX installations . . . . . . . . . . . . . 13Creating users and groups on the reporting servers for AIX installations . . . . . . . . . . . . . . 15

Enabling Data Execution Prevention for essential Windows programs and services . . . . . . . . . . . 17Optional: Changing the Temp directory for AIX installations . . . . . . . . . . . . . . . . . . . 18Optional: Changing the Temp directory for Windows installations . . . . . . . . . . . . . . . . . 18Installing WebLogic Server on Windows computers . . . . . . . . . . . . . . . . . . . . . . 18

Configuring WebLogic Server on a multihomed computer in a Windows environment . . . . . . . . . 19Installing WebSphere Application Server on AIX computers . . . . . . . . . . . . . . . . . . . 20

Installing the WebSphere Application Server fix packs on AIX computers. . . . . . . . . . . . . . 22Removing root user installation files for WebSphere Application Server . . . . . . . . . . . . . . 23

Multicasting in the OpenPages environment . . . . . . . . . . . . . . . . . . . . . . . . 23Port assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4. Oracle Database Server software installations . . . . . . . . . . . . . . 27Removing environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Prerequisite setup for AIX computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

AIX operating system file sets for Oracle database software . . . . . . . . . . . . . . . . . . 27Oracle Database Server installations . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Oracle package dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Adding an Oracle listener for the OpenPages database . . . . . . . . . . . . . . . . . . . . 30Creating a database instance for the OpenPages repository . . . . . . . . . . . . . . . . . . 31Adding a local net service name for the OpenPages database . . . . . . . . . . . . . . . . . . 33

Scripts to manually create the OpenPages database schema in Oracle before installation . . . . . . . . . . 34Creating the tablespace and users for the OpenPages database before installation . . . . . . . . . . . 35

Testing the connections to the database server and the OpenPages repository . . . . . . . . . . . . . 38

iii

Chapter 5. Cognos Business Intelligence installations . . . . . . . . . . . . . . . 41Installing IBM Cognos Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . 41Web server configuration options for Cognos BI . . . . . . . . . . . . . . . . . . . . . . . 43

Configuring IIS 7.0 Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Configuring virtual directories in IIS . . . . . . . . . . . . . . . . . . . . . . . . . . 45Configuring the Apache Web Server on a Windows operating system . . . . . . . . . . . . . . . 45Configuring the Apache Web Server on AIX or Linux operating systems . . . . . . . . . . . . . . 46

Configuring a connection to the content store for Oracle database . . . . . . . . . . . . . . . . . 46

Chapter 6. OpenPages application server installations . . . . . . . . . . . . . . . 49Prerequisite tasks for the OpenPages application installation . . . . . . . . . . . . . . . . . . . 49

64-bit Oracle Client software installations on OpenPages application servers. . . . . . . . . . . . . 49Copying the installation files for the application server . . . . . . . . . . . . . . . . . . . . 49Setting the ORACLE_HOME environment variable on OpenPages admin and managed servers . . . . . . 50

Custom OpenPages Database Schema installations . . . . . . . . . . . . . . . . . . . . . . 50Additional prerequisite setup for AIX computers . . . . . . . . . . . . . . . . . . . . . . . 51

Creating the installation directory for WebSphere Application Server . . . . . . . . . . . . . . . 51Worksheet for installing the OpenPages GRC Platform on application servers . . . . . . . . . . . . . 51Installing OpenPages and workflow server in interactive mode . . . . . . . . . . . . . . . . . . 53Testing the connections to the database server and the OpenPages repository . . . . . . . . . . . . . 61Starting WebLogic Server cluster members for the first time . . . . . . . . . . . . . . . . . . . 62

Chapter 7. OpenPages CommandCenter installations. . . . . . . . . . . . . . . . 65Prerequisite tasks for CommandCenter installations . . . . . . . . . . . . . . . . . . . . . . 65

Setting database environment variables for reporting servers on Windows operating systems . . . . . . . 65Setting environment variables for the reporting server on AIX computers. . . . . . . . . . . . . . 66Creating the installation directory for CommandCenter on AIX computers . . . . . . . . . . . . . 66Worksheet for CommandCenter installations . . . . . . . . . . . . . . . . . . . . . . . 67

Installing CommandCenter in interactive mode . . . . . . . . . . . . . . . . . . . . . . . 68CommandCenter post installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Creating the reporting schema and framework . . . . . . . . . . . . . . . . . . . . . . 72Changing the CommandCenter host settings . . . . . . . . . . . . . . . . . . . . . . . 74Creating an open session command block for the OpenPages data source . . . . . . . . . . . . . 75CommandCenter portal security . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 8. Post installation tasks . . . . . . . . . . . . . . . . . . . . . . . . 77Configuring OpenPages to work on a single computer . . . . . . . . . . . . . . . . . . . . . 77Verification checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Fix pack installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Database server tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Tuning the performance of the database instance . . . . . . . . . . . . . . . . . . . . . . 80Memory tuning guidelines for Oracle databases . . . . . . . . . . . . . . . . . . . . . . 80

Admin server tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Configuring the database connection pool on Windows computers . . . . . . . . . . . . . . . . 81Configuring the database connection pool on AIX computers . . . . . . . . . . . . . . . . . . 82Enabling simultaneous access to OpenPages applications and Fujitsu Interstage BPM for a single user on AIXcomputers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Preventing concurrency conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Optional: Increasing the paging file size on Windows computers . . . . . . . . . . . . . . . . 84Optional: Increasing the paging file size on AIX computers . . . . . . . . . . . . . . . . . . 85Increasing the Oracle WebLogic Maximum Message Size . . . . . . . . . . . . . . . . . . . 85

OpenPages application server tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Enabling LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Disabling LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Accessing OpenPages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 9. Starting and stopping OpenPages servers . . . . . . . . . . . . . . . 89Windows services used by OpenPages applications . . . . . . . . . . . . . . . . . . . . . . 89

Starting OpenPages application servers on Windows computers . . . . . . . . . . . . . . . . . 90Stopping OpenPages application servers on Windows computers . . . . . . . . . . . . . . . . 91

iv IBM OpenPages GRC Platform Version 6.2.1: Installation Guide

AIX scripts used to start and stop OpenPages application servers . . . . . . . . . . . . . . . . . 92Starting OpenPages application servers on AIX computers. . . . . . . . . . . . . . . . . . . 92Stopping OpenPages application servers on AIX computers . . . . . . . . . . . . . . . . . . 93

Chapter 10. Configuring clustered environments. . . . . . . . . . . . . . . . . . 95Configuring an OpenPages cluster to run as a Windows operating system service . . . . . . . . . . . . 95

Removing Windows operating system services for OpenPages and workflow servers . . . . . . . . . . 96Clustered OpenPages Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Increasing the Oracle connection limit . . . . . . . . . . . . . . . . . . . . . . . . . 97Configuring OpenPages applications to use a domain account on Windows operating systems . . . . . . 98Configuring file share permissions on AIX operating systems. . . . . . . . . . . . . . . . . . 98Sharing a network OpenPages storage directory on Windows operating systems . . . . . . . . . . . 98Sharing a network OpenPages storage directory on AIX operating systems . . . . . . . . . . . . . 100

Configuring Apache Web Server for load balancing in Windows environment . . . . . . . . . . . . . 102Customizing the load balancer in Windows environments for large data sets . . . . . . . . . . . . 105

Configuring IBM HTTP Server for load balancing on AIX operating systems . . . . . . . . . . . . . 106Configuring property files for load balancing on AIX and Linux operating systems . . . . . . . . . . 107Configuring property files for each OpenPages instance . . . . . . . . . . . . . . . . . . . 108Customizing the load balancer in an AIX environment for large data sets . . . . . . . . . . . . . 109

Load balancing the OpenPages reporting server . . . . . . . . . . . . . . . . . . . . . . . 110Adding OpenPages servers to Cognos Application Firewall safe list . . . . . . . . . . . . . . . 110Communication Between CommandCenter Servers . . . . . . . . . . . . . . . . . . . . . 111Configuring the primary CommandCenter server . . . . . . . . . . . . . . . . . . . . . 111Configuring secondary CommandCenter servers . . . . . . . . . . . . . . . . . . . . . 112Configuring an Apache load balancer or proxy server . . . . . . . . . . . . . . . . . . . . 113Changing the CommandCenter host settings . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 11. Single signon integration for OpenPages application server and thereporting server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Configuring OpenPages applications for single signon. . . . . . . . . . . . . . . . . . . . . 115Configuring the single signon logout destination . . . . . . . . . . . . . . . . . . . . . . 116Configuring the application server for single signon on Windows computers . . . . . . . . . . . . . 116Disabling OpenPages single signon . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Configuring single signon for a reporting server . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 12. Silent installations . . . . . . . . . . . . . . . . . . . . . . . . . 121Response files for silent installations. . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Editing the response file for 64-bit database client silent installations . . . . . . . . . . . . . . . 121Editing the response file for OpenPages application silent installations . . . . . . . . . . . . . . 122Editing the response file for CommandCenter silent installations . . . . . . . . . . . . . . . . 122

Response file parameters for use with silent installations . . . . . . . . . . . . . . . . . . . . 123Installation program in silent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Running the installation program for the database server in silent mode . . . . . . . . . . . . . 138Running the installation program for the database client in silent mode . . . . . . . . . . . . . . 139Running the installation program for the OpenPages application in silent mode . . . . . . . . . . . 139Running the installation program for the CommandCenter in silent mode . . . . . . . . . . . . . 140

Chapter 13. OpenPages GRC Platform software uninstallations . . . . . . . . . . . 141Uninstalling OpenPages applications . . . . . . . . . . . . . . . . . . . . . . . . . . 141Optional: Uninstalling the workflow server . . . . . . . . . . . . . . . . . . . . . . . . 142Uninstalling CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Appendix. Troubleshooting problems . . . . . . . . . . . . . . . . . . . . . . 145Troubleshooting resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Support Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146OpenPages Customer Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Fix Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Knowledge bases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Contents v

Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Installation issues and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Uninstalling OpenPages with an Oracle database before you reinstall . . . . . . . . . . . . . . 148Removing files on AIX computers after an incomplete Installation. . . . . . . . . . . . . . . . 149Manually loading the configuration data after a new installation . . . . . . . . . . . . . . . . 150OP-03620: The Reporting Schema has not been instantiated error . . . . . . . . . . . . . . . . 151

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

vi IBM OpenPages GRC Platform Version 6.2.1: Installation Guide

Introduction

This document is intended for use with IBM® OpenPages® GRC Platform. Theinformation includes planning, preparing for, completing, and maintaining productinstallations, configuring the product after installation, and some troubleshootingtips and techniques.

Installation and upgrade documentation

The instructions that you use to install or upgrade IBM OpenPages GRC Platformdepends on your environment.

Use the following table to find the right installation information for yourinstallation environment.

Table 1. Installation and upgrade documentation based on installation environments

OperatingSystem

ApplicationServer Database

InstallationType Document title

AIX® WebSphere® DB2® New Deploying to WebSphere Application ServerInstallation Guide

AIX WebSphere Oracle New Installation Guide

Installation Guide with Database

AIX WebSphere Oracle Upgrade Upgrade Guide

Linux WebSphere DB2 New Deploying to WebSphere Application ServerInstallation Guide

Linux WebSphere Oracle New Deploying to WebSphere Application ServerInstallation Guide

Windows WebSphere DB2 New Deploying to WebSphere Application ServerInstallation Guide

Windows WebSphere Oracle New orUpgrade

Deploying to WebSphere Application ServerInstallation Guide

Windows WebLogic Oracle New Installation Guide

Installation Guide with Database

Windows WebLogic Oracle Upgrade Upgrade Guide

Audience

This document is intended for use by OpenPages administrators. An administratormust have a background in operating systems administration, application servermanagement, relational database management, systems security management, andother aspects of systems management.

Related documentation

Supplemental documentation is available on the web. Go to the IBM OpenPagesPlatform documentation library IBM OpenPages GRC Platform documentationlibrary on the IBM support website (http://www.ibm.com/support/docview.wss?uid=swg27028308).

vii

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

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

To find IBM OpenPages product documentation on the web, access the IBMOpenPages Information Center (http://pic.dhe.ibm.com/infocenter/op/v6r2m1f0/index.jsp).

For information about OpenPages phrases and terminology, see the IBM OpenPagesGRC Platform Administrator's Guide.

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

Documentation conventions

To illustrate screen displays, menu items, product displays, information that youenter, the following typographic conventions are used:

Table 2. Typographic conventions used in this document

Convention Meaning

KEYWORD Keywords of SQL or some other programming languages aredisplayed in uppercase letters in a serif font.

italics

< text>

Variables that represent an object or entity that you replacewith specific information.Note: To avoid confusion, in some situations, angle bracketsenclose variables.

boldface Names of interface elements (such as icons, menu items, andbuttons) are displayed in boldface.

monospace Information that the product displays and information that youenter is displayed in a monospace typeface.

> This symbol indicates a menu item. For example, "ChooseTools > Options" means choose the Options item from theTools menu.

The installation directory is the location of product artifacts after a package,product, or component is installed. The following table lists the conventions thatare used to refer to the installation location of installed components and products.

Important:

v Directory locations that contain spaces are not supported. Do not installOpenPages or any software that OpenPages uses into a directory with spaces.For example, do not install database server, database client, or application serversoftware into the Program Files directory.

v Only install OpenPages or any software that OpenPages uses into a directorythat contains only ASCII characters in the path name.

Table 3. Typographic conventions for installation directories

Directory Meaning

OP_HOME The installation directory where OpenPages GRC Platform isinstalled.

On Windows computers, c:\OpenPages

On UNIX computers, opt/openpages

viii IBM OpenPages GRC Platform Version 6.2.1: Installation Guide

http://pic.dhe.ibm.com/infocenter/op/v6r2m1f0/index.jsp

http://pic.dhe.ibm.com/infocenter/op/v6r2m1f0/index.jsp

Table 3. Typographic conventions for installation directories (continued)

Directory Meaning

Workflow_HOME The installation location of Fujitsu Interstage BPM.

For example, C:\Fujitsu\InterstageBPM

ORACLE_HOME The installation location of the Oracle Client software.

For example, if you purchased Oracle database software fromIBM:

C:\openpages_data\repository\client112_ac_x64\software

Cognos_HOME The installation location of Cognos® Business Intelligence.

On Windows computers, C:\Program Files\IBM\cognos\c10_64

On AIX computers, /usr/IBM/cognos/c10_64

JAVA_HOME The installation location of your Java™ Runtime Environment(JRE) or your Java Development Kit (JDK).

For example, on a reporting server, JAVA_HOME would pointto the JRE used by the IBM Cognos installation, such asC:\Program Files\IBM\cognos\c10_64\bin64\jre\6.0

CC_HOME The installation location of OpenPages CommandCenter.

On Windows computers, C:\OpenPages\CommandCenter

On AIX computers, /opt/OpenPages/CommandCenter

Introduction ix

x IBM OpenPages GRC Platform Version 6.2.1: Installation Guide

Chapter 1. IBM OpenPages GRC Platform components

Use IBM OpenPages GRC Platform to manage risk and regulatory challengesacross the enterprise. OpenPages GRC Platform provides core services andfunctional components that span risk and compliance domains. These functionalcomponents include operational risk, policy, and compliance, financial controlsmanagement, IT governance, and internal audit.

The following diagram shows the architectural components for OpenPages GRCPlatform applications. The platform contains the database and key services such asthe security framework and reporting framework, the workflow engine, anddocument management. The modules are configurations that sit on top of theplatform.

Server topology and installation configurationsBefore you install OpenPages GRC Platform, plan the server topology. The numberof computers you use depends on the expected user loads.

The OpenPages GRC Platform consists of the following components:v Database serverv Application server

Figure 1. OpenPages GRC Platform components

1

v Reporting server

Use the following guidelines to help you determine your topology:

Two computers

For light user loads, install the OpenPages application and IBM Cognos BusinessIntelligence on the same computer as the application server. A second computerhosts the database server.

This topology is typical in a testing or staging environment. Do not use this setupin a production environment.

The following diagram shows a test environment that uses two computers for theOpenPages GRC Platform installation.

Three computers

For moderate user loads, use three computers: one database server, one applicationserver, and one reporting server. Install the OpenPages application on a singlecomputer with the application server software. The database server software andCognos Business Intelligence are each installed on separate computers

The following diagram shows an installation where the application server,reporting server and database server are each on separate computers.

Figure 2. Topology for test environments or light user loads

2 IBM OpenPages GRC Platform Version 6.2.1: Installation Guide

Multiple computers

To scale for heavier user loads, you can scale the OpenPages application verticallyor horizontally. You scale by configuring more nodes. Scaling either vertically orhorizontally requires that you use a load balancer. The load balancer distributes theincoming requests across the nodes.

To scale vertically, add a node to the same computer. To scale horizontally, add anode to an extra computer.

The following diagram shows an example of using a web server as a load balancer.The web server distributes incoming requests to horizontal cluster members.

Figure 3. Topology for moderate user load

Chapter 1. IBM OpenPages GRC Platform components 3

Vertical and horizontal scalingIf required, after the IBM OpenPages GRC Platform installation is complete, youcan add additional OpenPages managed servers. To scale vertically, you can addan OpenPages application and workflow managed server to an existing cluster. Toscale horizontally, you can add additional OpenPages application and workflowinstances onto an existing OpenPages cluster member.

Load balancing configurationsLoad balancing divides the load of incoming client requests across multipleapplication servers. The load on each computer is lessened. This configurationenables the OpenPages application to scale as the number of concurrent usersincreases.

The redundancy of the application tier, combined with the redundant hardware,also provides a path to high-availability for OpenPages.

Clustered OpenPages environmentsServer cluster consists of multiple OpenPages application and workflow serverinstances that run simultaneously to provide increased scalability.

The server instances that comprise a cluster can run on the same computer or ondifferent computers. You can add more server instances to the cluster on anexisting computer. You can also add computers to the cluster to host theincremental server instances.

Figure 4. Topology for heavy user load


The OpenPages repositoryThe OpenPages database is a central source for metadata management, versionedapplication data, and access control.

The OpenPages application requires a set of database users and a tablespace, calledthe OpenPages database schema. You install these database componentsautomatically during the OpenPages application installation or manually by usingSQL scripts. Both the scripts and the installation program create and configure allof the required elements.

Oracle database softwareAn Oracle database is used for the OpenPages GRC Platform repository.

You must obtain the Oracle database and client software from the vendor. Installthe Oracle database and the Oracle Client and also create a database instance. Youmust install the Oracle database before you install the OpenPages application.

Application server softwareAn application server is required to host the OpenPages applications. Theapplication server runs the application modules, and includes the definition andadministration of business metadata, UI views, user profiles, and userauthorization.

The application server software must be installed before you install the IBMOpenPages GRC Platform components.

For Windows installations, use WebLogic Server. For AIX installations, useWebSphere Application Server.

OpenPages workflow serverOpenPages workflow server provides automated workflow capabilities to ensureconsistent execution of business processes. Fujitsu Interstage BPM is installed aspart of the OpenPages application server installation.

OpenPages workflow technology automates GRC processes, enabling companies tofocus their resources on the gray areas of business where critical human decisionmaking is required. Automation can help optimize the flow of risk and complianceactivities.

Cognos Business IntelligenceIBM Cognos Business Intelligence provides executive dashboards and reportsdesigned to accelerate review and approval of governance, risk, and compliancemanagement (GRCM) information throughout the enterprise.

Business users can browse through complex information easily by clickingdashboard elements to drill down through detailed reports.

Content store databaseThe content store is a relational database that contains data, such as reportspecifications, published models, and the packages that contain them. The contentstore also contains connection information for data sources.

Chapter 1. IBM OpenPages GRC Platform components 5

Note: For the best performance if you use Oracle database server, use twoseparate databases for the content store and OpenPages database.

CommandCenterThe IBM OpenPages CommandCenter deploys the framework generator, theOpenPages security provider, creates the OpenPages data sources, and imports thestandard OpenPages report packages.


Chapter 2. Installation planning

The key to a successful installation is planning. Review the IBM OpenPages GRCPlatform supported software environments and other system requirements, such ashardware requirements, on the IBM support website ((http://www.ibm.com/support/ docview.wss?uid=swg27037756).Related concepts:“Server topology and installation configurations” on page 1Before you install OpenPages GRC Platform, plan the server topology. The numberof computers you use depends on the expected user loads.

Software prerequisitesTo ensure that your product works properly, apply all minimum requiredoperating system patches, and use only the supported versions of third-partysoftware. Review the prerequisite software before installing OpenPages GRCPlatform.

Prerequisite software for all serversBefore you install OpenPages GRC Platform, ensure that the prerequisite softwareis installed on each server in your environment.

The following tables list the third-party software that must be installed on allOpenPages servers before you start the OpenPages installation.

Table 4. Software prerequisites for all Windows computers

Requirement Specification

Operating System Windows

Web browser Internet Explorer

File compression utility For example, WinZip

PDF reader Adobe Acrobat

Table 5. Software prerequisites for all AIX or Linux computers


Operating System AIX

File compression utility For example, GNU compression utility(gtar)

Prerequisite software for the database serverIn addition to the software required for all servers, ensure that the prerequisitesoftware is installed on the database server.

Oracle database server

The Oracle database server that hosts the OpenPages database must have therequired server software installed.

7

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


v Oracle Database Server 11g Release 2 (11.2.0.1) Standard with October 2010Critical Patch Update applied

v Oracle Database Server 11g Release 2 (11.2.0.1) Enterprise Edition with October2010 Critical Patch Update and p8795792_112010_Generic.zip patch applied. Youmust contact Oracle Support and request the p8795792_112010_Generic.zippatch file.

v Oracle Real Application Clusters 11g Release 2Related concepts:“Oracle Database Server installations” on page 28IBM OpenPages GRC Platform requires a database server. Use the installationinstructions from the vendor to install the Oracle database server on the IBMOpenPages database server. After you install Oracle Database, some configurationis required.

Prerequisite software for application serversEnsure that you install the prerequisite software on all servers that host IBMOpenPages GRC Platform.

The following tables list the software requirements for application servers.

Table 6. Software prerequisites for application servers on Windows computers


Java Development Kit JDK 1.6 or greater, 64-bit is required if youdid not purchase WebLogic Server from IBM

Application server Oracle WebLogic Server (is a prerequisiteonly if you did not purchase WebLogicServer from IBM).

Application server installation location Restriction: The IBM OpenPages GRCPlatform Installer requires that applicationserver software is installed to a path with nospaces.

Database client software Oracle database client softwareImportant: Ensure that you use the sameversion of the database client software as theserver software. Apply all required patches,interim fixes, or services to both thedatabase server and the database clientsoftware

Table 7. Software prerequisites for application servers on AIX computers


Application server IBM WebSphere Application Server NetworkDeployment and required fix packs.

Application server installation location Important: The IBM OpenPages GRCPlatform requires a dedicated AIX LPAR andIBM WebSphere Application Serverenvironment. Sharing the OpenPages LPARwith other applications and IBM WebSphereApplication Server environments is notsupported.


Table 7. Software prerequisites for application servers on AIX computers (continued)


Database client software Oracle database client softwareImportant: Ensure that you use the sameversion of the database client software as theserver software. Apply all required patches,interim fixes, or services to both thedatabase server and the database clientsoftware

Prerequisite software for reporting serversEnsure that you install IBM Cognos Business Intelligence and the IBM CognosSoftware Development Kit on reporting servers.

For information about the software prerequisites for IBM Cognos BusinessIntelligence, see the IBM Cognos Intelligence Installation and Configuration Guide.

Prerequisite software for OpenPages client computersEnsure that prerequisite software is installed on all computers that access the IBMOpenPages GRC Platform application.

The following table lists the software requirements for client computers.

Table 8. Software prerequisites for client computers


Web browser Microsoft Internet Explorer

PDF reader For example, Adobe Reader

Optional: Microsoft Excel If required, for some reporting functions

Optional: Microsoft .NET Framework Required on clients where IBMCognos Officeproducts are installed

VMWare configuration requirements on Windows computersThe VMWare performance on a virtualized system is comparable to hardware. Youcan use the hardware guidelines for the database server, application server, orreporting server for sizing VM requirements.

Cloning of OpenPages application server VMs is not supported.

Each VM server computer must meet the following software requirements:v VMWare ESX Server version 4.1 or 5.0v VMWare Infrastructure Client version 4.0v Red Hat KVM 6.0v Microsoft Windows 2008 R2

Chapter 2. Installation planning 9


Chapter 3. Preparing your system for installation

Before you install OpenPages GRC Platform, some preinstallation tasks arerequired.

Procedure1. Ensure that the database server software is installed.

For more information about installing Oracle database server, see “OracleDatabase Server installations” on page 28

2. Ensure that database passwords have not expired.3. Ensure that the application server software and any required software updates

for it are installed.v For more information about installing WebLogic Server on Windows

computers, see “Installing WebLogic Server on Windows computers” onpage 18.

v For more information about installing WebSphere Application Server onAIX computers, see “Installing WebSphere Application Server on AIXcomputers” on page 20.

4. Ensure that the required users and groups exist and that they each have theappropriate permissions for installing applications.For more information about setting up users and groups for AIX operatingsystems, see “Users and user groups for installation on AIX computers” onpage 12.

5. Ensure that IBM Cognos Intelligence and the IBM Cognos SoftwareDevelopment Kit are installed.

6. For Windows installations, enable Data Execution Prevention (DEP), andensure that you have access to the Microsoft Registry Editor (regedit.exe).

7. Ensure that all required ports are available for application use.8. If the database server is separate from the OpenPages application servers,

install the database client software on application server computers.9. If the database server is separate from the Cognos Business Intelligence server,

install the database client software on reporting servers.10. Set the environment variables on OpenPages administration and managed

servers and on reporting servers.

The Super Administrator

IBM OpenPages GRC Platform uses the concept of a Super Administrator account.A Super Administrator is set up as part of the installation process and hascomplete access to all objects, folders, role templates, and groups in the OpenPagessystem.

In a new installation, the Super Administrator is the only user in the system. Youcan change the logon user name and the password or both the user name andpassword of the OpenPages Super Administrator account before, during or afterinstallation. If you use the application interface to change the user accountinformation, you must manually make corresponding changes to theCommandCenter Framework Generator property file. For more information, seethe IBM OpenPages GRC Platform Administrator's Guide.

11

Users and groups for installations on Windows operating systemsThe user account required to install and configure the OpenPages environmentmust be members of the power user or administrator groups. Users in either ofthese groups can install and configure IBM OpenPages GRC Platform.

Important: The password for this user cannot contain special characters due toconflicts with OpenPages scripts.

Users and user groups for installation on AIX computersThe users and groups must be created and configured by a user with SYSADMINprivileges and access to root.

For more information, see the Oracle documentation.

If you are installing a cluster environment, you must create these users on thecluster administrator server and on each cluster member.

Creating users and groups on the database server for AIXinstallations

For AIX installations, create and configure the oinstall, dba, and oper groups andthe oracle user on the server that hosts the Oracle database.

About this task

Use the following table to help you create the required users and user groups forthe database server.

Table 9. Required users and groups for database server

User Assign to Groups Permissions Reason

oracle oinstall; dba

oinstall is theprimary group forthis user.

Read, write, executepermission to the Oracleclient installationdirectory.

Required by Oracle databaseinstallation program.Important: The password forthis user cannot contain specialcharacters due to conflicts withOpenPages scripts

Procedure1. Log on to the database server as root.2. To create a group called oinstall, open an AIX shell and type the following

command:mkgroup -A oinstallmkgroup -A dba

This group is the primary group for the oracle user. This group is theinventory group.

Note: The Oracle database requires these names.3. Create a user called oracle, assign the initial login group (oinstall), and add

the user to the dba group.a. Go to the /usr/sbin/ directoryb. Type the following command:


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

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

5. At the New Password prompt, enter a new password.6. To limit the size of a file the user can create, configure the oracle user by

typing the following command:chuser fsize=# cpu=# data=# stack=# rss=# oracle

The following list describes the parameters:v fsize sets the largest file that a user process can create or extendv cpu sets the largest amount of system unit time (in seconds) that a user's

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

Note: To allow this user to copy the installation kit from the installation mediato a local system, use a negative number to set the limits to unlimited. Thesevalues 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 servers for AIXinstallations

To install the Oracle Client, WebSphere Application Server, and the OpenPagesapplication, you must create two users and one group. You can create a separateuser and group to install WebSphere Application Server.

About this task

To install the Oracle client, create and configure the oinstall group and the oracleuser on the server that hosts the OpenPages application.

Table 10. Required users and groups for application servers


oracle oinstall Read, write, executepermission to: the Oracleclient installationdirectory

Required by Oracle clientinstallation program.

wasuser IBM WebSphereApplication Serverinstallation

Read, write, executepermission to theWebSphere ApplicationServer installationdirectory.

You can create a non-root userto install the WebSphereApplication Server software.You can create a separate userand group or use opuser.

Chapter 3. Preparing your system for installation 13

Table 10. Required users and groups for application servers (continued)


opuser staff

security

audit

bin

cron (optional)

WebSphereApplication serverinstallation group

staff is theprimary group forthis user.

Read, write, executepermission to thefollowing directories:

v Oracle clientinstallation directory

v IBM WebSphereApplication Serverinstallation directory

v Java JDK or JREinstallation directory

v Cognos BI installationdirectory

User must be able to runSQL*Plus commands.

v staff

A standard, default groupthat most users have as theprimary group.

v cron

Optionally, add the user tothis group to allow this userto run cron jobs.

v security

Add the user to this group toallow the user to set userattributes.

v audit

Add the user to this group toallow the user to be auditedor to audit.

v bin

Add the user to this group toallow access to tools in thebin directory, such as gunzip.

Procedure1. Log on to the application server as root and open an AIX shell.2. To create a group called oinstall, enter the following command:

mkgroup -A oinstall

This group is the primary group for the oracle user.

Note: The Oracle Client installer requires that this group is named oinstall.3. To create a user called oracle and assign the user to the oinstall group, go to

the /usr/sbin/ directory and enter the following command:/usr/sbin/useradd -m -g oinstall oracle

This user is used to install Oracle client.

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

4. To limit the size of a file the user can create, configure the oracle user bytyping the following command:chuser fsize=# cpu=# data=# stack=# rss=# oracle

The following list describes the variables:v fsize sets the largest file that a user process can create or extendv cpu sets the largest amount of system unit time (in seconds) that a user's

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


Note: To allow this user to copy the installation kit from the installationmedia to a local system, use a negative number to set the limits to unlimited.These values can be changed later to better suit your environment.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

5. Use the following command to change the password for the oracle user:passwd oracle

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

useradd -m name

8. To limit the size of a file the user can create, configure the opuser user.chuser fsize=# name

Use a negative number for unlimited.9. Type the following command to add the OpenPages user to the

bin,security,, and audit Oracle groups.usermod -g staff -G bin,security,cron,audit opuser

Optionally, you can add the user to the cron group.10. Change the password for the OpenPages user by using the following

command:passwd name

11. At the New Password prompt, enter a new password.

Creating users and groups on the reporting servers for AIXinstallations

To install the Oracle client and IBM Cognos Business Intelligence create two usersand one group.

About this task

To install the Oracle client, create and configure the oinstall group and the oracleuser on the server that hosts the OpenPages application.

Use the following table to help you create the users and groups

Table 11. Required users for reporting servers


oracle oinstall Read, write, executepermission to Oracleclient installationdirectory

oinstall is required by Oracleclient installation program


Table 11. Required users for reporting servers (continued)


opuser staff

cron

security

audit

bin

staff is theprimary group forthis user.

Read, write, executepermission to thefollowing directories:

v Oracle clientinstallation directory

v WebSphereinstallation directory

v Cognos installationdirectory

v Java JDK or JREinstallation directory

v Apache Web Serverinstallation directory

User must be able torun SQL*Pluscommands.

v staff

A standard, default group towhich most users have as theprimary group..

v cron

Optionally, add the user tothis group to allow this userto run cron jobs.

v security

Add the user to this group toallow the user to set userattributes.

v audit

Add the user to this group toallow the user to be auditedor to audit.

v bin

Add the user to this group toallow access to tools in thebin directory, such as gunzip.

Procedure1. Log on to the application server as root user and open an AIX shell.2. To create a group called oinstall, enter the following command.

mkgroup -A oinstall

This group is the primary group for the oracle user.

Note: The Oracle Client installation program requires that this user is namedoracle.

3. To create a user called oracle and assign the user to the oinstall group, go tothe /usr/sbin/ directory and enter the following command.usr/sbin/useradd -m -g oinstall oracle

This user is used to install Oracle client.

Note: The Oracle Client installer requires that this user is named oracle.4. To limit the size of a file the user can create, configure the oracle user.

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

Use a negative number for unlimited.The following list describes the variables:v cpu sets the largest amount of system unit time (in seconds) that a user's

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

allocate.


Note: To allow this user to copy the installation kit from the installationmedia to a local system, use a negative number to set the limits tounlimited. These values can be changed later to better suit yourenvironment.

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

5. Use the following command to change the password for the oracle user.passwd oracle.

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

useradd -m name.

8. To limit the size of a file the user can create, configure the opuser user.chuser fsize=# name

Use a negative number for unlimited.9. Add the OpenPages user to the bin, security, and audit Oracle groups.

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

Optionally, you can add the user to the cron group.10. Use the following command to change the password for the OpenPages user.

passwd name.

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

Enabling Data Execution Prevention for essential Windows programsand services

By default, Windows Server 2008 uses settings that are designed to prevent anapplication from running unauthorized programs. However, these settings caninterfere with the IBM OpenPages GRC Platform installations. During the softwareinstallation, configure Data Execution Prevention (DEP) to allow the installers towork.

Procedure1. Log on to the server.2. Open Windows Explorer.3. Right-click Computer > Properties.4. In the System Properties window, click Advanced System Settings.5. On the Advanced tab, under the Performance heading, click Settings.6. In the Performance Options dialog box, click the Data Execution Prevention

tab, and then select Turn on DEP for essential Windows programs andservices only.

7. Click OK and then restart your system to enable the change.8. Repeat these steps for each server in the installation.

What to do next

When the installation of all software is complete, you can disable the setting.


Optional: Changing the Temp directory for AIX installationsBy default, the /tmp directory is configured as the TEMP directory. For AIXinstallations, you can change the TEMP directory by adding the following variablesto the .profile of the user who is installing the product.

Procedure1. On Oracle database and OpenPages application servers, ensure that the /tmp

directory on the database server is set to a minimum size of 4 GB.2. Log on to application server as the IBM OpenPages installation user.

The user has non-root privileges.3. 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

For example, use the following commands:export IATEMPDIR=/opt/temp

export TEMP=/opt/temp

export TMP=/opt/temp

export TMPDIR=/opt/temp

export TEMPDIR=/opt/temp

Optional: Changing the Temp directory for Windows installationsBy default, the TEMP and TMP environment variables are set to a hidden user folderlocation. The folder location is typically %USERPROFILE%\AppData\Local\Temp. Youcan change the location of the TEMP and TMP directory by changing the environmentvariables in the system properties.

Procedure1. On the database and OpenPages application servers, ensure that the /tmp

directory is set to a minimum size of 4 GB.2. Log on to application server as the IBM OpenPages administrator.3. Right-click My Computer > Properties.4. Click Advanced System Settings.5. Click Environment Variables.6. Select the TEMP variable and click Edit. TEMP and TMP might be defined as

system variables or user variables, depending on how your system is set up.7. In the Variable value box, type the new temporary folder location and click

OK.8. Repeat the steps to change the folder location for the TMP variable.

Installing WebLogic Server on Windows computersYou must have an application server installed and running before you install IBMOpenPages GRC Platform. You must install application server software where youplan to install OpenPages application software. In a Windows environment, use thecommand line to install the 32-bit version or the 64-bit version of WebLogic Server.


If you purchased Oracle WebLogic Server as part of OpenPages (the OpenPagesembedded installation program), the application server software is automaticallyinstalled during the OpenPages application.

For horizontal cluster configurations, install the software on the cluster admin andcluster member servers.

The WebLogic Server version on the non-admin server must be the same as theWebLogic version on the admin server.

Procedure1. Log on to the application server as a user with admin privileges.2. On Windows computers, start a Command Prompt window by using the Run

as Administrator option.3. Go to the directory that contains the Oracle WebLogic Server installation

media.4. Run the installation program from your WebLogic Server installation media,

by using the following command:v For 64-bit systems, run the wls1033_generic.jar file.v For 32-bit systems, run the java -jar wls1033_generic.jar file.

5. On the Welcome page, click Next to continue.6. On the Create New Middleware Home page, select a location for the

WebLogic Server middleware home directory, or use an existing homedirectory, and click Next.

7. On the Register for Security Updates page, optionally register for Oracleupdates, and click Next

8. On the Choose Installation Type page, select Custom and then click Next.9. On the Choose Products and Components page, ensure that all components

are selected, except for Server Example and click Next.10. On the JDK Selection page, select one or more Java Development Kits to

install or click Browse to locate an exiting supported JDK (Java DevelopmentKit), and click Next.

11. On the Choose a Product Installation Directory page, select a location for theWebLogic Server installation directory and click Next.

Note: Record the installation directory. This WL_HOME location is used duringthe installation procedures. The default location is c:\Oracle\Middleware\wlserver_10.3).

12. On the Install Windows Service page, select No and click Next.13. On the Installation Summary page, review your selections and when you are

satisfied, click Next.14. Click Next to begin the installation.15. After the installation finishes, clear the Run Quickstart option and click Done

to exit the installer.

Configuring WebLogic Server on a multihomed computer in aWindows environment

If the WebLogic Server uses more than one network interface card (NICs) to createmultiple network interfaces, you must modify the Windows hosts file. TheWindows host file must point to the primary NIC. Without specifying the IPaddress of each NIC, the Oracle WebLogic Server might listen on the wrong NIC.


Procedure1. Log on to the application server as a user with admin privileges.2. Open a Command Prompt window by using the Run as Administrator option.3. Go to the %SYSTEMROOT%\system32\drivers\etc\ directory, and open the hosts

file in a text editor.

Note: WebLogic Server picks up the fully qualified domain name from the firstentry in the %SYSTEMROOT%\system32\drivers\etc\hosts file.

4. On a separate line, enter the IP address and host name of the primary NIC.5. On separate lines, enter the IP address and host name of any other NICs on

that server.6. Save and then close the file.7. Restart WebLogic Server.

Installing WebSphere Application Server on AIX computersYou must have an application server installed and running before you installIBMOpenPages GRC Platform. You must install application server software whereyou plan to install OpenPages application software. In an AIX environment, youmust install WebSphere Application Server where you plan to install theOpenPages application software.

For horizontal cluster configurations, install the software on the clusteradministrator and cluster member servers.

The WebSphere Application Server version on the non-admin server must be thesame as the WebSphere Application Server version on the admin server.

Procedure1. Log on to the application server as user that has permission to create

directories.2. Open an AIX shell and then create a directory for the installation files in an

appropriate location, such as /opt/opuser/WebSphere.mkdir /opt/opuser/WebSphere

3. Change ownership of the directory to the user who runs the IBM WebSphereApplication Server installation.chown opuser /opt/opuser/WebSphere

4. If required, log out of the application server and log in as the user who runsthe installation program.

5. Open an AIX shell as a non-root user.6. Select a umask that allows the owner to read/write to the files, and allows

others to access the files according to the prevailing system policy.Depending on whether the users share the group, for non-root users, use aumask of 002 or 022. For a root user, use a umask of 022.To set the umask setting to 022, type the following command umask 022

7. Ensure that you have 755 access to all directories where you download andinstall the software.

8. Access the root directory of your installation image on your hard disk, orinsert the WebSphere Application Server installation disk into the disk drive.

9. Start the installation of a product image by using the following command:./install


10. On the Welcome page, click Next to continue.11. On the License Agreement page, select I accept both the IBM and the

non-IBM terms to agree to the license agreement and click Next to continue.12. On the Systems Prerequisite Check page, confirm that your operating system

is supported and that you installed all required patches, and then click Next.v If the wizard detects a previous installation, the Product-Detection page is

displayed.v If the wizard does not detect a previous installation, go to the next step.

13. If the Product-Detection panel displays, select the following actions:v Select Add features to the existing installation, click Next.v Select Install a new copy of the product to another directory, and click

Next.v Select Create a new WebSphere profile using the Profile management

tool, and click Next.v Select Upgrade the product to another edition and click Next.

14. On the Optional Features Installation page, use the following table to selectthe features to install and then click Next.

Table 12. Optional installation features

Feature to install Description Required?

Install the sampleapplications

Installs the samples applications forlearning and demonstration environments.The samples are not required forinstallation on production environments.

Not required

Install non-Englishlanguage packages for theadministrative console

Installs all the non-English language filesfor using the administrative console fromcomputers with non-English locales. If youdo not select this option, only the Englishlanguage pack is installed.

Optional

Install non-Englishlanguage packages for theapplication server runtimeenvironment

Installs all the non-English language filesthat support the application server runtimeenvironment such as the administration tooland logging. If you do not select thisoption, only the English language pack isinstalled.

Optional

15. On the Installation Directory page, specify the installation root directory,record the location, and then click Next.

Important: Do not use spaces in the name of the installation directory.16. On the WebSphere Application Server Environments page, select None and

then click Next.When prompted by a message that confirms whether you want to proceedwithout creating a profile displays, click Yes. The installation program createsa profile for the WebSphere Application Server.

17. On the Repository for Centralized Installation Managers page, select thefollowing settings.a. Select Create a repository for Centralized Installation Managers.b. Select the Populate the repository with this installation package.c. Specify the location for the repository or accept the default setting.d. Click Next.


18. On the Installation Summary page, review your selections and click Verifymy permissions to perform this installation and if successful, click Next tobegin the installation.

19. In the Installation Results page, verify that the installation is successful.To verify that there were no file system or other errors, you can check theapp_server_root/logs/install/log.txt installation log file

20. Click Finish to close the installation wizard.

Installing the WebSphere Application Server fix packs on AIXcomputers

For AIX installations, IBM OpenPages GRC Platform requires WebSphereApplication Server fix packs.

About this task

You must obtain and install the required fix pack for WebSphere ApplicationServer. Review the IBM OpenPages GRC Platform supported softwareenvironments and other system requirements on the IBM support website(http://www.ibm.com/support/docview.wss?uid=swg27037756), for moreinformation about supported software requirements.

Note: The admin user that runs the update installation program must be able torun the slibclean command. Otherwise, a root user must run the slibclean beforeinstalling the fix pack.

Procedure1. On each server where WebSphere Application Server is installed, log on as the

same user who installed the original software.2. Stop the WebSphere Application Server processes and any related processes by

using the following command:stopServer

3. Open an AIX shell as a root user, then create a directory for the installationfiles in an appropriate location.mkdir /opt/opuser/WebSphere/WebSphere_Update

4. Download the required WebSphere Application Update Installer package forAIX from the IBM website into the new directory.

5. Extract the Update Installer package file.6. Open an AIX shell as opuser user or another non-root user.7. Go to the /opt/opuser/WebSphere/WebSphere_Update/UpdateInstaller

directory.8. Run the Update Installer by using the following command:

./install

9. Go to the installation root directory specified during the new installation./opt/IBM/WebSphere/WebSphere_Update/UpdateInstaller

10. Run the Update Installer by using the following command:./update.sh




Removing root user installation files for WebSphereApplication Server

For AIX installations, if a root user installed WebSphere Application Server, youmust remove some installation files and directories. Otherwise, these files mightinterfere with the OpenPages installation.

Procedure1. Log on to the application server where WebSphere Application Server is

installed.2. Go to the home directory of the root user who installed WebSphere Application

Server.3. If present, remove the following files and directories:

v .com.registry

v .InstallAnywhere

v InstallShield

v .InstallShield

4. Go to the /usr/lib/objrepos directory.5. Rename the vpd.properties file to vpd.properties.old.

Multicasting in the OpenPages environmentThe Fujitsu Interstage BPM software that is installed by IBM OpenPages GRCPlatform requires a multicast IP address. Fujitsu Interstage BPM uses the multicastIP address to communicate with itself and with other components in theOpenPages environment.

In a clustered OpenPages environment with multiple Fujitsu Interstage BPMinstances, Fujitsu Interstage BPM requires the multicast IP address to communicatewith each instance.

In a single OpenPages environment with a single Fujitsu Interstage BPM instance,Fujitsu Interstage BPM requires the multicast IP address to communicate with itself

There are multiple Fujitsu Interstage BPM servers in a single environment and themulticast IP is used for JMS synchronization in the workflow.

You must obtain a multicast address before installing the OpenPages application.v The multicast IP address must be unique within the network address space.v When installing on a secondary server in a horizontal environment, use the

same multicast IP address on all servers.

Port assignmentsBoth dedicated ports and ports that are dynamically assigned for each installationare used for IBM OpenPages GRC Platform deployments. These default ports canbe changed after installation.

You can change some port settings during the installation. You can also change thedefault port settings after installation. For information about changing the portsafter installation, see the IBM OpenPages GRC Platform Administrator's Guide.


Fixed ports

The following table lists the fixed default ports.

Table 13. Fixed ports used by Windows and AIX operating systems

Description Windows Port AIX Port

Oracle database server console application port 1158 1158

OpenPages database instance 1522 1521

OpenPages admin server 7001 9060

OpenPages admin server (SSL) 7002 9043

Workflow admin server 49901 9061

Workflow admin server (SSL) 49902 9044

OpenPages application server 7009 10108

OpenPages application server (SSL) 7010 10111

Workflow application server 49951 20108

Workflow application server (SSL) 49952 20111

Cognos Business Intelligence gateway 80 80

Framework Generator port 8080 8080

Cognos Business Intelligence dispatcher URI 9300 9300

On Windows computers, additional OpenPages installations increment by two. Forexample, the HTTP ports are 7009, 7011, 7013. The HTTPS ports are 7002, 7004,7006.

On Windows, additional workflow installations also increment by two.

For AIX computers, IBM WebSphere Application Server requires a range of 20ports for plug-ins and listeners. This default value is the starting port of that range.

Files containing port numbers

The following tables list property files on the OpenPages admin server that containport numbers.

Table 14. Files on Windows servers that contain default port numbers

File Port Parameter Name

OP_HOME\aurora\conf\server.config.props

OpenPages admin serverport

OpenPages admin serverSSL port

WC_adminhost

WC_adminhost_secure

OP_HOME\temp\aurora\conf\OPSERVER_STATUS.txt¹

OpenPages applicationport

OpenPages application SSLport

WC_defaulthost

WC_defaulthost_secure

OP_HOME\aurora\conf\server_name-InterstageBPMCS#-server.properties.config.props

Workflow admin serverport

url.path.workflow.admin


Table 14. Files on Windows servers that contain default port numbers (continued)


OP_HOME\NETWORK\ADMIN\tnsnames.ora

OpenPages databaseinstance port

OP_HOME\aurora\conf\aurora.properties

Framework Generator port

CommandCenter port

cognos.framework

cognos.server

OP_HOME\aurora\conf\aurora.properties

Framework Generator port

CommandCenter port

Cognos Dispatcher URI

cognos.computation.server

Table 15. Files on AIX computers that contain default port numbers


OP_HOME/temp/wasconfig/OpenPagesCell.dmgr.config.props

OpenPages admin serverport

OpenPages admin serverSSL port

WC_adminhost

WC_adminhost_secure

OP_HOME/temp/wasconfig/OpenPagesCell.server_name-OPNode#Server#.config.props

OpenPages applicationSSL port


OP_HOME/temp/wasconfig/IBPMCell.dmgr.config.props

Workflow admin serverport

Workflow admin serverSSL port

WC_adminhost

WC_adminhost_secure

OP_HOME/temp/wasconfig/IBPMCell.server_name-OPNode#Server.config.props

Workflow applicationport

Workflow applicationSSL port

WC_defaulthost


ORACLE_HOME/NETWORK/ADMIN/tnsnames.ora

Oracle database instanceport

OP_HOME/aurora/conf/aurora.properties

Framework Generatorport

CommandCenter port

Cognos Dispatcher URI

cognos.framework

cognos.server

cognos.computation.server

Dynamically assigned ports

Port numbers for OpenPages servers that are not listed, such as OpenPagesmanaged servers, are assigned dynamically during the installation.

OpenPages application and workflow managed server port numbers start at thefollowing values and increment by 1 for each additional managed server in theinstallation:v OpenPages application managed servers: In an OracleWebLogic Server

environment, 7009 (7010 for SSL). In an IBMWebSphere, 9080.


v OpenPages workflow managed servers: 49951 for both WebLogic Server andWebSphere environments.

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

On Windows computers, OP_HOME\aurora\conf\OPSERVER_STATUS.txt

On AIX computers, 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 portinformation is found in:v OpenPagesCell.dmgr.config.props

v OpenPagesCell.server_name-OPNode#;Server#;.config.props

v IBPMCell.dmgr.config.props

v IBPMCell.server_name-IBPMNode#Server.config.props

On a cluster system, the OpenPagesCell.server_name-OPNode1Server1.config.propsfile and IBPMCell.server_name-IBPMNode1Server.config.props file contain portinformation for that managed server only. If there is a second managed serverwithin the same computer (vertical cluster), the port information is displayed inOpenPagesCell.server_name-OPNode1Server2.config.props andIBPMCell.server_name-IBPMNode2Server.config.props.

In a horizontal cluster, the numbering for the managed servers in the .props filerestarts at 1 for each cluster member computer.


Chapter 4. Oracle Database Server software installations

Install and configure the Oracle database software to use with IBM OpenPagesGRC Platform.

Use the installation instructions from the vendor to install Oracle Server software.After installation, create an Oracle database instance, add a database listener, andinstall an Oracle Client.

Removing environment variablesYou must remove or unset any Oracle database system environment variablesbefore installing the Oracle Database Server software.

Procedure1. If required, remove or unset the following environment variables.

v ORACLE_BASEv ORACLE_HOMEv PERL5LIBv TNS_ADMIN

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

Prerequisite setup for AIX computersIf you are installing the database server software into an AIX environment, ensurethat your system and environment meet additional prerequisites.

For example, you must create installation users and groups and ensure thatoperating system file sets for Oracle database software exist.Related concepts:“Users and user groups for installation on AIX computers” on page 12The users and groups must be created and configured by a user with SYSADMINprivileges and access to root.

AIX operating system file sets for Oracle database softwareOn AIX computers, Oracle database requires some file sets.

As required for Oracle database server software, ensure that the followingoperating system files sets are installed and committed:v bos.adt.base

v bos.adt.lib

v bos.adt.libm

v bos.perf.perfstat

v bos.perf.libperfstat

v bos.perf.protocols

v rsct.basic.rte

v rsct.compat.clients.rte

27

v xIC.aix61.rte

In an AIX shell, type the following command:

lslpp -l <fileset>

If successful, a message similar to the following is displayed:

<fileset> COMMITTED

Oracle Database Server installationsIBM OpenPages GRC Platform requires a database server. Use the installationinstructions from the vendor to install the Oracle database server on the IBMOpenPages database server. After you install Oracle Database, some configurationis required.

Restriction: Do not install Oracle database server or Oracle client software into adirectory that contains spaces.

Important: The password for database users (such as SYSTEM, SYS, DBSNMP,SYSMAN) cannot contain special characters due to database requirements andconflicts with OpenPages scripts.

In addition, the name of the database server cannot contain underscores. Issueswith connectivity between the Oracle Enterprise Manager and the Oracle WebLogicServer can occur if the name has underscores

After installing the Oracle Database server, you must install an Oracle Client on allapplication server computers.

Oracle package dependenciesTo function correctly, the OpenPages Oracle packages must have access to thestandard Oracle objects.

If objects are deleted, or access to an object is removed from the PUBLIC group,the OpenPages application user must be granted explicit permissions to them.Also, you must create private synonyms within the OpenPages Database Schema.

Each package object requires the EXECUTE permission. All other objects requirethe SELECT permission.

The following table lists the standard Oracle objects that include the base object,the object name, and the public synonym for Oracle database objects.

Table 16. Base objects for the package object type

Base Object Object Name Public Synonym

SYS.DBMS_RANDOM DBMS_RANDOM PUBLIC.DBMS_RANDOM

SYS.DBMS_SQL DBMS_SQL PUBLIC.DBMS_SQL

SYS.DBMS_JOB DBMS_JOB PUBLIC.DBMS_JOB

SYS.DBMS_OUTPUT DBMS_OUTPUT PUBLIC.DBMS_OUTPUT


Table 16. Base objects for the package object type (continued)


SYS.DBMS_SESSION DBMS_SESSION PUBLIC.DBMS_SESSION

SYS.DBMS_UTILITY DBMS_UTILITY PUBLIC.DBMS_UTILITY

SYS.DBMS_SNAPSHOT DBMS_MVIEW PUBLIC.DBMS_MVIEW

SYS.DBMS_STATS DBMS_STATS PUBLIC.DBMS_STATS

SYS.STANDARD N/A N/A

SYS.DBMS_STANDARD N/A PUBLIC.ODCICONST

SYS.ODCICONST ODCICONST N/A

SYS.PLITBLM N/A PUBLIC.DUAL

Table 17. Base objects for the view object type


SYS.ALL.PROCEDURES ALL_PROCEDURES PUBLIC.ALL_PROCEDURES

SYS.ALL_TAB_PRIVS ALL_TAB_PRIVS PUBLIC.ALL_TAB_PRIVS

SYS.NLS_SESSION_

PARAMETERS

NLS_SESSION_PARAMETERS

PUBLIC.NLS_SESSION_PARAMETERS

SYS.PRODUCT_COMPONENT_

VERSION

PRODUCT_COMPONENT_VERSION

PUBLIC.PRODUCT_COMPONENT_VERSION

SYS.USER_CONS_COLUMNS

USER_CONS_COLUMNS PUBLIC.USER_CONS_COLUMNS

SYS.USER_CONSTRAINTS

USER_CONSTRAINTS PUBLIC.USER_CONSTRAINTS

SYS.USER_DB_LINKS USER_DB_LINKS PUBLIC.USER_DB_LINKS

SYS.USER_IND_COLUMNS

USER_IND_COLUMNS PUBLIC.USER_IND_COLUMNS

SYS.USER_INDEXES USER_INDEXES PUBLIC.USER_INDEXES

SYS.USER_OBJECTS USER_OBJECTS PUBLIC.USER_OBJECTS

SYS.USER_SEGMENTS USER_SEGMENTS PUBLIC.USER_SEGMENTS

SYS.USER_SEQUENCES USER_SEQUENCES PUBLIC.USER_SEQUENCES

SYS.USER_SOURCE USER_SOURCE PUBLIC.USER_SOURCE

SYS.USER_TAB_COLS USER_TAB_COLS PUBLIC.USER_TAB_COLS

Chapter 4. Oracle Database Server software installations 29

Table 17. Base objects for the view object type (continued)


SYS.USER_TAB_COLUMNS

USER_TAB_COLUMNS PUBLIC.USER_TAB_COLUMNS

SYS.USER_TABLES USER_TABLES PUBLIC.USER_TABLES

SYS.USER_TABLESPACES

USER_TABLESPACES PUBLIC.USER_TABLESPACES

SYS.USER_TRIGGERS USER_TRIGGERS PUBLIC.USER_TRIGGERS

Adding an Oracle listener for the OpenPages databaseYou must manually add an Oracle database listener for the OpenPages database.

Procedure1. Log on to your database server as a user with administrative privileges.2. Start the Net Configuration Assistant by using one of the following methods:

Table 18. Methods to start Net Configuration Assistant

If you purchasedOracle from... Then...

IBM 1. For Windows installations, open a Command Promptwindow, or for AIX, installations, start a shell.

2. Go to one of the following folders:

v On Windows computers, openpages_data\repository\server112_x64\software\bin

v On AIX computers,/opt/openpages_data/repository/server112_x64/software/bin

3. To start the Net Configuration Assistant, type the followingcommand: netca

Vendor other than IBM 1. For Windows installations, open a Command Promptwindow, or for AIX, installations, start a shell.


v On Windows computers, Oracle_Home\bin

v On AIX computers, Oracle_Home/bin

To start the Net Configuration Assistant, type the followingcommand: netca

3. On the Welcome page, select the Listener configuration option and clickNext.

4. On the Listener Configuration, Listener page, select Add and click Next.5. On the Listener Configuration, Listener Name page, type a name for the new

listener and click Next.Each listener name must be unique in the current Oracle Home.

6. On the Listener Configuration, Select Protocols page, select TCP for theprotocol and click Next.

7. On the TCP/IP Protocol page, choose a port and click Next.


v If this instance is the only Oracle database instance installed on yourcomputer, select the Use standard port number of 1521 option.

v If you have other instances of Oracle installed, choose another port number.This port number cannot be used by any other services that are running onyour computer.

8. On the More Listeners page, select No and click Next.9. On the Listener Configuration Select Listener page, select the listener you

created and click Next to start the listener service.10. On the Listener Configuration Done page, click Next to return to the

Welcome page.11. On the Welcome page, click Finish.

Creating a database instance for the OpenPages repositoryAfter installing the Oracle software, you must create a database instance forOpenPages to use.

Procedure1. Log on to your database server as a user with administrative privileges.2. Start the Database Configuration Assistant by using one of the following

methods:

Table 19. Methods to start Database Configuration Assistant

If you purchased Oraclefrom... Then...

IBM 1. As a user with Administrative privileges, on Windowscomputers, open a Command Prompt window or on AIXcomputers, open a shell.


v On Windows computers, openpages_data\repository\server112_se_x64\software\BIN

v On AIX computers /opt/oracle/openpages_data/repository/server112_se_x64/software/bin

3. To start the Database Configuration Assistant, type thefollowing command: dbca.

a vendor other than IBM 1. As a user with Administrative privileges, on Windowscomputers, open a Command Prompt window or on AIXcomputers, open a shell.



v On AIX computers Oracle_Home/bin

3. To start the Database Configuration Assistant, type thefollowing command: dbca.

3. On the Welcome page, click Next to begin the database configuration.4. On the Operations page, select Create a Database and then click Next.5. On the Database Templates page, select Custom Database and click Next

6. On the Database Identification page type the Global Database Identifier andclick Next

7. On the Management Options page, select Configure Enterprise Manager.a. Select Configure Database Control for local management.


b. If required, enable E-mail Notifications and Daily Backups and clickNext.

8. On the Database Credentials page, set the passwords for the default Oracleaccounts and click Next.

9. On the Database File Locations page, select the following options:a. Select File System for the Storage Type.b. Select the location for the database files.

v If you want to use the same drive that the Oracle Home directory islocated, select Use Database File Locations from Template

v If you want to place the files on a different drive or in another location,Use Common Location for All Database Files, and then type thedesired location for the database files

c. Optionally, click File Location Variables to show the current settings forthe database template you chose, and click OK.

d. Click Next.10. On the Recovery Configuration page, clear all options and click Next.11. On the Database Content page, clear all check boxes except Enterprise

Manager Repository.a. Click Standard Database Components.b. Clear all options.

Note: An Oracle message displays when you clear the Oracle DB XMLcomponent. You can click YES and ignore this message. The Oraclecomponents affected by clearing this option are not used by theOpenPages environment.

c. Click OK to close the dialog.d. Click Next.

12. On the Initialization Parameters page, change the settings.a. On the Memory tab, click Custom and then set the following options:

v Memory Management to Automatic Shared Memory Management.

v SGA Size field to 1024.v PGA Size field to 768.

b. On the Sizing tab, set the following options:v Block Size to 8192.v Processes to 250.

c. On the Character Sets tab, select Use Unicode (AL32UTF8) and set theNational Character Set option to AL16UTF16 - Unicode UTF-16 Universalcharacter set

Note: You must create your database with the AL32UTF8 character set.d. On the Connection Mode tab, select Dedicated Server Mode.

13. Click All Initialization Parameters > Show Advanced Parameters.a. Enter the following custom settings:

Table 20. Initialization parameter values for Oracle database instance

Parameter Name Value Default

compatible 11.2.0.0


Table 20. Initialization parameter values for Oracle database instance (continued)

Parameter Name Value Default

nls_length_semantics CHARNote: CHAR is required forglobalization.

BYTE

open_cursors 300

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

b. Click Close and click Next.14. On the Database Storage page, if required, modify the database storage

parameters and click Next.15. On the Creation Options page, select Create Database and click Finish.16. On the Configuration page, review the settings and click Finish to begin the

database creation process and then click OK.

Adding a local net service name for the OpenPages databaseIf you did not purchase Oracle database software from IBM OpenPages, you mustadd a net service name on all servers that run the OpenPages application. Thedatabase client uses the net service name to connect to the database.

Procedure1. To start the Net Configuration Assistant, do one of the following steps:

Table 21. Methods to start Net Configuration Assistant

If you purchasedOracle from... Then...

IBM 1. On Windows computers, open a Command Prompt window,or on AIX computers, start a shell.


v On Windows computers, OpenPages_data\repository\server112_x64\software\bin

v On AIX computers, /opt/OpenPages_data/repository/server112_x64/software/bin

3. To start the Net Configuration Assistant, type the followingcommand: netca.

a vendor other thanIBM

1. On Windows computers, open a Command Prompt window,or on AIX computers, start a shell.



v On AIX computers, Oracle_Home/bin

To start the Net Configuration Assistant, type the followingcommand: netca.


2. On the Welcome page, select Local Net Service Name configuration and clickNext.

3. On the Net Service Name Configuration page, select Add and click Next.4. On the Service Name page, type the global database name for the Oracle

instance and click Next

For example, use OP for the service name.5. On the Select Protocols page, choose the TCP protocol and click Next.6. On the TCP/IP Protocol page, type the name of the server in for the Host

Name field, use the standard port number, and then click Next.If you changed the port number when you created the listener for thedatabase instance, type the new value instead.

7. On the Test page, select Yes, perform a test to confirm the connection.The test fails if you changed the password for the SYSTEM user during thedatabase creation procedure. In this case, click Change Login after the testfailure. Overwrite the SYSTEM password with the value you entered duringthe database creation procedure (Oracle Server installation), click OK, andthen click Next.

8. On the Net Service Name page, modify default Net Service Name if necessaryand click Next.By default, the value matches the Service Name you entered at the beginningof the procedure.

9. On the Another Net Service Name? page, select No and click Next.10. On the Net Service Name Configuration Done page, click Next to return to

the Welcome page.11. Click Finish to exit the Net Configuration Assistant.

Scripts to manually create the OpenPages database schema in Oraclebefore installation

To create the OpenPages schema before you install, use the SQL wrapper scriptsthat are included in the media kit.

The IBM OpenPages GRC Platform requires that you create an OpenPagesdatabase schema, a set of database users, and a tablespace. During the OpenPagesGRC Platform installation, you can choose to automatically create the schema.Optionally, you can manually create the OpenPages database schema before youinstall OpenPages application servers.

Scripts used to create the database schema

To create the OpenPages application tablespace and users, run a SQL wrapperscript. The SQL wrapper script calls other scripts.

sql-wrapper.sqlThe script runs other required SQL scripts in the correct order. Use thisscript to manually install the database.

database-install.sqlThe wrapper script contains default definition values that you can modify.Change settings in the script file and not the command-line interface.Default values include the OpenPages administrator user account, basecurrency denomination, and the location of the OpenPages storage folder.


The base currency must match the base currency that is set in any previousinstallations. You cannot change the base currency after installation.

op-app-global-env.sqlThe script is called by the wrapper script and defines the SuperAdministrator user account. You must verify the user account values inthis script.

Creating the tablespace and users for the OpenPagesdatabase before installation

You can manually create the OpenPages database schema before you install IBMOpenPages GRC Platform by running scripts. You must modify some of the scriptsbefore you run the scripts use them.

Before you begin

Ensure that you have the following information available.v Workflow user namev Workflow user passwordv TNS name aliasv System user namev System user passwordv OpenPages super administrator user namev OpenPages super administrator password

Ensure that the passwords have not expired.

Procedure1. Log on to a system as a user with administrator privileges.

Tip: You can use any system that has access to SQL*Plus and that can connectto the database server.

2. Start a Command Prompt window by using the Run as Administrator option,or on an AIX computer, open a shell as a user with administrative privileges.For AIX installations, use the opuser user that you created for the OpenPagesinstallation.

3. Copy the OP_version_Configuration directory from the Installer DVD ornetwork share location to the local system.

4. Go to the OP_version_Configuration\Database\ORACLE directory and copy theINSTALL_SCRIPTS directory to the local system.For an AIX computer, ensure that you have full rights to the local installationdirectory and to the files in the directory.

5. Go to the INSTALL SCRIPTS directory on the local system and open thecreate-opx-tablespaces.sql script in a text editor.a. As appropriate for your environment, modify the SQL script under --

permanent storage, protected by logging, -- dedicated temporarytablespace and --temporary storage, no logging protection:CREATE TABLESPACE iflowdb DATAFILE ’&dbf_location/&tablespace_name.dbf’

SIZE 25M REUSE AUTOEXTEND ON NEXT 25M MAXSIZEUNLIMITED ONLINE EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K’;

b. Save and close the file.6. Open the ibpm-ts-and-schema-owner.sql script in a text editor.


a. Use the following syntax to modify the SQL script under ReCreate thetablespace and RECREATE THE USER:CREATE TABLESPACE iflowdb DATAFILE ’&dbf_location/&tablespace_name.dbf’


b. Save and close the file.

For example, the following SQL Syntax creates a tablespace with a data filecalled OPdatafile in the Oracle data home location. The tablespace is managedlocally.CREATE TABLESPACE iflowdb DATAFILE ’&&10/OPdatafile.dbf’


Where &&10 uses the datafile_storage_location parameter that you entered inthe database-install.sql command for the data file location. OPdatafile.dbfis the name of the data file.The following SQL syntax creates a temporary tablespace with a data file indisk_group_1. The tablespace is managed locally.CREATE TEMPORARY TABLESPACE OPDATA_TEMP TEMPFILE ’+disk_group_1’ SIZE 2GEXTENT MANAGEMENT LOCAL;

7. To verify the default definition values, open the sql-wrapper.sql wrapperscript in a text editor and modify the values as required for the followingdefinitions.For a Microsoft Windows operating system:v define opx_base_currency_iso_code=’USD’

v define opx_dflt_stor_srv_root=’C:\openpages-storage’

For an AIX operating system.v define opx_base_currency_iso_code=’USD’

v define opx_dflt_stor_srv_root=’/opt/openpages-storage’

Do not change the define opx_op_admin_name or define opx_op_admin_pwddefinitions.

For example, by default, the base currency is set to USD. If you use Euros asyour base currency, change the default ISO currency code from USD to EUR.define opx_base_currency_iso_code=’EUR’

8. From the INSTALL_SCRIPTS directory, open the custom environment scriptop-app-global-env.sql in a text editor.a. Modify the following default values for the Super Administrator.

v define super_admin_username=’OpenPagesAdministrator’

v define super_admin_password=’OpenPagesAdministrator’

b. Save and close the file.9. Use the following syntax to run the database-install.sql wrapper script that

creates the database components:sqlplus /nolog @sql-wrapper.sql database-install.sql log_fileoracle_tns_alias dba_user dba_password workflow_userworkflow_password op_user op_passworddatafile_storage_location

The following table provides a list of parameters that are passed to the SQLwrapper script.


Table 22. Examples of SQL wrapper script parameters and descriptions

Parameter Name Description Example

log_file The log file name that the scriptcreates and writes information to.

logfile.txt

oracle_tns_alias The database alias for theOpenPages database instance, asset during the Oracle databaseinstallation. If necessary, you canretrieve this alias from thetnsnames.ora file.

OP

dba_user The Oracle system user name.

If you do not have access to thesystem user account, then use adatabase user account withadministrative privileges.

system

dba_password The password for the Oraclesystem account.

openpages

workflow_user The workflow database username.

OpenPages uses this account tocreate and access the workflowdatabase, and to manageworkflow-related transactions.

opworkflow

workflow_password The password for the workflowdatabase user account.

opworkflow

op_user The user name that is used byOpenPages to create and accessthe OpenPages database instance

openpages

op_password The password for the OpenPagesdatabase user account.

openpages

datafile_storage_location The location of the Oracle datadirectory on the database server.The location of this directory isset during the Oracle installationprocess.

If the database server isrunning MicrosoftWindows

v C:\oracle\ora112\oradata\OP

v C:\openpages_data\repository\database112_se_x64\oradata\OP

If the database server isrunning AIX

v /opt/oracle/ora112/oradata/OP

v opt/openpages_data/repository/database112_se_x64/oradata/OP

The following sample code shows the SQL*Plus command line with examplevalues from the table from the preceding step as the variables.


Table 23. Example code for Microsoft Windows and AIX operating systems

Operatingsystem Code

Windows sqlplus /nolog @sql-wrapper.sql database-install.sql logfile.txt OPsystem openpages opworkflow opworkflow openpages openpagesC:\oracle\ora112\oradata\OPC:\openpages_data\repository\

database112_se_x64\oradata\OP

AIX sqlplus /nolog @sql-wrapper.sql database-install.sql logfile.txt OPsystem openpages opworkflow opworkflow openpages openpages/opt/oracle/ora112/oradata/OP/opt/openpages_data/repository/

database112_se_x64/oradata/OP

After the SQL script finishes, the OpenPages database schema is created. A logfile is created in the directory where you ran the SQL script. The name of thelog file matches the value of the log_file parameter you entered.

Results

If you have problems when you run the database-install.sql script, you can usethe OP_version_Configuration\Database\ORACLE\INSTALL_SCRIPTS\init-db-cleanup.sql script. The init-db-cleanup.sql removes the database componentsthat were added. Then, you can run the database-install.sql script in a cleandatabase environment.

Examplesqlplus /nolog @sql-wrapper.sql init-db-cleanup.sql log_fileoracle_tns_alias dba_user dba_password workflow_user op_user

Testing the connections to the database server and the OpenPagesrepository

Test whether the SQL*Net connect string can connect to the database listener byusing the TNSPING utility in the ORACLE HOME/bin directory. The TNSPING utilitytests if the listener is available. It does not test whether the databases behind thelistener are working.

To test that the OpenPages repository is created, use SQL*Plus to log on to theOpenPages Oracle database schema.

Procedure1. To test whether you can log on to Oracle Enterprise Manager Database Control,

the web-based interface that is used to administer an Oracle database, type thefollowing command:https://oracle_server_name:port/em

In a default installation, the port number is 1158.2. To test whether a SQL*Net connect string can connect to the listener, type the

following command:tnsping database_instance_name

The utility requests acknowledgement that the service name is valid and thatthe listener is configured to handle requests for that service name.If the configuration is correct, a message is displayed that shows the returntime.


If the configuration is not correct, the utility returns an error message. Ensurethat you use the correct service name and that the listener is started on theserver computer.

3. To test that OpenPages repository is created, type the following command:sqlplus username/password@service_name

For example, sqlplus system/openpages@op

The system connects you to an Oracle Database instance.4. To exit SQL*Plus, type exit.



Chapter 5. Cognos Business Intelligence installations

IBM Cognos Business Intelligence is installed on the same server as the OpenPagesCommandCenter. This server is referred to as the reporting server.

Reporting server distribution options

For light user loads, with fewer than 50 concurrent users, Cognos BI andCommandCenter can be installed on the same server as the OpenPages application.

For heavier user loads, install Cognos BI and CommandCenter on separate fromOpenPages application servers. IBM OpenPages GRC Platform operates at peakperformance when components are installed on multiple servers: a database server,an application server, and a reporting server.

DB2 database server requirements

Two separate DB2 database instances are required for the IBM OpenPages GRCPlatform installation. The DB2 database instance that hosts the Cognos contentstore must not be the same DB2 database instance that hosts the OpenPagesdatabase. Each DB2 database instance has different requirements.

Installing IBM Cognos Business IntelligenceBefore you install OpenPages GRC Platform components, ensure that IBM CognosBusiness Intelligence and the IBM Cognos Software Development Kit are installedand running in your environment.

Restriction: Do not install Cognos BI into a directory that contains spaces.

For more information about upgrading to IBM Cognos BI, see the IBM CognosBusiness Intelligence Installation and Configuration Guide.

Important: In the 64-bit installations, the report server component in Cognos BI isprovided in both 32-bit and 64-bit versions. Selecting which version you use isdone in IBM Cognos Configuration after installation. By default, the report servercomponent is set to use the 32-bit mode, even on a 64-bit computer. With the 32-bitmode, you run reports from all packages. If you configure the 64-bit mode, youcan run only reports that are created from packages that use dynamic query mode.For OpenPages applications, you must use the default 32-bit report server.

Note: The IBM Cognos Business Intelligence Installation and Configuration Guide isavailable in the IBM Cognos documentation library

Before you begin

If the OpenPages database is remote from the Cognos BI server, ensure that thedatabase client software is installed on the Cognos BI server. The database clientthat Cognos BI uses to connect to the OpenPages database must be a 32-bit client.

Restriction: Do not install the database client software into a directory withspaces.

41


Procedure1. Ensure that a web server, such as Microsoft IIS or IBM HTTP Server is

installed.A web server is required so that users can view content in the IBM Cognos BIportal.

2. On the reporting server, install the new version of Cognos Business Intelligence,IBM Cognos Software Development Kit, and optionally Framework Manager.a. Install Cognos BI Server.

Restriction: In the installation wizard, accept the default components thatare selected. Do not select Cognos Content Database. Install Cognos BI intoa directory that contains only ASCII characters in the path name.After the installation is complete, ensure that the IBM Cognos Configurationcheck box is clear. Before you configure Cognos BI Server, you must doother tasks to set up your environment.For information about installing Cognos BI Server on Windows operatingsystems, see Installing server components on Windows operating systems inthe IBM Cognos BI Information Center.For information about installing Cognos BI Server on AIX operatingsystems, see Installing server components on UNIX or Linux operatingsystems in the IBM Cognos BI Information Center.

b. Install Cognos Software Development Kit in the same installation locationas Cognos BI Server.In the installation wizard, accept the default components that are selected.For more information about installing IBM Cognos Software DevelopmentKit on Windows-based computers, see Installing and configuring theSoftware Development Kit in the IBM Cognos BI Information Center.

c. Optional: Install Framework Manager.Framework Manager is not required in production environments.Framework Manager is the modeling tool for creating and managingbusiness-related metadata.

Restriction: If you need Framework Manager in your developmentenvironment, you must install the 64-bit Cognos BI server and the 32-bitFramework Manager to different directories. The default installationlocations for 32 and 64-bit Cognos components are different. For moreinformation about installing Framework Manager, see Installing FrameworkManager in the IBM Cognos BI Information Center.

3. Copy the JDBC database driver, ojdbc5.jar, file to the c10_location\webapps\p2pd\Web-Inf\lib directory.

4. Append the Cognos_HOME/bin64 directory to the library path environmentvariable.export LIBPATH=$LIBPATH:/opt/ibm/cognos/c10_64/bin64

5. Append the Cognos_HOME/bin64 directory to the PATH environment variable.


http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc%2Ft_instsrvrwin.html&path%3D0_13_6_1_1

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc%2Ft_instsrvrunix.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc%2Ft_instsrvrunix.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.ig_crn_sdkcd.10.2.0.doc%2Ft_installingandconfiguringthesdk.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.ig_crn_sdkcd.10.2.0.doc%2Ft_installingandconfiguringthesdk.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.qrc_inst.10.2.0.doc%2Ft_qrc_inst_fm.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.qrc_inst.10.2.0.doc%2Ft_qrc_inst_fm.html

Related tasks:“Manually creating the reporting tablespace and user for Oracle databases” onpage 73After you create the Cognos content store, you can manually create the contentstore user and the content store tablespace. This user must be able to create, alter,and drop tables, triggers, views, procedures, and sequences, and have theCONNECT and RESOURCE roles.

Web server configuration options for Cognos BIYou must configure your Web server before users can connect to the IBM CognosBI portal.

For more information, see the Configuring a web server in the IBM CognosBusiness Intelligence Information Center, which contains details on the following:v Enable the 64-bit web gateway

If you want to use the 64-bit version of the IBM Cognos BI gateway, you mustmanually move the 64-bit gateway files in your installation directory.

v Use compiled gateways for production systemsFor production systems, you can improve performance by changing the gatewayfrom the default CGI gateway.

v Use CGI gatewaysYou can use the CGI gateway on IBM HTTP Server, Apache Web Server, orMicrosoft Internet Information Services (IIS) Server.

v Configuring WebDAV to view and browse imagesTo view and browse images in the Report Studio, configure Web DistributedAuthoring and Versioning (WebDAV) on your web server. Report authors canbrowse for images to include in reports in a way that is similar to browsing afile system.

Configuring IIS 7.0 Web ServerBefore you can view reporting data on Windows computers, you must configure aweb server. If your web server is a Windows Server 2008 with IIS 7.0, configureISAPI and CGI to allow CommandCenter pages to load.

About this task

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, Cognosfiles that have these web service extensions are unable to run. To modify IIS 7.0security features so that Cognos files with Web Service extensions can executeproperly, you must enable IIS to allow CGI.

The following instructions are specific to Windows Server 2008 with IIS 7.0.

For more information, see Configuring the web server in the IBM Cognos BusinessIntelligence Information Center.

Procedure1. Log on to the reporting server as a user with administrative privileges.2. Open the Windows Internet Information Services Manager from the Start

menu, by clicking Administrative Tools > Internet Information ServicesManager.

Chapter 5. Cognos Business Intelligence installations 43

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc%2Fc_configureawebserver_single.html&path%3D0_13_6_15

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/topic/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc/t_inst_64-bitgateway.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/topic/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc/c_compiledgateways.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/topic/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc/c_cgigateways.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/topic/com.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc/t_enablewebdavforreportstudio.html

http://pic.dhe.ibm.com/infocenter/cbi/v10r2m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.inst_cr_winux.10.2.0.doc%2Fc_configureawebserver_single.html&path%3D0_13_6_15

3. In Internet Information Services Manager, select the application server thatyou want to configure.

4. In the Features view, locate the ISAPI and CGI Restrictions icon.v If the ISAPI and CGI Restrictions icon is not displayed, enable ISAPI and

CGI extensions as described in the step 5.v If the ISAPI and CGI Restrictions exists, skip the following step, and

continue to step 6.5. To enable ISAPI and CGI extensions, create a role in the Windows Server

Manager.a. In Internet Information Services Manage, right-click Roles and select Add

Roles.b. On the Before You Begin page in the Add Role Services wizard, click

Next.c. On the Select Server Roles page, select WebServer (IIS) and click Next.d. In the Add Server Roles page, under Application Development, select

CGI, ISAPI Extensions, and ISAPI filters, and click Next.e. On the Confirm Installation Selections page, click Install, and when the

installation is complete, click Close.6. In the Features view of the Internet Information Services Manager,

double-click the ISAPI and CGI Restrictions icon.7. In the Actions pane, select Add.8. In the Add ISAPI or CGI Restriction dialog box, click browse.9. In the ISAPI and CGI Restrictions box, change the File Type filter from .dll

to All Files.10. Enter the path to the cognos.cgi file in the Cognos_HOME\cgi-bin directory.11. Enter a description for the restriction, such as Cognos-CGI.12. Select Allow extension path to execute and click OK.13. Add the module mapping to the web.config or the applicationhost.config

file or both.a. Find the applicationHost.config file.

C:\Windows\System32\inetsrv\config\applicationHost.config.

If the applicationHost.config does not exist, continue to step 14.b. Open the applicationHost.config in a text editor and find the following

entry:<add name="Cognos-CGI" path= "cognos.cgi" verb="*" modules="CgiModule"resourceType="Unspecified" />

c. Add allowPathInfo="true" to the end of the line:<add name="Cognos-CGI" path= "cognos.cgi" verb="*" modules="CgiModule"resourceType="Unspecified" allowPathInfo="true" />

d. Save and close the file.14. Go to the Cognos_HOME\cgi-bin directory and open the web.config file in a

text editor.a. Find the following entry:

<add name="Cognos-CGI" path= "*.cgi" verb="*" modules="CgiModule"resourceType="Unspecified" />

b. Add allowPathInfo='true' to end of the line:<add name="Cognos-CGI" path= "*.cgi" verb="*"modules="CgiModule" resourceType="Unspecified" allowPathInfo="true" />

c. Save and close the file.


Configuring virtual directories in IISYou must configure a virtual directory or alias that is used by the MicrosoftInternet Information Services to map to a physical location.

Procedure1. From the Internet Services Manager, expand the tree for the server that you

want to configure, and then expand Default Web Site.2. Right-click Default Web Site and select Add Virtual Directory from the

menu.3. On the Add Virtual Directory page, create the ibmcognos virtual directory.

a. In the Alias field, type ibmcognos.b. In the Physical Path field, enter the path to the webcontent directory

under Cognos_HOME

c. Click OK.4. Right-click the ibmcognos virtual directory that you created and select Add

Virtual Directory.5. On the Add Virtual Directory screen, create a cgi-bin virtual subdirectory.

a. In the Alias field, type cgi-bin.b. In the Physical Path field, enter the path to the cgi-bin directory under

Cognos_HOME.c. Click OK.

6. In the Connections pane, select the cgi-bin virtual director, and double-clickHandler Mappings.

7. In the Actions pane click Add Module Mapping, and in the Request Pathfield, enter *.cgi..

8. In the Module list, select CgiModule and enter a name, such as Cognos-CGI.9. Click OK.

10. Internet Information Services Manager.

Configuring the Apache Web Server on a Windows operatingsystem

You must configure your web server before users can connect to the IBM CognosBusiness Intelligence portal.

Procedure1. Log on to the web server as a user with administrative privileges.2. From the command prompt, go to the Apache_Home\conf\ directory.3. Make a backup copy of the httpd.conf file and rename the file to:

httpd.conf.original.

4. Open the httpd.conf file in a text editor.5. Configure the virtual directories by adding the following lines to the end of the

httpd.conf file:ScriptAlias /ibmcognos/cgi-bin "<Cognos_HOME>\cgi-bin"<Directory "<Cognos_HOME>\cgi-bin">Options FollowSymLinksAllowOverride FileInfoOrder Allow,DenyAllow from All</Directory>

Alias /ibmcognos "<Cognos_HOME>\webcontent"


<Directory "<Cognos_HOME>\webcontent">Options FollowSymLinksAllowOverride FileInfoOrder Allow,DenyAllow from All</Directory>

6. Restart the web server service though the Window Services or by using theWindow Start menu.

Configuring the Apache Web Server on AIX or Linux operatingsystems

You must configure your web server before users can connect to the IBM CognosBusiness Intelligence portal.

Procedure1. Log on to web server as a non-root user with administrative privileges.2. Go to the Apache_HOME/conf directory.3. Make a backup copy of the httpd.conf file and rename the file to:

httpd.conf.original.

4. Open the httpd.conf file in a text editor.5. Configure the virtual directories by adding the following lines to the end of the

httpd.conf file:ScriptAlias /ibmcognos/cgi-bin "<Cognos_HOME>/cgi-bin"<Directory "<Cognos_HOME>\cgi-bin">Options FollowSymLinksAllowOverride FileInfoOrder Allow,DenyAllow from All</Directory>

Alias /ibmcognos "<Cognos_HOME>/webcontent"<Directory "<Cognos_HOME>\webcontent">Options FollowSymLinksAllowOverride FileInfoOrder Allow,DenyAllow from All</Directory>

6. Use the following commands to restart the Apache Web Server:Apache_HOME/bin/apachectl stop

Apache_HOME/bin/apachectl start

Configuring a connection to the content store for Oracle databaseAfter you install IBM Cognos Business Intelligence and the IBM Cognos SoftwareDevelopment Kit, configure a connection to the content store database.

Before you begin

Ensure that you copied the JDBC database driver, ojdbc5.jar, file to thec10_location\webapps\p2pd\Web-Inf\lib directory.

Procedure1. Start Cognos Configuration.

v On Windows computers, from the Start menu, click All Programs > IBMCognos 10 > IBM Cognos Configuration.


v ON AIX computers, go to the Cognos_HOME/c10_64/bin64 directory, and typethe following command:./cogconfig.sh

2. In Cognos Configuration, configure the database connection to the contentstore.a. In the Explorer pane, under Data Access > Content Manager,, right-click

Content Store > Delete.b. Right-click Content Manager > New Resource > Database.c. In the New Database dialog box, for the Name field, enter a descriptive

name for the connection.

Note: The name is not required to match the database identifier.d. For the Type, select Oracle Database (Advanced) for Oracle RAC databases,

or Oracle Database if you are not using an Oracle RAC database.e. Click OK.f. In the Explorer panel, select the new connection, and in the Properties

panel, use the following tables to enter the property settings.

Table 24. Content store property settings for Oracle database

Property name Property value

Database server and port number The name of the database server and thelistener port that is used for the databaseinstance.

User ID and Password Click the value field and then click thepencil icon.

In the Value - User ID and password field,enter the appropriate values for the Cognosuser you created for the content storedatabase.

If you used the IBM OpenPages GRCPlatform Installer for Cognos, the defaultuser is cognos.

Service name Enter the SID for the database instance.

Table 25. Content store property settings for Oracle database (Advanced) (Oracle RACdatabase)


Database server and port number The name of the database server and the listenerport that is used for the database instance.

User ID and Password Click the value field and then click the pencilicon.

In the Value - User ID and password field, enterthe appropriate values for the Cognos user youcreated for the content store database.

If you used the IBM OpenPages GRC PlatformInstaller for Cognos, the default user is cognos.


Table 25. Content store property settings for Oracle database (Advanced) (Oracle RACdatabase) (continued)


Database specifier Enter a database specifier string in the followingformat with no carriage returns:

(description=(address=(host=<server_name>)(protocol=tcp)(port=<port>)(connect_data(service_name=<service_name>)))

3. To test that the database connection to the content store database is successful,in the Explorer pane, right-click the content store database connection and clickTest.

4. To start the Cognos services, click Actions > Start.

Note: If you chose to upgrade your content store database by creating abackup and restoring it, you are prompted to upgrade your reports. Do notselect the option to upgrade your reporting content. Upgrade your reports laterby using the New Report Upgrade wizard in IBM Cognos Administration.


Chapter 6. OpenPages application server installations

Install the OpenPages application software on either an administrative server ormanaged server.

The OpenPages application installation program installs the following components:v OpenPages applicationv OpenPages workflow server and notification componentsv OpenPages database schema (optional)v Oracle WebLogic Server (if purchased from IBM)

Your installation tasks depend on the server role. Use the following table todetermine the type of application server installation.

Table 26. Server roles and installation type

Installation type Server role

Administrative serverinstallation Used as the administrative server for the OpenPages

environment.

In a clustered environment, there is one administrativeserver and all other application servers are managedserversImportant: If you use LDAP authentication, you mustinclude LDAP connection information in a configuredtnsnames.ora file on the application server to ensure thatOpenPages can connect to the database.

Managed server installation Used as an extra server in a cluster environment (notintended for administration).Restriction: You must install the OpenPages applicationon the administrative server before you can install themanaged servers in your configuration. The installationpath must be the same on the administrative server andon all managed servers.

Prerequisite tasks for the OpenPages application installationBefore you install the IBM OpenPages application, ensure that the Oracle databaseclient is installed on the OpenPages application server.

64-bit Oracle Client software installations on OpenPagesapplication servers

Depending on your environment, you must install Oracle Client software onmultiple OpenPages GRC Platform application server computers to connect toOracle database. Use the Oracle Client driver files, networking components, andtools to remotely administer the Oracle database.

Copying the installation files for the application serverTo improve performance, copy the installation kit files from the IBM OpenPagesGRC Platform media pack to the local system.

49

Procedure1. Log on to your database server as a user with administrative privileges.2. Using the Run as Administrator option for Windows computers, start a

Command Prompt window, or for AIX computers, open a shell.3. Copy the installation directory from the Installer DVD.

v For Windows installations, OP_version_Non_Embedded_Installerv For AIX installations, OP_version_Non_Embedded_Installer

Note: For AIX installations, ensure that you have full rights to the localinstallation directory.

Setting the ORACLE_HOME environment variable onOpenPages admin and managed servers

Set up the ORACLE_HOME environment variable to point to the directory wherethe Oracle database client software is installed. Set the variable on all admin andmanaged servers.

Procedure1. Log on to the application server as a user with administrative privileges and

full access to the local server drives.

Note: For AIX installations, log in as a non-root user, such as the opuser userthat you created for the OpenPages installation.

2. Set the ORACLE_HOME environment variable to point to the Oracle Clientinstallation directory:v On Windows computers, type the following command:

set ORACLE_HOME=ORACLE_BASE\client_software

v On Windows computers, if the OpenPages application server and thedatabase server are on the same computer, use the location of the Oracledatabase server.

v On AIX computers, type the following command:export ORACLE_HOME=ORACLE_BASE/software.

v On AIX computers, if the OpenPages application server and the databaseserver are on the same computer, use the location of the Oracle databaseserver.

3. Add the location of the Oracle client installation to the PATH environmentvariable.v For example, on Windows computers, C:\ORACLE_BASE\client_software.v For example, on AIX computers, type the following command:

export PATH=$ORACLE_HOME/bin:$PATH

4. On AIX computers, refresh the profile by closing and reopening the AIX shell.

Custom OpenPages Database Schema installationsInstead of loading the default OpenPages database schema, you can load your owncustom configuration data. You can install the OpenPages application before youload your custom data. However, you must load your data before you run theOpenPages application.


Additional prerequisite setup for AIX computersIf you are installing the OpenPages application software into an AIX environment,ensure that your system and environment meet additional prerequisites.

Creating the installation directory for WebSphere ApplicationServer

Create the installation directory for WebSphere Application Server and change theownership of the directory to the installation user.

Procedure1. Log on to the database server as root.2. Open an AIX shell.3. If the WebSphere Application Server installation directory does not exist, create

the directory.mkdir -p <SOFTWARE_INSTALLATION_DIRVE>

For example, mkdir -p /opt/OEI/Oracle

4. To change ownership of the directory, type the following command:chown -R opuser:oinstall <Location of SOFTWARE_INSTALL_DRIVE>

Worksheet for installing the OpenPages GRC Platform on applicationservers

Before you install OpenPages GRC Platform on application servers, collectinstallation and configuration information, such as server computer types, serverroles, host names, and ports.

Server role

Use the following table to record server role details.

Table 27. Server role details

Server role Details

Is this installation an OpenPages adminserver or managed server installation?

Is this installation admin server or one ormore managed servers installations?

Installation location of prerequisite software

The installation program prompts for the location of prerequisite software.

Use the following table to record prerequisite software details.

Table 28. Prerequisite software details

Software or software locations Details

Oracle database server host name

Oracle database server port

OpenPages database instance name and service ID (SID)

TNS alias name

Chapter 6. OpenPages application server installations 51

Table 28. Prerequisite software details (continued)

Software or software locations Details

ORACLE_HOME (Installation location of the Oracle databaseserver software)

Installation location of Oracle data

Installation location of WebSphere Application Server orWebLogic Server

Installation location of OpenPages application software

The installation program prompts for the following OpenPages installationinformation.

Note: The installation program creates new directories. For AIX environments,ensure that the user has the correct permissions to create the directories.

Use the following table to record prerequisite software details.

Table 29. Prerequisite software installation locations

Software location Details

Installation directory of the OpenPagesapplication software

Installation directory of the OpenPagesapplication server files directory

OpenPages workflow server files directory

OpenPages storage location for files andforms that are associated with OpenPagesobjects

Back up and restore locations for OpenPagesdatabase and application settings

Installation location of WebSphereApplication Server or WebLogic Server

Application directory (if WebLogic Server isnot already installed)

OpenPages host names and ports

The IBM OpenPages GRC Platform Installer creates the following configurationsettings from information that you specify.

Use the following table to record the OpenPages application details.

Table 30. OpenPages application settings

Setting Details

OpenPages admin server host name

OpenPages admin server port

OpenPages admin server SSL port

OpenPages workflow server admin port

OpenPages workflow server admin SSL port


Table 30. OpenPages application settings (continued)

Setting Details

Port used by OpenPages to connect to theFramework Generator

Multicast address for the OpenPagesworkflow server

Optional: Fully qualified domain name of amail server for OpenPagesworkflow server

Optional: Mail server email senderinformation

Cognos Business Intelligence

The installation program prompts for the following information.

Use the following table to record the Cognos Business Intelligence settings.

Table 31. Cognos Business Intelligence settings

Setting Details

Cognos BI server host name

Cognos BI server port

Application server information

User accounts

The installation program prompts for passwords.

Use the following table to record passwords for the user accounts that are createdduring the installation.

Table 32. User accounts

User accounts Details

Oracle Database system account

Oracle Database SYS account

OpenPages admin server

OpenPages workflow database

OpenPages Super Administrator

Installing OpenPages and workflow server in interactive modeUse the OpenPages GRC Platform installation program to install the OpenPagesapplication and workflow server on the administrator server and managed servers.

Procedure1. Log on to the OpenPages application server as a user with administrative

privileges and full access to the local server drives.Interactive mode installations on AIX servers require an application, such as XWindow System, that provides remote GUI logins.


Note: For AIX installations, use the opuser user or another non-root user.2. On Windows computers, go to Windows Explorer, or on AIX computers, open

an AIX shell.3. Go to the following location within the installer kit files you copied from the

Installer DVD.v On Windows computers, go to OP_version_Non_Embedded_WIN64\

OP_version_Non_Embedded_Installer\Disk1\InstData\VM

v On AIX computers, go to OP_version_Embedded_AIX64/OP_version_Embedded_Installer/Disk1/InstData/VM

4. Start the IBM OpenPages GRC Platform installation program.v On Windows computers, right click opinstall.exe and click Run as

administrator.v On AIX computers, type ./opinstall.bin

5. On the Welcome page, click Next.6. Accept the license agreement, and click Next.

Note: On AIX systems, if you do not have a printer that is configured, youcannot save the license agreement by using the print to file option. To save thelicense agreement to a file, you must configure a printer on the system.

7. On the Installation Information page, for the Installation Folder, specify thedirectory to install OpenPages, and click Next.The installation path must be the same on the admin server and on allmanaged servers. For example, on Windows computers, c:\OpenPages or onAIX computers, /opt/OpenPages.The installation location is OP_HOME.

8. On the Application Server Information page, specify the installation locationof WebLogic Server or WebSphere Application Server.The following table provides descriptions and default values.

Table 33. Application server settings

Field Description Default value or example

Middleware HomeFolder

On AIX computers, thisfield is not required.

Specify the location where youinstalled the WebLogic Servermanually, or the location forthe IBM OpenPages GRCPlatform Installer to use for theinstallation.

C:\oracle\middleware

For Windowsinstallations: WebLogicServer Folder

For AIXinstallations:WebSphereServer Folder

Specify the installation locationfor WebLogic Server orWebSphere Application Server.Note: If you use theinstallation program thatinstalls WebLogic Server thisfield is not displayed.

On Windowscomputers:C:\oracle\middleware\wlserver_10.3

On AIX computers:/opt/IBM/WebSphere/AppServer

Java Home FolderNote: This field is notdisplayed for theOpenPages withWebLogic embeddedinstaller.

Specify the installation locationof Java Development Kit (JDK). On Windows computers:

C:\Java

On AIX computers:/opt/IBM/WebSphere/AppServer/java

9. At the Will this machine administer the cluster prompt, select the server role:


v Select Yes if the computer is the administrator server.The installation can have one administrator server and it must be on thecluster administrator server.

v Select No if the computer is a managed server.The installation can have multiple managed servers on the clusteradministrator server and on cluster member servers.

10. In the How many cluster members do you want to configure on thismachine field, specify the number of managed servers to install.

11. For AIX installations, in the OpenPages Application Starting Port Numberfield, specify the starting port number for the port range that is required byIBM WebSphere Application Server.The default port is 10100

12. For AIX installations, in the OpenPages Workflow Starting Port Numberfield, specify the starting port number for the port range that is required byIBM WebSphere Application Server.The default port is 20100

13. For Windows installations, on the OpenPages Administration ServerInformation page, use the following table to help you specify the OpenPagesadmin server settings.

Note: Port numbers must be 1 - 62545.If there is a port conflict, you change ports after the installation. Forinformation about changing ports, see the IBM OpenPages GRC PlatformAdministrator's Guide.

Restriction: Do not change the port number for the OpenPages admin serveror the workflow admin server.v For Windows installations, the default OpenPages administrator server port

is 7001, and the default workflow administrator server port is 49901.v For AIX installations, the default OpenPages administrator server port is

9060, and the default workflow administrator server port is 9061.

Table 34. Admin server settings on Windows computers

Field Description Default Value

Admin Server Host NameNote: If you areconfiguring an adminserver, this field is notrequired.

Specify the name of theOpenPages admin server.

Admin Port Number Specify the port number thatis used internally to access theOpenPages admin server.

7001

Admin SSL Port Number Specify the port number thatis used internally to access theOpenPages admin serverthrough a secure SSLconnection.

7002

Application HTTP Port Specify the port number thatis used to access theOpenPages application.

7009


Table 34. Admin server settings on Windows computers (continued)


Application HTTPS Port Specify the port number thatis used to access theOpenPages applicationthrough a secure SSLconnection.

7010

Admin Server User Name The OpenPages admin serveruser name.Note: If you are installing acluster member, ensure thatthe WebLogic Server username and password are thesame as used on the clusteradmin. If you enter a differentpassword, the installation willfail.

weblogic

Admin ServerPasswordConfirmPassword

Specify the OpenPages adminserver password.Note: This password mustconsist of at least 8alphanumeric characters,starting with a letter andcontaining at least onenumber.

14. On the OpenPages Workflow Server Information page, use the followingtable to help you specify the workflow server information

Table 35. Workflow server settings


Enter the installationfolder for the WorkflowServer

Specify the installationlocation for OpenPagesworkflow server

For Windows installations:C:\Fujitsu\InterstageBPM

For AIX installations:/opt/Fujitsu/InterstageBPM

Admin Port Number

For AIX installations, thisfield is not displayed.

Specify the OpenPagesworkflow server admin portnumber.

For Windows installations:49901

SSL Port Number

For AIX installations, thisfield is not displayed.

Specify the workflow serverSecure Sockets Layer (SSL)port number.

For Windows installations:49902

Application HTTP Port Specify the port that is used toaccess the workflow server.

49951

Application HTTPS Port If you are using SSLconnections, specify the portthat is used to access theworkflow server.

49952


Table 35. Workflow server settings (continued)


Multicast Address Specify the OpenPagesworkflow server multicast IPaddress.

Do not use 224.0.0.0.

The multicast IP address mustbe unique within the networkaddress spaceNote: When you install on asecondary server in ahorizontal environment, usethe same multicast IP addresson all servers.

15. On the E-mail Notifications page, use the following table to provide the emailaccount information for the workflow notification and OpenPages backupservices, and click Next.

Table 36. Description of email notification settings.

Field Description Default

Mail Server Specify the mail server to usefor OpenPages workflownotifications.

yourserver.yourdomain.com

E-mail User Name Specify the display name ofthe email sender address.Enter a name with no spaces.

sysadmin

From Address Specify the email addressthat is used for sendingmessages from the workflownotification service.

[email protected]

16. For cluster admin server installations, on the OpenPages Database Schemapage, choose whether to configure the OpenPages database schema and useraccounts.v Select Yes to install the OpenPages database schema and users as part of

the OpenPages application installation.v Select No if you manually installed the OpenPages database schema.

Important: You must run the SQL scripts to manually configure thedatabase before installing in interactive mode. If you did not run the SQLscripts in your OpenPages installation kit to configure the database, youcannot complete the current installation.

17. On the Database Connection Information page, specify the information toaccess the OpenPages database instance.Use the following table to help you specify the database connection settings.


Table 37. Description of database connection information


Enter the path to theOracle Home folder onthis machineNote: This field displaysif you are installing theOpenPages DatabaseSchema.

Specify the Oracle database homedirectory on the local computer.

This location is ORACLE_HOME.

This value is takenfrom theenvironmentvariable you set onthe system.

Database Host Name Specify the name of the Oracle databaseserver computer.

Port Number Specify the port number of the Oracledatabase server computer.

This port is the database instance portnumber, and must be the same numberyou entered during the Oracle softwareinstallation.Note: The number can be in theORACLE_HOME/software/NETWORK/ADMIN/tnsnames file.

Database Identifier Select the method for identifying theOpenPages database instance, either SIDor Service Name and enter the SID orService Name in the field.

Use the same name used duringOpenPages database installation.

For Oracle RAC installations, always usethe Service Name.Note: The name can be in theORACLE_HOME/software/NETWORK/ADMIN/tnsnames file.

TNS Alias Name Enter the TNS (Transparent NetworkSubstrate) alias name. The TNS alias isthe name by which an Oracle databaseinstance is known on a network.

Use the same name used duringOpenPages database installation.

Enter the Oracle DatafileFolder on the DatabaseServerNote: If you are installingthe OpenPages DatabaseSchema this field isrequired.

Specify the Oracle data home directoryon database server. This directory is thelocation where Oracle data is stored.

For example, on Windows computers,C:\openpages_data\repository\database112_se_x64\oradata\SID

For example, on AIX computers,opt/openpages_data/repository\database112_se_x64/oradata/SID

The installation program uses the SID or service name and JDBC drivers toconnect to the database instance. Also, the installation program uses theOracle Client to verify the TNS alias name. If the installation program cannot


connect to the database, an error message is displayed. Return to theDatabase Connection Information screen to correct the problem.

18. On the Database User Information page, specify the user name andpasswords for the Oracle database.If you already installed the OpenPages database schema, these fields are notdisplayedThe following table provides descriptions and default values.

Table 38. Database user settings


DB System User Name Specify the current Oraclesystem account user name.

system

DB System Password Specify the password for theDB System User Name.Note: If you do not haveaccess to the system useraccount, then any databaseuser that has administrativeprivileges can enter thepassword.

DB SYS User Name Specify the DB SYS username.

sys

DB SYS Password Specify the password for theDB SYS User NameNote: If you do not haveaccess to the SYS useraccount, then any databaseuser that has administrativeprivileges can enter thepassword.

OpenPages User Name Specify the user name for theOpenPages applicationdatabase.

openpages

OpenPages Password Specify the password for theOpenPages User Nameaccount.

Workflow User Name Specify the user name andpassword for the workflowapplication database.

opworkflow

Workflow Password Specify the password for theWorkflow User Nameaccount.

The installation program accesses the database instance by using the settingsthat you specified during the installation. If the installation program cannotaccess the specified instance, an error message is displayed. Return to theDatabase User Information page and the Database Connection Informationpage to correct the problem.

19. If you chose to configure the database schema, on the Base Currency Codepage, select the base currency to use as the basis for an exchange rateconversion.If you have a test environment, development environment, or user acceptancetesting environment, set the currency to the same value in each environment.


Important: You cannot change the base currency after installation.20. On the Storage and Configuration Information page, specify storage, backup,

and restore locations.The following table provides descriptions and default values for the storagesettings.

Note: In a load-balanced environment, the OpenPages Storage Locationdirection must be in the same location on the Admin server and on eachmanaged server.

Table 39. Storage and configuration settings


OpenPages StorageLocationNote: Field notdisplayed or requiredfor a new managedserver installation.

Specify the directory where attached filesand forms associated with OpenPagesobjects are stored.

You can also specify a valid UNC path tothe shared storage directory.

For example, on Windows computers,\\your-server-name\openpages_storage.

For example, on AIX computers,"/opt/OpenPages/openpages-storage.

On Windowscomputers,C:\OpenPages\openpages-storage.

On AIX computers,/opt/OpenPages/openpages-storage.

OpenPagesBackup/RestoreLocation

Specify the directory where the backupand restore utility places the files itcreates when backing up and restoring theOpenPages database and applicationsettings.

On Windowscomputers,C:\OpenPages\openpages-backup-restore.

On AIX computers,/opt/OpenPages/openpages-storage.

Do you want to loadOpenPagesConfiguration Data?Note: Field notdisplayed or requiredfor a new managedserver installation.

Select Yes to enable user access toOpenPages GRC Platform data and tostandard Cognos Business Intelligencereports.

Select No, if you already loaded theconfiguration data. For example, in testenvironments where you have multipleinstallations of IBM OpenPages and youalready loaded the configuration data.

If you select No, and the defaultconfiguration is not already loaded, youmust manually load the level-0 schema.Otherwise, you see garbled text when inthe OpenPages application.

Yes

21. On the OpenPages Administrator Information page, specify the user name tocreate for the OpenPages application Super Administrator.Ensure that you enter the Super Administrator user name and passwordcorrectly. The installation program does not verify the user name.

22. On the CommandCenter Information page, specify the IBM Cognos BusinessIntelligence server settings.


Note: The installation program does not verify the information that youenter. You can specify the settings before you install the CommandCenter .You can change these values after the installation by editing theaurora.properties file

Table 40. CommandCenter settings


Host Name Specify the computer name of the serverwhere IBM Cognos Business Intelligenceserver is installed.

Port Number Specify the port number that is used byIBM Cognos Business Intelligence serverfor http requests.

80

URL Context Root Specify the context root of IBM CognosBusiness Intelligence. The context rootmaps to the URL or the applicationvirtual directory of the IBM Cognos BIserver.

ibmcognos

Cognos Dispatcher Port Specify the port number that is used bythe IBM Cognos BI server dispatcher toconnect to the Framework Generator

9300

Framework Generator Port Specify the pot that the FrameworkGenerator uses.

8080

23. On the Confirm Installation Data page, review the settings and click Installto begin the installation of both the OpenPages application software and theworkflow server.

What to do next

Verify that the installation works. You must also install CommandCenter. Tochange host names or post numbers, see the IBM OpenPages GRC PlatformAdministrator's Guide.Related concepts:“Port assignments” on page 23Both dedicated ports and ports that are dynamically assigned for each installationare used for IBM OpenPages GRC Platform deployments. These default ports canbe changed after installation.Related tasks:“Manually loading the configuration data after a new installation” on page 150The installation program for OpenPages GRC Platform automatically loads theOpenPages GRC Platform data and enables user access to the standard CognosBusiness Intelligence reports. In limited situations, you can manually load thelevel-0 schema.

Testing the connections to the database server and the OpenPagesrepository

Test whether the SQL*Net connect string can connect to the database listener byusing the TNSPING utility in the ORACLE HOME/bin directory. The TNSPING utilitytests if the listener is available. It does not test whether the databases behind thelistener are working.


To test that the OpenPages repository is created, use SQL*Plus to log on to theOpenPages Oracle database schema.

Procedure1. To test whether you can log on to Oracle Enterprise Manager Database Control,

the web-based interface that is used to administer an Oracle database, type thefollowing command:https://oracle_server_name:port/em

In a default installation, the port number is 1158.2. To test whether a SQL*Net connect string can connect to the listener, type the

following command:tnsping database_instance_name

The utility requests acknowledgement that the service name is valid and thatthe listener is configured to handle requests for that service name.If the configuration is correct, a message is displayed that shows the returntime.If the configuration is not correct, the utility returns an error message. Ensurethat you use the correct service name and that the listener is started on theserver computer.

3. To test that OpenPages repository is created, type the following command:sqlplus username/password@service_name

For example, sqlplus system/openpages@op

The system connects you to an Oracle Database instance.4. To exit SQL*Plus, type exit.

Starting WebLogic Server cluster members for the first timeIf you installed an OpenPages instance on a cluster member server, you mustmanually start the OpenPages and workflow services the first time. For example, ifthe computer where you installed OpenPages is not used to administer the cluster,use the command prompt.

Using the command prompt to start WebLogic services creates a boot.propertiesfile. The boot identity file contains user credentials for starting and stopping anWebLogic Server services.

After the first time, you can use Windows Services or the command prompt.

Procedure1. Log on to the managed server as a user with Administrator privileges.2. Use the Run as Administrator option to open a Command Prompt window.3. Start the OpenPages services.

a. Go to the OP_Home\OpenPagesDomain\bin directory:b. For each OpenPages instance on this system, type the following command:

startOPServer.cmd<host_name>-OpenPagesServer<managed_server_Number>

For example:startOPServer.cmd managedserver01-OpenPagesServer1startOPServer.cmd managedserver01-OpenPagesServer2

c. At the prompt, enter the WebLogic Server administrator user name andpassword.


d. Optional: Verify that the boot.properties file is created in theOP_Home\OpenPagesDomain\ directory.The user name and password are encrypted.

4. Start the workflow service by using the command line:a. Go to the Workflow_Home\IBPMDomain\bin directory:

The Workflow_Home directory is the installation location of Fujitsu InterstageBPM.

b. For each workflow instance on this system, type the following command:startIBPMServer.cmd<host_name>-InterstageBPMCS<managed_server_number>

For example:startIBPMServer.cmd managedserver01-InterstageBPMCS1startIBPMServer.cmd managedserver01-InterstageBPMCS2

c. At the prompt, enter the Oracle WebLogic administrator user name andpassword.

d. Optional: Verify that the boot.properties is in the Workflow_Home\IBPMDomain\ directory.The user name and password are encrypted.



Chapter 7. OpenPages CommandCenter installations

The OpenPages CommandCenter component integrates the OpenPages applicationwith IBM Cognos Business Intelligence. When you install the CommandCenter, theIBM OpenPages Reporting Framework Generator is installed.

You can generate reports that use the hierarchy of OpenPages compliance objects.You can also report on the metadata that is attached to those objects.

Prerequisite tasks for CommandCenter installationsSome prerequisite tasks are required before you install CommandCenter on thereporting server.

Setting database environment variables for reporting serverson Windows operating systems

You must set some system environment variables on the reporting server.

Procedure1. Log on to the reporting server as a user with administrative privileges.2. Set the following environment variables.

Table 41. Environment variable settings on the reporting server on Windows operatingsystems

Environment variable Setting

JAVA_HOME Specifies the installation location of your Java RuntimeEnvironment (JRE).

COGNOS_HOME Specifies the location of IBM Cognos BusinessIntelligence bin directory.

ORACLE_HOME The default location is a subdirectory ofORACLE_BASE, such as ORACLE_BASE=C:\app\product\11.2.0

If you installed the OpenPages application and IBMCognos Business Intelligence on the same server, enterthe location for the 32-bit Oracle Client.Example: ORACLE_HOME=C:\app\product\11.2.0\client_32bit

TNS_ADMIN Specifies the location of the tnsnames.ora file

The default location is the Oracle_Home\network\admindirectory

NLS_LANG Specifies the database character set configured duringthe database installation. By default, set it toAMERICAN_AMERICA.AL32UTF8

To display non-English characters for Japanese locales,set the NLS_LANG property:NLS_LANG=JAPANESE_JAPAN.JA16SJISTILDE

3. Append the JAVA_HOME and ORACLE_HOME to the PATH environment variable.

65

Example: Add %JAVA_HOME%/bin and %ORACLE_HOME%/bin to the PATHenvironment variable.

Setting environment variables for the reporting server on AIXcomputers

You must set some system environment variables on the reporting server.

Procedure1. Log on to the reporting server as a non-root user with administrative

privileges.2. To determine the version of Java that is in the PATH variable, enter the

following command:java -version

If you get the following error, Java is not in the PATH variable.Command not found

3. Set the environment variables.

Table 42. Environment variable settings on the reporting server on AIX operating systems

Environment variable Example settings

JAVA_HOME Specifies the installation location of your Java RuntimeEnvironment (JRE).

/opt/local/jdk1.6.0/bin

COGNOS_HOME Specifies the installation location of IBM CognosBusiness Intelligence.

/opt/IBM/cognos/c10

ORACLE_HOME The default location is /opt/oracle/openpages_data/repository/client112_ac_x64/software

If you installed the OpenPages application andCommandCenter on the same server, enter the locationto the 32-bit Oracle Client.

TNS_ADMIN Specifies the location of the tnsnames.ora file

The default location is the $Oracle_Home\network\admindirectory

NLS_LANG Specifies the database character set configured duringthe database installation. By default, set toAMERICAN_AMERICA.AL32UTF8Important: To display non-English characters forJapanese locales, setNLS_LANG=JAPANESE_JAPAN.JA16SJISTILDE

4. Append the JAVA_HOME and ORACLE_HOME to the PATH variable.

Example: PATH=$ORACLE_HOME/bin:$JAVA_HOME/bin:$PATH

5. Refresh the profile.

Creating the installation directory for CommandCenter on AIXcomputers

Create the installation directory for the CommandCenter installation and changethe ownership of the directory to the installation user.


Procedure1. Log on to the reporting server as a root user.2. Open a shell.3. If the CommandCenter installation directory does not exist, create it by typing

the following command:mkdir -p <SOFTWARE_DIRVE>

4. To change ownership of the directory, type the following command:chown -R <user>:<group> <SOFTWARE_DRIVE>

For example: chown –R opuser:staff /opt/OpenPages/CommandCenter

Worksheet for CommandCenter installationsBefore you install the CommandCenter, ensure that you collect installation andconfiguration information, such as host names, and ports.

Installation information about the CommandCenter software

The installation program prompts for the following CommandCenter installationinformation.

The installation program creates new directories.

For AIX operating systems, ensure that the user has the correct permissions tocreate the directories.

Table 43. Installation location for CommandCenter software

Installation location Details

CommandCenter installationlocation

Cognos Framework Model outputlocation

CommandCenter URL

Cognos Framework Generatorport number

Installation settings for prerequisite software

The installation program prompts for information about prerequisite software.

Table 44. CommandCenter installer prompts for prerequisite software

Setting Details

Cognos Business Intelligence installation folder

Oracle 32-bit Client Installation Folder

CommandCenter Dispatcher URL (IBM Cognos BI dispatcherURL)

OpenPages database host name

OpenPages database port

OpenPages database alias

OpenPages database SID

OpenPages user name

Chapter 7. OpenPages CommandCenter installations 67

Table 44. CommandCenter installer prompts for prerequisite software (continued)

Setting Details

OpenPages user password

OpenPages application server name

Database alias name for content store database

Cognos user name

Cognos password

Mail server (workflow notifications)

Email user name

Email sender address

Back up and restore location for the content store database

Email address for sender

Installing CommandCenter in interactive modeInstall the CommandCenter on the reporting server. The CommandCenterinstallation deploys the Framework Model Generator. After installation, you cangenerate reports that use the hierarchy of OpenPages compliance objects. You canalso run reports on the metadata attached to those objects.

Before you begin

Ensure that Cognos Business Intelligence Server is running.

Procedure1. Log on to the reporting server as a user with administrative privileges and

full access to the local server drives.Interactive mode installations on AIX servers require an application thatprovides remote GUI logins.

Note: For AIX installations, use the opuser user or another non-root user.2. Go to the location where you copied the CommandCenter installation files.

v On Windows computers, go to OP_version_CommandCenter\OpenPages_CommandCenter\Disk1\InstData\Windows\VM

v On UNIX computers, go to OP_version_CommandCenter\OpenPages_CommandCenter\Disk1\InstData\AIX\VM

3. Start the IBM OpenPages GRC Platform installation program for theCommandCenter.v On Windows computers, right-click CommandCenterSetup.exe and click Run

as administrator.v On AIX computers, type ./CommandCenterSetup.bin

4. On the Welcome page, click Next.5. On the Software License Agreement page, accept the license agreement and

click Next.6. On the Installation Information page, specify the installation settings and

click Next.


Table 45. Installation field descriptions and default values

Installation fieldname Description Default Value

CommandCenterInstallation Folder

Specifies the location to installCommandCenter.

On Windows computers:C:\OpenPages\CommandCenter

On AIX computers:/opt/OpenPages/CommandCenter

Cognos InstallationFolder

Specifies the location where CognosBusiness Intelligence components areinstalled.

On Windows computers:

C:\ProgramFiles\ibm\cognos\c10_64

On AIX computers:

/opt/ibm/cognos/cognos10_64

Oracle 32-bit ClientInstallation Folder

Specifies the location where the 32-bitversion of the Oracle Client isinstalled.

For example, on Windowcomputers:

ORACLE_BASE\product\

version

For example, on AIXcomputers,/ORACLE_BASE/product/version

CommandCenterDispatcher URL

Specifies the IBM Cognos BIdispatcher URL.

http://cognos_server_name:9300/p2pd/servlet/dispatch

For an SSL environment,

https://cognos_server_name:9300/p2pd/servlet/dispatch

7. On the OpenPages Database Information page, specify the databaseconnection information and click Next.

Table 46. Database field descriptions and default values

Database field name Description

Database Host Name Specifies the name of the server that hosts the OpenPagesdatabase.

Database Port Specifies the port used to access the OpenPages database.Note: Ensure that the OpenPages application uses the sameport.

Alias Name Specifies the TNS alias name of the OpenPages databaseinstance.

Database Identifier Specifies the method for identifying the CommandCenterdatabase instance. Use either SID or Service Name.Note: For Oracle RAC installations, use Service Name.

OpenPages User Name Specifies the user name of the account that is used to access theOpenPages database instance.

The default user name is openpages.


Table 46. Database field descriptions and default values (continued)

Database field name Description

OpenPages Password Specifies the password for the OpenPages user account.

8. On the OpenPages Server Information page, enter the required information.

Table 47. OpenPages server settings and descriptions

OpenPages Server field name Description

Application Server Host Name Specifies the IP address or computer name of theOpenPages application server.

v If this installation is the first CommandCenterserver, enter the IP address or computer name ofthe OpenPages cluster administrator.

v If this installation is a secondary CommandCenterserver, enter the IP address of the OpenPagescluster member application server.

Application User Name Specifies the user name of the account thatCommandCenter uses to access the OpenPagesapplication.

The default user is OpenPagesAdministrator.

Application Password Specifies the password belonging to the account thatCommandCenter uses to access the OpenPagesapplication.

Is SSL configured for theOpenPages Server

If CommandCenter must use an SSL connection tothe OpenPages application, select Yes. Ensure thatyou enter the SSL port for the Application ServerPort.

On Windows computers, the SSL port is listed in theOP_HOME\temp\aurora\conf\OPSERVER_STATUS.txt logfile.

On AIX computers, the SSL port is listed in theOP_HOME/temp/wasconfig/OpenPages_Node_Name/config.props log file.

Otherwise, if an SSL connection is not required,select No. If you select Yes, make sure you enter theSSL port in the Application Server Port field above.The SSL port is listed in the following log.

Application Server Port Specifies the port used to access the OpenPagesapplication. Specify the SSL port number for SSLconnections.Note: If this installation is a secondaryCommandCenter server, enter the port of theOpenPages cluster member . The port for clustermember is dynamically assigned during theinstallation, and is available in theObjectManager.properties file on the OpenPagesserver.

9. On the Reporting Framework Information page, specify the information thatis required to configure the Framework Generator service, and then click Next.


Table 48. Description of the reporting framework settings

Reporting Framework field name Description

Framework Output Folder Specifies the location where the FrameworkModel is stored.

The default setting is the CommandCenterinstallation location.

On Windows computers: C:\CommandCenter\FrameworkGeneration\output.

On AIX computers: /opt/OpenPages/CommandCenter/ FrameworkGeneration/output.

Framework Port Specifies the port number used to access theFramework Generator server.

The default port is 8080.

10. On the Backup & Restore Information pages, specify the database andCognos Business Intelligence information that CommandCenter needs toconfigure the backup and restore utility.

Table 49. Page 1 Cognos BI settings and descriptions

Backup and Restore field name Description

Database Alias Name Specifies the name of the content store databaseinstance on the database server computer.

Cognos User Name Specifies the Cognos user name.

The default value is cognos

Cognos Password Specifies the password for the Cognos User Name.

Table 50. Page 2 mail server settings and descriptions

Backup and RestoreMail Server fieldname Description Default value

Mail Server Specifies the mail server to usefor OpenPages workflownotifications.

yourserver.yourdomain.com

E-mail User Name Specifies the user nameassociated with the E-mailSender Address.

sysadmin

From Address Specifies the email address usedfor sending messages from theworkflow notification service.

[email protected]


Table 50. Page 2 mail server settings and descriptions (continued)

Backup and RestoreMail Server fieldname Description Default value

OpenPagesBackup/RestoreLocation

Specifies the directory where theBackup/Restore utility places thefiles it creates when backing upand restoring the content storedatabase and applicationsettings.

Uses the CommandCenterInstallation location.

On Windows computers,C:\CommandCenter\openpages_cc_backup_restore

On AIX computers,/opt/CommandCenter/openpages_cc_backup_restore

11. On the Confirm Installation Data screen, review your selections and whensatisfied, click Install.The installation might take awhile to complete.

12. On the Install Complete page, click Done to complete the installation.

What to do next

Some post-installation tasks, such as creating the reporting schema and frameworkand adding servers to the list of safe domain names, are required.Related tasks:“Creating the reporting schema and framework”To see the default OpenPages reports, you must create a reporting schema andupdate the reporting framework.

CommandCenter post installation tasksAfter you install CommandCenter, some post installation tasks are required. Youmust update CommandCenter configuration files to ensure that OpenPagescomponents can communicate with each other.

Creating the reporting schema and frameworkTo see the default OpenPages reports, you must create a reporting schema andupdate the reporting framework.

Procedure1. In a web browser, open the OpenPages application:

http://openpages_server:port/openpages

2. Log on to the OpenPages application as a user with administrative privileges.3. For System Admin Mode, switch from Disabled to Enabled.4. From the menu bar, click Administration and select Reporting Schema.5. Click Create.6. After the create operation finishes, click System Admin Mode to switch from

Enabled to Disabled.7. From the menu bar, click Administration > Reporting Framework >

Generation.8. On the Reporting Framework Operations page, click Update.


9. In the Reporting Framework Generation window, under FrameworkGeneration, select the Framework Model and Labels and other options youwant for the relational data model.

10. Click Submit.11. To view the progress of the update, click Refresh.

The Percent Complete column on the Reporting Framework Operations tableupdates the percentage of completion.

Results

Updating the reporting framework process takes approximately 30 minutes orlonger.

What to do next

You must drop the reporting schema before you install the IBM OpenPages GRCPlatform Modules.

Manually creating the reporting schemaThe database schema and users for the content store is automatically created whenthe Cognos Business Intelligence services are started for the first time. You canmanually create the database schema and users.

IBM Cognos Business Intelligence uses a database structure, called the contentstore, to store, organize, and retrieve information about the queries and reports youcreate.

For optimal performance, ensure that the IBM Cognos Business Intelligence contentstore and OpenPages have separate database instances. However, for a smallerdeployment or a test environment, you can use a single database instance.

Use the database scripts in the OpenPages GRC Platform installation to manuallycreate the content store schema.

Manually creating the reporting tablespace and user for Oracle databases:

After you create the Cognos content store, you can manually create the contentstore 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.

Procedure

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

Note: For AIX operating systems, log in as a non-root user.2. From the IBM OpenPages GRC Platform Installer version DVD or your network

share location, copy the OP_version_Configuration\Database\ORACLE\COGNOSdirectory to the local system.

3. Log on to SQL*Plus by using the following command:sqlplus system/system_password@oracle_tns_alias

To create the tablespace in the OpenPages database instance, enter theoracle_tns_alias of the OpenPages database. oracle_tns_alias is the database alias


for the OpenPages database instance, as set during the Oracle databaseinstallation. If necessary, you can retrieve this alias from the tnsnames.ora file.If you created a separate database instance for the content store, create thetablespace in the content store database instance. Enter the oracle_tns_alias ofthe content store database.

4. At the SQL prompt, type the following command:@cognosdbcreate.sql cognos_user cognos_password oracle_data_hometablespace_name log_file

Table 51. Parameter descriptions for cognosdbcreate.sql script for Oracle databases

Script parameters Description

cognos_user Specifies the new user name for the content store database

cognos_password Specifies the password for the cognos_user

oracle_data_home Specifies the location of the Oracle data home directory for thecontent store database instance.

On Windows operating systems: C:\ORACLE_BASE\oradata\SID

On AIX operating systems: ORACLE_BASE/oradata/SID

tablespace_name Specifies the name of the exported tablespace.

log_file Specifies the file name and location of the log file to create.

Changing the CommandCenter host settingsYou must update configuration files to use the CommandCenter server name andport settings.


privileges.2. Open a browser window and go to the OpenPages application by typing the

following URL:http://OP_server_name:port/openpages

3. Log on to the OpenPages application as a user with administrative privileges.4. Under Administration, select Settings.

a. Expand the OpenPages > Platform > Reporting Schema > Object URLGenerator.

b. Click Host.c. In the Value field, update the setting to point to the OpenPages server.

Note: If you use the CommandCenter in a load-balanced environment,you must type the fully qualified domain name of the load balancingserver. If required, change the port.

5. Stop OpenPages services.6. On the application server, go to the OP_Home\aurora\conf directory and open

the aurora.properties file in a text editor.7. In the cognos.framework.refresh.servlet=http\://server_name\:8080/crf-

refresher property, replace server_name\:8080 with the reporting server nameand port.cognos.framework.refresh.servlet=http\://ccserver\:8080/crf-refresher


8. In the cognos.server=http\://server_name\:80/ibmcognos/cgi-bin/cognos.cgi property, replace server_name:80 with the reporting server nameand port number.For example,cognos.server=http\://ccserver:80/ibmcognos/cgi-bin/cognos.cgi

9. On Windows computers, add the following value to the logout.url.cognos=property:http\://CommandCenter_server_name\CommandCenter_port\

/ibmcognos/cgi-bin/cognos.cgi?b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

logout.url.cognos=http\://ccserver\:8080/ibmcognos/cgi-bin/cognos.cgi?b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

10. For AIX computers, add the following value to the logout.url.cognos=property:http\://CommandCenter_server_name\CommandCenter_port

/ibmcognos\cgibin\cognos.cgi?b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

logout.url.cognos=http\://ccserver\:8080/ibmcognos/cgi-bin/cognos.cgi?b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

11. Save your changes and exit the editor.

Creating an open session command block for the OpenPagesdata source

For IBM OpenPages GRC Platform to work, you must create an open sessioncommand block for the OpenPages data source.

Procedure1. In the Internet Explorer browser, type the following URL:

http://cognos_server_name/ibmcognos

2. Open IBM Cognos Administration:a. If the Cognos Welcome page is displayed, click Administer IBM Cognos

Content.b. If the IBM Cognos Connection is displayed, click Launch > IBM Cognos

Administration.3. On the Configuration tab, click Data Source Connections.4. Click More next to OpenPages DataSource.5. Click Set properties.6. Select the Connection tab.7. Beside the Open session commands, click Set.8. In the XML database commands box, copy the following text:

<commandBlock><commands><sqlCommand><sql>begin OP_SESSION_MGR.SET_ACTOR_ID_PRIVATE(#$account.parameters.openPagesUserId#);end;</sql></sqlCommand></commands></commandBlock>

9. Click OK to save your changes.


CommandCenter portal securityAfter installation, you can restrict which user groups are allowed to modifyreports. To grant CommandCenter administrative rights, create a group in theOpenPages application or use an existing group, such as OPAdministrators. This isoptional.

OpenPages standard reports can be overwritten during an upgrade. If you want tomodify these standard reports, copy them to your personal folders. From yourfolders, you can then change the reports and restrict access to them.

To restrict user access to administrative functions within the Cognos portal, useIBM Cognos Administration. To prevent users from deleting, changing, or savingreports, restrict access to the OpenPages reports that are in Public Folders. You canalso restrict users from running reporting tools, such as Report Studio, or frommodifying CommandCenter reports.

For more information, see the IBM OpenPages GRC Platform Administrator's Guide.


Chapter 8. Post installation tasks

After installing the OpenPages GRC Platform, you can modify the installationenvironment to improve performance, enhance security, or change default settings.For example, you can tune the application servers or configure LDAP.

For information about SSL configuration, adding a member to a cluster, orchanging ports, see the IBM OpenPages GRC Platform Administrator's Guide.

Configuring OpenPages to work on a single computerFor test and development environments, you can install IBM OpenPages GRCPlatform, Oracle database, the 32-bit Oracle Client, and Cognos BusinessIntelligence on a single computer. However, some configuration is required.

About this task

You can install the IBMOpenPages GRC Platform on a single computer as forpredeployment testing or proof of concept demonstrations. For single computerinstallations, ensure that the correct Oracle Client is used by each softwarecomponent.

If you install OpenPages GRC Platform on a single server, you must install twoversions of Oracle Client. Both the 32-bit and 64-bit versions are required. TheOpenPages application requires the 64-bit Oracle Client and the Cognos BusinessIntelligence Software requires the 32-bit Oracle Client.

Procedure1. Log on to the CommandCenter server as a user with administrative privileges.2. Ensure that the ORACLE_HOME environment variable points to the 32-bit

Oracle Client.3. Edit the PATH variable to add %ORACLE_HOME%\bin.4. If set, remove the TNS_ADMIN variable.5. From the command line, go to the OP_Home\CommandCenter\framework\conf\

directory.6. Open the framework.properties file in a text editor and ensure that the

oracle.client.path property contains the location of the 32-bit Oracle clientbin directory.

7. Save and close the file.8. Restart the CommandCenter service.

77

Verification checklistAfter installing the OpenPages application, verify that the installation is workingas expected.

Use the following checklist to verify whether the installation is successful.

Table 52. Post-installation verification checklist

Task Guidance

Review all installation logs for errors.For log file locations and names, see“Installation log files” on page 147.

Verify that the database parameters arecorrect.

Review the database parameters, such asCharacter set=AL32UTF8 andNLS_LENGTH_SEMANTICS=CHAR, to ensure that theyare correct.

Verify that a backup copy of the systemwas made after installing.

If it does not exist, create a backup of yoursystem by running the OPBackup command fromOP_HOME\aurora\bin directory.

Verify that a compressed file was created withthe correct timestamp. The file is in theOP_Home\openpages-backup-restore directory.

For information about on using the backuputility, see the IBM OpenPages GRC PlatformAdministrator's Guide.

Confirm that the reporting schema andframework generated successfully.

For more information, see “Creating thereporting schema and framework” on page 72.

Confirm that base reports are functioningas expected.

Log on to the OpenPages application and runthe All Documentation CommandCenter report.

If single signon (SSO) is enabled, verifythat user accounts can access theenvironment.

Log on to the OpenPages application with anSSO user account.

If you use TeamMate, confirm that theTeamMate loader-files are implementedand working.

Test the integration from the TeamMate client.

Confirm that you can upload anddownload sample attachments.

Log on to the OpenPages application andupload and download a file attachment.

Verify that links in reports reference thecorrect server address and use the correctweb URL parameters.

Run a report that uses OpenPages links. Select alink and confirm that the target object isrendered successfully in the OpenPagesinterface.

For clustered environments, verify thatall servers can upload and downloadattachments.

Upload and download files from both primaryand secondary application servers.


Table 52. Post-installation verification checklist (continued)

Task Guidance

For load-balanced environments, confirmthat backup scheduling is working.

Ensure that services on secondary serversare stopped before backing up theprimary server. Ensure that services arestarted post 7001 (port) availability onthe primary server.

On primary and secondary servers, verifybackup scheduling and process times.

Test that you can access the IBM CognosBusiness Intelligence portal.

Type the following web URL:

http://server_name/ibmcognos

Confirm that you can log on to the portal.

Confirm that you ran theenable-session-sleep.sql script.

For more information, see “Preventingconcurrency conflicts” on page 84.

After backup, confirm that object data iscreated.

Log on to the OpenPages application and createsample Entity, Process, and Risk objects. Deletethese objects.

Related concepts:“Installation log files” on page 147The installation programs write errors and other information to the log files. Uselog files to troubleshoot problems.

Fix pack installationsIBM provides interim maintenance packages that contain updates to one or morecomponents in your IBM product. If a fix pack is available when you are installingor upgrading, install it after you install the IBM OpenPages GRC Platform.

If a fix pack becomes available after you deploy OpenPages applications:1. Stop all services.2. Backup content and directory structures.3. Install the fix pack in the same location as existing components.4. Restart services

Fix packs are cumulative. When you install the latest fix pack, it includes updatesfrom all the previous fix packs.

Fix packs are available for download from IBM Support (http://www.ibm.com/support/us/en).

Note: Fix packs are not stand-alone installations. You must install them oncomputers that have IBM OpenPages components installed. Install the fix packsthat are appropriate for your product version.

Database server tuningTo improve performance, tune the Oracle database. You must change some ofdefault values for Oracle server parameters. Other changes are suggested inenvironments where there are heavy user loads.

Chapter 8. Post installation tasks 79

http://www.ibm.com/support/us/en/

Tuning the performance of the database instanceTo improve the performance of the Oracle database instance, disable the Oracleskip scan and set cursor sharing to force.

The Oracle skip scan feature splits a composite index logically into smallersubindexes. In skip scanning, the initial column of the composite index is notspecified in the query. In other words, it is skipped. For larger databases where thedata changes frequently, skip scanning can be less efficient than a range scan.

The cursor sharing feature specifies how SQL statements are parsed. Issuingmany SQL statements that have literal values can result in many nearly identicalstatements in the cache. The large result set can slow performance and cause latchproblems. Setting cursor sharing to force causes the SQL statements to be reusedif the text is similar except for the literal value.

Procedure1. Log on to a computer with SQL*Plus and access to the database server.

Note: For AIX installations, use opuser user or another non-root user.2. From the command-line, log on to SQL*Plus.

sqlplus sys/sys_password@SID as sysdba

3. At the SQL prompt, type the following command:alter system set "_optimizer_skip_scan_enabled"=false scope=both;alter system set cursor_sharing = force scope=both;

4. Log out from SQL*Plus.

Memory tuning guidelines for Oracle databasesIf your application is running in a heavy-load environment, consider allocating asmuch memory as possible to the Oracle database instance.

The following table provides general guidelines for memory allocation on a systemwith 4 GB of RAM or more.

Table 53. Memory Tuning Guidelines

For this... Allocate...

Operating system 1 - 4 GB of physical RAM

SGA Size 75% of remaining physical RAM to the SGA_TARGETparameter.

Minimum allocation: 2048 MB (or 2 GB)

PGA Size 25% of remaining physical RAM to thePGA_AGGREGATE_TARGET parameter.

Minimum allocation: 1024 MB (or 1 GB)

Example 1: Computer with 4 GB of RAM

If a computer has 4 GB of physical RAM:v SGA (2 GB) and PGA (1 GB)v 1 GB is available for the Windows OS


Example 2: Computer with 8 GB of RAM

If a computer has 8 GB of physical RAM and you want 2 GB available for theWindows OS, then 6 GB remains for allocation to Oracle. The remaining 6 GB canbe allocated to a single database instance:v SGA: 4608 MB (or 4.5 GB, which is 75% of 6 GB)v PGA: 1536 MB (or 1.5 GB, which is 25% of 6 GB)

Example 3: Computer with multiple database instances

Note: If you are planning to run multiple database instances on the samecomputer, adjust the memory to ensure that concurrently running instances fit intothe available physical RAM. Using physical memory avoids swapping to disk.

For example, to run the OpenPages Repository and CommandCenter Repositoryservices on the same computer with 8 GB of RAM:v 1 GB of RAM for the OSv The remaining 7GB of RAM can 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

Admin server tuningYou can tune your admin server settings to improve performance.

Configuring the database connection pool on Windowscomputers

The OpenPages and workflow servers each have a pool of JDBC connections thatcan be used by applications when connecting to the database. You must configurethe number of available connections in the pool. Depending on your situation, useyour previous settings or the number of named users as a guideline. Theseconnections are returned to the connection pool when the application disconnectsfrom the database.

Procedure1. Open a web browser.2. Enter the URL for the Oracle WebLogic Administration Console for the

OpenPages server:http://OP_server_name:port/console

The WebLogic Server port is assigned during installation. By default the portused is 7001.

Note: Do not use localhost for the OP_server_name.3. Log on to the WebLogic Administration Console as with an administrator

account.4. In the Domain Structure section, click Services > JDBC.5. In the Change Center, click Lock & Edit to make the settings available for

editing.6. On the Summary of Services page, click Data Sources.7. On the Summary of JDBC Data Sources page, click OpenPages Data Source.


8. On the Settings for OpenPages Data Source page, click General >Connection Pool.

9. Enter a values for the Initial Capacity and Maximum Capacity fields.By default, these values are set to 75. For an upgrade installation, use thevalue that was set in your previous system.

10. Click Save.11. In the Change Center, click Activate Changes to implement the changes.12. Log out of the Oracle WebLogic Administration Console.13. Navigate to the Oracle WebLogic Administration Console for the workflow

server:http://workflow_server_name:port/console

The WebLogic Server port is assigned during installation. By default, the valueis 49901.

Note: Do not use localhost for the workflow_server_name.14. Repeat steps 3-12 for the workflow server computer.

Configuring the database connection pool on AIX computersThe OpenPages and workflow servers each have a pool of JDBC connections thatcan be used by applications when connecting to the database. You must configurethe number of available connections in the pool. Depending on your situation, useyour previous settings or the number of named users as a guideline. Theseconnections are returned to the connection pool when the application disconnectsfrom the database.

Procedure1. Open a web browser.2. Enter the following URL to go to the IBM Integrated Solutions Console for the

OpenPages server.http://OP_server_name:port/ibm/console/

The port is assigned during installation. By default the port used is 9060.

Note: Do not use localhost for the OP_server_name.3. Expand Resources > JDBC.4. Click Data sources from 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.7. On the Connection Pools page, enter a value for the Maximum connections

and Minimum connections.The default value for Maximum connections is 75 and for Minimumconnections is 1.For an upgrade installations, enter the value set in your previous system

8. Click Apply.9. To commit the changes to the master configuration, in the Messages box, click

Save and then click OK.10. Log out of the Integrated Solutions Console.11. Navigate to Integrated Solutions Console for the workflow server

http://workflow_server_name:port/ibm/console/



Note: Do not use localhost for the workflow_server_name.12. Repeat steps 3-10 to configure the database connection pool for the workflow

server.

Enabling simultaneous access to OpenPages applications andFujitsu Interstage BPM for a single user on AIX computers

By default, the IBM WebSphere Application Server does not allow a single user tolog on to the OpenPages application and the Fujitsu Interstage BPM consoleconcurrently. Some configuration is required to enable simultaneous access by thesame user to both applications.

Procedure

For OpenPages applications:1. Open a web browser.2. Enter the following URL in the IBM Integrated Solutions Console for the

OpenPages server.http://OP_server_name:port/ibm/console/


Note: Do not use localhost for the OP_server_name.3. Expand Servers > Server Types.4. Click WebSphere application servers from the list.5. On the Application servers page, 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.c. Under Container Settings, expand Web Container Settings and then click

Web container.d. On the Web Container page, click Session management.e. Under Session tracking mechanism, click Enable cookies.f. On the Cookies page, enter opsosa in the Cookie name field.g. Click Apply.h. To commit the changes to the master configuration, in the Messages box,

click Save.i. Click OK to exit.

For Fujitsu Interstage BPM:6. Open a web browser.7. Type the following URL:

http://OP_server_name:port/ibm/console/

8. Expand Servers > Server Types.9. Click WebSphere application servers from the list.

10. On the Application servers page, for each OpenPages server listed:a. On the OpenPages-server-name page, click the Configuration tab.b. Under Container Settings, expand Web Container Settings and then click

Web container.c. On the Web Container page, click Session management.


d. Under Session tracking mechanism, click Enable cookies.e. On the Cookies page, enter opibpm in the Cookie name field.f. Click Apply.g. To commit the changes to the master configuration, in the Messages box,

click Save.h. Click OK to exit.

Preventing concurrency conflictsIf two administrators both try to modify settings at the same time, errors mightoccur. To help avoid concurrency errors, run the SQL enable-session-sleep.sqlscript.

A concurrency conflict might result in the following error message:Operation failed, security settings are beingconcurrently modified by another administrator.Please try again later.

Procedure1. On a computer that has SQL*Plus and access to the database server, log on as a

user with SYSDBA permissions.2. From the Installer DVD or from your network share location, copy the

/OP_version_Configuration/Database/ORACLE/INSTALL_SCRIPTS directory to thelocal system.

3. Run the enable-session-sleep.sql script.On a command line, use the following syntax:sqlplus /nolog @sql-wrapper enable-session-sleep.sql <log_file_name><connect_identifier> <sysdba_user_name><sysdba_user_password> <schema_owner_name>

Example:sqlplus /nolog @sql-wrapper enable-session-sleep.sql enable-session-sleep.logopx10g sys manager openpages

If the process completes successfully, a message is displayed.If the script fails, check the log files for error messages.

Optional: Increasing the paging file size on Windowscomputers

On computers that have 4 GB of RAM, the suggested paging file size is 8 GB.

Procedure1. Click Start > Run and then type sysdm.cpl, and press Enter.2. Click the Advanced tab, then in the Performance section, click Settings.3. In the Performance Options dialog box, in the Virtual Memory section, click

the Advanced tab, and then click Change.4. Find the list of drives and select the drive that contains your paging file.

Note: If necessary, clear the Automatically manage page file size for alldrives box.

5. Under Paging File Size, select Custom Size.6. Reset both the Initial Size and Maximum Size values to higher values.7. Click Set.


8. Click OK to close the three open dialog boxes.

Optional: Increasing the paging file size on AIX computersOn computers that have 4 GB of RAM, the suggested paging file size is 8 GB.

Procedure1. On AIX computers, open a shell as user with administrative privileges.2. Type the following command to change the attributes of the paging space:

chps -s LogicalPartitions <PagingSpace_Name>

For example, the following command adds four logical partitions to the pgspcepaging space:chps -s 4 pgspce

Increasing the Oracle WebLogic Maximum Message SizeThe workflow server might send log messages that exceed the default size that isconfigured for WebLogic Server. A workflow message that exceeds the maximumsize can cause the workflow service to stop working. To avoid this issue, increasethe WebLogic Server maximum message.

Procedure1. Verify that the workflow InterstageBPMAdminServer service is running.2. Open a web browser and log on to the Oracle WebLogic Server Admin

Console as a user with admin privileges.http://workflow_server_name:49901/console

3. In the Change Center pane of the Console, click Lock & Edit.4. In the Domain Structure pane, expand the Environment > Servers.5. On the Summary of Servers page, click the Configuration tab, and from the

servers list, click the name of the workflow server.6. On the page for server settings, click Protocols.7. Under the General tab, change the Maximum Message Size setting to

2000000000 and click Save.8. For each additional workflow managed servers, repeat steps 5-7.9. When finished, to implement the changes, in the Change Center, click

Activate Changes.10. Log out of the Oracle WebLogic Server Admin Console.

You are not required to restart services.

OpenPages application server tuningYou can tune application server settings to control how the application serverprovides services for running applications and their components. Each applicationserver instance contains interrelated components that must be properly tuned tosupport the specific needs of your application.

Enabling LDAPIf you are installing OpenPages GRC Platform into an environment that usesLDAP environment, you must enable LDAP. The Openpages module in the LDAPconfiguration file, aurora_auth.config, determines whether LDAP is enabled. Ifyou have a load-balanced system, disable LDAP on the primary and secondaryservers.



privileges.2. Use your LDAP Directory Server to add users who require access to the

OpenPages application or to the OpenPages environment to the LDAPauthentication server.For more information about the steps required to add OpenPages users to theLDAP server, see your LDAP Directory Server.

3. Log on to the OpenPages application and create the same users.4. Stop all OpenPages services.5. Go to the directory where you copied the aurora_auth.config file.6. Open the LDAP configuration file, aurora_auth.config, in a text editor.7. Rename the Openpages module to something different, such as

Openpages_default..8. Depending on your LDAP server, rename the LDAP modules to Openpages

v If you are using a Microsoft Active Directory server, change the OpenpagesADmodule name to Openpages.

v If you are using a Sun One Directory Server, change the OpenpagesIPmodule name to Openpages.

9. Specify the correct values for the following properties in the appropriatemodule:

Table 54. Property settings and description

Property Description

provider.url IP address and port number of the LDAPauthentication server, in the<protocol>://<ip_address>:<port> format.Note: If you are configuring LDAP over SSL(LDAPS), the protocol is ldaps and the portis the LDAPS port.

security.search.user.dn The fully qualified name of anadministrative user on the LDAP server.

security.search.user.credentials The password for the specified user

base.dn The top level of the LDAP directory treestructure (Domain Name) on the LDAPserver.

If the users to be authenticated are inmultiple locations within your ActiveDirectory structure, list all locationsexplicitly. Use the distinguished names ofthe locations, each separated by asemi-colon.

user.attr.id The attribute name of the user identifier.

Typically a common name (CN), uid, orsAMAccountName.

For example, Openpages_default{com.openpages.aurora.service.security.namespace.AuroraLoginModulerequired debug=false;};


Openpages{com.openpages.aurora.service.security.namespace.LDAPLoginModulerequired debug=falseprovider.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 on to the OpenPages application and change the OpenPages

Administrator password to openpages.12. Restart all OpenPages services.13. Log on to the OpenPages application as one of the users that you created in

the LDAP Directory Server.

Disabling LDAPIf LDAP is enabled on your system, the default Openpages module was renamed.Either the OpenpagesIP or OpenpagesAD was renamed to Openpages. To disableLDAP, change the name of the current Openpages module and change the name ofthe default Openpages module back to Openpages.

Procedure1. Log on to the application server as a user with administrative privileges.2. Stop all OpenPages services.3. Go to the directory where you copied the aurora_auth.config file.

OP_HOME\aurora\conf

4. Open the LDAP configuration file, aurora_auth.config, in a text editor.5. Change the name of the Openpages_default module back to Openpages.6. Change the name of the current Openpages module to something different.7. Save and close the file.

Accessing OpenPagesTo view the application login page for your installation, type the OpenPages URLinto your web browser.

For default installations, type the following URL in your web browser:


If you are using an SSL connection to access the OpenPages application, you musthave an SSL digital certificate. After configuration, type the following URL in yourweb browser:

https://openpages_server:ssl_port/openpages



Chapter 9. Starting and stopping OpenPages servers

Use Windows services or AIX scripts to start and stop the IBM OpenPages GRCPlatform servers. The OpenPages application runs only if all of the services arestarted and all of the services for all supporting applications are running. To startor stop the OpenPages application, you must start or stop the services or scripts inthe correct sequence.

Windows services and AIX scripts

In a Windows environment, you can configure the OpenPages services required tostart automatically. In an AIX environment, manually run scripts to start theOpenPages application servers.

Sequence of starting servers

You must start the OpenPagesAdminServer service on Windows computers, or runthe OpenPages startManager script on AIX computers first. Then start the otherservices or run the other scripts.

If you are running OpenPages in a load-balanced environment, you must start theserver on the cluster administrator first.

Initial startup time

The first time you start the OpenPages server, it precompiles all of the includedJavaServer Pages (JSP). This initialization process can take several minutes tocomplete. Future startup times take much less time.

Windows services used by OpenPages applicationsMany Windows services are associated with the OpenPages application and FujitsuInterstage BPM Services servers. After a service is installed, it can be managedfrom the Windows Control Panel.

The following table lists Windows services associated with the OpenPagesapplication and workflow servers.

Table 55. OpenPages application and Fujitsu Interstage BPM services on Windowscomputers

Service Name Description

OpenPagesAdminServer Starts or stops the OpenPages Adminservice.Note: In a horizontal-cluster environment,cluster members do not have an OpenPagesAdmin service.

89

Table 55. OpenPages application and Fujitsu Interstage BPM services on Windowscomputers (continued)

Service Name Description

OpenPagesServer# Starts or stops an OpenPages managedserver.

# represents the number of the managedserver.

In a cluster environment, the number foreach managed server increments by one.

InterstageBPMAdminServer Starts or stops the Fujitsu Interstage BPMDeployment Manager service.

InterstageBPMCS# Starts or stops the Fujitsu Interstage BPMapplication server.

# represents the number of the managedserver.

In a cluster environment, the number foreach managed server increments by one.

Starting OpenPages application servers on Windowscomputers

By default, all OpenPages and Fujitsu Interstage BPM services are configured tostart manually. If you restart your computer, you must restart the OpenPagesservers.

You can configure all OpenPages and Fujitsu Interstage BPM services to startautomatically. Use Windows Services or use scripts to start the services on eachserver when you restart the computer.

Procedure1. To use the Windows Start menu to start or stop all OpenPages servers on the

current system:a. Log on to the OpenPages application server as a user with administrative

privileges.b. Click Start > IBM OpenPages version > Manage OpenPages Server > Start

All OpenPages Servers.2. To start the services individually, in the Windows Administrative > Tool

Services, right-click each service in the following order and select Start:v OpenPagesAdminServer (if present).v OpenPagesServer#.

If there is more than one managed server, start the OpenPagesServer# servicefor each managed server in sequence before starting Fujitsu Interstage BPMservices.

v InterstageBPMAdminServer (if present).v InterstageBPMCS#.

Note: # represents the number of the managed server.You restart the services in the reverse order that you started them.


3. To use the StartAllServers.cmd script to start all services in the correctsequence:a. Log on to the OpenPages application server as a user with administrative

privileges.b. Using Run as Administrator, open a Command Prompt window and go to

the OP_Home\bin directory.c. Run the StartAllServers.cmd script.

When all services are started, the Command Prompt window closes.

Results

As services start, Windows Services might indicate that the services are started.However, background OpenPages processes might be running. It might take a fewminutes for the OpenPages service to be operational.

Stopping OpenPages application servers on Windowscomputers

You can configure all OpenPages and Fujitsu Interstage BPM services to stopautomatically, or you can stop the services manually. If you are runningOpenPages in a load-balanced environment, you must stop the server on eachcluster member first before stopping the cluster.

Important: Stopping the OpenPages Admin service before stopping each managedserver causes the OpenPages application to stop on all servers. Stopping theOpenPages Admin service first can result in the loss of data.

Procedure1. To use the Windows Start menu to start stop all OpenPages servers on the

current system:a. Log on to the OpenPages application server as a user with administrative

privileges.b. Click Start > IBM OpenPages version > Stop All OpenPages Servers.

2. To stop the services individually, in the Windows Administrative > ToolServices, right-click each service in the order listed below and select Stop.In the following list, the number sign (#) represents the number of the managedserver.v InterstageBPMCS#v InterstageBPMAdminServer (if present)v OpenPagesServer#v OpenPagesAdminServer (if present)If there is more than one managed server on the current system, stop theOpenPagesServer# service for each managed server before stopping theOpenPagesAdminServer service. You can stop the managed servers in anyorder.You stop the services in the reverse order that you started them.

3. To use the StopAllServers.cmd script to stop all services in the correctsequence, do the following steps:a. Log on to the OpenPages application server as a user with administrative

privileges.b. Using Run as Administrator, open a Command Prompt window and go to

the OP_Home\bin directory.

Chapter 9. Starting and stopping OpenPages servers 91

c. Run the StopAllServers.cmd script.When all services are started, the Command Prompt window closes.

AIX scripts used to start and stop OpenPages application serversIn AIX environments, OpenPages includes a number of scripts to start and stopOpenPages application servers.

Note: You can run these scripts individually or combine them in another script.

The following table lists the scripts required to start and stop the OpenPagesapplication.

Table 56. Scripts to start and stop OpenPages application servers and Fujitsu InterstageBPM servers on AIX computers

Script Name Description

startManager.sh Starts the Fujitsu Interstage BPMDeployment Manager.

startNode.sh Starts the Fujitsu Interstage BPM node agent.

startServer.sh Starts the Fujitsu Interstage BPM applicationserver.

stopManager.sh Stops the Fujitsu Interstage BPMDeployment Manager.

stopNode.sh Stops the Fujitsu Interstage BPM node agent.

stopServer.sh Stops the Fujitsu Interstage BPM applicationserver.

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.

startAllServers.sh Starts all OpenPages and Fujitsu InterstageBPM services in the correct sequence.

stopAllServers.sh Stops all OpenPages and Fujitsu InterstageBPM services in the correct sequence.

Related tasks:“Removing files on AIX computers after an incomplete Installation” on page 149If the OpenPages installer does not complete, files and directories might remain.These files prevent the installation program from running again. If the uninstallutility is not in the OP_Home\OpenPages\Uninstall directory, you must manuallyremove these files.

Starting OpenPages application servers on AIX computersUse the startAllServers.sh script to start all OpenPages and Fujitsu InterstageBPM services in the correct sequence. You can also start the services individually.



privileges.2. Open a shell.3. To use one script to start the services, do the following steps:

a. Go to the OP_Home/bin directory.b. To stop all the services, run the ./stopAllServers.shscript.

4. To stop the OpenPages application servers individually, do the following steps:a. Go to the OP_Home/profiles/OpenPagesDmgr/bin directory.b. To start the OpenPages Deployment Manager, run the ./startManager.sh

script.c. After the script completes, go to the OP_Home/profiles/OpenPagesNode1/bin

directory, and run the following scripts:v ./startNode.sh

v ./startServer.sh <OPNode#><Server#>

OPNode# is the node of the current server. <Server#> is the number of theserver within that node. For example, OPNode1Server1.

d. After the script completes successfully, go to the app_server_root/Profiles/IBPMDmgr/bin directory, and run the following scripts to start the IBPMNode Agent and the IBPM application server:v ./startNode.sh

v ./startServer.sh <IBPMNode#>server

<IBPMNode#> is the node of the current server. Do not specify a servernumber. Only one server exists for each Fujitsu Interstage BPM node. Forexample, IBPMNode1server.

Stopping OpenPages application servers on AIX computersUse the stopAllServers.sh script to stop all OpenPages and Fujitsu InterstageBPM services in the correct sequence. You can also stop the services individually.


privileges.2. Open a shell.3. To use one script to stop the services, do the following steps:

a. Go to the OP_Home/bin directory.b. To start all the services, run the ./startAllServers.sh script.c. To stop all the services, run the ./stopAllServers.sh script.

4. To stop the OpenPages application servers individually, do the following steps:a. Go to the app_server_rootProfiles/IBPMDmgr/bin directory, and run the

following scripts to stop the IBPM Node Agent and the IBPM applicationserver:v ./stopServer.sh <IBPMNode#>Server

v ./stopNode.sh

<IBPMNode#>is the node of the current server. Do not specify a servernumber. Only one server exists for each Fujitsu Interstage BPM node. Forexample, IBPMNode1server.

b. Go to the OP_Home/profiles/OpenPagesDmgr/bin directory.

Chapter 9. Starting and stopping OpenPages servers 93

c. To stop the OpenPages Deployment Manager, run the ./stopManager.shscript.

d. After the script completes, go to the OP_Home/profiles/OpenPagesNode1/bindirectory, and run the following scripts:v ./stopServer.sh <OPNode#><Server#>

v ./stopNode.sh

OPNode# is the node of the current server. Server# is the number of theserver within that node. For example, OPNode1Server1.


Chapter 10. Configuring clustered environments

To accommodate increased user loads, scale horizontally or vertically by addingnodes to the OpenPages environment. When you scale, load balancing is requiredto distribute the incoming requests across the nodes.

A node consists of an instance of the OpenPages application server and acorresponding instance of the workflow server. Each node runs on a different port.

You can also scale the CommandCenter, the OpenPages reporting server, verticallyor horizontally.

Scaling the reporting server vertically

Scaling vertically increases the number of processes that are available to handlerequests. Depending on the load, scaling vertically might involve configuringadditional dispatchers

Scaling the reporting server horizontally

Scaling horizontally requires that you install additional report servers. Configurethe additional Cognos dispatchers to ensure that the incoming requests aredistributed across the multiple servers.

Load balancing configurations

To create a clustered OpenPages environment, install and configure eachOpenPages and CommandCenter instance as a stand-alone system. Then, configureeach system for load balancing.

You can deploy a hardware or software load balancer. The load balancer mustsupport session affinity and port-based URL routing.

Install the load balancer on the OpenPages application server or on an externalsystem.

Configuring an OpenPages cluster to run as a Windows operatingsystem service

You can configure an OpenPages and workflow cluster on WebSphere ApplicationServer to run as services on the Windows operating system. When WebSphereApplication Server clusters run as a service, the cluster automatically restarts aftera failure. Also, cluster member processes remain active after you log out from yourMicrosoft Windows system account.

Procedure1. On the OpenPages administrative server, log on as an administrator.2. Click Start > All Programs > Accessories, and right-click Command Prompt >

Run as Administrator.3. From the command prompt, go to the WAS_HOME\bin directory, and run the

following command:

95

wasservice -add OpenPagesDmgr -servername dmgr -profilePath"<OP_HOME>\profiles\OpenPagesDmgr" -wasHome"<WAS_HOME>" -logFile"<OP_HOME>\profiles\OpenPagesDmgr\logs\dmgr\startServer.log"-logRoot "<OP_HOME>\profiles\OpenPagesDmgr\logs\dmgr

4. Run the following command:wasservice -add <HOST_NAME>-OPNode1 -servername nodeagent -profilePath"<OP_HOME>\profiles\<HOST_NAME>-OPNode1"-wasHome "<WAS_HOME>" -logFile"<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\nodeagent\startServer.log"-logRoot "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\nodeagent

5. On each OpenPages application server, run the following command:wasservice -add <HOST_NAME>-OPNode1Server<SERVER#> -servername<HOST_NAME>-OPNode1Server<SERVER#> -profilePath"<OP_HOME>\profiles\<HOST_NAME>-OPNode1" -wasHome"<WAS_HOME>" -logFile "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\<HOST_NAME>-OPNode1Server<SERVER#>\startServer.log"-logRoot "<OP_HOME>\profiles\<HOST_NAME>-OPNode1\logs\<HOST_NAME>-OPNode1Server<SERVER#>

6. Run the following command:wasservice -add IBPMDmgr -servername dmgr -profilePath"<WORKFLOW_HOME>\profiles\IBPMDmgr" -wasHome"<WAS_HOME>" -logFile"<WORKFLOW_HOME>\profiles\IBPMDmgr\logs\dmgr\startServer.log"-logRoot "<WORKFLOW_HOME>\profiles\IBPMDmgr\logs\dmgr

7. Run the following command:wasservice -add <HOST_NAME>-IBPMNode<SERVER#>-servername nodeagent -profilePath"<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>"-wasHome "<WAS_HOME>" -logFile"<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\nodeagent\startServer.log" -logRoot"<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\nodeagent"

8. Run the following command:wasservice -add <HOST_NAME>-IBPMNode<SERVER#>Server -servername<HOST_NAME>-IBPMNode<SERVER#>Server -profilePath"<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>"-wasHome "<WAS_HOME>" -logFile"<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\<HOST_NAME>-IBPMNode<SERVER#>Server\startServer.log"-logRoot "<WORKFLOW_HOME>\profiles\<HOST_NAME>-IBPMNode<SERVER#>\logs\<HOST_NAME>-IBPMNode<SERVER#>Server"

9. Repeat steps 7 and 8 on each workflow server.

Removing Windows operating system services for OpenPagesand workflow servers

To remove OpenPages and workflow clusters that run as a service, use thecommand prompt window to run commands on each server.

Procedure1. On the OpenPages administrative server, log on as an administrator.2. Click Start > All Programs > Accessories, and right-click Command Prompt >

Run as Administrator.3. From the command prompt, go to the WAS_HOME\bin directory, and run the

following command:wasservice -remove OpenPagesDmgr

4. Run the following command:


wasservice -remove <HOST_NAME>-OPNode1

5. Run the following command for each OpenPages server:wasservice -remove <HOST_NAME>-OPNode1Server<SERVER#>

6. Run the following command:wasservice -remove IBPMDmgr

7. Run the following command:wasservice -remove <HOST_NAME>-IBPMNode<SERVER#>

8. Run the following command:wasservice -remove <HOST_NAME>-IBPMNode<SERVER#>Server

9. Repeat steps 6 and 7 on each workflow server.

Clustered OpenPages ConfigurationsSome configuration tasks are required for clustered OpenPages environments.

Increasing the Oracle connection limitIn clustered environments, you must increase the number of users who canconnect to the database instance.

Procedure1. Log on to the database server as a user with administrative privileges.2. To start the Oracle Enterprise Manager console, open a web browser and enter

https://server_name:1158/em

3. Log on to the Oracle Enterprise Manager console by using the followingsyntax: sys/[email protected]. For the User Name, enter sys.b. Enter the password for the sys user.c. From the Connect As list, select SYSDBA.

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 fieldand then clicking Go.

8. Enter a value in the Processes field.In a clustered environment, for best performance allocate sufficient processesfor each OpenPages application instance, each corresponding FujitsuInterstage BPM instance, and each corresponding CommandCenter instance.For a two-node OpenPages environment, use the following settings:

OpenPagesConfigure 75 processes for each OpenPages instance.

Workflow serverConfigure 35 processes for each associated workflow server.

CommandCenterConfigure 80 processes for each CommandCenter instance.

Database processing usageConfigure 60 processes for database connection processing andbackground processes.

Chapter 10. Configuring clustered environments 97

By default, this setting is 250 processes and 280 sessions for atwo-node OpenPages environment. If you have two or moreapplication servers, increase the number of processes.

9. Click Apply.You are prompted to restart the server.

10. To restart the server, select Immediate.

Configuring OpenPages applications to use a domain accounton Windows operating systems

In a clustered environment, the OpenPages application services access a file share.The account that starts the services must have permissions to the file share.

About this task

By default, on Windows operating systems, services run under the LocalSystemaccount. This account cannot access a shared drive on another computer. In ahorizontal cluster, configure the OpenPages application services on all applicationservers to run under a domain account that has access the shared drive.

The following OpenPages application services must have permissions to the fileshare:v OpenPagesAdminServerv OpenPagesServer#v IBPMAdminServerv InterstageBPMCS#

Procedure1. Log on to each 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, right-click the service name, and select

Properties from the menu.a. In the Properties dialog box, click the Log On tab.b. Select This account.c. Type a domain, account name, and password for at least one user who has

access to the shared drive.d. Click OK to continue.

Configuring file share permissions on AIX operating systemsFor clustered OpenPages environments that run on AIX operating systems,configure the same user name and password on all systems. File share permissionsare the same on all systems. If you are using a network file share (NFS), ensurethat users have read and write access to the file share.

Sharing a network OpenPages storage directory on Windowsoperating systems

The OpenPages application installation includes a pointer to the OpenPagesstorage location. The storage location is a directory where attached files and formsthat are associated with OpenPages objects are stored.


If you pointed to a location on the local computer, you must change the pointer toa shared network storage location. You can use the update-storage script tochange the storage directory to a shared directory on the same or another server.

If you specified a shared network storage location, this task is not required.

Before you begin

For installations that use an Oracle database, ensure that the SQL Plus utility isavailable on the managed application server.

Procedure1. Log on to a managed application server as a user with administrative privileges

and full access to the local server drives.2. Open a Command Prompt window.3. Copy the OP_version_Configuration directory from the Installer DVD or on

your network share location to the local system.4. Copy the INSTALL_SCRIPTS directory to the local system.

v For Oracle databases, go to the OP_version_Configuration\Database\ORACLEdirectory.

5. For Oracle databases, go to the ORACLE\INSTALL SCRIPTS directory and run theupdate-storage script:sqlplus /nolog @sql-wrapper.sql update-storage.sql log_file_name TNS_alias_nameOpenPages_schema_owner_name OpenPages_schema_owner_passwordstorage_type storage_server_name computer_nameOpenPages_storage_platform sharename

The following table lists the command-line parameters that must be passed tothe SQL wrapper script.

Table 57. Update storage wrapper script parameters for Oracle database

Variable name Description

log_file_name The location of the log file that is created by the script.

If a location is not specified, the log file is created inthe current working directory.

If a log with the same name exists in the same location,the log is overwritten by the script.

TNS_alias_name The database connection identifier, such as TNS aliasname.

OpenPages_schema_owner_name The name of the OpenPages user, created during theOpenPages application installation.

By default, openpages.

OpenPages_schema_owner_password The password of the OpenPages user.

storage_type Enter either LFS for local file system, or UNC forUniversal Naming Convention or Uniform NamingConvention.

storage_server_name The name of the server where the OpenPages storage islocated.

computer_name The name of the cluster administrator computer.


Table 57. Update storage wrapper script parameters for Oracle database (continued)


OpenPages_storage_platform The operating system on the server where theOpenPages storage is located.

Enter Windows.

sharename The name of the shared OpenPages storage directory orthe mount point.

By default, openpages-storage

Sharing a network OpenPages storage directory on AIXoperating systems

The OpenPages application installation includes a pointer to the OpenPagesstorage location. The storage location is a directory where attached files and formsthat are associated with OpenPages objects are stored.

If you pointed to a location on the local computer, you must change the pointer toa shared network storage location. You can use the update-storage script tochange the storage directory to a shared directory on the same or another server.

If you specified a shared network storage location, this task is not required.

Procedure1. Mount the storage folder on the admin server to the non-admin server.

a. Log on to the OpenPages managed server as the root user or a user thatbelongs to the System group, and open a shell.

b. Go to the /etc directory, and open the hosts file in a text editor.c. Add the IP address and name of each OpenPages managed server.d. Save and close the hosts file.e. Create a file with the name exports in the /etc folder.

Important: Ensure that you have full rights to the local installationdirectory.

f. Open the exports file in a text editor and add the full path to the storagefolder./opt/OpenPages/openpages-storage

g. Export all file systems that are named in /etc/exports directory by usingthe following command:exportfs -a

The exportfs command maintains the current table of exported file systemsfor NFS in the /var/lib/nfs/etc file.

h. Restart the NFS server by using the following commands:stopsrc -g nfsstartsrc -g nfs

The NFS server processes requests from the NFS clients.i. Use following command to check that the openpages-storage folder is

exported and ready for mounting:showmount -e

Ensure that the openpages-storage folder is listed.


2. Mount the storage directory from the admin server on the managed server.a. Log on to the OpenPages managed server as the root user or a user that

belongs to the System group.b. Open a shell as a user with administrative privileges.c. Go to the /etc directory.d. Open the hosts file in a text editor and add the IP address and name of

each OpenPages managed server.e. Save and close the hosts file.f. Run the following command to mount the storage folder:

mount nfsservername mountpoint

v nfsservername is the name of the OpenPages admin server and the locationof the openpages-storage directory on the admin server.

v mountpoint is the name and path of the openpages-storage directory onthe managed server.

Example:mount aix61-1-5.openpages.com:/usr/OpenPages/openpages-storage/usr/OpenPages/openpages-storage

3. For Oracle databases, use the following command to change the storagedirectory that is used by the OpenPages application to a shared directory onthe application server:sqlplus /nolog @sql-wrapper.sql update-storage.sql log_file_name TNS_alias_nameOpenPages_schema_owner_name OpenPages_schema_owner_passwordstorage_type storage_server_name computer_nameOpenPages_storage_platform sharename

The following table lists the command-line parameters that must be passed tothe SQL wrapper script.

Table 58. Update storage wrapper script parameters for Oracle database


log_file_name The location of the log file that is created by the script.

If a location is not specified, the log file is created inthe current working directory.

If a log with the same name exists in the same location,the log is overwritten by the script.

TNS_alias_name The database connection identifier, such as TNS aliasname.

OpenPages_schema_owner_name The name of the OpenPages user, created during theOpenPages application installation.

By default, openpages.

OpenPages_schema_owner_password The password of the OpenPages user.

storage_type Enter either LFS for local file system, or UNC forUniversal Naming Convention or Uniform NamingConvention.

storage_server_name The name of the server where the OpenPages storage islocated.

computer_name The name of the cluster administrator computer.


Table 58. Update storage wrapper script parameters for Oracle database (continued)


OpenPages_storage_platform The operating system on the server where theOpenPages storage is located.

Enter Unix.

sharename The name of the shared OpenPages storage directory orthe mount point.

The default mount point is openpages-storage

Configuring Apache Web Server for load balancing in Windowsenvironment

In a typical configuration that uses Apache Web Server for load balancing onWindows computers, Apache Web Server is installed on a separate computer.

Procedure1. Log on to load-balancing server as a user with administrative privileges.2. Open a Command Prompt window by using the Run as Administrator

option.3. Go to the Apache_Home\conf directory.4. Open the httpd.conf file.

a. To load the required modules, add or uncomment the following lines:LoadModule negotiation_module modules/mod_negotiation.soLoadModule proxy_module modules/mod_proxy.soLoadModule proxy_ajp_module modules/mod_proxy_ajp.soLoadModule proxy_balancer_module modules/mod_proxy_balancer.soLoadModule proxy_connect_module modules/mod_proxy_connect.soLoadModule proxy_http_module modules/mod_proxy_http.soLoadModule status_module modules/mod_status.soLoadModule weblogic_module modules/mod_wl_22.so

b. Change the ServerName=MYSERVERNAME.DOMAIN.COM setting to point to thehost name where you installed the Apache Web Server.ServerName=op-load-balancer.domain.com

c. Change the ServerRoot setting to point to the directory where youinstalled the Apache Web Server.The default setting is ServerRoot=C:/Program Files/Apache SoftwareFoundation/Apache2.2

d. Change all Directory element tags to point to the location of the Apacheweb server installation, and then add the setting "Allow from all" to thetag attributes.<Directory "C:/Apache2.2/htdocs">Options Indexes FollowSymLinksAllowOverride NoneOrder allow,denyAllow from all</Directory>

e. To configure the web server to forward requests to Oracle WebLogicServer, add the following entries to the end of the httpd.conf file.

Note: SERVER.DOMAIN.COM:port is the server name and application portthat hosts the application nodes.


WebLogicPort is the admin server port for the OpenPages or workflowserver.For the <Location /opws> and <Location /openpages> entries, include allOpenPages application nodes in the cluster.For the <Location /ibpmweblogicconsole> entries, include all workflownodes in the cluster.The following example uses a two-node installation with the first node atport 7001, and the second port at 7011.<Location /console>SetHandler weblogic-handlerMaxPostSize 0Debug OnWLLogFile logs/weblogic_console.logWebLogicHost <SERVER>.<DOMAIN>.COMWebLogicPort 7001</Location>

<Location /opws>WLCookieName opappSetHandler weblogic-handlerMaxPostSize 0KeepAliveEnabled ONKeepAliveSecs 15Debug OnWLLogFile logs/openpages_webservices.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT></Location>

<Location /openpages>WLCookieName opappSetHandler weblogic-handlerDynamicServerList ONMaxPostSize 0Debug OnWLLogFile /logs/openpages.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT></Location>

<Location /ibpmconsole>WLCookieName opibpmSetHandler weblogic-handlerDynamicServerList ONMaxPostSize 0Debug OnWLLogFile logs/ibpmconsole.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT></Location>

<Location /ibpmweblogicconsole>SetHandler weblogic-handlerMaxPostSize 0Debug OnWLLogFile logs/ibpmweblogic_console.logWebLogicHost <SERVER>.<DOMAIN>.COMWebLogicPort 49901</Location>

f. To enable monitoring and status of the load balancer, add theExtendedStatus On parameter and setting.


g. To enable monitoring and status of the load balancer, set the location tagsfor server-status and server-info

<Location /server-status>SetHandler server-statusOrder Deny,AllowDeny from allAllow from all</Location>

<Location /server-info>SetHandler server-infoOrder Deny,AllowDeny from allAllow from all</Location>

5. Save and close the file.6. Log on to the OpenPages cluster member, as a user with administrative

privileges.7. Open a Command Prompt window by using the Run as Administrator

option.8. Go to the OP_Home\aurora\conf directory and open the aurora.properties file

in a text editor.a. Edit the application.url.path lines to point to the fully qualified domain

name of the load balancer:application.url.path=http\://top-load-balancer.domain.com\:

port/openpages

b. Save and close the file.9. Open each server_name-OpenPagesServer#-server.properties file in a text

editor.a. Edit the url.path lines to point to the fully qualified domain name of the

load balancer.url.path.workflow.admin=http\://<top-load-balancer.domain.com>

\:<port>/ibpmconsoleurl.path.openpages=http\://<top-load-balancer.domain.com>\:<port>/openpages

b. Save and close each server.properties file.10. Open each server_name-OpenPagesServer#-sosa.properties file in a text

editor.a. Edit the Application.url.path lines to point to the fully qualified domain

name of the load balancer.application.url.path=https\://op-load-balancer.domain.com\:port/openpages

b. Save and close each file.11. Open each server_name-InterstageBPMCS#-server.properties file in a text


load balancer.url.path.workflow.admin=http\://op-load-balancer.domain.com\:

port/ibpmconsoleurl.path.openpages=http\://op-load-balancer.domain.com\:port/openpages

b. Save and close each server.properties file.12. Using the Windows Start menu, start Apache web server in a console

window.


This command opens a console window and starts the Apache Web Serverrunning inside it. Closing this console window terminates the Apache WebServer.

Customizing the load balancer in Windows environments forlarge data sets

For databases with a large data set, some OpenPages reports might timeout beforecompletion. If you experience problems with reports that are timing out, changeconfiguration settings in the Apache Web Server configuration file.

Change the following settings:

TimeOutThe number of seconds Apache waits to receive a GET request, betweenreceipt of TCP packets on a POST or PUT request and between ACKs ontransmissions of TCP packets in responses.

KeepAliveSecsThe number of seconds that idle connections between the plug-in andWebLogic Server are kept open.

KeepAliveTimeoutThe number of seconds Apache waits for a subsequent request beforeclosing the connection.

Note: A high value for the setting can cause performance problems,especially if the higher timeout causes server processes to wait for idleclients.

Procedure1. Log on to load balancing web server as a user with administrative privileges.2. Open a Command Prompt window.3. Open the Apache_Home\conf\httpd.conf file in a text editor4. Add and then set the TimeOut property.

Ensure that the setting prevents timeout errors.For example, TimeOut 1800

5. Change the KeepAliveTimeout property to a higher value.KeepAliveTimeout 1800

6. Find the <Location /opws> parameter and change the value of theKeepAliveSecs setting to a higher value.<Location /opws>WLCookieName opappSetHandler weblogic-handlerMaxPostSize 0KeepAliveEnabled ONKeepAliveSecs 1800Debug OnWLLogFile logs/openpages_webservices.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,

<SERVER>.<DOMAIN>.COM:<PORT></Location>

7. Save and close the file.8. Restart Apache Web Server.


Configuring IBM HTTP Server for load balancing on AIX operatingsystems

In a typical configuration that uses IBM HTTP Server for load balancing on AIXoperating systems, IBM HTTP Server is installed on a separate computer.

Web server plug-ins enable IBM HTTP Server to communicate requests fordynamic content, such as servlets, to the application server. A configuration file isgenerated for each plug-in.

Before you begin

If you are configuring the OpenPages environment for SSL, configure SSL beforeyou configure the plugin-cfg.xml file. For more information, see the IBMOpenPages GRC Platform Administrator's Guide.

Procedure1. Log on to the load-balancing server as a user with administrative privileges.2. Copy the OP_version_Configuration directory from the Installer DVD or on

your network share location to the local system.3. Create the web server instances for the OpenPages application and for the

workflow server.a. Log on to the application server as a non-root user who has administrative

privileges.b. In a web browser, type http://admin_server_name:9060/ibm/console

c. Click Servers > Server Types > Web Servers.d. On the Web Servers page, click New.e. On the Select a node for the Web server page, select the application server

from the Select node list.f. Enter opapp in the Server name field.g. From the Type list, select IBM HTTP Server and click Next.h. On the Confirm new Web server page, review the settings and click Finish.i. In the messages box, click Save to commit the changes to the master

configuration file.j. In a web browser, type http://admin_server_name:9061/ibm/console, and

repeat step 3 to create a web server instance that uses ibpmapp for the servername.

4. To create the plug-in for the OpenPages server instance, open a web browserand type http://admin_server_name:9060/ibm/console.a. Click Servers > Server Types > Web Servers.b. Select the OpenPages server instance that you created and then click

Generate Plugin.The plug-in is created and saved to the $IHS_HOME/Plugins/config/webserver_name/ directory.The webserver_name is the OpenPages server instance that you created.

c. To create the plug-in for the workflow server, In a web browser, typehttp://WAS_server_name:9061/ibm/console

d. Click Servers > Server Types > Web Servers.e. Select the workflow server instance that you created and click Generate

Plugin.


f. Copy both plug-in files to the load-balancing server.5. On the load balancing server, create a text file for the merged file.

a. Open the plugin-cfg.xml files for the OpenPages and workflow servers.b. Copy the <Config> root element from one of the plugin-cfg.xml file and

paste into the new file.

Note: Ensure that there is only one <Config> element in merged file.c. Copy the <Log> element from one of the two files, and if required, modify

the name, and paste into the new file.d. Copy all the <VirtualHostGroup> elements from both files and paste into the

new file.The <VirtualHostGroup> name must be unique. There must be only one<VirtualHostGroup>.

e. Copy all <ServerCluster> elements from both the files and paste into thenew file and ensure that the names are unique.Ensure that the Server Name is unique across all clusters.

f. In the <Transport> element, ensure that the keyring and stashfileproperties use the same location for all the application servers in the mergedfile.

g. Copy all the <URIGroup> elements from both files and paste into the newfile, and ensure that the names are unique.Ensure that the names are unique.

h. Copy all the <Route> elements from both files and paste into the new file.i. Apply any changes that you made to the names of VirtualHostGroup,

ServerCluster or URIGroup.j. Save the new file.

6. Open the httpd.conf file and add or modify the following line to point to thenew merged plug-in file.WebSpherePluginConfig/usr/IBM/HTTPServer/Plugins/config/OP/merged_file.xml

7. Ensure that the IgnoreAffinityRequests setting in the <ServerCluster> sectionis set to false:

8. Save and close the file.

Configuring property files for load balancing on AIX and Linuxoperating systems

Some configuration is required when using IBM HTTP Server as a load balancer ina WebSphere Application Server environment.

Procedure1. On the load-balancing web server, open a shell and go to the

/usr/IBM/HTTPServer/modules/ directory.2. Open merged plug-in file (plugin-cfg-merged.xml) in a text editor to make the

following changes:a. Change the IgnoreAffinityRequests setting to true.b. Change the ServerIOTimeout setting for all servers to a value that allows

sufficient time for the OpenPages application to respond to request from aclient.

c. For users to access the IBPM console and OpenPages simultaneously, ineach of the following Uri groups, change the cookie name.


For OpenPages change the cookie name to opsosa. For IBPM, change thename to opibpm.<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/*"/>

d. Save and close the file.3. Open the httpd.conf file in a text editor and make the following changes:

The default location of the file is /usr/IBM/HTTPServer/conf/httpd.conf.a. To load the required modules, add or uncomment the following lines

LoadModule negotiation_module modules/mod_negotiation.soLoadModule proxy_module modules/mod_proxy.soLoadModule proxy_ajp_module modules/mod_proxy_ajp.soLoadModule proxy_balancer_module modules/mod_proxy_balancer.soLoadModule proxy_connect_module modules/mod_proxy_connect.soLoadModule proxy_http_module modules/mod_proxy_http.soLoadModule status_module modules/mod_status.soLoadModule was_ap22_module modules/mod_was_ap22_http.so

b. Modify the ServerName setting to point to the host name where youinstalled the IBM HTTP Web Server.ServerName=MYSERVERNAME.DOMAIN.COM

c. Modify the ServerRoot setting to point to the installation location of theApache Web Server. For example,ServerRoot=/usr/IBM/HTTPServer/htdocs

d. Add the Allow from all attribute to each Directory element.<Directory>Options Indexes FollowSymLinksAllowOverride NoneOrder allow,denyAllow from all</Directory>

e. Uncomment the parameter ExtendedStatus setting and set the value to On.f. Set the location tags for server-status and server-info.

For example,<Location /server-status>SetHandler server-statusOrder Deny,AllowDeny from allAllow from all</Location>

<Location /server-info>SetHandler server-infoOrder Deny,AllowDeny from allAllow from all</Location>


Configuring property files for each OpenPages instanceYou must edit the server properties file on each OpenPages cluster member topoint to the load balancer.


Procedure1. Log on to the OpenPages cluster member as a non-root user who has

administrative privileges.2. Go to the OP_Home/aurora/conf directory.3. Open the aurora.properties file in a text editor.

a. Edit the application.url.path to point to the fully qualified domain nameof the load balancer.application.url.path=http\://op-load-balancer.domain.com\:port/openpages

b. Save and close the file.4. Open each server_name-OpenPagesServer#-server.properties file in a text




b. Save and close each server.properties file.5. Open each server_name-OpenPagesServer#-sosa.properties file in a text editor.

a. Edit the Application.url.path lines to point to the fully qualified domainname of the load balancer.application.url.path=https\://op-load-balancer.domain.com\:port

/openpages

b. Save and close each server.properties file.6. Open each server_name-InterstageBPMCS#-server.properties file in a text




b. Save and close each server.properties file.7. Restart the web server.

Customizing the load balancer in an AIX environment for largedata sets

For databases with a large data set, some OpenPages reports might timeout beforecompletion. If you experience problems with reports that are timing out, changeconfiguration settings in the IBM HTTP Web Server configuration file.

Change the following settings:

TimeOutThe number of seconds IBM HTTP Web Server waits to receive a GETrequest, between receipt of TCP packets on a POST or PUT request andbetween ACKs on transmissions of TCP packets in responses.

KeepAliveTimeoutThe number of seconds IBM HTTP Server waits for a subsequent requestbefore closing the connection.


Note: A high value for the setting can cause performance problems,especially if the higher timeout causes server processes to wait for idleclients.

Procedure1. Log on to load balancing web server as a user with administrative privileges.2. Open httpd.conf in a text editor.3. Change the KeepAliveTimeout property to a higher value.

KeepAliveTimeout 1800

4. Add and then set the TimeOut property.Ensure that the setting prevents timeout errors.For example, TimeOut 1800

5. Save and close the file.6. Restart IBM HTTP Web Server.

Load balancing the OpenPages reporting serverCommandCenter uses IBM Cognos Business Intelligence, which can scalehorizontally. To scale CommandCenter vertically within the same environment,increase the number of processes that are available to handle request. Dependingon the load, you can configure additional dispatchers.

To scale CommandCenter horizontally, install additional environments and registerthe Cognos dispatchers. Incoming requests are distributed across the multipleenvironments.

The number of dispatchers you need depends on the operating system, systemresources, the number of users, and other factors.

For more information about configuring dispatchers for your environment, see theIBM Cognos documentation library .

Adding OpenPages servers to Cognos Application Firewallsafe list

By default, Cognos Application Firewall (CAF) is enabled. IBM Cognos ApplicationFirewall validates domain and host names to protect URLs that are created. IBMCognos Application Firewall considers domain names derived from theenvironment configuration properties as safe domain names. Use the IBM CognosConfiguration to add OpenPages application servers to the list of valid domainsand host names.

Procedure1. Log on to the reporting server as a user with administrative privileges.2. Start IBM Cognos Configuration.3. In the Explorer pane, go to 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.5. In the Valid domain or hosts dialog box, click Add.6. Enter the names of all OpenPages application servers.7. Click OK.



8. Save the configuration and restart the Cognos service.If you use Windows Services to restart the Cognos service, the service is listedas CommandCenter.

Communication Between CommandCenter ServersIf you install CommandCenter on more than one computer, you must configure thedistributed installations to communicate with each other

Configure the following communication paths:v Configure the primary CommandCenter server as the default active server.v All CommandCenter servers must know the location of the content store

database.v All CommandCenter servers must know the location of the other

CommandCenter servers.v All CommandCenter servers must use the same cryptographic settings.v 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,or default active server, and one or more CommandCenter servers act as secondaryservers.

Procedure1. Ensure that CommandCenter is not running on any server.2. On the reporting server that is designated as the primary server, start IBM

Cognos Configuration that you want to designate as the primaryCommandCenter server.

Tip: Use the computer with the highest processor speed for the default activeserver.

3. In the Explorer pane, click Environment.4. For the Gateway URI, change the localhost portion of the URL to the name

of the primary.5. For the Dispatcher URI for Gateway, click Dispatcher URI for Gateway click

the pencil icon next to the Value box.6. In the Current Values list, change the localhost portion of the URL to the

name of the primary CommandCenter computer.a. For each additional CommandCenter computer, click Add.b. Change the localhost portion of the URL to the name of each additional

CommandCenter computer.c. Click OK.

7. For the Content Manager URIs, click the pencil icon next to the Value box.a. In the Current Values list, change the localhost portion of the URL to the

name of the primary CommandCenter computer.b. For each additional CommandCenter computer, click Add.c. Change the localhost portion of the URL to the name of each additional

CommandCenter computer.d. Click OK.

8. In the Explorer pane, click Security > Cryptography.


9. In the Properties pane, under CSK settings, ensure that Store symmetric keylocally? is set to True. The keystore must be created on the default activeCommandCenter computer

10. Click File > Save.11. Click Actions > Start.

When the services start, this computer becomes the default activeCommandCenter computer.

Configuring secondary CommandCenter serversIn a clustered environment, configure one or more CommandCenter servers to actas secondary servers.

Procedure1. Ensure that CommandCenter is running on the primary CommandCenter

server.2. On the reporting server that is designated as secondary server, start IBM

Cognos Configuration CommandCenter server.3. In the Explorer pane, click Environment.4. In the Environment - Group Properties pane, click Gateway URI.5. In the Value field, change the localhost portion of the URL to the name of

the primary CommandCenter computer.6. In the Environment - Group Properties pane, click Dispatcher URI for

Gateway.a. Click the pencil icon next to the Value box.b. In the Current Values list, change the localhost portion of the URL to the

name of the primary CommandCenter computer.c. For each additional CommandCenter computer, click Add.d. Change the localhost portion of the URL to the name of each additional

CommandCenter computer.e. Click OK.

7. In the Environment - Group Properties pane, click Content Manager URIs.a. Click the pencil icon next to the Value box.b. In the Current Values list, change the localhost portion of the URL to the

name of the primary CommandCenter computer.c. For each additional CommandCenter computer, click Add.d. Change the localhost portion of the URL to the name of each additional

CommandCenter computer.e. Click OK.

8. In the Explorer pane, under Security, click Cryptography.9. In the Properties pane, under CSK settings, set Store symmetric key locally?

to False.

Note: The keystore is created on the primary CommandCenter computer.There can be only one keystore in a load balanced CommandCenterinstallation.

10. In the Explorer window, under Security, Cryptography, click Cognos.11. Under the Certificate Authority settings property group, set the Password

property to match the one that you configured on the primaryCommandCenter server.


a. Ensure that all other cryptographic settings match the settings that youconfigured on the primary CommandCenter computer.

12. In the Explorer pane, under Data Access > Content Manager, click ContentStore.

13. Ensure that the values for the content store match the primaryCommandCenter computer

14. Click File > Save.15. Click Actions > Start.

Configuring an Apache load balancer or proxy serverIf you are using an external proxy server for load balancing, you must add a proxyredirection directive to the httpd.conf file on the proxy server. Requests sent to theproxy server are redirected to the server specified in the httpd.conf file.

Procedure1. Log on to the load balancer server as a user who has administrative privileges.2. Go to the Apache_Home\conf\ directory, and open the httpd.conf file in an

editor.3. Add the following lines:

<Location /ibmcognos/>ProxyPass http://primary_reporting_server/ibmcognos/SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1</Location>

Note: You must include the trailing forward slash in the ProxyPass directivewhen specifying the Cognos virtual directory (/ibmcognos/).


Changing the CommandCenter host settingsYou must update configuration files to use the CommandCenter server name andport settings.


privileges.2. Open a browser window and go to the OpenPages application by typing the

following URL:http://OP_server_name:port/openpages

3. Log on to the OpenPages application as a user with administrative privileges.4. Under Administration, select Settings.

a. Expand the OpenPages > Platform > Reporting Schema > Object URLGenerator.

b. Click Host.c. In the Value field, update the setting to point to the OpenPages server.

Note: If you use the CommandCenter in a load-balanced environment,you must type the fully qualified domain name of the load balancingserver. If required, change the port.

5. Stop OpenPages services.6. On the application server, go to the OP_Home\aurora\conf directory.


7. In the cognos.framework.refresh.servlet=http\://localhost\:8080/crf-refresher property, replace localhost\:8080 with the reporting server nameand port.cognos.framework.refresh.servlet=http\://ccserver\:8080/crf-refresher

8. In the cognos.server=http\://localhost:80/cognos8/cgi-bin/cognos.cgiproperty, replace localhost:80 with the reporting server name and portnumber.cognos.server=http\://ccserver:80/cognos8/cgi-bin/cognos.cgi

9. Add the following value to the logout.url.cognos= property:http\://CommandCenter_server_name\CommandCenter_port\/cognos/cgi-bincognos.cgi?

b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

Example:logout.url.cognos=http\://ccserver\:8080/cognos/cgi-bincognos.cgi?

b_action\=xts.run&m\=portal/logoff.xts&h_CAM_action\=logoff

10. Save your changes and exit the editor.


Chapter 11. Single signon integration for OpenPagesapplication server and the reporting server

IBM OpenPages GRC Platform can integrate into a number of single sign-onsolutions, such as CA SiteMinder. You can also configure the reporting server forsingle signon.

Configuring OpenPages applications for single signonIntegrate single signon for IBM OpenPages GRC Platform applications byconfiguring the settings in the OpenPages application interface.

Procedure1. Start the OpenPages services.2. Log on to the OpenPages application interface as a user with administrative

privileges.3. Under Administration, select Settings.4. Set the value of the Show Hidden Settings setting to true

a. Expand the OpenPages > Applications > Common > Configuration.b. Click Show Hidden Settings to open its detail page.c. In the Value field on the setting detail page, change the value to true

d. Click Save.5. Set the value of the Session Attribute and Username Attribute settings:

a. Expand the OpenPages > Platform > Security > Single Sign On >Implementations > Header-based.

b. Click Class Name to open its detail page.c. In the Value field, enter

com.openpages.singlesignon.HTTPHeaderBasedModule.d. Click Session Attribute to open the detail page.e. In the Value field, modify the value to match the session attribute for your

single signon system.The following examples show values for the Session Attribute parameter.v Using SiteMinder 6.0, the value of the Session Attribute parameter is

SMSERVERSESSIONID

v Using Tivoli® Access Manager 6.1, the value of the Session Attributeparameter is iv_creds

f. Click Save.g. Click Username Attribute to open its detail page.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.The following examples show values for the Username Attribute parameter.v Using SiteMinder 6.0, the value of the Username Attribute is SMUSER

v Using Tivoli Access Manager 6.1, the value of the Username Attribute isiv_user

i. Click Save.6. Enable single sign-on:

115

a. OpenPages > Platform > Security > Single Sign On > Implementations >Header-based

b. Click OP 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 SOX to open its detail page.f. In the Value field on the setting detail page, set the value to true.g. Click Save.

7. Reset the value in the Show Hidden Settings setting to false.

Configuring the single signon logout destinationTo securely log out from an OpenPages application session where single signon isenabled, configure the system to redirect the user.

Logging out of the OpenPages application does not automatically log the user outof a single signon system. If you use Back in the web browser to reenter theOpenPages application, your session is re-created. The session uses the existing,valid third-party credentials.

Procedure1. Log on to the OpenPages application interface as a user with administrative

privileges.2. Under Administration, select Settings.3. Expand the OpenPages > Platform > Security.4. Click Logout URL to open its detail page.5. In the Value box, type a fully qualified URL.6. Click Save.

Configuring the application server for single signon on Windowscomputers

If you are using Apache web server as a load balancer, in addition to configuringthe OpenPages application for single signon, you must configure additionalsettings. You must prevent specific files from going through the SSO application.

When an authenticated user attempts to click a job remediation link, OpenPagesauthenticates the user. However, when OpenPages is connected to a single signonapplication, that application can block the authentication request and theremediation link does not function.

Configure the application server to route two Java servlets, opLogin andsecurityHelper, directly to the OpenPages for internal authentication.

Procedure1. Log on to the application server as a user with administrative privileges.2. Go to the Apache_Home\conf directory.3. Open the httpd.conf file in a text editor.

Note: In an SSL environment, edit the httpd-ssl.conf file.


4. To create a path to route the opLogin and securityHelper servlets to theOpenPages without traversing the single signon application, add the followinglines:<Proxy balancer://backend>BalancerMember <http://<server_name>.openpages.com:<port> route=1BalancerMember <http://<server_name>.openpages.com:<port> route=2Order Allow,DenyAllow from all</Proxy>

ProxyPass /openpages/opLogin balancer://backend/openpages/opLoginProxyPass /openpages/securityHelper balancer:

//backend/openpages/securityHelper

Note: In an SSL environment, enter the SSL address and port.For example<Proxy balancer://backend>BalancerMember <https://qe-vm07.openpages.com:7009> route=1BalancerMember <https://qe-vm07.openpages.com:7011> route=2Order Allow,DenyAllow from all</Proxy>

ProxyPass /openpages/opLogin balancer://backend/openpages/opLoginProxyPass /openpages/securityHelper balancer:

//backend/openpages/securityHelper

5. To ensure that traffic to the OpenPages login page is routed the single signonapplication, add the following lines:<Proxy balancer://cluster>BalancerMember <http://<server_name>.openpages.com:<port> route=1Order Allow,DenyAllow from all</Proxy>

ProxyPass /openpages/ balancer://cluster/openpages/ stickysession=opapp|opappProxyPass /ibpmconsole/ balancer://cluster/ibpmconsole/

stickysession=JSESSIONID|jsessionidProxyPass /ibpm/ balancer://cluster/ibpm/ stickysession=JSESSIONID|jsessionid

Note: In an SSL environment, enter the SSL address and port.6. Remove any references to /openpages and /ibpmconsole from the file.

For example, remove the following sections that were added during theconfiguration of a cluster environment:<Location /openpages>WLCookieName opappSetHandler weblogic-handlerDynamicServerList ONMaxPostSize 0Debug OnWLLogFile /logs/openpages.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT></Location>

<Location /ibpmconsole>WLCookieName opibpmSetHandler weblogic-handlerDynamicServerList ONMaxPostSize 0Debug OnWLLogFile logs/ibpmconsole.logWebLogicCluster <SERVER>.<DOMAIN>.COM:<PORT>,<SERVER>.<DOMAIN>.COM:<PORT></Location>

Chapter 11. Single signon integration for OpenPages application server and the reporting server 117

Note: Do not remove the <Location /ibpmweblogicconsole> parameter:<Location /ibpmweblogicconsole>SetHandler weblogic-handlerMaxPostSize 0Debug OnWLLogFile logs/ibpmweblogic_console.logWebLogicHost <SERVER>.<DOMAIN>.COMWebLogicPort 49901 </Location>

7. Go to the OP_HOME\aurora\conf directory:8. Open the aurora.properties file and ensure that application.url.path is

pointing to the OpenPages application server:application.url.path=http\://server_name.openpages.com\:OpenPages_port/openpages

Note: In a load balanced environment, enter the fully qualified domain nameof the load balancer. In an SSL environment, enter the SSL address (https://)and port.

9. Save and close the file.10. Open the server.properties file and ensure that the following paths are

pointing to the OpenPages application server and workflow server:url.path.openpages=http\://server_name\:

OpenPages_port/openpages

url.path.workflow.admin=http\://server_name\:IBPM_port/ibpmconsole

Note: In an SSL environment, enter the SSL address (https://) and port. In aload balanced environment, enter the fully qualified domain name of the loadbalancer.

11. Save and close the file.12. Open the sosa.properties file and ensure that the application.url.path is

pointing to the OpenPages application server:application.url.path=http\://server_name\:port/openpages

Note: In an SSL environment, enter the SSL address (https://) and port. In aload balanced environment, enter the fully qualified domain name of the loadbalancer.


Disabling OpenPages single signonYou must disable single signon registry settings before you upgrade OpenPagesGRC Platform. After the upgrade, you can re-enable the settings.

Procedure1. Start the OpenPages services.2. Open a web browser and go to the current OpenPages application.3. Log on as a user with administrative permissions.4. From the Administration menu, select Settings.5. In all versions, disable single sign-on as follows:

a. Expand the OpenPages > Platform > Security > Single Sign On.b. Click OP 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 SOX to open its detail page.


f. In the Value field on the setting detail page, set the value to false.g. Click Save.

Configuring single signon for a reporting serverIf you are using a single sign-on system such as CA SiteMinder with theOpenPages application, you must load an updated redirect JavaServer Pages (JSP).

Load the JavaServer Pages through the ObjectManager tool by using theCommandCenter-integration-op-config.xml file. The file is located on theOpenPages installation DVD.

Procedure1. Log on to a computer that has SQL*Plus and access to the database server.

Note: For AIX installations, log on as the opuser or a non-root user who hasadministrative privileges.

2. From the Installer DVD or on your network share location, copy theOP_version_Configuration\loader-data\commandcenter directory to the localsystem.

3. Go to the OP_Home/bin directory.4. Run the following command:

ObjectManager load config OpenPagesAdministrator passwordpath-to-loader-file CommandCenter-integration

Chapter 11. Single signon integration for OpenPages application server and the reporting server 119


Chapter 12. Silent installations

You can install the OpenPages GRC Platform components by using the installationprogram in silent mode. Silent mode installations are useful when you areinstalling identical configurations across several computers. Silent modeinstallations automate the installation and configuration process by specifyingoptions. During the silent installation process, you are not prompted forinformation.

Typically, an interactive installation is done first to capture user responses.

To silently install components, the following tasks required:1. Edit the response file to record your installation preference.2. Run the installer in silent mode.

Response files for silent installationsInstead of prompting for installation options, the installation program installs thesoftware using a predefined set of options, which are stored in a response file.

You modify the response file for a component to record your installationpreferences.

Editing the response file for 64-bit database client silentinstallations

Modify the response file with your installation preferences. The installationprogram uses the information in the file to install the database client software insilent mode.

Before you begin

Ensure that you completed the prerequisite installation tasks.

Procedure1. Log on to the application server as a user with administrative privileges.

For AIX installations, use the oracle user that you created for the OpenPagesinstallation.

2. On Windows computers, open a Command Prompt window by using the Runas Administrator option, or open an AIX shell.

3. Go the OEI_SERVER_CLIENT_64bit_Win\Disk1\InstData\VM directory where youcopied the repository files.

4. Open the ClientInstaller.properties file in a text editor.5. Modify the parameters listed in the following table to suit your environment.

For a description of the parameters, see “Response file parameters for 64-bitdatabase client installations” on page 125.

Note: Do not modify settings that are not listed.6. Save and close the file.

121

Editing the response file for OpenPages application silentinstallations

Modify the response file with your installation preferences. The installationprogram uses the information in the file to install the IBM OpenPages GRCPlatform application server in silent mode.

About this task

Where indicated, do not change parameter values in the response files. Thesesettings might be internal values required by installation program.

The install kit contains a sample response file that contains default values for eachparameter. You can use this file for examples of the values you can use. You canalso edit this file directly. If you edit the file, save the it as op-silentInstall-WL.properties or op-silentInstall-WAS.properties.


For AIX installations, use the oracle user that you created for the OpenPagesinstallation.


3. Go the following location:OP_version_Non_Embedded_WIN64\OP_version_Configuration\Install\silent-installer

4. Copy the parameter file to the installation location:v On Windows computers, copy the op-silentInstall-WL.properties file to

the OP_version_Non_Embedded_Installer\ Disk1\InstData\VM directory.v On AIX computers, copy the op-silentInstall-WAS.properties file to the

OP_version_Non_Embedded_Installer/Disk1/InstData/VM directory.5. Open the response file in a text editor.6. Modify the parameters to suit your environment.

For a description of the parameters, see “Response file parameters forOpenPages application installations” on page 126.


Editing the response file for CommandCenter silentinstallations

Modify the response file with your installation preferences. The installationprogram uses the information in the file to install CommandCenter in silent mode.

About this task

Where indicated, do not change parameter values in the response files. Thesesettings might be internal values required by installation program.

The install kit contains a sample response file that contains default values for eachparameter. You can use this file for examples of the values you can use. You canalso edit this file directly. If you edit the file, save the it as op-silentInstall-


WL.properties or op-silentInstall-WAS.properties.


For AIX installations, use the opuser user that you created for the OpenPagesinstallation.


3. Go the following location:OP_version_Non_Embedded_WIN64\OP_version_Configuration\Install\silent-installer

4. Copy the parameter file to the installation location:v On Windows computers, copy the cc-silentInstall-WLS.properties file to

the OP_version_Non_Embedded_Installer\ Disk1\InstData\VM directory.v On AIX computers, copy the cc-silentInstall-WLS.properties file to the

OP_version_Non_Embedded_Installer/Disk1/InstData/VM directory.5. Open the response file in a text editor.6. Modify the parameters to suit your environment.

For a description of the parameters, see “Response file parameters forCommandCenter installations” on page 137.


Response file parameters for use with silent installationsInstead of prompting for installation options, a silent installation installs thesoftware using a predefined set of options, which are stored in a response file.

The parameters in the response file vary depending on what type of installationyou are doing. For information about editing response files, see “Response files forsilent installations” on page 121.

Response file parameters for 64-bit database server installations

When editing the response file, do not modify settings that are not listed in thefollowing table.

Parameter Description

INSTALL_ORACLE_SERVER Enter 1 to install the software.

For example INSTALL_ORACLE_SERVER=1

SERVER_SOFTWARE_INSTALL_DRIVE Enter the Window drive or AIX directoryused to install the database server.

For Windows computers, a colon is required.For example,SERVER_SOFTWARE_INSTALL_DRIVE=C:

DB_INSTANCE_PORT Enter the port used by the database instance.The port must be in the range of 1024-65535.

Chapter 12. Silent installations 123


DB_INSTANCE_INSTALL_DRIVE Enter the drive or directory used for thedatabase instance.

For AIX installations, the directory mustexist.

DB_INSTANCE_NAME Enter the name of the OpenPages databaseinstance. By default, the instance name isOP.

The name must follow the standardguidelines for a database name:

v Use alphanumeric characters, underscore(_), dollar sign ($), or hash symbol (#).

v The first character must be a lower oruppercase letter.

v Maximum length must not exceed 8characters.

ORACLE_SYSTEM_PASSWORD

ORACLE_SYS_PASSWORD

ORACLE_DBSNMP_PASSWORD

ORACLE_SYSMAN_PASSWORD

Enter the passwords for the listed users.Reenter the password in the RECOFNIRMparameter.

The database includes the following users:

v SYSTEM (Oracle superuser.)

v SYS

v DBSNMP

v SYSMAN

The passwords must follow these rules:

v Maximum length cannot exceed 30characters

v Use alphanumeric characters, underscore(_), dollar sign ($), or hash symbol (#).

v The first character must be a lower oruppercase letter.

LICENSE_ACCEPTED Enter TRUE to accept the license agreement,otherwise the installation programterminates.

Response file parameters for 32-bit database client installations



INSTALL_ORACLE_CLIENT Enter 1 to install the software.

For example INSTALL_ORACLE_CLIENT=1





For AIX installations, use the directory youcreated as a prerequisite.

DB_INSTANCE_PORT Enter the port used by the OpenPagesdatabase instance.

For example, DB_INSTANCE_PORT=1521

DB_HOSTNAME

DB_INSTANCE_NAME

Enter the address of the Oracle database andthe name of the OpenPages databaseinstance.

For example

v DB_HOSTNAME=10.128.28.104

v DB_INSTANCE_NAME=OP


Response file parameters for 64-bit database client installations



INSTALL_ORACLE_CLIENT Enter 1 to install the software.

For example INSTALL_ORACLE_CLIENT=1



For AIX installations, use the directory youcreated as a prerequisite.

DB_INSTANCE_PORT Enter the port used by the OpenPagesdatabase instance.

For example, DB_INSTANCE_PORT=1521

DB_INSTANCE_INSTALL_ADDRESS Enter the address of the Oracle database andthe name of the OpenPages databaseinstance.

For example

v DB_HOSTNAME=10.128.28.104

v DB_INSTANCE_NAME=OP




Response file parameters for OpenPages applicationinstallations

When editing the response file, do not modify settings that are not listed in thefollowing tables.

Table 59. Response file parameters and descriptions for Windows computers


LICENSE_ACCEPTED Enter true to accept the license agreement,otherwise the installation programterminates.

SYSTEM_DRIVE_ROOT Enter the drive for installing the OpenPagesapplication environment.

Use the format Drive\:\\ format.

For example: C\:\\

USER_INSTALL_DIR Enter the installation location of OpenPagessoftware components.

APPSERVER_ADMIN_PASSWORD Enter the Oracle WebLogic Server adminserver password. This password mustcontain at least 8 alphanumeric characters,start with a letter and contain at least onenumber.

APPSERVER_ADMIN_PASSWORD_CONFIRM Re-enter the password to confirm.

APPSERVER_ADMIN_PORT Enter the port used internally to access theOpenPages admin server.

Example: 7001

APPSERVER_ADMIN_SSLPORT Enter the port used internally to access asecure SSL connection to the OpenPagesadmin server.

Example: 7002

OP_HTTP_PORT Enter the port used to access the OpenPagesapplication.

Default: 7009

OP_HTTPS_PORT Enter the port used for a secure SSLconnection to the OpenPages application.

Default: 7010

APPSERVER_HOME Enter the installation location of OracleWebLogic Server

Example: C:\\Oracle\\Middleware


Table 59. Response file parameters and descriptions for Windows computers (continued)


APPSERVER_WLHOME Enter the installation location of WebLogicServer.

Example: C:\\Oracle\\Middleware\\wlserver_version

APPSERVER_JAVAHOME Enter the location where the JavaDevelopment Kit (JDK 1.6) is installed.

If Oracle WebLogic Server is installed, thislocation must be the same Java instanceused by Oracle WebLogic Server.

Example: C:\\Program Files\\Java\\jdk1.6.0_26

APPSERVER_NOOFSERVERS=1 Enter the number of managed servers toinstall.

Default: 1

SERVER_INSTANCE_COUNT=1 Enter the number of managed servers toinstall.

Enter same value asAPPSERVER_NOOFSERVERS.

Default: 1

COGNOS_CRN_PORT Enter the port used by OpenPages tocommunicate with Cognos IBM BusinessIntelligence.

COMMANDCENTER_HOSTNAME Enter the computer name of the Cognos BIserver.

COGNOS_CRN_CTXTROOT Enter the context root for the Cognos BIURL.

Example: ibmcognos

FRAMEWORK_GENERATOR_PORT Enter the port used by OpenPages to theFramework Model Generator service.

Example: 8080

CORE_CONFIGURATION=1 This value controls whether the Level 0configuration metadata required byOpenPages is installed.

Must be set to 1.

CORE_NOCONFIGURATION=0 This value controls whether the Level 0configuration meta data required byOpenPages is installed.

Must be set to 0.

CUSTOMCODE_HOST_NAME= Enter the name of computer whereOpenPages custom code is stored.

APPSERVER_ADMIN_HOSTNAME Enter the name of the OpenPages adminserver.

Must be the same as CUSTOMCODE_HOST_NAME=.




DB_CURRENCY_SELECTED Enter the three-letter ISO code for the basecurrency to use with OpenPagesapplications.

For example USD

IBPM_DB_USERNAME Enter the user name used by OpenPages tocreate and access the workflow databaseinstance.

Example: opworkflow

IBPM_DB_PASSWORD Enter the password for the workflow useraccount.

IBPM_DB_PASSWORD_CONFIRM Re-enter the password to confirm.

IBPM_INSTALL_DIR Enter the location of the InterstageBPMfolder.

Example: C:\\OpenPages\\Fujitsu\\InterstageBPM

IBPM_JDK_HOME Enter the installation of the JavaDevelopment Kit (JDK 1.6).

If Oracle WebLogic Server is installed, thislocation must be the same Java instanceused by Oracle WebLogic Server.

The value must be the same asAPPSERVER_JAVAHOME.

Example: C:\\Program Files\\Java\\jdk1.6.0_26

IBPMSERVER_ADMIN_PORT Enter the port used for the workflow serveradmin console.

Example: 49901

IBPMSERVER_ADMIN_SSLPORT Enter the port used for secure SSLconnections to access the workflow serveradmin console.

Example: 49902

IBPM_HTTP_PORT Enter the port used to access the OracleWebLogic Server admin console (workflowserver).

Example: 49951

IBPM_HTTPS_PORT Enter the port used for secure SSLconnections to access the Oracle WebLogicServer admin console.

Example: 49952




IBPM_MULTICAST_ADDR Enter the workflow server multicast IPaddress.

Use the same multicast address on allservers.

Do not use 224.0.0.0.

IBPM_EMAIL_USERNAME Enter the display name of the e-mail addressof the sender.

Do not use spaces.

Example: sysadmin

IBPM_EMAIL_SENDADDRESS Enter the reply-to e-mail address used forsending messages from the OpenPagesworkflow notification service.

Example: [email protected]

IBPM_MAIL_SERVER Enter the mail server to use for OpenPagesworkflow notifications.

Example: yourserver.yourdomain.com

INSTALL_LOG_DESTINATION Enter the location within theUSER_INSTALL_DIR directory whereOpenPages installation logs are stored.

Example: C:\\OpenPages\\logsNote: If you specify a drive other than thedefault, the installer might also store logfiles in the default location.

INSTALLER_DEBUG_LOG Enter the location within theUSER_INSTALL_DIR directory where allOpenPages installation debug logs arestored.

Example: C:\\OpenPages\\logs\\openpages_installer_debug.logNote: If you specify a drive other than thedefault, the installer might also store logfiles in the default location.

INSTALL_LOG_NAME Specify the name of the installation log thatis crated during the install.

Example: OpenPages_version_Install.log

OP_BACKUP_RESTORE_LOCATION Enter the location within theUSER_INSTALL_DIR directory where theBackup/Restore utility stores the files itcreates.

Example: C:\\OpenPages\\openpages-backuprestore




OP_STORAGE_DIR Enter the location within theUSER_INSTALL_DIR directory where theattached files and forms associated withOpenPages objects are stored.

Example: C:\\OpenPages\\openpages-storage

OP_PRIMARY_SERVER Enter 1 if this OpenPages server is theadmin server.

Enter 0 if the server is a not the adminserver.

OP_SECONDARY_SERVER Enter 1 if this OpenPages server is not theadmin server.

Enter 0 if the server is the admin server.

OPENPAGES_ADMINISTRATOR_USERNAME Enter the user name for the OpenPagesapplication Super Administrator.

Default: OpenPagesAdministrator

OPENPAGES_ADMINISTRATOR_PASSWD Enter the password for the SuperAdministrator user account

OPENPAGES_ADMINISTRATOR_CONFPASSWD Re-enter the password to confirm.

ORACLE_HOME Enter the location of Oracle Home folder onthe local computer.

Example: C:\\OpenPages\\database\\openpages_data\\repository\\server112_se_x64\\software

ORACLE_ALIAS Enter the TNS alias name for the Oracledatabase instance.

ORACLE_DATA_HOME Enter the location of the Oracle data homedirectory on the database server.

This location is where Oracle data is storedfor OpenPages applications.

Example: C:\\OpenPages\\database\\openpages_data\\ repository\\database112_se_x64\\oradata\\SID

ORACLE_HOSTNAME Enter the computer name of the Oracledatabase server.

ORACLE_PORT Enter the port used by the Oracle databaselistener.

This port is the database instance port.

Example: 1521

ORACLE_SYSTEM_USERNAME Enter the current Oracle system account username.

Example: system




ORACLE_SYS_USERNAME Enter the current Oracle SYS account username.

Example: sys

ORACLE_SYSTEM_PASSWORD Enter the password for the Oracle systemuser account.

ORACLE_SYS_PASSWORD Enter the password for the Oracle sys useraccount.

ORACLE_SYSTEM_CONFIRM_PASSWORD Re-enter the system user password toconfirm.

ORACLE_SYS_CONFIRM_PASSWORD Re-enter the sys user password to confirm.

OP_DB_USERNAME Enter the user name used by OpenPages tocreate and access the OpenPages databaseinstance.

Example: openpages

OP_DB_PASSWORD Enter the password for the OpenPages useraccount,

OP_DB_PASSWORD_CONFIRM Re-enter the password to confirm.

IS_DB_SERVICENAME Enter 1 to specify that the instance name is aService Name.

Enter 0 if the instance name is an SID.

Default: 0

IS_DB_SID Enter 1 to specify that the instance name isan SID.

Enter 0 if the instance name is a ServiceName.

Default: 1

DB_IDENTIFIER_TYPE Enter either SID or Service Name to describethe OpenPages database identifier.

DB_IDENTIFIER Enter the string in the tnsnames.ora file thatis used to identify the OpenPages database.

DB_SERVICENAME Enter the service name that is used for theOpenPages database instance.

DB_SID Enter the SID of the OpenPages database.

CUSTOMCODE_UNC_MACHINE_NAME Enter the name of the computer whereOpenPages custom code is stored.

CUSTOMCODE_UNC_STORAGE_LOCATION Enter the location within theUSER_INSTALL_DIR directory where customcode associated with OpenPages objects isstored.

Default: C:\\OpenPages\\openpages-storage




CUSTOMCODE_OPSTORAGELOCATION Enter the location within theUSER_INSTALL_DIR directory where theattached files and forms associated withOpenPages objects are stored.

Default: C:\\OpenPages\\openpages-storage

Table 60. Response file parameters and descriptions for AIX computers



UNIX_OPT Enter the location of the opt directory.

For example: /opt

USER_INSTALL_DIR Enter the installation location of OpenPagessoftware components.

Example: /opt/OpenPages

OP_PRIMARY_SERVER Enter 1 if this OpenPages server is theadmin server.

Enter 0 if the server is a not the adminserver.

OP_SECONDARY_SERVER Enter 1 if this OpenPages server is not theadmin server.

Enter 0 if the server is the admin server.

APPSERVER_HOME Enter the installation location of IBMWebSphere Application Server

Example: /home/usr/opuser/IBM/WebSphere/Appserver

APPSERVER_JAVAHOME Enter the location where the JavaDevelopment Kit (JDK 1.6) is installed.

This location must be the same Javainstance used by WebSphere ApplicationServer.

Example: /home/usr/opuser/IBM/WebSphere/Appserver/java

APPSERVER_NOOFSERVERS=1 Enter the number of managed servers toinstall.

Default: 1

SERVER_INSTANCE_COUNT=1 Enter the number of managed servers toinstall.

Enter same value as APPSERVER_NOOFSERVERS.

Default: 1


Table 60. Response file parameters and descriptions for AIX computers (continued)


OP_CLUSTER_STARTING_PORT_INPUT= Enter the starting port number for the firstmanaged OpenPages server instance.

IBM WebSphere Application Server requires20 consecutive, dedicated ports.

Example: 10101

IBPM_CLUSTER_STARTING_PORT_INPUT Enter the starting port number for the firstmanaged workflow server instance.

IBM WebSphere Application Server requires20 consecutive, dedicated ports.

Example: 20101

COGNOS_CRN_PORT Enter the port used by OpenPages tocommunicate with Cognos IBM BusinessIntelligence.

COMMANDCENTER_HOSTNAME Enter the computer name of the Cognos BIserver.

COGNOS_CRN_CTXTROOT Enter the context root for the Cognos BIURL.

Example: ibmcognos

FRAMEWORK_GENERATOR_PORT Enter the port used by OpenPages to theFramework Model Generator service.

Example: 8080

CORE_CONFIGURATION=1 This value controls whether the Level 0configuration metadata required byOpenPages is installed.

Must be set to 1.

CORE_NOCONFIGURATION=0 This value controls whether the Level 0configuration meta data required byOpenPages is installed.

Must be set to 0.

CUSTOMCODE_HOST_NAME= Enter the name of computer whereOpenPages custom code is stored.

APPSERVER_ADMIN_HOSTNAME Enter the name of the OpenPages adminserver.

Must be the same asCUSTOMCODE_HOST_NAME=.

DB_CURRENCY_SELECTED Enter the three-letter ISO code for the basecurrency to use with OpenPagesapplications.

For example USD.

IBPM_DB_USERNAME Enter the user name used by OpenPages tocreate and access the workflow databaseinstance.

Example: opworkflow




IBPM_DB_PASSWORD Enter the password for the workflow useraccount.

IBPM_DB_PASSWORD_CONFIRM Re-enter the password to confirm.

IBPM_EMAIL_USERNAME Enter the display name of the e-mailaddress of the sender.

Do not use spaces.

Example: sysadmin

IBPM_EMAIL_SENDADDRESS Enter the reply-to e-mail address used forsending messages from the OpenPagesworkflow notification service.

Example: [email protected]

IBPM_MAIL_SERVER Enter the mail server to use for OpenPagesworkflow notifications.

Example: yourserver.yourdomain.com

IBPM_INSTALL_DIR Enter the location of the InterstageBPMfolder.

Example: /opt/OpenPages/Fujitsu/InterstageBPM

IBPM_JDK_HOME Enter the installation of the JavaDevelopment Kit (JDK 1.6).

The value must be the same asAPPSERVER_JAVAHOME.

Example: /opt/IBM/WebSphere/AppServer/java

IBPM_MULTICAST_ADDR Enter the workflow server multicast IPaddress.

Use the same multicast address on allservers.

Do not use 224.0.0.0.

INSTALL_LOG_DESTINATION Enter the location where OpenPagesinstallation logs are stored.

Example: /opt/OpenPages/logs

INSTALLER_DEBUG_LOG Enter the location where all OpenPagesinstallation debug logs are stored.

Example: /opt/OpenPages/logs/openpages_installer_debug.logNote: If you specify a drive other than thedefault, the installer might also store logfiles in the default location.

INSTALL_LOG_NAME Specify the name of the installation log thatis created during the install.

Example: OpenPages_version_Install.log




OP_BACKUP_RESTORE_LOCATION Enter the location where theBackup/Restore utility stores the files itcreates.

Example: /opt/OpenPages/openpages-backuprestore

OP_STORAGE_DIR Enter the location where the attached filesand forms associated with OpenPagesobjects are stored.

Example: /opt/OpenPages/openpages-storage

OPENPAGES_ADMINISTRATOR_USERNAME Enter the user name for the OpenPagesapplication Super Administrator.

Default: OpenPagesAdministrator

OPENPAGES_ADMINISTRATOR_PASSWD Enter the password for the SuperAdministrator user account

OPENPAGES_ADMINISTRATOR_CONFPASSWD Re-enter the password to confirm.

ORACLE_HOME Enter the location of Oracle Home folder onthe local computer.

Example: /opt/oei/openpages_data/repository/ client112_ac_x64/software

ORACLE_ALIAS Enter the TNS alias name for the Oracledatabase instance.

ORACLE_DATA_HOME Enter the location of the Oracle data homedirectory on the database server.

This location is where Oracle data is storedfor OpenPages applications.

Example: /opt/openpages_data/openpages_data/ repository/database112_se_x64/oradata/AIX6110

ORACLE_HOSTNAME Enter the computer name of the Oracledatabase server.

ORACLE_PORT Enter the port used by the Oracle databaselistener.

This port is the database instance port.

Example: 1521

ORACLE_SYSTEM_USERNAME Enter the current Oracle system accountuser name.

Example: system

ORACLE_SYS_USERNAME Enter the current Oracle SYS account username.

Example: sys

ORACLE_SYSTEM_PASSWORD Enter the password for the Oracle systemuser account.




ORACLE_SYS_PASSWORD Enter the password for the Oracle sys useraccount.

ORACLE_SYSTEM_CONFIRM_PASSWORD Re-enter the system user password toconfirm.

ORACLE_SYS_CONFIRM_PASSWORD Re-enter the sys user password to confirm.

OP_DB_INSTALL_SELECTED Enter 1 to install the OpenPages databaseschema and users as part of the OpenPagesapplication installation.

Enter 0 if the OpenPages schema isinstalled.

Default: 1

OP_DB_INSTALL_NOTSELECTED Enter 0 if the OpenPages schema isinstalled.

Enter 1 if you are installing the OpenPagesdatabase schema and users as part of theOpenPages application installation.

Default: 0

OP_DB_USERNAME Enter the user name used by OpenPages tocreate and access the OpenPages databaseinstance.

Example: openpages

OP_DB_PASSWORD Enter the password for the OpenPages useraccount,

OP_DB_PASSWORD_CONFIRM Re-enter the password to confirm.

IS_DB_SERVICENAME Enter 1 to specify that the instance name isa Service Name.

Enter 0 if the instance name is an SID.

Default: 0

IS_DB_SID Enter 1 to specify that the instance name isan SID.

Enter 0 if the instance name is a ServiceName.

Default: 1

DB_IDENTIFIER_TYPE Enter either SID or Service Name to describethe OpenPages database identifier.

DB_IDENTIFIER Enter the string in the tnsnames.ora file thatis used to identify the OpenPages database.

DB_SERVICENAME Enter the service name that is used for theOpenPages database instance.

DB_SID Enter the SID of the OpenPages database.

IBPMSERVER_ADMIN_SOAP_PORT Enter the port for the workflow adminconsole SOAP listener.

Example: 8891




APPSERVER_ADMIN_SOAP_PORT Specify the port for the WebSphereApplication Server admin console SOAPlistener.

Example: 8889

CUSTOMCODE_IS_UNC Enter TRUE if the custom code storagelocation is on a separate network drive.

Enter FALSE if the storage location is on thelocal system.

CUSTOMCODE_UNC_MACHINE_NAME Enter the name of the computer whereOpenPages custom code is stored.

CUSTOMCODE_UNC_STORAGE_LOCATION Enter the location where custom codeassociated with OpenPages objects is stored.

Default: /opt/OpenPages/openpages-storage

CUSTOMCODE_OPSTORAGELOCATION Enter the location where the attached filesand forms associated with OpenPagesobjects are stored.

Default: /opt/OpenPages/openpages-storage

Response file parameters for CommandCenter installations

When editing the response file, do not modify settings that are not listed in thefollowing tables.

Table 61. CommandCenter parameters and descriptions for Windows computers



SYSTEM_DRIVE_ROOT Enter the drive for installing the OpenPagesapplication environment.

Use the format Drive\:\\ format.

For example: C\:\\

USER_INSTALL_DIR Enter the directory to installCommandCenter.

Example: C:\\OpenPages\\CommandCenter.

COGNOS_RN_ROOT Enter the installation location of Cognos IBMBusiness Intelligence.

CC_URL Enter the Cognos dispatcher.

Example: http://server_name:9300/p2pd/servlet/dispatch.

ORACLE_ROOT_INSTALL_FOLDER Enter the path to where the Oracle Client isinstalled.


Table 62. CommandCenter response file parameters and descriptions for AIX computers



USER_INSTALL_DIR Enter the directory to installCommandCenter.

Example: /opt/OpenPages/CommandCenter

COGNOS_RN_ROOT Enter the installation location of Cognos IBMBusiness Intelligence.

CC_URL Enter the Cognos dispatcher.

Example: http://server_name:9300/p2pd/servlet/dispatch.

ORACLE_ROOT_INSTALL_FOLDER Enter the path to where the Oracle Client isinstalled.

Installation program in silent modeTo run the installation program in silent mode, you must use a response file thathas your installation options recorded.

Running the installation program for the database server insilent mode

Use the response file to run the installation program in silent mode.

Procedure1. Run the installation program in silent mode.

v On Windows computers, type the following command:openpages_oei.exe -i silent -f ServerInstaller.properties

v On AIX computers, type the following command:openpages_oei.bin -i silent -f ServerInstaller.properties

2. To determine whether the installation is successful, review theOP_Home\logs\OpenPages_version_install.log

v If the installation is successful, you see a message similar to the followingtext:SummaryInstallation Successful

v On Windows computers, if the installation is not successful, review thec:\openpages_data\repository\ia\server112_se_x64\OpenPages_OEI_Install_Debug.log log file.

v On AIX computers, if the installation is not successful, review the/opt/openpages_data/repository/ia/server112_se_x64/OpenPages_OEI_Install_Debug.log log file.

v If the installation hangs when creating the database, ensure that there are noJava software (JRE or JDK) conflicts on the computer.


Running the installation program for the database client insilent mode

Use the response file to run the installation program in silent mode.

Procedure1. Run the installation program in silent mode.

v On Windows computers, type the following command:openpages_oei.exe -i silent -f clientinstaller.properties

v On AIX computers, type the following command:openpages_oei.bin -i silent -f clientinstaller.properties

2. To determine whether the installation is successful, review theOP_Home\logs\OpenPages_version_install.log

v If the installation is successful, you see a message similar to the followingtext:SummaryInstallation Successful

v On Windows computers, if the installation is not successful, review thec:\openpages_data\repository\ia\client112_ac_x64\OpenPages_OEI_Install_Debug.log log file.

v On AIX computers, if the installation is not successful, review the/opt/openpages_data/repository/ia/client112_ac_x64/OpenPages_OEI_Install_Debug.log log file.

v If the installation hangs when creating the database, ensure that there are noJava software (JRE or JDK) conflicts on the computer.

Running the installation program for the OpenPagesapplication in silent mode

Use the OpenPages application response file to run the installation program insilent mode.

Procedure1. Go to the installation program location.

v On Windows computers, go to path\OP_version_Non_Embedded_WIN64\OP_version_Non_Embedded_Installer\Disk1\InstData\VM directory, run theinstallation program in silent mode.

v On AIX computers, go to path/OP_version_Non_Embedded_AIX64/OP_version_Non_Embedded_Installer/Disk1/InstData/VM directory, run theinstallation program in silent mode.

2. Run the installation program in silent mode.v On Windows computers, type the following command:

opinstall.exe -i silent -f op-silentInstall-WL.properties

v On AIX computers, type the following command:opinstall.bin -i silent -f op-silentInstall-WAS.properties

3. To determine whether the installation is successful, review the OP_Home\logs.If the installation is not successful, the following message is displayed:Install failed. Exit Code [error code]

If the installation is successful, the logs and operating system processes indicatethat the installation succeeded.


Running the installation program for the CommandCenter insilent mode

Use the CommandCenter response file to run the installation program in silentmode.

Procedure1. Go to the installation program location.

v On Windows computers, go to \path\OP_version_CommandCenter\OpenPages_CommandCenter\Disk1\InstData\Windows\VM directory, run theinstallation program in silent mode.

v On AIX computers, go to /path/OP_version_CommandCenter/OpenPages_CommandCenter/Disk1/InstData/AIX/VM directory, run theinstallation program in silent mode.

2. Run the installation program.v On Windows computers, type the following command:

CommandCenterSetup.exe -i silent -f cc-silentInstall-WLS.properties

v On AIX computers, type the following command:CommandCenterSetup.bin -i silent -f cc-silentInstall-WAS.properties

3. To determine whether the installation is successful, review the OP_Home\logs.If the installation is not successful, the following message is displayed:Install failed. Exit Code [error code]

If the installation is successful, the logs and operating system processes indicatethat the installation succeeded


Chapter 13. OpenPages GRC Platform softwareuninstallations

You can uninstall all, or parts, of IBM OpenPages GRC Platform. Use theOpenPages and CommandCenter uninstallation programs to remove theOpenPages application and related software or to remove the CommandCenter. Toremove other software, use the vendor documentation.Related tasks:“Removing files on AIX computers after an incomplete Installation” on page 149If the OpenPages installer does not complete, files and directories might remain.These files prevent the installation program from running again. If the uninstallutility is not in the OP_Home\OpenPages\Uninstall directory, you must manuallyremove these files.

Uninstalling OpenPages applicationsUse the uninstallation program to remove IBM OpenPages GRC Platform. TheOpenPagesUninstall.exe program also removes the workflow server during theOpenPages uninstall.

However, if required, you can remove the workflow server independently. Forexample, if OpenPages did not fully install, you must remove the workflow serversoftware before you reinstall OpenPages GRC Platform.

Note: Removing OpenPages GRC Platform software does not affect the data thatis contained in the Oracle database instance. To remove your OpenPages data,delete the contents of the database instance manually.

About this task

If you purchased WebLogic Server from IBM, WebLogic Server is also removedwhen you uninstall the OpenPages GRC Platform.

If you used the silent installation option when you installed OpenPages GRCPlatform, the uninstaller automatically starts in silent mode.



Note: For AIX installations, log in as the opuser user or another non-root user.2. Stop all OpenPages servers.3. To uninstall in a Windows environment, go to the OP_Home\OpenPages\

Uninstall directory.a. Right-click the OpenPagesUninstall.exe program and select Run as

Administrator.b. Click Yes when prompted to start the uninstallation.

4. To uninstall in an AIX environment, open a shell.a. Open an AIX shell.b. Go to the OP_Home/OpenPages/Uninstall directory

141

c. Run the OpenPagesUninstall script.5. Optional: To uninstall workflow server in a Windows environment, from the

Windows Start menu, click All Programs > Interstage Business ProcessManager > Uninstall.a. Right-click Uninstall and select Run as Administrator.b. Click Yes when prompted to start the uninstallation.

6. Optional: To uninstall workflow server in an AIX environment, open an AIXshella. Go to the Fujitsu_Interstage_BPM_HOME/uninst/ directory.b. Run the uninstall.sh command

7. Restart your computer to complete the uninstallation.

Results

After the uninstall process is complete, a number of folders remain on theapplication server. Manually remove the remaining folders and files, such as theOP_Home directory.

Note: A removal log file, OpenPages_uninstaller.log, is created in theOP_Home\logs directory.

If the Cognos_HOME, CommandCenter_HOME, or Oracle_HOME directories are in theOP_HOME directory, do not delete them.

Optional: Uninstalling the workflow serverThe OpenPagesUninstall.exe file removes the workflow server when you uninstallthe OpenPages. If OpenPages does not fully install, you can remove the workflowserver software before attempting to re-install OpenPages



Note: For AIX installations, log on as the opuser user or another non-root user.2. For Windows computers, find the workflow server uninstall program using the

Window Start menu. By default, Start > All Programs > Interstage BusinessProcess Manager > Uninstall.a. Right-click Uninstall > Run as Administrator.b. When prompted to start the uninstall, click Yes

c. Open an AIX shell and navigate to the <Workflow_Home>/_uninst/ directory.d. Execute the uninstall.sh command.

3. For AIX computers, open an AIX shell and go to the Workflow_Home/_uninst/directory and run the uninstall.sh script.

4. When the uninstall process is finished, restart the machine.

Uninstalling CommandCenterUse the uninstallation program to remove the CommandCenter.


Before you begin

Note: If the application or reporting server components are on the same computeras the database server, you must remove the database before removing any servercomponents.

Procedure1. Log on to the reporting server as a user with administrative privileges.2. To uninstall on Windows computers, do the following steps:

a. In Windows Explorer, and go to theCommandCenter_HOME_Uninstall_OpenPages_CommandCenter directory.

b. Right-click the Uninstall_OpenPages_version_CommandCenter.exe programand select Run as Administrator.

c. Click Yes when prompted to start the uninstall.3. To uninstall on AIX, do the following steps:

a. Open an AIX shellb. Go to the CommandCenter_HOME/Uninstall_Opepages_CommandCenter directory.c. Run the Uninstall_OpenPages_version_CommandCenter command.

4. Restart your computer to complete the uninstallation.

Chapter 13. OpenPages GRC Platform software uninstallations 143


Appendix. Troubleshooting problems

Troubleshooting is a systematic approach to solving a problem. The goal oftroubleshooting is to determine why something does not work as expected andhow to resolve the problem.

Review the following table to help you or customer support resolve a problem.

Table 63. Troubleshooting actions to prevent problems

Action Description

Apply all known fix packs, service levels,or program temporary fixes (PTF).

A product fix might be available to fix theproblem.

Ensure that the configuration issupported.

Review the software and hardwarerequirements.

Look up error message codes by selectingthe product from the IBM Support Portal(http://www.ibm.com/support/entry/portal) and then typing the error messagecode into the Search support box.

Error messages give important information tohelp you identify the component that iscausing the problem.

Reproduce the problem to ensure that itis not just a simple error.

If samples are available with the product, youmight try to reproduce the problem by usingthe sample data.

Check the installation directory structureand file permissions.

The installation location must contain theappropriate file structure and the filepermissions.

For example, if the product requires writeaccess to log files, ensure that the directory hasthe correct permission.

Review relevant documentation, such asrelease notes, technotes, and provenpractices documentation.

Search the IBM knowledge bases to determinewhether your problem is known, has aworkaround, or if it is already resolved anddocumented.

Review recent changes in your computingenvironment.

Sometimes installing new software might causecompatibility issues.

If you still need to resolve problems, you must collect diagnostic data. This data isnecessary for an IBM technical-support representative to effectively troubleshootand assist you in resolving the problem. You can also collect diagnostic data andanalyze it yourself.

Troubleshooting resourcesTroubleshooting resources are sources of information that can help you resolve aproblem that you have with a product. Many of the resource links provided canalso be viewed in a short video demonstration.

To view the video version, search for "troubleshooting" through either Googlesearch engine or YouTube video community.

145

http://www.ibm.com/support/entry/portal/

Support PortalThe IBM Support Portal is a unified, centralized view of all technical support toolsand information for all IBM systems, software, and services.

Use IBM Support Portal to access all the IBM support resources from one place.You can adjust the pages to focus on the information and resources that you needfor problem prevention and faster problem resolution. Familiarize yourself with theIBM Support Portal by viewing the demo videos (https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos).

Find the OpenPages GRC Platform content that you need by selecting yourproducts from the IBM Support Portal (http://www.ibm.com/support/entry/portal).

Service requestsService requests are also known as Problem Management Records (PMRs). Severalmethods exist to submit diagnostic information to IBM Software Technical Support.

To open a service request, or to exchange information with technical support, viewthe IBM Software Support Exchanging information with Technical Support page(http://www.ibm.com/software/support/exchangeinfo.html). Service requests canalso be submitted directly by using the Service requests (PMRs) tool(http://www.ibm.com/support/entry/portal/Open_service_request) or one of theother supported methods that are detailed on the exchanging information page.

OpenPages Customer CenterThe IBM OpenPages Customer Center provides specific information, updates, andtroubleshooting resources for IBM OpenPages GRC Platform.

To view OpenPages troubleshooting information, access the OpenPages CustomerCenter (http://www.ibm.com/software/analytics/openpages/customercenter).

Fix CentralFix Central provides fixes and updates for your system software, hardware, andoperating system.

Use the pull-down menu to go to your product fixes on Fix Central(http://www.ibm.com/support/fixcentral). You might also want to view Gettingstarted with Fix Central (http://www.ibm.com/systems/support/fixes/en/fixcentral/help/getstarted.html).

Knowledge basesYou can often find solutions to problems by searching IBM knowledge bases. Youcan optimize your results by using available resources, support tools, and searchmethods

You can find useful information by searching the information center for IBMCognos, but sometimes you must look beyond the information center to resolveproblems.

IBM Support Portal

The portal provides tools and information for all IBM systems, software,and services. The IBM Support Portal provides you with access to the IBM


https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos


http://www.ibm.com/software/support/exchangeinfo.html

http://www.ibm.com/support/entry/portal/Open_service_request

http://www.ibm.com/software/analytics/openpages/customercenter/

http://www.ibm.com/software/analytics/openpages/customercenter/

http://www.ibm.com/support/fixcentral/

http://www.ibm.com/systems/support/fixes/en/fixcentral/help/getstarted.html

http://www.ibm.com/systems/support/fixes/en/fixcentral/help/getstarted.html

electronic support portfolio from one place. You can customize the pages tofocus on the information and resources that you need for problemprevention and faster problem resolution.

Find the OpenPages GRC Platform content that you need by selecting yourproducts from the IBM Support Portal (http://www.ibm.com/support/entry/portal).

From the IBM Support Portal, you can search technotes and APARs(problem reports).

IBM masthead search

Use the IBM masthead search by typing your search string into the Searchfield at the top of any ibm.com page.

External search engines

Search for content by using any external search engine, such as Google,Yahoo, or Bing. If you use an external search engine, your results are morelikely to include information that is outside the ibm.com® domain.However, sometimes you can find useful problem-solving informationabout IBM products in newsgroups, forums, and blogs that are not onibm.com.

Tip: Include “IBM” and the name of the product in your search if you arelooking for information about an IBM product.

Installation log filesThe installation programs write errors and other information to the log files. Uselog files to troubleshoot problems.

The following logs are created during the installation.

Cognos Business IntelligenceLogs related to the Cognos software installations are created in theCognos_Home\instlog directory.

Other log files are in the Cognos_Home\logs\cogserver.log file.

Framework generationLogs related to the framework generator are stored in theOP_HOME\framework\logs directory on the reporting server:v framework-generator.log

v script-player-error.log

v script-player.log

Framework Manager action logs are stored in the OP_HOME\framework\FrameworkGenerator\output directory on the application server.

Framework Manager model files, such as model.xml are stored on theCognos Business Intelligence server in the folder specified during theinstallation.

Installation issues and solutionsError messages and log files provide you with information about errors that occurduring the installation process. Use the error messages and log files to determinewhich part of the process failed.

Appendix. Troubleshooting problems 147


Review common problem scenarios, recovery methods, and ways to get help if youencounter a problem during software installation. You can diagnose problemswhen the installation and configuration is unsuccessful.

Uninstalling OpenPages with an Oracle database before youreinstall

In test or development environments, you might be required to uninstallOpenPages GRC Platform or remove the OpenPages database in Oracle databaseserver before you reinstall. You must completely uninstall before you reinstall.

Procedure1. Log on a computer that has SQL*Plus as a user, such as SYSTEM, who has

database administration permissions.2. Run the following SQL statements:

drop user <workflow_user> CASCADE;drop user <openpages_user> CASCADE;drop user <cognos_user> CASCADE;

Note: Drop the cognos_user if the OpenPages database and the Cognos contentstore schemas are in the same Oracle database. If you use a separate databasefor the Cognos content store, dropping the cognos_user is not required.

3. Run the following SQL statements to drop the default tablespaces and datafiles:drop tablespace AURORA including contents and datafiles;drop tablespace INDX including contents and datafiles;drop tablespace AURORA_SNP including contents and datafiles;drop tablespace AURORA_TEMP including contents and datafiles;drop tablespace AURORA_NL including contents and datafiles;drop tablespace AURORA_NLI including contents and datafiles;drop tablespace AURORA_CLOB_DATA including contents and datafiles;drop tablespace AURORA_DOMAIN_INDX including contents and datafiles;drop tablespace IFLOWDB including contents and datafiles;drop tablespace IFLOWTEMPDB including contents and datafiles;drop tablespace COGNOS including contents and datafiles;

4. Run the following script to drop the Oracle data pump storage directory.drop directory <OP_DATAPUMP_DIRECTORY>;

5. Uninstall IBM OpenPages GRC Platform Modules.For more information, see the IBM OpenPages GRC Platform Modules InstallationGuide.

6. Use the uninstallation programs to uninstall IBM OpenPages GRC Platform.7. If required, remove environment variables that reference OpenPages GRC

Platform, or Cognos BI, or both products.8. Restart the servers.9. Remove existing OpenPages application or Cognos BI installation directories.

The following table lists examples of the installation directories for OpenPagesand Cognos BI components

Table 64. Example directory locations for OpenPages and Cognos BI components

Installation directoryLocation on Windowsoperating system

Location on AIX operatingsystem

OpenPages

(OP_HOME)

C:\OpenPages /opt/OpenPages


Table 64. Example directory locations for OpenPages and Cognos BIcomponents (continued)

Installation directoryLocation on Windowsoperating system

Location on AIX operatingsystem

Fujitsu Interstage BPM

(Workflow_HOME)

C:\Fujitsu\InterstageBPM /opt/Fujitsu/InterstageBPM

CommandCenter

(CC_HOME)

C:\OpenPages\CommandCenter /opt/OpenPages/CommandCenter

Cognos BI

(Cognos_HOME)

C:\IBM\cognos\c10_64 /opt/IBM/cognos/c10_64

10. Review the TEMP or TMP directories for temporary installation files that mightexist.The location of temporary directories varies. The location depends on theenvironmental variables that are set during the installation process.For Windows operating systems, common temporary directory locationsincludev C:\temp

v C:\Users\<user_name>\AppData\Local\Temp

For AIX operating system, a common temporary file location is /tmp.11. Remove OpenPages application shortcuts that still exist in the Start menu.12. On AIX computers, remove any related remaining files and directories in the

home directory of the user who installed or uninstalled OpenPages.Remove the following files and directories:v .com.zerog.registry.xml

v IBM OpenPages GRC Platform

v IBM OpenPages GRC Platform - CommandCenter

v OpenPages

Removing files on AIX computers after an incompleteInstallation

If the OpenPages installer does not complete, files and directories might remain.These files prevent the installation program from running again. If the uninstallutility is not in the OP_Home\OpenPages\Uninstall directory, you must manuallyremove these files.

About this task

You must remove references to OpenPages and the workflow server (IBPM) fromthe profileRegistry.xml file. This file lists WebSphere Application Server profilesand profile configuration data.

The file contains two listings for the deployment manager: OpenPagesDmgr andIBPMDmgr, and a listing for each node. For example: server_name-OPNode1,server_name-IBPMNode1, server_name-OPNode2, server_name-IBPMNode2.


Procedure1. Log on to the application server as a non-root user with administrative

privileges and full access to the local server drives.2. Open an AIX shell.3. Remove the OP_Home directory.

a. Go to the OP_Home directory.b. Recursively remove the directory.

4. Uninstall the workflow server.a. Go to the Workflow_Home/_uninst/ directory.

The Workflow_Home is the installation location of bFujitsu Interstage BPM.b. Type uninstall.sh.

5. Remove any entries for OpenPages and IBPM (workflow server) in theprofileRegistry.xml file.a. Go to the WAS_Home/properties directory.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"augmentortemplate="/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 application server.

Results

After these files are removed and the profileRegistry.xml file is returned to itsprior state, you can reinstall the OpenPages application.

Manually loading the configuration data after a newinstallation

The installation program for OpenPages GRC Platform automatically loads theOpenPages GRC Platform data and enables user access to the standard CognosBusiness Intelligence reports. In limited situations, you can manually load thelevel-0 schema.

Before you begin

OpenPages GRC Platform must be installed.

The OpenPages and workflow (IBPM) services must be running.

About this task

When you install the OpenPages application, On the Storage and ConfigurationInformation page, you are prompted to choose whether to load configuration data.


If you select No, and the default configuration is not already loaded, you mustmanually load the level-0 schema and the CommandCenter data.

Procedure

To manually load the level-0 schema, use the following steps:1. Log on to the OpenPages admin server as a user with administrative privileges.2. Go to the OP_HOME/addon_module/loaderdata directory.3. Make a backup copy of the following script file:

v For Windows installations, back up the schema_loader_properties.bat file.v For AIX installations, back up the schema_loader_properties.sh file.

4. Open the original schema_loader_properties file in a text editor.5. In the following line, update the password for the OpenPages application Super

Administrator.v For Windows installations:

SET OPXUserName=Super_Administrator_user_nameSET OPXUserPassword=********

v For AIX installations:OPXUserName=Super_Administrator_user_nameOPXUserPassword=********

The default user name is OpenPagesAdministrator.The password for the OPXUserName user is masked by asterisks (***). Replace themask with clear text. After the default configuration data is loaded, you canmanually mask the password value with asterisks (***).

6. Save and close the file.7. To load the default OpenPages GRC Platform configuration, run the following

script:v For Windows installations, run the openpages-level0-loader-data.bat file.

Tip: Redirect the output to a log file so that you can conveniently track theprogress:

openpages-level0-loader-data.bat > openpages-level0-loader-data.log

v For AIX installations, run the openpages-level0-loader-data.sh file.

Tip: Redirect the output to a log file so that you can conveniently track theprogress:

./openpages-level0-loader-data.sh > openpages-level0-loader-data.log

The script takes awhile to finish loading the data. For example, the data mighttake two hours to load.

8. Restart the OpenPages services.

OP-03620: The Reporting Schema has not been instantiatederror

If you log on to the OpenPages home page, http://server_name:7009/openpages,and have not created the reporting schema, an error message is displayed.

The default OpenPages application port is 7009.

A message similar to the following error message is displayed:


The Home Page cannot be viewed without a valid Reporting Schema.Please contact your System Administrator. OP-03620:The Reporting Schema has not been instantiated. Please instantiate itbefore executing this operation.

To resolve the problem, disable System Admin Mode, and generate the reportingschema.

Procedure1. In a web browser, open the OpenPages application:


2. Log on to the OpenPages application as a user with administrative privileges.3. For System Admin Mode, switch from Disabled to Enabled.4. From the menu bar, click Administration and select Reporting Schema.5. Click Create.6. After the create operation finishes, click System Admin Mode to switch from

Enabled to Disabled.7. From the menu bar, click Administration > Reporting Framework >

Generation.8. On the Reporting Framework Operations page, click Update.9. In the Reporting Framework Generation window, under Framework

Generation, select the Framework Model and Labels and other options youwant for the relational data model.

10. Click Submit.11. To view the progress of the update, click Refresh.

The Percent Complete column on the Reporting Framework Operations tableupdates the percentage of completion.


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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service. This document maydescribe products, services, or features that are not included in the Program orlicense entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

153

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationLocation Code FT0550 King StreetLittleton, MA 01460-1250U.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 document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only. Thisinformation is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


Copyright

Licensed Materials - Property of IBM Corporation.

© Copyright IBM Corporation, 2003, 2013.

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

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform 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 theseprograms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM for the purposes of developing, using, marketing, ordistributing application programs conforming to IBM's application programminginterfaces.

Trademarks

IBM, the IBM logo and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.

The following terms are trademarks or registered trademarks of other companies:v Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered

trademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

v Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

v Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

v UNIX is a registered trademark of The Open Group in the United States andother countries.

v Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “ Copyright andtrademark information ” at www.ibm.com/legal/copytrade.shtml.

Notices 155

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml


Index

Aaccess-web-browser 87add

cluster members 4administrator

Super Administrator 11AIX installations

creating database server users 12AL32UTF8 character set 31Apache web server

load-balancing (Windows) 102Apache Web Server

configuring on AIX computers 46configuring on Windows computers 45

application serveradding after install 4configuring single sign-on 115default port 24installing 53installing WebLogic 19paging file size and 84, 85post-install tasks 81, 85scaling and 95server topology 5software prerequisites 7

application serversprerequisite software 8

architectureplatform 1

audience vii

Ccertificates

secondary CommandCenter 112client systems

prerequisites 7clustered environment

about 95add member to 4configuring 97load balancing and 110member systems, adding 4

Cognos Business Intelligenceinstalling 41report server 5

command blockcreating for OpenPages data sources 75

CommandCentercreating installation directory 67framework generator 7host setting 74, 113installation worksheet 67installing 68port setting 74, 113port settings, changing 74, 113post-installation tasks 72scaling and 95silent installations 140

concurrency conflict 84

configuration datamanually loading after installation 150

configuringmulticasting 23

content storeconfiguring a connection 46manually creating tablespace and user 73

content store databaseoverview 6

creatingdatabase schema 34tablespaces and users 35

DData Execution Prevention (DEP)

enabling 17database client

64-bit installations 49database components

creating 35database instance

create 31installing 31

database listenerinstalling 30

database schemamanually creating 34

database schemascustom installations 51

database servercreating a database instance 31default port 24dependencies 28instance, installing 31listener, installing 30net service name, adding 33OpenPages repository 5prerequisites 7server topology 5standard objects 28

database server connectionstesting 38, 62

debuglog files 147

default definition valuesverifying 35

documentationrelated information vii

Eenvironment variables

reporting server 66reporting server on Windows operating system 65setting 50

error messagesOP-03620 152

157

FFix Central

getting fixes 146Fujitsu Interstage BPM

workflow server 5

Ggroups

creating for AIX installations 12

Hhorizontal scaling

about 95

IIIS web server

configuring 43installation

default ports 24setting environment variables 50

installing64-bit Oracle database clients 49troubleshooting 148

Kknowledge bases

masthead search 146

LLDAP

disable 87listener

installing 30load balancing

configurations 4raising the Oracle connection limit 97

load-balancingabout 110configuring single signon 116reporting server configuration 110

log filesinstallation 147

MMicrosoft Internet Information Services

See IISmulticasting

Fujitsu Interstage BPM 23

Nnet service name

instanceadding 33

OOpenPages

add new instance 4cluster member, add 4default ports 24multicasting 23scaling and 95

OpenPages applicationadding after install 4concurrency conflict 84configuring single sign-on 115multiple users 84post-install tasks 81, 85

OpenPages CommandCenterextracting installation files 65

OpenPages Customer Centertroubleshooting resources 146

OpenPages databasedatabase server 5

OpenPages repositorydatabase server 5

Oracle Client.See also database clientinstalling on OpenPages application servers 49

Oracle database serverinstalling 28

Oracle standard objects 28ORACLE_HOME

setting 50

Ppaging file size

increasing on application server 84, 85increasing on reporting server 84, 85

PATH variablemodifying for installation 50ORACLE_BASE, removing 27ORACLE_HOME, adding to 50ORACLE_HOME, removing 27PERL5LIB, removing 27TNS_ADMIN, removing 27

platformarchitecture 1

portsdefault 24fixed 24

post-installationapplication server and 81, 85CommandCenter tasks 72

prerequisite softwareapplication servers 8

prerequisitesclient systems 7software 7

Problem Management Recordsservice requests

See Problem Management Records

Rreport server

server topology 5reporting schema

creating 72manually creating 73


reporting serverconfiguring single signon 119default port 24environment variables on Windows operating system 65load balancing and 110paging file size and 84, 85port settings, changing 74, 113prerequisites 7prerequisites tasks 65scaling and 95software requirements 9

reporting serverssetting environment variables 66

reportsgenerating the framework 72

response filesCommandCenter installations 122OpenPages application server installations 122

Ssecurity

securing access to the CommandCenter 76server topology

application server 5database server 5report server 5workflow server 5

serverstopology 1

service name, adding 33service requests

opening Problem Management Records (PMR) 146sharing network storage 99silent installations

CommandCenter 140response file for CommandCenter 122response file for OpenPages application servers 122

single serverconfiguring 77

single signonconfiguring for logging out 116configuring OpenPages interface 115disabling 118

softwarerequirements 7

software requirementsreporting server 9

SSLwith OpenPages 87

SSOSee single signon

startingOpenPages 87OpenPages with Web browser 87

Super Administrator 11Support Portal

overview 146

Ttablespaces and users

creating 35third-party software

requirements 7topology

servers 1troubleshooting

getting fixes 146installation issues and solutions 148installation log files 147OpenPages Customer Center 146reporting schema not instantiated error 152resources 145Support Portal 146understanding symptoms of a problem 145video documentation resources 145

Uupdate-storage script 99users

creating for AIX installations 12

Vvertical scaling

about 95video documentation

YouTube 146virtual directories

configuring for IIS web server 45virtualization

supported configurations 9

Wweb server

configuration options 43installing WebSphere Application Server 20

WebLogic Serverinstalling 19

WebSphere Application Serverinstalling 20

workflow serverinstalling 53server topology 5

Index 159

Date post:	26-Aug-2020
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times

IBM OpenPages GRC Platform Version 6.2.1: Installation...

Documents