Quick path to installing Tivoli Common Reporting v

Transcription

1 Quick path to installing Tivoli Common Reporting v Bhanu Prathap

2 TCR Component TCR is the reporting component in Jazz for Service Management (JazzSM). TCR does NOT have it s own separate installer product ID. Instead you get TCR as part of JazzSM. Official documentation: %2Ftcr_t_install.html JazzSM is a middleware platform Tivoli products ship to get the base services used by the products. JazzSM includes the following optional: WebSphere Application Server DB2 Tivoli Common Reporting DASH (new UI console) Registry Services Administration Services Administration Services UI Enterprise Single Signon (ESS) To ship reporting, or any other services in JazzSM, products simply include the JazzSM part numbers in the products bundle Loosely coupled All customers, regardless of the entitled product, get the same middleware services from the common installer

3 Update: There is a new TCR installation quick start guide TCR : %2Fcom.ibm.psc.doc_ %2Ftcr_qsg.html 3

4 Required for TCR install Jazz for Service Management Part Numbers Jazz for Service Management V for AIX Multilingual CIN3DML Jazz for Service Management V for Linux Multilingual CIN3EML Jazz for Service Management V for Linux on System z Multilingual CIN3FML Jazz for Service Management V for Windows Multilingual CIN3GML IBM Tivoli Common Reporting V for AIX Multilingual IBM Tivoli Common Reporting V for Linux Multilingual IBM Tivoli Common Reporting V for Linux on System z Multilingual IBM Tivoli Common Reporting V for Windows Multilingual IBM Tivoli Common Reporting V Cognos Framework Manager Windows Multilingual CIN3HML CIN3IML CIN3JML CIN3KML CIN3LML IBM WebSphere Application Server V for Jazz for Service Management for AIX Multilingual CIES5ML IBM WebSphere Application Server V for Jazz for Service Management for Linux CIES6ML IBM WebSphere Application Server V for Jazz for Service Management for Linux on System z CIES7ML Optional, use IBM WebSphere Application Server V for Jazz for Service Management for Windows your own WAS CIFS5ML if you have one, otherwise you need this IBM DB2 10.1, Enterprise Server Edition - Restricted Use - Quick Start and Activation CI71NML IBM DB2 Enterprise Server Edition for 64-bit AIX CI6W9ML Optional, use IBM DB2 Enterprise Server Edition for Linux on AMD64 and Intel EM64T systems (x64) CI6W6ML your own DB2 IBM DB2 Enterprise Server Edition for Linux on System z CI6W7ML if you have one, IBM DB2 Enterprise Server Edition for Windows on AMD64 and Intel EM64T systems (x64) CI6WEML otherwise you need this

5 2 ways to install Full Install Easy & minimal inputs However system must be clean. No existing installs, no DB2 client, no left over DB2 groups, etc. Recommended Custom install More steps, only install the minimum needed Can distribute DB2 off to another system Additionally, there is an optional Mobile installer (last chart)

6 Custom Install

7 Custom Install, continued Install only the components TCR requires: IBM WebSphere Application Server 8.5 JazzSM extensions for WAS 8.5 IBM Dashboard Application Services Hub (DASH) *Note: The optional TCR Admin service tasks require several other services to be installed (Registry, Admin Services, Admin Services UI). This option is not covered in this document DB2 decision time Before installing the TCR component, you need to make a decision on a DB2 to use. This DB2 houses the TCR reporting artifacts. Either you have your own DB2 or you need to install the DB2 that comes with JazzSM at this time. This DB2 can be anywhere on the network.

8 Custom Install Download and unzip the Jazz for Service Management part numbers all to the same directory (minus DB2, more info on that in a later chart) TIP: For this custom install, the unzipped images aren t required to be in the same location. But if they are, the file prompts will default to the correct locations, avoiding you have to point the install to them. Start the launchpad64.exe.sh Select Custom from launchpad Click Next button

9 Custom Install, continued Click on Next button (This panel is useful to upgrade JazzSM version from to ) By default all JazzSM source locations will be populated, please ensure filled in paths are correct and click on Next button

10 Custom Install, continued Please select below operations only which are required for Reporting Services and click on Next button Reporting Services IBM Wehsphere Application Server Please accept the license panel and click on Next button Specify the Installation locations and click on Next button

11 Custom Install, continued Please provide Websphere application Server user details and db2 login details and click on Next button Click on Run button to start the installation process Prerequisite scanner will be run as part of the installation process Once installation is successful please click on exit

12 Custom Install, continued After the installation completes, TCR should be up and running at (update with your host and ports):

13 Full Install

14 Full Install Install must be clean. That means no DB2, DB2 client, left over DB2 users or groups, prior installs of JazzSM, Download and unzip the Jazz for Service Management part numbers all to the same directory Start the launchpad.exe.sh Select Full from launchpad Select the option to install TCR JazzSM service, including WAS, DB2, and TCR are installed

15 Optional, Mobile installation

16 Optional Mobile install One command is required to add Mobile server-side support to the TCR installation 1.Update the response file by accepting the two agreements in it: <JazzSM_Home>\reporting\mobile\response.ats 2.cd <JazzSM_Home>\reporting\mobile\ 3../installMobile.bat.sh <Mobile_image> <Jazz_User> <Jazz_Pwd> Where: <Mobile_image> is on the TCR media: <TCR_Media>\CognosMobile <Jazz_User> and <Jazz_Pwd> are the WAS user and password used by TCR

17 Install TCR having Content store in Remote machine

18 Create the reporting database in DB2 with the generated SQL: Run a TCR command to generate required DB2 SQL <image_media>/tcrinstaller/contentstoredatabase/tcr_generate_content_store_db_definition.bat.sh <new database to create> <existing db2 user to give permissions> Move generated SQL file to machine where DB2 is installed Issue the SQL from a DB2 Command line editor db2 tvf <SQL file prior command created> TIP: If the user ID running the command is the same user passed into the script, the command will give a message saying you can t grant permissions to yourself. This is okay since this user owns the database. Run TCR installation Back in the launchpad, Tools => Tivoli Common Reporting => Installation Browse to the image location => Run

19 Troubleshooting / Known Issues

20 Possible reasons why Reporting Services installation fails Operating system user does not have privilege to create Reporting Services content store database through JazzSM Launchpad custom install. JazzSM Launchpad fail to invoke Tivoli Common Reporting(TCR) installer (this happens some times only on Windows platforms) When previous instance of Reporting Services or TCR is not uninstalled successfully (TCR registry entries still appears under DE) Previous instance of TCR(2.x/1.x) is already up and running Follow below manual steps to install reporting services successfully Please follow the steps in slide-18 and create Reporting Services database If old instance of TCR already exists on the system, please make sure to stop old instance of TCR If the previous TCR uninstallation was not clean, then please follow below link to clear all failed entries ually.html Go to Tivoli Common Reporting zip file extracted location I,e C:\Downloads\TCRInstaller Luanch Install.sh/.bat in GUI mode and follow the panels to install Reporting Services successfully. To install Reporting Services in silent mode, please follow instructions in C:\Downloads\TCRInstallerTCR_sample_response.txt file