1. Cognos 8 BI Configuration, Administration, and Upgrade Cognos 8 BI

2. Objectives  In this module we will examine:  Installation & Configuration  Administrative Features  Upgrade

3. AGENDA  Installation & Configuration  Installation Functionality  Cognos Configuration  Standby Dispatchers  CM Conformance  Administrative Features  Upgrade

4. Installation and Configuration Summary  Installation and configuration is very similar to ReportNet (CRN) 1.1.  New features to address:  Available for distributed installations  Support for Metric Studio and Cognos 8 installation to the same location with shared components  Test capability from Cognos Configuration and improved feedback on system initialization

5. Installation  Install essentially identical to CRN 1.1  “Report Server” component has been renamed to “Application Tier Components” and is shared by Metric Studio  Transfer enhancements detecting (in)compatible installed components

6. Installation Over Existing Product – CRN 1.1  No major changes from CRN 1.1 in supported installations  Must uninstall prior version to install over existing installation  Installation directly over a CRN 1.1 installation is physically prevented

7. Installation To Existing Location – Cognos 8  Installer detects the existence of a compatible installation  warns before continuing

8. Installation To Existing Location – Cognos 8  If you continue with the installation you will be prompted to create a backup of the current files.

9. Install Over Directory While Software Still Running

10. Uninstall  It is now possible to uninstall components separately  Granularity:  Cognos Connection  Framework Manager  Metric Studio  Metric Designer  New Unix uninstall program replaces file deletion

11. Cognos 8 with Metric Studio – Cognos Configuration  The only visible difference is the Metrics Manager and Data Integration services appearing  The Metric store must be configured via a wizard and does not appear in Cognos Configuration

12. Cognos Configuration Property Restructuring  Environment properties have been grouped by component  “SDK URI” is now named “Dispatcher URI for External Applications”

13. Cognos Configuration: Test Capabilities  Ability to test database and Authentication Provider connections through Cognos Configuration  Content Store  Logging Database  Authentication Providers  Notification DB Note: In this example the mail server was not running

14. Cognos Configuration: Starting Cognos 8  To start Cognos 8, you must navigate to Environment/Cognos 8 Service then select Cognos 8 to start the service.

15. Cognos Configuration: Log Data Displayed  Log files relevant to starting and stopping components and services are now displayed interactively when “Details” is selected

16. Standby Dispatchers for a Gateway CRN 1.x  CRN 1.x Gateways can only communicate with a single dispatcher  Single Point of Failure if dispatcher goes down  To mitigate Cognos specified router between gateways and dispatchers Content Store DB Gateways Report Server Active CM Report Server Standby CM

17. Standby Dispatchers for a Gateway Cognos 8  Gateway detects primary dispatcher failure and routes to standby(s)  Removes Single Point of Failure in CRN 1.x  Automatically returns to primary once return to service detected

18. Get Java Information  Ctrl+F3 will show all the Java properties  Get Java path, version, installed location  See the installed components

19. CM Conformance  New Supported Content Store:  Sybase ASE version: 12.5.1 via Sybase's JConnect 5.5  Existing DB conformance updated to match Tier 1 reporting DB conformance

20. Before You Install  Before you install the software you need to know:  Is this the first time ReportNet has been installed on this machine?  If Yes, then proceed with standard install.  If No, then are you installing a new instance or are you upgrading?  If you are installing a new instance, then proceed with standard install, except if you have to create a new content store. You then need to point to the new content store. Pointing to an old content store will automatically upgrade the content store.

21. First Time Installing ReportNet on a Machine  Proceed with standard install  Create the default Web aliases  Create the standard content store  Restore the databases using the default names  Deploy the samples

22. CRN 1.x and Cognos 8 in Separate Instances  Proceed with standard install with a few exceptions:  Create a new content store and change the configuration to use the new content store. Pointing to an old content store, will automatically upgrade the content store.  Create the Web aliases.  Restore the databases. For example restore GOSL to GOSL2. The tables have changed between CRN 1.x and Cognos 8.  Deploy the package.  Change the data source connection using Cognos Connection.  You must republish FM models and upgrade all the reports.

