as04 c8.3 c8se install and config[1]

Cognos Proprietary Information

DOC ID: AS04 Version 8.3.0.0

Cognos Special Edition - Installation and Configuration

Product(s): Cognos 8.3 Special Edition

Area of Interest: Infrastructure

Installation and Configuration of Cognos 8 Special Edition


Copyright

Copyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to the information contained in this document will be documented in subsequent editions. This document contains proprietary information of Cognos. All rights are reserved. No part of this document may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos. Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBM and the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries, or both. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos products can be found at www.cognos.com

This document is maintained by the Best Practices, Product and Technology team. You can send comments, suggestions, and additions to [email protected] .



Table of Contents

1 Introduction ...........................................................................................................................................1

1.1 Definitions, Acronyms, and Abbreviations ..................................................................................1

1.2 Purpose.........................................................................................................................................1

1.3 Scope............................................................................................................................................2

1.4 Assumptions & Prerequisites .......................................................................................................3

2 System Preparation ...............................................................................................................................5

2.1 Cleanup Existing Environment ....................................................................................................5

2.2 User Accounts ..............................................................................................................................5

2.3 Install Java on UNIX / Linux .......................................................................................................6

2.4 IBM Software CD Images............................................................................................................6

3 Script Architecture................................................................................................................................9

4 Scenario - Single-Server (All In One) ................................................................................................10

4.1 Cognos 8 Installer - ISSetup.......................................................................................................10

4.2 Manual Environment Changes ...................................................................................................15

4.3 Manually Starting the IBM Product Install and Configuration ..................................................17

4.4 C8SE_master – Script Progress and Output ...............................................................................18

5 Scenario - Distributed Component Install.........................................................................................19

5.1 Cognos 8 Content Manager Install .............................................................................................19

5.2 Cognos 8 Application Tier Component Install...........................................................................23

5.3 Cognos 8 Gateway Install...........................................................................................................30

6 Managing the IBM Product Suite ......................................................................................................35

6.1 IBM DB2 WSEE........................................................................................................................35

6.2 IBM WebSphere.........................................................................................................................36

6.3 IBM HTTP Server (IHS)............................................................................................................37

7 Uninstalling IBM and Cognos Products............................................................................................39

7.1 IBM DB2 UDB / WSE...............................................................................................................39

7.2 IBM WebSphere.........................................................................................................................39

7.3 IBM HTTP Server (IHS)............................................................................................................39

7.4 Cognos 8.....................................................................................................................................39

8 Troubleshooting & Verification .........................................................................................................40

8.1 IBM Product Installer (DB2 and WAS) .....................................................................................40

8.2 IBM DB2 Database Configuration Error ...................................................................................42

8.3 IBM DB2 License Registration..................................................................................................44

8.4 Distributed Installation...............................................................................................................45

8.5 IBM WebSphere.........................................................................................................................45

9 Error Messages....................................................................................................................................49

9.1 JAVA_HOME environment variable has not been set...............................................................49

9.2 XML Parser - Transformation Aborted......................................................................................49

9.3 CM-CFG-5063 / CM-SYS-5003 / SQL1032N...........................................................................49



9.4 Setuid execution is not allowed..................................................................................................50

9.5 SQL1225N / SQLSTATE=57049 ..............................................................................................50

9.6 Warnings / Errors that are safe to ignore....................................................................................50

Appendix A - Script Functions...................................................................................................................52

Installation and Configuration of Cognos 8 Special Edition 1


1 Introduction

1.1 Definitions, Acronyms, and Abbreviations

Term Definition

C8SE Cognos 8 Special Edition

WAS IBM WebSphere Application Server

IHS IBM HTTP Server (Apache)

UDB IBM Universal Database (DB2)

CM Cognos 8 Content Manager Component

ATC Cognos 8 Application Tier Components

GW Cognos 8 Gateway Component

WSE IBM DB2 WorkGroup Server Edition

1.2 Purpose

Cognos 8 Special Edition provides a mechanism that automates the installation and configuration of Cognos 8, IBM WebSphere, IBM DB2 UDB and IBM HTTP Server with a minimal amount of user input. This document is for those who have limited experience with Cognos 8 Special Edition and who wish to set up an environment using the IBM product infrastructure. It also contains some detailed troubleshooting information and functionality of the scripts used in the install. In addition to performing the normal Cognos 8 installation ISSetup will prompt for information relating to the IBM components listed below when the associated Cognos 8 component is selected by the user during the install.

� Cognos 8 – Content Manager

� IBM WebSphere Application Server * � IBM DB2 UDB Server *

� Cognos 8 – Application Tier Components

� IBM WebSphere Application Server * � IBM DB2 UDB Client *

� Cognos 8 – Gateway

� IBM HTTP Server

* Note: Only 1 copy of IBM WebSphere or DB2 will be installed when CM or ATC or both CM & ATC are selected.



1.3 Scope

Product Versions

The Cognos 8.3 Special Edition product suite currently consists of:

• Cognos 8 Special Edition (8.3)

• IBM WebSphere Express Edition v6.1.0.3 Base

• IBM HTTP Server v6.1.0.3 [Apache/2.0.47] (Packaged with IBM WebSphere but installed and configured separately)

• IBM DB2 Workgroup Server Edition (2 CPU License) v9.1

Platforms

Windows, AIX, Solaris, HP/UX, Linux i386 (Intel) Update: IBM DB2 is not available on HP-UX 11.2 for PA-RISC so HP support was removed .

Platform Variations

The instructions in this document will work cross platform (Windows / UNIX / Linux) however the examples shown will often be based on a Windows install although there is a mixture throughout this document. The user is expected to know the proper format regarding the syntax for variables and other operating system difference. For example, use ${VARIABLE} for UNIX and %VARIABLE% for Windows. Consult your UNIX and Windows documentation for more information regarding commands, syntax and scripting.

Install Types

The installation and setup of a single server environment and the installation of separate components will be documented. Other install scenarios are simply variations on these two basic install types.



1.4 Assumptions & Prerequisites

Before continuing, make sure the following prerequisites have been met.

• Clean Environment - C8SE makes the assumption that you have a clean working environment and that the products that will be installed do not currently reside on your system. It is imperative that any existing products that may conflict with the C8SE (and the IBM components in particular) be properly removed prior to running the C8SE installation. Note: Manual deletion of directories is typically not an appropriate removal method as registration files are left behind in various locations such as the Windows registry and Unix system directories. Use the appropriate

uninstall tools to successfully remove conflicting/similar products. In addition to path conflicts (DB2 on UNIX for example must install into a specific path) existing products may use default ports that will also conflict with the C8SE versions that will be installed.

• User Accounts / Access Rights - IBM DB2 requires Root access on UNIX platforms and on Windows the user must be a member of the Administrators group. Windows installs will therefore be performed using a single user ID and you must be logged on as that user to run the C8SE install (and dependant IBM products). UNIX installs require 3 accounts. You must be logged on as a root-equivalent user to perform the C8SE install (and dependant IBM products) and must have the User ID and password information for a DB2 administrative user as well as a DB2 client user. These accounts must therefore be created prior to running the C8SE installation.

• IBM Product Versions / CD Images - C8SE may only be used with the versions of the IBM products included in the package and other CD images may cause the installation and configuration to fail.

• Hardware and Operating System Dependencies – There are many dependencies for DB2, WebSphere and Cognos 8. As these are numerous, please consult the IBM website and/or the DB2 and WebSphere documentation to determine the software and operating system requirements. The Cognos customer support web site should also be consulted to determine the minimum requirements for the Cognos 8 product. In most cases, the hardware and operating system is not validated for conformance and the install tools assume it is suitable.

• System Resources - Considerably more memory, hard disk space and CPU power is required to run any full Database Server (DB2) and Application Server (WebSphere). The minimum requirements for DB2, WebSphere and Cognos 8 should be compared to available resources. 1GB of physical memory should be considered a minimum to ensure performance and reliability. The default configuration will set 768MB of memory for the maximum java heap size in WebSphere, although this can be adjusted manually after the installation and configuration has completed. Approximately 5GB of disk space is required to hold the CD images and product installs.

• Temporary Disk Space – At least 500MB of temporary working disk space must be available in addition to the product space requirements to allow for building and deploying application files as well as other functions.

• Java Version - The JRE used to perform the installation must meet minimum conformance levels for both WebSphere and Cognos 8. An environment variable with the name JAVA_HOME must be set prior to running the C8SE installation. The JVM used for running the product after the installation and configuration will be the one that is installed as part of the WebSphere install.

• Documentation – Installation and administrative documentation for WebSphere, DB2 UDB, IBM HTTP Server and Cognos 8 must be available as a resource.



• Basic O/S Knowledge - Familiarity with the operating system (O/S) with which you are using is essential. You must be familiar with O/S level tasks including user commands at the command line, variable syntax, scripting, etc. as many basic functions that are not documented.

• Product Knowledge - You must already know how to setup and run Cognos 8 in a standard environment (non-application server). Knowledge of Cognos 8 in an application server environment would be a definite asset. Familiarity with the IBM product suite (DB2, WAS and IHS) is also required. Once C8SE and the associated products have been installed and configured, the user must be able to manage (start / stop / configure) the various processes.

• Default Values – Since the environment into which you are installing is assumed to be “clean”, default port values will be used to perform the product installs. In addition, some product install paths (DB2 on Unix for example) are not modifiable by the C8SE scripts.

Default ports:

� IBM HTTP Server: 80, 8008

� IBM WebSphere: 9080, 9060, 9443, 2809, 8880, 9401, 9402, 9403, 9100, 9353, 7276, 7286, 5558, 5578

� IBM DB2: 50001(Windows), 50002 (UNIX)

� Cognos 8: 9362



2 System Preparation

2.1 Cleanup Existing Environment

• Uninstall existing DB2 client or database server instances. (On Windows, use Add/Remove Programs. On UNIX, use the db2_deinstall program located under the DB2 install kit.)

• Remove remaining directories that the uninstall program didn’t remove (e.g. C:\DB2, C:\Program Files\IBM, etc.) You may wish to do a file search for “IBM” and “DB2”.

• Remove any Windows services that may still be registered. (Check Services dialog and regedit)

• Remove the existing Cognos 8 and WebSphere installs or install C8SE to a new location.

• Make sure you have plenty of space available on your hard disk.

• Clear unnecessary files from your Temp or /tmp directory.

2.2 User Accounts

Cognos 8 Special Edition requires that you create one or more local user accounts. The primary consumer of the user account information is IBM DB2. DB2 requires root or administrative privileges to install, DB2 administrative right to be administered and user privileges to access the database instances. Creating accounts with the appropriate rights / privileges is critical to a successful install. On Unix, ensure the profile of the db2user account is set to run the DB2 profile script even though it won’t exist until DB2 is installed. (T#579638)

2.2.1 Windows

On Windows, a single user account can be used to perform all of the install, configuration and management tasks. If possible (local security policies may override) create a user called “db2admin” with password “db2admin_1234” and add the user to the Administrators group. If you cannot use these credentials, read carefully the section later in this document where the user information may be modified after Cognos 8 is transferred to disk, prior to running the Special Edition scripts.

Log in as the new DB2 user and run the Cognos 8 issetup utility after performing the other prerequisite tasks.

2.2.2 UNIX / Linux

For UNIX / Linux installs, three user accounts are required. The installs will be performed as a root equivalent user. A DB2 administrative account will be used to administer / configure the DB2 instance and a DB2 user account will be used to access the instance. Create, and log in as, a user account that has root privileges.

Example .profile if [ -f /home/db2user/sqllib/db2profile ]; then . /home/db2user/sqllib/db2profile fi



Create 2 accounts to be used for DB2. Use the default names if security policies permit. If you cannot use these credentials, read carefully the section later in this document where the user information may be modified after Cognos 8 is transferred to disk, prior to running the Special Edition scripts. DB2 Administrative User ID: db2admin DB2 User ID: db2user DB2 User (db2user) Password: db2user_1234 Both the DB2 Administrative and regular user should be made members of a group called “db2” (again, see the appropriate section if this default group name is not used).

2.3 Install Java on UNIX / Linux

During the Cognos 8 installation and configuration phases, access to a JRE is required to perform certain actions. Cognos 8 on Windows ships with a JRE that will be used. No further action is required on this platform. After the installation, the JRE that ships with WebSphere will be used since this is the environment that the Cognos 8 product will run under. For UNIX / Linux, install a Cognos 8 compatible JRE or JDK and set an environment variable named “JAVA_HOME” that points to the appropriate directory.

2.4 IBM Software CD Images

In addition to the C8SE CD, the CDs for the IBM products must be copied to your computer or available (mounted) from the computer where you run the Cognos 8 installation. The Cognos 8 installation wizard prompts you for the location of the IBM installation source files, and then runs the IBM installation programs after the Cognos 8 products are installed. Important: If you are installing on UNIX or Linux, you cannot copy the files from a Windows computer. If you do, the file names may be converted to all capital letters, permissions are not set correctly and the installation will not work. The CD must be mounted on the UNIX computer to maintain the case sensitivity of the file names and the proper permissions. More information on this issue can be found on the IBM web site:



2.4.1 IBM WebSphere (Base)

Mount the WebSphere CD or Copy WebSphere Application Server and HTTP Server Installation

Source Files

The WebSphere CD contains the installation files for both WebSphere Application Server and HTTP Server.

1. Insert the CD for the WebSphere Application Server. 2. On Windows, if the Launchpad window appears because autorun is enabled, close the window. 3. If you cannot mount/load more than 1 CD at a time, copy the entire contents of the CD to your

computer, or to a network directory that is available from the computer where you run the Cognos 8 installation.

The directory where you copy the contents is treated as the root directory of the CD when you are prompted for the location of the IBM installation source files.

2.4.2 IBM WebSphere Refresh Pack

Not applicable for this release

2.4.3 IBM DB2 UDB / WSE

Mount the DB2 CD or Copy DB2 Installation Source Files

1. Insert the CD for DB2.

Technote (FAQ)

Installation of WebSphere Application Server fails due to file name case sensitivity mismatch

Problem

After FTP download of installation files from a Microsoft® Windows® platform to a UNIX® platform, file names are in uppercase, causing installation to fail.

Cause

When viewing a UNIX installation CD for WebSphere® Application Server on a Windows platform, file names all appear in uppercase. The installation files were transferred to the Unix platform using FTP. When the files were transferred to the UNIX system, they were received with uppercase file names. This causes the installation on the UNIX platform to fail.

Solution

On UNIX platforms, mount the installation CD on the system to maintain the case sensitivity of the files. Remote installations of WebSphere should be between like platforms, such as UNIX to UNIX or Windows to Windows, so that the correct file structure, symbolic links and file permissions are preserved.



2. On Windows, if the Launchpad window appears because autorun is enabled, close the window. 3. If you cannot mount/load more than 1 CD at a time, copy the entire contents of the CD to your

computer. The directory where you copy the contents will be the directory you are prompted for in the installation wizard.



3 Script Architecture

The following diagram outlines the flow and run order for the C8SE scripts. These scripts are located in <C8SE_install_path>/C8SE.

Issetup is invoked (passing appropriate command line parameters). This step creates / populates the C8SE_env[.bat|.sh] file based on defaults and user input. Unix users may have to manually edit this file to match values to their environment.

C8SE_master_env[.bat|.sh] contains all the non-editable values that the remaining scripts will use.

C8SE_env[.bat|.sh] and C8SE_master_env[.bat|.sh] are used as inputs by the other scripts along with a variety of template files that are also located in this directory.

The C8SE_master[.bat|.sh] script controls the remaining scripts which are invoked in the order listed in the diagram below.

Note: The IBMSE references in the above diagram should be changed to C8SE



4 Scenario - Single-Server (All In One)

The following images show an example run of a single server C8SE install on a Windows platform.

4.1 Cognos 8 Installer - ISSetup

Issetup must be invoked by passing command line parameters to enable the C8SE functionality. Open a command prompt and navigate to the C8 install directory or CD.

Run issetup passing the following command line parameters:

Windows: issetup –i setupc8se.csp

UNIX / Linux: ./issetup –i setupc8se.csp

The installation wizard welcome page will be displayed. Select the appropriate language.



The Cognos 8 License Agreement must be read and accepted to continue with the installation.

The IBM License Agreement must be read and accepted to continue with the installation.



Enter or browse to a suitable installation location. The path must not contain spaces.

Select the Cognos 8 component(s) that you will be installing. This example run will be a full install. The associated IBM products will be automatically selected based on the Cognos 8 components.



Specify the shortcut folder name and associated properties.

On a full C8SE install, in addition to the C8 components, all of the IBM products will be installed. It is therefore necessary to specify the source locations where the CD images were copied to in order for the C8SE scripts to launch the IBM installers. Browse to or type in the source CD path for the listed products. Note: If the WebSphere CD path is entered, it is not necessary to enter the IHS path since they reference the same location. Example with values filled in on a Windows platform.

The installation summary page will show the Cognos 8 and associated IBM products that will be installed.



The installation progress indicator will show the completion status of the Cognos 8 components. The IBM products will be installed and configured later in the process.

Once the Cognos 8 components have been transferred to disk, you may view the logs and perform other selections similar to a tomcat install. In addition, if no other manual configuration changes are required, you may select to launch the C8SE master script upon exiting issetup.

Important:

If you must make changes to the C8SE_env[.bat|.sh] script, then uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox now. More information on this is provided in the next section.



It is also possible that you simply want to defer the IBM product installation and configuration until a later time. In this case, you may also uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox and launch the script manually when you are ready.

Important:

It is not recommended that you “Start Cognos Configuration” unless you understand the potential consequences. You run a risk of creating incompatible encryption keys and will potentially be altering values that will cause the IBM automated configuration to fail. If you want to make changes in Cognos Configuration, it is advisable to do so after the IBM products have been installed and configured.

4.2 Manual Environment Changes

Once issetup completes, a directory called C8SE will be created under the Cognos 8 root directory. It will contain several scripts prefixed with “C8SE_”. For example, if you chose to install Cognos 8 in D:\cognos8SE\c8, then you will find the scripts in D:\cognos8SE\c8\C8SE. These scripts and templates, with the exception of C8SE_env[.bat|.sh], are not meant to be edited or changed by the user. C8SE_env[.bat|.sh] contains all the variables that may safely be modified prior to running the IBM product installs and configuration. This file will be pre-populated with either default values or values that have been entered via the issetup UI.

4.2.1 DB2 User Credentials

IBM DB2 is installed and configured as part of the C8SE process. As such, this product needs to be aware of user account names, passwords and other values in order to successfully complete the installation. Some of this information is also used by Cognos Configuration to access the Content Store database after installation. Edit the values in the C8SE_env[.bat|.sh] script to match the DB2 user(s) and password that you created. This is a text based file. Use only a text based editor or be sure to save the file in the proper format.



Notepad (Windows) and vi (UNIX / Linux) are examples of safe editors should you need to make changes to this file. The C8SE_C8_DB_Name variable is used by Cognos Configuration to specify the name of the DB2 database instance that will be used for the Cognos 8 Content Manager component. The default value is “CM” The C8SE_C8_DB_UID and C8SE_C8_DB_Pass variables are used by Cognos Configuration to connect to the database instance. On Windows, this must be the administrative account information that you used to log in to the system. For security purposes, this information should be removed from the file after the install and configuration is complete. Example: C8SE_env.bat (Windows)

Note: Only the relevant portion of the file is displayed above.

For UNIX and Linux platforms the following information must be provided. Similar to Windows, the C8SE_C8_DB_Name, C8SE_C8_DB_UID and C8SE_C8_DB_Pass variables must be populated with the correct values. In this case, though, the C8SE_C8_DB_UID value represents the User ID/Name of the account that will be used to access the DB2 Content Store instance. On these platforms the DB2 administrative user and the DB2 instance owner must be unique. For security purposes, this information should be removed from the file after the install and configuration is complete. The C8SE_DB2_Admin variable must contain the User ID/Name of the account that was previously created for DB2 Administration. The C8SE_DB2_Group variable must contain the UNIX group ID/Name that the DB2 user account and administrator account belong to. The default value is “db2”. This group must exist for successful completion. The C8SE_User_Home variable must be set to the root of where user home directories are located. The user account information and the user home path will be combined during the installation so that scripts and configuration commands can be run by the DB2 administrative user. The default value is “/home” but this may not be appropriate for your environment. This directory must exist for successful completion.

@rem ******************************************************* @rem IBM DB2 and Cognos 8 Content Store Database Information @rem ******************************************************* @rem Cognos 8 Content Store Database Name set C8SE_C8_DB_Name=CM

@rem IBM DB2 Database Administrator Account Name

set C8SE_C8_DB_UID=db2admin

@rem IBM DB2 Database Administrator Account Password

set C8SE_C8_DB_Pass=db2admin_1234



Example: C8SE_env.sh (UNIX / Linux)

Note: Only the relevant portion of the file is displayed above. Save the changes and close the file.

4.3 Manually Starting the IBM Product Install and Configuration

After the DB2 (or other appropriate) values have been modified and saved, you may now launch the IBM product install and configuration script manually. Ensure the JAVA_HOME environment variable is set in your system or manually set it within the command window or terminal window prior to launching the master script. Navigate to the <C8_Root>/C8SE directory from a command prompt or via Explorer (Windows) and launch the master script by typing: Windows: C8SE_master.bat

UNIX / Linux: ./C8SE_master.sh

# Cognos 8 Content Store Database Name C8SE_C8_DB_Name=CM # IBM DB2 Database Administrator Account Name C8SE_DB2_Admin=db2admin # IBM DB2 Content Store Database Instance Owner Account Name C8SE_C8_DB_UID=db2user # IBM DB2 Content Store Database Instance Owner Account Password C8SE_C8_DB_Pass=db2user_1234 # Group Name that the DB2 User and Administrator belong to C8SE_DB2_Group=db2 # Path to the User Home directories under which the DB2 Instance owner directory can be found C8SE_User_Home="/home"



4.4 C8SE_master – Script Progress and Output

Whether run automatically after issetup or launched manually, the output from the master script will be the same. The scripts will output basic progress information to the console as they proceed. This information is kept at a minimal level so that the console is not overloaded as it would make troubleshooting very difficult. A detailed log of the installation will be made in the <C8_Root>/logs directory as indicated in the console. This detailed log should be examined at the end of the run to find potential issues that the installer ran into. In some cases it is necessary to look in alternative locations to find some of the third party log files. More information on this topic can be found in the troubleshooting section of this document. The following examples show the progress and output from running an install end to end on Windows and UNIX. Windows Example:

Unix Example:

When the installation and configuration cycle has completed you will be returned to the command prompt.



5 Scenario - Distributed Component Install

In order to perform a distributed install Cognos 8 Content Manager must be installed, configured and running first. If the Cognos 8 Application Tier Component install is not included with the Content Manager install, then that must be performed next. Separate Cognos 8 Gateway installs must be the last in the install sequence.

Note: If you plan on installing components across platforms, you may need to use IP Addresses instead of machine names, depending on your server and network configuration. If the machines don’t recognize each other by name, use their IP address, instead.

To save space, where appropriate, references will be made to the Single Server install section above rather than post identical screen captures and information. Please ensure you read and reference this chapter.

5.1 Cognos 8 Content Manager Install








The Cognos 8 License Agreement must be read and accepted to continue with the installation. Screen capture available in the Single Server Install chapter


Screen capture available in the Single Server Install chapter



In this distributed install example, all components other than Content Manager will be unselected.

Specify the shortcut folder name and associated properties. Screen capture available in the Single Server Install chapter

On a C8SE Content Manager install, in addition to the C8 components, DB2 and WebSphere will be installed. It is therefore necessary to specify the source locations where the CD images were copied to in order for the C8SE scripts to launch the IBM installers.



Browse to or type in the source CD path for the listed products.





Important:

If you must make changes to the C8SE_env[.bat|.sh] script, then uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox now. More information on this is provided in the Manual Environment Changes section.



It is also possible that you simply want to defer the IBM product installation and configuration until a later time. In this case, you may also uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox and launch the script manually when you are ready.

“Start Cognos Configuration”


5.1.1 Manual Environment Changes

Information / steps for this section are identical to the single server install

section that can be found earlier in this document. Please reference the

appropriate chapter for more information and screen captures.

Reminder:

You may need to modify the DB2 User Credentials and home directory,

particularly on UNIX / Linux. The Manual Environment Changes section

under the Single Server install documents the steps required to accomplish

this task.



5.1.2 Manually Starting the IBM Product Install and Configuration




5.1.3 C8SE_master – Script Progress and Output




5.1.4 Script Completion

When the installation and configuration cycle has completed you will be returned to the command prompt. Note that in the case of a Cognos 8 Content Manager distributed install, IHS is not required and therefore will not be installed or configured. Now that the installation and configuration is complete, you may start the installed components / products at any time. The steps to start the products and test your environment are located later in this document. Cognos 8 Content Manager must be running before performing other component installs.

5.2 Cognos 8 Application Tier Component Install

The following screen captures show the UNIX install dialogs.

Reminder: Cognos 8 Content Manager must be installed, configured and operational before attempting to perform additional Cognos 8 Application Tier Component installs. Issetup must be invoked by passing command line parameters to enable the C8SE functionality. Open a command prompt and navigate to the C8 install directory or CD.







Enter or browse to a suitable installation location.



Select the Cognos 8 component(s) that you will be installing. This example run will be an Application Tier Components distributed install. The associated IBM products will be automatically selected based on the Cognos 8 components. Unselect all other components.

(Windows) Specify the shortcut folder name and associated properties. Screen capture available in the Single Server Install chapter

On an Application Tier Components install, in addition to the C8 components, DB2 client and WebSphere will be installed. It is therefore necessary to specify the source locations where the CD images were copied to in order for the C8SE scripts to launch the IBM installers. Browse to or type in the source CD path for the listed products.



The Application Tier Component only install prompts for the Gateway URI and Content Manager URI. Enter appropriate values for your environment using either host names or IP addresses.






Important:

If you must make changes to the C8SE_env[.bat|.sh] script, then uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox now. More information on this is provided in the next section. It is also possible that you simply want to defer the IBM product installation and configuration until a later time. In this case, you may also uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox and launch the script manually when you are ready.

Important:




5.2.1 Manual Environment Changes




Reminder:

You may need to modify the DB2 User Credentials and home directory,

particularly on UNIX / Linux. The Manual Environment Changes section

under the Single Server install documents the steps required to accomplish

this task.












When the installation and configuration cycle has completed you will be returned to the command prompt. Note that in the case of a Cognos 8 ATC distributed install, IHS is not required and therefore will not be installed or configured. If you are now ready to start the products and test your environment, skip to the appropriate chapter in this document.

5.3 Cognos 8 Gateway Install














In this distributed install example, all components other than Gateway will be unselected.

(Windows) Specify the shortcut folder name and associated properties. Screen capture available in the Single Server Install chapter

On a C8SE Gateway install, in addition to the C8 components, IBM HTTP Server will be installed. It is therefore necessary to specify the source location where the CD image was copied to in order for the C8SE scripts to launch the IBM installer. Browse to or type in the path to the location where you copied the WebSphere CD as this CD image contains both WebSphere and IHS.



The Gateway only install prompts for the Dispatcher URI. Enter an appropriate value for your environment using either host names or IP addresses.







Important:

If you must make changes to the C8SE_env[.bat|.sh] script, then uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox now. More information on this is provided in the next section. It is also possible that you simply want to defer the IBM product installation and configuration until a later time. In this case, you may also uncheck the “Launch Cognos 8 Special Edition Master Script” checkbox and launch the script manually when you are ready.

Important:









Except as noted, information / steps for this section are identical to the

single server install section that can be found earlier in this document.

Please reference the appropriate chapter for more information and screen

captures.

For Windows and UNIX / Linux, no user interaction is required for the IHS install and configuration.


When the installation and configuration cycle has completed you will be returned to the command prompt. Note that in the case of a Cognos 8 Gateway distributed install, DB2 and WebSphere are not required and therefore will not be installed or configured. Windows Example:



6 Managing the IBM Product Suite

The IBM documentation and web site should be consulted and used for full instructions on using these products. The basic commands are covered in this section to help you get up and running quickly. Included in the C8SE package is a DB2 documentation CD. For a single server install or for a distributed install, the product startup order is the same. For a distributed install, the Content Manager system must be up and running first, followed by the Application Tier Component system and the Gateway must be started last. On each system, DB2 must be started first (if installed), followed by WebSphere (if installed) and lastly IHS (if installed). In all cases (starting, stopping, managing) it is assumed you are logged in with a user account that has the appropriate administrative rights to perform the action requested.

6.1 IBM DB2 WSEE

On all platforms, DB2 will be installed in a path relative to the Cognos 8 install path entered into issetup.

Windows, UNIX & Linux:

<C8_Root>/IBM/DB2-91

6.1.1 Starting DB2

Windows:

You can use the Services dialog or start menu to start the DB2 server process.

UNIX / Linux:

Navigate to the $INSTHOME/sqllib/adm directory. Type in the following:

Steps for AIX only: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM

All UNIX / Linux platforms (including AIX): db2start

6.1.2 Stopping DB2

Windows:

You can use the Services dialog or start menu to stop the DB2 server process.

UNIX / Linux:

Navigate to the $INSTHOME/sqllib/adm directory. Type in the following: db2stop



6.2 IBM WebSphere

On all platforms, WebSphere will be installed in a path relative to the Cognos 8 install path entered into issetup.

Windows, UNIX & Linux:

<C8_Root>/IBM/WAS-61

6.2.1 Starting WebSphere

Windows:

You can start WebSphere from the Windows Start Menu.

All Platforms (including Windows):

Navigate to <C8_Root>\IBM\WAS-61\bin in a command / terminal window and issue the startServer command followed by the server name, server1.

Windows: startServer.bat server1

UNIX / Linux: ./startServer.sh server1

6.2.2 Stopping WebSphere

Windows:

You can stop WebSphere from the Windows Start Menu.

All Platforms (including Windows):

Navigate to <C8_Root>\IBM\WAS-61\bin in a command / terminal window and issue the stopServer command followed by the server name, server1.

Windows: stopServer.bat server1



UNIX / Linux: ./stopServer.sh server1

6.3 IBM HTTP Server (IHS)

On all platforms, IHS will be installed in a path relative to the Cognos 8 install path entered into issetup.

Windows, UNIX & Linx:

<C8_Root>/IBM/IHS-61

Once running, you can access the Cognos 8 portal using the URL http://localhost/cognos8

6.3.1 Starting IHS

Windows:

To start the web server, you can double-click on the Apache.exe. The prompt must remain open while using the web server. To install and start IBM HTTP Server as a service, run the following command: Apache –k install Apache –k start

UNIX / Linux:

Navigate to <C8_Root>/IBM/IHS-61/bin and enter:

apachectl start



6.3.2 Stopping IHS

Windows:

To stop the web server, you can close the window that opened when you ran Apache.exe or use the Services manager. To stop the IBM HTTP Server as a service, run the following command: Apache –k stop

UNIX / Linux:

Navigate to <C8_Root>/IBM/IHS-61/bin and enter:

apachectl stop



7 Uninstalling IBM and Cognos Products

The products that make up the Cognos 8 Special Edition should be uninstalled using the tools provided. Manual uninstalls (directory deletion) will often result in difficulties in reinstalling the products since files are left behind elsewhere on the disk.

It is recommended that the IBM products be uninstalled first, followed by Cognos 8 although the uninstall order is not mandatory as long as all products have been shutdown.

The uninstall process varies by platform and product and therefore specific examples have not been provided. Some notes or links have been provided that contain related information, but in all cases the customer documentation should be consulted.

Note that after performing an uninstall using the utilities provided, it is often necessary to manually remove some remaining files and / or directories. These typically contain configuration information that is purposely not removed as part of the uninstall.

7.1 IBM DB2 UDB / WSE

Follow the standard uninstall using the utilities / documentation provided by IBM. It is critical that you do not manually delete files / directories until the uninstall has been properly run. Included in the C8SE package is an IBM DB2 documentation CD.

7.2 IBM WebSphere

Follow the standard uninstall using the utilities / documentation provided by IBM. It is critical that you do not manually delete files / directories until the uninstall has been properly run.

Example (subject to change without notice):

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/info/exp/ae/tins_uninstall.html

7.3 IBM HTTP Server (IHS)

Follow the standard uninstall using the utilities / documentation provided by IBM.

Example (subject to change without notice):

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/aes/ae/tihs_uninstall.html

7.4 Cognos 8

Follow the standard uninstall using the utilities / documentation provided with the main Cognos 8 product.



8 Troubleshooting & Verification

The first place to look when troubleshooting an install is to check the various log files. C8SE (scripts) will try and log to <C8_Root>/logs/C8SE_install_<date>_<time>.log or <C8_Root>/C8SE/C8SE_install.log. Where possible, the various log files will be consolidated into the Cognos 8 Special Edition install log. The C8SE log file should be the first place to look if you encounter an install or configuration issue.

The IBM products write to an assortment of log files in various locations, some of which are identified here:

/tmp

/temp

<Drive>:\Documents and Settings\<User_ID>\Local Settings\Temp\<assorted file names>

<DB2_Install_Path>/log.txt

<DB2_Install_Path>/tmp/log.txt

<IHS_Install_Path>/ihsv6_install.log

<WAS_Install_Path>/profiles/default/logs

<WAS_Install_Path>/logs/update/6.0-WS-WAS-WinX32-RP0000002.instal/\updatelog.txt

Cognos 8 will write logs files in <C8_Root>/logs

Should you discover an error in the log and be able to correct the problem, then it may be possible to simply rerun the master script. Completed steps will be bypassed (see the triggers in Appendix A for more information on triggers) and it may therefore be successful the second time through. It is important to keep in mind that other phases of the installation and configuration may be affected by one of the earlier steps as well. For example, if DB2 does not install then it will not be possible to copy the db2java.jar file in a step that runs in a later script unless the trigger for that script is also reset.

In other cases it may not be possible to rerun the master. For example if DB2 installs using an incorrect user ID. It is therefore recommended that all IBM and Cognos products that were installed as part of the C8SE be uninstalled and the process restarted from scratch.

If the errors are minor then it may be possible to simply ignore them or complete the failed steps manually.

8.1 IBM Product Installer (DB2 and WAS)

Since the C8SE scripts wrap existing installers, it is often not possible to determine programmatically the cause of a failure or determine that there was one. In some cases the IBM product installer is called and exits without writing a log or providing any feedback since they are running in a silent mode. Should you encounter problems like this, the recommended troubleshooting technique is to launch the IBM product installer manually from the CD image (see the appropriate IBM documentation on how to perform this action) and make note of any error or failure messages in the installer dialog. Often system prerequisites such as disk or swap space, user privileges and previous product installs are the cause of this behaviour. It will be necessary to uninstall the product after the manual install to allow the scripts to pass the appropriate values via a response file.



8.1.1 Forcing an Install

Under certain circumstances, installation of the IBM product site will fail. One typical failure is a pre-requisite check failure issued by the IBM installer. In these cases, it is suggested that you manually review the installation requirements for the IBM product in question by visiting the appropriate web page. Should the error be thrown in error, then it is possible to force an install using one of the methods described below.

8.1.1.1 IBM DB2 on HP/UX 11v3 (note support has been removed for this release)

Installing IBM DB2 on HP-UX 11v3 (11.31) will issue a pre-requisite failure in the logs and DB2 will not be installed (T#579439). The C8SE_install_{date}.log will indicate the following:

Verify your system is at or above the appropriate patch level for IBM DB2 v9.1. If it is, then edit <c8_root>/C8SE /C8SE_install_DB2-91.sh Add a new line right after

That contains:

8.1.1.2 IBM WAS and IHS Installation Fails on Unix

After running the Cognos 8 Special Edition install, IBM WebSphere and IHS will not be installed (T#580216) and the C8SE logs will contain the following error message:

This error can be thrown when your maintenance level exceeds the required minimum maintenance level. Check to ensure your system is in compliance and then bypass the pre-requisite check.

“07-11-03 12:23:17 INFO: DB2-91: Running db2setup -r /{path}/C8SE/C8SE_rspfile_DB2-91.rsp ERROR: The required bundle is not found on the system : QPKAPPS (minimum version: 11.23.0505) ERROR: The required bundle is not found on the system : QPKBASE (minimum version: 11.23.0505) Check the following web site for the up-to-date system requirements of IBM DB2 Version 9.1: http://www.ibm.com/software/data/db2/udb/sysreqs.html Aborting the current installation ...

Run installation with -f parameter to force the installation.”

C8SE_DB2_options="-f"

# C8SE_DB2_options="-t ${C8SE_scripts}/../logs/C8SE_DB2_install.log"

(Date & Time), Process, com.ibm.ws.install.ni.ismp.actions.MaintenancePrereqCheckAction, err, CWUPI0037E: A supported operating system architecture was not detected. Support for your operating system architecture might have been added after the release of the product. You can continue with the installation, but the installation might not succeed. See the WebSphere Application Server supported hardware and software Web pages at http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html for more information about supported operating systems



Example: We have encountered this issue on an AIX 5.3 system with ML6 installed. ML4 is the minimum requirement for WebSphere 6.1.0.3 % oslevel -r 5300-06 % instfix -i|grep AIX_ML All filesets for 5.3.0.0_AIX_ML were found. All filesets for 5300-01_AIX_ML were found. All filesets for 5300-02_AIX_ML were found. All filesets for 5300-03_AIX_ML were found. All filesets for 5300-04_AIX_ML were found. All filesets for 5300-05_AIX_ML were found. All filesets for 5300-06_AIX_ML were found. Bypass the prerequisite checks by editing the files <cognos8>/C8SE/C8SE_install_WAS-61.sh and <cognos8>/C8SE/C8SE_install_IHS-61.sh Uncomment the following line in both files (remove the #) #echo -OPT disableOSPrereqChecking="true">>${RESPONSE_FILE} Clear existing Special Edition products from the system (using the appropriate uninstall programs) and run the Cognos 8 Special Edition install again.

8.1.1.3 IBM WebSphere does not install on Linux

After running the Cognos 8 Special Edition on Linux, IBM WebSphere is not installed (T#580959 Uninstall the Cognos 8 Special Edition product suite using the appropriate uninstall tools. Alter the script edit <c8_root>/C8SE/C8SE_install_WAS-61.sh Change the line that contains: ./install -options ${RESPONSE_FILE} -is:javahome ${JAVA_HOME} -silent >>${C8SE_logfile} To ./install -options ${RESPONSE_FILE} -is:javaconsole -silent >>${C8SE_logfile} Rerun the Cognos 8 Special Edition install

8.2 IBM DB2 Database Configuration Error

Accessing the Past Activities tab in the Cognos Administration portal generates the following error (T#580675): SOAPFaultException NAV-ERR-1001 Content Manager returned an error. A more detailed error message will be logged. The Cognos 8 cogserver.log will contain the error SQL1585N A system temporary table space with sufficient page size does not exist. SQLSTATE=54048

If you encounter this error, use the IBM DB2 tools to recreate the System Temporary Tablespace with a 32K PageSize



Option 1 – Cognos 8 Special Edition is installed

Replace {C8SE_DB2_Dst} in the line below with the path (C:\cognos8SE\c8\IBM\DB2-91 for example)

Option 2 – Cognos 8 Special Edition is not installed or can be reinstalled

If Cognos 8 Special Edition has not yet been installed (or if you uninstall all Cognos 8 Special Edition products and reinstall), then you can avoid this error by editing the file <cognos8_root>/C8SE/C8SE_template_DB2-91.db2 1) After this line:

Add

2) Change:

To

Run the Cognos 8 Special Edition installation.

CONNECT TO CM CREATE BUFFERPOOL "CM_32KBP" IMMEDIATE SIZE 250 PAGESIZE 32K NOT EXTENDED STORAGE DROP TABLESPACE TSN_SYS_CM CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_CM IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32K MANAGED BY SYSTEM USING ('{C8SE_DB2_Dst}/CNT_SYS_CM') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL CM_32KBP ALTER TABLESPACE TSN_SYS_CM OVERHEAD 10.5 TRANSFERRATE 0.14 COMMIT

CONNECT RESET

C8SE_DB2_Command CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_C8SE_C8_DB_Name IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 16K MANAGED BY SYSTEM USING ('C8SE_DB2_Dst/CNT_SYS_C8SE_C8_DB_Name') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL C8SE_C8_DB_Name_16KBP

C8SE_DB2_Command CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_C8SE_C8_DB_Name IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32K MANAGED BY SYSTEM USING ('C8SE_DB2_Dst/CNT_SYS_C8SE_C8_DB_Name') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL C8SE_C8_DB_Name_32KBP

C8SE_DB2_Command CREATE BUFFERPOOL "C8SE_C8_DB_Name_32KBP" IMMEDIATE SIZE 250 PAGESIZE 32K NOT EXTENDED STORAGE

C8SE_DB2_Command CREATE BUFFERPOOL "C8SE_C8_DB_Name_16KBP" IMMEDIATE SIZE 250 PAGESIZE 16K NOT EXTENDED STORAGE



8.3 IBM DB2 License Registration

The IBM DB2 logs will show the following error (T#580811):

Manually register IBM DB2 Workgroup Server Edition. Windows: go to the <db2>\bin directory Unix: source sqllib/db2cshrc and go to the <db2>/adm directory Copy the db2wse_c.lic file (available from Cognos Customer Support) to this directory and run “db2licm -a db2wse_c.lic” to import the license. Run “db2licm –l” to list the current license information. Windows Example:

ADM12026W The DB2 server has detected that a valid license for this product has not been registered.

db2\BIN>db2licm -l Product name: "DB2 Workgroup Server Edition" License type: "License not registered" Expiry date: "License not registered" Product identifier: "db2wse" Version information: "9.1" Max number of CPUs: "4" Max amount of memory (GB): "16" Annotation: "1;(_b)" dbB2\BIN>db2licm -a db2wse_c.lic LIC1402I License added successfully. LIC1426I This product is now licensed for use as specified in the License Agreement and License Information documents pertaining to the licensed copy of this product. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT AND LICENSE INFORMATION DOCUMENTS, LOCATED IN THE FOLLOWING DIRECTORY: "C:\xxx\license\en" db2\BIN>db2licm -l Product name: "DB2 Workgroup Server Edition" License type: "CPU" Expiry date: "Permanent" Product identifier: "db2wse" Version information: "9.1" Max number of CPUs: "4" Max amount of memory (GB): "16" Annotation: "3;(_c)" Features: DB2 Performance Optimization WSE: "Not licensed" DB2 High Availability WSE: "Not licensed" Homogeneous Federation for DB2: "Not licensed" DB2 Workload Management WSE: "Not licensed" DB2 Pure XML WSE: "Not licensed"



8.4 Distributed Installation

8.4.1 Application Tier Installation (No Content Manager)

The Cognos 8 cogserver.log will contain the following error (T#580312):

If you encounter this error, start Cognos Configuration and manually enter the Notification Database information. Save and exit Cognos Configuration. Restart the WebSphere Application server instance.

8.4.2 Gateway Installation

The C8SE installation will exit prematurely and the following error message will appear on the C8SE_install.log file (T#580318):

The Cognos 8 Gateway installation will not be properly configured. If you encounter this error, start Cognos Configuration and manually enter the Dispatcher URI for gateway information. Save and exit Cognos Configuration. Restart IBM HTTP Server.

8.5 IBM WebSphere

The following sections provide a means to verify the configuration and operation of the various products.

8.5.1 WebSphere Configuration

Should you encounter memory issues or have difficulty connecting to the Content Store database, manually verify that WebSphere has been configured correctly. Access the WebSphere Administration Console using the default URL http://localhost:9060/admin. A User ID is not required at this point unless there is more than one person administering the system.

The administration console will load and the correct version information should be displayed in the upper right of the console (WebSphere Application Server Express 6.1.0.3).

CNC-SDS-0256 Unable to connect to the database using jdbc:JSQLConnect://localhost:1433/cm.

{date} {Time} FATAL: C8: Unable to locate "\java\jre\lib\ext\bcprov-jdk14-134.jar"



Select Applications -> Enterprise Applications and you should see Cognos 8 in the list of deployed applications.

Select Servers -> Application Servers, click on server1 to access the server properties.

Select Java and Process Management under the Server Infrastructure section.



Under the expanded Java and Process Management section click on the Process Definition link.

On the Process Definition page, Under Additional Properties, click on the Custom Properties link.

The IBM DB2 environment variables should be listed along with a Path / SHLIB_PATH / etc. environment variable. (Example below is for Windows)



8.5.2 Cognos 8 Content Manager Application

After starting the server1 instance in WebSphere (verify it is running through administration console as indicated above), you can check the state of Cognos 8 Content Manager. On the server where Cognos 8 Content Manager is installed (or replace localhost with the appropriate host name or IP address), open a browser and enter the URL http://localhost:9080/p2pd/servlet. The build number and state will be displayed. If the state is “not running” check the Cognos 8 and WebSphere logs for more information. Note that DB2 must also be running in order for Content Manager to start correctly.

8.5.3 Cognos 8 Application Tier

If the Application Tier is installed and running (as indicted in the WebSphere Administration Console) you can also verify that it is operational by opening a browser window and entering the URL: http://localhost:9080/p2pd/servlet/dispatch.

The Cognos 8 portal page should load, but the icons, images, style sheets etc. will not load since by default the application is built and deployed without the static content files.



9 Error Messages

The C8SE install will log pertinent information to a text file located in <C8_Root>/logs. This file should be examined after the installation and configuration has completed for errors such as those listed below. In addition, critical errors will also be output to the console window.

9.1 JAVA_HOME environment variable has not been set

Message: JAVA_HOME environment variable has not been set.

Platform: UNIX / Linux

Cause: C8SE scripts require access to a JRE / JDK in order to perform certain actions. The scripts check for the presence of an environment variable called “JAVA_HOME” that points to an acceptable version.

Solution: Install a JRE or JDK and set an environment variable JAVA_HOME prior to running the C8SE scripts.

9.2 XML Parser - Transformation Aborted

Message: Transformation aborted. XML Parser error: can't declare any more prefixes in this context - uri = file :/{Path}/c8/C8SE/C8SE_config_DB2-82.xslt - line = 2 - column = -1

Cause: There is an incompatibility in the JRE used to perform the install and configuration due to the way certain functions were implemented by the vendor. Solution: Set JAVA_HOME to an alternate JRE, preferably a Sun JRE if it is available for that platform. Perform a cleanup and run the installation again.

9.3 CM-CFG-5063 / CM-SYS-5003 / SQL1032N

Message: StartService Warning CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. CM-SYS-5003 Content Manager is unable to access the content store. Verify your database connection parameters and then contact your database administrator. [IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019 Cause: DB2 is not running and Cognos 8 Content Manager attempted to connect to the Content Store. Solution: Start DB2, restart WebSphere once DB2 is running.



9.4 Setuid execution is not allowed

Message: <path>/das/adm/db2dasrrm: Setuid execution not allowed Cause: The volume on which DB2 is being installed / configured does allow the Switch User function to be called. Solution: Remount the volume with the setuid flag enabled.

9.5 SQL1225N / SQLSTATE=57049

Message: SQL1225N The request failed because an operating system process, thread, or swap space limit was reached. SQLSTATE=57049

Cause: DB2 cannot be configured because of a system limitation. Solution: Check swap space and O/S kernel parameters to ensure they meet IBM DB2 system requirements.

9.6 Warnings / Errors that are safe to ignore

When examining the C8SE installation and configuration log file, there are many instances where warning messages are displayed. Many of these are expected and will be identified below. These warnings and errors can safely be ignored as they have no impact on the proper operation of your environment.

9.6.1.1 WASX7017E

Message: Exception received while running file "/{Path}/c8/C8SE/C8SE_config_WAS6.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7254E: "startServer" action not supported when process type is "UnManagedProcess"

Solution: Ignore message

9.6.1.2 ADMA0080W / WASX7327I

Message: ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application. You can modify the Java 2 Security policy for the enterprise application by editing the was.policy file that is located in the ${user.install.root}/config/cells/(yourCellName)/applications/(yourAppName).ear/deployments/(yourAppName)/META-INF directory after the application is installed. WASX7327I: Contents of was.policy file: // // Template policy file for enterprise application. // Extra permissions can be added if required by the enterprise application. // // NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.



// Extreme care should be taken when editing these policy files. It is advised to use // the policytool provided by the JDK for editing the policy files // (WAS_HOME/java/jre/bin/policytool). //


9.6.1.3 DB21034E / SQL0554N

Message: DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0554N. An authorization ID cannot grant a privilege to itself.


9.6.1.4 CMcheck

Message: [available] DEPRECATED - <available> used to override an existing property. [available] Build file should not reuse the same property name for different values. Solution: Ignore message

9.6.1.5 DB2 WARNING

Message: WARNING:Notification SMTP server has not been specified. Notifications cannot be sent to contacts in your contact list until this is specified. For more information see the DB2 administration documentation. Solution: Ignore message

9.6.1.6 Error or Fatal Log Entry for “File <name> will be modified”

Message: <date> <time> ERROR|FATAL: <product>: File <name> will be modified Cause: incorrect label of the message. Should have been “INFO:”. Future releases will correct this. Solution: Ignore message



Appendix A - Script Functions

The following table lists the scripts and the main functions that will be accomplished when this script is run. Should a step fail in the installation and configuration process, it may be possible to correct the underlying cause and rerun the master script (or in some cases the individual script). Under the script name in the table some trigger are listed. Typically if these files are present, it indicates that that phase of the install or configuration has been run previously so it will be bypassed by the script unless you manually delete the trigger file.

The preferred solution is to perform an uninstall of all the products (instructions provided in the Uninstalling IBM and Cognos Products chapter), cleanup and outstanding files / directories and start with a fresh install.

Script Name Main Functions

C8SE_env • Created by ISSetup and contains default environment variables that may be modified by the user

C8SE_master_env • Contains default values used by all scripts that must not be changed by the user

C8SE_master

• Creates a name for the log file based on Date and Time values from the OS

• Load dynamic environment variables (User changeable) from C8SE_env

• Load static environment variables from C8SE_master_env

• Dump “cmplst.txt” to the log file

• Loop to run:

� C8SE_install_DB2-91

� C8SE_install_WAS-61

� C8SE_install_IHS-61

• Loop to run:

� C8SE_config_DB2-91

� C8SE_config_WAS-61

� C8SE_config_IHS-61

� C8SE_config_C8

• Clear environment variables

C8SE_install_DB2-91

The DB2 install script will not run if:

C8SE_DB2_Src is not set

C8SE_install_DB2-91.flg exists



• Check to see if DB2 is already installed

• Check to see if the install utility is in the proper source directory

• Build an install response file based on the install type (Server for CM install, client for CM and ATC install)



• Launch the DB2 installer passing the response file as an input

• Copy the install logs into the C8SE logs

C8SE_install_WAS-61

The WAS install script will not run if:

C8SE_WAS_Src is not set

C8SE_install_WAS-61.flg exists

The WAS updater will not run if {C8SE_WAS_Dst}/updateinstaller/update.exe exists



• Check to see if WAS is already ready installed


• Build an install response file

• Launch the WAS installer passing the response file as an input

• Check to see if the WAS update has already run

• Call “setupCmdLine” from the WAS install to set environment variables

• Call “backupConfig” from the WAS install to save a default copy of the configuration

• Check to see if the updater utility is in the proper source directory

• Copy the update installer from the source directory to the WAS install directory.

• Launch the update installer passing the default response file as an input


C8SE_install_IHS-61

The IHS install script will not run if:

C8SE_IHS_Src is not set

C8SE_config_IHS-61.flg exists



• Check to see if IHS is already ready installed


• Build an install response file

• Launch the IHS installer passing the response file as an input


C8SE_config_DB2-91

The DB2 config script will not run if:

C8SE_DB2_Src is not set

C8SE_config_DB2-91.flg exists



• Verify DB2 was installed

• Verify JAVA_HOME is set



{C8}/configuration/cogstartup.xml does not exist

• Verify cogstartup.xml is available for modification and make a backup copy

• Verify the jar files for the xslt transformation have been installed

• Use C8SE_template_DB2-91.xslt as a base and replace the CM database name and user credentials. The template is also preset to remove the Cognos Bootstrap Service (CBS)

• Apply the xslt transformation file against cogstartup.xml

• Copy the db2java.jar database client driver from the DB2 install into the C8 install so that it can be bundled into the ear file for deployment into WebSphere

• Use C8SE_template_DB2-91.db2 as a base and replace the User ID tokens with actual values

• Run the DB2 script using the DB2 utilities. Unix: switch users to the db2administrative account and run the script. This set of commands will create the DB2 database instance and setup appropriate base values within DB2 for table space, temp space etc.

C8SE_config_WAS-61

The WAS config script will not run if:

C8SE_WAS_Src is not set

C8SE_config_WAS-61.flg exists



• Verify that the configuration has not already been performed

• Build the p2pd application file

• Copy the BouncyCastle security provider file from the C8 install into the JRE used by WebSphere

• Run “setupCmdLine” from the WAS install to set WAS specific environment variables

• Use the C8SE_template_WAS6.jacl file as a base and replace the token values with actual values for servername, nodename, install paths, DB2 environment variables, etc.

• Run the jacl script through wsadmin to:

� Set the maximum heap size to the default value (768)

� Set the DB2 environment variables

� Set the Path (or appropriate Unix equivalent) to C8/bin

� Deploy the application file

• Restart WebSphere to ensure the application is deployed and the classloader is reset

• Remove the p2pd.ear application file

C8SE_config_IHS-61




The IHS config script will not run if:

C8SE_IHS_Src is not set

C8SE_config_IHS-61.flg exists



• Backup the httpd.conf file

• Append the C8 specific information to the http.conf file

C8SE_config_C8

The C8 config script will not run if:

C8SE_config_C8.flg exists




• Verify JAVA_HOME is set appropriately. Verify and take a backup copy of cogstartup.xml prior to making modifications

• Use C8SE_template_C8.xslt as a base and replace tokens with appropriate URI values

• Run the xslt transformation to modify the cogstartup.xml file

• Run Cognos Configuration in silent mode to apply the cogstartup.xml changes and create encryption keys (if appropriate based on install type)

• Append the Cognos Configuration log to the C8SE log

C8SE_template_C8.xslt • Used by C8SE_config_C8 for xslt transformations against cogstartup.xml

C8SE_template_DB2-94.xslt • Used by C8SE_config_DB2-91 for xslt transformations against cogstartup.xml

C8SE_template_DB2-91.DB2 • Used by C8SE_config_DB2-94 as an input to the DB2 command that will create the DB2 instance and set default values

C8SE_template_WAS-61.jacl • Used by C8SE_config_WAS-61 to modify the WebSphere configuration, set environment variables and deploy the C8 application on Windows

C8SE_U_template_WAS-61.jacl • Used by C8SE_config_WAS-61 to modify the WebSphere configuration, set environment variables and deploy the C8 application on Unix