INSTALLING COGNOS 10.2.1: TIPS TRICKS T - Senturus PDF Free Download

1y ago

25 Views

1 Downloads

2.69 MB

50 Pages

Report/dmca

Download PDF

Transcription

INSTALLING COGNOS 10.2.1:TIPS AND TRICKS FROM THE TRENCHESHow to Ensure a Successful Upgrade

Today’s Agenda Welcome Core Architecture of the BI Server The Ever-Growing Maze of Bitness (32 versus 64) Common Installation Problem Areas Using the Cognos Knowledge Base About Senturus 100 off Senturus Training Winners Q&ACopyright 2014 Senturus, Inc. All Rights Reserved3

Introduction: Today’s PresentersGreg HerreraPresident & CoFounderSenturusSteven Reed-PittmanPractice Director - SystemsIntegration & OptimizationSenturusCopyright 2014 Senturus, Inc. All Rights Reserved5

OVERVIEWCore Architecture of the BI Server(and Some Common Misconceptions)

COGNOS 10.2.1 BI SERVERCognos Connection web portalCORE COMPONENTSTier 1: WebTier 2:ApplicationTier 3: DataNote: Report Servers are part of the “Application TierComponents” in the Cognos installation program

COMPONENT SELECTION OPTIONSNote: The Cognos Content Database isn’tgenerally used in enterprise installations – it isonly recommended for use in demoenvironments.

CONTENT “*” CONFUSION: WHAT ARE THESE THINGS?Content Manager:The Cognos service that manages the storage andretrieval of report specifications, published packages,configuration data and Cognos security settings fromthe content store database.Content Store:The set of database tables that are used by theContent Manager to store Cognos application data.Cognos Content Database:Self-contained Apache Derby database server – canbe used to host the content store database in demoenvironments when an enterprise DBMS isunavailable.

WHATIS ADISPATCHER? The “Dispatcher” is a Java application which runs a configurable set ofCognos services, not just reports: A dispatcher can also route requests to other dispatchers for load balancing.

LOAD BALANCING BASICS Cognos load balancing is performed by the Dispatchers, not the Gateway. The gateway always sends its requests to a single dispatcher URI -- wecould call this the gateway’s “current” target dispatcher: The gateway’s “current” target dispatcher performs load balancing asneeded with the other dispatchers in the environment. The gateway will switch to a different dispatcher only if the “current”target dispatcher stops responding.

64-BIT IDENTITY CRISISThe Ever-Growing Maze of Cognos Bitness

32-BIT AND 64-BIT COMPONENTS Java code is architecture agnostic (can run on a 32-bit or 64-bit JVM) Some components are still strictly 32-bit native C code (e.g., BIBusprocesses for Compatible Query Mode)Java code(32-bit or 64-bit)C code (32-bit)

32-BIT COMPONENTS IN 64-BIT COGNOSThere are still some 32-bit-only components embeddedin 64-bit Cognos 10.2.1: Report execution processes for Compatible Query Mode(BIBusTKServerMain.exe) are still 32-bit 32-bit database client libraries are required for native-clientintegration with third-party databases.

SELECTABLE-BIT COMPONENTS IN 64-BIT COGNOSIn 64-Bit Cognos 10.2.1, some components aredelivered as BOTH 32-bit and 64-bit: Web gateway components have been available as both 32-bit and64 bit since Cognos 10.2.0 Both versions of the gateway components are installed wheneveryou install the 64-bit BI Server In 10.2.0, the 32-bit gateway components were used by default In 10.2.1, the 64-bit gateway components are now used by default Use the “copyGateMod.bat” script to switch between them

MORE SELECTABLE-BIT COMPONENTS IN 64-BIT COGNOSIn 64-Bit Cognos 10.2.1, the Report Server execution mode can beset to 32-bit or 64-bit: 32-bit execution mode allows the report server to handle CQM orDQM requests (DQM query requests are forwarded to the 64-bitQuery Service for execution) 64-bit execution mode allows the report server to handle DQM andDynamic Cubes requests ONLY (note: routing rules are needed ifrunning a combination of modes in one environment)