23. Upgrade Instance, Keep CRN 1.x Intact  Proceed with standard install with a few exceptions:  Create a new content store and change configuration to use the new content store. Pointing to an old content store, will automatically upgrade the content store.  Create the Web aliases.  Restore the databases. For example restore GOSL to GOSL2. The tables have changed between 1.x and Cognos 8. If you are upgrading, you can re-use the same data source connections (optional step).  Import Deployment package from CRN 1.x.  Change the data source connection using Cognos Connection if required.

24. AGENDA  Installation & Configuration  Administrative Features  User Account Management  Report Server Affinity  Publishing PowerCubes  Auditing  Upgrade

25. User Account Management: Deleted Accounts  CRN 1.1 had no way to detect or remove content associated with a namespace account that no longer exists  Content Store Consistency Check is new for Cognos 8  Initially detects and corrects user accounts that no longer exist

26. Content Store Consistency Check  Consistency Check can be run for either a specified namespace or all namespaces  Can be used to find obsolete references or find and fix  Administrator must be logged into any namespace that is to be checked

27. Consistency Check Results Options

28. Consistency Check Results (find)

29. Consistency Check Results (fix)

30. User Account Management: Administrator Copy  Administrator now has ability to:  Copy account information to another user  Delete a user account

31. User Account Management: Administrator Copy (cont’d)  Copying can be done between existing accounts with options

32.  Administrator can also use the Directory tool to copy content between users User Account Management: Administrator Copy (cont’d)

33. Report Server Affinity  A number of customers would like the ability to restrict which servers in their environment handle certain users or certain content.  Cognos 8 allows an administrator to configure designated servers which should process requests on basis of:  Group/Role  Package  This is accomplished by:  Assigning users/packages to Routing Sets  Assigning Routing Rules to Dispatcher server groups designating which Routing sets can be processed

34. Report Server Affinity: Defining Routing Sets  Navigate to the properties pane of either a package or user group  Define routing sets

35.  Type the name of the routing set of which you would like this object to be a member of  The default routing set name is based on the object name Report Server Affinity: Defining Routing Sets

36. Create a Server Group Name

37.  Go to the “Configure” tab of the Server Administration tool and select “Specify Routing Rules” Report Server Affinity: Defining Routing Rules

38.  Add rules directing Routing sets to server groups  Server groups must already be defined prior to defining rules Report Server Affinity: Defining Routing Rules

39. Audit Logs  No significant changes to Audit logs or tables  Analysis studio usage will be logged similarly to existing CRN logs  Native Query table will log MDX queries vs. SQL

40. AGENDA  Installation & Configuration  Administrative Features  Upgrade  Content Store Upgrade  Deployment Upgrade  Upgrading reports  Metadata Upgrade  SDK Upgrade/Compatibility

41. Scope of Upgrade Discussion  Upgrade from CRN 1.x  CRN 1.1 to Cognos 8 supported directly  CRN 1.0.x requires intermediate upgrade to 1.1  Upgrade of CRN 1.x SDK applications  Not including  Migration of IWR to Cognos 8  Migration of Series 7 PowerPlay content to Cognos 8

42. Upgrade – Background Information  Cognos 8 includes significant changes to report specifications and metadata models.  Cognos 8 studios will only save Cognos 8 format reports, queries, and analysis.  Cognos 8 Report Servers will only natively execute Cognos 8 format report specifications.

43. Upgrade – Considerations  Some customer SDK applications access, manipulate & save reports with CRN 1.x format.  Either keep the report specifications in 1.x format or alter the SDK application to reflect Cognos 8 report specifications.

44. Content Store Upgrade  Content Store Upgrade:  Performed from Cognos Configuration when Cognos 8 is first started  Content Store schema, Cognos 8 object changes and published model upgrades occur automatically  Customer can optionally upgrade reports to Cognos 8 format

