IBM OpenPages GRC Platform 6.0.1public.dhe.ibm.com/software/data/cognos/...IBM® OpenPages® GRC Platform . Version 6.0.1 FP3 . Patch ReadMe . December 2011

IBM® OpenPages® GRC Platform

Version 6.0.1 FP3 Patch ReadMe December 2011

IBM OpenPages GRC Platform 6.0.1 FP3 Patch Installer 2 of 29

Copyright Information Licensed Materials – Property of IBM Copyright IBM Corporation 2003, 2011. All rights reserved.

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

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

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

IBM Corporation Location Code FT0 550 King Street Littleton, MA 01460 U.S.A.

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

Document Release Information Last Modified: December 23, 2011 3:58:33 PM


Table of Contents About this Patch Installer..............................................................................................4 Enhancements and Bug Fixes ........................................................................................4

Enhancements.........................................................................................................4 Bug Fixes ...............................................................................................................5 Verifying Pre-Requisites............................................................................................5

Install the Prerequisite Software ...........................................................................5 Verify Space Requirements for the Patch Installer....................................................5 Confirm Required Information is Available ..............................................................6

Backing Up the Existing IBM OpenPages GRC Platform Environment....................................6 Task 1: Backing Up the Entire OpenPages Environment .................................................6

Task A: Update the CommandCenter Backup Utility – 6.0.1.1 only .............................6 Task B: Modify the op-cc-backup-restore.xml File – 6.0.1.1 only ...............................7 Task C: Run the OpenPages and CommandCenter Backup Utilities .............................7

Task 2: Backing Up Directories and Files Needed for a Rollback ......................................7 Selecting the Type of Installation...................................................................................9 Installing the Patch.................................................................................................... 10

Task 1: Verify That Servers Are Running ................................................................... 10 Task 2: Use SQL Scripts to Update the Database Server .............................................. 10 Task 3: Launch the Patch Installer Program............................................................... 11 Task 4: Choose the Type of Installation..................................................................... 12 Task 5: Enter OpenPages Application Information....................................................... 12 Task 6: Enter OpenPages Administrator Information ................................................... 14 Task 7: Enter Reporting Server Information............................................................... 14 Task 8: Enter OpenPages Database Server Information ............................................... 15 Task 9: Start the Upgrade....................................................................................... 15 Task 10: Start Servers ........................................................................................... 16

Locating Patch Installation Log Files ............................................................................. 16 Patch Log Files for the Application, Workflow, and Reporting Servers............................. 16 Patch Log Files for the Database Server .................................................................... 16

Post-Installation Tasks ............................................................................................... 17 Task 1: Update the IBM Cognos Server and Dashboards.............................................. 17 Task 2: Limit Transactions of the OpenPages and Workflow Database Users ................... 18 Task 3: Update the CCH® TeamMate R8 Integration Loader Files ................................. 19

Creating Back Up Directories in the Event of a Rollback................................................... 20 Task 1: Stop all Services......................................................................................... 20 Task 2: Create a Backup Directory ........................................................................... 20 Task 3: Backup OpenPages Application Directories...................................................... 20 Task 4: Backup the Interstage BPM Directory............................................................. 21 Task 5: Backup IBM Cognos Directories .................................................................... 21 Task 6: Backup CommandCenter Directories and Files................................................. 22 Task 7: Start all Services ........................................................................................ 22

Uninstalling This Patch ............................................................................................... 23 Task 1: Stop all Services......................................................................................... 23 Task 2: Restore OpenPages Application Directories and File ......................................... 23 Task 3: Restore the Workflow Directory .................................................................... 24 Task 4: Restore IBM Cognos Directories .................................................................... 24 Task 5: Restore OpenPages CommandCenter Directories and File ................................. 25 Task 6: Update the OpenPages Framework Model Generator Service ............................. 25 Task 7: Restore the Database.................................................................................. 26 Task 8: Start all Services ........................................................................................ 26

Documentation Updates ............................................................................................. 26 Notices .................................................................................................................... 27


About this Patch Installer This patch installer updates the IBM® OpenPages® GRC Platform environment from version 6.0.1.x or higher to version 6.0.1.3 for either a Windows/WebLogic Server or AIX/WebSphere Application Server installation. It is an incremental update. Depending on your environment and preferences, you can update the database server by using the patch installer program or by manually running SQL scripts. The patch installer program automatically runs the SQL database update scripts in the proper order, and depending on your configuration, can be run either from the application server or directly on the database server. Important! You must use the patch installer program to update the OpenPages application, workflow, and reporting servers. The patch installer must be run on all application and reporting servers.

Enhancements and Bug Fixes The following enhancements and bug fixes are included in this release. The numbers shown in square brackets after a description, such as [Q 13067 or A PM53631], represent a case number: Q= Quality Center ID (internal defect tracking) A= Authorized Problem Analysis Report (APAR) ID S= SalesForce ID Enhancements The following enhancements have been introduced in IBM OpenPages GRC Platform 6.0.1.3.

• Enable/Disable Triggers. You can now configure a setting in OpenPages to disable all configured triggers. When OpenPages | Applications | GCRM | Disable Triggers is set to true, all triggers are disabled. When set to false, all triggers are enabled. [Q12780] Disabling triggers allows you to perform operations, such as data loading, without the additional processing overhead of the trigger mechanism. How and when you would use this feature depends upon the operation being performed and whether any triggers would fire during the operation.

