Setting Up the Samples

You can use the Cognos samples to learn how to use Cognos 8, including Framework Manager, Metric Studio, Metric Designer, and Event Studio.

Cognos 8 provides sample databases that contain sales, marketing, and financial information for a fictional company named the Great Outdoors Company that sells sporting equipment.

Before you can use the sample databases, Cognos 8 must be installed, configured, and running. For Cognos 8 reports and analyses, Framework Manager should also be installed, configured, and running.

To use the sample content for Metric Designer, the optional modeling tool for Metric Studio, Metric Designer must also be installed, configured, and running.

To set up the samples, do the following:

	Restore the samples databases.
	Create the data source connections to the samples databases.
	If you plan to use OLAP data source samples, set up the sample cubes, if this is required, and create data source connections to the OLAP data sources you want to use. Setup tasks are required only for Microsoft Analysis Services cubes and DB2 cubes.
	If you plan to use the Metric Studio sample, set up the Metric Studio sample.
	If you plan to use the Metric Designer sample, set up a data source connection to it, set up the Metric Studio sample, and import the Cognos_Samples and GO_Metrics deployment archives.
	Import the samples content (packages) into the content store.
	If you want to test the sample agent ELM Returns Agent using Event Studio, run the sample agent against changed data.

After you complete these tasks, use Cognos 8 to run the sample reports or scorecards. You can later remove the Cognos 8 samples.

Restore Backup Files for the Samples Databases

To use the samples, you must restore backup files for the samples databases. This action re-creates multilingual versions of the Great Outdoors databases.

The following sample databases and associated files are provided with Cognos 8. For SQL Server and Oracle, each database is delivered as a Microsoft SQL Server backup file and an Oracle export file (.dmp). For DB2, the database schemas are delivered in a DB2 move file. The file are compressed, and you must extract them before you can restore the databases or schemas.

When restoring the samples databases, ensure that you do the following:

• Give the restored databases the same names as the backup or export file names.

  The names are case-sensitive.

• Create a user in your database who has select privileges for all schemas.

  The GO Sales package references tables in all schemas.

• Use the UTF-8 character set.

• Have sufficient disk space available in the target location. Reserve 150MB for the GO Sales data (four schemas) and 200MB for the GO Sales warehouse data (one schema).

Steps

1. On the computer where Cognos 8 is installed, go to the sql server, oracle, or db2 directory located in c8_location /webcontent/samples/datasources.

2. If required, copy the backup files for the samples databases to your database backup directory.

   To ensure the security and integrity of Cognos 8, copy the files to a directory that is protected from unauthorized or inappropriate access.

3. Restore the samples databases using your database management tool.

   Tip: For SQL backup files, restore the database from a device and ensure that the restore locations are correct for the .ldf and .mdf database files. For more information, see the Microsoft SQL Server documentation or the Cognos Knowledge Base (http://support.cognos.com/kb-app/knowledgebase).

4. For each database, create at least one user who has select permissions for all the tables in the restored databases.

You can now create the data source connections in the portal.

Create Data Source Connections to the Samples Databases

You must create data source connections to the samples databases that you restored. Cognos 8 uses this information to connect to the samples databases and run the sample reports or use the sample package.

The DB2 database name that you type must use uppercase letters. Also, in Framework Manager, the schema names that you type for the DB2 data sources must use uppercase letters.

Before you create the data source connections, you must restore the backup files for the samples databases. Also, ensure that the Cognos 8 service is running.

To create data sources, you must have execute permissions for the Directory secured feature and traverse permissions for the Administration secured function.

Steps

1. Open Cognos Connection.

2. In the upper-right corner, click Launch, Cognos Administration.

3. On the Configuration tab, click Data Source Connections.

4. Click the new data source button .

5. In the Name box, type great_outdoors_sales and then click Next.

6. In the connection page, click the type of database that you restored and want to connect to, select an isolation level, and then click Next.

   The connection string page for the selected database appears.

   Tip: The user specified in the great_outdoors_sales data source must have select privileges on the tables in each of the GOSALES, GOSALESRT AND GOSALESHR schemas .

7. Do one of the following:

   • If you restored the samples databases in SQL Server, in the Server Name box, type the name of the server where the restored databases are located. In the Database name box, type GOSALES.

     Cognos 8 samples require TCP/IP connectivity with SQL Server. Ensure the SQL Server Security is set to SQL Server and Windows, instead of Windows Only. The samples use SQL Server security for authentication.

   • If you restored the samples databases in Oracle, in the SQL*Net connect string box, type the Oracle connection string.

   • If you restored the samples database in DB2, in the DB2 database name box, type GO_DB using uppercase letters. In the DB2 connect string box, type the DB2 connection string.

8. Under Signons, select the Password and Create a signon that the Everyone group can use check boxes, type the user ID and password for the user that you created when you restored the databases, and then click Finish.

   Tip: To test whether the parameters are correct, click Test.

9. Click Finish.

10. Repeat steps 4 to 9 for the GOSALESDW samples database.

    For the GOSALESDW database in SQL Server and Oracle, type great_outdoors_warehouse for the data source name and GOSALESDW for the database name. For DB2, type great_outdoors_warehouse for the data source name and GS_DB for the database name.

The Great Outdoors data source connections appear as entries in the Data Sources tab of the Directory tool.

You can now import the samples unless there is a syntax error in the connection string or an incorrect parameter.

Set Up Microsoft Analysis Services Cube Samples

Microsoft Analysis Services (MSAS) cubes are provided which you can use from Cognos Connection or Framework Manager. The cube samples are contained in the GOSALESDW.cab and GOSALESDW.abf archive files in the c8_location/webcontent/samples/datasources/cubes/MSAS directory. The archive files must be restored to a Microsoft SQL Server database running Microsoft Analysis Services .

The Go Sales Fact cube contains the same monthly sales data as the GOSALESDW database.

The GO Finance Fact cube contains year-to-date and monthly financial data for all accounts so you can create model financial statements in Analysis Studio, Query Studio, and Report Studio. The GO Finance Fact cube contains Actuals in US dollars submissions for 2004, 2005, or 2006.

Note: Both Microsoft XML 6.0 Parser and Microsoft SQL 2005 Analysis Services 9.00 OLEDB Provider must be installed on the local client in order to establish data source connections to MSAS cubes.

Steps

1. On the computer where Cognos 8 is installed, go to the c8_location/webcontent/samples/datasources/cubes/MSAS/en directory.

2. Copy the GOSALESDW.cab and GOSALESDW.abf files to a directory that you can access from the Analysis Manager console in the Analysis Servers of Microsoft SQL Server.

3. Use the Analysis Manager to restore the database from the GOSALESDW.cab and GOSALESDW.abf files.

You can now create the data source connections using either the GO Sales Fact or GO Finance Fact cubes .

Set Up the DB2 Cube Sample

To set up the DB2 cube sample, you must have Hyperion Essbase installed, and a DB2 OLAP Server with Essbase Integration Services Console.

Steps

1. Using Essbase Integration Services Console, perform an outline member load and a data load.

2. Using the GOSLDW_ML database for the cube, import the GOSLDW_EN_FR_DE_JA_RU_SC.xml model and the GOSLDW_language.xml metadata outline for the language that you want to use, where language is one of: EN (English), DE (German), FR (French), JA (Japanese), RU (Russian) or SC (Chinese).

   Information about cubes is available in the cube details file for each language: DB2OLAPGOSLDWlanguageCubeInfo.xml.

3. Using Hyperion Solutions Essbase Administration- Administration Console, set up the generations for the model and populate the cube.

You can now create a data source connection to the cube .

Create Data Source Connections to OLAP Data Sources

Cognos 8 provides the following OLAP samples:

• GO Sales Fact and GO Finance Fact Microsoft Analysis Services cubes

• Great Outdoors Company cube

• Great Outdoors DB2 cube

You must create data source connections to the cubes to use the samples. You must set up the Microsoft Analysis Services cube samples or set up the DB2 cube sample, if you are using them, before creating data source connections.

You can increase the read cache size to improve query performance, although this setting has no effect on the initial time required to open a cube.

To create data sources, you must have execute permissions for the Directory secured feature and traverse permissions for the Administration secured function.

Steps for PowerCubes

1. Open Cognos Connection.

2. In the upper-right corner, click Launch, Cognos Administration.

3. On the Configuration tab, click Data Source Connections.

4. Click the new data source button.

   Note: You must add a data source connection for each cube.

5. To create a data source connection for the Sales and Marketing cube, type sales_and_marketing in the Name box, and then click Next.

   You can define a Windows path or a UNIX path.

   If you define a UNIX path and you plan to use Framework Manager, you must also define the Windows path and ensure that the cube is also available in the Windows location. Framework Manager can access cubes only from Windows locations.

6. In the connection page, under Type click Cognos PowerCube, select an isolation level, and then click Next.

   The connection string page for the selected database appears.

7. In the Read cache size (MB) box, type the cache size of the cube in megabytes.

   If you leave this field blank or type 0, Cognos Connection uses the default value in the ppds_cfg.xml file in the configuration folder.

8. In the Windows location box, type the location and name of the SalesandMarketing.mdc file for the data source connection. For example, type

   c8_location/webcontent/samples/datasources/cubes/PowerCubes/En/SalesandMarketing.mdc

9. To test whether the parameters are correct, click Test.

10. Click Finish.

You can now import the sample package for the PowerCube to use this data source.

Steps for DB2 Cubes

1. Open Framework Manager.

2. Click Create a new project.

3. In the New Project page, specify a name and location for the project.

4. In the Select Language page, click the design language for the project.

5. Click OK.

   The Import wizard appears.

6. In the connection page, under type click IBM DB2 OLAP Server, select an isolation level, and then click Next.

   The connection string page for the selected database appears.

7. In the Server name box, type the name of the server.

8. To test whether the parameters are correct, click Test.

9. Click Finish.

To use this data source, you must create a package using this data source in Framework Manager, and then publish the package.

Steps for Microsoft Analysis Service Cubes

1. Open Cognos Connection.

2. In the upper-right corner, click Launch, Cognos Administration.

3. On the Configuration tab, click Data Source Connections.

4. Click the new data source button.

5. In the Name box, type go_sales_fact or go_finance_fact and then click Next.

6. In the connection page, click the type of Microsoft SQL Server database that you restored and want to connect to, select an isolation level, and then click Next.

   The connection string page for the selected database appears.

7. In the Server Name box, type the name of the server where the restored databases are located. If needed, in the Database name box, type the name of the database you restored.

8. Under Signons, select the Password and Create a signon that the Everyone group can use check boxes, type the user ID and password for the user that you created when you restored the databases, and then click Finish.

   Tip: To test whether the parameters are correct, click Test.

9. Click Finish.

10. You now have the option to create a package using your new data source. Click Create a Package and OK, and follow the instructions in the new package wizard.

    Note: You must create a package with this data source in order to use this data source, and you must create a connection between the GOSALESDW_MSAS2005.zip deployment and the MSAS service before you can use the samples.

11. Click New Connection and follow the steps in the new connection wizard, naming the connection GOSALESDW_MSAS2005, and selecting the database based on the language you are using. For example, GOSALESDW for English, or GOSALESDW_DE for German.

    When the new connection is created, it appears in the data source connection list.

Set Up the Metric Studio Sample

To set up the Metric Studio sample, do the following:

	Create a metric store named GOMETRICS.
	Create a new metric package named GO Metrics that uses the GOMETRICS metric store. For the data source name, type go_metrics. When prompted by the wizard, select the standard Gregorian calendar and accept the defaults for Years, Quarters, and Months. Select January 1, 2004 as the start date for a period of three years. For more information, see the section about metrics in the Administration and Security Guide.
	Set the import source.
	Import the metric data and files into the metric store.

Steps to Set the Import Source

1. Copy all text files from c8_location/webcontent/samples/datasources/metricsdata/GO_Metrics_Unicode to c8_location/deployment/cmm.

   Tip: You may need to create the cmm folder.

2. Specify the source and collation code for Unicode in Metric Studio.

3. In Metric Studio, in the Tools list, click Import Sources.

4. Under Metric Deployment Location, click Use the default deployment location.

5. Click the Set Properties icon in the Actions column next to the default import source.

6. Under Character Set Encoding, select Unicode (UTF-16) and click OK.

You can now use the GO Metrics package in Metric Studio.

Steps to Import Metric Data and Files into the Metric Store

1. In Metric Studio, in the Tools list, click Import Sources.

2. Click New.

3. In the Name box, type a descriptive name for the data source.

4. Click Metrics import directory.

5. Specify the identification code. This identifies the new import source.

6. If the folder includes sub-folders, click Include sub-folders.

7. In the File format box, click 8.3.1.

8. In the Character Set Encoding box, specify Unicode UTF16 and click OK.

9. Choose whether to import the files into the metric store using Cognos Connection or Metric Studio.

   • To use Cognos Connection, in Public Folders or My Folders, open the GO Metrics package by clicking the view metric package contents icon in the Actions column. Click Metric Maintenance.

   • To use Metric Studio, in Metric Studio, in the Tools list, click Metric Maintenance.

10. Click the Import and transfer data from files into metric store metric task.

    Tip: If an error occurs, click Clear staging area rejected data logs, Clear metric history data only, and Clear metric history and calendar data.

You can now use the GO Metrics package in Metric Studio.

Import the Samples

To use the sample package and other content, you must import them from the sample deployment archive.

Before you import the Cognos_Samples.zip and GO_Metrics.zip deployment archives, you must restore the databases . For each database, you must create one or more named users with select permissions for the database tables. You must also create data source connections to the samples databases .

Before you import the Cognos_PowerCube.zip or Cognos_PowerCube_Financial.zip deployment archive, you must create a database connection to the appropriate PowerCube and select the language that you want to use. The language that you select must be supported by your locale.

Steps

1. Copy the zip file from the c8_location/webcontent/samples/content directory to the directory where your deployment archives are saved.

   The default location is c8_location/deployment. The location is set in the configuration tool. For information about changing the location, see the configuration tool online help.

2. Open Cognos Connection.

3. In the upper-right corner, click Launch, Cognos Administration.

4. On the Configuration tab, click Content Administration.

   Note: To access this area in Cognos Administration, you must have the required permissions for the Administration tasks secured feature.

5. On the toolbar, click the new import button.

   The New Import wizard appears.

6. In the Deployment Archive box, select Cognos_Samples, Cognos_Powercubes, GO_Metrics, or GO_Audit.

7. Click Next.

8. Type a unique name and an optional description and screen tip for the deployment archive, select the folder where you want to save it, and then click Next.

9. In the Public Folders Content box, select the packages and folders that you want to import.

   The Cognos_Samples deployment archive has the following packages or folders:

   • GO Data Warehouse (analysis), GO Data Warehouse (query), GO Sales (analysis), GO Sales (query), Sample Template and Practical Examples.

   The Cognos_PowerCube deployment archive for the Great Outdoors Company has packages or folders for the following languages:

   • English

   • French

   • German

   • Japanese

   • Russian

   • Simplified Chinese

   The GO_Metrics deployment archive has the following packages or folders:

   • GO Metrics

10. Select the options you want, along with your conflict resolution choice for options that you select, and then click Next.

11. In the Specify the general options page, select whether to include access permissions and references to external namespaces, and who should own the entries after they are imported.

12. Click Next.

    The summary information appears.

13. Review the summary information and click Next.

14. Select the action that you want:

    • To run once now or later, click Save and run once. Click Finish, specify the time and date for the run, then click Run. Review the run time and click OK.

    • To schedule at a recurring time, click Save and schedule. Click Finish, and then select frequency and start and end dates. Click OK.

      Tip: To temporarily disable the schedule, select the Disable the schedule check box.

    • To save without scheduling or running, click Save only and click Finish.

15. When the import is submitted, click Finish.

You can now use the sample packages to create reports and analyses in Report Studio, Query Studio, and Analysis Studio, view extracts in Metric Designer, or create agents in Event Studio. You can also run the sample reports that are available on the Public Folders tab in the portal.

Sample Database Models

The following sample models provide information for the fictional company, the Great Outdoors and are provided with Cognos 8:

• go_sales, which refers to the samples database GOSALES

• go_data_warehouse, which refers to the database GOSALESDW

• gosales_scriptplayer, which refers to the samples databases GOSALES

You can use sample database models on different platforms. For information about moving models from one platform to another, see the Framework Manager User Guide.

Note: Transformer 8 uses some of the reports in the GO Data warehouse (query) package and GO Sales (query) package as source data for various cubes. These reports are meant to be simple list reports with no formatting. The description information for the reports indicates if the report was developed to be source data for Transformer 8.

Example - Running the Sample ELM Returns Agent Against Changed Data

You can change data in the GOSALES database if an Event Studio user wants to test the sample agent ELM Returns Agent. The Event Studio user can then run the sample agent twice and detect a new event. For more information, see the Event Studio User Guide.

Running the sample agent against changed data involves the following steps:

	The Event Studio user runs the sample agent against the default data and then asks you to change the data.
	You simulate the occurrence of some initial events and then ask the Event Studio user to run the sample agent a second time.
	The Event Studio user runs the sample agent against the changed data. The Event Studio user informs you when the agent has completed running.
	You simulate the passage of time and the resolution of some events and then ask the Event Studio user to run the sample agent a third time.
	The Event Studio user runs the sample agent for the final time. The Event Studio user informs you when the agent has completed running.
	You modify the data so that the ELM Returns Agent detects no events.

Example - Simulate the Occurrence of Initial Events

Run part of the Event_Studio_ELM_Agent_Modify_GOSALES.sql script to simulate the following data changes:

• change the date to the current date

• change the follow-up code to -1 in four records.

  A code of -1 indicates that follow-up is required.

Steps

1. In SQL Query Analyzer, from the File menu, click Open.

2. Go to c8_location/webcontent/samples/datasources/sqlserver and double-click the Event_Studio_ELM_Agent_Modify_GOSALES.sql file.

3. In the toolbar, from the list of databases, click GOSALES.

4. In the Query window, under Part 1, select all sixteen lines of code.

5. From the Query menu, click Execute.

The database is updated with the changes.

Example - Simulate the Passage of Time and the Resolution of Some Events

Run part of the Event_Studio_ELM_Agent_Modify_GOSALES.sql script to simulate data changes. First, change it so that two days elapsed since the ELM Returns Agent sample was last run. Second, for three of the four event instances found the last time that the ELM Returns Agent sample ran, change the follow-up code from -1 to +1. This indicates that only one of the these event instances still requires follow-up and the other instances are resolved.

Steps

1. In SQL Query Analyzer, from the File menu, click Open.

2. Go to c8_location/webcontent/samples/datasources/sqlserver and double-click the Event_Studio_ELM_Agent_Modify_GOSALES.sql file.

3. On the toolbar, click GOSALES from the list of databases.

4. In the Query window, under Part 2, select all lines of code that appear after the comments.

5. From the Query menu, click Execute.

The database is updated with the changes.

Example - Modify the Data So That the ELM Returns Agent Detects No Events

When the Event Studio user finishes running the sample ELM Returns Agent against changed data, they should notify you. You can then modify the GOSALES database so that the agent no longer detects any event instances.

Remove the Samples Databases from Cognos 8

You can delete the packages on which the samples are based after you finish using the sample reports to learn about Cognos 8, including Framework Manager. This action permanently removes the samples from the content store.

Steps

1. Open Cognos Connection.

2. Click the Public Folders tab.

3. Select the check box for the sample package you want to delete.

4. Click the delete button on the toolbar, and click OK.

   To use the samples again, you must set up the samples.