Ibm Cognos Bi Administration And Security Guide

1y ago
15 Views
1 Downloads
846.92 KB
14 Pages
Last View : 5d ago
Last Download : 5m ago
Upload by : Jenson Heredia
Transcription

Continue

Ibm cognos bi administration and security guide Author Theme: Cognos 10 Security and Management Guide - pdf (Read 18155 times) IBM Cognos Mobile extends the functionality of your existing IBM Cognos BI installation to mobile devices so that users can view and interact with Cognos BI content on their tablets or smartphones. With the Cognos Mobile rich client, users can view Report Studio COGnos BI reports and Cognos Workspace workspaces on their mobile devices. Reports and workspaces are interactive and optimized for viewing on mobile devices. COGnos BI request functionality and scheduling mechanism are used to deliver custom reports in a timely manner. Cognos BI security and various vendor-specific security mechanisms, including device- and server-based security, are used to protect report and workspace content. Many of the device-specific management servers and management tools used by Cognos Mobile offer the ability to remotely remove content from a device or disable the device altogether. For example, if a device is lost or stolen, the Cognos BI administrator can use this functionality to protect sensitive content on the device. The Cognos BI administrator can also set an expiration date for a report after which the report becomes inaccessible until the user re-authenticates. Cognos Mobile supports requests between the mobile device and the server environment for the following product features: After you install and configure IBM Cognos Mobile, you can perform management tasks to manage the delivery of Cognos BI content to mobile devices. The IBM Cognos Administration Mobile tab provides centralized management capabilities for Cognos Mobile. To access this tab, the administrator must have the necessary access permissions for the Mobile Administration functionality. Mobile administrators, one of the predefined roles in the Cognos namespace, can be used to specify access permissions for this functionality. Cognos Mobile uses the same set of users as Cognos Business Intelligence. For information about managing Cognos BI, see other sections of the IBM Cognos Business Intelligence Administration and Security Guide. For information about Cognos Connection, see the IBM Cognos Connection User Guide. Procedure 1. Open the Servlet Gateway web.xml file, located at install location/war/ gateway/ or in the servlet deployment directory, depending on the server you are using, in an editor that supports saving files in UTF-8 format. 2. Change the parameter values according to Necessary. <param-name>pingPeriod <param-value>180 <param-name>fileCheckPeriod <param-value>30 Procedure 1. On the Status tab, click System. 2. Click the Arrow on the Actions menu next to System and click Set Properties. Tip: You can also change the hotspot settings at the dispatcher or at the service level. 3. Click the Settings tab. 4. Select Adjustment from the Category list. 5. Locate the number of access points generated in a chart by Lot</param-value> </param-name> </param-value> </param-name> </param-name> the number of access points generated in a chart by the reporting service configuration. In the Value column, click the arrow next to Unlimited, and then click . Enter a new value for the maximum number of access points 6. 108 IBM Cognos Analytics Version 11.0.0: Administration and Security Guide Setting the Report Size Limit for the Report Data Service You can increase the size limit for report data. To limit resources, such as memory, used by the reporting data service, IBM Cognos software restricts the size of report data that can be sent. If you receive errors in IBM Cognos for Microsoft Office that a report result is too large, you can increase the size limit for report data by changing the governor's limit settings. The maximum runtime setting takes precedence over this setting. For more information, see Configuring the Maximum Runtime on page 106. Procedure 1. In IBM Cognos Administration, on the Status tab, click System. 2. In the Scorecard panel, on the Change Current View menu, click Services > Report Data. Tip: The current view is one of all servers, All Server Groups, All Distributors, or Services. 3. On the ReportDataService Actions menu, click Set Properties. 4. Click the Settings tab. 5. In the Value column, change the controller limit number (MB). 6. Click OK. Excluding the context ID of an agent from WebSphere web service tasks by default, when the agent service interacts with a web service, the agent context ID is included. If you are running an agent that includes a web service task in IBM WebSphere , you must exclude this context ID to avoid a conflict with the WebSphere context IDs themselves. Procedure 1. Follow the steps in the Configuring advanced settings for specific services section on page 573. 2. For AgentService, in the Parameter column, type asv.webservice.useRunContext. You must specify this setting on each AgentService instance that you are running. 3. Type true as the value for this parameter and click OK. 4. Restart IBM Cognos services. Tuning Metric Studio Connections You can set Metric Studio parameters that control the number of connections established with the database server and how long unused connections are left open. Unused data source connections can affect metric studio performance and performance of other applications on the server. Chapter 6. Managing Server 109 To determine the configuration to use, monitor connections to the database server periods of low, typical and high use. For specific instructions, see the data source documentation. For example, you have 500 users. Because keeping 500 connections open all the time could affect database server performance, set the initial number of connections to 100 and the maximum number of connections to 500. Set the timeout for unused connections to 10 minutes and set the time period between unused connection checks to 5 minutes. Set the increment connections to 10. 10. the number of open database connections changes in increments of 10 to match the user's load as it increases and decreases throughout the day. The following parameters are available: v initialConnections The number of connections that the Metric Studio service opens when a database is first accessed. These connections never close. They remain available to service the typical user load. Valid configuration is 0 to 30,000. The default value is 5. If you want to close all connections when they are not in use, set it to zero. v incrementConnections The number of connections that the Metric Studio service opens when more of the initial connections are required to handle user load. Connections are opened and closed in a block. Connections in a block are not closed until all connections in the block are used. Valid configuration is 1 to 30,000. The default value is 5. v maximumConnections The maximum number of connections that the Metric Studio service opens. The user receives an error when the maximum number of connections is reached and all assigned connections are processing other requests. Valid configuration is 1 to 30,000. The default value is 200. This setting must be greater than the initialConnections configuration. v connectionIdleTimeout The time in seconds when a connection is not used before it is closed. Valid configuration is 1 to 30,000. The default value is 3600 (1 hour). v connectionMaintenanceInterval The time in seconds that the Metric Studio service waits before checking for unused connections to be closed. Valid configuration is 1 to 30,000. The default value is 3600 (1 hour). You must have the necessary permissions to access IBM Cognos Administration. For more information, see Chapter 14, Secure Features and Functions, on page 231. Procedure 1. Follow the steps in the Configuring advanced settings for specific services section on page 573. 2. For the MetricStudioService, in the Parameter column, type one of the parameter names described in this section. For example, type connectionIdleTimeout. 3. In the Value column, type the associated value for the configuration. 4. Continue typing the configuration names and settings as needed. 5. Click OK 110 IBM Cognos Analytics Version 11.0.0: Administration and Security Guide 6. Restart the Metric Studio service for the new configuration to take effect. For more information, see Stop and Start Dispatchers and Services on page 76. Tune cache for the repository service You can adjust the cache for the repository service. There are several size properties that can be set for local memory and disk resources. The configuration can be unique in each The following table provides a description of the cache types that can be adjusted for the repository service. Table 35. Cache types available in the repository service Description Parameter Maximum number of seconds reports and report items can exist in the cache The maximum number of seconds that a report can exist in the cache, regardless of how often it is used. After a report expires, it recovers repository instead of the cache. The default value is 1200 seconds (20 minutes). A value of 0 means that the report is not cached. Maximum number of reports and report items that can be overflowed to disk The maximum number of cache entries to be kept in local memory. The default value is 1000 entries. A value of 0 means that there is no limit to the number of items held in local memory. Maximum number of reports and report items that can be stored in memory The maximum number of cache entries that can be written to the local disk. When the cache reaches the limit, items are overflowed to the local disk. The default is 100 reports and report items. A value of 0 means that there is no limit to the number of items written to disk. Entries are written to the location of the data files defined in IBM Cognos Configuration. The repository service uses the advanced repository.maxCacheDocSize configuration to specify, in megabytes, the maximum size of each report output that can be cached. Outputs that are larger than the specified size are not cached and should always be retrieved from the repository or Content Manager. The default value is 10. You can specify these advanced settings individually for a specific repository service or distributor, or globally for the entire IBM Cognos environment. For more information, see Appendix I, Advanced Configuration, on page 571. Simultaneous query execution Depending on your environment, you might be able to improve report execution performance by enabling concurrent query execution. By default, IBM Cognos software runs queries on a report sequentially. To do this, set advanced server properties for the reporting service, the batch reporting service, or both. When concurrent query execution is enabled, the report server determines which report queries can run concurrently. The report author must specify queries for a report that are candidates for concurrent execution. For more information, see the IBM Cognos Analytics Reporting User Guide. Chapter 6. Server Administration 111 RSVP. CONCURRENTQUERY. NUMHELPERSPERPROCESS Use this parameter to enable concurrent query execution and set the maximum number of query execution helpers for each reporting service or batch reporting service process. The default value is 0, which means that concurrent query execution is disabled. Each query execution helper results in an additional data source connection. For example, a Reporting has four processes with two high affinity connections and two low affinity connections: v If the maximum number of query execution helpers is set to 0 (disabled), the maximum number of data source connections created by the reporting service is 16 (two low affinity connections plus two high affinity connections plus zero four-process query execution helpers). v If the maximum number of query execution helpers is set to 2, the maximum number of data source connections created by the report report is 24 (two low affinity connections plus two high affinity connections plus two four-process query execution helpers). Rsvp. CONCURRENTQUERY. MAXNUMHELPERSPERREPORT Use this parameter to specify the maximum number of query execution helpers for each report. This parameter is used to prevent a single report from consuming all available query execution helpers. For example, a report has eight queries that can run concurrently: v If RSVP. CONCURRENTQUERY. NUMHELPERSPERPROCESS and RSVP. CONCURRENTQUERY. MAXNUMHELPERSPERREPORT are set to four, the report consumes all query helpers when it runs. No other report can run queries simultaneously until the report has finished running. v If RSVP. CONCURRENTQUERY. MAXNUMHELPERSPERREPORT is set to two instead, the report consumes two query helpers, leaving two for other reports to use. The default value for this parameter is 1. This setting has no effect unless RSVP. CONCURRENTQUERY. NUMHELPERSPERPROCESS is set to greater than 0. Rsvp. CONCURRENTQUERY. ENABLEDFORINTERACTIVEOUTPUT Use this parameter to enable concurrent query execution when the reporting service produces interactive results. For interactive reports, if concurrent query execution is enabled, some queries may run unnecessarily because the results are not used. For example, all queries in a multi-page report can run with at least one query on each page, but the user can see only the first page. If you do not want to use resources for results that are not used in interactive reports, disable this parameter. Authoring request pages are not interactive output and are not affected by this setting. The default value for this parameter is false, which means disabled. 112 IBM Cognos Analytics Version 11.0.0: RSVP Security and Administration Guide. Soon. EFFECTIVEPROMPTINFO. IGNORE Use this parameter to disable the issuance of the effectivePromptInfo attribute on metadata requests and effectively disable moving request information from the caption attribute of a level to the level itself. The default value for this parameter is false, which means disabled. Set parameters for concurrent query execution Use the following procedure to configure parameters for concurrent query execution. Procedure 1. Follow the steps in the Configuring advanced settings for specific services section on page 573. 2. For the ReportService or BatchReportService, in the Parameter column, type one of the parameter names described in the Simultaneous Query Execution section in the 111. 3. In the Value column, type the corresponding value for the parameter. 4. Click OK. Configuring Query Prioritization You can set parameters that specify how query prioritization works. When you run a report with request controls defined, all parameter information, including parameter information defined in the report, model, and data source, is retrieved. This is necessary for writing data and aligning the capabilities of quick controls with those of your This operation can affect performance, especially when there are many or complex queries. From the user's perspective, it may take too long to submit the first request page or report page. To increase speed, report authors can set a query hint in Reports to prioritize a query when determining parameter information. Queries are prioritized based on where they are used and whether they contain filters. A priority group is the set of queries that share similar attributes, such as a filter. Instead of retrieving parameters for all queries at the same time, parameters for author-defined priority queries are retrieved first, regardless of how automated query prioritization is established. For more information about request parameters, filters, and controls, see the IBM Cognos Analytics - Reporting User Guide. Queries are grouped by priority, as shown in the following table. When a query group has subgroups, the first subgroup takes precedence over the second subgroup. Query group priority queries with the Use for Parameter Info property set to Yes in Reporting 1 Queries with defined filters that are not used to populate the request controls 2 v First reference to those queries v References after those queries Chapter 6. Server Administration 113 Query Group Priority Queries with Defined Filters That Are Used to Populate Request Controls 3 v First Reference to Such Queries v Post-Query References Without Defined Filters That Are Not Used to Populate Request Controls 4 v First Reference to Those Queries v Subsequent References to Those Queries Without Defined Filters That Are Used to Populate Controls 5 v First Reference to such queries v Post-references to such queries Queries To specify a system-wide configuration that defines how queries and query groups are processed, you can assign a configuration value or name to advanced report server settings, RSVP. Soon. Reconciliation. This allows you to specify the degree of reconciliation between the fast control capabilities and the data type to that of the associated parameter. The settings you choose determine whether precision or reconciliation speed is most important. For example, if the report author ensures that parameters are defined with the same data type and capabilities (that is, optionality, cardinality, and discretion), in all queries, specifying CHUNKED or 3 would likely achieve the best performance in the widest variety of situations. Rsvp. Soon. Reconciliation. CHUNKSIZE allows you to specify the size of the fragment. This applicable when using CHUNKED GROUPED and CHUNKED. The default fragment size is 5. Advanced report server properties and report query hints work cooperatively to provide the best performance. You can use the options shown in the following table to configure RSVP. Soon. Reconciliation. Configuration Name Purpose 0 COMPLETE All queries are sent at once. This is the slowest and most accurate form of reconciliation. This is the default setting. 1 114 GROUPED are sent by priority group. This setting works best for reports that have many unfiltered queries and few filtered queries. Provides average speed and high reconciliation accuracy. IBM Cognos Analytics Version 11.0.0: Administration and Security Guide Purpose Name Configuration 2 FRAGMENTED GROUPED queries are sent by priority group with a maximum number per request. Queries do not cover groups. This setting works best on reports that have many queries with similar filter expressions. Provides maximum speed and low reconciliation accuracy. 3 CHUNKED queries are sent per priority group with a maximum number per request. Queries can span groups. Before you begin You must have the necessary permissions to access IBM Cognos Administration Chapter 14, Secured Functions and Features, on page 231. Procedure 1. Follow the steps in the Configuring advanced settings for specific services section on page 573. 2. For the reporting service, in the Parameter column, type one of the parameter names described in this section. 3. In the Value column, type a value associated with the configuration. 4. Optional: If necessary, continue typing other settings and values. 5. Click OK. 6. Repeat the same steps for BatchReportService. Converting numeric lookup keys to strings in queries An error can occur if the data source does not convert numeric data elements to strings. A search message is associated with a query that does not execute when the search request is rendered the first time. When you type a search string, the query is filtered and the results are displayed in a list box. The report server does not check the data type of the filtered query item because most data sources convert the data item to a string (varchar) and the filter becomes valid. However, some data sources, such as Teradata, do not perform the conversion, causing an error. The following error message is displayed when you run a Reporting or Query Studio report: RQP-DEF-0177 An error occurred while performing the 'sqlPrepareWithOptions' status''-69' UDA-SQL-0043 Operation The underlying database encountered an error while processing the SQL request. [NCR] [ODBC Teradata Driver] [Teradata Database] Partial string matching requires character operands. To avoid this error, make sure that the advanced RSVP settings. Soon. CASTNUMERICSEARCHKEYTOSTRING is set to true (default) for ReportService and BatchReportService. This advanced setting is used to convert numeric data elements to a string (varchar) format. For more information about configuring advanced options, see Configuring Advanced Settings for specifics on page 573. Chapter 6. Server Administration 115 Example of unsationed data item [data item] starts with '20' [data item] contains '123' Or a Boolean join: [data item] starts with '2' and [data item] contains '009' or [data item] contains '119' Example of unscathed data item with lower function If search is case insensitive , then the expressions contain the lower function, which will contain the lower function, which more meaningful when searching for string data items than in numerics: lower([data item]) starts with lower('20') lower([data item]) contains ('123')lower ([data element]) starts with lower('2') AND lower([data data item]) contains lower('009') OR lower([data item]) contains lower('119') Example of data item converted to string cast([data item], varchar(128)) starts with '20' cast([data item], varchar(128)) contains '123' cast([item data], varchar(128)) starts with '2' AND cast([data item], varchar(128)) contains '009' OR cast([data item], varchar(128)) contains '119' Caching In Reporting, Query Studio, and IBM Cognos Viewer, the results of previous database requests are cached during a session when session caching is enabled. To increase performance, for subsequent queries, IBM Cognos software uses cached results for some actions instead of accessing the database. This applies when the same results can be used or when the new results are a subset of the cached results. You can disable session caching at the server level or at the package or report level. Since performance may be affected, you might want to disable server-level session caching in the following situations: v Users expect updated results directly from the database for each query, for example, new records that were added to the database in the middle v that you want to limit the number of times the cache is accessed during a session You can also disable session caching for individual reports due to high resource consumption, such as reports that use bursts. 116 IBM Cognos Analytics Version 11.0.0: Administration and Security Guide You can also enable and disable session caching for specific queries in reports in Reports (see IBM Cognos Analytics - Report User Guide) and for models in Framework Manager (see the IBM Cognos Framework Manager User Guide). Session caching for new models and reports is enabled by default. Existing packages and reports retain existing session caching settings. Disabling session caching at the server level You can disable session caching at the server level. Procedure 1. In the install location/configuration directory, make a copy of the CQEConfig.xml.sample file and rename it to CQEConfig.xml. 2. Open the install location/configuration/CQEConfig.xml in an editor. Make sure that the editor supports saving files in UTF-8 format. 3. Locate the queryReuse parameter in the CQEConfig file.xml and change value to 0. 4. Save the CQEConfig.xml. 5. Using IBM Cognos Configuration, stop and restart the IBM Cognos service. For more information, see the IBM Cognos Analytics Installation and Configuration Guide. Disable session caching at the package or report level You can disable session caching at the package or report level. Procedure 1. Copy the install location/configuration/CQEConfig.xml.sample file to install location/bin and rename it to CQEConfig.xml. 2. Open the install location/bin/CQEConfig.xml in a 3. Make sure that your editor supports saving files in UTF-8 format. 4. Locate the queryReuse parameter and delete it. 5. Save the CQEConfig.xml. 6. Using IBM Cognos Configuration, stop and restart IBM Cognos software. For more information, see the IBM Cognos Analytics Installation and Configuration Guide. Enabling the HTTPOnly parameter to protect the CAM passport of the passport cookie identifies the user's web browser session with the server. Administrators can set the HTTPOnly attribute to prevent scripts from reading or manipulating the CAM passport cookie during a user's session with the web browser. About this enable HTTPOnly attribute task prevents malicious scripts from stealing the user's session identity. When an administrator sets this attribute, the web browser can only use the session cookie to send HTTP requests to the server. If you want to enable the HTTPOnly attribute, make sure that users have a web browser that supports this attribute. Chapter 6. Server Administration 117 Procedure 1. Go to IBM Cognos Administration(S). 2. On the Status tab, click System. 3. In the Dashboard pane, from the System drop-down menu click Set Properties. 4. Click the Settings tab. 5. In the Category list, select Environment. 6. For the HTTPOnly Cookie Support parameter, select the appropriate check box in the Value column. 7. Click OK. Parameter cache In IBM Cognos Analytics, if parameter caching is enabled, request pages run faster. As a result, overall server performance can improve. By default, parameter caching is disabled at the server level. To enable parameter caching for all reports, you can change the server settings. To override the server settings for a report, you can edit the XML attributes of a report specification. Parameter caching is set at the server level with the advanced RSVP property. PARAMSCACHEDISABLED. The default value for the advanced property is true. You can enable parameter caching by changing the value of the advanced property to false. Once enabled, the configuration takes effect when reports are updated and saved, and parameter and request metadata is embedded in the report specification. Then, when the report runs, the metadata is retrieved from the cache instead of the query engine. Parameter caching can improve overall server performance, especially when reports run on complex models and when reports have complex queries with many parameters. To decide whether to enable parameter caching, evaluate the stability of the model. If the model is static, consider enabling parameter caching. If the model is in development or if data types change frequently, do not enable parameter caching. If the server configuration for parameter caching is not appropriate for some reports, you can override the server configuration by editing the XML attributes of a report specification. Therefore, if parameter caching is enabled at the server level, you have the option to disable it for a particular report, determined, enable parameter caching for a given report if the server-level property is disabled. For information about how to set parameter caching for a report, see Configuring Parameter Caching for Reports on page 119. Configuring parameter caching for the server In IBM Cognos Analytics, parameter caching is disabled by default at the server level. To enable parameter caching at the server level, change the value of the RSVP advanced property. PARAMSCACHEDISABLED to false. About this task For information about deciding whether to enable parameter caching, see Parameter Caching. 118 IBM Cognos Analytics Version 11.0.0: Procedure 1 of the Administration and Security Guide. Follow the steps in the Configuring advanced settings for specific services topic on page 573. 2. On the Set Advanced Settings - ReportService page, in the Parameter column, locate or type RSVP. PARAMSCACHEDISABLED. 3. In the Value column, type true or false. Configuring Parameter Caching for Reports For an IBM Cognos Analytics report, you can override server settings for parameter caching. In the report specification, add the paramsCacheDisabled XML attribute and set the value to true or false. About this task For information about deciding whether to enable parameter caching for reports, see Parameter Caching on page 118. If the value of the RSVP advanced property. PARAMSCACHEDISABLED is true at the server level, to enable parameter caching for a report, in the report specification, add the following attribute: <XMLAttribute name-paramsCacheDisabled value-false></XMLAttribute> If the value of the RSVP advanced property. PARAMSCACHEDISABLED is false at the server level, to disable parameter caching for a report, in the report specification, add the following attribute: <XMLAttribute name-paramsCacheDisabled value-true></XMLAttribute> Procedure 1. Under Reports, click Tools > Copy Report to Clipboard. 2. Copy the Clipboard report specification to an XML editor. 3. Add the paramsCacheDisabled attribute to the <XMLAttributes> report with a value of true or false as follows: v <XMLAttribute name-paramsCacheDisabled value-true></XMLAttribute> v <XMLAttribute name-paramsCacheDisabled value-false></XMLAttribute> 4. Copy the revised report specification to the Clipboard. 5. Under Reports, click Tools > Open Report from Clipboard and click OK. The report is reloaded into Reports with the modified report specification. Reduce Decimal Precision You can set decimal precision in cross-tab reports. In a cross-tab report, values support a maximum of 18 digits, plus the decimal point. Decimal precision determines the number of digits reserved to express the decimal component of a number. The remaining digits are reserved to express the entire component of the number. By default, decimal precision is set to 7 digits, which restricts the length of integers to 11 digits. If you want to reserve more than 11 integers to express the entire component of a number, you must reduce the decimal precision. For example, </XMLAttributes> </XML