The ObjectManager tool can change this setting, based on a new property in the ObjectManager.properties file, configuration.manager.disable.triggers. When ObjectManager is run, if the configuration.manager.disable.triggers value is true, the ObjectManager tool will change the Disable Triggers setting to true if it is false. If configuration.manager.disable.triggers value is false, ObjectManager will not change the Disable Triggers setting. When the ObjectManager activity is complete, ObjectManager will return the Disable Triggers setting to false (if it was set to false when ObjectManager started).

• Change to User Role Assignments in Reports. The Administrator Permissions, Roles

by User, and User Role Assignments reports have been changed to hide inactive users. Previously, these reports displayed inactive users and their assigned roles. [S 54529]


Bug Fixes • The error message OP-08009 Failed to login to workflow engine caused by 6.0.1

upgrade has been corrected. [S 54392] • The default ObjectManager connect strings now run properly on Windows and AIX.

[S 52535] • Framework generation now completes successfully when running OpenPages on a

Japanese-language operating system. [54608] • An improper error message that may have displayed when attempting to delete a

system generated folder has been corrected. [Q 12782] • FastMap loading performance has been enhanced. [Q 12828] • The sporadic appearance of an OP-12000 error when viewing reporting fragments in a

load-balanced environment has been corrected. [Q 12867] • The OPRestore utility now functions as expected when database schema names are

not OPENPAGES and OPWORKFLOW. [Q 12876] • Upgrading from OpenPages versions 5.5.2.5 or 5.5.3 will complete properly, after

running a script to incorporate new columns in the GROUPMEMBERSHIPS table. The script was required during the OpenPages 6.0.1 upgrade and does not need to be executed for 6.0.1.3. [A PM49358]

• The time out problem encountered during large copies or moves as been corrected. [Q 12969]

• A JavaScript error is no longer displayed when selecting items after using the Next page link on List View pages. [Q 13045]

• The Entity Move/Rename Utility file for the AIX environment, batch-entity-move-rename.sh, has been restored. [Q 13067]

• An improper FastMap Transaction Timeout setting behavior as been corrected. [A PM53631]

• Transaction cleanup for failed FastMap loads as been corrected. [Q 13109] Verifying Pre-Requisites Before you begin, make sure your system and environment meet the following prerequisites. Install the Prerequisite Software Prior to installing patch version 6.0.1.3, IBM OpenPages GRC Platform version 6.0.1.1 or higher must be installed. Verify Space Requirements for the Patch Installer A minimum of 5 GB hard disk space is required to install this patch on a single vertical cluster in either a Microsoft Windows or IBM AIX environment. The required disk space may vary depending on the number of server instances in your environment.


Confirm Required Information is Available The 6.0.1.3 patch requires the following information. Please ensure it is readily available.

• For the OpenPages application update: o The existing installation path of the OpenPages application server and the

administrative server port number; o The existing installation path of the Interstage BPM workflow server and the

administrative server port number; o The existing installation path of the Oracle WebLogic Server; o The Oracle WebLogic Server or IBM WebSphere Application Server admin user

name and password; o The number of cluster members configured on the machine; o The user name and password of the OpenPages application super

administrator. • For the database update:

o The Oracle database alias name; o The existing location of the Oracle Client folder; o The OpenPages database user name and password.

• For the CommandCenter update: o The existing installation path of the Cognos server; o The existing installation path of the CommandCenter folder.

Backing Up the Existing IBM OpenPages GRC Platform Environment Before you start the patch update process, perform the following tasks. Task 1: Backing Up the Entire OpenPages Environment

These tasks are required. Use the OPBackup utility to back up the necessary OpenPages files and database content on the server where it is run. Task A: Update the CommandCenter Backup Utility – 6.0.1.1 only This fix pack contains a script to upgrade the CommandCenter backup utility. Use the following instructions to run the script prior to backing up CommandCenter in your 6.0.1.1 OpenPages GRC Platform environment.

Steps:

1. Log on as an administrative user to a machine with SQL*Plus and access to the database server.

2. From the IBM OpenPages GRC Platform Patch Installer 6.0.1.3 media kit, copy the entire OP_6.0.1.3_Database directory to a local directory.

3. Open a Command Prompt window (using the Run as Administrator option) or AIX shell and navigate to the OP_6.0.1.3_Database directory you just copied.

4. Launch SQL*Plus as the CommandCenter database user using the following command: sqlplus <cc_user>/<cc_password>@<SID> Where: <cc_user> is the user name for accessing the CommandCenter database <cc_password> is the password for the OpenPages database account <SID> is the Oracle System Identifier (for example, OP or OP11G)

5. Run the following SQL script.

@OP-6-0-1-2-cc-schema-upgrade.sql


Task B: Modify the op-cc-backup-restore.xml File – 6.0.1.1 only To prevent an invalid logon message for the Data Pump location in your 6.0.1.1 OpenPages GRC Platform environment, use the following instructions to manually edit the password property in the op-cc-backup-restore.xml file.

Steps:

1. Log on to the reporting server as a user with administrative privileges and full access to the local server drives.

2. Navigate to the <CC_Home>\tools\bin directory as follows. Where: <CC_Home> represents the installation location of the CommandCenter application, by default:

C:\OpenPages\CommandCenter Windows /opt/OpenPages/CommandCenter AIX

3. Open the op-cc-backup-restore.xml file in a text editor of your choice. 4. Search for and then change the value in the following line of code.

Note: This line appears twice in the file and the value must be changed in both locations.

From this: <arg value="${DB_CC_USER}/${DB_CC_USER}@${DB_ALIAS}" />

To this: <arg value="${DB_CC_USER}/${DB_CC_PWD}@${DB_ALIAS}" />

5. When finished, save and close the file.

Task C: Run the OpenPages and CommandCenter Backup Utilities