WHAT DIFFERENCE DOES IT MAKE? 32-BIT VERSUS 64-BIT 32-bit components are limited to a smaller amount of memory perprocess (4 GB max addressable) Out-of-memory errors can occur on complex reports when a BIBusprocess hits this limit. Even if additional memory is available onthe server, the BIBus process cannot use it. 64-bit components aren’t subject to the 4 GB memory limit, so theycan perform higher complexity, memory-intensive processing Dynamic Query Mode and Dynamic Cubes leverage 64-bitscalability to provide in-memory caching for high performance

THINGS GO WRONGCommon Installation Problem Areas

WHY THINGS GO WRONG: COGNOSIS NOT AN ISLANDFamous last words: ”How hard can this be don’t youjust, point, click and go?”External dependencies add unique and variable complexityin every environment, including:-network securityvirtual infrastructuredatabase access (SQL, Oracle, DB2, ODBC, JDBC)authentication mechanisms (AD, LDAP, Series 7)web server configurations (IIS, Apache, SSL)anti-virus and endpoint security solutions

WHERE THINGS GO WRONG:FOURCOMMON PROBLEM AREAS1) Operating System (Windows)2) Database (SQL Server, Oracle)3) Web server (IIS)4) Fix Packs

COMMON PROBLEM AREA #1Operating System

COMMON WINDOWS OSISSUES Service account not added to Local Administrators group

COMMON WINDOWS OSISSUES Cognos hasn’t been configured to run using the service accountcredentialsCheck theservice’sproperties

COMMON WINDOWS OSISSUES Data Execution Prevention (DEP) has not been configured toallow Cognos to runFor simplicity, DEP isenabled here for essentialWindows programs andservices only.Alternatively, individual DEPexceptions can also beexplicitly configured for Cognos.

COMMON WINDOWS OSISSUES Internet Explorer Enhanced Security Configuration is turned onSet IE ESC to “Off” inorder to access CognosConnection directly fromthe serverNote: This change is NOT required forbrowsers on client PCs to be able to connectto the server

COMMON PROBLEM AREA #2Database

COMMON DATABASE-RELATEDISSUES Incompatible collation sequence– The Cognos content store requires a case-insensitive collation sequence.Some common collation sequences for Cognos installations are: SQL Server: SQL Latin1 General CP1 CI AS Oracle: AL32UTF8 Oracle: Incorrect JDBC driver file for Content Manager– The correct JDBC driver must be copied from the Oracle client installationlocation to ./webapps/p2pd/WEB-INF/lib ojdbc6.jar is recommended for use with Cognos 10.2.1 Dynamic Query Mode: Spaces in the path to the JDBC drivers– Beware! DQM cannot handle spaces in the path to the JDBC drivers (e.g.,the default Cognos installation path “C:\Program Files\ibm\cognos\.” )– Use something like “C:\ibm\cognos\.” as your installation path instead.– See the IBM Cognos 10 Dynamic Query Cookbook for additional details onrequired JDBC driver files and configurations for DQM.

COMMON SQL SERVERANDORACLE DBISSUES Incorrect bitness of database client software– For Compatible Query Mode (CQM) access to third-partydata sources, 64-bit Cognos 10.2.1 still requires 32-bit clientlibraries. For Oracle, you must explicitly install the 32-bit Oracleclient libraries when running Cognos on 64-bit Windows. For SQL Server, the 64-bit SQL Native Client includesboth 32-bit and 64-bit libraries.

COMMON PROBLEM AREA #3Web Server

COMMON IIS CONFIGURATIONISSUES Role Services have not been installed for ISAPI and WindowsAuthenticationBoth of these shouldbe checked

COMMON IIS CONFIGURATIONISSUES Application Pool Identity not set to “NetworkService”Change identity to“NetworkService”

COMMON IIS CONFIGURATIONISSUES Application Pool not configured properly for the bitness of thegateway extensionsSet “Enable 32-BitApplications” to Truewhen using the 32-bitgateway extensionsSet “Enable 32-BitApplications” to Falsewhen using the 64-bitgateway extensions

