IBM OpenPages GRC Platform 6.2.1 Fix Pack 1 Readme

Fix readme


Abstract

IBM OpenPages GRC Platform 6.2.1 Fix Pack 1 Readme

Content

About this Patch Installer
This patch installer updates the IBM® OpenPages® GRC Platform environment from version 6.2.1 to version 6.2.1.1 for Windows/IBM WebSphere Application Server, Windows/Oracle WebLogic Server, AIX/IBM WebSphere Application Server, RHEL/IBM WebSphere Application Server installation. It is a cumulative update.

Depending on your environment and preferences, you can update the database server by manually running SQL scripts. Database scripts can be executed directly on the database server or from the application server.

Important! You must use the patch installer program to update the IBM OpenPages application, workflow, and reporting servers. The patch installer must be run on all application and reporting servers.



Bug Fixes and Known Issues

Bug Fixes

For more information, please see the IBM OpenPages 6.2.1 FP1 release page:
http://www.ibm.com/support/docview.wss?uid=swg27038028#tab_621FP1

Known Issues

1. If you have performed any changes to application.xml (for example, removed "openpages" from the app URL), then you will need to follow the steps below to preserve the settings.

Oracle WebLogic

1. Before applying the patch, navigate to OpenPages\applications\op-apps\META-INF\application.xml
2. Copy the file to a temporary location.
3. Apply the patch.
4. Stop all services (if running).
5. Return to OpenPages\applications\op-apps\META-INF\application.xml
6. Restore your old settings back from the file you backed up before.
7. Restart the services.

IBM WebSphere

  1. Before applying the patch, navigate to <OP_Home>/profiles/OpenPagesDmgr/config/cells/OpenPagesCell/applications/op-apps.ear/deployments/op-apps/META-INF/application.xml
  2. Copy the file to a temporary location.
  3. Apply the patch.
  4. Stop all services (if running)
  5. Return to <OP_Home>/profiles/OpenPagesDmgr/config/
    cells/OpenPagesCell/applications/op-apps.ear/deployments/
    op-apps/META-INF/application.xml
  6. Open the file in a text editor and compare it to the previously backed up file.
  7. Restore previously customized settings.
  8. This above step needs to be done for all nodes in the cluster. Each node will have a version of application.xml in a path similar to:
    <OP_Home>/profiles/<Node Name>1/installedApps/OpenPagesCell/op-apps.ear/META-INF/application.xml

If you have performed any changes to web.xml (for example, changed session time-outs), then you will need to follow the steps below to preserve the settings

2. Session Timeout Settings

Oracle WebLogic
  1. Please refer to the OpenPages Administrator’s Guide, "Setting a Session Inactive Timeout Values in Oracle WebLogic Environment”.
  2. Please note down the current "Session Timeout"

    For Example:
    <!-- Set the default session timeout (in minutes) -->
    <session-config>
    <session-timeout>90</session-timeout>
    </session-config>
  3. Apply the fix pack and then stop services.
  4. Again refer to the Administrator’s Guide to restore the original value.


IBM WebSphere
  1. Please refer to the OpenPages Administrator’s Guide, "Setting a Session Inactivity Timeout Values in IBM WebSphere Environment"
  2. Please note down the current Timeout Value.
  3. Apply the fix pack
  4. Again refer to the Administrator’s Guide to restore the original value.

Before You Begin

Prerequisite Software

Prior to installing the IBM® OpenPages® GRC Platform 6.2.1.1, you should have OpenPages 6.2.1 installed

Information You Need

The 6.2.1.1 patch requires the following information.

  • For the OpenPages application update:
  • The existing installation path of the OpenPages application server and the administrative server port number
  • The existing installation path of the Interstage BPM workflow server, application server port number and the administrative server port number
  • The existing installation path of the Oracle WebLogic or IBM WebSphere server with the corresponding admin server user name and password
  • The number of cluster members configured on the machine
  • The user name and password of the OpenPages application super administrator.
  • The status of WebSphere Global Security for the IBM WebSphere Application Server
  • · For the Oracle database update:
  • The existing location of the Oracle Client folder
  • The Oracle database alias name
  • The OpenPages database user name and password
  • The Interstage BPM workflow database user name and password
  • For the DB2 database update:
  • The existing location of the DB2 Client folder
  • The OpenPages database user name and password
  • The Interstage BPM workflow database user name and password
  • For the CommandCenter update:
  • The existing installation path of the Cognos server
  • The existing installation path of the CommandCenter folder
  • The dispatcher URL for the CommandCenter