Run the OpenPages backup (OPBackup) and CommandCenter backup (OPCCBackup) utilities to completely back up your OpenPages database and application, and CommandCenter Content Store and files. Note: If this is the first time you are using the CommandCenter backup utility (OPCCBackup), make sure you configure the Oracle ‘datapump’ storage directory before running this utility. For details on using the OpenPages and CommandCenter backup utilities and configuring the Oracle Data Pump directory for first-time use, see the “Using Utilities” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide. Task 2: Backing Up Directories and Files Needed for a Rollback

This task is recommended and applies to both Windows and AIX environments. In the event it is necessary to uninstall the IBM OpenPages GRC Platform 6.0.1.3 patch and revert to the previous 6.0.1.x patch level, this section identifies the directories and files that will be required for the uninstall and rollback process. For specific details of which files to back up, see Creating Back Up Directories in the Event of a Rollback. Steps:

1. Log on to the admin server as a user with administrative privileges and full access to the local server drives. For AIX, use non-root user, such as the user you created for the IBM OpenPages GRC Platform installation, for example opuser.

2. Stop all OpenPages services, including the following, on each server in your environment:

• OpenPages application and workflow services • CommandCenter service • OpenPages Framework Model Generator service • IBM Cognos 8 Go! Dashboard service (if installed)

Note: For details on stopping services, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.


3. Create the following backup directories in a location that is different from the installation location. For example:

Operating System Example backup directory path Windows C:\OpenPages6011Backup

C:\OpenPages6011Backup\Fujitsu\InterstageBPM C:\OpenPages6011Backup\Cognos\cognos\c8 C:\OpenPages6011Backup\CommandCenter

AIX /opt/OpenPages6011Backup /opt/OpenPages6011Backup/Fujitsu/InterstageBPM /opt/OpenPages6011Backup/Cognos/cognos/c8 /opt/OpenPages6011Backup/CommandCenter

4. Copy the following directories and file from the <OP_Home> installation directory to the

backup directory location OpenPages6011Backup\OpenPages\:

<OP_Home>\applications <OP_Home>\aurora <OP_Home>\bin <OP_Home>\OpenPagesDomain <OP_Home>\profiles <OP_Home>\openpagesregistry.xml

5. Copy the entire <Workflow_Home> installation directory to the backup directory location OpenPages6011Backup\Fujitsu\InterstageBPM.

6. Copy the following directories from the <Cognos_Home> installation directory to the backup directory location OpenPages6011Backup\Cognos\cognos\c8. <Cognos_Home>\webapps\p2pd\WEB-INF\lib <Cognos_Home>\ configuration

7. Copy the following directories and file from the <CC_Home> installation directory to the backup directory location OpenPages6011Backup\CommandCenter. <CC_Home>\apache-tomcat-6.0.26 <CC_Home>\tools\bin <CC_Home>\openpagesregistry.xml

8. Start all services including the following: • OpenPages application and workflow services • CommandCenter service • OpenPages Framework Model Generator service • IBM Cognos 8 Go! Dashboard service (if installed)

Note: For details on starting services, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.


Selecting the Type of Installation Before you update your system, use the following scenarios to help you decide where to run the patch installer in your particular environment:

• Scenario 1: The application, database, and reporting servers are on separate machines • Scenario 2: The application and database servers are on the same machine with the

reporting server on a separate machine • Scenario 3: The application, database, and reporting servers are on the same machine

Note: In any of these scenarios, you may choose to upgrade the database server manually, using SQL scripts. Scenario 1: The Application, Database, and Reporting Servers Are on Separate Machines If the application, database, and reporting servers are each running on different machines (for example, the application server is on Machine-1, the database server is on Machine-2, and the reporting server is on Machine-3), run the patch installer program as follows:

To update… Run the patch installer on this machine…

And select this…

An application server Application server Application The database server Any system with database

access Database

A reporting server Reporting server Reporting Scenario 2: The Application and Database Servers Are on the Same Machine with the Reporting Server on a Separate Machine If the application and database servers are running on the same machine (for example, Machine-1) with the reporting server running on a separate machine (for example, Machine-2), run the patch installer program as follows:


And select this…

An application and database server on one system

The application/database server

Application and Database

A reporting server The reporting server Reporting Scenario 3: The Application, Database, and Reporting Servers Are on the Same Machine If the application, database, and reporting servers are all running on the same machine (for example, Machine-1), use the following method. Run the patch installer program to automatically update the application, database, and reporting servers as follows.


And select this…

The application, database and reporting on one system

The application/reporting/ database server

Application, Database and Reporting


Installing the Patch To install the IBM OpenPages GRC Platform 6.0.1.3 patch, perform the following tasks. Important! Before installing the 6.0.1.3 patch, make sure you have all the required backup folders and files including those described Backing Up the Existing IBM OpenPages GRC Platform Environment. Task 1: Verify That Servers Are Running All servers need to be running during installation of the IBM OpenPages GRC Platform 6.0.1.3 patch. If any administrative or managed servers are stopped, start these servers. This is required so the patch installer program can validate user input.

• Verify that all administrative and managed servers are running, including database and reporting servers (both CommandCenter and Framework Manager).

• If this is a horizontal clustered environment then verify all managed servers are running on all non-administrative servers.

• Once the 6.0.1.3 patch installer has finished updating the application and reporting, restart the OpenPages application and reporting servers, including the administrative server.