Mobile administrators, one of the predefined roles in the Cognos namespace, can be used to specify access permissions for this functionality. Cognos Mobile uses the same set of users as Cognos Business Intelligence. For information about managing Cognos BI, see other sections of the IBM Cognos Business Intelligence Administration and Security .

Related Documents:

2 IBM Cognos Business Intelligence Version 10.1.1: Using IBM Cognos Series 7 and IBM Cognos Business Intelligence in the Same Environment. Chapter 2. Set up Interoperability Between IBM Cognos Series 7 and IBM Cognos BI Set up interoperability before and during migration to provide continuity to your

IBM Cognos ReportNet Model Upgrade 367 Verifying the Model in IBM Cognos ReportNet 367 Opening and Upgrading the Model 368 Verifying and Repairing the Upgraded IBM Cognos ReportNet Model 370 IBM Cognos 8.1 or 8.2 Model Upgrade 374 Verifying the Model in IBM Cognos 8.1 or 8.2 374 Opening and Upgrading the IBM Cognos 8.1 or 8.2 Model 375

IBM Cognos Analysis for Microsoft Excel 10.2.0 has feature enhancements in several key areas: v IBM Cognos Analysis for Microsoft Excel is now integrated with IBM Cognos TM1 data sources. Use IBM Cognos Analysis for Microsoft Excel with IBM Cognos TM1 data sources to enter and write back values to TM1 cubes. For more information, see