Notice to DB2 Customers

IBM® OpenPages® GRC Platform 6.2.1 was certified with DB2 10.1. To achieve the best performance and stability, it is now recommended that customers upgrade to DB2 10.1 Fix Pack 3. For more information about DB2 10.1 Fix Pack 3 and how to obtain it, please visit this page:

http://www-01.ibm.com/support/docview.wss?uid=swg24035759

Backing Up the Existing IBM OpenPages GRC Platform Environment

Before you start the patch update process, perform the following tasks.

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.

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.







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 and reporting servers are on separate machines
· Scenario 2: The application and reporting servers are on the same machine

Note: In any of these scenarios, you need to manually upgrade the database server first, using SQL scripts.

Scenario 1: The Application, Database, and Reporting Servers Are on Separate Machines
If the application and reporting servers are each running on different machines (for example, the application server is on Machine-1 and the reporting server is on Machine-2), 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
A reporting server Reporting server Reporting


Scenario 2: The Application, Database, and Reporting Servers Are on the Same Machine
If the application 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.

To update… Run the patch installer on this machine… And select this…
The application and reporting on one system The application/reporting server Application
and Reporting


Patch Installation Tasks

To install the IBM OpenPages GRC Platform 6.2.1.1 patch, perform the following tasks.

Important! Before installing the 6.2.1.1 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.2.1.1 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.2.1.1 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

Manually update the database server by running SQL scripts included in the media kit.

Important! Manually run SQL scripts to update the database server, you must run the SQL scripts BEFORE using the 6.2.1.1 patch installer.

To update the database server using SQL scripts, follow the instructions in this section.

For Oracle database ,

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.2.1.1 media kit, copy the entire OP_6.2.1.1_Database directory to a local directory.

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

4. Run v6.2.1.1 patch SQL scripts listed in the following table in the order specified.

Script Sequence Script Name
1.
OP-6-2-1-1-wfx-schema-upgrade.sql
2.
OP-6-2-1-1-wfx-core-data-upgrade.sql
3.
OP-6-2-1-1-wfx-app-data-upgrade.sql
4.
OP-6-2-1-1-opx-schema-upgrade.sql
5.
OP-6-2-1-1-opx-procedure-upgrade.sql
6.
OP-6-2-1-1-opx-core-data-upgrade.sql
7.
OP-6-2-1-1-opx-app-data-upgrade.sql


Example:

<openpages username> is the user name for accessing the OpenPages database. By default, this is: openpages
<openpages password> is the password for the OpenPages database account
<alias name> is the Oracle Alias name (for example, OP or OP11G)

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-wfx-schema-upgrade.sql OP-6-2-1-1-wfx-schema-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-wfx-core-data-upgrade.sql OP-6-2-1-1-wfx-core-data-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-wfx-app-data-upgrade.sql OP-6-2-1-1-wfx-app-data-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-opx-schema-upgrade.sql OP-6-2-1-1-opx-schema-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-opx-procedure-upgrade.sql OP-6-2-1-1-opx-procedure-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-opx-core-data-upgrade.sql OP-6-2-1-1-opx-core-data-upgrade.log

sqlplus <openpages username>/<openpages password>@<alias name> @sql-wrapper OP-6-2-1-1-opx-app-data-upgrade.sql OP-6-2-1-1-opx-app-data-upgrade.log


5. When finished, close the Command Prompt window.



For DB2 database,

Steps:
  1. Log on as an administrative user to a machine with CLPPlus and access to the database server.
  2. From the IBM OpenPages GRC Platform Patch Installer 6.2.1.1 media kit, copy the entire OP_6.2.1.1_Database directory to a local directory.
  3. Open a Command Prompt window (using the Run as Administrator option) or Unix shell and navigate to OP_6.2.1.1_Database directory you just copied.
  4. In Windows environments, run db2cmd to start the DB2 command line processor (CLP)
  5. Run each SQL script listed in the following table in the order specified.
    Script Sequence Script Name
    1.
    OP-6-2-1-1-wfx-schema-upgrade.sql
    2.
    OP-6-2-1-1-wfx-core-data-upgrade.sql
    3.
    OP-6-2-1-1-wfx-app-data-upgrade.sql
    4.
    OP-6-2-1-1-opx-schema-upgrade.sql
    5.
    OP-6-2-1-1-opx-procedure-upgrade.bat|.sh
    6.
    revalidate.sql
    7.
    OP-6-2-1-1-opx-core-data-upgrade.sql
    8.
    OP-6-2-1-1-opx-app-data-upgrade.sql