Note: For details on starting and stopping servers, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide. Task 2: Use SQL Scripts to Update the Database Server You can manually update the database server by running SQL scripts included in the media kit. If you are not using scripts to manually update the database server, go to Task 3: Launch the Patch Installer Program. Important! If you decide to manually run SQL scripts to update the database server, you must run the SQL scripts BEFORE using the 6.0.1.3 patch installer. To update the database server using SQL scripts, follow the instructions in this section.

Steps:



3. Open a Command Prompt window (using the Run as Administrator option) or AIX shell and navigate to OP_6.0.1.3_Database directory you just copied.

4. Launch SQL*Plus as the OpenPages database user using the following command: sqlplus <openpages_user>/<openpages_password>@<SID> Where: <openpages_user> is the user name for accessing the OpenPages database. By default, this is: openpages <openpages_password> is the password for the OpenPages database account <SID> is the Oracle System Identifier (for example, OP or OP11G)


5. Run each SQL script listed in the following table in the order specified. Script Sequence Script Name

1. OP-6-0-1-3-opx-app—data-upgrade.sql

2. advance_schema_version.sql 'OpenPages 6.0.1.3'

3. advance_application_version.sql 'OpenPages 6.0.1.3'

6. When finished, log out of SQL*Plus. 7. Launch SQL*Plus as the workflow database user using the following command:

sqlplus <workflow_db_user>/<workflow_db_password>@<SID> Where: <workflow_db_user> is the OpenPages workflow user name for accessing the workflow database <opworkflow_db_password> is the OpenPages workflow password for accessing the workflow database <SID> is the Oracle System Identifier (for example, OP or OP11G)

8. Run the following SQL script: OP-6-0-1-3-wfx-schema-upgrade.sql

9. When finished, log out of SQL*Plus.

Task 3: Launch the Patch Installer Program Launch the OpenPagesPatchSetup installer program to launch the upgrade. Notes

• If this is a horizontal clustered environment, the patch installer must be installed on the administrative server first, and then on all non-administrative servers.

• You must use the patch installer program to update the OpenPages application, workflow, and reporting servers. To update the database server, you can use either the patch installer program or manually run scripts. If you choose to manually run scripts, you must run the scripts before using the patch installer program.

Steps:

1. Log on to the server where you will perform the upgrade as a user with administrative privileges and full access to the local server drives. Note: For AIX installs, log in as a non-root user, such as the user you created for the reporting server installation, for example: opuser.

2. From the IBM OpenPages GRC Platform Patch Installer 6.0.1.3 installation media, copy the entire OP_6.0.1.3_Installer\IBM OpenPages GRC Platform Patch Installer directory to the application server.

3. Open a Command Prompt window (using the Run as Administrator option) or AIX shell, and do the following:

a. Navigate to the IBM OpenPages GRC Platform Patch Installer directory you just copied. Navigate to the patch installer in the IBM OpenPages GRC Platform Patch Installer directory: Disk1\InstData\[ AIX64 or WIN64]\NoVM

b. Launch the IBM OpenPages GRC Platform patch installer program as follows:

Windows OpenPagesPatchSetup.exe

AIX OpenPagesPatchSetup.bin

4. On the Welcome screen, click Next.


Task 4: Choose the Type of Installation These instructions assume that you have read the section “About Selecting the Type of Installation” and know which installation options you want to choose. Steps:

1. On the Installation Type screen, do the following. a. Depending on your requirements, select from the following options to

automatically update your environment:

For this server… Select this option…

Perform these Tasks…

Admin Application server Application Task 5; Task 6; Task 9; Task 10 Non-Admin Application server Application Task 5; Task 9; Task 10 Reporting server Reporting Task 7; Task 9; Task 10 Database Server Database Task 8; Task 9; Task 10 Application/Database server Application AND

Database Task 5; Task 6; Task 8; Task 9; Task 10

Application/Database/Reporting server

Application AND Reporting AND Database

Task 5; Task 6; Task 7; Task 8; Task 9; Task 10

b. When finished, click Next to continue.

Note: If you have manually run scripts to update the database, you can skip running the Database option in the installer interface.

Task 5: Enter OpenPages Application Information These screens will appear when upgrading an OpenPages application server. Use the following instructions to update the OpenPages application server using the patch installer program. Steps:

1. On the OpenPages Installation Information screen, do the following. a. Enter information for the following fields:

In this field… Enter this… OpenPages Installation Folder The installation location of the existing OpenPages

application. Example: Windows c:\OpenPages AIX /opt/OpenPages

IBPM Installation Folder The installation location of the existing Fujitsu Interstage BPM workflow server. Example: Windows c:\Fujitsu\InterstageBPM AIX /opt/Fujitsu/InterstageBPM


In this field… Enter this… WebLogic Installation Folder Windows/WebLogic Only

The installation location of the existing Oracle WebLogic server. Example: Windows c:\Oracle\Middleware\wlserver_10.3

b. When finished, click Next.

2. On the OpenPages Application Information screen, do the following. a. Enter information for the following fields:

In this field… Enter this… OpenPages Admin Server Port Number

The administrative server port number used by the Oracle WebLogic Server for the OpenPages application. By default, the port number is 7001.

IBPM Admin Server Port Number

The administrative server port number used by Oracle WebLogic Server for the workflow server. By default, the port number is 49901.

Admin Server User Name

The user name for accessing the Oracle WebLogic Server Administration Console. By default, this is: weblogic

Admin Server User Password

The password for the Oracle WebLogic admin account.

Confirm Password

Re-enter the above password for confirmation.

How many cluster members do you have configured on this machine?

The number of cluster members on the current machine.

Is Security Enabled? AIX/WebSphere Application Server Only

Select one of the following: • No – if WebSphere Global Security is not

enabled. • Yes – if WebSphere Global Security is enabled,

