This section contains additions and corrections that will appear in the next version of the Cognos 8 Administration and Security Guide.
Note: This topic will replace the topic "Set Up the DB2 Cube Sample" in a future release.
To set up the Essbase cube sample, you must have Hyperion Essbase and Essbase Integration Services Console installed.
Go to the c8_location\webcontent\samples\datasources\cubes\Essbase\Outlines_and_Raw_Data directory.
This directory contains zip files for the different languages, such as EN.zip or JA.zip for English and Japanese, respectively.
Unzip the file for your language.
Each zip file contains the following two files:
languageU_Data.txt, such as ENU_Data.txt or JAU_Data.txt.
GODWlanguageU.otl, such as GODWENU.otl or GODWJAU.otl.
Using block storage in Essbase, create a Unicode application.
Within the application, create a new database.
You can use GODWlanguageU, such as GODWENU or GODWJAU, as your database name, or use the name of your choice.
Copy and paste the GODWlanguageU.otl file in your database directory.
If the database name specified in step 4 is different than GODWlanguageU, rename the GODWlanguageU.otl file to match the database name that you created.
Confirm that you want to overwrite the .otl file.
In Essbase Administration Services console, open your database outline and save it.
Confirm that you want to save the outline even if it was not changed.
Copy the languageU_Data.txt file and paste it in the same directory as the .otl file.
In Essbase Administration Services console, right-click the database you created and select Load Data.
Browse to the languageU_Data.txt file in your database directory, select the file, and click OK.
After the data loads successfully, right-click the database and select Execute Calculation.
Select the default calculation, and click OK.
The calculation process may take up to 5 hours, depending on the computer where Essbase OLAP Server is installed.
You can now create a data source connection to the cube.
Note: The following information will be added to this topic in a future release.
You can use metrics as global filters in a page or in a dashboard with multiple tabs. The page must contain a Metric List portlet and a Cognos Viewer portlet configured to show reports associated with the metrics. You must also set up communication between the Metric List and the Cognos Viewer portlets using the channel property in both portlets. When a user clicks a metric name in the Metric List portlet, the Cognos Viewer portlet dynamically updates the associated reports based on the parameters of the clicked metric. For this functionality to work, the names of the metric parameters must match the names of the report prompt parameters. Currently, the following parameters are supported by the Metric List portlet:
Note: The following information will be changed in this chapter in a future release.
The following sentences contain errors.
"You can make more than one data source connection available by combining them, along with other elements, in packages created in Cognos Connection (for OLAP data sources) or created and published using Framework Manager."
The sentences should read:
"You can make more than one data source connection available by combining them, along with other elements, in packages created and published using Framework Manager. You can also make a Cognos PowerCube data source connection available by creating a package and publishing it from Cognos Connection."
In the following sentence in the section "Create a Data Source", step 7, replace the phrase “If you created an OLAP data source" with "For Cognos PowerCubes ".
If you created an OLAP data source, a confirmation appears and you are given the option to create a package using your new data source.
Note: The following information will be changed in this chapter in a future release.
The name of the sample model go_sales will be changed to great_outdoors_sales, and the name of the sample model go_data_warehouse model will be changed to great_outdoors_warehouse.
Note: The description of the Drill Through Assistant secured function in this topic, chapter “Securing Functions and Features “, is incorrect. The description should read as follows:
This secured function controls access to the drill-through debugging functionality in Cognos 8.
Note: The following information will be added to the topic "Conformed Dimensions"in this chapter.
In addition to ensuring that each level contains a business key that has values that match your PowerCube or other DMR models, you must also ensure that the Root Business Key property is set and using the business key of the first level in the hierarchy. This helps to ensure that you have a conformed member unique name when attempting to drill through using members from this dimension.
Note: The following information will be changed in a future release of the Administration and Security Guide and Cognos Connection User Guide:
The name of the portlet group Metric Studio Portlets is changed to Cognos Metrics.
Note: The following information must be added to the topic "Changes in the web.config File":
Add the following code under the <configuration>, <system.web>, <httpHandlers> element:
<add verb="*" path="CognosResources/*.axd"type="Cognos.Portal.Services.HttpResourceHandler, Cognos.BI.WebPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cb3c72729d0875cd" validate="false"/>