45. Initiating an Upgrade of Content Store  Upgrade requirements detected when configuration saved in Cognos Configuration  Additional step added to tasks performed

46. Initiating an Upgrade of Content Store (cont’d)  Upgrade requirements detected when configuration is saved in Cognos Configuration  When an upgrade is required the user is prompted to upgrade reports

47. Initiating an Upgrade of Content Store (cont’d)  Upgrade performed when service is started  Start Service Dialog and the log file contain information about upgraded content  Following startup, users can log into Cognos Connection as usual

48. Demo 1  System Upgrade

49. Upgrading via Deployment  CRN 1.x deployment packages can be imported into a Cognos 8 installation  You can choose to upgrade report specifications or keep them in their current format

50. Upgrading Reports After System Upgrade  Saving a report from the Studios will automatically upgrade the report  Bulk upgrade is available from the Content Administration Tool  Upgrade reports by containing folder or by associated package  Upgrades can be scheduled if desired

51. Upgrading Reports After System Upgrade (cont’d)  Select folders and packages

52. Upgrading Reports After System Upgrade (cont’d)  Select whether you want reports:  located in folder/package  based on a package  Note: Upgrading based on a package is the only way to automatically upgrade mypages content.

53. Upgrading Reports After System Upgrade (cont’d)  The results of upgrades are available in the run details

54. Published Metadata Upgrades  Published packages will be upgraded when the content store is upgraded  No option to maintain CRN 1.x format reports is required since all reports in previous formats will be upgraded at runtime

55. Upgrading Models in Framework Manager  You must use Cognos 8 FM to publish to Cognos 8  Cognos 8 FM is compatible with CRN 1.x action logs  Existing FM models:  Upgraded automatically when they are first opened in FM  Models will be incompatible with CRN 1.x once saved from Cognos 8  The automatic FM upgrade will be identical to that performed on published packages  Additional modeling will be required to make an existing package usable in Analysis studio

56. Upgrading SDK Applications: General  Intent is for CRN 1.x SDK applications to run with minimal changes.  All SDK applications must be:  recompiled against Cognos 8 SDK  SDK Version changed to match Cognos 8 SDK  Enumerations:  New values may exist corresponding to new Cognos 8 objects  Applications not coded to best practices regarding objects of unexpected types may encounter problems  Following these changes, CRN 1.x applications should run as they did before the upgrade.

57. Upgrading SDK Applications: Report Specifications  Often XML files such as report specifications are passed in SDK functions.  Cognos 8 SDK will accept CRN 1.x formatted report specifications or Cognos 8 formatted report specifications.  SDK applications can continue to access, update and save CRN 1.x formatted reports to the Cognos 8 content store.  CRN 1.x reports will be converted to Cognos 8 format in memory at runtime.  Limitations:  Any report saved from a studio will be converted to Cognos 8 format  Conversion of report in memory will affect performance  Only CRN 1.x functionality available via CRN 1.x specifications

58. Upgrading SDK Applications: Metadata  All models in Cognos 8 Content Store will be in Cognos 8 format.  Upgraded packages will continue to supply the same response to CRN 1.x SDK applications using:  Get Metadata  Update Metadata

59. Upgrading SDK Applications: Exceptions  The following exceptions to SDK application backwards compatibility apply:  Deployment Specifications are changing locations. Applications accessing these in their CRN 1.x locations will encounter problems.  Run Histories are generalized in Cognos 8 to a single class for all runnables. Applications accessing existing CRN 1.x histories will encounter problems.  Account object PortalPage and PortalProperties redesigned for Cognos 8. Applications accessing these will encounter problems.  QueryMetadata is not compatible with CRN 1.x.  Details of exceptions and deprecations are in the SDK Developer Guide.

60. Summary  In this module we examined:  Installation & Configuration  Administrative Features  Upgrade