Home

User Guide - Wikis on enterpriselab.ch

1. e On the list find the Miscellaneous category and disable the Access data sources across domains option e Click OK to apply the changes Charts in reports do not appear Symptoms When rendering a report charts do not appear and an error appears in the log files The log file is in the directory TCR_install_dir profiles TIPProfile logs in the form YYYY MM DD hh mm ss log where YYYY is the year MM is the month DD is the day hh is the hour mm is the minute and ss is the second The file reports the following error May 19 2010 2 09 43 PM org eclipse birt chart exception ChartException logThis WARNING Exception org eclipse birt chart exception ChartException CREATE_EXTENSION FAIL at org eclipse birt chart util PluginSettings getPluginXmlObject PluginSettings java 987 at org eclipse birt chart util PluginSettings getDisplayServer PluginSettings java 545 at org eclipse birt chart device swing SwingRendererImp init SwingRendererImp1 java 130 at org eclipse birt chart device swing SwingRendererImp lt init gt SwingRendererImp1 java 122 at org eclipse birt chart device image JavaxImagelOWriter lt init gt javaxImagelOWriter java 123 at org eclipse birt chart device image PngRendererImpl lt init gt PngRendererImp1 java 18 The error appears on UNIX operating system Causes BIRT requires a graphical user interface API to render charts This error appears only on UNIX like systems where a graphical user int
2. lt Uri AffinityCookie JSESSIONID_i Name jsw gt lt UriGroup gt lt Route ServerCluster serverl Cluster UriGroup Serverl_Cluster_URIs VirtualHostGroup admin_host gt lt RequestMetrics armEnabled false newBehavior false rmEnabled false traceLevel HOPS gt lt filters enable false type URI gt AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid AffinityURLIdentifier jsessionid lt filterValues enable false value servlet snoop gt lt filterValues enable false value webapp examples HitCount gt lt filters gt lt filters enable false type SOURCE_IP gt lt filterValues enable false value 255 255 255 255 gt lt filterValues enable false value 254 254 254 254 gt lt filters gt lt RequestMetrics gt lt Config gt e Restart IBM HTTP Server from the Service list window 6 Configure SSL communications between the WebSphere Application plugin and Tivoli Integrated Portal a b ad Log in to the WebSphere Application Server administrative console Select Security gt SSL certificates and key management gt Key stores and certificates Select NodeDefaultKeyStore Go to Personal C
3. IAGLOBAL_WASUserID tipadmin TAGLOBAL_WASPassword Save the file 2 Evoke the silent uninstallation from a command line interface by MOIS navigating to TCR_install_dir _uninst TIPInstal121 and running the uninstall exe i silent f 7CR_install_dir _uninst TIPInstal121 TCR_sample_response_uninstal txt command e and navigating to TCR_install_dir _uninst TIPInstal121 and running the uninstall i silent f TCR_install_dir _uninst TIPInstal121 TCR_sample_response_uninstall txt command Important Provide the full path to the response file in your command Results You have now uninstalled Tivoli Common Reporting without any_user interaction You can verify the uninstallation procedure by going through the Uninstalling manually 42 User Guide In most cases you should follow one of the other choices for uninstalling Tivoli Common Reporting However if the uninstallation program is not present or if an aborted installation did not create a complete and functional uninstallation program you can manually uninstall the product Follow this procedure only on the machine where Tivoli Common Reporting Server was installed About this task The manual uninstallation should only be performed when none of the standard uninstallation methods are possible Procedure 1 Stop the Tivoli Common Reporting Server by navigating to the following directory in the command line interface MIO cd TCR component_dir bin and running the s
4. Tivoli Common Reporting User Guide ah Tivoli Common Reporting User Guide Note Before using this information and the product it supports read the information in Notices Second edition This edition applies to Tivoli Common Reporting and to all subsequent releases and modifications until otherwise indicated in new editions Copyright IBM Corporation 2007 2011 US Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents Chapter 1 Overview Technical overview Web resources Getting started with reports Logging in to the reporting iterace Single sign on SSO Chapter 2 Installing Hardware and software requirements Installation scenarios and installation modes Tivoli Common Reporting installation paths Preparing to install Preinstallation Step 1 Read the release notes Preinstallation Step 2 Verify the environment Preinstallation Step 3 Preparing installation media Validation of additional disk space required fot the installation process Installing using the installation wizard Installing on one computer F Installing in a distributed ehvironment Installing the Cognos based Tivoli Commot Reporting engine r Installing Tivoli Common Reporting u user interface Installing by using the console mode Installing using the silent mode Response file for silent installation Installing into an
5. cognos_reporting_engine first step of the distributed installation scenario INSTALLATION SCENARIO cognos_reporting_engine ui_for_cognos second step of the distributed installation scenario INSTALLATION_SCENARIO ui_for_cognos single_computer_installation integrate_existing_cognos INSTALLATION _SCENARIO integrate_existing_cognos URL to Cognos The URL should point to the selected instance of Cognos which has been installed from a source other than the IBM Tivoli Common Reporting TCR_VERSIONG installation program COGNOS_URL Tivoli Integrated Portal configuration related WebSphere information Enter a WebSphere Application Server administrator user name and password If the password is not provided the installer will fail WAS_USER_NAME tipadmin WAS_PASSWORD ti padmin Should it be upgrade PERFORM _UPGRADE false Following variables are for upgrade only Path to the previous instance of TCR or migration package UPGRADE_SOURCE opt IBM tivoli tip or on Windows systems note double backslashes UPGRADE_SOURCE C IBM tivoli tip Define type of the upgrade source existing instance or a migration package Valid values instance package UPGRADE_MODE instance These are only for upgrade from existing instance of TCR PREVIOUS_INSTANCE_USER_ID tipadmin PREVIOUS_INSTANCE_US
6. export the data to preserve it Procedure 1 Export the complete Cognos Content Store from Web user interface a Select Launch gt Administration b Go to the Configuration tab and select Content Administration c Create new package export by clicking d Follow the wizard to export the archive The exported package is visible in the Administration window All choices that you made with the export wizard are saved in this export package so you can use it later to run an export with the same settings The export package is located in TCR_component_dir cognos deployment 2 Archive the directory where report images are stored What to do next Enable Tivoli Common Reporting to use external Cognos Enabling Tivoli Common Reporting to use external Cognos After you have exported your data you can modify your Tivoli Common Reporting instance to use Cognos installed on a different computer Procedure 1 Ensure that the Tivoli Common Reporting server is started If it is stopped start it from the command line interface a Navigate to the installation subdirectory EIS TCR _component_dir bin and run the startTCRserver bat command e TCR_component_dir bin and run the startTCRserver sh command and exit the console by typing quit Uninstall IBM Cognos 8 from WebSphere Application Server a Navigate to the installation subdirectory D 7 P_install_dir profiles TIPProfile bin and run the wsadmin bat command e T
7. Server gt lt PrimaryServers gt lt Server Name server1 gt lt Server Name server2 gt lt PrimaryServers gt lt ServerCluster gt lt UriGroup Name serverl_Cluster_URIs gt lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm console gt lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm console gt lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm console ISCProxy gt lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm console ISCProxy lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm help gt lt Uri AffinityCookie JSESSIONID isc AffinityURLIdentifier jsessionid Name ibm help gt v Chapter 4 Configuring 79 80 User Guide lt Uri AffinityCookie JSESSIONID_i Name mum js gt lt Uri AffinityCookie JSESSIONID_i Name mum js gt lt Uri AffinityCookie JSESSIONID_i Name j_security_check gt lt Uri AffinityCookie JSESSIONID_ i Name ibm_security_logout gt lt Uri AffinityCookie JSESSIONID_i Name ibm console ISCProxy gt lt Uri AffinityCookie JSESSIONID_i Name ibm console ISCProxy gt lt Uri AffinityCookie JSESSIONID_i Name ibm gt lt Uri AffinityCookie JSESSIONID_i Name jsp gt lt Uri AffinityCookie JSESSIONID_i Name jsv gt
8. command to see your data source settings and the command to modify them if necessary Tip BIRT reports are separate from Cognos predefined reports to which you can make simple changes You can also create or modify report designs with the use of an open source BIRT report designer which is not shipped with Tivoli Common Reporting but is available for downloading 2 If you have to create a new report package a Configure the database connection b Create a data model in Framework Manager Tip For more instructions see the Framework Manager User Guide in Cognos information center c Import the metadata from your data sources When you have done imported the metadata you can start modeling in Framework Manager You can define the relations between objects such as tables views and queries you can select the layers to define which objects you want to make visible you can define what you want to publish and finally you can create and Chapter 1 Overview 5 6 User Guide publish_a package containing the model and reports For more information see Framework Manger User Guide If you have configured the connection between Framework Manager and Tivoli Common Reporting the published package is automatically pushed to Tivoli Common Reporting and you can see it in its respective folder inside Tivoli Common Reporting d Log in to the reporting interface and select Launch gt Query Studio to test your model a
9. database configuring 82 database configuration 82 DB2 database configuring 82 DB2 database configuration 82 distributed environment installation 19 E existing Cognos infrastructure installation 33 F FIPS support 86 Framework Manager connection configuration 81 Copyright IBM Corp 2007 2011 IBM Tivoli Common Reporting description 1 installation console mode 20 distributed environment 19 existing Cognos infrastructure 33 preparing 14 environment 16 installation media 16 reading release notes 14 required disk space 16 response file 23 scenarios 12 silent mode 22 single computer 17 troubleshooting 108 verifying 35 wizard 17 installing overview 9 installing using installation wizard 17 L LDAP configuring 62 Cognos based Tivoli Common Reporting engine 63 Tivoli Common Reporting Server 62 LDAP configuration 62 Cognos based Tivoli Common Reporting engine 63 Tivoli Common Reporting Server 62 M manual uninstallation 42 MS SQL database configuring 83 MS SQL database configuration 83 O on line resources 5 Oracle database configuring 84 Oracle database configuration 84 P preparing to installation 14 R reporting getting started 5 reporting interface logging in 6 Tivoli Integrated Portal logging in 6 response file installation 23 S security configuring 88 89 security configuration 88 89 silent installation using response file 23 silent mode installation 22 silent mode uninst
10. information The report name is enclosed in double quotation marks because it contains spaces setdatasource is the keyword specifying which parameters are to be changed in the JDBC datasource All the parameters are in the NAME VALUE format Specify your own parameters What to do next You can now verify if the JDBC datasource was changed correctly using the list command The example below lists the properties of the ITM Top Resources by Memory Utilization report tremd sh user tipadmin password tipadmin list report content package name Tivoli Products Report information is displayed including the properties that you changed trcmd run 138 User Guide The run command flag for the tremd command runs a report and saves the result as an output version You can use this command for BIRT and Cognos reports Syntax tremd run report cognosSearchPath format format locale locale parameters p1 p2 p3 walidateParams true help Note 1 Authentication with user userID and password password is required 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider 3 To run BIRT reports use Cognos search path as a report name Arguments report cognosSearchPath The unique search path of the report you want to run Note that the search path for every Cognos report can be found in Cognos UI For more information see C
11. instance Connecting to an MS SQL database Connect the Tivoli Common Reporting to an MS SQL database Before you begin a Ex Perform this task with the support of a database administrator Chapter 4 Configuring 83 Make sure you have deployed an MS SQL database client on the computer where Cognos based Tivoli Common Reporting engine is installed About this task The configuration comprises of connecting the database to a client and activating optional cross database functionality Procedure 1 Connect the MS SQL client to the database server by running the MS SOL Management Studio Express configuring the local net service name configuration and restarting your system Important Note the name of the connection you have created as it is used in one of the following steps 2 Create new database connection for Cognos by following the steps a From the Common Reporting portlet go to Launch drop down list and choose the Administration b On the Configuration tab add a new data source by clicking c Follow the New Data Source wizard as required noting the following steps e On the second panel choose an Microsoft SQL Server database as Type e On the third panel specify the name of the connection you have noted before as the Server name and in the Signon section specify a new User ID and Password Results You have now connected your Tivoli Common Reporting to an MS SQL database instance Connecting to a
12. users belonging to a group named Everyone tremd bat user tipadmin password XXX dataSource add ITM dbType DB2 connectionName TDW dbname ITM dblogin db2inst1 dbpassword XXX groups Everyone users VMMProvider tipadmin This example tests the database connection of a data source named ITM tremd bat user tipadmin password XXX dataSource test ITM dbLogin otherdbuser dbPassword XXXX trcmd delete The delete command flag for the tremd command deletes an arbitrary object in Content Store based on its search path You can use this command for both Cognos and BIRT objects Syntax Use this syntax to delete an object from Content Store tremd delete searchPath cognosSearchPath recursive force help Note 1 Authentication with user userID and password password is required in all cases 2 If you have configured more than one user repository specify the namespace value By default the namespace parameter points to VMMProvider Arguments force Forces deletion of an object in case of problems by specifying whether Content Manager can consider the setPolicy permissions of a user when deciding if the user can delete a selected object If used the selected object will be deleted if Chapter 7 Reference 131 the current user has either write or setPolicy permission for the selected object the parent of the selected object and every descendant of the selected object If not used the selected obj
13. 1 e If you are upgrading from version 1 1 1 extract TCRInstaller COI PackageSteps TCRCore FILES tcr TCRPlugins zip to the 7CR_install_dir of your existing Tivoli Common Reporting instance prior to version 2 1 1 Important On non Windows platforms run the following command to add run permissions for all upgrade scripts chmod x existing_TCR_install_dir profiles TIPProfile upgrade bin sh c Run the following command to finish creating the package e For Tivoli Common Reporting versions 2 1 1 3 and 1 2 single computer installation existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade bat existing_TCR_install_dir username username password password productId TCR Pun existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade sh existing_TCR_install_dir username username password password productId TCR e For Tivoli Common Reporting version 1 1 1 existing _TCR_install_dir upgrade bin tcrUpgrade bat existing TCR_install_dir upgrade Jjava_home_dir operation export username username password password location existing_TCR_install_dir customPropertiesFile existing_TCR_install_dir upgrade plugins tcrCustomProperties propert existing TCR_install_dir upgrade bin tcrUpgrade sh existing TCR_install_dir upgrade Jjava_home_dir operation export username username password password location existing_TCR_install_dir customPropertiesFile existing_TCR_install_dir upgrade plugins tcrCust
14. 2_2_2 ReportEngine plugins org eclipse birt report data oda jdbc_2 2 2 r22x_v200712 Replace tcr_install_dir with the name of the Tivoli Common Reporting installation directory 2 For a DB2 data source copy the DB2 JDBC drivers as well as the license jar file to the same location You can copy db2jcc jar and db2jcc_licence_cu jar file on the DB2 server system from location C Program Files IBM SQLLIB java or download it from 3 Use the trcmd modify on page 136 command to specify the required JDBC information including the URL driver user ID and password Known limitations 98 User Guide We have used our best efforts in order to ensure proper support of BIRT reports and achieve as highest compatibility with Tivoli Common Reporting v 1 2 and v 1 3 as possible However due to the unavoidable changes of technology some features may no longer be operational IBMCognos version 8 4 1 Fix Pack 3 works properly for both single computer installation and distributed installation however you may encounter problems with specific Web container APIs At the present moment the following limitations are known to exist 1 BIRT reports cannot be imported using the Web user_interface You have to use the import command For detailed instructions see tremd import on page 133 2 Tivoli Common Reporting 2 1 1 can work on either WebSphere Application Server or on Apache Tomcat As a result you should not rely on server
15. 77 install_dir profiles TIPProfile bin and running the following command wsadmin f TCR_install_dir TIP21Components TCRComponent conf modifyClassloader py gateway PARENT_LAST You are asked to provide a username and a password Stop the server from a command line interface a Navigate to the installation subdirectory E 7CR_component_dir bin and run the stopTCRserver bat command e and B 7CR_component_dir bin and run the stopTCRserver sh command Edit the stop and start server scripts e Edit the startTCRserver script by commenting out the following lines EQS Using characters start B D COGNOS _DIR bin tcr_cogconfig bat s and Using the character COGNOS_DIR bin tcr_cogconfig sh s e Edit the stopTCRserver script by commenting out the following lines E Using characters call COGNOS DIR bin tcr_cogconfig bat stop and EE Using the character COGNOS_DIR bin tcr_cogconfig sh stop Open the IBM Cognos Configuration as described in step 2 and edit it a In the Explorer navigation on the left go to Environment section Group Properties panel opens on the right b Go to Gateway Settings and locate Dispatcher URIs for gateway Click on the value field and update it with the URI to your Tivoli Common Reporting server that is installed on a different computer as stated in prerequisites http lt server_hostname gt 9300 p2pd servlet dispatch c Save the new configuration Star
16. DashoAl0 at sun reflect NativeMethodAccessorImp1 invokeO Native Method at sun reflect NativeMethodAccessorImp invoke NativeMethodAccessorImp1 java 64 at sun reflect DelegatingMethodAccessorImp invoke DelegatingMethodAccessorImp1 java 43 at java lang reflect Method invoke Method java 615 at com zerog 1ax LAX launch DashoA10 at com zerog ax LAX main DashoA10 Invocation of this Java Application has caused an InvocationTargetException This application will n YH HS WH WH YH SY WH In this example the missing library is the following 1ibXft so 2 cannot open shared object file No such file or directory Install the rpm related to this library After upgrading from Tivoli Common Reporting 1 3 the reporting engine does not work 110 User Guide Symptoms After upgrading from version 1 3 to version 2 1 the reporting engine does not start Causes The problem appears most probably because you have manually modified the TCR13_instal_dir products tcr Cognos c8 webapps p2pd WEB INF 1ib directory for example by adding a DB2 driver for an external content store Resolving the problem Modify the TCR21_install_dir cognos webapps p2pd WEB INF 1ib directory in the same way as you have modified TCR13_instal_dir products tcr Cognos c8 webapps p2pd WEB INF 1ib Installation using the instal1l sh script fails Symptoms When running the instal1 sh script using the relative path the installation fails a
17. The furnishing of this document does not grant you any license to these patents You can send license inquiries in writing to IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504 1785 U S A For license inquiries regarding double byte character set DBCS information contact the IBM Intellectual Property Department in your country or send inquiries in writing to Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd 3 2 12 Roppongi Minato ku Tokyo 106 8711 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of express or implied warranties in certain transactions therefore this statement may not apply to you This information could include technical inaccuracies or typographical errors Changes are periodically made to the information herein these changes will be incorporated in new editions of the publication IBM may make improvements and or changes in the product s and or the program s described in this publication at any time without notice Any references in this informat
18. Tivoli Common Reporting user interface No additional configuration is necessary for the reporting engine About this task Tivoli Common Reporting can work on one Tivoli Integrated Portal instance at a time You can choose to configure it to operate on a higher version of Tivoli Integrated Portal than the one you were using before Procedure 1 Run the reconfigure bat script specifying the path to the new Tivoli Integrated Portal as the argument MEU TCR _component_dir integration reconfiguration reconfigure batTIP_destination_dir a TCR_component_dir integration reconfiguration reconfigure sh TIP_destination_dir 2 Log in to the newly upgraded Tivoli Integrated Portal console by entering http hostname port ibm console in your web browser and verify if Tivoli Common Reporting is working properly Note Pay attention to the port number that you enter to ensure that you are logging in to the upgraded Tivoli Integrated Portal 3 Depending on the result of your verification e Save the changes by running the following script WUE TCR component_dir integration reconfiguration commi tReconfiguration bat TCR_component_dir integration reconfiguration commi tReconfiguration sh Important If you decide to save the changes the Tivoli Common Reporting installed on the previous version of Tivoli Integrated Portal will not work It will work on the upgraded Tivoli Integrated Portal only e Roll back the changes by runn
19. _component_dir bin and running the stopTCRserver bat command BRO and TCR_component_dir bin and running the stopTCRserver sh In the command line interface navigate to the TCR_install_dir bin directory Run the following command ws_ant bat propertyfile C temp tcrwas props file C IBM tivoli tipv2 profileTemplates default actions updatePorts ant C temp tcrwas props is the path to the properties file created in Step 1 Change the port numbers in IBMCognos Configuration a Open IBMCognos Configuration by running TCR_component_dir cognos bin tcr_cogconfig bat for Windows operating systems and TCR_install_dir cognos bin tcr_cogconfig sh for Linux and UNIX b In the Environment section change the port numbers to the desired values as in Step 2 Chapter 2 Installing 39 c Save your settings and close IBMCognos Configuration 7 Start the Tivoli Common Reporting server by navigating to the following directory in the command line interface MRIS TCR _component_dir bin and running the startTCRserver bat command and TCR_component_dir bin and running the startTCRserver sh Enabling Cognos Application Firewall After installing Tivoli Common Reporting you can optionally enable the Cognos Application Firewall About this task After installing Tivoli Common Reporting the Cognos Application Firewall is by default disabled You can enable and configure the firewall To find out more about the firewall and how to
20. a a a a AAAA A a aE COPYRIGHT TOP OCO Source Materials 5724 T69 Copyright IBM Corp 2011 The source code for this program is not published or otherwise divested of its trade secrets irrespective of what has been deposited with the U S Copyright Office eat a A a EH a Ha a a a a a a a ae AE COPYRIGHT END ae HE A HE EH A a a Ea aa a a a a a a InstallAnywhere variables to configure the install of Tivoli Common Reporting TCR_VERSION components Usage install sh bat f lt full path to this file gt i lt installation mode gt available modes silent console gui On Windows install exe will return immediately To avoid this you should use the batch file install bat which wraps it sign is used here to comment out the lines that follow it PAARA AAAA PAAPAA AAAA AAAA EEE a AEAEE EEEE ib a a a a a a AAAA AAAA AAAA AAAA AAAA AAAA AEAEE AEAEE ER EEEE EEE This response file example is profiled for installing the UI for Cognos component of the distributed installation scenario for further details on installation scenarios see TCR TCR_VERSION documentation Variables that are necessary in this scenario have been left uncommented and with example values i a a a a a A EEE parse Set Silent License Acceptance To accept the license agreement change the value to true example LICENSE_ACCEPTED true If the LICENSE_A
21. acsi bin si_inst sh r f Note The r f command might fail if a DE operation ends abnormally In such case go to DE_install_dir asci logs and delete all files whose filenames begin with lock 3 M Remove the registered services by following the steps a Open Control Panel gt Administrative Tools gt Services and find the following services e Tivoli Integrated Portal TIPProfile Port_XXX service e Any IBM Cognos Content Database service b Right click on the service and choose Properties c Copy the property name enclosed in parentheses for example IBMWAS70Service TIPProfile Port_16310 and IBM Cognos Content Database and IBM Cognos 8 d Open the command line interface and run the following command sc delete IBMWAS70Service TIPProfile Port_16310 and sc delete IBM Cognos Content Database and sc delete IBM Cognos 8 Chapter 2 Installing 43 4 In the file system manually remove the program installation directory Do not remove the Tivoli Integrated Portal directory if you were reusing an existing version of Tivoli Integrated Portal for your Tivoli Common Reporting installation MIS 7 IP _components_dir and TIP_install_dir tipv2 e and TIP_components_dir and TIP_install_dir tipv2 5 MEMES Remove the shortcuts from menu Start Right click the Tivoli Common Reporting in the menu and select to delete it 6 MEMES Recommended Restart your computer Results You have now finished performing m
22. algorithms option and click Apply This option makes IBMJSSE2 and IBMJCEFIPS the active providers Configure the application server to use FIPS algorithms for Java clients that must access enterprise beans a Open the install_dir profiles TIPProfile properties ssl client props file in a text editor b Change the com ibm security useFIPS property value from false to true Configure the application server to use FIPS algorithms for SOAP based administrative clients that must access enterprise beans a Open the install_dir profiles TIPProfile properties soap client props file in a text editor b Add this line com ibm ssl contextProvider IBMJSSEFIPS Configure java security to enable IBMJCEFIPS a Open the install_dir java jre lib security java security file in a text editor b Insert the IBMJCEFIPS provider com ibm crypto fips provider IBMJCEFIPS before the IBMJCE provider and also renumber the other providers in the provider list The IBMJCEFIPS provider must be in the java security file provider list See the example at the end of this topic Enable your browser to use Transport Layer Security TLS 1 0 a Microsoft Internet Explorer Open the Internet Explorer and click Tools gt Internet Options On the Advanced tab select the Use TLS 1 0 option b Firefox TLS 1 0 is enabled by default Export Lightweight Third Party Authentication keys so applications that use these LTPA keys can be reconfigured a In th
23. and click Next 4 When prompted for the Cognos based Tivoli Common Reporting engine URL provide the address that you noted when you finished installing the reporting engine and click Next Example http example com 9300 p2pd servlet dispatch 5 Provide the port number for IBMCognos content database 6 Read the Pre Installation Summary information and choose to Install Results You have installed the reporting engine on one computer and installed the user interface on another Now you can start Tivoli Common Reporting Important During the installation procedure you have created an administrative user If you are planning to use LDAP you can now configure it You can also create new users and user groups and grant them permissions to access various reporting resources and functions Before you do make sure you increase the security settings for the Common Reporting user interface described in the Configuring section of the information center Installing by using the console mode 20 User Guide Use the console installation method to install IBM Tivoli Common Reporting from a command line About this task The console installation has the same logical flow as the graphical user interface installation wizard ETIS To perform this task you must belong to the Administrators group or be an Administrator Procedure 1 Copy the installation program file to a temporary directory on the target system The installati
24. are predicates used to filter a set of objects CAMID specifies the Cognos namespace The at sign specifies a property name The asterisk is a wildcard character Example The search path below can be used to find a report named Order Product List Report content package name GO Sales and Retailers folder name Documentation Reports report name Order Product List Report The following search path finds all reports whose name contains the Product List expression content package name GO Sales and Retailers folder name Documentation Reports report contains name Product List If you replace the report name with a wildcard character you can use the search path to select all objects in the Documentation Reports folder content package name GO Sales and Retailers folder name Documentation Reports Checking the search path of a report If you do not know the search path of a particular report you can check it using Cognos Connection About this task To check the search path of a report perform the following steps Procedure 1 Log in to Connection 2 In the Actions column click the Set properties icon for a particular row 3 Under the first tab General click View the search path ID and URL near the Location property 4 The search path of the report will be displayed in the first text field Chapter 5 Common Reporting 105 106 User Guide Chapter 6 Troubles
25. by running lt MA Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration E User interface TCR_component_dir cognos bin tcr_cogconfig sh reporting engine TCR_install_dir cognos bin tcr_cogconfig sh b Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to False c Save your configuration and restart the Tivoli Common Reporting server Upgrading the reporting engine using a package Perform the first part of the upgrade process with the use of a previously generated package that contains all the data from your existing Tivoli Common Reporting instance Before you begin Enable anonymous access to the reporting engine 1 Open the IBM Cognos Configuration by running MXIT Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration MO Es IP_install_dir products tcr Cognos c8 bin tcr_cogconfig sh 2 Select Security gt Authentication gt Cognos and edit the Allow anonymous access field changing it to True 3 Save your configuration and restart the reporting engine Procedure 1 Create the package with Tivoli Common Reporting data a From the Tivoli Common Reporting 2 1 1 installation media extract the TCRInstaller COI PackageSteps TCRCore FILES tcr TCRPlugins zip to the TCR_install_dir of your existing Tivoli Common Reporting instance prior to version 2 1 1 Important
26. choose the Administration from the Launch drop down list 3 Go to Configuration tab and open the Content Administration section ai 4 Create new package import by clicking This opens a New Import wizard 5 Follow the wizard to import a new package Tip For more information see the IBM Cognos 8 Reporting Getting Started Installation Guide 8 4 1 Exporting Cognos report packages Export your report package to be able to use it for example on a different Tivoli Common Reporting instance Procedure 1 Log in to the Tivoli Common Reporting user interface and go to Common Reporting 2 In the Work with reports window on the right choose the Administration from the Launch expandable list 3 Go to the Configuration tab and open the Content Administration section 4 Export a new package by clicking 5 Follow the wizard to export a package Copying report images to the Tivoli Common Reporting server Cognos report packages do not contain images so after you have imported a Cognos based report package you need to copy the static images to a folder on your computer for the images to display Before you begin Import a report package Chapter 5 Common Reporting 101 About this task Cognos report packages do not contain images this is why you need to copy the images manually The image location depends on the installation scenario that you chose Procedure 1 For single computer installation Copy the i
27. click serverName Change Log Detail Levels The default server name is server1 4 Click either the Configuration or Runtime tab e Click the Configuration tab if you want to make persistent changes to the log and trace levels These changes will take effect after the next server restart Copyright IBM Corp 2007 2011 107 e Click the Runtime tab if you want to make changes to the log and trace levels for the current session These changes take effect immediately and do not require a server restart If you use the Runtime tab you can select the Save runtime changes to configuration as well check box to make the changes persistent as well as applying to the current session 5 Expand the list of installed packages and click com ibm tivoli gt com ibm tivoli reporting 6 Click Message and Trace Levels gt finest and confirm your choice 7 If you are making persistent configuration changes click Save when prompted to save the changes to the master configuration 8 Stop and restart the Tivoli Common Reporting server Results Log and trace files are located in the profiles TIPProfile logs serverName subdirectory of the Tivoli Common Reporting installation directory Standard informational log messages are written to the SystemOut log file detailed trace messages are written to the trace log file Troubleshooting the installation Identify and resolve problems that might occur when you are installing upgrading or uninst
28. computer appears Resolving the problem Run Cognos in compatibility mode Chapter 6 Troubleshooting and support 111 1 Unpack the Tivoli Common Reporting installation image 2 Navigate to the unpacked_image TCR21Installer COI Dep loymentSteps FCI_INST_COG FILES win32 and locate the issetup exe file 3 Right click the file select Properties go to the Compatibility tab and select to Run this program in compatibility mode for Windows XP 4 Install Tivoli Common Reporting Cognos Business Intelligence does not install on Linux Symptoms Cognos does not install and the following error appears Error while loading shared libraries 1ibXm so 3 cannot open shared object file No such file or di Resolving the problem Cognos is linked to the openmotif library 2 2 X that contains a symbolic link to libXm so 3 When libXm so 3 library is upgraded the openmotif library is upgraded as well Newer versions of openmotif do not have the symbolic link to libXm so 3 but rather to libXm so 4 while Cognos requires libXm so 3 Create a new symbolic link In s 1ibXm so 4 libXm so 3 and return to the installer UDA SQL 0031 Unable to access database QE DEF 0285 Logon failure Symptoms Testing a database signon returns an error saying that the password is invalid despite the fact that the credentials used are correct Resolving the problem After you have installed Tivoli Common Reporting and the remote database add the follo
29. connect directly with Cognos enable anonymous access from VMMProvider 1 Open the IBM Cognos configuration by running EYY Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration ET Os IP_install_dir tipv2 products tcr Cognos c8 bin tcr_cogconfig sh 2 Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to True 3 Save your configuration and restart the Tivoli Common Reporting server CAUTION Enabling anonymous access makes Cognos open for anonymous connections without any authentication It is recommended that you upgrade in maintenance mode and secure access to Cognos with a firewall Note If LDAP was configured for version 1 3 or 2 1 after the upgrade Tivoli Common Reporting 2 1 1 command line is only able to authenticate users from LDAP About this task When upgrading from Tivoli Common Reporting version 2 1 Tivoli Integrated Portal is not upgraded You can upgrade Tivoli Integrated Portal to version 2 2 manually Procedure 1 Upgrade Tivoli Common Reporting engine 2 Upgrade Tivoli Common Reporting user interface 3 Confirm your choices to finish the upgrade Results You have upgraded to Tivoli Common Reporting version 2 1 1 and the following data was imported e Database drivers e Report snapshots were generated to PDF format and saved as saved reports e Cognos Content Store was migrate
30. detail for example date format Examples e This example creates a snapshot of the DBAvail report specifying several parameter values trcmd run report content package name package zip report name DBAvail parameters Note On UNIX like operating systems it is essential that you add double quotation marks for the parameters even thought there is no space in them trcmd version The version command flag for the tremd command shows current version and build information for Tivoli Common Reporting Syntax tremd version Arguments This command flag has no arguments Chapter 7 Reference 139 140 User Guide Notices This information was developed for products and services offered in the U S A IBM may not offer the products services or features discussed in this document in other countries Consult your local IBM representative for information on the products and services currently available in your area Any reference to an IBM product program or service is not intended to state or imply that only that IBM product program or service may be used Any functionally equivalent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility to evaluate and verify the operation of any non IBM product program or service IBM may have patents or pending patent applications covering subject matter described in this document
31. details on installation scenarios see TCR TCR_VERSION documentation Variables that are necessary in this scenario have been left uncommented and with example values i a a a a a a a EEE EEE Set Silent License Acceptance To accept the license agreement change the value to true example LICENSE_ACCEPTED true If the LICENSE_ACCEPTED has a value other than true the installation will exit ff ie By removing the sign before the LICENSE ACCEPTED false string and changing false to true you mark that you agree to the Tivoli Common Reporting TCR_VERSION license agreement LICENSE_ACCEPTED false Choose the preferred installation language For default leave commented Available values are cs de en es fr it ja ko pl pt pt_BR ru tr zh zh_CN zh_TW INSTALLATION_LANGUAGE en ae Install into existing WebSphere Application Server Specify decision to install Tivoli Common Reporting into an existing WebSphere Application Server Note that If this property is set to true then the following TCR_INSTALLATION DIRECTORY property must be correctly set to the existing WebSphere Application Server location aka WAS HOME INSTALL_INTO_EXISTING_WAS false Choose Installation Folder Silent installation provide a fully qualified path example TCR_INSTALLATION D
32. existing Cognos infrastructure Installing Tivoli Common Reporting into an existing Tivoli Integrated Portal instance Installing Framework Manager Verifying the installation Post installation tasks Migrating to a distributed environment Exporting data from Tivoli Common Reporting Modifying the existing single computer installation RT Ae do ok ee Importing data console Enabling Cognos Application Firewall Uninstalling Uninstalling using the u installa n wiza d Uninstalling using the console mode Uninstalling using the silent mode Uninstalling manually Verifying the uninstallation Chapter 3 Upgrading to Tivoli Common Reporting version 2 1 1 Preparing to upgrade Upgrading on a single computer Upgrading distributed environment Copyright IBM Corp 2007 2011 Nao kr 11 13 14 14 14 16 16 17 17 18 19 19 20 21 23 199 34 34 s39 30 35 35 36 39 Changing ports for the Tivoli Common Reporting So ae certo 40 40 40 41 41 42 44 45 45 46 48 Upgrading Tivoli Common Reporting engine Upgrading Tivoli Common Reporting user interface Upgrading with the use Sof a package Upgrading using a paraga in single computer scenario Upgrading with the use of a package i in distributed scenario Upgrading the reporting engine using a package Upgrading user interface using a pac
33. flag use the help flag For example to see information about the list command flag use this command tremd list help The command reference topics in this section use special characters to define command syntax Identifies an optional argument Arguments not enclosed in brackets are required Indicates that you can specify multiple values for an argument Indicates mutually exclusive arguments Specify either the argument to the left of the separator or the argument to the right of the separator but not both Encloses a set of mutually exclusive arguments separated by Copyright IBM Corp 2007 2011 125 Tip The documentation in this section shows the command usage for a Windows system On a Linux or UNIX system use tremd sh Command line authentication You must supply a valid user ID and password to use the Tivoli Common Reporting command line interface For some operations your user ID must have sufficient permissions to access the specified objects for example you might need access to a particular report or eport set For more information about authorization see Constraining access to r BIRT reports You can specify the user ID and password in the following way On the command line use the user userID password password arguments as in the following example trcmd list reports user tipAdmin password adminPassword You can also use the optional namespace paramete
34. instructions to install several instances of Cognos based Tivoli Common Reporting engines which are the Tivoli Common Reporting Cognos Application Tier Server components shown on the exemplary diagram as System B and System C Note To learn more about Application Tier Components installation go to IBM Cognos 8 Installation and Configuration Guide page 33 Then on a separate computer install the Tivoli Common Reporting user interface if you have not done so far on the diagram represented as System A Specify the URIs of all the installed engines in the Web user interface by following the steps a Open IBM Cognos Configuration by MMS Going to Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration i and EE running the following command TCR_component_dir Cognos bin tcr_cogconfig sh This opens a separate configuration tool b Go to Environment section and in the Environment Group Properties panel on the right look for Dispatcher URIs for gateway entry in the Gateway Settings section c Click on the value field and edit it by clicking the A The Value window opens d In the Value window click Add to add new URIs and click OK to save your changes e In the IBM Cognos Configuration window save your configuration changes by going to File gt Save What to do next Now you can configure a user repository and a central database Configuring distributed installation for l
35. location TCR_component_dir _uninst TIPInstal121 open and edit the TCR_sample response uninstall txt file with the user ID and password Tip You will not be asked for password if WebSphere Application Server has been stopped If you forgot your password you can kill WebSphere Application Server process first and then run the uninstallation Your password will not be required i EE A AEA a A A A a a A a a a a ea a HE COPYRIGHT TOP OCO Source Materials 5724 169 Copyright IBM Corp 2011 The source code for this program is not published or otherwise divested of its trade secrets irrespective of what has been deposited with the U S Copyright Office Hat EH a Ea a AARAA a a aa aa COPYRIGHT END Hedda dee dtd dite ete He Eee ee ee ee a a a a a ee ee a ee a a Chapter 2 Installing 41 InstallAnywhere variables to configure the installation of Tivoli Common Reporting for Asset and Performance Management Usage uninstall sh exe f lt full path to this file gt i lt installation mode gt available modes silent console gui On Windows uninstall exe will return immediately To avoid this you should wrap the uninstall exe command in a batch file sign is used here to comment out the lines that follow it i a a a A EE EEE Enter a WebSphere Application Server password If the password is not provided the uninstaller will fail
36. not be asked for the password The uninstallation process is now started and will take a moment to remove the Tivoli Common Reporting from your file system 4 MMSE Recommended Restart your computer What to do next Check the uninstallation process by going through the verification steps Uninstalling using the console mode Use the console uninstallation method to uninstall IBM Tivoli Common Reporting from a command line Procedure 1 Ata command prompt navigate to the _uninst TIPInstal121 subdirectory of the IBM Tivoli Common Reporting installation directory 2 Run the uninstall command specifying console mode Mr uninstal exe i console and M uninstall sh i console 3 Follow the displayed instructions to complete the uninstallation You will need to provide a user ID and password with the tipadmin role typically the same user ID you used to install IBM Tivoli Common Reporting Tip You will not be asked for password if WebSphere Application Server has been stopped If you forgot your password you can kill WebSphere Application Server process first and then run the uninstallation Your password will not be required Uninstalling using the silent mode Use the silent uninstallation procedure for unattended uninstallation It can be performed with the use of a response file You can choose the silent mode of uninstallation by using silent argument for the i parameter Procedure 1 From the following
37. note of the package location and copy the upgradeData zip package to the computer where the reporting engine is installed Use the tcrUpgrade bat Windows or tcrUpgrade sh Linux located in the TCR_install_dir upgrade bin directory to import the package to the previously upgraded Tivoli Common Reporting engine Use the following command to import the package to the computer with the reporting user interface installed tcrUpgrade sh upgrade_directory_location java_home_directory operation import location reporting_engine_path upgradeDataFile upgradeData zip_location upgrade_directory_location For Tivoli Integrated Portal based Tivoli Common Reporting version prior to 2 1 1 the directory is TCR_install_dir profiles TIPProfile upgrade and for version 2 1 TCR_component_dir integration For non Tivoli Integrated Portal based such as Tivoli Common Reporting 2 1 reporting engine the directory is TCR_install_dir upgrade Upgrading with external Cognos Upgrade Tivoli Common Reporting to version 2 1 1 using the existing Cognos instance Before you begin Ensure that you have done the following tasks e Prepare administrative user login and password Perform the following steps to upgrade your Tivoli Common Reporting instance to version 2 1 1 About this task When upgrading from Tivoli Common Reporting version 2 1 Tivoli Integrated Portal is not upgraded You can upgrade it manually to version 2 2 Procedure 1 Start th
38. on option is enabled between the two reporting options 2 Go to Reporting gt Common Reporting 3 Open the Launch drop down list and choose Administration 88 User Guide 4 On the Security tab go to Users Groups and Roles and edit the Cognos user namespace 5 Locate the System Administrators group and set properties for the group by clicking More gt Set properties 6 On Members tab click Add to add an individual administrative user 7 Add the administrative user of your choice from the VMMProvider namespace and click OK to save the settings 8 Remove the Everyone user group from System Administrators by checking the checkbox and clicking Remove 9 Click OK to save the new settings Constraining access to BIRT reports Manage permissions granted to users or user groups for BIRT reports and capabilities for reports report sets or folders in the same way as in Cognos reports By default permissions and capabilities that user groups or reports are assigned are inherited from the parent entry About this task You can change the default permissions that specific groups or users have to reports or report packages You can also change capabilities for reports report sets and folders Procedure 1 Log in to Tivoli Integrated Portal 2 Go to Reporting gt Common Reporting 3 Navigate to the report for which you want to change user permissions and select it 4 Click Actions gt Set properties 5 Go to
39. post processing script it must include two parameters e Parameter 1 specifies the name of the file that is the report e Parameter 2 specifies the name of the file that is the XML descriptor file About this task Follow the instructions below in order to generate a report Note Drill Through is supported Procedure 1 If you have not done so already log in to Tivoli Common Reporting and select Reporting gt Common Reporting 2 Click the p gt icon Public Folders gt Common Reporting E E WY 4 e Ej of x ay 33 Entries 1 i OINK Name Modified Actions m gt Reporting Overview September 16 2009 1 28 33 PM Ptions Reporting Overview 3 The options window will appear Choose the options you prefer and click Run 4 Set the parameters and click Finish The report is generated You can now save the report to be able to view it at a later time Saving a BIRT report After you have generated a report you can save it to be able to instantly view it at a later time with the data from the time of the report creation Before you begin Generate a report that you want to save About this task Procedure 1 Select Run 2 In the Run with options Reporting Overview select Save the report option The following formats are supported for BIRT reports e HTMLI PDF e DOC XLS 3 Specify the report parameters and click Finish to confirm your choice The
40. specific API For reports using the Java code the java jar files should be stored inside the resources directory unlike in Tivoli Common Reporting v 1 2 in which they were stored in the lt 7CR_install_dir gt lib directory 3 In contrast to Cognos reports BIRT reports are stored not in a data base but in a separate folder on the hard disc Consequently you cannot export a full report package using Cognos UI the package would include Cognos reports and links to the reports form the hard drive which would not work on a different work station Working with reports This section contains topics that provide instructions on how to work with reports using IBM Cognos 8 Business Intelligence Reporting Uo Use the Common Reporting user interface to navigate the reports About this task This is a simple reference instruction for creating publishing importing and running your reports Procedure 1 Create a data source for your reports with IBM Cognos 8 Framework Manager and publish your report package Note Creating data sources and publishing report packages requires report modeling experience Use IBM Cognos 8 Framework Manager to model reports This is a separately installed component of Tivoli Common Reporting available from your installation media For information on how to create data sources and publish packages see IBM Cognos amp Framework Manager User Guide 2 Import your report package 3 Run and dist
41. the Permissions tab The table shows default permissions set for user groups 6 Select Override the access permissions acquired from the parent entry and choose the types of permissions that you want to grant to specific user groups 7 Go to the Capabilities tab In the table you can see what capabilities are assigned to reports report sets or folders 8 Select Override the capabilities acquired from the parent entry to grant and deny capabilities What to do next To find out more about permissions and capabilities see IBM Cognos Administration and Security Guide Permissions and Capabilities ODBCINI variable configuration The ODBCINI environment variable sets a common path to the odbc ini file for all products using Tivoli Common Reporting This variable can be set for non Windows operating systems only Tivoli Common Reporting sets the ODBCINI environment variable in its start scripts startTCRserver sh and startTCRserver cmd ODBC first looks for the ODBCINI variable If the variable is not found ODBC tries other system locations Chapter 4 Configuring 89 Tivoli Common Reporting sets the variable to a path in Tivoli Integrated Portal so that it is common for all products using Tivoli Common Reporting Configuring portlet functions Customize your Tivoli Common Reporting installation by modifying the portlet functions Tivoli Integrated Portal configuration About this task You can perform further Tivoli In
42. the Tivoli Integrated Portal look and feel BIRT reports in Cognos IBM Cognos 8 supports BIRT reports BIRT reports in Cognos overview IBM Tivoli Common Reporting supports BIRT reports known from the previous version You can generate BIRT reports in the same way as Cognos reports Public Folders gt Common Reporting E 3 CS 2 A E of x a Ja Entries 1 C Name Modified fae Reporting Overview September 16 2009 1 28 33 PM Copyright IBM Corp 2007 2011 91 You can identify BIRT reports by the BIRT icon J Import BIRT reports into Cognos with the tremd import on page 133 command You can use the report packages created for Tivoli Common Reporting version 1 1 1 1 2 and 1 3 The operations you can perform on BIRT reports are the same as the ones for Cognos reports You can run copy cut paste and rename the reports You can also schedule them and send them via e mail You can create report views and save your reports Restriction Reports cannot be edited using the Report Studio Important IBM Tivoli Common Reporting supports BIRT versions 2 2 1 and 2 2 2 only Running BIRT reports 92 User Guide BIRT reports are generated in the same way as Cognos reports Run a report and check your infrastructure status Before you begin You can set file location to save copy of report output to use it again later or for archive purposes If you decide to use a
43. this flag is identical to the accessIdentity flag Its presence ensures compatibility with earlier versions of Tivoli Common Reporting deny Prevents a user or group from accessing the specified resource If a user belongs to more than one group and any of these groups has been denied access to a resource the user will not be able to access this resource entity cognosSearchPath Specifies the Cognos search path to a resource grant Adds an authorization permission for the specified user role or group to access the specified resources If a user has multiple roles and belongs to multiple groups it is enough to grant permission to any of these objects help Displays syntax and usage information of a command flag permissions permission permission 2 Specifies the type of permission that you want to grant to a user or group You can grant multiple permissions at the same time They must be separated by space Possible values are e read e write e execute e setPolicy e traverse remove Removes deny on a permission as well as an authorization role for the specified user or group to access the specified resources However if a user belongs to more than one group and any of these groups has access to a specified resource the user will still be able to access this resource Examples e This example grants user CAMID VMMProvider tester setPolicy and write permissions to the object content package name Common Reportin
44. upgrading to a higher version of Tivoli Integrated Portal easier Chapter 2 Installing 13 During the installation of the reporting engine only one directory is created as the reporting engine is not a Tivoli Integrated Portal based component Installation directories The following installation directories are created for default Tivoli Common Reporting stand alone installation e The directory that contains the uninstaller and the installation log files In documentation it is referred to as TCR_install_dir Windows operating systems C IBM tivoli tcr non Windows operating systems opt IBM tivoli tcr e Tivoli Integrated Portal installation directory referred to as TIP_install_dir Windows operating systems C IBM tivoli tipv2 non Windows operating systems opt IBM tivoli tipv2 e TIP_components_dir directory containing Tivoli Integrated Portal components Tivoli Common Reporting is one of Tivoli Integrated Portal components but there may be others installed as well Windows operating systems C IBM tivoli tipv2Components non Windows operating systems opt 1BM tivoli tipv2ComponentsTivoli Common Reporting is located in the TCRComponent directory in the documentation referred to as TCR_component_dir Windows operating systems C IBM tivoli tipv2Components TCRComponent non Windows operating systems opt IBM tivoli tipv2Components TCRComponent Cognos installation directory The directory that Cognos is installed in
45. will work with reports Scenario C Integrating existing Cognos BI infrastructure System A System B Tivoli Common Reporting server Tivoli Common Cognos Reporting console a ee ee Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting Use this if you already use Cognos BI infrastructure The Tivoli Common Reporting user interface is installed on one computer and configured to work with a Cognos that was installed from a source other than the IBM Tivoli Common Reporting installation program The engine can be an IBM Cognos BI Server or IBM Cognos 8 Business Intelligence Reporting Tivoli Common Reporting installation paths Learn about the location of the Tivoli Common Reporting installation directories that depends on the installation scenario The installation paths in version 2 1 1 remain the same as the installation paths in version 2 1 Changes in Tivoli Common Reporting version 2 1 The structure of the catalogs into which Tivoli Common Reporting 2 1 is installed is different than in previous versions This is caused by architectural changes in Tivoli Integrated Portal on which Tivoli Common Reporting is based The installation directory is now divided into two catalogs one containing Tivoli Integrated Portal only and the other containing Tivoli Integrated Portal based components and products This solution makes
46. 4 bit installer However you cannot use this installer to upgrade a previous version of Tivoli Common Reporting because of the discrepancy in bitness Users and groups are not migrated because they are usually stored in LDAP You can use the TIPProfile upgrade bin exportLDAPconfig bat file to export the LDAP settings The installer creates tipadmin as the default user present before and after upgrade Copyright IBM Corp 2007 2011 45 JNDI data sources are not migrated You must recreate them manually after upgrade Upgrade modes There are two upgrade modes that you can select from e Upgrading from the existing instance of Tivoli Common Reporting Choose this upgrade mode if you have 4 GB of available main memory e Upgrading from the package which allows you to upgrade your Tivoli Common Reporting instance on a different computer than the one on which it is installed by using a previously generated package This upgrade mode requires 2 GB of available memory Upgrading on a single computer 46 User Guide Choose this scenario to upgrade Tivoli Common Reporting version 1 1 1 and 1 2 For versions 1 3 and 2 1 this method is suitable if your existing installation is on a single computer You can upgrade interactively with the installation wizard as a single point of reference for the whole upgrade process or in silent mode which does not require any interaction on your part Before you begin Ensure that you have compl
47. 6 32 bit and 64 bit e SUSE Linux Enterprise Server 11 0 x86 32 bit and 64 bit Restriction The following system libraries are required to run Tivoli Common Reporting compat 32bit compat libstdc openmotif libs 32bit 2 2 4 e SUSE Linux Enterprise Server 10 0 System z 31 bit and 64 bit SUSE Linux Enterprise Server 11 0 System z 64 bit Restriction The following system libraries are required to run Tivoli Common Reporting on SUSE systems libstdc 33 32bit 3 3 3 11 9 compat 32bit 2009 1 19 2 1 openmotif22 libs 32bit 2 2 4 138 18 1 Solaris e Solaris 9 on SPARC 32 bit and 64 bit e Solaris 10 on SPARC 32 bit and 64 bit En Microsoft Windows Microsoft Windows Server 2003 R2 Enterprise Edition 32 bit and 64 bit e Microsoft Windows Server 2008 R2 Standard Edition 64 bit e Microsoft Windows Server 2008 Standard Edition 32 bit and 64 bit e Microsoft Windows Server 2008 Enterprise Edition 32 bit and 64 bit e Microsoft Windows Server 2008 R2 Enterprise Edition 64 bit Table 2 Hardware and software requirements continued Deployment Engine 400 MB in the usr directory or your home directory at least 1 MB in the var directory Important If you are installing on a non Windows operating system and you have the var and usr directories mounted on a different partition ensure that the partition is not empty Otherwise the Deployment Engine will not install Supported web browsers e Windows I
48. Administration b Go to the Configuration tab and select Content Administration c Create new package export by clicking d Follow the wizard to export the archive The exported archive is now visible in the Administration window For versions earlier than 2 1 archive the TCR_component_dir data directory where all BIRT objects are stored Archive the directory where report images are stored What to do next Modify the existing single computer installation Modifying the existing single computer installation Perform this task as the first step in migrating from single computer installation to distributed installation Before you begin Ensure that you have a computer with Cognos installed Procedure Navigate to the following directory and edit the web xml file A TCR _component_dir cognos war gateway and TCR_component_dir cognos war gateway Before the lt web app gt string add the following lines lt servlet mapping gt lt servlet name gt ServletGateway lt servlet name gt lt url pattern gt servlet component lt url pattern gt lt servlet mapping gt lt security constraint gt lt web resource collection gt lt web resource name gt C8 lt web resource name gt lt url pattern gt servlet component lt url pattern gt lt http method gt GET lt http method gt lt http method gt POST lt http method gt lt web resource collection gt lt auth constraint gt lt role name gt cps_user lt role n
49. Application server will use Only WAS_WC_defaulthost is required The rest of the ports if not specified will be derived basing on the WAS _WC_defaulthost WAS_WC_defaulthost 16310 WAS_WC_defaulthost_secure 16311 WAS_BOOTSTRAP_ADDRESS 16312 WAS_SOAP_CONNECTOR_ADDRESS 16313 WAS_IPC_CONNECTOR_ADDRESS 16314 WAS_WC_adminhost 16315 WAS_WC_adminhost_secure 16316 WAS_DCS_UNICAST_ADDRESS 16318 WAS_ORB_LISTENER_ADDRESS 16320 WAS_SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 16321 WAS_CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 16322 WAS_CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 16323 TCR_sample_response_dispatcher txt He HE a EA EE A A a a a a a a a a a aE COPYRIGHT TOP OCO Source Materials 5724 T69 Copyright IBM Corp 2011 The source code for this program is not published or otherwise divested of its trade secrets irrespective of what has been deposited with the U S Copyright Office Hatt a A a aH aE a a a a a a a a a AE O COPYRIGHT END He a HE A HE EH A a a a a a a a a a InstallAnywhere variables to configure the install of Tivoli Common Reporting TCR_VERSION components Usage install sh bat f lt full path to this file gt i lt installation mode gt available modes silent console gui On Windows install exe will return immediately To avoid this you should use the batch file install bat which wraps it sign is used here to comment out the
50. CCEPTED has a value other than true the installation will exit By removing the sign before the LICENSE_ACCEPTED false string and changing false to true you mark that you agree to the Tivoli Common Reporting TCR_VERSION license agreement LICENSE_ACCEPTED false PA Choose the preferred installation language For default leave commented Available values are cs de en es fr it ja ko pl pt pt_BR ru tr zh zh_CN zh_TW INSTALLATION_LANGUAGE en Install into existing WebSphere Application Server Specify decision to install Tivoli Common Reporting into an existing WebSphere Application Server Note that If this property is set to true then the following TCR_INSTALLATION_DIRECTORY property must be correctly set to the existing WebSphere Application Server location aka WAS_HOME INSTALL_INTO_EXISTING_WAS false Choose Installation Folder Silent installation provide a fully qualified path example TCR_INSTALLATION DIRECTORY C IBM tivoli tcr Note that Backslash is considered to be a special character and needs to be escaped so use double backslashes when defining the path on Windows Silent uninstallation do not define the TCR_INSTALLATION DIRECTORY leave it commented out Posse For reuse of an instance of Tivoli Com
51. ER_PASSWORD xxx F EEE Enter the ports that WebSphere Application server will use Only WAS_WC_defaulthost is required The rest of the ports if not specified will be derived basing on the WAS_WC_defaulthost WAS_WC_defaulthost 16310 WAS_WC_defaulthost_secure 16311 WAS_BOOTSTRAP_ADDRESS 16312 WAS_SOAP_CONNECTOR_ADDRESS 16313 WAS_IPC_CONNECTOR_ADDRESS 16314 WAS_WC_adminhost 16315 WAS_WC_adminhost_secure 16316 WAS_DCS_UNICAST_ADDRESS 16318 WAS_ORB_LISTENER_ADDRESS 16320 WAS_SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 16321 WAS_CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 16322 WAS_CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 16323 Installing into an existing Cognos infrastructure Use this installation scenario if you already use Cognos BI infrastructure The existing infrastructure can be either IBM Cognos BI Server or IBM Cognos 8 Business Intelligence Reporting Procedure 1 10 Insert the product DVD or if you are installing from an image open the directory that contains the files you extracted previously Start the installation launchpad EET launchpad exe and MOUS launchpad sh Read the installation information and click Install Tivoli Common Reporting Tip At any time of running the installation you can go back to the launchpad to access the on line documentation or the PDF version of the Installation Guide Choose your installation language read the Welcome page and accept the terms of th
52. Engine may already exist on your hard drive e If you are installing as root and var and usr are on the same partition the disk space required is 255 MB e If you are installing as root and var and usr are on different partitions the disk space required is 5 MB on the var partition and 250 MB on the usr partition e If you are installing as non root the disk space required is 255 MB on the home partition e g home 2 MII a additional disk space required for the installation of Deployment Engine in the target installation location is 255 MB b If the TEMP folder is located on the same partition as the target installation directory the installation requires additional 800 MB on this partition c If the TEMP folder is located on a different partition than the installation directory the installation requires 800 MB on that partition Installing using the installation wizard Use the graphical user interface to install the product automatically and to interactively check whether all the required configuration options are in place Two installation scenarios are possible when installing Tivoli Common Reporting About this task MIN To perform tasks described in this section you must belong to the Administrators group or be an Administrator Installing on one computer Install the components on a single system for non scalable reporting The installation program guides you through the process step by step About
53. IP_install_dir profiles TIPProfile bin and run the wsadmin sh command b Provide the login and password for a Tivoli Common Reporting administrator c Run the following commands e AdminApp uninstall IBM Cognos 8 e AdminConfig save Stop the server from the command line interface a Navigate to the installation subdirectory Chapter 4 Configuring 67 MMS TCR _component_dir bin and run the stopTCRserver bat command e MOLI TCR component_dir bin and run the stopTCRserver sh command 4 Edit the stop and start server scripts a Edit the startTCRserver script by commenting out the following lines E using the characters start B D COGNOS_DIR bin tcr_cogconfig bat s using the character COGNOS_DIR bin tcr_cogconfig sh s b Edit the stopTCRserver script by commenting out the following lines A using characters call COGNOS_DIR bin tcr_cogconfig bat stop using the character COGNOS_DIR bin tcr_cogconfig sh stop 5 Modify the urlconfiguration properties file a Go to IES 7CR_component_dir lib configuration 4 TCR_component_dir 1ib configuration b Change the following lines in the script e by adding the character at the beginning of the first line e urlprovider contextRoot tarf by adding the character at the beginning of the line e urlprovider servletMapping servlet component by adding the character at the beginning of the line e urlprovider portNumber 9300 by prov
54. IRECTORY C IBM tivoli tcr Note that Backslash is considered to be a special character and needs to be escaped so use double backslashes when defining the path on Windows Silent uninstallation do not define the TCR_INSTALLATION DIRECTORY leave it commented out For reuse of an instance of Tivoli Common Reporting point to its existing installation location Examples For Windows platform C IBM tivoli tcr For UNIX platform opt IBM tivoli tcr TCR_INSTALLATION_DIRECTORY For the TIP specific part of the solution Hogue If INSTALL_INTO_EXISTING_WAS true the install folder must be the location of WebSphere Application Server such as TIP_INSTALLATION DIRECTORY C IBM WebSphere AppServer Examples For Windows platform C IBM tivoli tip For UNIX platform opt IBM tivoli tip TIP_INSTALLATION_DIRECTORY For the reuse scenario If installing in a reuse scenario to simply add some additional components to already installed instance set this variable to true otherwise comment it out or set to false the default E E Example REUSE _EXISTING_INSTALLATION true REUSE_EXISTING_INSTALLATION false Installation scenario Choose one of the following installation components configuration for this in
55. L the statement Insert insert is wrongly translated because of the toLowerCase and toUpperCase functions of String class for the letters I and i that in Turkish have special meaning Resolving the problem Change the environment language to en_US UTF 8 Error QE DEF 0368 Unable to decrypt user name and password credentials from the content store Symptoms User name and password cannot be decrypted from the Cognos Content Store If you point Framework Manager to a new Tivoli Common Reporting installation you may get the following error QE DEF 0368 Unable to decrypt user name and password credentials from the content store Causes This happens when old credential keys are cached in Framework Manager Resolving the problem Chapter 6 Troubleshooting and support 117 1 Close Framework Manager together with its configuration user interface 2 Navigate to the FM_install_dir Configuration directory 3 Back up the following directories csk encryptkeypair signkeypair and delete them 4 Open Configuration click Save and Apply Unable to locate libcoguador on Linux with Oracle Symptoms If you are using Cognos on Linux with Oracle data source and you try to test the Cognos connection from the user interface you may get an error that Cognos is unable to locate the libcoguador gateway Resolving the problem Cognos does not support 64 bit systems so if you are using a 64 bit system and the Oracle client is a 64 bit ve
56. NNECTOR_ADDRESS 16314 WAS_WC_adminhost 16315 WAS_WC_adminhost_secure 16316 WAS_DCS_UNICAST_ADDRESS 16318 WAS_ORB_LISTENER_ADDRESS 16320 WAS_SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 16321 WAS_CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 16322 WAS_CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 16323 TCR_sample_response_external txt tate EH EE EEE EE a a a a a a a a AE COPYRIGHT TOP OCO Source Materials 5724 T69 Copyright IBM Corp 2011 The source code for this program is not published or otherwise divested of its trade secrets irrespective of what has been deposited with the U S Copyright Office ete Ea a eH a a a a a a a a a AE COPYRIGHT END ee EH EE EH a E a aa a a a a a aa a a a a EE InstallAnywhere variables to configure the install of Tivoli Common Reporting TCR_VERSION components Usage install sh bat f lt full path to this file gt i lt installation mode gt available modes silent console gui On Windows install exe will return immediately To avoid this you should use the batch file install bat which wraps it sign is used here to comment out the lines that follow it ae HE A HE EE a a aa a a a a a a a a PAARA ARAARA AARAA AAAA EEE EE AAE AA EAA EEA EEEE EEEEE tt This response file example is profiled for the external installation scenario for further details on installation scenarios see TCR TCR_VERSIONG documentation Variabl
57. On non Windows platforms run the following command to add run permissions for all upgrade scripts chmod x existing _TCR_install_dir profiles TIPProfile upgrade bin sh b Run the following command Chapter 3 Upgrading 55 56 User Guide reporting_engine_install_dir upgrade bin tcrUpgrade bat reporting _engine_install_dir upgrade java_home_dir operation export location reporting_engine_install_dir output reporting_engine_install_dir upgrade output customPropertiesFile reporting_engine_install_dir upgrade plugins tcrCustomProperties prope reporting_engine_install_dir upgrade bin tcrUpgrade sh reporting _engine_install_dir upgrade java_home_dir operation export location reporting_engine_install_dir output reporting_engine_install_dir upgrade output customPropertiesFile reporting_engine_install_dir upgrade plugins tcrCustomProperties prope The package is created in the existing_TCR_install_dir upgrade data upgradeData zip folder 2 Repeat steps 2 to 8 in Upgrading using a package in single compute scenario on page 51 What to do next 1 Disable anonymous access from VMMProvider a Open the IBM Cognos configuration by running lt A Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration e user interface TCR_component_dir cognos bin tcr_cogconfig sh reporting engine TCR_component_dir cognos bin tcr_cogconfig sh 2 Upgrade the user interface Upgrading user interfac
58. Restart the web browser Note Turning off the browser s XSS filter has little or no risk when done only on the Trusted Sites zone The IBM Cognos BI application has an internal firewall which protects it from XSS attacks so the browser s filter is redundant Reports in PDF format hang Symptoms When opening a PDF report the report hangs Resolving the problem The reason why the reports do not work properly is that they lack the images Ensure that the report images are in the following folder TCR_component_dir cognos webcontent tivoli Tivoli Common Reporting interface hangs Symptoms After applying permissions in Tivoli Common Reporting and configuring it with a large user repository the interface hangs shows an error or has a poor performance Causes This happens because all the configured users and groups are trying to be returned to the user interface at the same time When browsing the user registry while applying permissions to actions in Tivoli Common Reporting the default action is to display all groups There is also an option to display all users With large user repositories this may result in poor performance timeout or an error with too many results returned Resolving the problem Configure Tivoli Common Reporting to not return all users and groups Instead allow the end user to search for users and groups 1 Edit the VMMprovider properties file located in TIP_install_dir profiles TIPProfile installedA
59. SO 639 1 code for your language parameters pl p2 p3 A list of parameter values used for producing the distributed report separated by spaces These values override any default values specified in the report or report design Each parameter value must be specified using the following format param value If the value contains spaces enclose the parameter in double quotation marks param spaced value Each parameter must correspond to a valid parameter specified in the report design Examples e This example distributes a formatted PDF version of the DBAvail report specifying several parameter values and the output location for the PDF file trcmd distribute report DBAvail format PDF location C tmp reports Q3Avail pdf parameters quarter 3 type NTServers trcmd import The import command flag for the tremd command imports BIRT and Cognos report packages and report designs The type of a package is recognized automatically This command can be used for single box installation and on the reporting engine It is not supported for other scenarios Syntax Use this syntax to import a report package tremd import bulk pkgFile reportSetBase rsBase resourceBase resourceBase designBase designBase help Use this syntax to import a report design and also create a new report associated with the design Chapter 7 Reference 133 tremd import design designPath resourceDir resourcePath reportSetBase rsBas
60. T Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration e EE User interface TCR_component_dir cognos bin tcr_cogconfig sh reporting engine TCR_install_dir cognos bin tcr_cogconfig sh b Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to False c Save your configuration and restart the Tivoli Common Reporting server Upgrading with the use of a package in distributed scenario 54 User Guide Upgrade the reporting engine and user interface to Tivoli Common Reporting 2 1 1 The distributed upgrade scenario is available for Tivoli Common Reporting versions 2 1 and 1 3 only Before you begin e Ensure that you know the administrative user login and password e If you are upgrading from Tivoli Common Reporting version 1 3 or 2 1 ensure that all your report images are in the TCR_install_dir profiles TIPProfile installedApps TIPCel1 IBM Cognos 8 ear p2pd war tivoli directory because only this directory is moved over to version 2 1 1 Procedure 1 Upgrade the reporting engine 2 Upgrade the user interface Results You have upgraded to Tivoli Common Reporting version 2 1 1 and the following data was imported e Database drivers e Report snapshots were generated to PDF format and saved as saved reports e Cognos Content Store was migrated from the embedded derby database If your Content Store was located on a
61. Tool bat sh release lock username password Configuring the reporting engine for load balancing Load balancing for the reporting engine bases on Cognos It is recommended that the Cognos database you are using is based on Enterprise solution such as DB2 Oracle or MS SQL Before you begin You need to have one or more reporting engines installed in your infrastructure About this task When you have installed all the reporting engines you must configure Cognos Content Store to enable all the reporting engines to connect to it Procedure 1 Select the database on which you want to install Cognos Content Store You may installed a separate database to serve this purpose or reuse the existing derby database installed with one of the reporting engines 2 Run the tcr_cogconfig bat MENA or tcr_cogconfig sh to open IBM Cognos Configuration and configure your reporting engines to connect to the database with Cognos Content Store installed in it The script is located in user_installation_directory cognos bin for Cognos reporting engine installation scenario TCR_component_dir cognos bin for user interface for Cognos installation scenario e If you chose to install a new database refer to Cognos documentation for details on how to configure the database All reporting engines must point to this database e If you chose to reuse the database installed on one of the reporting engines you must delete the existing databases configure
62. a Open the IBM Cognos configuration by running MOI Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration e User interface TCR_component_dir cognos bin tcr_cogconfig sh reporting engine TCR_install_dir cognos bin tcr_cogconfig sh b Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to False c Save your configuration and restart the Tivoli Common Reporting server Chapter 3 Upgrading 49 Upgrading Tivoli Common Reporting engine Upgrade your Tivoli Common Reporting versons 1 3 or 2 1 instance to 2 1 1 The reporting engine must be upgraded before the user interface is upgraded Before you begin Enable anonymous access to the reporting engine 1 Open the IBM Cognos Configuration by running MEIN Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration EET EO CR install _dir tip products tcr Cognos c8 bin tcr_cogconfig sh 2 Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to True 3 Save your configuration and restart the reporting engine About this task Perform this task on the computer where Tivoli Common Reporting engine is installed Procedure 1 Start the upgrade by following steps 1 to 4 and 6 to 8 in Reporting installation instructions 2 Choose Upgrade the existing insta
63. allation 41 single sign on 7 single computer installation 17 SSO 7 T technical overview 1 troubleshooting using log files 107 troubleshooting Common Reporting 114 troubleshooting installation 108 U uninstallation console mode 41 manual 42 overview 40 silent mode 41 uninstallation wizard 40 verifying 44 V verifying installation 35 verifying uninstallation 44 W Web resources 5 wizard uninstallation 40 143 144 User Guide Printed in USA SC14 7613 00
64. alling the product Tivoli Common Reporting does not install after upgrading and uninstallation Symptoms After upgrading Tivoli Common Reporting instance to version 2 1 and then uninstalling version 2 1 Tivoli Common Reporting 2 1 does not install again Resolving the problem 1 Remove the program installation directory 2 Install Tivoli Common Reporting into a different directory 3 Set the IAGLOBAL_ENABLE_OPTIONAL_PRECHECKS property to false Installation fails because the Deployment Engine fails to initialize 108 User Guide Symptoms Installation or upgrade fails with the following error Deployment Engine failed to initialize Resolving the problem 1 Go to DE_install_dir logs and remove all lock_ files 2 Ensure that all installer processes are closed To do this run the following commands e ps ef grep java grep v grep E tskmgr look for Java processes pointing to the tmp parameter and kill the processes Remove the temporary files from previous unfinished installations Ensure that the Java process connected with Deployment Engine derby is closed by running the following command ps ef grep derby grep v grep E tskmgr and look for Java process with a parameter pointing to the derby database and Deployment Engine installation directory and kill the processes Non root installation fails Symptoms When running the Tivoli Common Reporting installer on a RedHat Linux operating sy
65. ame gt lt auth constraint gt lt security constraint gt lt login config gt lt auth method gt BASIC lt auth method gt lt realm name gt Cognos 8 lt realm name gt lt login config gt lt security role gt lt role name gt cps_user lt role name gt lt security role gt Open the IBM Cognos Configuration by running MECN Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration and UUM TCR component_dir cognos bin tcr_cogconfig sh 3 In IBM Cognos Configuration generate the ServletGateway ear file by performing these steps a Go to Actions gt Build Application Files b In the Application section deselect the IBM Cognos 8 and check Servlet gateway c In the Application Server Type section check IBM WebSphere 6 x and click Next d Check EAR file in the File type section specify location type in tarf as Context root and click Next 4 If stopped start the server from a command line interface a Navigate to the installation subdirectory B 7CR_component_dir bin and run the startTCRserver bat command and E 7CR_component_dir bin and run the startTCRserver sh command 5 Uninstall IBM Cognos 8 from WebSphere Application Server a Navigate to the installation subdirectory E 7 P_install_dir profiles TIPProfile bin and run the wsadmin bat command and E 7TIP_install_dir profiles TIPProfile bin and run the wsadmin sh command e Provide the login an
66. ample_response_gateway txt on the computer where you want to install the user interface e For the integration with existing Cognos BI scenario use the TCR sample response _external txt file CR_sample_response_embedded txt TCR_sample_response_dispatcher txt TCR_sample_response_gateway txt TCR_sample_response_external txt TCR_sample_response_embedded txt A A A a Ee EE a a E E E E a a a a EAE COPYRIGHT TOP OCO Source Materials 5724 T69 Copyright IBM Corp 2011 Chapter 2 Installing 23 24 User Guide The source code for this program is not published or otherwise divested of its trade secrets irrespective of what has been deposited with the U S Copyright Office Hee EE He Eee A ERARA ERRARE ERARE a a a a aA COPYRIGHT END ee HH A HH HE a Ea a a a a a a a a a a a EE InstallAnywhere variables to configure the install of Tivoli Common Reporting TCR_VERSION components Usage install sh bat f lt full path to this file gt i lt installation mode gt available modes silent console gui On Windows install exe will return immediately To avoid this you should use the batch file install bat which wraps it sign is used here to comment out the lines that follow it i a a a a a a EE EEE EEE i a a a a a EEE This response file example is profiled for the embedded single box installation scenario for further
67. and confirm your choice Close Cognos Configuration Create an empty file called FIPS mode in the bin cgi bin directories in TCR_component_dir cognos for distributed installation and for single computer installation and for user interface in distributed installation also in TIPProfile directory located in TCR_install_dir profiles Delete the following directories e TCR _component_dir cognos configuration encryptkeypair e TCR _component_dir cognos configuration signkeypair Overwrite the TCR_component_dir cognos configuration cogstartup xml with the cogstartup xml file that you saved in step 4 Run Cognos Configuration EUS TCR _component_dir Cognos bin tcr_cogconfig bat E 7CR component_dir cognos bin tcr_cogconfig sh Save the configuration and exit Cognos Configuration Start the Tivoli Common Reporting server by running E TCR component_dir bin startTCRserver bat e E TCR_component_dir bin startTCRserver sh Enabling FIPS 86 User Guide 1 You can configure the Tivoli Integrated Portal Server to use Federal Information Processing Standard Java Secure Socket Extension files About this task Follow these steps to enable FIPS 140 2 for the Tivoli Integrated Portal Server Procedure Configure the application server to use FIPS a In the administrative console click Security gt SSL certificate and key management b Select the Use the United States Federal Information Processing Standard FIPS
68. anual cleanup of your environment Verifying the uninstallation 44 User Guide Verify the uninstallation procedure after you have performed the procedure using the graphical user interface console or silent mode Procedure 1 Check that the Tivoli Common Reporting installation directories are empty 2 MEMS Check if there are any services registered for the program by opening Control Panel gt Administrative Tools gt Services and searching for Tivoli Integrated Portal TIPProfile Port_XxX service 3 If the Deployment Engine registry contained other components than Tivoli Common Reporting verify that there are no entries related to Tivoli Common Reporting in the Deployment Engine registry by listing the existing components M c Program Files IBM Common acsi bin listIU cmd and usr ibm common acsi bin listIU sh 4 If your Tivoli Common Reporting instance was the only component in Deployment Engine registry verify if the Deployment Engine has been removed completely 5 E Verify that there is no Tivoli Common Reporting entry in menu Start What to do next If any of the items were not removed correctly by the uninstallation procedure uninstall the program manually Chapter 3 Upgrading to Tivoli Common Reporting version You can upgrade your instance of Tivoli Common Reporting to version 2 1 1 Three upgrade scenarios are available depending on your needs e Single computer scenario e Distributed scen
69. aries exists before starting the Tivoli Common Reporting server and configure the system library path to point to the database client library directory by modifying the following environment variable ECM LIBPATH ERT SHLIB_PATH ETT BETO LD_LIBRARY_PATH For example you can modify the startTCRserver sh script by inserting the following line before starting WebSphere Application Server export LD LIBRARY _PATH opt ibm db2 V9 5 1ib32 LD_LIBRARY_PATH For non Windows systems you may also need to source the DB2 profile in the Tivoli Common Reporting environment before starting the server for example home db2 user sqlib db2profile You can modify the startTCRserver sh script by inserting the following line before starting WebSphere Application Server home db2 user sqlib db2profile where db2 user is your local DB2 user ID 2 Create new database connection for Cognos by following the steps a From the Common Reporting portlet go to Launch drop down list and choose the Administration b On the Configuration tab add a new data source by clicking c Follow the New Data Source wizard as required noting the following steps e On the second panel choose an DB2 database as Type e On the third panel specify the name of the connection you have noted before as the DB2 database name and in the Signon section specify a new User ID and Password Results You have now connected your Tivoli Common Reporting to an DB2 database
70. ario e Upgrading from package Preparing to upgrade Before upgrading review this section to learn about hardware requirements and other considerations Basic upgrade information You can upgrade to Tivoli Common Reporting version 2 1 1 from the following versions e Tivoli Common Reporting 1 1 1 e Tivoli Common Reporting 1 2 0 e Tivoli Common Reporting 1 2 0 1 e Tivoli Common Reporting 1 3 e Tivoli Common Reporting 2 1 There are two upgrade scenarios available one for single computer and one for distributed upgrade scenarios With versions 1 1 1 and 1 2 x distributed upgrade is a manual procedure in which you migrate a single computer installation to a distributed one If you are upgrading from Tivoli Common Reporting 2 1 the 2 1 1 version upgrades it together with its components such as Tivoli Integrated Portal which is upgraded from version 2 1 to version 2 2 and Cognos 8 Business Intelligence Reporting which is upgraded from version 8 4 1 to version 8 4 1 fix pack 3 If you are upgrading from version 2 1 the upgrade process does not change the port numbers or file paths For versions older than 2 1 the upgrade is a side by side process in result of which you have two instances of Tivoli Common Reporting the 2 1 1 version and the older version on your system To keep only the newest version of Tivoli Common Reporting on your computer uninstall the older version Tivoli Common Reporting version 2 1 1 introduces a 6
71. ashes when defining the path on Windows E Silent uninstallation do not define the TCR_INSTALLATION_DIRECTORY leave it commented out Examples For Windows platform C IBM tivoli tcr For UNIX platform opt IBM tivoli tcr TCR_INSTALLATION_DIRECTORY Installation scenario Choose one of the following installation components configuration for this installation procedure cognos_reporting_engine first step of the distributed installation scenario INSTALLATION SCENARIO cognos_reporting_engine ui_for_cognos second step of the distributed installation scenario INSTALLATION _SCENARIO ui_for_cognos single_computer_installation integrate_existing_cognos INSTALLATION _SCENARIO cognos_reporting_engine Port number for IBM Cognos content database COGNOS_CONTENT_DATABASE_PORT 1527 Should it be upgrade PERFORM _UPGRADE false Following variables are for upgrade only Path to the previous instance of TCR or migration package UPGRADE_SOURCE opt IBM tivoli tcr or on Windows systems note double backslashes UPGRADE_SOURCE C IBM tivoli tcr Define type of the upgrade source existing instance or a migration package Valid values instance package UPGRADE_MODE instance Chapter 2 Installing 27 28 User Guide TCR_sample_response_gateway txt Ht a HEH EA EA a a a
72. ation 108 Tivoli Common Reporting does not install after upgrading and uninstallation 108 Installation fails because the Deployment Engine fails to initialize 108 Non root installation fails 109 After upgrading from Tivoli Common Reporting 1 3 the reporting engine does not work 110 Installation using the install sh script fails 111 Installation fails on a system with Turkish locale 111 The Work with reports panel displays an error 111 Cognos Business Intelligence does not install on Windows 2008 64 bits R2 111 Cognos Business iin ais does not install lt on Linux 112 UDA SQL 0031 Unable t access database QE DEF 0285 Logon failure 112 Uninstalling the Deployment Engine io complete Tivoli Common Reporting manual uninstallation lt 112 Troubleshooting Common Reporting 114 Browsing images does not work in Report Studio 114 Your login session expires while working with the Common Reporting portlet 114 iv User Guide ODBC System DSN connections fail to test from the Tivoli Common Reporting server 114 When starting Framework Manager you are prompted to supply your login details twice 115 Drill through definitions in BIRT i sai do not work 5 115 The Work with reports window i is blank 116 An error UDA SQL 0569 appears while starting Cognos server 116 An error occurs when starting Fiamewoik Manager 116 Logon fails in Turkish locale P H7 Error QE DEF 0368 Unable to de
73. aved reports Cognos Content Store was migrated from the embedded derby database If your Content Store was located on an external database instead of on the embedded derby the same database is used by the new instance of Tivoli Common Reporting What to do next 1 2 3 If you want to use LDAP as your user repository LDAP configuration is not automatically transferred to the upgraded instance of Tivoli Common Reporting A file with LDAP information exported from the previous version of Tivoli Common Reporting is in TCR_component_dir logs upgrade repository Id properties If you upgraded from Tivoli Common Reporting version 1 3 or 2 1 configure LDAP in Tivoli Integrated Portal only Create new schedules for your reports Report schedules that are created for versions of Tivoli Common Reporting versions earlier than 2 1 are not mapped to Cognos scheduler Configuring JDBC data sources using JNDI on page 97 the same way as you configured them for the Tivoli Common Reporting version that you previously used JNDI data sources are not transferred during the upgrade process Verify that all your report images have been moved Chapter 3 Upgrading 47 5 Log in to the Tivoli Integrated Portal console and check whether all your reports appear in the Common Reporting gt Connection view Try to CTET check whether it is working properly 6 If you decided to import report snapshots ensure that the snapshot appears as R
74. ce p1 p2 p3 help Tip To get the unique report name used in this command run the tremd list on pane 134 age 134 command If reports from packages use a common library for the data source definition you need to only run the command against one report Note 1 Authentication with user userID and password password is required 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider Arguments caseSensitive Specifies that case is respected when matching the search query dataSource pl p2 p3 A list of data source properties separated by spaces Use this argument to restrict the search results to include only data sources whose properties match any of the specified values Each property value must be specified using the following format property value If the value contains spaces use double quotation marks property spaced value Each property must be one of the following e name e displayName e comments e odaDriverClass e odaURL e odaUser e odaPassword e odaJndiName dataSources Modifies the properties of data sources matching the specified search criteria displayName Specifies the report or report set display name query to use when searching for matching reports or report sets help Displays syntax and usage information of a command flag reportName cognosSearchPath Specifies the search path to use when s
75. crypt 1 user name and password credentials from the content store 117 Unable to locate libcoguador o on Linux with Oracle 118 Oracle environment vaviabl s for nanos default user 118 No content displayed i in Common Reporting portlet in Internet Explorer 7 118 Charts in reports do not appear 119 Cognos Configuration does not open 120 Cannot open the sample overview report 120 Error after running a sample overview report 120 When trying to find users in user repository an error appears 121 Connection with the d tasource fails xe Dil Cannot save IBM Cognos Configuration settings 121 The reporting engine fails to start with the SQLCODE 286 and SQLSTATE 42727 122 Report Studio does not work with Internet Explorer 8 122 Reports in PDF format hang 123 Tivoli Common Reporting interface hangs 123 Chapter 7 Reference 125 Commands y 125 Command line authentication 126 tremd access 126 tremd convert 127 tremd datasource 129 tremd delete 131 tremd distribute lt 132 tremd import 133 tremd list 134 tremd modify 136 tremd run 138 tremd version 139 Notices 141 Trademarks 142 Index 143 Chapter 1 Overview Tivoli Common Reporting provides an a integrated reporting solution for the products p in the Tivoli portfolio You can link multiple E reports across various Tivoli products to simplify the report navigation and accel
76. ct and that has at least one child report object In the parent folder expression parent is an axis and folder is a node test content package folder name Documentation Report Samples Selects all child objects in the Documentation Report Samples folder Expressions enclosed in square brackets are predicates used to filter a set of objects content package folder name Documentation Report Samples The at sign specifies a property name The asterisk is a wildcard character content package folder report contains name Product List Selects all report objects in the path content package folder with names that contain the string Product List The predicate contains a call to the function contains The at sign specifies a property name storeID le08b01ef26b496aac06a14f5ae9a572 report Selects all report objects that are descendants of the object that has the storeID with the value le08b01ef26b496aac06al4f5ae9a572 CAMID routingHints Selects all objects in the Cognos namespace where the routingHints property is not nil Expressions enclosed in square brackets are predicates used to filter a set of objects CAMID specifies the Cognos namespace The at sign specifies a property name The asterisk is a wildcard character CAMID not routingHints Selects all objects in the Cognos namespace where the routingHints property is nil Expressions enclosed in square brackets
77. curity module and Lightweight Third Party Authentication LTPA Cognos based Tivoli Common Reporting engine The dispatcher is the entry point for IBM Cognos 8 service requests sent by a web server gateway or other software The dispatcher handles the routing requests and balances the load of user requests to the various IBM Cognos 8 services Cognos gateway A portal enabling communication between Tivoli Common Reporting Server and the Cognos based Tivoli Common Reporting engine Cognos Content Store A database that contains data that IBM Cognos 8 needs to operate such as report specifications published models and the packages that contain them connection information for data sources information about the external namespace and the Cognos namespace itself and information about scheduling and bursting reports Tivoli Integrated Portal web user interface Based on Tivoli Integrated Portal the following web user interface is available for the reporting solution e Common Reporting a web portal for IBM Cognos 8 and a component which interacts with the Cognos Content Store It is a frontend to publish find manage organize and view organization s reports Optional components Tivoli Common Reporting Cognos Application Tier Server Cognos An existing instance of IBM Cognos BI Server or IBM Cognos 8 Business Intelligence Reporting Web resources 4 User Guide Check out other useful Web resourc
78. d for all the other reporting engines and configure them to use the one you chose Tivoli Common Tivoli Common Tivoli Common Reporting engine Reporting engine Reporting engine l IBM Cognos Content Store IBM Cognos IBM Cognos Content Store Content Store Chapter 4 Configuring 75 76 User Guide To configure your reporting engines a Go to the Data Access gt Content Manager section and select IBM Cognos Content Store from the navigation tree Right click the derby database and select Delete Right click Content Manager and select New resource Type the name and choose the type of the database that you want to add Mao g In the database properties window on the right type the IP address of the computer where the reporting engine with the database is installed f Type the user ID and password Return to the navigation tree right click on the database that you have just added and select Test A message informing you that the database works correctly appears 3 Configure the same LDAP for all the reporting engines 4 Configure the user interface to connect to all the reporting engines installed by specifying the URIs of the reporting engines a In the user interface open the Configuration b Go to the Environment section and in the Environment Group Properties panel on the right look for Dispatcher URIs for gateway entry in the Gateway Settings section c Click the value fie
79. d from the embedded derby database If your Content Store was located on an external database instead of on the embedded derby the same database is used by the new instance of Tivoli Common Reporting What to do next 1 If you want to use LDAP as your user repository LDAP configuration is not automatically transferred to the upgraded instance of Tivoli Common Reporting A file with LDAP information exported from the previous version of Tivoli Common Reporting is in TCR_component_dir logs upgrade repository Id properties If you upgraded from Tivoli Common Reporting version 1 3 or 2 1 configure LDAP in Tivoli Integrated Portal only Create new schedules for your reports Report schedules that are created for versions of Tivoli Common Reporting versions earlier than 2 1 are not mapped to Cognos scheduler N 3 iguring JDBC data sources using ge 97 the same way as you configured them for the Tivoli Common Reporting version that you previously used JNDI data sources are not transferred during the upgrade process 4 Verify that all your report images have been moved 5 Log in to the Tivoli Integrated Portal console and check whether all your reports appear in the Common Reporting gt Connection view Try to to check whether it is working properly 6 If you decided to import report snapshots ensure that the snapshot appears as Run history of the report for which it was generated 7 Disable anonymous access from VMMProvider
80. d password for a Tivoli Common Reporting administrator e Run the following commands 1 AdminApp uninstall IBM Cognos 8 2 AdminConfig save 6 Install IBM Cognos 8 Servlet Gateway to WebSphere Application Server by running the following commands in the wsadmin console a AdminApp install lt directory_with_ServletGateway ear gt ServletGateway ear MapWebModToVH default_host MapRolesToUsers cps_user No Yes Note MIN When specifying the lt directory_with_ServletGateway ear gt ServletGateway ear directory change all slashes to forward ones If there is a space character in the path escape it by typing in or placing it in double quotation marks b AdminConfig save Exit the console by typing in quit 7 Modify the class loader function by a Navigating to the following directory E 7CR_component_dir conf e and ML TCR_component_dir conf and replacing the lines Chapter 2 Installing 37 38 User Guide 10 T1 12 strApplicationName sys argv 0 strClassloaderMode sys argv 1 with the following ones selectedScenario sys argv 0 strClassloaderMode sys argv 1 if selectedScenario gateway strApplicationName IBM Cognos 8 Servlet Gateway else strApplicationName IBM Cognos 8 as well as appending AdminConfig save at the end of the modifyClassloader py file b Navigating to the following directory MOOS 7 P _install_dir profiles TIPProfile bin E and MOUS
81. der that modules are deployed removed or redeployed on each of the nodes While in maintenance mode any attempts to make changes in the portal that affect the global repositories are prevented and an error message is returned The only changes to global repositories that are allowed are changes to a user s personal portlet preferences Any changes outside the control of the portal for example a form submission in a portlet to a remote application are processed normally The following operations are also not synchronized within the cluster and must be performed manually at each node These updates do not place the cluster in maintenance mode e Deploying redeploying and removing wires and transformations e Customization changes to the console user interface for example custom images or style sheets using consoleProperties xml To reduce the chance that users could establish sessions with nodes that have different wire and transformation definitions or user interface customizations schedule these changes to coincide with console module deployments Requirements The following requirements must be met before load balancing can be enabled e Lightweight Directory Access Protocol LDAP must be installed and configured as the user repository for each node in the cluster For information about which LDAP servers you can use see List of supported software for WebSphere Application Server V7 0 See Configuring LDAP user registries fo
82. distributions of the product components Single computer Copyright IBM Corp 2007 2011 1 System A Tivoli Common Reporting server Tivoli Common Reporting console Cognos based Tivoli Common Reporting engine Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting Distributed environment 2 User Guide System A Tivoli Common Reporting server Tivoli Common Reporting console Cognos gateway Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting Integration with an existing Cognos instance SystemA Tivoli Common Reporting server Tivoli Common Reporting console Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting System B Tivoli Common Reporting Cognos Application Tier server Cognos based Tivoli Common Reporting engine Cognos Content Store System B Cognos Chapter 1 Overview 3 Note Tivoli Common Reporting version 2 1 1 is based on Cognos Business Intelligence Reporting version 8 4 1 Fix Pack 3 Table 1 Software components Core components Tivoli Common Reporting Server The application server is a J2EE lightweight implementation of the embedded WebSphere Application Server It provides a single sign on service based on the WebSphere se
83. dule reports go to IBM Cognos Connection User Guide Schedule Management Performing ad hoc reporting Create reports ad hoc by using simple queries and formatting Before you begin To perform ad hoc reporting you have to have some report packages imported 102 User Guide Procedure 1 Log in to the Tivoli Common Reporting interface and go to Common Reporting 2 In the Work with reports window on the right choose the Query Studio from the Launch drop down list 3 Select a package to work with This opens a New window where you can create the new report 4 From the navigation on the left drag and drop data items you want to include in your report Tip Change the appearance of the data by using the menu icons at the top 5 Once your data and appearance is edited save the report by specifying a Name and optionally a Description and a Screen tip Results You have now created your ad hoc report What to do next Learn more about authoring the reports in the I BM Cognos Query Studio User Guide Web based report authoring Create reports in a Web based tool that professional report authors use to build sophisticated multiple page multiple query reports against multiple databases You can create any reports that your company requires such as invoices statements and weekly sales and inventory reports Procedure 1 Log in to the Tivoli Common Reporting interface and go to Common Reporting 2 In the Work w
84. e During Cognos reports import the resourceBase designBase and resourceDir parameters are ignored You can import a single Cognos report from an xml file using the design parameter Note 1 Authentication by user userID and password password is required in all cases 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider Arguments bulk pkgFile The local path and file name including zip extension of the report package file to be imported design designPath The local path of the design file to be imported help Displays syntax and usage information of a command flag The following parameters are optional reportSetBase rsBase A search path to the package where a report is to be imported resourceBase resourceBase An optional base name for any resource directories imported from a report package The base name for a resource directory is used as the name of the top level parent directory for the resources in the package Use this option to avoid naming conflicts when importing resources in a package that have the same names and locations as existing resources in the data store designBase designBase An optional base name for any report designs imported from a report package The base name for a report design is used as the top level location for the designs in the package Use this option to avoid naming conflicts when importing r
85. e ODBC utility launched from Administrative Tools is the 64 bit version Tivoli Common Reporting is a 32 bit application so it does not see the 64 bit ODBC data sources Resolving the problem Use the 32 bit version of the Windows ODBC utility to define the data sources The 32 bit version of the Odbcad32 exe file is located in the system_drive Windows SysWoW32 folder For more information see http support microsoft com kb 942976 When starting Framework Manager you are prompted to supply your login details twice Symptoms When you initiate Framework Manager you are required to provide your login credentials When you have done that a Framework Manager login panel is displayed with the following text Provide valid credentials The user or password your provided is not valid Causes Framework Manager requires you to login twice because it does not support single sign on Resolving the problem Ignore the message about invalid user or password and provide your login credentials again Drill through definitions in BIRT reports do not work Symptoms From time to time drill throughs in BIRT might not be working Resolving the problem Restart the Tivoli Common Reporting server 1 Stop the server by navigating to the following directory in the command line interface Chapter 6 Troubleshooting and support 115 MEN 7CR_component_dir bin and running the stopTCRserver bat command TCR_component_dir bin and runni
86. e is used by the new instance of Tivoli Common Reporting What to do next Te 2 3 4 5 If you want to use LDAP as your user repository configure it again LDAP configuration is not automatically transferred to the upgraded instance of Tivoli Common Reporting A file with LDAP information exported from the previous version of Tivoli Common Reporting is in TCR_component_dir logs upgrade repository Id properties If you upgraded from Tivoli Common Reporting version 1 3 or 2 1 configure LDAP in Tivoli Integrated Portal only Create new schedules for your reports Report schedules that are created for versions of Tivoli Common Reporting versions earlier than 2 1 are not mapped to Cognos scheduler Configuring JDBC data sources using JNDI on page 97 the same way as you configured them for the Tivoli Common Reporting version that you previously used JNDI data sources are not transferred during the upgrade process Verify that all your report images have been moved Log in to the Tivoli Integrated Portal console and check whether all your reports appear in the Common Reporting gt Connection view Try to nee check whether it is working properly Chapter 3 Upgrading 53 6 If you decided to import report snapshots ensure that the snapshot appears as Run history of the report for which it was generated 7 Disable anonymous access from VMMProvider a Open the IBM Cognos configuration by running MXI
87. e license agreement Select Install new instance of Tivoli Common Reporting as the installation mode On the Installation scenarios page select Integrate your existing Cognos BI infrastructure Click Next Choose the installation directory and click Next Apart from the installation directory two new directories are created e C IBM tivoli tipv2 containing Tivoli Integrated Portal and e C IBM tivoli tipv2Components TCRComponent containing among others the component and scripts The directories are created because of Tivoli Integrated Portal 2 2 requirements Create user credentials for Tivoli Integrated Portal by choosing user ID and password and specify the port number for IBM Cognos content database Up to 15 ports can be used whose numbers begin with the port number that you provide and increase Provide a URL to the existing Cognos engine that you want to integrate and click Next After confirming the installation details click Install Results You have now completed the full installation procedure and can start using the reporting solution on single system by logging in to the reporting interface Chapter 2 Installing 33 Installing Tivoli Common Reporting into an existing Tivoli Integrated Portal instance If you already have a product based on Tivoli Integrated Portal 2 1 in your infrastructure you can install Tivoli Common Reporting components into it so that the two products are in the same Tivoli Inte
88. e navigation pane click Settings gt Websphere Admin Console and click Launch Websphere Admin Console b In the WebSphere Application Server administrative console select Settings gt Global security c In the Global security page from the Authentication area click the LTPA link d Under Cross cell single sign on specify a key file and provide a filename and password for the file that will contain the exported LTPA keys e Click Export keys Reconfigure any applications that use Tivoli Integrated Portal Server LTPA keys To reconfigure the Tivoli SSO service with the updated LTPA keys run this script profiles TIPProfile bin setAuthnSvcLTPAKeys jacl a Change directory to profiles TIPProfile bin b Start the Tivoli Integrated Portal Server e startServer bat e startServer sh c Run the following command wsadmin username tipadmin password tipadmin_password f setAuthnSvcLTPAKeys jacl exported_key_path key password Where exported_key_path is name and full path to the key file that was exported key_password is the password that was used to export the key For SSO enable FIPS for any other application servers then import the updated LTPA keys from the first server into these servers a Copy the LTPA key file from step 4 above to another application server computer b In the navigation pane click Settings gt Websphere Admin Console and click Launch Websphere Admin Console c In the WebSphere Appl
89. e upgrade by following steps 1 to 4 in Tivoli Common Reporting installation instructions 2 Select to Upgrade the existing Tivoli Common Reporting instance 3 Choose Integrate the existing Cognos BI infrastructure as the upgrade scenario 4 Select the installation directory and the existing instance of Tivoli Common Reporting to be upgraded Chapter 3 Upgrading 57 5 Specify the administrative user credentials that you used to log in to the previous version of Tivoli Integrated Portal and the port number that you want to use The port number must be different than the one you used for installation of the previous version of Tivoli Common Reporting 6 Provide the URL to the existing Cognos instance 7 On the IBM Cognos Content Database panel provide the port number for IBM Cognos Content database The default port number is 1527 8 Confirm your choices The upgrade runs in the background Results You upgraded to Tivoli Common Reporting version 2 1 1 The Cognos instance was not changed and Cognos configuration was moved What to do next 1 If you want to use LDAP as your user repository configure it again LDAP configuration is not automatically transferred to the upgraded instance of Tivoli Common Reporting If you upgraded from Tivoli Common Reporting version 1 3 it is enough to configure LDAP in Tivoli Integrated Portal only 2 Create new schedules for your reports Report schedules created for previous versions
90. e using a package Finish the upgrade procedure by upgrading the Tivoli Common Reporting user interface Procedure 1 Create the package with Tivoli Common Reporting data a From the Tivoli Common Reporting 2 1 1 installation media extract the TCRInstaller C0I PackageSteps TCRCore FILES tcr TCRPlugins zip to the TCR_install_dir of your existing Tivoli Common Reporting instance prior to version 2 1 1 Important On non Windows platforms run the following command to add run permissions for all upgrade scripts chmod x existing_TCR_install_dir profiles TIPProfile upgrade bin sh b Run the following command existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade bat username username password password profuctId TCR a mo existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade sh username username password password profuctId TCR The package is created in the existing_TCR_install_dir upgrade data upgradeData zip folder 2 Repeat steps 1 to 8 in Upgrading using a package in single compute scenario on page 51 3 When the user interface has been updated copy the package to the reporting engine What to do next You must manually move the upgrade package from the user interface to the reporting engine that you previously upgraded The post upgrade panel informs you where a package with all the data was stored TCR_ui_install_dir profiles TIPProfile upgrade data upgradeData zip Make a
91. earching for matching report sets reports Specifies that you want to modify the properties of the data sources associated with reports that match the specified search criteria setDataSource pl p2 p3 A list of new data source property values separated by spaces Each property value must be specified using the following format property value If the value contains spaces enclose the property in double quotation marks property spaced value Each property must be one of the following e name e displayName e comments e odaDriverClass e odaURL e odaUser e odaPassword e odaJndiName Chapter 7 Reference 137 Examples This example changes the odaDriverClass odaURL odaUser and odaPassword properties of the data source in the ITM Top Resources by Utilization Summary report tremd sh user tipadmin password tipadmin modify datasources reports reportname content package name Tivoli Products folder name ITM 6 2 Reports folder name Utilization report name ITM Top Resources by Utilization Summary setdatasource odaDriverClass com ibm db2 jcc DB2Driver odaURL jdbc db2 9 167 29 78 60000 WAREHOUS currentSchema ITMUSER odaUser db2instl odaPassword tcrl123test content package name Tivoli Products folder name ITM 6 2 Reports folder name Utilization report name ITM Top Resources by Utilization Summary is the report that will be used as the base for changing the JDBC
92. eceives a token which is stored for a given session When the LTPA token has been received and the user tries to access the server in the same security domain the authentication is automatic and the user is not prompted for a name and password if the browsing session was not terminated IBM Tivoli Common Reporting is available from the enhanced WebSphere Application Server This is why a client requesting that application can be required to perform multiple logons when accessing other secure applications such as advanced reporting Each log on is likely to require different logon identities Chapter 1 Overview 7 8 User Guide Chapter 2 Installing A complete Tivoli Common Reporting installation comprises multiple components Before installing one or more of these components you must understand them and the installation process Hardware and software requirements Tivoli Common Reporting is available on a range of operating systems and supports several browser types Table 2 Hardware and software requirements Hardware requirements e Main memory 2 GB e Processor speed for best performance processor speeds must be at least 1 GHz for RISC architectures and 2 GHz for Intel architectures Choosing faster processors should result in improved response time greater throughput and lower processor utilization e Disk storage Note The optional separately installed IBM Cognos 8 Business Intelligence Modeli
93. ect will be deleted if the current user has write permission for the selected object the parent of the selected object and every descendant of the selected object help Displays syntax and usage information of a command flag recursive Deletes an object together with its child objects searchPath cognosSearchPath The search path to the object that you want to delete Examples This example deletes the Test Reports folder and all its subfolders and reports tcrmd bat user tipadmin password tipadmin delete searchPath content package name Tivoli Products folder name Test Reports recursive trcmd distribute 132 User Guide The distribute command flag for the tremd command distributes a formatted report to a specified location on the server file system You can use this command for both BIRT and Cognos reports Syntax tremd distribute report cognosSearchPath location publishLocation parameters p1 p2 p3 format format locale locale imageDir imagePath baselmageURL URL help Note 1 Authentication with user userID and password password is required 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider Arguments location publishLocation The fully qualified path to the directory where the formatted report is to be saved help Displays syntax and usage information of a command flag report repo
94. ee the list of ISO codes for languages or to search by code or language go tolhttp www loc gov standards iso639 2 langhome html Find the 2 character ISO 639 1 code for your language validateParams true When set to its default value true enables checking of default report parameters When set to false requires you to specify the parameters that a report will use in detail for example date format report cognosSearchPath The unique search path of the report you want to run Restriction The report chosen for conversion has to be a BIRT report If you choose a Cognos report the conversion will be aborted and you will receive an error message help Displays syntax and usage information of a command flag There is an optional parameter available This is the following package cognosSearchPath This parameter allows you to choose the location where the converted report is saved different from the original one The package name specified must exist in Cognos Examples e This example converts a BIRT report named IT Finances trcmd user tipadmin password your password namespace VMMProvider convert report content p e This example converts a BIRT report named IT Finances and places it in a package named Business Plan trcmd user tipadmin password your password namespace VMMProvider convert report content package name Sales and Retailers report name IT Finances package content package name Busi
95. enable it oe eT A Uninstalling You can uninstall the report components either from a GUI or in silent mode It is also possible to remove components manually for example if the uninstallation program was accidentally deleted or not completely installed Remember Run the uninstallation procedure on each machine you have installed the program components on Uninstalling using the uninstallation wizard 40 User Guide The uninstallation program guides you through the uninstallation procedure in graphical user interface Procedure 1 From the program directory MXIT Go to Start gt All Programs gt Tivoli Common Reporting 2 1 1 and choose the Uninstall option and MMH CR product_dir _uninst TIPInstal121 run the uninstall sh file Important If you have installed Tivoli Common Reporting in silent mode you need to add the i parameter with the gui argument to invoke the installer in GUI mode Tivoli Common Reporting uninstaller is launched 2 Read the information and click Next 3 Type in a password for the administrative user created upon installation and click Uninstall Tip You do not need to provide this information if you are uninstalling the Cognos based Tivoli Common Reporting engine component Also you will not be asked for password if WebSphere Application Server has been stopped If you forgot your password you can kill WebSphere Application Server process first then run the uninstallation You will
96. enter Tip You are prompted for user ID and password when accessing the console from the Tivoli Integrated Portal 2 Expand the Reporting section click the Common Reporting section and verify that the view in the right window opens up a new portlet 3 Run the sample overview report that is provided with the reporting tool and verify that it only displays information about this particular report Post installation tasks Refer to this section to find out how you can modify your existing Tivoli Common Reporting installation Migrating to a distributed environment Migrate a single computer installation to a distributed environment First you need to install the Cognos based Tivoli Common Reporting engine then you have to modify the existing single computer installation Note Paths given in the instruction are default path values from the installation procedure Procedure Install the Cognos based Tivoli Common Reporting engine 2 Export data from the existing Tivoli Common Reporting instance 3 Modify single computer installation 4 Import data Exporting data from Tivoli Common Reporting During the migration from single to distributed installation you will need to export all data from the existing Tivoli Common Reporting instance to preserve them Chapter 2 Installing 35 36 User Guide Procedure 1 3 Export the complete Cognos Content Store from Web user interface a Select Launch gt
97. eport designs in a package that have the same names and locations as existing designs in the data store resourceDir resourcePath The path in the data store for imported resources Examples e This example imports a BIRT package named avail_skills zip with its resource directory imported from C download sth report trcmd import bulk C download sth report avail_skills zip reportSetBase myReportSetBase resourceBase myResourceBase designBase myDesignBase user tipadmin password admin tremd list 134 User Guide The list command flag for the tremd command lists available items in the data store or shows detailed information about a specific item You can use it for both BIRT and Cognos reports Syntax Use this syntax to list all available folders and packages also the hidden ones tremd list reportSets showHidden help Use this syntax to list reports folders or packages associated with a specific folder or a package tremd list reportSet congnosSearchPath reportSets reports help Use this syntax to list all available reports trcmd list reports help Use this syntax to display detailed information about a specific report tremd list report cognosSearchPath help Use this syntax to display authorizations to reports or packages for specified users tremd list authorizations entity cognosSearchPath help Use this syntax to list the data sources defined in Content Store tremd list dataSo
98. epository gather the following LDAP server information Distributed installation Tip If you do not have access to the LDAP information at the time of the installation you can configure it after the installation completion e Server host name e Server port number e Bind distinguished name e Bind password e Distinguished name of a base entry e PersonAccount entity type e Base entity for PersonAccount e Group entity type e Base entry for group e OrgContainer entity type e Base entry for OrgContainer Integrating existing Cognos BI If you choose to configure the LDAP user infrastructure repository gather the information shown in the preceding row of this table e You will also require the URL to the existing Cognos engine you want to integrate e Make sure that you have a range of 14 port numbers free starting with the port number you enter during an interactive installation wizard GUI or console mode Note The default port number for the installation program which starts the sequence is 16310 However in the silent installation mode you can manually assign ports for each application server component Therefore the server installed in a silent mode may not use 14 subsequent port numbers In that case make sure all the ports selected during silent installation are free Additionally port 1527 is used by the IBM Cognos 8 application and port 9300 is used during a distributed installation on t
99. epository such as o ibm c us b The base entry indicates the starting point for searches in this LDAP directory server such as o ibm c us c 4 Click Global security and then click set as current button to mark the federated repository as the current realm The Mark Federated repository must be set as current 5 Apply and save the changes 6 Restart the server to enable the configuration 7 Verify that the federated repository is correctly configured a In the navigation tree click Users and Groups gt Manage Users b Select User ID from the Search by list c Click Search to search Users in federated repository This list includes users from both LDAP and the local file registry On the Tivoli Common Reporting Server LDAP users are queried only by the userid attribute When users are imported into LDAP using an LDIF file an auxiliary class of type eperson and uid attribute is added to the LDAP user ID Note this is to be done only if you want to search the LDAP repository using VMM from the server 8 If you want to create a user in LDAP click Users and Groups gt Manage Users then click Create and continue as for the previous step Enter user ID first name last name email and password 9 For the changes to take effect save stop and restart the Tivoli Common Reporting Server What to do next If you intend to enable single sign on SSO so that users can log in once and then traverse to other applications without hav
100. er 1 Open the IBM Cognos configuration by running QS Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration EEC Ls IP install_dir tipv2 products tcr Cognos c8 bin tcr_cogconfig sh 2 Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to True 3 Save your configuration and restart the Tivoli Common Reporting server CAUTION Enabling anonymous access makes Cognos open for anonymous connections without any authentication It is recommended that you upgrade in maintenance mode and secure access to Cognos with a firewall Chapter 3 Upgrading 51 52 User Guide About this task Perform this task as an administrative user Procedure 1 Create the package with Tivoli Common Reporting data a Copy the following zip files from Tivoli Common Reporting 2 1 1 to the computer where previous version of Tivoli Common Reporting is installed e TCRInstaller COI PackageSteps TIPCore FILES tipUpgradeUtil zip e TCRInstaller COI PackageSteps TCRCore FILES tcr TCRPlugins zip b Extract the files you have just copied e If you are upgrading from version 2 1 1 3 or 1 2 extract TCRInstaller COI PackageSteps TIPCore FILES tipUpgradeUtil zip and TCRInstaller COI PackageSteps TCRCore FILES tcr TCRPlugins zip to the TCR_install_dir profiles TIPProfile folder of your existing Tivoli Common Reporting instance prior to version 2 1
101. erate F IS access to key reporting information Tivoli Common Reporting provides the following advantages for the users Simplified interaction Simplified interfaces and interactions for report writers to create customize and publish reports which let you build reports faster and easier Cross product report linking Extend the capability of cross product report linkage for seamless flow between related reports of various Tivoli products On demand reporting Enable report users to create and save ad hoc reports without the need for professional report writer s involvement Tivoli Common Reporting 2 1 1 is based on Cognos 8 Business Intelligence Reporting version 8 4 1 Fix Pack 3 The following Cognos components are available with Tivoli Common Reporting e Framework Manager a modeling tool that allows you to create data models e Query Studio a reporting tool for creating simple queries and reports e Report Studio a web based tool for creating sophisticated reports against multiple databases e Cognos Connection an application where you can see all your report and manage them Technical overview IBM Tivoli Common Reporting consists of data stores reporting engines their corresponding web user interfaces displayed in Tivoli Integrated Portal and a command line interface Tivoli Common Reporting provides a flexible structure that can be adapted for load balancing The following diagrams illustrate the possible
102. erface is an optional component It does not appear on Windows where the Win32 API always contains the graphical user interface API Resolving the problem Install the X system Below is a list of packages that help for SUSE Linux for other distributions similar packages are available Linux SLES 9 156 46 78 10 44 root usr lib rpm qa grep xorg e xorg x11 server 6 9 0 50 58 e xorg x11 fonts 75dpi 6 9 0 50 58 e xorg x11 6 9 0 50 58 Chapter 6 Troubleshooting and support 119 e xorg x11 fonts 100dpi 6 9 0 50 58 e xorg xl11 Xvnc 6 9 0 50 58 e xorg x11 driver video radeon 6 6 3 0 19 e xorg x1l server g x 6 9 0 50 58 e xorg x11 libs 6 9 0 50 58 e xorg x11 driver video nvidia 6 9 0 46 51 e xorg x11 fonts scalable 6 9 0 50 58 e xorg x11 libs 32bit 6 9 0 50 58 e xorg x11 Xnest 6 9 0 50 58 e xorg x11 driver video 6 9 0 46 51 Cognos Configuration does not open Symptoms Launching Cognos Configuration fails Causes This happens when the JAVA_HOME environment variable points to a different Java than the Cognos Java Resolving the problem To resolve the problem you can e Follow the steps in IBM Cognos information center to update your Java environment e Open the IBM Cognos Configuration by running QUITS CR _component_dir cognos bin tcr_cogconfig bat MOL TCR_component_dir cognos bin tcr_cogconfig sh The script sets the correct Java Cannot open the sample overview report Symptoms After installin
103. ertificates leave the default settings and click Extract Supply the path and name of the file for example root defaultCert arm arm is the recommended file extension Leave the encoding settings as Base64 and click OK In the httpd conf file find the WebSpherePluginConfig parameter This parameter shows you where the plugin cfg xml file is located for example WebSpherePluginConfig opt IBM HTTPServer Plugins1 config webserverl plugin cfg xml Open the plugin cfg xml file and find the keyring phrase Its value shows you the location of the kdb file for example lt Property Name keyring Value opt IBM HTTPServer Plugins1 config webserverl plugin key kdb gt Note this location for later use Start the ikeyman directory by issuing cd opt IBM HTTPServer bin and ikeyman You need an X Window server to perform this step j Select Key Database File gt Open and then select a key database of the CMS type k Specify the kdb file name and location for example plugin key kdb opt 1BM HTTPServer Plugins1 config webserverl plugin key kdb and confirm it Enter the password The default WebSphere Application Server password is WebAS m Select Signer Certificates from the Personal Certificates expandable list and click Add n Browse to the arm file that you exported Select it click Open and then OK Supply the name if prompted o Select Key Database File gt Save As and save it to the original locatio
104. es for Tivoli Common Reporting Common Reporting For more information about using the product or for technical assistance visit the This site provides information on support professional services and education Take a look at the Cognos 8 4 1 information center at http publib boulder ibm com infocenter c8bi v8r4m0 index jsp Getting started with reports Perform the necessary actions to use the reporting options in Tivoli Integrated Portal as the common integrated reporting platform for products across the Tivoli portfolio It enables you to link multiple reports across various Tivoli products to simplify the report navigation and accelerate access to key reporting information Before you begin 1 Install Tivoli Common Reporting 2 Install Framework Manager to be able to create your own data models 3 Configure the Framework Manager connection to Tivoli Common Reporting About this task After you have installed Tivoli Common Reporting prepare your report packages to be able to generate publish and edit your reports Procedure 1 If you have the report packages ready import the report packages e Import Cognos report packages e Import BIRT report packages a Create or update your data sources e For Cognos based report packages configure the database connection e For BIRT based report packages ensure that the report package data sources point to the existing data sources Use the
105. es that are necessary in this scenario have been left uncommented and with example values i a a A EE EEE EEP EEE EEEE EEEE Set Silent License Acceptance To accept the license agreement change the value to true example LICENSE_ACCEPTED true If the LICENSE_ACCEPTED has a value other than true the installation will exit By removing the sign before the LICENSE_ACCEPTED false string and changing false to true you mark that you agree to the Tivoli Common Reporting TCR_VERSION license agreement LICENSE _ACCEPTED false Choose the preferred installation language For default leave commented Available values are cs de en es fr it ja ko pl pt pt_BR ru tr zh zh_CN zh_TW INSTALLATION_LANGUAGE en Hews Install into existing WebSphere Application Server Specify decision to install Tivoli Common Reporting into an existing WebSphere Application Server Note that If this property is set to true then the following TCR_INSTALLATION DIRECTORY property must be correctly set to the existing WebSphere Application Server location aka WAS HOME INSTALL_INTO_EXISTING_WAS false Choose Installation Folder Silent installation provide a fully qualified path example TCR_INSTALLATION DIRECTORY C IBM tivoli tcr Note that Backslash is cons
106. eted the following tasks e Ensure that you know the administrative user login and password e If you are upgrading from Tivoli Common Reporting version 1 3 or 2 1 ensure that all your report images are in the TCR_install_dir profiles TIPProfile instal ledApps TIPCel1 IBM Cognos 8 ear p2pd war tivoli directory because only this directory is moved over to version 2 1 1 e If you are upgrading from version 1 3 and you have LDAP configured to connect directly with Cognos enable anonymous access from VMMProvider 1 Open the IBM Cognos configuration by running E Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration EET 7 IP_install_dir tipv2 products tcr Cognos c8 bin tcr_cogconfig sh 2 Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to True 3 Save your configuration and restart the Tivoli Common Reporting server CAUTION Enabling anonymous access makes Cognos open for anonymous connections without any authentication It is recommended that you upgrade in maintenance mode and secure access to Cognos with a firewall About this task When upgrading from Tivoli Common Reporting version 2 1 Tivoli Integrated Portal is not upgraded You can manually upgrade Tivoli Integrated Portal to version 2 2 Procedure 1 w Start the upgrade by following steps 1 to 4 in Tivoli Common Reporting installation ins
107. f the existing IBM Cognos 8 may already be set to a specified user repository By performing these instructions you can modify it 61 Copyright IBM Corp 2007 2011 Installation scenario Configuration path Upgrade Upgrade of single computer installation 1 Configure the Tivoli Common Reporting 2 Recommended for large user repositories Configure the engine Upgrade to a distributed installation e On the computer with Tivoli Common Reporting user interface installed configure the Tivoli Common Reporting e On the computer withCognos based Tivoli Common Reporting engine installed configure the reporting engine Configuring Tivoli Common Reporting Server Configure the Tivoli Common Reporting Server to communicate with an external repository such as Lightweight Directory Access Protocol LDAP or Microsoft 62 User Guide Active Directory Before you begin If you want all LDAP communications to be encrypted you can specify SSL communications If so be sure to import the LDAP signer s certificate into the trust store of the Tivoli Common Reporting Server before starting this task Procedure 1 Log in as an administrative user 2 If you need to add a new LDAP repository open the Tivoli Integrated Portal administrative console by direct link https hostname port_number ibm console secure securelogon do or from Tivoli Common Reporting user interface https hos
108. face and the reporting engine must both be either 32 bit or 64 bit Installing the Cognos based Tivoli Common Reporting engine Perform the first step in a distributed installation install the Cognos based Tivoli Common Reporting engine component Procedure 1 Insert the product DVD or if you are installing from an image open the directory that contains the files that you have previously extracted 2 Start the installation launchpad MMI launchpad exe and E launchpad sh 3 Read the installation information and click Install Tivoli Common Reporting Tip At any time of running the installation you can go back to the launchpad to access the on line documentation or the PDF version of the Installation Guide 4 Choose your installation language read the Welcome page and accept the terms of the license agreement 5 Select Install new instance of Tivoli Common Reporting as the installation mode On the Scenario Selection page select the Distributed installation Select to Install the Tivoli Common Reporting engine Choose the installation directory for the reporting engine o oND Provide the port number for IBM Cognos content database Up to 15 ports can be used whose numbers begin with the port number that you provide and increase Note Depending on the scenario additional ports belonging to tomcat will be used by the Cognos based Tivoli Common Reporting engine 10 After confirming the installation details c
109. g report name Reporting Overview trcmd bat user tipadmin password tipadmin access grant permissions write setPolicy entity content package name Common Reporting report name Reporting Overview accessIdentity CAMID VMMProvider tester e This example lists authorizations that the user tipadmin has to the object content package name Packagel tremd bat list authorizations entity content package name Packagel user tipadmin password tipadmin trcmd convert The convert command flag for the tremd command allows you to convert existing BIRT reports into Cognos draft reports A draft report includes some elements of Chapter 7 Reference 127 128 User Guide BIRT reports such as layout and style and is used as a basis for the creation of a fully fledged Cognos report It cannot be used for Cognos reports Syntax trcmd user userID password password namespace authentication namespace convert report cognosSearchPath parameters p1 p2 p3 imagesDir images_directory help Note 1 Authentication with user userID and password password is required 2 If you have configured more than one user repository specify namespace value By default namespace points to VMMProvider 3 Before converting a BIRT report ensure that it has properly configured data sources and that it can be run without errors Restriction After the conversion a report may not run properly This is a norma
110. g Browser to open the default browser with the correct URL 2 On the Tivoli Integrated Portal login page log in with a user ID that has access to Tivoli Common Reporting Access is determined by user roles associated with user IDs This might be the user ID and password you specified during the installation process or a user ID and password provided to you by an administrator The Tivoli Integrated Portal navigation window opens Tip Only one logon is required when accessing the reporting interface The single sign on option is enabled between the two reporting options 3 In the navigation pane on the left side of the window click the plus sign beside Reporting to expand the tree 4 Choose Common Reporting to work with the enterprise reporting options Single sign on SSO Single sign on SSO is the ability of a user to log on once and access multiple applications without having to log on to each application separately It is multi server session based authentication that allows web application users to log on once to WebSphere Application Server and then access another application s WebSphere Application Server in the same DNS domain that is enabled for single signon without having to log in again The server is configured to use the Lightweight Third Party Authentication LTPA authentication When logging in the user is prompted for a name and password which can later be reused When the user is authenticated the browser r
111. g Tivoli Common Reporting when opening the sample overview report an error message appears and the report does not open Resolving the problem To resolve the problem 1 Locate the file WEB INF services reportservice xml 2 In the file locate the section that refers to async_wait_timeout_ms 3 Modify the setting to increase the timeout from the default 30 seconds to a larger setting for example 90 seconds 90000 ms 4 Save the file 5 Restart the IBM Cognos 8 service Error after running a sample overview report Symptoms 120 User Guide After running a sample overview report an error with the ID UDA SQL 0114 is displayed Causes This error is caused by a memory issue Resolving the problem See the IBM web page for most common solutions to this problem When trying to find users in user repository an error appears Symptoms If you have configured a large user repository and then you are trying to find users in this user repository a NullPointerException appears as a result Resolving the problem To resolve the problem 1 In the Tivoli Integrated Portal console select Launch gt Cognos Administration gt Configuration gt Dispatchers and Services Click the link to the dispatcher Click Set Properties to the Content Manger Service Select Settings In Advanced Settings select Edit to Environment Enter CM CMREQUEST_PERFALARM_THRESHOLD as the parameter Enter 3600000 as the value 3600000
112. grated Portal instance About this task You can use either the installation wizard or silent mode to install into an existing Tivoli Integrated Portal instance In silent mode the WAS_USER_NAME and WAS_PASSWORD are credentials that you use to log into the existing Tivoli Integrated Portal console MAINA To perform this task you must belong to the Administrators group or be an Administrator Procedure 1 Start the installation launchpad from the product DVD or the installation image MOXIE launchpad exe e launchpad sh 2 Read the installation information and click Install Tivoli Common Reporting 3 Choose the installation language read the Welcome page and accept the license agreement 4 On the Installation Mode pane select to Reuse the existing instance of Tivoli Integrated Portal 5 Choose the installation scenario 6 Select the installation directory and the location of the existing Tivoli Integrated Portal 7 Provide administrative user credentials that you use to log into Tivoli Integrated Portal console 8 Provide the port number for IBM Cognos content database 9 Read the summary panel and click Install Installing Framework Manager 34 User Guide Framework Manager is a modeling tool for creating and modifying business views of data The output of the Framework Manager is a package used for creating reports in Tivoli Common Reporting About this task Framework Manager is a Windows based
113. hat verify if the installation was successful by opening http hostname 80 in your Web browser 2 Secure IBM HTTP Server with SSL communications When you have done that open https hostname 443 in your Web browser to ensure that the configuration works properly 3 On a different computer jinstall Tivoli Integrated Portal and enable load 4 Create Web server on each of the computers in the load balancing configuration a Open the server xml file located in TIP_install_dir profiles TIPProfile config cel1s TIPCel1 nodes TIPNode servers server1 find the following section in the file applicationserver webcontainer WebContainer and add the following line in the components section lt properties xmi id WebContainer_12345678 name HttpSessionCloneld value 12345 required false gt Note Insert the properties element into the components element referring to WebContainer The value element must be different for each of the computers belonging to Tivoli Integrated Portal high availability cluster The id must be the same as the one in the components section b Copy the plugin key kdb and plugin key sth located in TIP_install_dir profiles TIPProfile config cells TIPCel1 nodes node_created_by_running_configurewebserverl sh_script servers webserver1 to the computer where you installed IBM HTTP Server c Restart the Tivoli Integrated Portal server Remember Repeat step 4 on each of the computers that belongs to Tiv
114. he following command to finish creating the package Windows _ TIP_install_dir profiles TIPProfile upgrade bin tcrUpgrade bat TIP_install_dir username username password password productld TCR MOOV 7IP_install_dir profiles TIPProfile upgrade bin tcrUpgrade sh TIP_install_dir username username password password productld TCR The package is created in TIP_install_dir profiles TIPProfile upgrade data upgradeData zip 2 Extract the package on the computer with Tivoli Common Reporting using a higher Tivoli Integrated Portal version by issuing the following command new_TIP_install_dir profiles TIPProfile upgrade bin upgrade bat username username password password productId TCR upgradeDataFile path_to_upgradeData zip i me new_TIP_install_dir profiles TIPProfile upgrade bin upgrade sh username username password password productId TCR upgradeDataFile path_to_upgradeData zip 3 Restart Tivoli Common Reporting Configuring Tivoli Common Reporting 2 1 1 to use Cognos installed on a separate computer 66 User Guide You can modify your Tivoli Common Reporting instance and enable it to use Cognos installed on a different computer Procedure 1 2 3 Import the data to the computer where Cognos is installed See IBM Cognos information center nformation center for details Exporting data from Tivoli Common Reporting Before you enable your Tivoli Common Reporting instance to use external Cognos
115. he reporting engine system Also the 9362 port is used for reporting component logging e If you are installing on a non Windows operating system ensure that the number of open files for processes is set to a value higher than 1024 If it is not perform the following steps to increase this value MOYO Change or add the nofiles XXXXX parameter in the etc security limits file or by using the chuser nofiles XXXXX user_id command SET MEME Run the following command ulimit n nnnn where nnnn is the wanted number of open files Chapter 2 Installing 15 Tip On Linux operating system you can configure the open file limits globally To do this open the etc security limits conf file and add the following line hard unfile 2048 Preinstallation Step 3 Preparing installation media IBM Tivoli Common Reporting includes installation media for the Cognos based Tivoli Common Reporting engine version 8 4 1 and prerequisite software There are two forms of installation media e Product disks e Installation images which licensed customers can download from the IBM Passport Advantage website For non Windows operating systems there are additional installation media either an installation image or a disk that include IBM Cognos 8 Business Intelligence Modeling 8 4 1 and IBM Cognos 8 Enhanced Encryption for OpenSLL For Windows operating systems the Cognos Modeling installer is located on the Tivoli Common Reporting image Pr
116. hecking the search path of a report on page 105 parameters pl p2 p3 A list of parameter values used for running the report separated by spaces These values override any default values specified in the report or report design Each parameter value must be specified using the following format param value If the value contains spaces enclose the parameter in double quotation marks param spaced value Each parameter must correspond to a valid parameter specified in the report design Note that multivalued parameters are supported for example parameters color blue color red There are four optional parameters available These are the following format format Specifies output format for example format HTML It is possible to specify multiple formats at one time for example format PDF HTML If format is not used the output format is PDF The supported formats are PDF HTML CSV XML XLS locale Specifies the language of the report for example locale en for English To see the list of ISO codes for languages or to search by code or language go to w loc gov standards iso639 2 langhome html Find the 2 character ISO 639 1 code for your language help Displays syntax and usage information of a command flag validateParams true When set to its default value true enables checking of default report parameters When set to false requires you to specify the parameters that a report will use in
117. hooting and support This section provides information to help you identify and resolve problems that might occur when using Tivoli Common Reporting Learn how to use log files to determine the problem Using log files for troubleshooting You can troubleshoot problems by enabling the collection of detailed log and trace information also within WebSphere Application Server About this task By default only Cognos 8 Business Intelligence Reporting errors are logged in the logs folder in the Cognos installation directory To enable more detailed tracing Procedure 1 Open the PogoLogkitConfig_FullDebug xml file from the following location e For the distributed environment the machine with the Cognos based Tivoli Common Reporting engine installed lt Cognos_install_dir gt webapps p2pd WEB INF e For the single computer installation TCR_install_dir profiles TIPProfile installedApps TIPCel1l Cognos 8 ear p2pd war WEB INF 2 Change the name of the file to PogoLogkitConfig xml and save it 3 Restart the Cognos to apply the changes Enabling detailed log and trace information You can troubleshoot problems by enabling the collection of detailed log and trace information About this task To enable detailed tracing Procedure 1 In the Tivoli Integrated Portal navigation panel click Settings gt WebSphere Admin Console 2 Select Troubleshooting gt Logs and trace 3 In the Logging and Tracing console module
118. i Integrated Portal and e install_dir tipv2Components TCRComponent containing among others the component and scripts Tip See jinstallation paths for more information This is caused by Tivoli Integrated Portal 2 2 requirements What to do next Check the installation log for any error messages generated by the installation Locate the TCR211Instal1lTrace00 1og and TCR211Instal1Message00 1og files in your home directory If you installed in a distributed environment configure the connection with the Engine Note During the installation procedure you have created an administrative user You can now create new users and user groups and grant them permissions to access various reporting resources and functions Before you do make sure you configure security permissions Response file for silent installation The installation media and images for Tivoli Common Reporting provide scenario specific response files that are tailored to include only options relevant to your installation type Fast path If you already know your installation scenario choose one of the scenario specific response files that include only options relevant to your installation type e For the single computer installation scenario use the TCR sample response embedded txt file e For the distributed installation scenario first use the TCR_sample_response_dispatcher txt file on the computer where you want to install the reporting engine and then the TCR_s
119. ication Server administrative console select Settings gt Global security d In the Global security page from the Authentication area click the LTPA link e Under Cross cell single sign on provide the filename and password from above for the file that contains the exported LTPA keys f Click Import keys Run the ConfigureCLI command tip_home_dir bin tipcli bat ConfigureCLI useFIPS true Chapter 4 Configuring 87 tip_home_dir bin tipcli sh ConfigureCLI useFIPS true Example The IBM SDK tip_home_dir java jre lib security java security file looks like this when IBMJCEFIPS is enabled security provider 1l com ibm crypto fips provider IBMJCEFIPS security provider 2 com ibm crypto provider IBMJCE security provider 3 com ibm jsse IBMJSSEProvider security provider 4 com ibm jsse2 IBMJSSEProvider2 security provider 5 com ibm security jgss IBMJGSSProvider security provider 6 com ibm security cert IBMCertPath security provider 7 com ibm crypto pkcs1l provider IBMPKCS11 security provider 8 com ibm security cmskeystore CMSProvider security provider 9 com ibm security jgss mech spnego IBMSPNEGO Configuring security permissions Increase the security settings for the Common Reporting user permissions By default all the users created including the one specified during the installation process have full administrative privileges You can modify them in Administration About this task To find out more about_Tivoli Co
120. idered to be a special character and needs to be escaped so use double backslashes when defining the path on Windows Silent uninstallation do not define the TCR_INSTALLATION DIRECTORY leave it commented out For reuse of an instance of Tivoli Common Reporting point to its existing installation location Examples For Windows platform C IBM tivoli tcr For UNIX platform opt IBM tivoli tcr TCR_INSTALLATION_DIRECTORY For the TIP specific part of the solution If INSTALL_INTO_EXISTING_WAS true the install folder must be the location of WebSphere Application Server such as TIP_INSTALLATION DIRECTORY C IBM WebSphere AppServer Hoss Examples For Windows platform C IBM tivoli tip For UNIX platform opt IBM tivoli tip TIP_INSTALLATION_DIRECTORY Chapter 2 Installing 31 32 User Guide For the reuse scenario If installing in a reuse scenario to simply add some additional components to already installed instance set this variable to true otherwise comment it out or set to false the default Pf wich Example REUSE_EXISTING_INSTALLATION true REUSE_EXISTING_INSTALLATION false poise Installation scenario Choose one of the following installation components configuration for this installation procedure
121. iding the Cognos port number The default port number is 9300 e urlprovider hostName host_name by providing the name of the Cognos host Here is an example of the modified script Tue Jul 06 11 40 05 CEST 2010 74 urlprovider local portNumber 16311 urlprovider contextRoot tarf urlprovider servletMapping servlet component url provider portNumber 9300 urlprovider protocol http urlprovider hostName nc046074 kraklab pl ibm com 6 Remove the cognos tools and data directories located in TCR_component_dir 7 Start the server as described in step 1 8 Clear the cookie files in your browser before running the application What to do next Import the data you have previously exported See IBM Cognos information center for details 68 User Guide Configuring clustered environment Use the installation and configuring to maximize the performance availability or capacity Tivoli Common Reporting Cognos Application Tier Server use the Connection interface to balance loads perform queries schedule jobs and render reports Content Manager stores all report specifications results packages folders and jobs in the content store About this task You can configure the Tivoli Common Reporting to be using clustered Tivoli Common Reporting Cognos Application Tier Server components To improve scalability in an environment in which there is typically a large volume of report requests to process you can install the Tivoli Com
122. ing QUITS TCR _component_dir integration reconfiguration rollbackReconfiguration bat M E TCR component_dir integration reconfiguration rollbackReconfiguration sh Important If you choose to roll back the changes Tivoli Common Reporting will work on the previous version of Tivoli Integrated Portal only It will not work on the upgraded Tivoli Integrated Portal instance 4 Restart Tivoli Common Reporting Migrating data to Tivoli Common Reporting installed on a higher Tivoli Integrated Portal version Configure Tivoli Common Reporting installed in distributed scenario to ensure it works properly on a higher version of Tivoli Integrated Portal About this task If you have two instances of Tivoli Common Reporting each installed on a different computer and using a different Tivoli Integrated Portal version you can migrate the data to the Tivoli Common Reporting instance using higher version of Tivoli Integrated Portal Chapter 4 Configuring 65 Procedure 1 Create a package with Tivoli Common Reporting data that you want to migrate a Extract the following files e TCRInstaller COI PackageSteps TIPCore FILES tipUpgradeUtil zip e TCRInstaller COI PackageSteps TCRCore FILES tcr TCRPlugins zip to TIP_install_dir profiles TIPProfile Important On non Windows platforms run the following command to add run permissions for all upgrade scripts chmod x TIP_install_dir profiles TIPProfile upgrade bin sh b Run t
123. ing to re authenticate check out the Tivoli Integrated Portal information on how to configure SSO Configuring Cognos based Tivoli Common Reporting engine Configure the engine to use the same user repository as the Tivoli Common Reporting Server with the user interface You can configure a Lightweight Directory Access Protocol LDAP server or Microsoft Active Directory This procedure is recommended for large user repositories About this task If you have installed your Tivoli Common Reporting instance on a single computer the Tivoli Common Reporting WMMProvider is used for LDAP by default and no additional LDAP configuration is required In the case of distributed installation you must configure LDAP on both computers Chapter 4 Configuring 63 Procedure 1 Open the IBM Cognos Configuration by running MEIN Start gt All Programs gt Tivoli Common Reporting 2 1 1 gt IBM Cognos Configuration e and E 7CR_component_dir cognos bin tcr_cogconfig sh 2 In the Explorer navigation on the left go to Security and right click Authentication section 3 Select New resource gt Namespace 4 Type in a name select the registry type from the drop down list and click OK New user registry is added to the list 5 Select the entry you just created and edit the fields required for configuration You have to provide different values depending on the type of_user registr selected For details on how to configure the user regist
124. ion to non IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk Copyright IBM Corp 2007 2011 141 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you Licensees of this program who wish to have information about it for the purpose of enabling i the exchange of information between independently created programs and other programs including this one and ii the mutual use of the information which has been exchanged should contact IBM Corporation 2Z4A 101 11400 Burnet Road Austin TX 79758 U S A Such information may be available subject to appropriate terms and conditions including in some cases payment of a fee The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement IBM International Program License Agreement or any equivalent agreement between us Information concerning non IBM products was obtained from the suppliers of those products their published announcements or other publicly available sources IBM has not tested those products and cannot confirm the accuracy of performance compatibility or any other claims related to non IBM products Que
125. is an hour you can increase this value if necessary Noo e o N 8 Confirm your settings and restart the service Connection with the datasource fails Symptoms When testing the connection with the datasource the DPR ERR 2002 error message is displayed The connection with the data source cannot be established Resolving the problem Remove the hard_drive work tools windk bin directory from the PATH environment variable Cannot save IBM Cognos Configuration settings Symptoms When trying to save IBM Cognos Configuration settings the following error message appears The cryptographic infromation cannot be encrypted Do you want to save the configuration in plain text Resolving the problem Chapter 6 Troubleshooting and support 121 Go to the Environment section and specify http localhost 16315 tarf servlet dispatch for the Gateway URI and Dispatcher URI for external applications The reporting engine fails to start with the SQLCODE 286 and SQLSTATE 42727 Symptoms After you have installed Tivoli Common Reporting and configured it to use DB2 as the content store database the reporting engine does not start with SQLCODE 286 and SQLSTATE 42727 Causes The DB2 user that was used for connecting to DB2 and creating all the databases is the only user that can access this table space An error occurs when a different used is used to connect to DB2 Resolving the problem Use the DB2 user name and password that you p
126. ith reports window on the right choose the Report Studio from the Launch drop down list This opens up the Report Studio a Web based application 3 Use the menu controls to create a new report or edit existing ones by formatting the layout and manipulating the data that appears in the report 4 Save your report and run it anytime you need to present on its underlying data What to do next Learn more about Web based report authoring in Report Studio Professional Authoring User Guide available on clicking F1 from the Report Studio Search path A search path is a basic expression in IBM Cognos that allows you to find objects It is one of the parameters that you need for performing operations on reports using commands You can use the search path to find one particular object or a set of objects within a folder using an asterisk as a wildcard character If you want to search for a report or a report package whose full name you do not know you can use the Chapter 5 Common Reporting 103 104 User Guide contains function to search for all reports or report packages that contain the specified expression The basic parameters of a search path are location steps that reflect the structure of catalogs on your computer Location steps are separated by a slash and can be followed by one or more predicate A predicate is an expression that filters an object set It is enclosed in square brackets All predicates within a location s
127. ject in Framework Manager and Framework Manager no longer works properly Resolving the problem Overwrite the bmt ini file that you can find in the configuration directory You can find a working copy of this file on other computer or from the backup Logon fails in Turkish locale Symptoms When installing Tivoli Common Reporting on an unsupported locale errors related to database connection may appear Causes This problem occurs if you have the following configuration e You have DB2 installed and when testing the connection from DB2 client the connection test succeeds e You have created a native connection to Cognos Business Intelligence e The locale settings for your server machine is Turkish You can verify this from shell by typing enx grep LANG The system output for Turkish is LANG tr_TR UTF 8 e When testing the connection to Cognos you get the error UDA SQL 0031 Unable to access the testDataSourceConnection database UDA SQL 0040 A syntax error was detected while parsing 0 in the file 1 UDA SQL 0038 S syntax error was detected while parsing the line number 574 near insert in the file opt IBM tivoli TIP21Components TCRComponent Cognos c8 bin cogdmd2 ini In this case Cognos uses a meta SQL code independent from the vendor and the problem is in the conversion process from Cognos SQL to native SQL At line 574 of the cogdmd2 ini file that maps each Cognos SQL command to native DB2 SQ
128. kage Upgrading with external Cognos Upgrading across scenarios Exporting data from Tivoli Common Reporting Migrating to a distributed environment Exporting data from previous instances manually Chapter 4 Configuring Configuring LDAP or Microsoft Active Diea Configuring Tivoli Common Reporting Server Configuring Cognos based Tivoli Common Reporting engine Configuring Tivoli Common Reporting fot Tivoli Integrated Portal future upgrade Configuring Tivoli Common Reporting for future upgrade of Tivoli Integrated Portal Migrating data to Tivoli Common Reporting installed on a higher Tivoli Integrated Portal version Configuring Tivoli Common Reporting 2 1 1 io use Cognos installed on a separate computer Exporting data from Tivoli Common Reporting Enabling Tivoli Common Reporting to use external Cognos Configuring clustered environment Configuring distributed installation for i ad balancing Load balancing Monitoring a load balancing cluster Configuring the reporting engine for load balancing Configuring user interface or load balancing Configuring IBM HTTP Server Configuring Framework Manager connection Configuring database connection Connecting to a DB2 database Connecting to an MS SQL database Connecting to an Oracle database Enabling Federal Information aa aia Standard Enabling FIPS Configuring security permissions Constraining access to BIRT reports ODBCINI variable co
129. l situation In such case complete the report conversion in Report Studio to be able to run it Arguments imagesDir images_directory Specifies the location where the images generated by a BIRT report will be copied during the conversion After the conversion you will need to copy the This parameter is optional for single box installation and when you run this command on the computer where the user interface is installed If you run this command on the computer where the reporting engine is installed this parameter is obligatory Important If you are running this command on the computer with the user interface you must copy the images to the computer where the reporting engine is installed if you want them to display in PDF reports parameters pl p2 p3 A list of parameter values used for running the report separated by spaces These values override any default values specified in the report or report design Each parameter value must be specified using the following format param value If the value contains spaces enclose the parameter in double quotation marks param spaced value Each parameter must correspond to a valid parameter specified in the report design Note that the multivalued parameters are supported for example parameters color blue color red There are two optional parameters available These are the following locale Specifies the language of the report for example locale en for English To s
130. ld and edit it by clicking EN The Value window opens d In the Value window click Add to add new URIs and click OK to save your changes Use host IP addresses or fully qualified computer names e In the IBM Cognos Configuration window save your configuration changes by going to File gt Save Restart IBM Cognos 8 on the reporting engines in your infrastructure a Open the Configuration b Go to the Environment gt IBM Cognos 8 service section and select IBM Cognos 8 c Select the Stop icon on the toolbar at the top d Start IBM Cognos 8 service on the reporting engine where the central database is configured e Start IBM Cognos 8 services on all other reporting engines Restart user interface a Run the stopTCRserver bin EMANA or stopTCRserver sh EMA script located in TCR_component_dir bin b Run the startTCRserver bin MMS or startTCRserver sh MEMI script located in TCR_component_dir bin 7 Copy the report images to the Tivoli Common Reporting server and user interface Important The same reports must be imported and configured for all the reporting engines in your infrastructure e In the case of BIRT reports you must import and configure them on every reporting engine If you are establishing load balancing in an existing environment you can copy the data catalog from an existing reporting engine instead of importing and configuring the reports again e In the case of Cognos reports you
131. lder or package showHi dden Use this flag to see hidden reports and report sets which by default are not shown in command line Examples e This example lists all available reports trcmd sh username tipadmin password tipadmin list reports e This example lists all child folders or packages of the Monitoring folder trcmd sh username tipadmin password tipadmin list reportSet content package name Sales and Retailers folder name Monitoring reportSets e This example displays detailed information about the IT Finances report tremd sh username tipadmin password tipadmin list report content package name Sales and Retailers folder name Documentation Reports report name IT Finances e This example lists authorization to the Reporting Overview report for user tipadmin tremd sh user tipadmin password tipadmin list authorizations entity content package name Common Reporting report name Reporting Overview tremd modify 136 User Guide The modify command flag for the tremd command allows you to configure Tivoli Common Reporting with your data source information so that the reports can use external data sources Use this command for BIRT reports only Syntax Use this syntax to modify data sources associated with one or more reports tremd modify dataSources reports reportName cognosSearchPath displayName displayNameQuery dataSource p1 p2 p3 caseSensitive setDatasour
132. le do call deleteRootIU j TCR_HOME GOTO endlocal EMPTYSET echo Deployment Engine not installed on the system exit b 1 endlocal exit b 0 endlocal bin sh TCR_HOME 1 arch uname s if echo arch grep SunOS then USERNAME usr ucb whoami else USERNAME whoami fi setenvemd HOME acsi_ USERNAME setenv sh First look in the users location if f setenvcmd then setenvemd else Then try the common location setenvcmd var ibm common acsi setenv sh export setenvcmd if f setenvcmd then setenvemd else echo Deployment Engine not installed on the system exit 3 fi fi tmpTCRfile tmp out Chapter 6 Troubleshooting and support 113 listIU sh v grep TCR grep v SoftwareIUTypeID grep RootIUTypeID grep TCR_HOME awk F while read line do deleteRootIU sh line TCR_HOME done lt tmpTCRfile rm tmpTCRfile echo Operation completed successfully exit 0 Run the script twice for the first time specifying TCR_install_dir as path and for the second tme specifying TCR_component_dir as path Troubleshooting Common Reporting Identify and resolve problems that might occur when you are using the product This section contains problems that might occur when working with your reports as well as Cognos related problems Browsing images does not work in Report Studio Symptoms When adding image to a report in Report Studio you cannot brow
133. le computer installation System A Tivoli Common Reporting server Tivoli Common Reporting console Cognos based Tivoli Common Reporting engine Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting Use this scenario for non scalable lightweight reporting with all the components installed on a single system You can use a file based user registry from embedded WebSphere Application Server a as user repository Scenario B Distributed installation System A System B Tivoli Common Reporting Tivoli Common Reporting server Cognos Application Tier server Cognos based Tivoli Common Reporting engine Tivoli Common Reporting console Cognos gateway E F Cognos Content Store Cognos based reporting portlet Tivoli Common Reporting console closeup Tivoli Integrated Portal Common Reporting 12 User Guide Use this configuration for scalable enterprise wide installation with the components dispatched on at least two machines In this installation scenario LDAP can be used as the user repository to enable single sign on e Two phase installation 1 The Cognos based Tivoli Common Reporting engine is installed first on at least one computer in the organization 2 Then the Tivoli Common Reporting user interface is installed anywhere users
134. lick Install Results You have now installed the Cognos based Tivoli Common Reporting engine on one computer View the Installation summary panel and make note of the Cognos based Tivoli Common Reporting engine URL as this information will be used during the second component installation What to do next Configure Lightweight Directory Access Protocollif you want to use it as your repository When you have done that proceed to install the Tivoli user interface Installing Tivoli Common Reporting user interface When you have installed the Tivoli Common Reporting engine proceed to install the Tivoli user interface to complete the distributed installation Chapter 2 Installing 19 About this task C IBM tivoli is the default installation directory Procedure 1 Repeat steps 1 through 6 of the reporting engine installation instructions on the computer where you want to install the Tivoli user interface and choose to Install the Tivoli Common Reporting user interface 2 Specify the installation directory and click Next Apart from the installation directory two new directories are created e C IBM tivoli tipv2 containing Tivoli Integrated Portal and e C IBM tivoli tipv2Components TCRComponent containing among others the component and scripts The directories are created because of Tivoli Integrated Portal 2 2 requirements 3 Create an administrative Tivoli Integrated Portal user by providing User ID and Password
135. lines that follow it Hatta Hee He HE Eee ee ee ee ae a a a a a a a a a a a a a a Hada HEH He He AAA ee ee ee ae ae a a a a a a a a a a a a E This response file example is profiled for the dispatcher installation scenario for further details on installation scenarios see TCR TCR_VERSION documentation Variables that are necessary in this scenario have been left uncommented and with example values i EEE A AREA AEA EEE EEE EEEE E EEEE Set Silent License Acceptance To accept the license agreement change the value to true example LICENSE_ACCEPTED true If the LICENSE ACCEPTED has a value other than true the installation will exit Prass By removing the sign before the LICENSE_ACCEPTED false string and changing false to true you mark that you agree to the Tivoli Common Reporting TCR_VERSION license agreement LICENSE_ACCEPTED false Choose the preferred installation language For default leave commented Available values are cs de en es fr it ja ko pl pt pt_BR ru tr zh zh_CN zh_TW INSTALLATION_LANGUAGE en AAA Choose Installation Folder Silent installation provide a fully qualified path example TCR_INSTALLATION DIRECTORY C IBM tivoli tcr Note that Backslash is considered to be a special character and needs to be escaped so use double backsl
136. mages to the following location TCR_install_dir profiles TIPProfile instal ledApps TIPCel1 IBM Cognos 8 ear p2pd war tivoli 2 For distributed installation a Copy the images to all computers with user interface installed to the following location TCR_install_dir profiles TIPProfile instal ledApps TIPCel1 IBM Cognos 8 Servlet Gateway ear ServletGateway war tivol i b Copy the images to all computers with Tivoli Common Reporting engine to the following location TCR_component_dir cognos webcontent tivoli E mailing reports E mail your reports to share them with the group of people who do not have access to the reporting portal Before you begin To be able to distribute reports you have to have a connection to a mail server specified To learn more about that see the IBM Cognos 8 Business Intelligence Installation and Configuration Guide Procedure 1 Once you have run your report you can distribute it by clicking Keep this version and choosing Email report from the drop down list 2 Set the e mail options and checking off whether you want to include a link to the report or attach it 3 Click OK to distribute the report What to do next Learn about other ways to distribute reports by looking at Connection User Guide Scheduling reports A report schedule is a schedule for running a report at some time in the future You can create a schedule to run a report once or repeatedly About this task To learn how to sche
137. mmon Reporting version 2 1 1 security settings for authorizations see Cognos Administration and Security Guide By default all new users created for the Common Reporting portlet are assigned to Everyone user group which is a subset of System Administrators To increase the security of your reporting solution edit the members of the System Administrators user group Procedure 1 Log in to Tivoli Integrated Portal a Navigate to the following URL http hostname port ibm console The default URL is http localhost 16310 ibm console Replace hostname with the TCP IP host name of the system where Tivoli Common Reporting is installed or localhost if you are running the web browser on the same system Replace port with the port number that you specified during installation Tip On a Windows system where Tivoli Common Reporting is installed locally you can click Start gt Tivoli Common Reporting gt Launch Reporting Browser to open the default browser with the correct URL b On the Tivoli Integrated Portal login page log in with a user ID that has access to Tivoli Common Reporting Access is determined by user roles associated with user IDs This might be the user ID and password you specified during the installation process or a user ID and password provided to you by an administrator The Tivoli Integrated Portal navigation window opens Tip Only one logon is required when accessing the reporting interface The single sign
138. mon Reporting point to its existing installation location Examples For Windows platform C IBM tivoli tcr For UNIX platform opt IBM tivoli tcr TCR_INSTALLATION_DIRECTORY For the TIP specific part of the solution If INSTALL_INTO_EXISTING_WAS true the install folder must be the location of WebSphere Application Server such as TIP_INSTALLATION DIRECTORY C IBM WebSphere AppServer E Examples For Windows platform C IBM tivoli tip For UNIX platform opt IBM tivoli tip TIP_INSTALLATION_DIRECTORY For the reuse scenario If installing in a reuse scenario to simply add some additional components to already installed instance set this variable to true otherwise comment it out or set to false the default Example REUSE_EXISTING_INSTALLATION true REUSE_EXISTING_INSTALLATION false Installation scenario Choose one of the following installation components configuration for this installation procedure cognos_reporting_engine first step of the distributed installation scenario INSTALLATION SCENARIO cognos_reporting_engine ui_for_cognos second step of the distributed installation scenario INSTALLATION SCENARIO ui_for_cognos single_computer_installation integrate_existing_cognos INSTALLATION SCENARIO ui_f
139. mon Reporting Cognos Application Tier Server components on multiple computers dedicated to processing incoming requests By installing the components on multiple computers as shown on the diagram you distribute and balance loads among the computers You also have better accessibility and throughput than on a single computer as well as failover support Important In a clustered environment all Tivoli Common Reporting instances must share one common content store You must install the Tivoli Common Reporting Cognos reporting engine to install the central content store All the reporting engines must be configured to use one central content store System B System A Tivoli Common Reporting Cognos Application Tier Server Tivoli Common Reporting Server Cognos based Tivoli Common Reporting engine Tivoli Common Reporting console I BIRT based Cognos reporting i gateway Cognos Content Store IRT based reporting portlet Tivoli Common Reporting console close up SystemC _ _ _ _ _ OZO O O OoOo o oo Tivoli Common Reporting Tivoli Integrated Portal Cognos Application Tier Server t p Common Reporting Cognos based with BIRT reporting portlet Cognos based Tivoli Common Reporting engine Common Reporting Chapter 4 Configuring 69 Procedure 1 2 3 Use the first part of the distributed installation
140. must import the reports on the first reporting engine visible on the list in the Administration Panel It is enough to import the reports on one reporting engine because all the reporting engines are connected to one Cognos Content Store Related information L JDBC Driver Options for Using DB2 Database as a Content Store Di Dispatchers and Services Configuring user interface for load balancing Configure all the instances of user interface that you have installed to benefit from load balancing and share the workload among multiple computers Before you begin You need to have two or more user interfaces pointing to one reporting engines installed Note You must perform all the steps described below for all the user interfaces in your infrastructure About this task Load balancing for user interface in Tivoli Common Reporting is based on Tivoli Integrated Portal To fully benefit from load balancing you need to configure the following components e DB2 database that stores data and replicates them multiple instances of Tivoli Common Reporting DB2 database can be configured for failover e An LDAP server to act as a centralized user registry e IBM HTTP Server that routes HTTP requests to the server with the least activity to provide the best performance and share the workload Procedure 1 Configure all the user interfaces installed to point to all the dispatchers 2 Configure DB2 for load balancing 3 Configu
141. n p Restart IBM HTTP Server 7 Open Tivoli Integrated Portal console in your Web browser by typing in the following address http computer_with_IHS_installed ibm console Tip If you experience any problems with the plugin cfg xml file contents and parsing go to error 1og located in the HTTPServer_install_dir logs folder for more information Related information L Tivoli Integrated Portal load balancing L Web server plug in tuning tips Configuring Framework Manager connection Framework Manager is a separately installable application used to model reports If you have installed it in a location different from the default one you need to configure it to run with the Cognos based Tivoli Common Reporting engine and user interface Before you begin Make sure you have extracted and installed the Framework Manager component available from the installation media on the machine where you want to model reports Before you install Framework Manager ensure that the JAVA_HOME environment variable is not set Framework Manager is delivered together with its own version of Java so if you have JAVA_HOME set to Java version already installed on your computer Framework Manager configuration may fail to start If you have installed Framework Manager on a system other than the system where Tivoli Common Reporting engine is installed the data source must exist on this Framework Manager system as well as on the Tivoli Common Reporti
142. n Oracle database 84 User Guide Connect the Tivoli Common Reporting to an Oracle database Before you begin iiin GA Perform this task with the support of a database administrator Make sure you have deployed the 32 bit Oracle database client on the machine where Cognos based Tivoli Common Reporting engine is installed Important You may need to export the TNS_ADMIN environment variable before starting the Tivoli Common Reporting server The TNS_ADMIN variable in the startTCRserver sh script should be set to point to the location of Oracle tnsnames ora file See the Oracle documentation for details About this task The configuration comprises of connecting the database to a client configuring calculations for Oracle functions and activating optional cross database functionality Procedure 1 Connect the Oracle database client to the database server by running the Oracle Net Configuration Assistant configuring the local net service name configuration and restarting your system Important Note the name of the connection you have created as it is used in one of the following steps 2 Create new database connection for Cognos by following the steps a From the Common Reporting portlet go to Launch drop down list and choose the Administration b On the Configuration tab add a new data source by clicking G c Follow the New Data Source wizard as required noting the following steps e On the second panel choose an O
143. n external database instead of on the embedded derby the same database is used by the new instance of Tivoli Common Reporting What to do next 1 If you want to use LDAP as your user repository LDAP configuration is not automatically transferred to the upgraded instance of Tivoli Common Reporting A file with LDAP information exported from the previous version of Tivoli Common Reporting is in TCR_component_dir logs upgrade repository Id properties If you upgraded from Tivoli Common Reporting version 1 3 or 2 1 configure LDAP in Tivoli Integrated Portal only 2 Create new schedules for your reports Report schedules that are created for versions of Tivoli Common Reporting versions earlier than 2 1 are not mapped to Cognos scheduler 3 Configuring JDBC data sources using JNDI on page 97 the same way as you configured them for the Tivoli Common Reporting version that you previously used JNDI data sources are not transferred during the upgrade process 4 Verify that all your report images have been moved Log into the Tivoli Integrated Portal console and check whether all your reports appear in the Common Reporting gt Connection view Try to sample report to check whether it is working properly 6 If you decided to import report snapshots ensure that the snapshot appears as Run history of the report for which it was generated o 7 Disable anonymous access from VMMProvider a Open the IBM Cognos configuration
144. nce of Tivoli Common Reporting and select Distributed installation as your upgrade scenario 3 Select Install the Tivoli Common Reporting engine 4 Choose the existing Tivoli Common Reporting installation directory as the base for upgrade 5 Provide the port number that is to be used for Cognos database The port number must be different than the default port 1527 6 Confirm your choices The upgrade runs in the background What to do next Upgrade the user interface Upgrading Tivoli Common Reporting user interface 50 User Guide Upgrade your Tivoli Common Reporting user interface to finish the upgrade process About this task For this task you need the administrative user login and password Perform this task on the computer where the Tivoli Common Reporting user interface instance is installed Procedure 1 Start the upgrade process by performing steps 1 to 4 in the installation 2 Select the upgrade option and choose the existing Tivoli Common Reporting user interface as the base for the upgrade 3 Choose Distributed installation as your installation scenario and select to Install the Tivoli Common Reporting user interface 4 Select the existing instance that you want to upgrade and confirm your choices 5 Provide the user credentials and port number that will be used to create the Tivoli Integrated Portal profile 6 Provide the administrative user credentials that you used to log in to the previo
145. nd create simple ad hoc reports or select Launch gt Report Studio to create more complex reports e Create a final package Logging in to the reporting interface Use your web browser to access the reporting interface based on the Tivoli Integrated Portal About this task With the reporting interface you can perform simple lightweight tasks as well as more advanced scalable reporting Common Reporting Scalable enterprise reporting option provided by IBM Cognos 8 Business Intelligence Reporting Using this feature you can access the following reporting options e Create on demand reports e Use the Web based report authoring e Email reports Tip To access Tivoli Common Reporting or Tivoli Integrated Portal documentation from the user interface click Help in the upper right corner To access Cognos Administration and Security guide click in the console For more Cognos guides click Procedure 1 Navigate to the following URL http hostname port ibm console The default URL is http localhost 16310 ibm console e Replace hostname with the TCP IP host name of the system whereTivoli Common Reporting is installed or localhost if you are running the web browser on the same system e Replace port with the port number that you specified during installation Tip On a Windows system where Tivoli Common Reporting is installed locally you can click Start gt Tivoli Common Reporting gt Launch Reportin
146. nd provide the port number Click Next 9 Provide the port number for IBM Cognos content database 10 Read the pre installation summary panel and click Install The installation process which may take a longer time begins No action is required When the installation is complete a summary panel is displayed Results You have now completed the full installation procedure and can start to run reports on a single system by logging in to the reporting interface What to do next In this installation scenario the Tivoli Common Reporting VMMProvider is used for Lightweight Directory Access Protocol LDAP by default and no additional configuration is required Important During the installation procedure you have created an administrative user You can now create new users and user groups and grant them permissions to_access various reporting resources and functions Before you do make sure you configure security permissions Installing in a distributed environment 18 User Guide Install the components on separate systems to enable engine load balancing First you have to install the Cognos based Tivoli Common Reporting engine on one computer and configure the Lightweight Directory Access Protocol LDAP user repository Then on a separate computer you have to install the Tivoli Common Reporting user interface Before you begin Ensure that all the components that you want to install are of the same bitness The user inter
147. nd table contains an annotation that states which data set it used in the BIRT report You can find the detailed annotations for each data set at the bottom of the report These annotations contain the data set s SQL query before and after the data set s open script was run and all filters and computer columns To create a query navigate to the Query explorer page and drag and drop a query item from the toolbox into the editor Double click a query to edit it and drag and drop data items from the model into the Data Items editor To add a filter to a query navigate to the Query explorer page and select a query Select Data gt Filters from the menu or click the Filters button If your Tivoli Common Reporting is installed in distributed environment copy the report images to all computers with user interface installed to the following location TCR_install_dir profiles TIPProfile instal1edApps TIPCe11 IBM Cognos 8 ear p2pd war tivoli and to all computers with the reporting engine installed to the following location CR_instal1_dir cognos webcontent tivoli 6 Test if the converted reports work properly For more information see run on page 138 and tremd distribute on page 132 What to do next To find out more go to IBM Cognos 8 Business Intelligence information center Known limitations This section describes Conversion Assistant limitations caused by technology changes in Tivoli Common Reporting 2 1 1 At the present m
148. nd the following error occurs Deployment Engine failed to initialize Resolving the problem Run the installation command again specifying the absolute path to the install sh script Installation fails on a system with Turkish locale Symptoms The installation of Tivoli Common Reporting fails on a system with Turkish locale Resolving the problem Change your system locale to English for the time of the installation When the installation has finished change the locale back to Turkish The Work with reports panel displays an error Symptoms This problem occurs if you have installed Tivoli Common Reporting logged into the reporting console and then uninstalled Tivoli Common Reporting without logging out of the console If after performing these steps you install Tivoli Common Reporting again and try to open the Work with reports panel you get the following error PRS CSE 1258 Problem encountered during verification of session capability information Resolving the problem To resolve the problem restart the web browser or delete the cookie files Cognos Business Intelligence does not install on Windows 2008 64 bits R2 Symptoms Cognos does not officially support Windows 2008 64 bits R2 and the installer fails if you try to install it on this system You can test it by double clicking the unpacked_image TCR21Installer COI DeploymentSteps FCI INST COG FILES win32 issetup exe An error message saying that you cannot install on this
149. ness Plan trcmd datasource Use the datasource command flag for the tremd command to add a data source or test data source connectivity Important This command can be used for Cognos data sources only Syntax Use this syntax to add a new data source tremd datasource add data_source_name connectionName connection_name connectionString connection_string dbType DB2 ORACLE ODBC XML dbName database_name collation collation_sequence signonName signon_name dbLogin database_login dbPassword database_password users namespacel usernamel1 namespace2 username2 groups namespacel groupnamel namespace2 groupname2 roles namespacel rolename1 namespace2 rolename2 force hidden help Use this syntax to test the data source connection with the database tremd datasource test data_source_name connectionName connection_name signonName signon_name dbLogin database_login dbPassword database_password Tip The datasource command is used for creating a new data source connection If you want to modify and existing data source connection you can do this with the force flag using the existing connection s name To modify the data source Chapter 7 Reference 129 130 User Guide 1 Obtain the name of the data source that you want to change 2 Run the datasource as if you were creating a new data source and use the force flag The flag modifies the data source by overwriting the existing data so
150. nfiguration Configuring portlet functions Tivoli Integrated Portal configuration 50 50 ol nol 54 200 56 s97 58 58 59 59 61 61 62 63 64 64 65 66 67 67 69 70 coe 74 75 77 78 81 82 82 83 84 85 86 88 89 89 90 90 iii Chapter 5 Common Reperng 91 BIRT reports in Cognos 91 BIRT reports in Cognos overview 91 Running BIRT reports 92 Saving a BIRT report 93 Creating a Report View of a BIRT report 93 Scheduling reports os ae 94 Importing BIRT reports 94 Retrieving the User Name from within a BIRT Report 94 Converting BIRT reports to Cognos reports 94 Known limitations Z 2 4 amp 97 Administering BIRT reports 97 Setting up JDBC data sources 97 Known limitations 98 Working with reports SO ee 99 Running the sample overview Ww teport 99 Sample overview report 100 Importing report packages 101 Exporting Cognos report packages 101 Copying report images to the Tivoli Common Reporting server 101 E mailing reports 102 Scheduling reports 102 Performing ad hoc reporting 102 Web based report authoring 103 Search path 103 Checking the search path of a report 105 Chapter 6 Troubleshooting and support z 107 Using log files for eoublcivctine 107 Enabling detailed log and trace information 107 Troubleshooting the install
151. ng component requires additional disk space of 700 MB For single computer installation up to 2 4 GB depending on installation options selected For distributed installation Cognos based Tivoli Common Reporting engine 800 MB user interface 1 5 GB For existing Cognos BI infrastructure installation 450 MB Temporary directory 800 MB Copyright IBM Corp 2007 2011 10 User Guide Table 2 Hardware and software requirements continued Supported operating systems BC HP UX e HP UX 11i v3 IA 64 bit e HP UX 11i v3 PA RISC 32 bit and 64 bit Tolerate ETE pM Axe e IBM AIX version 5 3 32 bit and 64 bit e IBM AIX version 6 1 32 bit and 64 bit e IBM AIX version 7 1 32 bit and 64 bit NTE Red Hat Enterprise Linux Important Because Tivoli Common Reporting installs 32 bit binary files you must install the 32 bit versions of the prerequisite libraries even on 64 bit system Otherwise the installation fails e RedHat Enterprise Linux 5 0 Advanced Platform x86 32 bit and 64 bit Restriction The following system libraries must be installed compat libstdce 33 3 2 3 compat glibc 2 3 4 2 26 openmotif22 2 2 3 18 e RedHat Enterprise Linux 5 0 System z 31 bit and 64 bit Restriction Tivoli Common Reporting can only run on this system with the following libraries installed libXmu 1 0 2 5 libXp 1 0 0 8 openmotif22 2 2 3 18 BEEJ sust e SUSE Linux Enterprise Server 10 0 x8
152. ng engine system Procedure 1 Open the Framework Manager configuration program by running Framework_Manager_install_dir bin cogconfigw exe Tip The default Framework Manager installation directory is c Program Files cognos bin cogconfigw exe Chapter 4 Configuring 81 2 In the Explorer navigation on the left go to Environment section Group Properties panel opens on the right 3 Go to Gateway Settings and locate Gateway URI Click on the value field and update it with the URI to your Tivoli Common Reporting server Tip The default value for a single computer installation is https localhost 16311 tarf servlet component The URIs in Step 3 and Step 4 should match the values in the Tivoli Common Reporting IBM Cognos Configuration manager You can check those values by running tcr_cogconfig bat Windows or tcr_cogconfig sh UNIX on the Tivoli Common Reporting server in the TCR_component_dir cognos bin 4 In the Other URI Settings edit the value for Dispatcher URI for external applications to match the location of your Tivoli Common Reporting engine Tip The default value for Dispatcher URI for external applications is http localhost 16310 tarf servlet dispatch ext for a single computer installation and http localhost 9080 p2pd servlet dispatch for the distributed installation 5 Save the new configuration What to do next You can now start modeling your reports with the use of Framework Manager You will need
153. ng the stopTCRserver sh 2 Start the server from the command line interface by navigating to MMI 7CR_component_dir bin and running the startTCRserver bat command ETE TCR_component_dir bin and running the startTCRserver sh The Work with reports window is blank Symptoms After restarting Tivoli Integrated Portal server and navigating to Common Reporting the Work with reports window on the right is blank Causes This happens because when Tivoli Integrated Portal server is starting all the applications installed in embedded WebSphere Application Server start as well which takes some time Resolving the problem Wait for all the applications to load An error UDA SQL 0569 appears while starting Cognos server Symptoms When starting Cognos server the error UDA SQL 0569 Unable to load the driver manager library db2cli d11 occurs The server does not start Causes Cygwin is installed on Windows Server and the bin directory is added to the PATH variable Diagnosing the problem You can find the error in the log file or directly in the details of Cognos startup dialog which is displayed by the Configuration tool cogconfigw Resolving the problem Remove the Cygwin bin entry from your system PATH and restart the system An error occurs when starting Framework Manager 116 User Guide Symptoms An error BME EX 0047 Unable to read preferences for the requested appears when opening or creating a pro
154. ning the export LAX DEBUG 1 command Run the installer Collect the output Below is an exemplary system output Exception in thread main java lang UnsatisfiedLinkError tmp install dir 20635 Linux resource jre jre bin xawt 1ibmawt so libXft so 2 cannot open shared object file No such file or directory at at at at at at java lang ClassLoader loadLibraryWithPath ClassLoader java 957 java lang System load System java 441 java lang ClassLoader loadLibraryWithPath Native Method java lang ClassLoader loadLibraryWithPath ClassLoader java 949 java lang ClassLoader loadLibraryWithClassLoader ClassLoader java 926 java lang System loadLibrary System java 453 Chapter 6 Troubleshooting and support 109 at sun security action LoadLibraryAction run LoadLibraryAction java 77 at java security AccessController doPrivileged AccessController java 193 at sun awt NativeLibLoader loadLibraries NativeLibLoader java 75 at sun awt DebugHelper lt clinit gt DebugHelper java 57 at java lang J9VMInternals initializeImp Native Method at java lang J9VMInternals initialize J9VMInternals java 192 at java awt Component lt clinit gt Component java 582 at java lang J9VMInternals initializeImp Native Method at java lang J9VMInternals initialize J9VMInternals java 192 at java lang J9VMInternals initialize J9VMInternals java 157 at java lang J9VMInternals initialize J9VMInternals java 157 at com zerog ia i
155. nstaller util BidiUtilImp setDefaultLocale DashoAl0 at ZeroGay a DashoAl0 at com zerog ia installer LifeCycleManager j DashoAl0 at com zerog ia installer LifeCycleManager e DashoAl0 at com zerog ia installer LifeCycleManager a DashoAl0 at com zerog ia installer LifeCycleManager a DashoAl0 at com zerog ia installer Main main DashoA10 at sun reflect NativeMethodAccessorImp1 invokeO Native Method at sun reflect NativeMethodAccessorImp1 invoke NativeMethodAccessorImp1 java 64 at sun reflect DelegatingMethodAccessorImp invoke DelegatingMethodAccessorImp1 java 43 at java lang reflect Method invoke Method java 615 at com zerog 1ax LAX launch DashoA10 at com zerog ax LAX main DashoAl0 java lang UnsatisfiedLinkError java awt Component initIDs V at java awt Component lt clinit gt Component java 595 at java lang J9VMInternals initializeImp Native Method at java lang J9VMInternals initialize J9VMInternals java 192 at java lang J9VMInternals initialize J9VMInternals java 157 at java lang J9VMInternals initialize J9VMInternals java 157 at com zerog ia installer util BidiUtilImp setDefaultLocale DashoAl0 at ZeroGay a DashoAl0 at com zerog ia installer LifeCycleManager j DashoAl0 at com zerog ia installer LifeCycleManager e DashoAl0 at com zerog ia installer LifeCycleManager a DashoAl0 at com zerog ia installer LifeCycleManager a DashoAl0 at com zerog ia installer Main main
156. nternet Explorer version 7 or 8 on Microsoft Windows Tip For some operations the browser security settings are too restrictive See the Troubleshooting section of the information center for additional security configuration of the Internet Explorer browser e Mozilla Firefox version 3 6 Installation scenarios and installation modes You can choose from two installation modes and three main Tivoli Common Reporting installation configurations You can choose from the following installation modes e Install new instance of Tivoli Common Reporting e Reuse the existing instance of Tivoli Integrated Portal Use this option if you already have a product based on Tivoli Integrated Portal in your infrastructure This mode allows you to install Tivoli Common Reporting on the same instance of Tivoli Integrated Portal as the product you already have Tivoli Common Reporting version 2 1 1 introduces a 64 bit installer alongside the 32 bit installer present in previous versions Important The 64 bit installer can only be used for a stand alone Tivoli Common Reporting installation and only Tivoli Integrated Portal version 2 2 can be reused Because the previous Tivoli Common Reporting versions were 32 bit you cannot use the 64 bit installer to upgrade an existing Tivoli Common Reporting version The following installation scenarios are available Single computer installation Chapter 2 Installing 11 Scenario A Sing
157. oad balancing 70 User Guide Configure your reporting system to obtain higher performance and usability levels while running reports by adding another reporting engine system and ensure failover About this task Load balancing allows you to have multiple user interfaces as well as reporting engines installed which will distribute and balance loads among the computers This in turn improves scalability in an environment where there is a large volume of report requests to process It also ensures failover The diagram below presents how various components are linked together to ensure load balancing HTTP Load Balancer Tivoli Common Reporting user interface Tivoli Common Reporting user interface Tivoli Common Reporting user interface Tivoli Common Reporting engine Tivoli Common Reporting engine Tivoli Common Reporting engine IBM Cognos Content Store database This task is based on a distributed installation scenario Important Remember to install the reporting engine first and only then the user interface Procedure 1 Run distributed installation Tip To add reporting engines to your infrastructure a Run the installation program on each computer where you want to install the reporting engine b Select the distributed installation scenario c Select to install the reporting engine 2 Configure the Tivoli Common Reporting engines that you have installed Ti
158. ocedure di and MUS Log on as the same user used to install the full Tivoli Common Reporting product 2 Place all the downloaded installation images in a single directory on the computer where you are installing For example MII CC install_images and MUM install_images 3 Extract the contents of all installation images to the directory that you created What to do next The installation images are now ready Validation of additional disk space required for the installation process 16 User Guide The installation process of Tivoli Common Reporting involves the validation of additional disk space required for both temporary directory TEMP and the target installation directory in which Deployment Engine is installed Important This topic describes additional disk space required to successfully finish the installation process The main disk space required for the installation of Tivoli Common Reporting is described in the Hardware and software requirements section of the Installation Guide Procedure a a disk space required for the TEMP folder is checked the space required is 800 MB Note Additional disk space in the TEMP folder is required only for the time of the installation b disk space required for the installation of Deployment Engine is checked Note Deployment Engine drives the installation process and stores information about the installed components after the process is finished Note Deployment
159. of Tivoli Common Reporting are not mapped to Cognos scheduler 3 Configuring JDBC data sources using JNDI on page 97 the same way as you configured them for the Tivoli Common Reporting version that you previously used JNDI data sources are not transferred during the upgrade process Upgrading across scenarios When you have upgraded Tivoli Common Reporting you can migrate the upgraded Tivoli Common Reporting from single to distributed environment and enable Tivoli Common Reporting 2 1 1 to use Cognos installed on a different computer Before you begin Ensure that you have a computer with Cognos installed Procedure 1 Migrate the upgraded product from a single computer to a distributed environment 2 Configure Tivoli Common Reporting to use Cognos installed on a separate Exporting data from Tivoli Common Reporting Before you enable your Tivoli Common Reporting instance to use external Cognos export the data to preserve it Procedure 1 Export the complete Cognos Content Store from Web user interface a Select Launch gt Administration b Go to the Configuration tab and select Content Administration c Create new package export by clicking 58 User Guide d Follow the wizard to export the archive The exported package is visible in the Administration window All choices that you made with the export wizard are saved in this export package so you can use it later to run an export with the same setting
160. oli Integrated Portal load balancing configuration 5 Configure the plugin cfg xml file on the computer where IBM HTTP Server is installed The file is located in HTTPServer_install_dir Plugins config webserverl a Point to the plugin key kdb and plugin key sth that you copied in step 4e b Provide correct Tivoli Integrated Portal server information such as name port or LoadBalanceWeight for each of the computers in the cluster c Change the AffinityCookie value to AffinityCookie JSESSIONID_isc Check if the VirtualHostGroup parameter is set to admin_host Below is an example of the plugin cfg xml file for Tivoli Common Reporting lt Config ASDisableNagle false IISDisableNagle false IgnoreDNSFailures false RefreshInterval 60 ResponseChunkSize 64 AcceptAl Content false IISPluginPriority High FIPSEnable false AppServerPortPreference HostHeader VHostMatchingCompat false ChunkedResponse false gt lt Log LogLevel Error Name C Program Files IBM HTTPServer Plugins logs webserverl http_plugin log gt lt Property Name ESTEnable Value true gt lt Property Name ESIMaxCacheSize Value 1024 gt lt Property Name ESIInvalidationMonitor Value false gt lt Property Name PluginInstallRoot Value C Program Files IBM HTTPServer Plugins gt lt VirtualHostGroup Name admin_host gt lt VirtualHost Name 36310 gt lt VirtualHost Name 36311 gt lt VirtualHost Name 46310 gt lt Virt
161. omProperties propert e For Tivoli Common Reporting 2 1 1 3 and 1 2 installed as a separate product 7 8 existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade bat username username password password productId TCR Ra tina existing_TCR_install_dir profiles TIPProfile upgrade bin preupgrade sh username username password password productId TCR The package is created in the following location e For versions 1 2 1 3 and 2 1 existing_TCR_install_dir profiles TIPProfile upgrade data upgradeData zip e For version 1 1 1 existing_TCR_install_dir upgrade data upgradeData zip Perform steps 1 to 4 of installation instructions Select Upgrade Tivoli Common Reporting from the package as the installation mode Choose Single computer installation as the upgrade scenario Choose the installation directory and provide the location of the package Enter the user ID and password that you use to log into Tivoli Integrated Portal console Provide the port number for IBM Cognos content database Read the summary panel and click Install Results You have upgraded to Tivoli Common Reporting version 2 1 1 and the following data was imported Database drivers Report snapshots were generated to PDF format and saved as saved reports Cognos Content Store was migrated from the embedded derby database If your Content Store was located on an external database instead of on the embedded derby the same databas
162. oment the following limitations are known to exist e Because of the incompatibility issues BIRT data source script and data sources are not transferred to Cognos reports Additionally transferring items such as inserting SQL directly into Cognos based report would lose the added benefit this technology brings e The new Cognos based format does not support JavaScript during report generation e Web services data sources are not automatically moved from BIRT to Cognos reports e Globalization is not supported The converted report is in the language in which it was generated However you can globalize the new report in the Report Studio after the conversion e oda data cube is not supported in Cognos reports Administering BIRT reports Learn to configure the data sources for your reports Setting up JDBC data sources Some reports might require that you set up JDBC data sources to provide report data You can use either of two methods to configure JDBC data sources for these reports Before you begin Restriction BIRT and Cognos have separate data sources that are created and managed differently JOBC and JNDI data sources are only supported for BIRT reports Cognos is using native drivers Configuring JDBC data sources using JNDI You can use WebSphere Application Server scripting to configure JDBC providers and data sources for your reports and to configure JNDI names for reports to use when accessing data sources If you
163. on program file is in the TCRInstaller directory of the installation DVD or downloaded installation image Use the installation program for your operating system EAIN install exe 2 Start the installation program from the command line Use the following command lt install_program gt i console For example to run the Windows installation program run this following command install i console 3 Follow the instructions to complete the installation Tip At any time during the installation you can type in previous to go back to the previous pane or quit to quit the installation You need the following information e The location where you want to install IBM Tivoli Common Reporting The path can contain only alphanumeric characters and the following special characters underscore _ hyphen period colon slash backslash space e The user ID and password you want to use to log on to IBM Tivoli Common Reporting you can create additional user IDs after installation User IDs and passwords can contain only alphanumeric characters and the following special characters underscore _ hyphen period Apart from the installation directory two new directories are created e C IBM tivoli tipv2 containing Tivoli Integrated Portal and e C IBM tivoli tipv2Components TCRComponent containing among others the component and scripts The directories a
164. or_cognos osce URL to Cognos The URL should point to the machine on which the Cognos reporting engine is installed COGNOS_URL http lt hostname gt 9300 p2pd servlet dispatch Tivoli Integrated Portal configuration related WebSphere information Enter a WebSphere Application Server administrator user name and password If the password is not provided the installer will fail WAS_USER_NAME tipadmin Chapter 2 Installing 29 30 User Guide WAS_PASSWORD ti padmin Should it be upgrade PERFORM _UPGRADE false Following variables are for upgrade only Path to the previous instance of TCR or migration package UPGRADE_SOURCE opt IBM tivoli tip or on Windows systems note double backslashes UPGRADE_SOURCE C IBM tivoli tip Define type of the upgrade source existing instance or a migration package Valid values instance package UPGRADE_MODE instance These are only for upgrade from existing instance of TCR PREVIOUS_INSTANCE_USER_ID tipadmin PREVIOUS_INSTANCE_USER_PASSWORD xxx fuse Enter the ports that WebSphere Application server will use Only WAS_WC_defaulthost is required The rest of the ports if not specified will be derived basing on the WAS_WC_defaulthost WAS_WC_defaulthost 16310 WAS_WC_defaulthost_secure 16311 WAS_BOOTSTRAP_ADDRESS 16312 WAS_SOAP_CONNECTOR_ADDRESS 16313 WAS_IPC_CO
165. os Connection User Guide Schedule Management Importing BIRT reports You can import single reports as well as report packages from Tivoli Common Reporting v 1 1 1 and 1 2 About this task You can import reports and report packages only by using the tremd import command The package will be installed in the directory chosen by you_within the Cognos Content Manager For more information and examples see the command Retrieving the User Name from within a BIRT Report You can retrieve the user name from the context of a BIRT report About this task Similarly to previous versions Tivoli Common Reporting 2 1 1 allows you to retrieve the user name from a BIRT report Using the following command reportContext getAppContext you can use the application context to obtain the property com ibm tivoli reporting api reportEngine IUserInfo which contains an object that has a method getUserPrincipal This object will return a security Principal object containing the user name Restriction This will only work if information on the current user is available Example Below you can find a sample code fragment used to retrieve the user name TCR_IUSER com ibm tivoli reporting api reportEngine IUserInfo userInfo reportContext getAppContext get TCR_IUSER userName unknown if userInfo null userName userInfo getUserPrincipal Converting BIRT reports to Cognos reports Use Conversion Assistant to help you conve
166. ou have just created to the data model and publish it on a server Then configure the report using the Set Properties icon to be able to use it 4 Open the converted report in Report Studio a Log in to the Tivoli Common Reporting interface and go to Common Reporting b In the Work with reports window on the right choose Report Studio from the Launch expandable list c Open the report that you have just converted 5 Fill in the report layout with missing elements from the data model a Header and Footer are blank after the conversion Add any items that you want to be displayed in these sections b If you want to display static text delete the HTML item and replace it with a text item from the toolbox Do not delete the block item with the text item because it contains the CSS style of the text item c If you want to display script delete the HTML item and replace it with a text item from the toolbox by changing the Source Type from Text to Report Expression in the properties editor When you do this you can copy and paste your script into the expression editor by double clicking on the item If you want to display JavaScript ensure that you placed your script between the following tags lt SCRIPT TYPE text javastcript gt lt SCRIPT gt d To display HTML edit the HTML text within the editor by double clicking on it e Create a query for each dynamic parameter in your report During the conversion a stylized paramete
167. p Repeat this step for every reporting engine that you have installed 3 Configure the user interface Tip You can add more interfaces to your infrastructure a Run the installation program on the machine where you want to install the user interface Select the distributed installation scenario Select to install the user interface Chapter 4 Configuring 71 d Configure each of the user interfaces that you have installed What to do next 1 To finish the configuration see the following topics of the IBM Cognos 8 information center e Balance requests among reporting engines You can set the way in which the requests are handled among the dispatchers e Use cluster compatible mode for dispatchers You can change the way in which the load is balanced in your infrastructure e Installing and configuring distributed installations Learn how to properly configure the server component Content Manager component Application Tier components and gateway The sequence in which you configure the computers is important Visit the topic to find out more 2 Learn how to e Start and stop dispatchers and services e Activate a Content Manager service e Remove dispatchers from your environment Load balancing 72 User Guide You can setup a load balancing cluster of portal nodes with identical configurations to evenly distribute user sessions Load balancing is ideal for Tivoli Integrated Product installations
168. port the Cognos data a Open the Tivoli Integrated Portal console and select Launch gt Administraton b Go to the Configuration tab and select Content Administration ee c Create new package export by clicking d Import the previously exported data Chapter 3 Upgrading 59 60 User Guide Chapter 4 Configuring Configure the IBM Tivoli Common Reporting you have installed to optimize its usage Use the configuring section to learn how to set up data sources and configure for high availability Configuring LDAP or Microsoft Active Directory After installation you can configure a Lightweight Directory Access Protocol LDAP server or Microsoft Active Directory as a user registry Perform the following configuration steps depending on the installation scenario you selected Installation scenario Configuration path Single computer installation 1 Configure the Tivoli Common Reporting 2 Recommended for large user repositories Configure the engine Distributed installation On the computer with Tivoli Common Reporting user interface installed configure the Tivoli Common Reporting e On the computer with Cognos based Tivoli Common Reporting engine installed configure the reporting engine On the computer with Tivoli Common Reporting user interface installed configure the Tivoli Common Reporting Integrating existing Cognos BI infrastructure Important The configuration o
169. pps TIPCel1 IBM Cognos 8 ear p2pd war WEB INF 1ib VMMprovider properties 2 Uncomment the following two lines by removing the first character A11owAl 1GroupsSearch false AllowAl 1UsersSearch false 3 Save and close the file 4 Restart Tivoli Common Reporting server Chapter 6 Troubleshooting and support 123 124 User Guide Chapter 7 Reference Reference information supports the tasks that you want to complete It includes system messages Commands This section contains topics that provide information about command line interface in IBM Tivoli Common Reporting The tremd command provides access to the Tivoli Common Reporting command line interface Use this command to perform administrative tasks related to reports report sets and report designs The command line interface is available only on the system where Tivoli Common Reporting is installed To use the tremd command go to the tipv2Components TCRComponent bin subdirectory of theTivoli Integrated Portal installation directory Each command function is accessed using a command flag which must be the first command line argument following tremd tremd sh on Linux and UNIX systems Each command flag might have multiple flag sets a flag set is a set of command line arguments used together to perform a specific task For example different flag sets for tremd import are used to import reports To see syntax and usage information for any tremd command
170. r If you do not provide it default value will be used Its default value depends on the installation scenario that you chose For installation on a single computer it is VMMProvider and for distributed installation it is LDAP trcmd access 126 User Guide The access command flag for the tremd command grants removes or denies access for a particular user group or role to access a specified resource Syntax Use this syntax to change access to a resource trcmd access grant remove deny permissions permission1 permission 2 entity cognosSearchPath reportSet cognosSearchPath accessIdentity cognosSearchPath accessUser cognosSearchPath accessGroup cognosSearchPath help Use this syntax to cause a resource to inherit all its permissions from a parent object tremd access inheritPermissions entity cognosSearchPath Note 1 Authentication with user userID and password password is required in all cases 2 If you have configured more than one user repository specify the namespace value By default the namespace parameter points to VMMProvider Parameters accessIdentity identityName The name of entity for which authorization is to be changed It can be a user group or role accessGroup groupName The function of this flag is identical to the accessIdentity flag Its presence ensures compatibility with earlier versions of Tivoli Common Reporting accessUser userName The function of
171. r instructions on how to enable LDAP for each node Chapter 4 Configuring 73 74 User Guide A front end network dispatcher for example IBM HTTP Server must be setup to handle and distribute all incoming session requests See for more information about this task e DB2 Version 9 7 must be installed within the network to synchronize the global repositories for the console cluster e Each node in the cluster must be enabled to use the same LDAP using the same user and group configuration e All console nodes in load balancing cluster must be installed in the same cell name After console installation on each node use the cellName parameter on the manageprofiles command e All console nodes in load balancing cluster must have synchronized clocks e The WebSphere Application Server and Tivoli Integrated Portal Server versions must have the same release level including any fix packs Fixes and upgrades for the runtime must be applied manually at each node Monitoring a load balancing cluster If synchronized data fails to be committed to a node in the cluster that node should be removed from the cluster for corrective action Use the diagnosis tool to identify any unsynchronized nodes in the load balancing cluster To determine if changes to global data are not committed to any of the nodes use the HATool command script to check the synchronization of modules and repositories on the nodes in a cluster For the HATool you must pro
172. r prompt page is created containing all the BIRT parameters grouped by parameter group The grouping is for Chapter 5 Common Reporting 95 96 User Guide aesthetics only Static parameters are converted completely dynamic parameters must be linked to a query Use the parameter query annotation to create a query for each dynamic parameter If you want to apply parameters to the data generated for the report add filters to the appropriate queries If your report contains Report Period and Start End Date parameters replace the parameter prompts with the TCR Date Range Prompt that you can find in the toolbox To keep the same style copy and paste the Date Filter into the old Report Period prompt cell and the Date Range prompt into the old Start Date prompt cell Delete the End Date parameter row and follow the instructions for applying the query filter If you want to display the parameter values dynamically change the Source Type property of the static text item in the properties from Text to Report Expression Double click the text item and select the Parameters tab in the editor then drag and drop the appropriate parameter into the editor Organize your data into charts by creating or editing a query that references the data set annotations To do this select the Query tab then drag and drop the data items into the series categories and measures where applicable Ensure that the Query property value matches the name of the quer
173. racle database as Type e On the third panel specify the name of the connection you have noted before as the SQL Net connect string and in the Signon section specify a new User ID and Password Results You have now connected your Tivoli Common Reporting to an Oracle database Enabling Federal Information Processing Standard Configure Tivoli Common Reporting to use the United States government Federal Information Processing Standards FIPS relating to encryption Before you begin Enable Federal Information Processing Standard for Tivoli Integrated Portal About this task For more information about FIPS see http csrce nist zov publications fips If you have Tivoli Common Reporting installed in distributed environment perform the steps on the computer where your reporting engine is installed first and then on the computer where your user interface is installed To enable FIPS in Cognos Procedure 1 Stop the Tivoli Common Reporting server by running the stopTCRserver script UTS 7CR_component_dir bin stopTCRserver bat 2 Run Cognos Configuration B TCR _component_dir Cognos bin tcr_cogconfig bat MCL TCR_component_dir Cognos bin tcr_cogconfig sh Chapter 4 Configuring 85 10 11 Export your configuration by selecting File gt Export As The file contains unencrypted information so it is recommended that you save it in a secure location Specify cogstartup xml as the name of the file
174. re LDAP as user repository for load balancing 4 Configure IBM HTTP Server to point to all the user interfaces Note If you are using other HTTP server refer to its documentation for configuration details 5 Copy the report images to the Tivoli Common Reporting server and user Important The same reports must be imported and configured for all the reporting engines in your infrastructure If you want to add a new reporting engine you can copy the data catalog from an existing reporting engine instead of importing and configuring the reports again In the case of Cognos reports it is enough to import the reports on any reporting engine because all the reporting engines are connected to one Content Store You must import BIRT reports on each of the engines separately Chapter 4 Configuring 77 78 User Guide Related information L Tivoli Integrated Portal load balancing Configuring IBM HTTP Server Configure IBM HTTP Server as Tivoli Integrated Portal load balancer The server must point to all the user interfaces that you have installed About this task The infrastructure that you configure in this task consists of a computer on which IBM HTTP Server together with WebSphere Application plugin is installed and two or more computers on which Tivoli Integrated Portal high availability cluster is configured Procedure 1 Install IBM HTTP Server version 7 0 together with WebSphere Application 7 0 After you have done t
175. re created because of Tivoli Integrated Portal 2 2 requirements Results After the installation program finishes IBM Tivoli Common Reporting is installed and ready to use Installing using the silent mode Silent installation also known as unattended installation uses a response file to automate the installation process No user interaction is required Tip Choose silent installation when you want to perform identical installation on several computers Chapter 2 Installing 21 22 User Guide About this task MXN To perform this task you must belong to the Administrators group or be an Administrator Important If you are installing in distributed scenario ensure that the reporting engine and the user interface are both either 32 bit or 64 bit Installing components of different bitness is not supported and returns errors Procedure di Copy the installation program file to a temporary directory on the target system The installation program file is in the TCR21Installer directory of the installation DVD or downloaded installation image Use the installation program for your operating system lt EZTA install exe and UC install sh Copy the TCR_sample_response txt file available from the installation DVD or downloaded installation image to a directory on the target system Fast path If you already know your installation scenario choose one of the scenario specific response files that include only option
176. report has been saved and you can now view it 4 To view the saved report a Select i View the output versions for this report icon b Choose the version of the report that you want to view and open the report Report overview opens Note You can also save the report by selecting Keep this version gt Save report in the Reporting Overview pane Creating a Report View of a BIRT report A Report View is a saved version of a report using data from a particular time The Report View has the same specification as the source report but has different properties such as schedules or output formats About this task To create a Report View Procedure 1 Log in to Connection 2 Go to Reporting gt Common Reporting 3 Locate the report you want to run using the Navigation or Search tab and select the report 4 Click Keep this version and select Save as a Report View from the drop down list 5 Specify the name and the location for the Report View Results The new Report View appears immediately in the table under the source report Chapter 5 Common Reporting 93 What to do next For other ways of creating Report Views visit IBM Cognos Connection User Guide Create a Report View Scheduling reports A report schedule is a schedule for running a report at some time in the future You can create a schedule to run a report once or repeatedly About this task To learn how to schedule reports go to IBM Cogn
177. reviously used to create the database If you do not know this user name or password 1 Run the following command to check if the user has access to the temporary user table space db2 connect to database_name user_id using password db2 declare global temporary table t1 cl char 1 with replace on commit preserver rows not logg db2 disconnect database_name If this command fails it means that the user cannot access the temporary user table space in the database In such case move on to Step 2 2 Run the following command to create a new temporary table space for the user db2 connect to database_name user_id using password db2 create user temporary tablespace usertmp2 managed by system using usertmp2 db2 disconnect database_name For more information consult DB2 information center Report Studio does not work with Internet Explorer 8 122 User Guide Symptoms When trying to open Cognos 8 4 1 reports in Internet Explorer 8 the following error message appears CM REQ 4158 The search path content folder na e folder report name report is invalid Causes The Internet Explorer 8 XSS filter scrambles the Cognos search path rendering it invalid Environment All Windows operating systems Resolving the problem Apply the following changes to Internet Explorer 8 1 Add Cognos URL to Trusted Sites list 2 Modify the options of the Trusted Sites zone and set the Enable XSS Filter property to Disable 3
178. ribute your reports Running the sample overview report After you have installed Tivoli Common Reporting 2 1 1 you can run a check on the reporting functionality by running your first sample report The report can also be run for an overall reporting overview Before you begin You can set file location to save copy of report output to use it again later or for archive purposes If you decide to use a post processing script it must include two parameters e Parameter 1 specifies the name of the file that is the report e Parameter 2 specifies the name of the file that is the XML descriptor file Chapter 5 Common Reporting 99 100 User Guide Procedure i 2 3 6 Log in to your reporting interface by following Navigate to the Common Reporting A new tab opens on the right Open the out of the box Common Reporting package in your Public Folders view Click on Reporting Overview report to run it Specify the date parameters to limit the time frame of the report Tip If you run this as an overview of your reporting activities you can also limit the scope of data to a given report package a specific report or a report owner by specifying the appropriate filters Click Finish The report is now generated Sample overview report Tivoli Common Reporting comes with a sample report to allow you to monitor your reporting activity Tivoli Common Reporting Reporting Overview The report available from Common Repo
179. rsion install a 32 bit version of the Oracle client and see the following instructions to configure it Cognos Oracle connection problems Fast path 1 Install 32 bit Oracle client 2 Restart your computer 3 Set the variable COGNOS_HOME to point to the base directory of the Oracle client installation 4 Configure the system library path to point to the Oracle client libraries 32 bit version You must modify the following variables gt MES LD_LIBRARY_PATH e LD_LIBRARY_PATH gt MEO SHLIB_PATH ERC LIBPATH EIS PATH Oracle environment variables for non Oracle default user Symptoms The variables ORACLE_HOME and LD_LIBRARY_PATH necessary to correctly connect to an Oracle data source are set automatically by the etc profile d oracle sh script This happens only for an Oracle user Resolving the problem If you are using non Oracle user set the ORACLE_HOME and LD_LIBRARY_PATH manually or modify the oracle sh script to set them for all users No content displayed in Common Reporting portlet in Internet Explorer 7 Symptoms 118 User Guide The Common Reporting portlet is blank when opened in Internet Explorer 7 with default security settings Resolving the problem Customize the browser security settings to match the portlet demands To change the settings e In Internet Explorer 7 window go to Tools gt Internet Options and on the Security tab in the Security level for this zone section click Custom level
180. rt The unique name of the report you want to distribute Only the specified report is distributed drill through reports are not included The following optional parameters are available baseImageURL The base URL to use in references to images in an HTML formatted report This URL should reflect the location of the image files at the time the report is viewed The default value is images are read from the same directory as the HTML file format format Specifies output format for example format HTML It is possible to specify multiple formats at one time for example format PDF HTML If this parameter is not used the output format of the report is PDF The supported formats are PDF HTML CSV XML XLS imageDir imagePath The location to use when saving image files used by an HTML formatted report If you do not specify an image directory images are saved in the same location as the distributed report Note Each time a report is distributed to the file system new image files are generated with unique file names Existing image files in the target location are not overwritten You must manually delete files generated by previous report runs when they are no longer needed locale locale Specifies the language of the report for example locale en for English To see the list of ISO codes for languages or to search by code or language go to www loc gov standards iso639 2 langhome html and find the two character I
181. rt your BIRT reports into Cognos This action is necessary because of the change from BIRT technology to Cognos technology in Tivoli Common Reporting 2 1 1 94 User Guide Before you begin Ensure that the report you want to convert is working properly Important The BIRT report that you want to convert must be a valid Tivoli Common Reporting BIRT report otherwise the conversion tool will not work About this task Conversion Assistant converts a BIRT report output to Cognos report specification It transfers the report layout images and data however there are certain actions that you must perform manually to finish the conversion Conversion Assistant facilitates the manual part of the process by placing annotations and tips in the report which instruct you what actions you should take To convert your BIRT report into Cognos report Procedure 1 Run the tremd convert on page 127 command Note A report that has just been converted may not run properly You need to open it in Report Studio and finish the conversion process manually 2 Create a data source in Cognos BIRT data sources are incompatible with Cognos data sources Cognos data source must connect to the same database as BIRT reports It is recommended for a Cognos data source to have the same name as a BIRT data source 3 Associate a model provided by Tivoli for the intended product or create a data model in the Framework Manager add the data source that y
182. rting panel shows an inventory of report packages and reports created in the time period specified with date parameters The pie chart shows the percentage value of reports from one package in the overall number of all the reports and the table below gives the number of reports per given package Date Filter All Start Date Jan 1 1970 12 00 00 AM End Date Jun 30 2010 11 59 59 PM Package Folder All Report All Owner All Package Folder E HSE Admin Reports E HSE Advanced Repor E HEr Audit Reports E IBM Tivoli Monitoring E TTM4Wrepper reportChecker Standard Reports Reports Package Folder Reports HSlz Admin Reports HSlz Advanced Reports HSIz Audit Reports 8 IBM Tivoli Monitoring OS Agents Reports 2 TTM4 Vrapper 30 reportChecker Standard Reports 4 Summary 59 Importing report packages Import report packages to your workspace using the user interface and start using an existing report model and reports This importing method can be used for Cognos reports only Before you begin You have to obtain a report package you want to work with You can download packages from ISML library or you can create one using the Content Administrator interface All the packages you want to import have to be stored in the deployment folder in TCR_component_dir cognos deployment Procedure 1 Log in to the Tivoli Common Reporting interface and go to Common Reporting 2 In the Work with reports window on the right
183. s The export package is located in TCR_component_dir cognos deployment 2 Archive the directory where report images are stored What to do next Enable Tivoli Common Reporting to use external Cognos Migrating to a distributed environment Migrate a single computer installation to a distributed environment First upgrade the Cognos based Tivoli Common Reporting engine then modify the existing single computer installation Procedure 1 Upgrade Tivoli Common Reporting 2 Export data from the existing Tivoli Common Re 3 Modify the single computer installatio 4 Exporting data from previous instances manually Migrate the data from your previous Tivoli Common Reporting instances to Tivoli Common Reporting version 2 1 1 Procedure 1 Export BIRT reports from previous version of Tivoli Common Reporting to version 2 1 1 a Run the tcrmd export command to export the reports from the older version of Tivoli Common Reporting See the documentation to your old Tivoli Common Reporting instance documentation for details b Import the reports into version 2 1 1 by running the tremd import on page 133 ge 133 command 2 Copy your own custom jar files from previous_TCR_install_dir lib to new_TCR_component_dir 1ib 3 Copy the report images to a folder with reports in Tivoli Common Reporting 2 1 1 installation directory 4 If you are migrating data from Tivoli Common Reporting version 1 3 or 2 1 ex
184. s relevant to your installation type e For the single computer installation scenario use the TCR sample response embedded txt file e For the distributed installation scenario first use the TCR_sample_response_dispatcher txt file on the computer where you want to install the reporting engine and then the TCR_sample_response_gateway txt on the computer where you want to install the user interface e For the integration with existing Cognos BI scenario use the TCR sample response _external txt file Edit the sample response file using a text editor You must update the file to indicate acceptance of the software license installation directory and installation scenario selection Additionally depending on the installation scenario you can specify the following parameters Single computer installation single_computer_installation All parameters can be used except for COGNOS_URL Distributed installation ui_for_cognos All parameters can be used Integrating existing Cognos BI integrate_existing_cognos All parameters can be used Start the installation program from the command line Use the following command specifying the name and the location of your response file lt install_program gt i silent f TCR_sample_response txt Results The installation program runs without any prompts or user interaction Apart from the installation directory two new directories are created e install_dir tipv2 containing Tivol
185. s the password needed to access the database force Overrides the data source connection or sign on if it already exists groups namespacel groupnamel namespace2 groupname2 Specifies the names of groups that can access the sign on If you omit namespace the default Cognos namespace will be used hidden Hides the data source from other users help Displays syntax and usage information of a command flag roles namespacel rolenamel namespace2 rolename2 Specifies the names of roles that can access the sign on If you omit namespace the default Cognos namespace will be used SignonName signon_name When used with the add parameter it specifies the sign on name needed to access the database If you do not use signonName database_login name will be used as the sign on name When used with the test parameter it specifies the sign on name needed to access the tested database If you do not specify it the dbLogin and dbPassword parameters will be used as the sign on name If you omit signonName dbLogin and dbPassword the first sign on on the list will be used to test the data source test data_source_name Tests the connection between the data source and the database users namespacel usernamel namespace2 username2 Specifies users that can access the sign on If you omit namespace the default Cognos namespace will be used Example This example adds a DB2 data source named ITM that can be accessed by tipadmin
186. se images The image directory is displayed as empty Causes WebSphere Application Server does not support WebDav Resolving the problem Type the image URL as a relative path For example tivoli tcr_common images tivoli gif Your login session expires while working with the Common Reporting portlet Symptoms While working with Common Reporting portlet your session expires and a Cognos authentication window appears asking you to provide your user name and password Resolving the problem Click Cancel return to Tivoli Integrated Portal login screen provide your credentials and open the Common Reporting portlet again ODBC System DSN connections fail to test from the Tivoli Common Reporting server Symptoms On 64 bit Windows operating systems ODBC System DSN connections test successfully from the Windows ODBC utility but fail to test successfully from the 114 User Guide Tivoli Common Reporting server when creating a data source The following error message is displayed UDA SQL 0532 Data Source is not accessible Causes 64 bit Windows contains both a 32 and 64 bit version of the ODBC utility e The 32 bit version of the Odbcad32 exe file located in the system_drive Windows SysWoW32 folder e The 64 bit version of the Odbcad32 exe file located in the system_drive Windows SysWoW64 folder 64 bit applications only see the data sources defined from the 64 bit Windows ODBC utility The same happens for 32 bit Th
187. see Configuring IBN Cognos 8 Components to Use an Authentication Provider ot IBMCognos information center 6 Test the connection configuration to verify it before saving 7 Select Cognos entry and edit the Allow anonymous access field changing it to False 8 Save the new configuration Results Important When you have configured LDAP the reporting portlet can no longer be used by users not contained in the configured LDAP Configuring Tivoli Common Reporting for Tivoli Integrated Portal future upgrade Learn how to configure your Tivoli Common Reporting instance before you decide to upgrade Tivoli Integrated Portal About this task Tivoli Common Reporting is installed on Tivoli Integrated Portal as might be other products in your infrastructure If you are planning to upgrade your Tivoli Integrated Portal instance in the future you need to configure Tivoli Common Reporting binaries to ensure that your environment will function properly Configuring Tivoli Common Reporting for future upgrade of Tivoli Integrated Portal 64 User Guide Configure Tivoli Common Reporting installed on the same computer as Tivoli Integrated Portal to work on a higher Tivoli Integrated Portal version Before you begin Provide all the necessary credentials in the TCR_component_dir integration reconfiguration reconfiguration properties file If you have installed Tivoli Common Reporting in distributed scenario perform these steps for
188. stallation procedure cognos_reporting_engine first step of the distributed installation scenario INSTALLATION_SCENARIO cognos_reporting_engine ui_for_cognos second step of the distributed installation scenario INSTALLATION SCENARIO ui_for_cognos single_computer_installation integrate_existing_cognos INSTALLATION SCENARIO single_computer_instal lation Port number for IBM Cognos content database COGNOS_CONTENT_DATABASE_PORT 1527 Tivoli Integrated Portal configuration related WebSphere information Enter a WebSphere Application Server administrator user name and password If the password is not provided the installer will fail WAS_USER_NAME tipadmin WAS_PASSWORD ti padmin Should it be upgrade PERFORM _UPGRADE false Following variables are for upgrade only Chapter 2 Installing 25 26 User Guide Path to the previous instance of TCR or migration package UPGRADE_SOURCE opt IBM tivoli tip or on Windows systems note double backslashes UPGRADE_SOURCE C IBM tivoli tip Define type of the upgrade source existing instance or a migration package Valid values instance package UPGRADE_MODE instance These are only for upgrade from existing instance of TCR PREVIOUS_INSTANCE_USER_ID tipadmin PREVIOUS_INSTANCE_USER_PASSWORD xxx Enter the ports that WebSphere
189. stem the following link error is reported java lang UnsatisfiedLinkError java awt Component initIDs V at at at at at at at at at at at at at at at at at at java awt Component lt clinit gt Component java 595 java lang J9VMInternals initializeImp Native Method java lang J9VMInternals initialize J9VMInternals java 192 java lang J9VMInternals initialize J9VMInternals java 157 java lang J9VMInternals initialize J9VMInternals java 157 com zerog ia installer util BidiUtilImp setDefaultLocale DashoA10 ZeroGay a DashoAl10 com zerog ia installer LifeCycleManager j DashoAl0 com zerog ia installer LifeCycleManager e DashoAl0 com zerog ia installer LifeCycleManager a DashoAl0 com zerog ia installer LifeCycleManager a DashoAl0 com zerog ia installer Main main DashoAl0 sun reflect NativeMethodAccessorImp invokeO Native Method sun reflect NativeMethodAccessorImp1 invoke NativeMethodAccessorImp1 java 64 sun reflect DelegatingMethodAccessorImp1 invoke DelegatingMethodAccessorImp1 java 43 java lang reflect Method invoke Method java 615 com zerog 1ax LAX aunch DashoA10 com zerog 1ax LAX main DashoA10 YH Sw WH Causes The problem is in the InstallAnywhere code that requires extra libraries to be installed into the system Resolving the problem Run the installer in debug mode to discover what kind of library is missing 1 2 3 Set the installer for DEBUG mode by run
190. stions on the capabilities of non IBM products should be addressed to the suppliers of those products This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the examples include the names of individuals companies brands and products All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental IBM Corp 2010 Trademarks 142 User Guide IBM the IBM logo and ibm com are trademarks or registered trademarks of International 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 www ibm com legal copytrade shtml Index A application server FIPS enablement 86 architecture overview 1 C clustered environment configuring 69 Common Reporting ad hoc reports performing 102 overview 91 report packages importing 101 reports Web based authoring 103 working 99 sample report 100 running 99 troubleshooting 114 configuration clustered environment 69 database 82 DB2 82 MS SQL 83 Oracle 84 Framework Manager connection 81 LDAP 62 Cognos based Tivoli Common Reporting engine 63 Tivoli Common Reporting Server 62 overview 61 security 88 89 console mode installation 20 console mode uninstallation 41 D
191. t the server as described in Clear the cookie files in your browser before running the application Results You have migrated from a single computer installation to a distributed installation What to do next Export and import your data Importing data Import data from the previous Tivoli Common Reporting instance to preserve them You can also use this procedure to move data from one system to another for example from test to production environment provided the systems are configured in the same way Procedure Changing ports for the Tivoli Common Reporting console You can assign new ports to an installed Tivoli Common Reporting console Procedure 1 Create a properties file containing values such as host name that match your environment The exemplary properties file below uses default values Modify the values to match your environment Save the file in any location WAS_HOME C ibm tivoli tip22 was install root C ibm tivoli tip22 profi leName TIPProfile profilePath C ibm tivoli tipv2 profiles TIPProfile templatePath C ibm tivoli tipv2 profileTemplates default nodeName TIPNode cel 1Name TIPCel1 hostName your_TCR_host portsFile C ibm tivoli tipv2 properties TIPPortDef properties Edit the TCR_install_dir properties TIPPortDef properties file to contain the desired port numbers Stop the Tivoli Common Reporting server by navigating to the following directory in the command line interface MEN TCR
192. tegrated Portal configuration such as security or user registry configuration To access the advancedTivoli Integrated Portal configuration read the post installation tasks section inTivoli Integrated Portal information center 90 User Guide Chapter 5 Common Reporting The Common Reporting component provided by IBM Cognos 8 Business Intelligence Fe E Reporting application embedded in Tivoli Fa FJ T Integrated Portal interface contains several additional advanced reporting functions Common Reporting functions See the top tasks you can perform with the embedded Cognos 8 Business Intelligence Reporting application e E mailing reports on page 102 Performing ad hoc reporting on page 102 e Web based report authoring on page 103 Using the Common Reporting within the Tivoli Integrated Portal interface Signing in to the interface You can now use one login and password to access Common Zeer application while keeping the security options For details see Singiel sign on SSO on page 7 Viewing the advanced reports in the interface context Launch the Cognos reports within the context of Tivoli Integrated Portal framework They can now be displayed with the use of launch in context logic which generates the appropriate report URLs Mapping the advanced reporting interface to the original Cognos 8 Business Intelligence Reporting application The original Cognos interface is modified to match
193. tep must be true for an object to be found You can use logical or comparison operators and searchable properties as a predicate expression Use to specify the property name The list below contains examples and descriptions of search path parameters that you can use to construct your search path w Selects the account object associated with the current user Selects the session object associated with the current user Selects the root Selects the child objects of the root The asterisk is a wildcard character folder Selects all folder objects in the content store When a path starts with two slashes all objects in the content store that fulfill the specified criteria are selected In this case the selected objects must be instances of the class folder folder report Selects all folder objects and all report objects in the content store The vertical bar specifies that the results of two search paths will be combined Selects all objects in the content store The asterisk is a wildcard character configuration Selects the configuration object and all its descendants The two slashes specify all descendant objects of the current object configuration and the current object itself The text between the slashes is called a location step The asterisk is a wildcard character content folder report parent folder Selects every descendant of the content object that is a folder obje
194. this task C tivoli is the default installation directory Procedure 1 Insert the product DVD or if you are installing from an image open the directory that contains the files that you have previously extracted 2 Start the installation launchpad UTS J aunchpad exe e and E launchpad sh Tip You can also run the installation wizard directly EON install bat Chapter 2 Installing 17 e and B install sh 3 Read the installation information and click Install IBMTivoli Common Reporting 2 1 1 Tip At any time of running the installation you can go back to the launchpad to access the on line documentation or the PDF version of the Installation Guide 4 Choose your installation language read the Welcome page and accept the terms of the license agreement 5 Select Install new instance of Tivoli Common Reporting as the installation mode 6 On the Installation scenarios page select Single computer installation Click Next 7 Choose the target directory for your installation and click Next Apart from the installation directory two new directories are created e C IBM tivoli tipv2 containing Tivoli Integrated Portal and e C IBM tivoli tipv2Components TCRComponent containing among others the component and scripts The directories are created because of Tivoli Integrated Portal 2 2 requirements 8 Create administrative user credentials for Tivoli Integrated Portal by choosing user ID and password a
195. tname port_number ibm console from the navigation tree on the left select Settings gt WebSphere Admin Console and Launch WebSphere Admin Console When the console opens in a new window perform the following steps a Go to Security gt Global security b Select Federated repositories from the available realm definitions then click Configure c Click Manage repositories under Related Items Then click Add to add a new LDAP Repository d Enter LDAP security setting information The primary host name and the distinguished name must contain no spaces e Select Require SSL communications if all LDAP communications should be encrypted f Select Centrally managed g Click OK base realm a Click Add Base entry to Realm Return to Global security gt Federated repositories and add an entry to the b Enter the distinguished name DN of a base entry that uniquely identifies this set of entries in the realm This base entry must uniquely identify the external repository in the realm c Click OK If multiple repositories are included in the realm use the DN field to define an additional distinguished name that uniquely identifies this set of entries within the realm For example repositories LDAP1 and LDAP2 might both use o ibm c us as the base entry in the repository So o ibm c us is used for LDAP 1 and o ibm2 c us for LDAP2 The specified DN in this field maps to the LDAP DN of the base entry within the r
196. to is called c8_locations and can be found in the following locations e For a single computer installation and for the user interface of the distributed installation TCR_component_dir cognos e For the reporting engine of a distributed installation TCR_install_dir cognos Preparing to install Verify that your environment meets basic requirements for an IBM Tivoli Common Reporting installation The installation program automatically verifies most requirements but you must check some prerequisites manually Preinstallation Step 1 Read the release notes Release notes contain late breaking information about installation To access the release notes go to http tivihelp v35r1 index jsp topic com ibm tivoli tcr doc_21 tcr_relnotes pdf Preinstallation Step 2 Verify the environment 14 User Guide Tivoli Common Reporting comprises a collection of components and applications that work together to form a powerful reporting system You must ensure that you meet the requirements for all the product components Make sure that you meet the prerequisites before you start to install the product e Verify the Hardware and software requirements e Choose your installation scenario e Gather all the following information required during the installation procedure Installation scenario Information required Single computer installation If you choose to configure the Lightweight Directory Access Protocol LDAP user and r
197. to log in twice because Framework Manager does not support single sign on Configuring database connection Configure the connection to a database to access your data Tivoli Common Reporting supports several database types Related information Lt TBM Cognos Administration and Security Guide 8 4 1 Data Sources and Connecting to a DB2 database 82 User Guide Connect Tivoli Common Reporting to a DB2 database Before you begin GA Perform this task with the support of a database administrator Make sure you have deployed the 32 bit DB2 database client on the machine where Cognos based Tivoli Common Reporting engine is installed The version of the client should match the version of your database About this task The configuration comprises of connecting the database to a client and activating optional cross database functionality Procedure 1 Windows Connect the DB2 database client to the database server by running the Configuration Assistant configuring the local net service name configuration and restarting your system For other operating systems see Configuring client to server connections in the DB2 information center Important Note the name of the connection you have created as it is used in one of the following steps Additionally for non Windows platforms the Tivoli Common Reporting must be able to find the native DB2 libraries To ensure this check if the DB2 directory containing libr
198. topTCRserver bat command MEET and MEUM TCR component_dir bin and running the stopTCRserver sh Note If the server does not stop terminate Tivoli Common Reporting processes 2 Remove the Deployment Engine by navigating to the following directory in the command line interface CAUTION Removing this component if you have other Tivoli Common Reporting or Tivoli Integrated Portal instances installed on your computer will prevent you from performing upgrades If you have other programs that use the Deployment Engine they may not work properly after removing it In this case see Uninstalling the Deployment Engine Windows a Open the command line interface and source the DE environment by evoking C Program Files IBM Common acsi setenv cmd b Uninstall DE C Program Files IBM Common acsi bin si_inst bat r f Note The command might fail if a DE operation ends abnormally In such case go to DE_install_dir asci logs and delete all files whose filenames begin with lock c Remove database backup rmdir s C Program Files IBM Common acsi and Ma Note For a non root user Deployment Engine is located at lt USER_HOME_DIR gt acsi Follow the same steps modifying your file paths a Source the DE environment by evoking the following command var ibm common acsi setenv sh Important Make sure you include the dot and space characters when running the command b Uninstall DE usr ibm common
199. tructions Choose to upgrade the existing Tivoli Common Reporting instance Choose Single computer installation as the upgrade scenario Select the installation directory and the existing instance of Tivoli Common Reporting to be upgraded Provide the administrative user credentials Specify the administrative user credentials that you used to log in to the previous version of Tivoli Integrated Portal and the port number that you want to use to create Tivoli Integrated Portal profile On the IBM Cognos Content Database panel provide the port number for IBM Cognos Content database The default port number is 1527 Remember The ports you select must be free and must be different from the ports used by the previous Tivoli Common Reporting instance The default Tivoli Integrated Portal port numbers are the same as the default port numbers in Tivoli Common Reporting version 1 3 When upgrading these port numbers must differ Decide whether you want to import report snapshots Attention Importing report snapshots may take a while especially if there are many BIRT reports in your infrastructure because each BIRT snapshot is run and exported into a PDF file Confirm your choices to begin the upgrade process No more action is required on your part Results You have upgraded to Tivoli Common Reporting version 2 1 1 and the following data was imported Database drivers Report snapshots were generated to PDF format and saved as s
200. ualHost Name 46311 gt lt VirtualHost Name 80 gt lt VirtualHost Name 443 gt lt VirtualHostGroup gt lt ServerCluster Name serverl Cluster CloneSeparatorChange false LoadBalance Round Robin PostBufferSize 64 IgnoreAffinityRequests true PostSizeLimit 1 RemoveSpecialHeaders true RetryInterval 60 gt lt Server Name server1 CloneID 12346 ConnectTimeout 5 ExtendedHandshake false ServerIOTimeout 60 LoadBalanceWeight 10 MaxConnections 1 WaitForContinue false gt lt Transport Hostname tiv isc02 cn ibm com Port 36310 Protocol http gt lt Transport Hostname tiv isc02 cn ibm com Port 36311 Protocol https gt lt Property name keyring value C Program Files IBM HTTPServer Plugins plugin key kdb gt lt Property name stashfile value C Program Files IBM HTTPServer Plugins plugin key sth gt lt Transport gt lt Server gt lt Server Name server2 CloneID 12345 ConnectTimeout 5 ExtendedHandshake false ServerIOTimeout 60 LoadBalanceWeight 1 MaxConnections 1 WaitForContinue false gt lt Transport Hostname tiv isc02 cn ibm com Port 46310 Protocol http gt lt Transport Hostname tiv isc02 cn ibm com Port 46311 Protocol https gt lt Property name keyring value C Program Files IBM HTTPServer P1ugins ha2 plugin key kdb gt lt Property name stashfile value C Program Files IBM HTTPServer Plugins ha2 plugin key sth gt lt Transport gt lt
201. un history of the report for which it was generated 7 Disable anonymous access from VMMProvider a Open the IBM Cognos configuration by running EOT Start gt All Programs gt Tivoli Common Reporting gt IBM Cognos Configuration e EE User interface TCR_component_dir cognos bin tcr_cogconfig sh reporting engine TCR_install_dir cognos bin tcr_cogconfig sh b Select Security gt Authentication gt Cognos in the navigation on the left and edit the Allow anonymous access field changing it to False c Save your configuration and restart the Tivoli Common Reporting server Upgrading distributed environment 48 User Guide Select this scenario to upgrade Tivoli Common Reporting versions 1 3 or 2 1 installed in distributed environment to version 2 1 1 You can upgrade interactively with the installation wizard as a single point of reference for the whole upgrade process or in silent mode which does not require any interaction on your part Before you begin Ensure that you have completed the following tasks e Ensure that you know the administrative user login and password e If you are upgrading from Tivoli Common Reporting version 1 3 or 2 1 ensure that all your report images are in the TCR_install_dir profiles TIPProfile installedApps TIPCel1 IBM Cognos 8 ear p2pd war tivoli directory because only this directory is moved over to version 2 1 1 If you are upgrading from version 1 3 and you have LDAP configured to
202. ups to roles Note Global repositories should never be updated manually During normal operation within a cluster updates that require synchronization are first committed to the database At the same time the node that submits the update for the global repositories notifies all other nodes in the cluster about the change As the nodes are notified they get the updates from the database and commit the change to the local configuration If data fail to be committed on any given node a warning message is logged into the log file The node is prevented from making its own updates to the database Restarting the Tivoli Integrated Portal Server instance on the node rectifies most synchronization issues if not the node should be removed from the cluster for corrective action See Monitoring a load balancing cluster on page 74 for more information Manual synchronization and maintenance mode Updates to deploy redeploy or remove console modules are not automatically synchronized within the cluster These changes must be performed manually at each node For deploy and redeploy operations the console module package must be identical at each node When one of the deployment commands is started on the first node the system enters maintenance mode and changes to the global repositories are locked After you finish the deployment changes on each of the nodes the system returns to an unlocked state There is not any restriction to the or
203. urce Note 1 Authentication with user userID and password password is required 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider Restriction Testing XML data sources is not supported by the command line Arguments add data_source_name Adds a new data source When used with force overrides the existing data source connectionName connection_name The name of the connection between the data source and the database If you do not specify it when adding a new data source the data source name will be used as connection name If you do not specify it when testing the database connection with the data source the first found connection will be used connection string connection_string Specifies the parameters of the database connection If you specify dbType connectionString must contain database specific connection string If you do not specify dbType connectionString must contain fully qualified Cognos connection string collation collation_sequence Specifies the collation sequence dbType Specifies the type of the database such as DB2 Oracle ODBC or XML If you specify a database other than one of these you must provide the exact Cognos connection string dbName database_name Specifies the name of the database dbLogin database_login The database login needed to access the database dbPassword database_password Specifie
204. urces help Use this syntax to list the connections defined in the specified data source tremd list connections cognosSearchPathOrDataSourceName help Note 1 Authentication with user userID and password password is required in all cases 2 If you have configured more than one user repository specify the namespace value By default namespace points to VMMProvider Arguments authorizations Lists authorizations to reports packages and folders for specified users connections cognosSearchPathOrDataSourceName Lists connections defined for the specified data source You can use the Cognos search path or data source name dataSources Lists data sources defined in Content Store entity cognosSearchPath The search path of an object in the Cognos Content Store help Displays syntax and usage information of a command flag report cognosSearchPath The Cognos search path of an existing report The search path of each report can be found in the web interface in Properties view Chapter 7 Reference 135 reports Lists available reports When used with the reportSet command flag this argument displays the reports associated with the specified folder or package reportSet cognosSearchPath The search path of an existing folder or package reportSets Lists available folders and packages When used with the reportSet flag this argument displays the folders and packages that are children of the specified fo
205. us version of Tivoli Common Reporting 7 Confirm your choices The upgrade process runs in the background Upgrading with the use of a package To upgrade across computers you can upgrade your Tivoli Integrated Portal instance on a computer different than the one on which the existing version is installed It also requires less free memory than the wizard upgrade mode About this task To upgrade in this mode you need 2 GB of available memory You can upgrade in this mode in both single computer and distributed scenarios but the distributed scenario is available for versions 1 3 and 2 1 only When upgrading from Tivoli Common Reporting version 2 1 Tivoli Integrated Portal is not upgraded You can upgrade Tivoli Integrated Portal to version 2 2 manually Upgrading using a package in single computer scenario Generate a package that contains all the data from your existing Tivoli Common Reporting instance and upgrade to a higher version Before you begin e Ensure that you know the administrative user login and password e If you are upgrading from Tivoli Common Reporting version 1 3 or 2 1 ensure that all your report images are in the TCR_install_dir profiles TIPProfile instal ledApps TIPCel1 IBM Cognos 8 ear p2pd war tivoli directory because only this directory is moved over to version 2 1 1 e If you are upgrading from version 1 3 and you have LDAP configured to connect directly with Cognos enable anonymous access from VMMProvid
206. use this method the data source properties for reports can access the data source using JNDI without directly specifying the JDBC information Before you begin Data sources are configured in the embedded WebSphere Application Server environment To use scripting you must start the WebSphere wsadmin tool For Chapter 5 Common Reporting 97 more information refer to the WebSphere Application Server documentation at publib boulder ibm com infocenter wasinfo v7r0 topic icom ibm websphere nd iseries doc info iseriesnd ae txml_script html Any JDBC driver properties required by your database vendor must also be set as data source properties in the WebSphere Application Server configuration For more information refer to the WebSphere Application Server documentation and the documentation for your database software If you have Tivoli Common Reporting installed in distributed environment the reporting engine runs on a Tomcat web server In such case the JNDI data sources must be configured on that server For more details see Tomcat documentation Procedure 1 Configure a JDBC provider 2 Configure a JDBC data source and its JNDI name Configuring JDBC data sources for direct access You can set up JDBC drivers for direct access by reports without using JNDI About this task To set up direct JDBC access Procedure 1 Copy the required JDBC driver files to the following directory TCR_component_dir lib birt runtime
207. utility included in the Cognos Modeling product The installation image for Cognos Modeling is located on the Tivoli Common Reporting Windows image in the following location CognosModeling win32 issetup exe for Windows operating systems and as a separate image for non Windows systems Beginning with Tivoli Common Reporting 2 1 1 you can install Framework Manager on a 64 bit computer but it must be installed in a separate directory from the 64 bit components Procedure 1 Run the installation image and provide all the necessary parameters Note If you are installing the 64 bit Framework Manager create a FrameworkManager directory in the TCR_component_dir directory and select it as the Framework Manager installation path 2 If you installed a 32 bit Tivoli Common Reporting server on a remote host or in a different directory install the Cognos FIPS package by running CognosModel ingFix win32 issetup exe Specify the same installation directory as the directory you specified for Framework Manager If you installed a 64 bit Tivoli Common Reporting server do not install FIPS Verifying the installation After you have installed the reporting solution access it in a Web browser to verify its installation Procedure 1 Log in to the Tivoli Integrated Portal and verify that the reporting section is present in the left hand navigation bar under Reporting For instructions on logging in to the reporting interface see the information c
208. vide the DB2 administrator s credentials Query synchronization of modules Use this command to determine if all nodes have identical sets of modules deployed HATool bat sh modules username password byNodes showAl The following parameters are optional e byNodes Specifies that the results of the command are ordered by the node in the cluster This parameter is optional The default is to list the results by module e showAll Specifies that all modules and nodes in the cluster should be returned This parameter is optional The default is to return only modules for unsynchronized nodes Query the synchronization of global repositories Use this command to determine if all repositories are synchronized on all nodes HATool bat sh repositories username password byNodes showAl1 The following parameters are optional e byNodes Specifies that the results of the command are ordered by the node in the cluster This parameter is optional The default is to list the results by repository e showAll Specifies that all modules and nodes in the cluster should be returned This parameter is optional The default is to return only repositories for unsynchronized nodes Release the global lock Use this command to manually release the global lock placed on all of the console nodes when the cluster is in maintenance mode This command is used when a node cannot commit a change during synchronization and has to be taken offline HA
209. wing lines to the startTCRserver sh script located in TCR_component_dir Setup Cognos and DB2 Environment LIBPATH opt IBM tivoli tipv2Components TCRComponent cognos bin export LIBPATH PATH PATH opt IBM tivoli tipv2Components TCRComponent cognos bin export PATH home db2inst1 sql1ib db2profile Uninstalling the Deployment Engine to complete Tivoli Common Reporting manual uninstallation 112 User Guide Uninstalling the Deployment Engine if there are other products using it is risky and may cause the products to work improperly To avoid this situation uninstall the Deployment Engine using Tivoli Common Reporting scripts Symptoms Manual uninstallation of Tivoli Common Reporting involves removing the Deployment Engine and therefore cannot be completed if there are other products using the Deployment Engine Resolving the problem Create the following scripts to uninstall the Deployment Engine echo off setlocal SET TCR_HOME 1 SET COMMON_SETENV1 ProgramFi1es IBM Common acsi setenv cmd SET COMMON_SETENV2 ProgramFi les x86 IBM Common acsi setenv cmd IF EXIST COMMON_SETENV1 GOTO COMMONSET1 IF EXIST COMMON _SETENV2 GOTO COMMONSET2 GOTO EMPTYSET COMMONSET1 CALL COMMON_SETENV1 GOTO FOUND COMMONSET2 CALL COMMON_SETENV2 FOUND call listIU v findstr v SoftwareIUTypeID findstr RootIUTypeID findstr i TCR_HOME gt TEN for F tokens 4 delims j IN TEMP tempDE fi
210. with a large user population When a node within a cluster fails new user sessions are directed to other active nodes Work load is distributed by session not by request If a node in the cluster fails users who are in session with that node must log back in to access the Tivoli Integrated Product Any unsaved work is not recovered You must have some experience with Lightweight Directory Access Protocol LDAP or the Tivoli Netcool OMNIbus ObjectServer DB2 and network dispatchers for example IBM HTTP in a distributed environment to successfully setup load balancing Synchronized data After load balancing is set up changes in the console that are stored in global repositories are synchronized to all of the nodes in the cluster using a common database The following actions cause changes to the global repositories used by the console Most of these changes are caused by actions in the Settings folder in the console navigation e Creating restoring editing or deleting a page e Creating restoring editing or deleting a view e Creating editing or deleting a preference profile or deploying preference profiles from the command line e Copying a portlet entity or deleting a portlet copy e Changing access to a portlet entity page external URL or view e Creating editing or deleting a role e Changes to portlet preferences or defaults e Changes from the Users and Groups applications including assigning users and gro
211. y that you wish to use You can use the image beside each chart as a reference Stylize the chart using the properties editor Create tables by creating or editing a query referencing the data set annotations Select the Query tab in the report editor then drag and drop the data items into the columns of the Cognos list Ensure that the Query property value matches the name of the query that you wish to use Stylize the chart using the properties editor i Create heat charts and cross tabs for your report by creating or editing a query referencing the data cube annotations To do this select the Query tab in the report editor then drag and drop the data items into the columns rows and corner of the cross tab Ensure that the Query property value matches the name of the query that you wish to use For heat charts you need to delete the list that was generated during report conversion and add a cross tab item in its place Note any styles applied to the list so you can add them to the new cross tab Add conditional styling to the cross tab by right clicking the cross tab intersection and selecting Style gt Conditional styles for displaying different styles for different values Use advanced conditional styling when using expressions to define the styles for each value otherwise use a regular conditional style j Create queries for your reports Charts tables and parameters require a query to retrieve and display data Each chart a

User Guide - Wikis on enterpriselab.ch

Contents

Download Pdf Manuals

Related Search

Related Contents