COMMON PROBLEM AREA #4Fix Packs

FIX-PACK MADNESS: WHICH FIXES TO INSTALL? 10.2.1 Fix Pack 1 10.2.1 Fix Pack 1 Dynamic Query Feature Bundle Unlike standard fix packs, FP1 also added new functionalitySupport for the RAVE visualization engine was added in FP1XML schema change for report specifications – requires a separate step toupgrade existing 10.2.1 content after applying FP1.Also known as 10.2.1.1 Interim Fix 3This is a separate install that goes on top of 10.2.1 FP1 to add enhancedcapabilities for DQM and Dynamic CubesThe Dynamic Query Feature Bundle MUST be installed before FP2 if itsfeatures are needed. It CANNOT be installed after FP2 has been installed.10.2.1 Fix Pack 2 Unlike standard Cognos fix packs, FP2 is not-quite-cumulative (it doesn’tinclude the Dynamic Query Feature Bundle changes)

RECOMMENDED INSTALL SEQUENCE FOR10.2.1 BI FIX PACKSTo get to the latest, most stable and most feature-complete version ofCognos 10.2.1, use the following install sequence:1.2.3.4.10.2.110.2.110.2.110.2.1base installFix Pack 1FP1 Dynamic Query Feature Bundle (aka 10.2.1.1 Interim Fix 3)FP2

ADDITIONAL GOTCHAS:10.2.1 MOBILE FIX PACKS Mobile adds a further layer of complexity to the Fix Pack process:– Cognos Mobile 10.2.1 has its own, separate Fix Packs– The latest SERVER-SIDE Mobile Fix Pack is Mobile 10.2.1 Fix Pack 2, whichrequires BI 10.2.1 FP1 or later to be installed FIRST.– Mobile 10.2.1 Fix Pack 3 is also available now, but Mobile 10.2.1 FP3 is onlyan app upgrade (iOS/Android), not a server-side upgrade.Plan Carefully and Patch Carefully!

SOME FINAL NOTES- Keeping 32-bit Tools Separate- Disabling the Query Service to Save Memory

KEEPING 32-BIT TOOLS SEPARATE As always, the “pure” 32-bit client tools still can’t beinstalled in the same directory as the 64-bit BI Servercomponents. Because Framework Manager, Transformer and Cube Designer are32-bit components, they must be installed in a separate directoryfrom any Cognos BI 64-bit server components. The Dynamic Query Analyzer is available as both a 32-bit and a 64bit install.

THECOGNOS 10 QUERY SERVICEIf DynamicQuery Mode isnot being used,you can disablethe QueryService to savememory.The Query Service uses a dedicated JVM instance forDynamic Query Mode execution, which allocates 1 GB ofmemory by default at startup.

GETTING UNSTUCK:USE THE COGNOS KNOWLEDGE BASEThe knowledge base is (mostly) your friend

USINGTHEIBM COGNOS KNOWLEDGE BASE- Simple searches are more likely to produce relevant articles- Detailed searches are less likely to return anything at all oftware/Information Management/Cognos Business IntelligenceSelect “Search onlyCognos BusinessIntelligence” –otherwise, you’ll getresults for all IBMproducts

SENTURUS OVERVIEWWho we are

Senturus: Business Analytics ConsultantsBusinessIntelligenceEnterprise PlanningPredictive AnalyticsOur Team:Business depth combined with technical expertise.Former CFOs, CIOs, Controllers, DirectorsCopyright 2014 Senturus, Inc. All Rights Reserved43

Upgrade Assistance Free Estimate– With detailed steps Flexible model– Mentoring: train your resources to do the upgrade– Full service upgrade to your production environmentFor more information, contact:Jim Frazier, Vice-President of Client Solutions, Senturusjfrazier@senturus.com650 949 2921Copyright 2013 Senturus, Inc. All Rights Reserved.47

senturus.com888 601 6010info@senturus.com

The Cognos service that manages the storage and retrieval of report specifications, published packages, configuration data and Cognos security settings from the content store database. Content Store: The set of database tables that are used by the Content Manager to store Cognos application data. Cognos Content Database: