IBM Cognos Command Center Version 10.2.0: Installation...

IBM Cognos Command CenterVersion 10.2.0

Installation Guide

��

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

Product Information

This document applies to IBM Cognos Command Center Version 10.2.0 and may also apply to subsequent releases.

Licensed Materials - Property of IBM

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

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1. Overview of IBM Cognos Command Center . . . . . . . . . . . . . . . 1Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. IBM Cognos Command Center installation prerequisites . . . . . . . . . . 5Preparations for installing the agent component . . . . . . . . . . . . . . . . . . . . . . . 5Preparations for installing the server component . . . . . . . . . . . . . . . . . . . . . . . 5

Server installation prerequisites for an Oracle database in a 64-bit environment . . . . . . . . . . . . 6Preparations for installing the web application component . . . . . . . . . . . . . . . . . . . . 7

Chapter 3. Upgrade IBM Cognos Command Center software . . . . . . . . . . . . . 9

Chapter 4. Installing IBM Cognos Command Center . . . . . . . . . . . . . . . . 11Installing the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring the server repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting the server connection parameters . . . . . . . . . . . . . . . . . . . . . . . . 12Setting the server configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . 13

Installing the agent component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing the client component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installing the web application component . . . . . . . . . . . . . . . . . . . . . . . . . 16

Completing the web client installation . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing the command line client component . . . . . . . . . . . . . . . . . . . . . . . . 19Finishing the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 5. Starting IBM Cognos Command Center . . . . . . . . . . . . . . . . . 21Starting the server from the server installation directory . . . . . . . . . . . . . . . . . . . . 21Starting the agent component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Starting the client component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Starting the web client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 6. Post installation configuration . . . . . . . . . . . . . . . . . . . . . 23Certificates for securing communication . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing the server host certificate on Windows 2003 or 2008 operating systems . . . . . . . . . . . 24Installing the server host certificate on Windows Vista or Windows 7 operating systems. . . . . . . . . 25Configuring the client-to-server port when HTTPS is the chosen protocol. . . . . . . . . . . . . . 25

Securing the installation with a password . . . . . . . . . . . . . . . . . . . . . . . . . 26Configuring an external authentication server . . . . . . . . . . . . . . . . . . . . . . . . 26Registering agents with your server . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installing plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Setting up email notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Setting up the event listener module . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Starting processes with an external application . . . . . . . . . . . . . . . . . . . . . . 30Editing the event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Setting up a high availability server . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installing the server component on the secondary host . . . . . . . . . . . . . . . . . . . . 31Configuring failover settings on the primary server host . . . . . . . . . . . . . . . . . . . 32Configuring the message queue for high availability on systems that use an SQL Server RDBMS . . . . . . 32Configuring the message queue for high availability on systems that use an Oracle RDBMS . . . . . . . 33

Appendix. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Viewing the system log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

© Copyright IBM Corp. 2008, 2013 iii

Log file for the server component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Troubleshooting failures of the high availability server . . . . . . . . . . . . . . . . . . . . . 35

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

iv IBM Cognos Command Center Version 10.2.0: Installation Guide

Introduction

This document provides information to help system administrators install andconfigure IBM® Cognos® Command Center® software.

Finding information

For information on supported environments and system requirements for IBMCognos Command Center, see the IBM Software Product Compatibility Reports(http://www.ibm.com/support/docview.wss?uid=swg27039626).

To find IBM Cognos Command Center product documentation on the web, accessthe IBM Cognos Information Center (http://pic.dhe.ibm.com/infocenter/ccc/v10r2m0/index.jsp). Release Notes are published directly to Information Centers,and include links to the latest technotes and APARs.

You can also access PDF versions of the product documentation from the productdisks or from the IBM Cognos Command Center documentation web page(http://www.ibm.com/support/docview.wss?uid=swg27039519).

For information about using IBM Cognos Command Center, see the IBM CognosCommand Center Administration Guide.

Accessibility features

IBM Cognos Command Center does not currently support accessibility featuresthat help users with a physical disability, such as restricted mobility or limitedvision, to use this product.

Forward-looking statements

This documentation describes the current functionality of the product. Referencesto items that are not currently available may be included. No implication of anyfuture availability should be inferred. Any such references are not a commitment,promise, or legal obligation to deliver any material, code, or functionality. Thedevelopment, release, and timing of features or functionality remain at the solediscretion of IBM.

© Copyright IBM Corp. 2008, 2013 v

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

http://pic.dhe.ibm.com/infocenter/ccc/v10r2m0/index.jsp

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

vi IBM Cognos Command Center Version 10.2.0: Installation Guide

Chapter 1. Overview of IBM Cognos Command Center

IBM Cognos Command Center provides a centralized, fully integrated, secure, andhighly extensible environment for system monitoring and automation.

The software manages script and batch files that are spread over multiple serverenvironments, in a central environment. Cognos Command Center reduces the costof maintenance and simplifies the work flow of automated and manual processes.

ComponentsThe IBM Cognos Command Center software includes multiple components.

The Cognos Command Center software includes the following components:

Cognos Command Center serverThe central Cognos Command Center component handles all theprocessing logic, scheduling, event listening, and connections to theCognos Command Center agents and email servers. For the optional highavailability feature, a second instance of the server is installed.

Cognos Command Center repositoryA relational database that holds all system objects, event history, andsecurity information for the Cognos Command Center environment. Therepository can be on the same workstation or on a different workstationthan the Cognos Command Center server.

Cognos Command Center agentsAgents are installed on hosts where Cognos Command Center tasks, suchas scripts, are run.

Cognos Command Center message queueHandles all communication between the server, agents and, if applicable,other high availability servers for fail over.

Cognos Command Center clientThe primary Cognos Command Center interface for users andadministrators. This component is a Microsoft Windows application thatprovides full design, administration, and monitoring features.

Cognos Command Center web applicationA secure web browser user interface for running and monitoring CognosCommand Center processes.

Cognos Command Center command line clientA Microsoft Windows command line application. The client can query,start, pause, and stop Cognos Command Center processes, test agentconnectivity, and perform full and partial exports of the repository.

© Copyright IBM Corp. 2008, 2013 1

System architectureIBM Cognos Command Center has a distributed system architecture that allows forvariation to best fulfill your requirements.

Communication between Cognos Command Center clients and the server, usesWindows Communication Foundation (WCF). WCF can be configured to TCP orSOAP 1.2 Web HTTP or HTTPS. Communication between the Cognos CommandCenter server and the agents, uses HTTPS.

When you install the Cognos Command Center components, you have the optionof selecting the appropriate network protocol for your environment: TCP, HTTP, orHTTPS.

Regardless of which network protocol you choose, all communication is secure andencrypted. Cognos Command Center also integrates with external authenticationservers, and SMTP servers to enable email alert integration and event-basedprocessing of automation requests.

Figure 1. Cognos Command Center System Architecture

2 IBM Cognos Command Center Version 10.2.0: Installation Guide

High availabilityIBM Cognos Command Center can optionally be configured for high availability. Ahigh availability configuration provides a more robust and fail-tolerant automationsystem.

The key features of a high availability system are as follows:v Redundant servers in a master and subordinate setup with a hot standby

subordinate stands ready to take over processing when the master is stopped orfails.

v Redundant message queue in a master and subordinate setup, allowing agentsto send asynchronous status events regardless of the availability of the server.

v A software-assisted switchover mechanism for the client, allowing users toreconnect when a master server is stopped.

Figure 2. Cognos Command Center System Communication

Chapter 1. Overview of IBM Cognos Command Center 3

The following Cognos Command Center components are involved in a highavailability system:

Cognos Command Center serverThe server is installed on two separate servers and operates in a masterand subordinate configuration. Only one server instance is active at a time,handling user requests and controlling automation processes. The twoinstances share the Cognos Command Center repository and synchronizethe master and subordinate role through a locking shared databaseresource.

Cognos Command Center message queueThe message queue middleware also operates in a master and subordinateconfiguration. The two instances of the message queue, use the CognosCommand Center repository to synchronize the master and subordinaterole. The repository also stores events that will be consumed by the masterserver instance.

Cognos Command Center repositoryThe central RDBMS (relational database management system) for allCognos Command Center objects and pending agent messages. Therepository is the only single point of failure on a high availability systemso the RDBMS must be running in a standard clustered configuration.

Cognos Command Center agentsAgents send messages to the current master server by way of the currentmaster message queue instance. If agents fail to deliver events to thecurrent master queue, they automatically switch over to the alternativemessage queue instance.

Figure 3. Cognos Command Center high availability configuration


Chapter 2. IBM Cognos Command Center installationprerequisites

There are preinstallation tasks that you must perform before you install the IBMCognos Command Center software. If you plan to install the agent, the server, orthe web application components, there are additional preinstallation tasks.

Before you install Cognos Command Center, perform the following tasks:v Verify that you have the necessary software, a license key, and documentation.v When you install IBM Cognos Command Center for the first time, you must first

design your system and identify computers for each Cognos Command Centercomponent. For more information, see “System architecture” on page 2.

For each workstation that you designate for the installation, perform the followingtasks:v Install Microsoft .NET Framework.v Review and meet the minimum system requirements for each component that

you plan to install. For information on supported environments and systemrequirements for IBM Cognos Command Center, see the IBM Software ProductCompatibility Reports (http://www.ibm.com/support/docview.wss?uid=swg27039626).

If you are upgrading Cognos Command Center, see Chapter 3, “Upgrade IBMCognos Command Center software,” on page 9.

Preparations for installing the agent componentThere are preinstallation tasks you must perform before you install the IBMCognos Command Center agent component.

The Cognos Command Center agent runs on Microsoft Windows operatingsystems and on variants of UNIX and Linux operating systems.

For information on planning and installing the agent component on a UNIX orLinux system, see the IBM Cognos Command Center for UNIX Agents InstallationGuide.

If you plan to install the agent component on a Microsoft Windows operatingsystem, create a dedicated local Microsoft Windows account named cccAgent andrun the cccAgent Microsoft Windows service under this account.

You can configure the account during the installation, but before you install theagent, ensure that the account has read access to the cccAgent installation directory.The default directory is C:\Program Files (x86)\IBM\Cognos Command Center.

Preparations for installing the server componentThere are preinstallation tasks that you must perform before you install the IBMCognos Command Center server component.




The Cognos Command Center server requires a relational database managementsystem (RDBMS) repository, in either a Microsoft SQL Server or an Oracledatabase. If you plan to install the server component, you must also meet thesystem requirements for the repository.

If you use an Oracle RDBMS and want to maintain full control over the databaseparameters, ask your system administrator to create a new, empty schema in theOracle database before you run the installation wizard. For more information, see“Configuring the server repository” on page 12.

Server installation prerequisites for an Oracle database in a64-bit environment

If you use an Oracle database in 64-bit Microsoft Windows environment, there aresteps you must take before you run the IBM Cognos Command Center installationwizard. You must install the Oracle 32-bit driver and temporarily change thevalues for several Windows system, environmental variables. These steps arerequired because installation wizard runs as a 32-bit application.

About this task

After you install the Oracle 32-bit driver, you point your TNS settings to the 32-bitOracle client folder. After the installation, revert your TNS settings to point to the64-bit driver before you start the Cognos Command Center server.

Procedure1. Install the Oracle 32-bit driver using the Administrator option.2. In the Windows Control Panel, navigate to System > Advanced system

settings > Environmental Variables.3. In the System variables list, find the TNS_NAME variable and the

ORACLE_HOME variable. If you do not see these two variables, create them.4. For the ORACLE_HOME variable, ensure the value points to the 32-bit Oracle

driver folder. For example: C:\oracle\product\10.2.0.5. For the TNS_NAME variable, ensure the value points to the tnsname.ora file

folder. For example: C:\oracle\product\10.2.0\network\Admin.6. To save your system variables, click OK.7. Verify that the tnsname file folder has the most recent tnsname.ora files.8. At the command prompt, run the tnsping [Oracle_DB_NAME] command to

test your Oracle DB connection. Ensure that your test is successful before youproceed to the next step.

9. You can now proceed to install Cognos Command Center. During theinstallation, when you set the server configuration parameters, clear the Startservice check box. If this step is not done, the installer will attempt to start theserver service after the installation, and you can receive an error message.

10. After installation, before you start the Cognos Command Center serverWindows service, change the values of your TNS_NAME andORACLE_HOME variables to point to your 64-bit Oracle driver folder. You cannow start the Cognos Command Center server Windows service. The queuestarts automatically after you start the server. You can start the agent service.You can now use the Cognos Command Center client to log on to the CognosCommand Center server.

11. Optionally, uninstall the Oracle 32-bit driver.


Preparations for installing the web application componentThere are preinstallation tasks that you must perform before you install the IBMCognos Command Center web application component.

To use the web client, you must install and configure Microsoft IIS (InternetInformation Service). Install the appropriate version of IIS on each workstation.The IIS version that you choose depends on the Windows operating systemversion.v For Windows 2003 or Windows 2003 R2, install IIS version 6.0v For Windows 2008, install IIS version 7.0v For Windows 2008 R2, install IIS version 7.5

Install IIS for Microsoft Windows 2003 and 2003 R2 operatingsystems

For information on installing IIS, see Microsoft Windows documentation. Thefollowing information can help you with your installation of IIS:

In Microsoft Windows, when you open the Add / Remove Programs page andclick Change Windows Components, select the Application Server check box, andthen click Details. Select the ASP.NET check box, and then click Enable networkCOM+ access. Select the Internet Information Services (IIS) check box, and thenclick Details. Select the World Wide Web Services check box, and then clickDetails. Select the Active Server Pages and World Wide Web Service check boxes.

You must also configure IIS, but you perform this task in the Cognos CommandCenter installation wizard.

Install IIS for Windows 2008 and 2008 R2 operating systems

Install IIS version 7.0 on workstations with Microsoft Windows 2008 operatingsystems or IIS version 7.5 on workstations with Microsoft Windows 2008 R2operating systems. The installation procedures are the same for both IIS versions.For information on installing IIS, see Microsoft Windows documentation. Thefollowing information can help you with your installation of IIS:

In the Microsoft Windows Server Manager's Add Roles Wizard, add or expandWeb Server (IIS) role services, accept the set of required role services in the pop upwindow, and ensure the selected check boxes include the Application DevelopmentASP.NET and the Management Tool IIS Management Console.

You must also configure IIS, but you perform this task in the Cognos CommandCenter installation wizard.

Chapter 2. IBM Cognos Command Center installation prerequisites 7


Chapter 3. Upgrade IBM Cognos Command Center software

When you upgrade to a new version of IBM Cognos Command Center, you createa backup copy of your Cognos Command Center repository database and then runthe installation wizard.

Before you upgrade to a new version of Cognos Command Center software, createa backup copy of your repository database.

You do not need to uninstall the existing installation of the software. You run theunified installation wizard and the wizard installs the new version on top of theexisting version. The existing configuration values and information are retained sothat the fields in the pages of the wizard are pre-populated.

The installation wizard does not delete a prior database. You point the newinstallation to the existing database when you run the installation wizard. On theDatabase Type Selection page of the wizard, select the Use exiting database option.For more information, see “Configuring the server repository” on page 12.



Chapter 4. Installing IBM Cognos Command Center

IBM Cognos Command Center has a unified installation wizard that installs all theCognos Command Center components that you select. In the wizard, you can alsocreate or update the RDBMS repository.

Before you begin

Ensure that you have met the requirements and prepared to install CognosCommand Center components. For more information, see Chapter 2, “IBM CognosCommand Center installation prerequisites,” on page 5.

About this task

The installation wizard leads you through the installation of one or more of thefollowing components:v Clientv Command line clientv Agentv Serverv Web application

Run the installation wizard on each Microsoft Windows workstation in yourCognos Command Center system, and select one or more components for eachinstallation.

Procedure1. Run the IBMCognosCommandCenterStarter.10.2.msi file or the

IBMCognosCommandCenterStandard.msi file. The installation wizard opens.2. In the wizard, follow the prompts to proceed with the installation.

Installing the serverIf you install the server component of IBM Cognos Command Center, theinstallation wizard leads you through configuring the following serversubcomponents: the repository, connection parameters, and configurationparameters.

About this task


The repository can be on the Cognos Command Center server workstation or on adifferent workstation. The Cognos Command Center server process requiresread/write access to the database. During the installation process, a connectionmust be made to the database, otherwise the Cognos Command Center serverinstallation terminates.


Procedure

In the wizard, click Next to proceed with the installation.

Configuring the server repositoryThe IBM Cognos Command Center server component uses a database repository.The installation of the server requires that you select an Oracle or an SQL Serverrelational database management system (RDBMS).

About this task

The RDBMS database can reside on a different workstation than the servercomponent, but the installation requires a connection to an RDBMS server. You canuse an existing Cognos Command Center server repository or create a newrepository.

For systems that use an Oracle RDBMS

For typical installations, before you run the Cognos Command Center installationwizard, the system administrator creates a new empty schema in the Oracledatabase. Then when you install the Cognos Command Center and the wizardprompts you to configure the repository, select the Use existing database option.

If you select the Use existing database option without first creating a new emptyschema, the repository is created in an existing Oracle schema.

The Create New option is typically used for demonstration purposes. If you createa new database, the password you enter when prompted by the wizard, must beidentical to the system user's password. The reason is that the installer firstconnects as the system, using the system password, to create the schema.

For systems that use an SQL Server RDBMS

In the wizard, for the server name, if you use SQL Server Express®, follow thenaming convention for connecting to SQL Server Express. Use the name of yourworkstation followed by \SQLEXPRESS. For example: CORP-AUTOMATION\SQLEXPRESS.

You can use the default SQL Server Trusted Connection or you can configure aconnection specific to your SQL Server.

Procedure1. In the wizard, configure the repository.2. In the wizard, proceed with the installation to set the server connection

parameters.

Setting the server connection parametersIn the IBM Cognos Command Center installation wizard, set the following serverconnection parameters: the server port, the server protocol, and the servercertificate.

About this task

To configure the server connection, you set the following parameters:


Server portThe port number that is used by the Cognos Command Center client toserver communication.

Server protocolThe server to client communication in the Cognos Command Centerenvironment is secured with one of the following communicationprotocols: TCP, HTTP, or HTTPS. When you install the software, use theprotocol that best suits your network environment needs.v TCP efficiently encrypts end to end communication.v HTTP sends encrypted messages inside standard SOAP envelopes over a

clear text HTTP connection.v HTTPS is similar to HTTP, but the SOAP envelopes are sent over an

encrypted SSL connection.

With all communication protocols, the client authenticates to the server byusing a username and password that is validated against the CognosCommand Center set of users.

Server certificateYou can select the Use self signed certificate checkbox or you can chooseto use a trusted certificate. To use a trusted certificate, in the Certificatethumbprint field, enter the assigned thumbprint value. For moreinformation, see “Certificates for securing communication” on page 23.

Procedure1. In the wizard, enter or select values to configure the server connection

parameters.2. In the wizard, proceed with the installation to set the server configuration

parameters.

Setting the server configuration parametersThe message queue handles all communication between the IBM CognosCommand Center components. This includes the server, the agents and, ifapplicable, other high availability servers for failover. In the installation wizard, setthe server message queue connection parameters and the server service settings.

About this task

For more information about the message queue, see “System architecture” on page2.

In the wizard you set the following Server Message Queue connectionparameters:

User nameThe user name is used internally by Cognos Command Center to secureaccess to the Cognos Command Center queue component. This user nameis not related to any Windows account. It is for internal use and it is notnormally changed.

PasswordThe password is used internally by Cognos Command Center componentsto secure access to the Cognos Command Center queue component. Foroptimum security, select a unique password.

Chapter 4. Installing IBM Cognos Command Center 13

Queue PortThe port is used by the Cognos Command Center components forcommunicating with the Cognos Command Center queue. This port mustbe accessible from all hosts that run the Cognos Command Center agent.

In the wizard, you set the following Server service settings:

Create serviceSelect the check box to create a Windows Service named CognosCommand Center server. This service automatically starts the CognosCommand Center server when the host starts. Select this check box forboth the host and secondary servers if you are setting up a highavailability configuration.

Tip: If you use an Oracle database in a 64-bit Windows environment, donot select the checkbox. For more information see “Server installationprerequisites for an Oracle database in a 64-bit environment” on page 6.

Start serviceSelect the check box to start the Cognos Command Center server serviceafter installation is complete. Do not select the check box if the serviceneeds further configuration after the installation. If you are setting up ahigh availability configuration, do not select this check box. For the highavailability configuration you must perform additional post-installationtasks before you start the server. For more information, see “Setting up ahigh availability server” on page 31.

Use local system accountThe Cognos Command Center server service can run as a local systemaccount, or as a specific workstation user account.

User nameThe workstation user account name in the form DomainName\UserName.

PasswordThe workstation user account password.

Procedure1. In the wizard, enter or select values for the Server Message Queue connection

parameters and for the Server service settings.2. In the wizard, follow the prompts to proceed with the installation.

Installing the agent componentAgents must be installed on every workstation where IBM Cognos CommandCenter tasks, such as scripts, are run. In the installation wizard, you are promptedto enter or select values for the agent connection parameters and the agent servicesettings.

Before you begin

Ensure that you have completed the installation prerequisites for CognosCommand Center components. For more information, see Chapter 2, “IBM CognosCommand Center installation prerequisites,” on page 5.


About this task

The Cognos Command Center installation package includes a JRE (Java™ RuntimeEnvironment) for the Microsoft Windows operating system.

Important: For agent software to operate in the Cognos Command Center system,it must be installed and each agent must also be registered with the CognosCommand Center server repository. You can register the agents by using theCognos Command Center client. When you register the agent, you enter the sameconnection values that you entered in the agent installation wizard. For moreinformation, see “Registering agents with your server” on page 27.

In the installation wizard, you set the following agent connection parameters forthe agent:

User nameThe user name that is used internally by Cognos Command Center tosecure access to the agent user name. This user name is not related to anyWindows account. For security reasons, the agent requires any incomingrequest from the server to have a valid user name and password.

PasswordThe agent password. This password is not related to any Windowsaccount.

Port The port number that the agent listens on for commands from the CognosCommand Center server.

In the installation wizard, you set the following service settings for the agent:

Create serviceSelecting the check box, creates a Windows Service named CognosCommand Center agent. This service automatically starts the CognosCommand Center agent when the host starts.

Start serviceSelecting the check box, starts the Cognos Command Center agent serviceafter installation is complete. Do not select the check box if the serviceneeds further configuration after the installation.

Use local system accountThe service can either run as a local system account, or as a specificworkstation user account.

User nameThe name of the workstation user account in the form:DomainName\UserName.

PasswordThe workstation user account password.

Procedure1. On the Agent Configuration Parameters page of the wizard, enter or select

values for the connection parameters and the service settings.2. In the wizard, follow the prompts to proceed with the installation.


Installing the client componentThe client is the primary interface for users and administrators of the IBM CognosCommand Center environment. To install the client on a workstation, follow theinstallation wizard and set the client to server connection parameters.

Before you begin

The client is a Microsoft Windows application that provides full design,administration, and monitoring features. Users that set up and design the CognosCommand Center system and processes, must have the client installed on theirworkstations. The client and the server components do not need to be installed onthe same workstation.


Important:For Cognos Command Center to install and run, you must install Microsoft .NETFramework 4.0 before you install the Cognos Command Center client.

About this task

In the wizard, you set the following connection parameters:

Server host nameEnter the computer name where the Cognos Command Center server isinstalled.

Server portEnter the port number that you configured the Cognos Command Centerserver to use.

Server protocolSelect the protocol type that you configured the Cognos Command Centerserver to use.

Server uses self-signed certificateSelect the check box if you configured the Cognos Command Center serverto use a self-signed certificate. For more information on certificates, see“Certificates for securing communication” on page 23.

Procedure1. In the wizard, on the Client to Server Connection Parameters page, enter or

select values for the client to server connection parameters.2. In the wizard, follow the prompts to proceed with the installation.

Installing the web application componentThe web application provides a secure web browser user interface to run andmonitor IBM Cognos Command Center processes. To install the web application ona workstation, follow the installation wizard and set the configuration parameters.


Before you begin

The Cognos Command Center web application runs on IIS (Microsoft InternetInformation Services).


To use the web-based user interface, you must install the Cognos Command Centerweb application on the workstation that is hosting the website.

About this task

If you install the Cognos Command Center server and the web applicationcomponents on the same workstation, then you only set an http port number forthe web application. The remaining configuration parameters are taken from theserver configuration.

If you install the web application component on a separate workstation, you mustset the server hostname port, the chosen communication protocol, and a set ofcredentials to be used by the web application when making requests to the server.

The following list describes the web application configuration parameters that youset in the wizard:

Web Server portThe specific workstation port that is assigned to the Cognos CommandCenter web application.

Server user nameThe Cognos Command Center user account that is assigned to the webapplication. You should use the default value of Cognos Command Centerweb, but you do have the option of changing the default value for the useraccount.

When both the server and web application components are installed, thisuser is automatically created in the repository. If only the CognosCommand Center web application is installed, this user must be manuallycreated in the repository by using the Cognos Command Center client.

Server passwordThe password for the server user name.

Server host nameYou are only required to enter a value for this parameter when you installthe web component without installing the server component on the sameworkstation. In this case, the web component needs to know the host namewhere the server runs.

Server portYou are only required to enter a value for this parameter when you installthe web component without installing the server component on the sameworkstation. Enter the port number that you configured the CognosCommand Center server to use.

Server protocolYou are only required to enter a value for this parameter when you install


the web component without installing the server component on the sameworkstation. Select the protocol type that you configured the CognosCommand Center server to use.

Server uses self-signed certificateYou are only required to enter a value for this parameter when you installthe web component without installing the server component on the sameworkstation. Select this check box if you configured the Cognos CommandCenter server to use a self-signed certificate. For more information oncertificates, see “Certificates for securing communication” on page 23.

Procedure1. In the wizard, on the Web Application Configuration Parameters page, set the

configuration parameters.2. In the wizard, follow the prompts to proceed with the installation.

Completing the web client installationTo complete the installation of the IBM Cognos Command Center web client, IIS(Microsoft Internet Information Services) must be configured.

Use the procedure that is appropriate for your operating system.

Configuring IIS for Microsoft Windows 2003 and 2003 R2operating systemsTo use the IBM Cognos Command Center web client with Microsoft Windows2003, and Microsoft Windows 2003 R2 operating systems, IIS (Internet InformationServices) version 6.0 must be configured.

Before you begin

You must install IIS. For more information, see “Preparations for installing the webapplication component” on page 7.

Use the following information to configure IIS.

Procedure1. Open Internet Information Services (IIS) Manager.2. Delete the IBM Cognos Command Center application if it exists.3. On the Web Service Extension node, allow APS.NET v4.0.30319.4. On the Web Sites node, select the IBM Cognos Command Center website

and view its properties.5. On the Home Directory tab, click Configuration.6. Edit any existing wildcard application map, or insert a new one as follows:

v On a 32-bit operating system set the executable to C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll.

v On a 64-bit system set the executable to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll.

7. Clear the Verify that file exists check box.8. On the ASP.NET tab, set the ASP.NET Version to 4.0.30319.9. If a restart warning displays, click Yes.

10. On the Directory Security tab, click Server Certificate.


11. To start the Web Server Certificate wizard, click Next, then click Assign anexisting certificate.

12. On the Available Certificates page, click the ccserver.staranalytics.comself-signed certificate.

13. On the SSL Port page, set the SSL port to 8180.14. Finish the wizard.

Configuring IIS for Windows 2008 and 2008 R2 operatingsystemsTo use the IBM Cognos Command Center web client with Microsoft Windows2008, and Microsoft Windows 2008 R2 operating systems, IIS (Internet InformationServices) must be configured.

Before you begin

You must install IIS version 7.0 on workstations with Microsoft Windows 2008operating systems or IIS version 7.5 on workstations with Microsoft Windows 2008R2 operating systems. For more information, see “Preparations for installing theweb application component” on page 7.

The configuration procedures are the same for both IIS versions. Use the followinginformation to configure IIS.

Procedure1. Open a command prompt and register .NET 4.0 ASP.NET in IIS by running one

of the following commands:v On a 32-bit system, run the command %windir%\Microsoft.NET\Framework\

v4.0.30319\aspnet_regiis.exe -i

v On a 64-bit system, run the command %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

2. Open Internet Information (IIS) Manager.3. Delete the Cognos Command Center application if it exists.4. Click theCognos Command Center website, right click > Edit Bindings.5. In the Site Bindings window, select Edit.6. In the Edit Site Bindings window, select the CCServer_wixCert_0 self-signed

certificate.7. In IIS Manager, select the Application Pools node, then in the Application

Pools pane, select Cognos Command Center, and click the Advanced Settingsaction.

8. In the Advanced Settings window, set the .NET Framework Version to v4.0.

Installing the command line client componentThe IBM Cognos Command Center command line client component is a MicrosoftWindows application. You can use the client to query, start, pause, and stop IBMCognos Command Center processes, to test agent connectivity, and to perform fulland partial exports of the repository. To install the command line component,follow the installation wizard.


Before you begin


For the product to install and run, you must install Microsoft .NET Framework 4.0before you install the Cognos Command Center command line client.

Procedure1. In the wizard, follow the prompts to install the command line client

component.2. To configure the command line component in the wizard, follow the procedure

that is used to configure the Cognos Command Center web client component.For more information, see “Configuring IIS for Microsoft Windows 2003 and2003 R2 operating systems” on page 18 or “Configuring IIS for Windows 2008and 2008 R2 operating systems” on page 19.

Finishing the installationIn the wizard, after you install and configure all the IBM Cognos Command Centercomponents that you selected to install, you complete the installation.

Before you begin

Now is your last opportunity to go back and change configuration values beforeyou initiate the installation process. If you want to change any of the configurationvalues, click Back.

Procedure

In the installation wizard, on the Ready to install page, click Finish. You exit theinstallation wizard. The installation process takes a few minutes.


Chapter 5. Starting IBM Cognos Command Center

After you install the IBM Cognos Command Center software components, youstart them to ensure that the software is properly installed.

Starting the server from the server installation directoryIf you do not install the IBM Cognos Command Center server as a Windowsservice, then you start the server from the server installation directory.

Procedure

From the server installation directory, start the SccServer.exe file. The serverconsole window opens and runs the executable file.

Starting the agent componentAfter you install the IBM Cognos Command Center software components, youstart them to ensure that the software is properly installed.

About this task

If you choose to run the Cognos Command Center agent as a Windows service andyou select the installation option to create an agent service, then the agent startsautomatically upon successful completion of the installation process.

To verify that the agent is running, look in the Windows Task Manager for theSccAgent.exe process.

If you did not install the software as a Windows Service, use the followingprocedure to start the agent.

Procedure

From the agent installation directory, start the SccAgent.bat file. The agent consolewindow opens and runs the file.

Starting the client componentAfter you install the IBM Cognos Command Center software components, youstart them to ensure that the software is properly installed.

About this task

The installation process creates an Cognos Command Center program group and ashortcut on the Microsoft Windows desktop.

When Cognos Command Center is first installed, a user that is called Default iscreated without a password. By providing the host name and port number of theCognos Command Center server, you connect to a running Cognos CommandCenter server and the Cognos Command Center client is displayed.

You can change the network protocol by clicking Advanced.


If you experience an error, for information, see “Troubleshooting,” on page 35.

Procedure

1. On your desktop, click the IBM Cognos Command Center icon. Theclient login window opens.

2. Respond to the prompts and remember to use the host name and port numberof the Cognos Command Center server.

Starting the web clientAfter you install the IBM Cognos Command Center software components, youstart them to ensure that the software is properly installed.

Before you begin

The web interface requires that browsers have JavaScript enabled.

Smartphone browsers must also be set to allow JavaScript popups, and must be setto allow slow running scripts.

Procedure

Open a web browser and enter the following URL into the address bar:https://CCC-HOST:8180/Home The Cognos Command Center login page opens. Ifyou experience an error, see “Troubleshooting,” on page 35.


Chapter 6. Post installation configuration

After you install IBM Cognos Command Center components, there are security,communication, registration, and other tasks to complete, especially on newsystems.

Certificates for securing communicationBoth the IBM Cognos Command Center client and the server use certificates toestablish secure communications.

After you install the server component, you must install a certificate on the server.If you use the HTTPS protocol, the client-to-server port must also be configured touse the certificate.

Different types of certificates include self-signed certificates and certificates that areissued by a trusted party, such as VeriSgin. In a production system, the highestlevel of security is required and the certificate should be issued by a trusted party.Self-signed certificates can be forged and should not be used in productionsystems.

For development environments, trusted certificates are not normally available, so aself-signed certificate is used. The Cognos Command Center software comes with aself-signed certificate that can be used in development environments.

The three options for Cognos Command Center client-to-server communication alluse certificates.

TCP Communication is encrypted on the wire.

A certificate must be issued by a trusted issuer or installed inLocalMachine-Personal store.

HTTP Messages are encrypted and sent as clear text.

A certificate must be issued by a trusted issuer, or installed inLocalMachine-Personal store.

HTTPSMessages are encrypted and sent over an encrypted connection.

A certificate must be issued by a trusted issuer and the name of thecertificate must match the server hostname, or the client is configured toaccept a self-signed certificate.


Table 1. Required certificate configuration for possible installation scenarios

Protocol

Server hostconfiguration:self-signed andissued certificate

Client hostconfiguration:self-signedcertificate

Client hostconfiguration: issuedcertificate

TCP Install certificate inLocalMachine -Personal store.

Install certificate inLocalMachine -Personal store.

No configuration isrequired.

HTTP Install certificate inLocalMachine -Personal store.

Install certificate inLocalMachine -Personal store.


HTTPS Install certificate inLocalMachine -Personal store.Configure SSL on theclient-to-server portto use the certificate.



The client host configuration is handled by the installer for the Cognos CommandCenter application if the Server uses self-signed certificate option is selectedduring installation.

The server host configuration must be done manually. Use the procedures for youroperating system. For more information, see “Installing the server host certificateon Windows 2003 or 2008 operating systems,” or “Installing the server hostcertificate on Windows Vista or Windows 7 operating systems” on page 25.

Installing the server host certificate on Windows 2003 or 2008operating systems

A default server host security certificate is installed during the IBM CognosCommand Center server installation. This certificate must be manually replacedand configured.

Procedure1. Run the Microsoft Management Console mmc.exe file.2. In the Console window, click File > Add/Remove Snap-in.

a. In the Add/Remove Snap-in window, if there is no Certificates entry, clickAdd.

Figure 4. Secure client to server communication


b. In the Add Standalone Snap-in window, click the Certificates item, andclick Add.

c. In the Certificates Snap-in window, click Computer Account.d. In the Select Computer window, click Local computer, and click Finish.

Close the Snap-in window.3. In the Console window, select the Certificates folder from the file path Console

Root\Certificates (Local Computer)\Personal\Certificates, and then clickAction > All Tasks > Import. The Certificate Import wizard opens.

4. Click Next, and on the File to Import page, click Browse.5. In the Server installation directory, from the Files of type list, select the

Personal Information Exchange option, and for the File name select theStarCCServer.pfx file. Then, click Open.

6. Continue in the wizard.7. On the Certificate Store page, click Place all certificates in the following store.

Click Next , and then Finish. You see a confirmation and then you see thecertificate appear in the Issued To and Issued By pane.

8. Close the Console window.

Installing the server host certificate on Windows Vista orWindows 7 operating systems

A default server host security certificate is installed during the IBM CognosCommand Center server installation. This certificate must be manually replacedand configured.

Procedure1. Run the Microsoft Management Console, mmc.exe file.2. To add the Certificates snap-in for the computer account, in the Console

window, click File > Add/Remove Snap-in.3. Select the target folder for the certificate import (Personal), and then click

Action > All Tasks > Import. The Certificate Import wizard opens.4. Follow the wizard to install the certificate.

Tip: For the self-signed certificate that comes with IBM Cognos CommandCenter the password is password.

5. After the certificate is imported, double-click on the certificate and inspect theCertificate Information page to verify that it says You have a private key thatcorresponds to this certificate.

Configuring the client-to-server port when HTTPS is thechosen protocol

When you define your configuration to use the HTTPS (Hypertext TransferProtocol Secure) communications protocol, you must configure your SSL (SecureSockets Layer) on a port, to use a certificate.

About this task

The thumbprint of the certificate consists of 20 hexadecimal characters with nospace. The thumbprint for the self-signed certificate that comes with CognosCommand Center is 8d3b42ffb30eeb15c76efb51cdd99b56425bb69f.

Chapter 6. Post installation configuration 25

Procedure1. On Windows Vista, 2003, or 2008 operating systems, use the netsh command as

follows:netsh http add sslcert ipport=0.0.0.0:portcerthash=ThumbprintOfSSLCertificateappid={16C7288A-AC50-4d86-B806-703FCA3932A9}

2. In the Certificate Information window, on the Details tab, verify thethumbprint.

Securing the installation with a passwordAccess to the Cognos Command Center environment is controlled by user levelsecurity. Create a password for the default administration account that is createdduring the installation of IBM Cognos Command Center.

About this task

Each user can be assigned one or more roles that define access to environments,file resources, and processes. For more information, see the IBM Cognos CommandCenter Administration Guide.

The first time that Cognos Command Center is installed, a default administrationaccount is created. The user name of the default account is DEFAULT. This accountdoes not have a password. To secure the installation, create a password for theadministration account.

Important: If you installed the Cognos Command Center web component, theinstallation includes a user and role name that matches the information that isprovided during the installation. The default name is WEB. Do not change thedefault name without consulting IBM technical support. Changing the propertiesfor the web user and roles, can affect your ability to access the web user interface.

Procedure1. Log on to the Cognos Command Center server with the Cognos Command

Center client.2. Navigate to the Security > Users folder.3. Edit the default user properties by double-clicking Default.4. Enter a password for your default administration user account, and confirm it.5. Save your changes.

Configuring an external authentication serverBy default, IBM Cognos Command Center uses its own user authentication systemwith database encrypted passwords. In addition, you can optionally use anexternal LDAP (Lightweight Directory Access Protocol) authentication server foruser authentication.

About this task

Each user can be defined with an authentication property of either Local, orExternal. When a user is defined with the Local property, the password is managedby Cognos Command Center authentication. When a user is defined with theExternal property, the password is handled by the external source, and it is nolonger managed by Cognos Command Center.


To configure Cognos Command Center to work with an external authenticationserver, set the following properties:

Enable Local AuthenticationThe default value is true. A true value specifies that users can beauthenticated by the Cognos Command Center Server. Set the value tofalse to use only an external authentication server.

Enable External AuthenticationSet the value to true or false. A true value specifies that users can beauthenticated with an external authentication server.

External LDAP HostLDAP host URL, for example: Idap://example.com:389

External Base DNLDAP Base DN, for example: ou=People,dc=example,dc=com

External Bind DNLDAP Bind DN, for example: cn=Joe,ou=People,dc=example,dc=com

External Bind PasswordLDAP Bind Password.

External Search AttributeLDAP Search Attribute, for example: sAMAccountName

For more information, see the IBM Cognos Command Center Administration Guide.

Follow this procedure to configure IBM Cognos Command Center to work with anexternal authentication server:

Procedure1. Use an Cognos Command Center administration account to log in to the

Cognos Command Center client.2. Click Tools > System Configuration.3. In the Manage system configuration window, click the Authentication

subsystem.4. Enter the appropriate Property values.5. To save the values, click OK.

Registering agents with your serverYou must register all installed IBM Cognos Command Center agents with yourIBM Cognos Command Center server.

Procedure1. Use an Cognos Command Center administration account to log in to the client.2. Navigate to the Setup and Design\Agents folder.

3. On the toolbar, click the New icon .4. In the New Agent window, enter the host name of the server where the agent

is installed and enter the port number that you entered during the agentinstallation.

5. Enter the agent user name and password that was defined during the agentinstallation.


Tip: This user name and password is not an Cognos Command Center username and password; it is specific to the Cognos Command Centeragent-to-server communication.

6. Click Test the Agent to verify that the agent is installed, properly configured,and running.

7. Repeat these steps for each agent that is installed in your system.

Installing plug-insAn IBM Cognos Command Center plug-in is a set of task types and computingresources types that targets a specific technology or target system.

About this task

During the first installation of Cognos Command Center, a default set of plug-insis installed in INSTALLDIR > Plugins and loaded into the repository.

When you upgrade an existing Cognos Command Center installation, no plug-insare loaded. You can update plug-ins after the upgrade, or when existing plug-insare updated, or when new plug-ins become available. Plug-ins are distributed ascompressed files and are installed by using the Cognos Command Center client.

For information on configuring computing resources for each plug-in and on theuse of plug-in tasks in processes, see the IBM Cognos Command CenterAdministration Guide.


Cognos Command Center client.2. Click Tools > Manage plugin tasks.3. In the Manage plugin tasks window, click Load file.

Tip: The plugin packages are in INSTALLDIR > Plugins on the workstationwhere the Cognos Command Center server is installed.

4. After you install plug-ins, click Close.

Setting up email notificationIBM Cognos Command Center can send email notifications to users duringspecified automation process states. To enable this feature, configure an SMTPserver.

About this task

To configure an SMTP server, set the following properties:

HostnameDefines the Hostname address of the SMTP Server.

Port Defines the Port number of the SMTP Host. Usually this value is set to 25.

Enable SSLDefines whether SSL is enabled.

UsernameUsername who has access rights that allow submitting mail to the server.


PasswordPassword.

From AddressDefines the From address that appears on any alerts that are sent from theCognos Command Center server.

Helo DomainCertain environments require a Helo Domain.

SCC Web URLThe Cognos Command Center web address.

Procedure1. Using an Cognos Command Center administration account, log in to the

Cognos Command Center client.2. Click Tools > System Configuration.3. In the Manage system configuration window, select the Email subsystem.4. Enter the appropriate property values.5. Stop and restart the IBM Cognos Command Center server. For more

information, see the IBM Cognos Command Center Administration Guide.

What to do next

Each Cognos Command Center process has email notification settings. To ensurethat the email settings are properly configured for each process, define and run atest process. For more information, see the IBM Cognos Command CenterAdministration Guide.

Setting up the event listener moduleAn external program can send a message to the IBM Cognos Command Centerserver to start a specific process if the optional event listener module is configured.

About this task

To configure the event listener module, set the following properties:

Enable APIEnables the event listener interface.

UsernameA valid Cognos Command Center user name.

HostnameDefines the hostname address of the Cognos Command Center server.

Port Defines the listening port number of the Cognos Command Center host.Usually this value is set to 9002.

Request Queue LengthDefines the maximum number of concurrent requests for a given process.

For changes to the settings to take effect, you must stop and restart the IBMCognos Command Center server. For more information, see the IBM CognosCommand Center Administration Guide.


Procedure1. Use a Cognos Command Center administration account to log in to the Cognos

Command Center client.2. Click Tools > System Configuration.3. In the Manage system configuration window, select the Event Listener

subsystem.4. Enter the appropriate property values.5. Stop and restart the Cognos Command Center server.

Starting processes with an external applicationAfter the event listener module is enabled, external applications can trigger thestart of IBM Cognos Command Center processes by issuing an HTML GET requestto the configured port.

About this task

The URL Get request is constructed by using the Ecosystem, Environment, andProcess name.

Optionally, you can assign a user name to the request, and you can submitparameter values as part of the run request.

For example, a URL Get request that includes a user name and parameter valueslooks as follows:

http://hostname:9002/run/EcosystemName/EnvironmentName/ProcessName?User=Name&Variable1=Value&Variable2=Value

Procedure1. Construct a URL by using the Ecosystem, Environment, and Process name as

follows: http://hostname:9002/run/EcosystemName/EnvironmentName/ProcessName.

2. Optionally, assign a user name to the request by appending ?User=Name to theURL.

3. Optionally, submit parameter values as part of the run request by appendingVariableName=Value for each variable that should be set.

Editing the event logBy default, IBM Cognos Command Center logs process state change and task statechange events. You can change the default types of events that are logged. You canalso change the format of the log entries.

About this task

Cognos Command Center outputs process state change and task state changeevents to the file INSTALLDIR\Server\events.txt.

The log entries are formatted with the following information:1. YYYY-MM-DD. The date of the event.2. hh:mm:ss. The time of the event using a 24 hour clock.3. {Task|Process}.{State}. The type of event, and the new state.


4. Reserved for future use.5. Ecosystem Name.6. Environment Name.7. Process Name.8. Reserved for future use.9. User name. The name of the user that starts the process.

10. Reserved for future use.11. ID. The process ID.

Tip: To customize the delimiter, in the Cognos Command Center client, Managesystem configuration window, select the General subsystem and enter values forthe properties.

To change the type of process state change, or task state change events that arelogged, edit the INSTALLDIR\Server\log4net.config file.

Procedure1. Open the INSTALLDIR\Server\log4net.config file.2. To edit the file, follow the instructions in the file.3. After the file is edited, stop and restart the Cognos Command Center server.

For more information, see the IBM Cognos Command Center Administration Guide.

Setting up a high availability serverThe optional high availability feature provides a more fail tolerant automationsystem. The key to this capability is an automatic failover to a secondary IBMCognos Command Center server.

Both the host and secondary Cognos Command Center servers must be installed asWindows Services.

To set up a high availability architecture, complete the following tasks:v Install Cognos Command Center server on the secondary host.v Configure failover settings on the primary server host.v Modify the message queue configuration files to enable a master and

subordinate configuration. Follow the procedure for systems that use an SQLServer RDBMS, or the procedure for systems that use an Oracle RDBMS.

v Restart the primary server queue and the server Windows services.v Restart secondary server queue and the server Windows services.

Installing the server component on the secondary hostSetting up a high availability architecture for IBM Cognos Command Center,requires multiple tasks that include installing the server on a secondary host.

Procedure1. Install the Cognos Command Center server component on the secondary host.

For more information, see “Installing the server” on page 11.2. Stop the secondary host Cognos Command Center server.3. Stop the secondary host Cognos Command Center message queue.


Configuring failover settings on the primary server hostSetting up a high availability architecture for IBM Cognos Command Center,requires multiple tasks that include configuring failover settings on the primaryserver host.

About this task

Set the following properties for the queue subsystem:

External URIUse this format failover:(ssl://PRIMARY:61617,ssl://SECONDARY:6161 7,and replace PRIMARY and SECONDARY with the server names.

QueueDefault: SFCC.AgentEvent

User nameThe Cognos Command Center server message queue user name. The username is configured during server installation and must be the same valuefor both primary and secondary servers.

PasswordThe Cognos Command Center server message queue password. Thepassword is configured during server installation and must be the samevalue for both the primary and the secondary servers.

Procedure1. Using an Cognos Command Center administration account, log in to the

Cognos Command Center client.2. Click Tools > System Configuration.3. In the Manage system configuration window, select the Queue subsystem.4. Enter the appropriate property values.

What to do next

Next, you modify the message queue configuration files to enable a master andsubordinate configuration.

If your system uses an SQL Server RDBMS, see “Configuring the message queuefor high availability on systems that use an SQL Server RDBMS.”

If your system uses an Oracle RDBMS, see “Configuring the message queue forhigh availability on systems that use an Oracle RDBMS” on page 33.

Configuring the message queue for high availability onsystems that use an SQL Server RDBMS

To set up a high availability architecture for IBM Cognos Command Center, youperform multiple tasks that include modifying the message queue to enable amaster and subordinate configuration.

Procedure1. On the host and secondary servers, edit the following file: <INSTALLDIR>\

Common\apache-activemq-5.8.0\conf\activemq.xml.highavail.2. In the SQL Server repository, create a database named SccQueue.3. Edit the persistenceAdapter element as follows:


<persistenceAdapter><jdbcPersistenceAdapter createTablesOnStartup="true"

dataSource="#mssql-ds"/></persistenceAdapter>

4. Enable the bean element with id="mssql-ds" by removing the surrounding XMLcomments and by editing the settings to point to the SQL Server repository, asfollows:<bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource"destroy-method="close">

<property name="driverClassName"value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>

<property name="url"value="jdbc:sqlserver://host:1433;databaseName=SccQueue;integratedSecurity=true"/>

<property name="username" value="SccQueue"/><property name="password" value="password"/>

5. In the same directory, save the file as activemq.xml, overwriting the stand aloneconfiguration.

6. Restart the primary server, Cognos Command Center queue, and CognosCommand Center server Windows services. For more information, see the IBMCognos Command Center Administration Guide.

7. Restart the secondary server, Cognos Command Center queue, and CognosCommand Center server Windows services.

Configuring the message queue for high availability onsystems that use an Oracle RDBMS

To set up a high availability architecture for IBM Cognos Command Center, youperform multiple tasks that include modifying the message queue to enable amaster and subordinate configuration.

Procedure1. Stop the Cognos Command Center queue and Cognos Command Center server

Windows services on both the primary server and the secondary server.2. Create a SccQueue user in the Oracle repository. The user must be granted

CONNECT, RESOURCE, and CREATE VIEW privileges.3. Go to the Oracle website (www.oracle.com) and search for JDBC driver file

ojdbc6.jar. Download the file and save it to the directory <INSTALLDIR>\Common\apache-activemq-5.8.0\lib.

4. Edit the <persistenceAdapter> element as follows:<persistenceAdapter>

<jdbcPersistenceAdapter createTablesOnStartup="true"dataSource="#oracle-ds"/></persistenceAdapter>

5. Enable the bean element with id=”oracle-ds” by removing the XMLsurrounding XML comments and editing the settings to point to the Oraclerepository as follows:<bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"destroy-method="close">

<property name="driverClassName"value="oracle.jdbc.driver.OracleDriver"/>

<property name="url"value="jdbc:oracle:thin:@localhost:1521:SccQueue"/>

<property name="username" value="SccQueue"/><property name="password" value="password"/><property name="poolPreparedStatements" value="true"/>

</bean>


6. In the same directory, save the file as activemq.xml, overwriting the stand aloneconfiguration.

7. Restart the primary server, Cognos Command Center queue, and CognosCommand Center server Windows services. For more information, see the IBMCognos Command Center Administration Guide.

8. Restart the secondary server, Cognos Command Center queue, and CognosCommand Center server Windows services.


Appendix. Troubleshooting

Log files can provide information that can aid you in troubleshooting problemswith IBM Cognos Command Center.

High-level diagnostic information is available through the Cognos CommandCenter client by viewing the system log. You can view more detailed errormessages and diagnostic information in various other log files.

Viewing the system logHigh-level diagnostic information is available through the IBM Cognos CommandCenter client by viewing the system log. Server events are logged and provideinformation that aids in troubleshooting.


Cognos Command Center client.2. Click Tools > System Log.3. In the System log window, enter Retrieval condition values.

Log file for the server componentWhen the IBM Cognos Command Center server attempts to start, messages arewritten to a log file. If an attempt to start the server fails, view the log.txt file thatis in the INSTALLDIR>\Server\log.txt directory.

The log file can provide valuable diagnostic information to determine the cause ofserver errors. The contents of the log file are useful if you contact IBM technicalsupport.

The most common problem in starting the server is related to the service accountaccess rights that are used to start the server process:v The service account must have access to the RDBMS repository. The startup

process terminates if no connection is established.v The service account must be able to read the digital certificate that is defined for

the server process.

Troubleshooting failures of the high availability serverIf the IBM Cognos Command Center high availability server fails to start, inspectthe log files on both the primary and secondary servers.

Check the following log files for error information about the servers. The log.txtcontains the latest set of messages.

<INSTALLDIR>\Server\log.txt.

<INSTALLDIR>\Common\apache-activemq-5.8.0\data\activemq.log.

<INSTALLDIR>\Common\apache-activemq-5.8.0\data\wrapper.log.



Notices

This information was developed for products and services offered worldwide.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service. This document maydescribe products, services, or features that are not included in the Program orlicense entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

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

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

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

IBM Software GroupAttention: Licensing3755 Riverside DrOttawa, ON K1V 1B7Canada

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

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


Trademarks

IBM, the IBM logo and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “ Copyright andtrademark information ” at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:v Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.v Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.v Java and all Java-based trademarks and logos are trademarks or registered

trademarks of Oracle and/or its affiliates.

Notices 39

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml


Index

Aaccessibility status vagent

installing 14preinstall tasks 5starting 21

authentication system 26

Cclient

installing 16starting 21

communication 2

Eevent logs 30

Ffailover system 3finding information

system requirements 5

Hhigh availability

overview 3troubleshooting 35

IIBM Cognos Command Center client

Installing 20installation

agent 14client 16server 11

communication protocols 12configuration parameters 13configuring the server repository 12server message queue connection parameters 13service settings 13setting connection parameters 12

web application 17web client

configuring 18configuring IIS for Windows 2003 and 2003 R2 18configuring IIS for Windows 2008 and 2008 R2 19

wizard 11Installing

IBM Cognos Command Center client 20

Llink to information center vlink to PDF documentation web page v

Ppost installation configuration 23

editing event logs 30plug-ins 28registering agents with server 27security

certificates issued by a trusted party 23changing the default password 26communication protocols 23configuring external authentication system 26HTTPS configuration 25self-signed certificates 23server host certificate Windows 2003 or 2008 24server host certificate Windows Vista or 7 25

setting up a high availability server 31setting up email notification 28setting up the event listener module 29starting processes with an external application 30

preinstall tasksagent 5dedicated local Windows account 5installing Microsoft .NET Framework 5Oracle RDBMS 6server 6web application 7

product overview 1

Rregistering agents with server 27

Ssecurity

certificates issued by a trusted party 23changing the default password 26communication protocols 23enabling external authentication 26enabling local authentication 26HTTPS configuration 25self-signed certificates 23server host certificate Windows 2003 or 2008 24server host certificate Windows Vista or 7 25

serverinstallation 11preinstall tasks 6starting from the server installation directory 21troubleshooting 35

server host certificate for Windows 2003 or 2008installing 24

server host certificate for Windows Vista or 7installing 25

setting up a high availability server 31configuring failover settings on the primary server

host 32configuring the message queue on systems that use an

Oracle RDBMS 33configuring the message queue on systems that use an SQL

Server RDBMS 32installing the server on the secondary host 31


setting up email notification 28setting up the event listener module 29starting

client 21starting processes with an external application 30system architecture 2

components 1

Ttroubleshooting 35

high availability server 35server 35viewing system log 35

Uupgrading 9

Vviewing system log 35

Wweb application

installing 17preinstall tasks 7

web clientconfiguring 18configuring IIS for Windows 2003 and 2003 R2 18configuring IIS for Windows 2008 and 2008 R2 19starting 22

wizardinstallation 11


Date post:	25-Sep-2020
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

IBM Cognos Command Center Version 10.2.0: Installation...

Documents