Example:

<openpages username> is the user name for accessing the OpenPages database. By default, this is: openpages
<openpages password> is the password for the OpenPages database account
<host name> is the database machine name
<instance port> is the instance port (for example, 50000)
<database name> is the instance name (for example, OPX)

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-wfx-schema-upgrade.sql OP-6-2-1-1-wfx-schema-upgrade.log

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-wfx-core-data-upgrade.sql OP-6-2-1-1-wfx-core-data-upgrade.log

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-wfx-app-data-upgrade.sql OP-6-2-1-1-wfx-app-data-upgrade.log

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-opx-schema-upgrade.sql OP-6-2-1-1-opx-schema-upgrade.log

OP-6-2-1-1-opx-procedure-upgrade.bat|.sh <DATABASE NAME> <openpages username> <openpages password>


clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper revalidate.sql revalidate.log <openpages username>

db2rbind <DATABASE NAME> -l oprbind.log -u <openpages username> -p <openpages password> -r any

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-opx-core-data-upgrade.sql OP-6-2-1-1-opx-core-data-upgrade.log

clpplus -nw <openpages username>/<openpages password>@<HOST NAME>:<instance port>/<DATABASE NAME> @sql-wrapper OP-6-2-1-1-opx-app-data-upgrade.sql OP-6-2-1-1-opx-app-data-upgrade.log

6. When finished, close the Command Prompt window.


Task 3: Launch the Patch Installer Program

Launch the OpenPagesPatchSetup installer program to launch the patch installation.

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, manually run scripts and needs to be executed 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 Unix 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.2.1.1 installation kit, copy the entire OP_6.2.1.1_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 Unix shell, and do the following:
    1. Navigate to the IBM OpenPages GRC Platform Patch Installer directory you just copied.
    2. Navigate to the patch installer in the IBM OpenPages GRC Platform Patch Installer directory:

      IBM WebSphere installations:
      Disk1\InstData\[Linux, AIX64 or WIN64]\NoVM

      Oracle Weblogic installations:
      Disk1\InstData\NoVM
    3. Launch the IBM OpenPages GRC Platform patch installer program as follows:
    Windows OpenPagesPatchSetup.exe
    AIX/Linux OpenPagesPatchSetup.bin

4. On the Introduction 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 8; Task 9
Non-Admin Application server Application Task 5; Task 6; Task 8; Task 9
Reporting server Reporting Task 7; Task 6; Task 9
Application/ Reporting server Application AND Reporting Task 5; Task 6; Task 7; Task 8; Task 9

b. When finished, click Next to continue.


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 Installation Directory screen, do the following.
a. Enter information for the following fields:

In this field… Enter this…
OpenPages GRC Platform Installation directory The installation location of the existing OpenPages application.

Example:
Windows
c:\OpenPages

AIX or Linux
/opt/OpenPages
Workflow(Interstage BPM) Installation Folder The installation location of the existing Fujitsu Interstage BPM workflow server.

Example:
Windows
c:\Fujitsu\InterstageBPM

AIX or Linux
/opt/Fujitsu/InterstageBPM
WebLogic Installation Folder Windows/Oracle 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 Server Information screen, do the following.
a. Enter information for the following fields:

In this field… Enter this…
OpenPages Admin Server Port Number
Windows/Oracle WebLogic Only
The administrative server port number used by the Oracle WebLogic Server for the OpenPages application.

Windows Default: 7001
Interstage BPM Admin Server Port Number
Windows/Oracle WebLogic Only
The administrative server port number used by Oracle WebLogic Server for the workflow server.

Windows Default: 49901
Admin Server User Name

Windows/Oracle WebLogic Only
The user name for accessing the Oracle WebLogic Server Administration Console.

Windows Default: weblogic
Admin Server User Password