and then proceed to the following fields: o Admin Server User Name - enter the

user name for accessing the IBM WebSphere Integrated Solutions Console.

o Admin Server User Password - enter the password for the IBM WAS admin account.

o Confirm Password - re-enter the above password for confirmation.



Task 6: Enter OpenPages Administrator Information This screen will appear when upgrading an OpenPages admin server.

Use the following instructions to update the admin server using the patch installer program.

1. On the OpenPages Application User Information screen, do the following. a. Enter information for the following fields:

In this field… Enter this… OpenPages Application User The administrative user name for

accessing the OpenPages application. By default, this is: OpenPagesAdministrator

OpenPages Application Password The password for the OpenPages administrator account.

Confirm Password Re-enter the above password.

b. Click Next.

Task 7: Enter Reporting Server Information This screen will appear when upgrading a CommandCenter reporting server. Use the following instructions to update the reporting server using the patch installer program. Steps:

1. On the OpenPages Reporting Information screen, enter information for the following fields:

In this field… Enter this… Cognos Installation Folder The installation location of the Cognos application.

Example: Windows C:\OpenPages\Cognos\cognos\c8 AIX /opt/OpenPages/Cognos/cognos/c8

OpenPages CommandCenter Folder

The location of the OpenPages CommandCenter folder. Example: Windows C:\OpenPages\CommandCenter AIX /opt/OpenPages/CommandCenter

2. When finished, click Next.


Task 8: Enter OpenPages Database Server Information This screen will appear when upgrading an OpenPages database server. Use the following instructions to update the database using the patch installer program. Steps:

1. On the OpenPages Database Information screen, do the following: a. Enter information for the following fields:

In this field… Enter this… Oracle Client Folder The location on the OpenPages application server

where the Oracle Client software is installed. Example In this example, the database and application servers are on different machines: Windows C:\openpages_data\repository\ client112_ac_x64\software AIX /opt/oracle/openpages_data/repository/ client112_ac_x64/software

Database Alias Name The TNS name of the OpenPages database instance.

OpenPages User Name The user name for accessing the OpenPages database. By default, this is: openpages

OpenPages Password The password for the OpenPages database account.

Confirm Password Re-enter the above password for confirmation.


Task 9: Start the Upgrade

This screen will appear in all upgrade scenarios.

1. On the OpenPages Database Information screen, do the following: a. Review your selections. b. Click Install. c. When finished, click Done to exit the installer.


Task 10: Start Servers This task applies in all upgrade scenarios.

Note: For details on starting and stopping servers, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.

Steps: 1. Start all application and workflow servers using the StartAllServers script. 2. Restart the reporting server (including the CommandCenter and OpenPages

Framework Model Generator services). For a horizontal clustered environment, use the following sequence to restart CommandCenter services:

a. Stop CommandCenter services on all secondary servers. b. Stop CommandCenter service on the primary server. c. Start CommandCenter service on the primary server. d. Start CommandCenter services on all secondary servers.

Locating Patch Installation Log Files If errors occur during the patch installation process, you can review the following patch installer log files for troubleshooting.

Patch Log Files for the Application, Workflow, and Reporting Servers Log files related to the OpenPages application, workflow, and reporting servers can be found on the server where you ran the patch installer:

• <OP_Home>\patch\logs\OpenPages_Patch_Installer_Debug.log • <OP_Home>\patch\logs\OpenPages_Patch_Installer_Error.log

Where: <OP_Home> is the installation location of the IBM OpenPages GRC Platform application. By default, the path is:

Windows C:\OpenPages

/opt/OpenPages AIX

Patch Log Files for the Database Server Log files related to the database server upgrade can be found on the server where you ran the database patch installer.

• <OP_Home>\patch\logs\debug\OpenPages_Patch_Installer_Debug.log

Where: <OP_Home> is the installation location of the IBM OpenPages GRC Platform application. By default, the path is: Windows C:\OpenPages

/opt/OpenPages AIX


Post-Installation Tasks Perform the following tasks after completing the upgrade to 6.0.1.3. Note: Any legacy systems with CCH® TeamMate R8 must perform Task 3: Update the CCH® TeamMate R8 Integration Loader Files. This is required for your environment. Task 1: Update the IBM Cognos Server and Dashboards

This task is required for all OpenPages environments. After you have updated your system to IBM OpenPages GRC Platform 6.0.1.3, apply the IBM Cognos 8 Interim Fix on all reporting servers in your environment. Note: If you installed these interim fixes during the upgrade to OpenPages 6.0.1.2 you must re-install the fixes for OpenPages 6.0.1.3. The IBM Cognos 8 Business Intelligence 8.4.1 Interim Fix (IF) includes important updates to the IBM Cognos server and dashboards. Steps:


2. Copy each of the following IBM Cognos download files from the media pack: • up_c8bisrvr_<operating_system>_8.4.104.1115_ml.tar.gz • up_c8bisrvr_<operating_system>_8.4.105.1172_ml.tar.gz • up_exdashboards_<operating_system>_8.4.102.64_ml.tar.gz Where: <operating_system> is the type of operating system – either winx64 (for Microsoft Windows) or aix64 (for IBM AIX)

3. Extract each of the download files into a separate directory. 4. Open IBM Cognos Configuration and stop the IBM Cognos service, if it is running. 5. Stop the following services:

• OpenPages Framework Model Generator For details, see the “Starting and Stopping the OpenPages Framework Model Generator Service” topic in the “Starting and Stopping Servers” chapter of the IBM® OpenPages® GRC Platform Administrator’s Guide.