With the release of IBM Cognos Business Intelligence V10.1, the IBM Cognos Platform delivered a new 64-bit, in-memory query processing . mode with dynamic query capabilities. IBM Cognos Business Intelligence Dynamic Query is an optional mode included with the Cognos Business Intelligence query service, which can be implemented

Componentes de Cognos Mobile instalados en un sistema . . 33 Componentes de Cognos Mobile instalados en distintos sistemas . . 34 IBM Cognos Analytics con otr os pr oductos de IBM Cognos . . 34 Pr oductos de IBM Cognos que inter operan con IBM Cognos Analytics . . 34 Capítulo 3.

found in the Cognos Connection User Guide, a link to which can be found on the Resources tab in the IIT Cognos portal. 2. About the Cognos Portal The IIT Cognos Portal (aka "Cognos Connection") allows users to access Cognos reports and launch the various Cognos tools for authoring reports and queries based on data stored

WebSphere security and IBM Cognos 8 directly or - more common – for single signon between IBM WebSphere Portal and IBM Cognos 8. 1.2 Applicability While for creation of this document IBM Cognos 8 BI MR2 and IBM WebSphere 6.0.2 were used the technique described in here applies to all versions of IBM Cognos 8.

There are no new features in this release of IBM Cognos Real-time Monitoring Dashboard. New features in version 10.1.1 Listed below are new features for version 10.1.1. Closer integration between IBM Cognos Real-time Monitoring Dashboard and IBM Cognos Business Insight When working with IBM Cognos Real-time Monitoring dashboard objects in IBM