Windows/Oracle WebLogic Only
The password for the Oracle WebLogic or IBM WebSphere admin account.
Confirm Password
Windows/Oracle WebLogic Only
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? IBM 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.

b. When finished, click Next.


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 Server Information screen, enter information for the following fields:

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

Example:
Windows
C:\OpenPages\Cognos\cognos\c10_64

AIX or Linux
/opt/OpenPages/Cognos/cognos/c10_64
OpenPages CommandCenter Directory The location of the OpenPages CommandCenter folder.

Example:
Windows
C:\OpenPages\CommandCenter

AIX or Linux
/opt/OpenPages/CommandCenter
CommandCenter Dispatcher URL The Dispatcher URL for the OpenPages CommandCenter

Example:
http://<servername>:9300/p2pd/servlet/dispatch

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:

For Oracle Database:

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

In this field… Enter this…
Oracle Client Directory The location on the OpenPages application server where the Oracle Client software is installed. This should be the same as the ORACLE_HOME value.

Example
In this example, the database and application servers are on different machines:

Windows
C:\openpages_data\repository\ client112_ac_x64\software

AIX or Linux
/opt/oracle/openpages_data/repository/ client112_ac_x64/software
Database Alias Name The TNS name of the OpenPages database instance.

OpenPages Database User Name The user name for accessing the OpenPages database.

By default, this is: openpages
OpenPages Database Password The password for the OpenPages database account.
Workflow Database User Name The user name for accessing the Workflow database.

By default, this is: opworkflow
Workflow Database Password The password for the Workflow database account.

b. When finished, click Next.

For DB2 Database:

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

In this field… Enter this…
DB2 Client Directory The location on the OpenPages application server where the DB2 Client software is installed. This should be the same as the DB2_HOME value.

Example
In this example, the database and application servers are on different machines:

Windows
C:\db2inst1\sqllib
AIX or Linux
/home/db2inst1/sqllib
OpenPages Database User Name The user name for accessing the OpenPages database.

By default, this is: openpages
OpenPages Database Password The password for the OpenPages database account.
Workflow Database User Name The user name for accessing the Workflow (Interstage BPM) database.

By default, this is: opworkflow
Workflow Database Password The password for the Workflow (Interstage BPM) database account.

b. When finished, click Next.


Task 9: Start Servers
This task applies in all patch 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. Start the reporting server (including the CommandCenter and OpenPages Framework Model Generator services).

For a horizontal clustered environment, use the following sequence to restart IBM Cognos services:
a. Stop IBM Cognos services on all secondary servers.
b. Stop IBM Cognos service on the primary server.
c. Start IBM Cognos service on the primary server.
d. Start IBM Cognos 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\V6211\logs\OpenPages_Patch_Installer_Debug.log
· <OP_Home>\patch\V6211\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
AIX or Linux /opt/OpenPages



Post-Installation Tasks
Perform the following tasks after completing the patch to 6.2.1.1.

Task 1: Apply the Modules Patch
This task is required for all OpenPages environments with the optional Modules installed.

After you have updated your system to IBM OpenPages GRC Platform 6.2.1.1, apply the OpenPages Modules patch

<OpenPages 6.2.1.1 Kit>\Modules solutions reports and version update files

Steps:
  1. Load updated reports:
    1. Log into OpenPages application as administrator
    2. Under the Reporting menu select Cognos Connection
    3. In Cognos Connection, in the Public Folders section, select OpenPages Solutions V6
    4. Navigate to Risk Reports / Risk Analysis
    5. For the report Risk Analysis, under the actions options select the right angle triangle to open the report in Report Studio
    6. If asked whether to allow the web page to access your clipboard, select Allow access
    7. If a prompt window opens asking for the Risk Domain, and Resource ID, you can close this window and ignore the error message.
    8. Select Tools > Copy Report to Clipboard
    9. Open a new text file in Notepad or other editor and paste the contents of your clipboard to the file.
    10. Save the text file in a location of your choice as a backup.
    11. Open the new report definition: OP_6.2.1.1_Installer\Modules\Risk Analysis.xml
    12. Select all of the text in the file (ctrl-a) and copy (ctrl-c)
    13. In Report Studio go to the Tools menu. Select Open Report from Clipboard. This should paste a new report into Report Studio.
    14. Save the report. You will be prompted to Save as. Select Risk Analysis, and replace the original report.
    15. To verify that the new report has taken effect, in the OpenPages application go to the Reporting menu. Navigate to OpenPages V6/ Risk Reports/ Risk Analysis. Verify the contents.
    16. Repeat this process for the Risk Assessment Summary report using the Risk Assessment Summary.xml
  2. Update OPS_DojoCallsAddModifyPlans.jsp