• IBM Cognos 8 Go! Dashboard For details, see the “Starting the IBM Cognos 8 Go! Dashboard Service” topic in the “Starting and Stopping Servers” chapter of the IBM® OpenPages® GRC Platform Administrator’s Guide.

6. Open a Command Prompt window (using the Run as Administrator option) or AIX shell.


7. To update the IBM Cognos server component, navigate to the directory where you extracted the up_c8bisrvr_<operating_system>_8.4.104.1115_ml.tar.gz file.

8. Launch the IBM Cognos 8 Business Intelligence 8.4.1 Interim Fix (IF) installation wizard as follows:

Windows Double-click the issetup.exe file. AIX Type ./issetup and press Return.

9. Follow the directions in the installation wizard. Make sure you install the updates in the

same location as your existing IBM Cognos BI server components. Note: The issetup program prompts you to allow the fix pack to create a backup copy in the installation folder before copying new files.

10. To update the IBM Cognos server component, navigate to the directory where you extracted the up_c8bisrvr_<operating_system>_8.4.105.1172_ml.tar.gz file, and repeat Steps 8 and 9.

11. To update the IBM Cognos dashboard component, navigate to the directory where you extracted the up_exdashboards_<operating_system>_8.4.102.64_ml.tar.gz file, and repeat Steps 8 and 9.

12. When the update program is finished, start the IBM Cognos service as follows: a. Open IBM Cognos Configuration. b. Save the configuration. c. Start the IBM Cognos service.

Task 2: Limit Transactions of the OpenPages and Workflow Database Users

This task is optional. Run the following script to revoke the FORCE ANY TRANSACTION privilege of the OpenPages and workflow database user accounts so these accounts cannot modify XA transactions created by other users. Steps:



3. Open a Command Prompt window (using the Run as Administrator option) or AIX shell and navigate to OP_6.0.1.3_Database directory you just copied.

4. Launch SQL*Plus and log on with the sys account as sysdba. sqlplus sys/<sys_password>@<SID> as sysdba Where: <sys_password> is the password for the sys database user account. <SID> is the name of the OpenPages database instance.

5. Execute the following commands:

@OP-6-0-1-2-sysdba-xa-grants-upgrade.sql <OPENPAGES_DATABASE_SCHEMA_NAME> @OP-6-0-1-2-sysdba-xa-grants-upgrade.sql <WORKFLOW_DATABASE_SCHEMA_NAME>

6. When finished, log out of SQL*Plus.


7. Start the following services: • OpenPages Framework Model Generator service.

Note: For details, see the “Starting and Stopping the OpenPages Framework Model Generator Service” topic in the “Starting and Stopping Servers” chapter of the IBM® OpenPages® GRC Platform Administrator’s Guide.

• IBM Cognos 8 Go! Dashboard service Note: For details, see the “Starting the IBM Cognos 8 Go! Dashboard Service” topic in the “Starting and Stopping Servers” chapter of the IBM® OpenPages® GRC Platform Administrator’s Guide.

8. If this is a horizontal clustered environment, repeat this task on all remaining reporting servers in your environment.

9. When finished, update the reporting framework. For details on updating the reporting framework, see the “Managing the Reporting Schema and Framework” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.

Task 3: Update the CCH® TeamMate R8 Integration Loader Files

This task is required only for legacy systems with CCH® TeamMate R8 integrated into the IBM OpenPages GRC Platform application. To enhance security and prevent unauthorized file downloads, use the following instructions to run the ObjectManager tool to update specific data loader files. Steps:

1. Make sure that the IBM OpenPages GRC Platform application servers are running. 2. From the IBM OpenPages GRC Platform Patch Installer 6.0.1.3 media kit, copy the

entire OP_6.0.1.3_Loader-Data directory to a local directory. 3. Open a Command Prompt window (using the Run as Administrator option) or AIX

shell and navigate to OP_6.0.1.3_Loader-Data directory you just copied. 4. Use the following syntax to run the ObjectManager command to load these updated

data loader files: • teammate-core-op-config.xml • teammate-reports-op-config.xml

Syntax ObjectManager load config <OP_ADMIN_USERNAME> <OP_ADMIN_PASSWORD> <OP_6.0.1.3_KIT_LOCATION>\OP_6.0.1.3_Loader-Data <loader_file> Where: <OP_ADMIN_USERNAME> is the user name of the OpenPages super administrator account <OP_ADMIN_PASSWORD> is the password for the OpenPages super administrator account <OP_6.0.1.3_KIT_LOCATION> is the location of the OP_6.0.1.3_Loader-Data directory of the patch kit. <loader_file> is the name of the loader file. Windows Examples ObjectManager load config OpenPagesAdministrator OpenPagesAdministrator c:\temp\OP_6.0.1.3_Patch\OP_6.0.1.3_Loader-Data teammate-core-op-config.xml ObjectManager load config OpenPagesAdministrator OpenPagesAdministrator c:\temp\OP_6.0.1.3_Patch\OP_6.0.1.3_Loader-Data teammate-reports-op-config.xml AIX Examples ObjectManager.sh load config OpenPagesAdministrator OpenPagesAdministrator /opt/OP_6.0.1.3_Patch/OP_6.0.1.3_Loader-Data teammate-core-op-config.xml ObjectManager load config OpenPagesAdministrator OpenPagesAdministrator /opt/OP_6.0.1.3_Patch/OP_6.0.1.3_Loader-Data teammate-reports-op-config.xml

For more information on using the ObjectManager tool, see the “Using the ObjectManager Tool” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.


Creating Back Up Directories in the Event of a Rollback This task is recommended.

