180 likes | 288 Views
Matthew Glover - Advisory Software Engineer - matthewg@us.ibm.com 24 May 2011. Differences between TCR 1.3 and 2.1. Agenda. TCR history TCR 1.3 architecture TCR 2.1 architecture Similarities Differences Examples. TCR history. TCR 1.1. TCR 1.1.1. TCR 1.2. TCR 1.3. June 2007. TCR 2.1.
E N D
Matthew Glover - Advisory Software Engineer - matthewg@us.ibm.com 24 May 2011 Differences between TCR 1.3 and 2.1
Agenda • TCR history • TCR 1.3 architecture • TCR 2.1 architecture • Similarities • Differences • Examples
TCR history TCR 1.1 TCR 1.1.1 TCR 1.2 TCR 1.3 June 2007 TCR 2.1 TCR 1.2 Oct 2007 Oct 2008 Mar 2010 Now
LDAP TCR 1.3 architecture TIP Server TCR ISC/JSR168 Web UI BIRT Report Store BIRT BIRT Reports BIRT Data Sources iframe Cognos Reports Cognos Data Sources Cognos Server UI Cognos report processing Report Store
Cognos portlet in TIP for Cognos report administration TCR 1.3 architecture Existing TCR portlet for legacy reports View BIRT based Report View Cognos based Report
TIP 2.1-JSR168 Web UI Other Tivoli Products TCR Portlet Cognos Report Store Content Manager Report Engine TCR 2.1 architecture, single-computer WAS 7 Embedded Cognos UI contains Cognos and BIRT WAS Built In Repository (VMM-filebased) TCR Custom Authentication Provider LDAP (Optional) Cognos Dispatcher (+ static content) TCR CLI Report Data Cognos Report Specs Sources BIRT Report Metadata BIRT Report Specs and Resources BIRT Engine
WAS 7 TIP 2.1-JSR168 Web UI Other Tivoli Products TCR Portlet Cognos Gateway TCR CLI LDAP Cognos Dispatcher (Tomcat) TCR CLI Cognos Report Data Report Store Content Manager Sources Report Engine Cognos Report BIRT Report BIRT Engine TCR 2.1 architecture, distributed
Similarities • All previous versions of TCR reports are able to run with no changes • TIP continues as UI • Installation is still DE (Deployment Engine) based • Single-computer fresh installation
Differences • Upgraded versions of TIP, DE, WAS, IBM JRE, BIRT • Conversion Assistant • Removed BIRT report portlet • Advanced installation options removed • Updated CLI
Examples • Importing a BIRT report • Adding BIRT datasources • Manually adding Cognos reports
Importing a BIRT report – command syntax trcmd -import -bulk pkgFile [-reportSetBase rsBase] [-resourceBase resourceBase] [-designBase designBase] [-help] -user userID -password password • -bulk pkgFile • The local path and file name (including .zip extension) of the report package file to be imported. • -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 report designs in a package that have the same names and locations as existing designs in the data store.
Importing a BIRT report – actual example [root@tetsuo:/opt/IBM/tivoli/tipv2Components/TCRComponent/bin]# ./trcmd.sh -import –bulk /opt/IBM/ITCAMForSOAReports.zip -reportSetBase "/content/package[@name='Common Reporting']/folder[@name='BIRT']" -user tipadmin -password xyxyxyxy CTGTRQ092I Import operation successfully performed.
Adding BIRT datasources – command syntax trcmd -user userID -password password -modify -dataSources -reports [-reportName cognosSearchPath] -setDatasource p1 p2 p3 • -reportName cognosSearchPath - Specifies the search path to use when searching 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 p1 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: * name * displayName * comments * odaDriverClass * odaURL * odaUser * odaPassword * odaJndiName
Adding BIRT datasources – actual example • ./trcmd.sh -user tipadmin -password xyxyxyxy -modify -datasources -reports -reportname "/content/package[@name='Common Reporting']/folder[@name='BIRT']/package[@name='Tivoli Products']/folder[@name='ITCAM for SOA Reports']/folder[@name='Performance Reports']/report[@name='Report by Requester Identity']" -setdatasource odaDriverClass=com.ibm.db2.jcc.DB2Driver "odaURL=jdbc:db2://tetsuo:60000/WAREHOUS:currentSchema=ITMUSER;" odaUser=db2inst1 odaPassword=xyxyxyxy • Verification command: ./trcmd.sh -user tipadmin -password xyxyxyxy -list -report "/content/package[@name='Common Reporting']/folder[@name='BIRT']/package[@name='Tivoli Products']/folder[@name='ITCAM for SOA Reports']/folder[@name='Performance Reports']/report[@name='Report by Requester Identity']"
Manually adding Cognos reports http://www.youtube.com/watch?v=H_6g_oXpahM
Resources • TCR YouTube channel - http://www.youtube.com/user/TivoliCommonReport • TCR Information Center - http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_21/ic-home.html • TCR developerWorks - https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=9caf63c9-15a1-4a03-96b3-8fc700f3a364