WAS environment:
    1. Login the system in which OpenPages is installed. Navigate to directory <OP_HOME>/OpenPages/profiles/<hostname>-OPNode1/installedApps/OpenPagesCell/op-apps.ear/sosa.war/Wizard.
    2. Backup the OPS_DojoCallsAddModifyPlans.jsp.
    3. Replace OPS_DojoCallsAddModifyPlans.jsp with the new JSP file located in the <OpenPages 6.2.1.1 Kit>\Modules folder.
    4. Restart OP services.

WLS environment:
    1. Login the system in which OpenPages is installed. Navigate to directory <OP_HOME>/OpenPages/applications/op-apps/sosa/Wizard.
    2. Backup the OPS_DojoCallsAddModifyPlans.jsp.
    3. Replace OPS_DojoCallsAddModifyPlans.jsp with the new JSP file located in the <OpenPages 6.2.1.1 Kit>\Modules folder.
    4. Restart OP services.
3. Update the Modules data
    1. Open a command prompt of shell and navigate to the OpenPages bin directory. For example:
      1. c:\OpenPages\bin
      2. /home/opuser/OpenPages/bin
    2. Run the command:

      ObjectManager b c <OPUserName> <OPUserPassword> <PATCH_LOADER_DATA> <PATCH_LOADER_DATA>/openpages-patch-modules-loader-data.txt

      Replacing <OPUserName> <OPUserPassword> with an OpenPages administrator user name and password. Replace each instance of <PATCH_LOADER_DATA> with the path to the loader-data folder in the Modules directory in the patch. For example:

      ObjectManager b c OpenPagesAdministrator myPassword c:\6211\ OP_6.2.1.1_Installer\Modules\loader-data c:\6211\ OP_6.2.1.1_Installer\Modules\loader-data\openpages-patch-modules-loader-data.txt

Task 2: Update Apache Tomcat for the IBM OpenPages Framework Model Generator

This task is required for all OpenPages environments.
  1. Rename the existing <OpenPages CommandCenter Install Directory>\apache-tomcat to <OpenPages CommandCenter Install Directory>\apache-tomcat-old
  2. Unzip the apache-tomcat.zip to <OpenPages CommandCenter Install Directory> from <Patch Kit>\CommandCenter
  3. Rename server.xml to server.xml.backup in <OpenPages CommandCenter Install Directory>\apache-tomcat\conf
  4. Copy the server.xml from <OpenPages CommandCenter Install Directory>\apache-tomcat-old\conf to <OpenPages CommandCenter Install Directory>\apache-tomcat\conf
  5. Copy the crf-refresher.war from <OpenPages CommandCenter Install Directory>\apache-tomcat-old\webapps to <OpenPages CommandCenter Install Directory>\apache-tomcat\webapps
  6. Rename catalina.bat/.sh to catalina.bat.backup/.sh.backup in <OpenPages CommandCenter Install Directory>\apache-tomcat\bin
  7. Copy the catalina.bat/.sh from <OpenPages CommandCenter Install Directory>\apache-tomcat-old\bin to <OpenPages CommandCenter Install Directory>\apache-tomcat\bin
  8. Copy the tomcat6.exe & tomcat6w.exe from <OpenPages CommandCenter Install Directory>\apache-tomcat-old\bin to <OpenPages CommandCenter Install Directory>\apache-tomcat \bin
  9. Restart the Tomcat

Uninstalling This Patch

Uninstalling the 6.2.1.1 patch will revert the system to the previous 6.2.1 level, including the data in the database.

To uninstall the IBM OpenPages GRC Platform 6.2.1.1 patch perform the following tasks.

Task 1: Stop all Services

Stop all services including the following:
· OpenPages application and workflow services
· IBM Cognos service
· OpenPages Framework Model Generator service

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

Task 2: Run Patch Uninstaller

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

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

Windows C:\OpenPages\Patch\v6211\Uninstall_OpenPages_Patch
AIX or Linux /opt/OpenPages/patch/V6211/Uninstall_OpenPages_Patch