Before installing the IBM OpenPages GRC Platform 6.0.1.3 patch, create a backup directory and copy essential system files in the event you need to restore your previous OpenPages environment. Task 1: Stop all Services


2. Stop all services including the following: • OpenPages application and workflow services • CommandCenter service • OpenPages Framework Model Generator service • IBM Cognos 8 Go! Dashboard service (if installed)

Note: For details on stopping services, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.

Task 2: Create a Backup Directory

1. Create a backup directory in a location that is different from the installation location. For example:

Windows C:\OpenPages6011Backup

AIX /opt/OpenPages6011Backup

Task 3: Backup OpenPages Application Directories

1. Navigate to the <OP_Home> installation directory.

2. Copy the following directories and file from the <OP_Home> installation directory to the

backup directory location:

Copy this directory or file in <OP_Home>…

To the backup location…

For example, copy the applications directory from <OP_Home> to OpenPages6011Backup\OpenPages\applications

applications

For example, copy the aurora directory from <OP_Home> to OpenPages6011Backup\OpenPages\aurora

aurora

bin For example, copy the bin directory from <OP_Home> to OpenPages6011Backup\OpenPages\bin

Windows only: OpenPagesDomain

For example, copy the OpenPagesDomain directory from <OP_Home> to C:\OpenPages6011Backup\OpenPages\OpenPagesDomain

AIX only: profiles

For example, copy the profiles directory from <OP_Home> to /opt/OpenPages6011Backup/OpenPages/profiles

For example, copy the openpagesregistry.xml file from <OP_Home> to OpenPages6011Backup\OpenPages\ openpagesregistry.xml

openpagesregistry.xml


Task 4: Backup the Interstage BPM Directory Copy specified files to the backup directories you created.

Steps:

1. Navigate to the <Workflow_Home> installation directory. Where: <Workflow_Home> represents the installation location of the Fujitsu Interstage BPM server. By default, this is: Windows C:\Fujitsu\InterstageBPM

AIX /opt/Fujitsu/InterstageBPM

2. Copy the <Workflow_Home> root installation directory to the backup directory location:

Copy this directory… To the backup location… <Workflow_Home> For example, copy the <Workflow_Home> directory

to OpenPages6011Backup\Fujitsu\InterstageBPM

Task 5: Backup IBM Cognos Directories Copy specified files to the backup directories you created. Steps:

1. Log on to the reporting server as a user with administrative privileges and full access to the local server drives. For AIX, use non-root user, such as the user you created for the IBM OpenPages GRC Platform installation, for example opuser.

2. Navigate to the <Cognos_Home> installation directory. Where: <Cognos_Home> represents the installation location of the IBM Cognos application, by default: Windows C:\OpenPages\Cognos\cognos\c8

AIX /opt/OpenPages/Cognos/cognos/c8

3. Copy the following directories from the <Cognos_Home> installation directory to the


Copy this directory in <Cognos_Home>…


webapps\p2pd\WEB-INF\lib For example, copy the lib directory from <Cognos_Home>\webapps\p2pd\WEB-INF to OpenPages6011Backup\Cognos\lib

configuration For example, copy the configuration directory from <Cognos_Home> to OpenPages6011Backup\Cognos\configuration


Task 6: Backup CommandCenter Directories and Files

Steps: 1. On the reporting server, navigate to the <CC_Home> installation directory.

Where: <CC_Home> represents the installation location of the OpenPages CommandCenter application. By default, this is: Windows C:\OpenPages\CommandCenter

AIX /opt/OpenPages/CommandCenter

2. Copy the following directories and file from the <CC_Home> installation directory to the


Copy this directory or file in <CC_Home>…


apache-tomcat-6.0.26 For example, copy the apache-tomcat-6.0.26 directory from <CC_Home> to OpenPages6011Backup\CommandCenter\apache-tomcat-6.0.26

tools\bin For example, copy the bin directory from <CC_Home>\tools to OpenPages6011Backup\CommandCenter\bin

openpagesregistry.xml For example, copy the openpagesregistry.xml file from <CC_Home> to OpenPages6011Backup\CommandCenter\ openpagesregistry.xml

Task 7: Start all Services

Start all services including the following:




Uninstalling This Patch Uninstalling the 6.0.1.3 patch will revert the system to the previous 6.0.1.x patch level, including the data in the database. To uninstall the IBM OpenPages GRC Platform 6.0.1.3 patch perform the following tasks. Task 1: Stop all Services Stop all services including the following:


Note: For details on stopping services, see the “Starting and Stopping Servers” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide. Task 2: Restore OpenPages Application Directories and File

Steps:


2. Navigate to the <OP_Home> installation directory. Where: <OP_Home> represents the installation location of the OpenPages application, by default: Windows C:\OpenPages

AIX /opt/OpenPages

3. Delete the following directories and file from the <OP_Home> installation directory, and

then copy the corresponding directories and file from the backup directory location into the <OP_Home> installation directory to restore them:

Delete this directory or file in <OP_Home>…

Copy the corresponding directory or file from the backup location into <OP_Home>…

applications For example, copy the applications directory from OpenPages6011Backup\OpenPages\applications into <OP_Home>

aurora For example, copy the aurora directory from OpenPages6011Backup\OpenPages\aurora into <OP_Home>

bin For example, copy the bin directory from OpenPages6011Backup\OpenPages\bin into <OP_Home>

Windows only: OpenPagesDomain

For example, copy the OpenPagesDomain directory from C:\OpenPages6011Backup\OpenPages\OpenPagesDomain into <OP_Home>

AIX only: profiles

For example, copy the profiles directory from /opt/OpenPages6011Backup/OpenPages/profiles into <OP_Home>

openpagesregistry.xml For example, copy the openpagesregistry.xml file from OpenPages6011Backup\OpenPages\ openpagesregistry.xml into <OP_Home>


Task 3: Restore the Workflow Directory

Steps: 1. Navigate to the <Workflow_Home> installation directory.

Where: <Workflow_Home> represents the installation location of the Fujitsu Interstage BPM server, by default: Windows C:\Fujitsu\InterstageBPM

AIX /opt/Fujitsu/InterstageBPM

2. Delete the <Workflow_Home> root directory, and then copy the corresponding

<Workflow_Home> root installation directory from the backup directory location into the <Workflow_Home> installation directory to restore it: Delete this installation directory…

Copy the corresponding directory from the backup location into <Workflow_Home>…

<Workflow_Home> For example, copy the root Fujitsu\InterstageBPM directory from OpenPages6011Backup\Fujitsu\InterstageBPM into the <Workflow_Home> location.

Task 4: Restore IBM Cognos Directories Steps:

1. Log on to the reporting server as a user with administrative privileges and full access to the local server drives. For AIX, use non-root user, such as the user you created for the IBM OpenPages GRC Platform installation, for example opuser.

2. Navigate to the <Cognos_Home> installation directory. Where: <Cognos_Home> represents the installation location of the IBM Cognos application, by default: Windows C:\OpenPages\Cognos\cognos\c8

AIX /opt/OpenPages/Cognos/cognos/c8

3. Delete the following directories from the <Cognos_Home> installation directory, and

then copy the corresponding directories from the backup directory location into the <Cognos_Home> installation directory to restore them:

Delete this directory in <Cognos_Home>…

Example backup path

webapps\p2pd\WEB-INF\lib For example, copy the lib directory from OpenPages6011Backup\Cognos\lib into <Cognos_Home>\webapps\p2pd\WEB-INF

configuration For example, copy the configuration directory from OpenPages6011Backup\Cognos\configuration into <Cognos_Home>


Task 5: Restore OpenPages CommandCenter Directories and File Steps:

1. On the reporting server, navigate to the <CC_Home> installation directory. Where: <CC_Home> represents the installation location of the OpenPages CommandCenter application, by default: Windows C:\OpenPages\CommandCenter

AIX /opt/OpenPages/CommandCenter

2. Delete the following directories and file from the <CC_Home> installation directory, and

then copy the corresponding directories and file from the backup directory location into the <CC_Home> installation directory to restore them:

Delete this directory or file in <CC_Home>…

Copy the corresponding directory or file from the backup location into <CC_Home>…

apache-tomcat For example, copy the apache-tomcat-6.0.26 directory from OpenPages6011Backup\CommandCenter\apache-tomcat-6.0.26 into <CC_Home>

tools\bin For example, copy the bin directory from OpenPages6011Backup\CommandCenter\bin into <CC_Home>\tools

openpagesregistry.xml For example, copy the openpagesregistry.xml file from OpenPages6011Backup\CommandCenter\ openpagesregistry.xml into <CC_Home>

Task 6: Update the OpenPages Framework Model Generator Service This task is required and only applies to Windows environments upgraded from 6.0.1.1.

The path of the Framework Model Generator service was changed to <CC_HOME>\apache-tomcat\bin for OpenPages 6.0.1.2 and higher. The following scripts restore the path to the previous 6.0.1.1 patch version, which is <CC_HOME>\apache-tomcat-6.0.26\bin. Steps:

1. Log on to the reporting server as a user with administrative privileges. IMPORTANT! Close the Services windows (services.msc) if it is open.

2. Launch a Command Prompt window using the Run as Administrator option. 3. Navigate to the <CC_HOME>\apache-tomcat-6.0.26\bin directory

Where: <CC_Home> represents the installation location of the OpenPages CommandCenter application. By default, this is C:\OpenPages\CommandCenter.

4. Run the following commands: • sc delete Tomcat6 • service.bat install • sc config Tomcat6 DisplayName= "OpenPages Framework Model Generator"

start= auto 5. Click the Windows Start menu and select All Programs. 6. Select Administrative Tools and choose Services from the list. 7. In the Services window, select Action from the menu bar and click Refresh. 8. In the right pane, verify that the OpenPages Framework Model Generator service is

present in the list of services.


Task 7: Restore the Database Run the OpenPages restore (OPRestore) and CommandCenter restore (OPCCRestore) utilities to restore the database to the previous IBM OpenPages GRC Platform 6.0.1.2 patch level. Note: For details on using the restore utilities, see the “Using Utilities” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide. Task 8: Start all Services Start all services including the following:



Documentation Updates To download updates to the IBM® OpenPages® GRC Platform documentation set, point your browser to the IBM information server at: http://www.ibm.com/support/docview.wss?uid=swg27021291

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


Notices This information was developed for products and services offered in the U.S.A. IBM® may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan, Ltd.

1623-14, Shimotsuruma, Yamato-shi

Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

Location Code FT0

550 King Street

Littleton, MA 01460

U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.


Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both.

IBM

IBM logo

AIX

Cognos

OpenPages

ReportNet

WebSphere

Interstage is a trademark of Fujitsu Limited. Portions of this guide were reused or adapted from the Interstage Business Process Manager User Guide with written permission from Fujitsu, Inc. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation and/or its affiliates. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.

Documents

IBM OpenPages GRC Platform 6.0.1public.dhe.ibm.com/software/data/cognos/...IBM® OpenPages® GRC Platform . Version 6.0.1 FP3 . Patch ReadMe . December 2011