3. Run Patch Uninstaller
   a. OpenPagesPatchUninstall.exe for Windows
   b. OpenPagesPatchUninstall.bin for Unix

4. Delete the contents of the 6.2.1.1 fxtag file from the <OP_Home>\properties\version directory


Task 3: 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.2.1.1 level.

Note: For details on using the restore utilities, see the “Using Utilities” chapter in the IBM® OpenPages® GRC Platform Administrator’s Guide.


Task 4: Start all Services

Start all services including the following:
· OpenPages application and workflow services
· IBM Cognos service
· OpenPages Framework Model Generator service

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

Documentation Updates

You can download the latest revision to the IBM® OpenPages® GRC Platform 6.2 documentation set from the IBM information server at:

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



Appendix A – Silent Patch Installation and Uninstallation

Silent Patch Installation:

Complete Task 1 and Task 2 from the “Patch Installation Tasks”

Task 1: Update Silent Installer Properties
  1. Log on to the server where you will perform the patch as a user with administrative privileges and full access to the local server drives.

    Note: For Unix 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.2.1.1 installation kit, copy the entire OP_6.2.1.1_Installer\IBM OpenPages GRC Platform Patch Installer directory to the application server.
  3. Navigate to the IBM OpenPages GRC Platform Patch Installer 6.2.1.1 installation kit directory: Install\silent-installer
  4. Update Silent Installer properties file

For IBM WebSphere Application Server
op-silentInstaller-Patch-WAS.properties file with the right values and copy it to Disk1\InstData\[Linux, AIX64 or WIN64]\NoVM under the IBM OpenPages GRC Platform Patch Installer directory you just copied

For Oracle WebLogic Application Server
op-silentInstaller-Patch-WLS.properties file with the right values and copy it to Disk1\InstData\NoVM under the IBM OpenPages GRC Platform Patch Installer directory you just copied

Task 2: Run Patch Installer Silently

Silently Launch the OpenPagesPatchSetup installer program to launch the patch installation.

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, manually run scripts and needs to be executed before using the patch installer program.

Steps:
1. Open a Command Prompt window (using the Run as Administrator option) or Unix 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\[Linux, AIX64 or WIN64]\NoVM

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

For Oracle WebLogic

Windows OpenPagesPatchSetup.exe -i silent -f op-silentInstaller-Patch-WLS.properties

For IBM WebSphere

Windows OpenPagesPatchSetup.exe -i silent -f op-silentInstaller-Patch-WAS.properties
AIX/Linux OpenPagesPatchSetup.bin -i silent -f op-silentInstaller-Patch-WAS.properties

Task 3: Start Servers
This task applies in all patch 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. Start the reporting server (including the CommandCenter and OpenPages Framework Model Generator services).

For a horizontal clustered environment, use the following sequence to restart IBM Cognos services:
a. Stop IBM Cognos services on all secondary servers.
b. Stop IBM Cognos service on the primary server.
c. Start IBM Cognos service on the primary server.
d. Start IBM Cognos services on all secondary servers.

Task 4: Complete the “Locating Patch Installation Log Files” and “Post-Installation Tasks”

Silent Patch Uninstallation:

If you have run the Patch Installer silent then Uninstaller automatically run silently. Follow all the instructions under “Uninstalling the Patch”


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. This document may
describe products, services, or features that are not included in the Program or
license entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant 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.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, 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-1250
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 document 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 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.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

This Software Offering does not use cookies or other technologies to collect
personally identifiable information.

Copyright
Licensed Materials - Property of IBM Corporation.

© Copyright IBM Corporation, 2003, 2014.

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

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

IBM, the IBM logo and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.

The following terms are trademarks or registered trademarks of other companies:
· 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.
· Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
· Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
· UNIX is a registered trademark of The Open Group in the United States and
other countries.
· Java and all Java-based trademarks and logos are trademarks or registered
trademarks 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 and
trademark information ” at www.ibm.com/legal/copytrade.shtml.

Rate this page:

(0 users)Average rating

Document information


More support for:

OpenPages GRC Platform

Software version:

6.2.1

Operating system(s):

AIX, Linux, Windows

Reference #:

1671458

Modified date:

2014-05-12

Translate my page

Machine Translation

Content navigation