COGNOS(R) ENTERPRISE BI SERIES

C O G N O S R E PO R T N E T
( TM )

QUICK START INSTALLATION AND CONFIGURATION GUIDE

Cognos ReportNet Quick Start Installation and Configuraton Guide 10-09-2004 CR Transfer 1.1MR2 Type the text for the HTML TOC entry Type the text for the HTML TOC entry Cognos ReportNet( T M ) Readme Quick Start Installation and Cognos ReportNet Configuration Guide Cognos ReportNet
(TM) (TM)

Version 1.1MR2

QUICK START INSTALLATION AND CONFIGURATION GUIDE

THE NEXT LEVEL TM OF PERFORMANCE

Product Information
This document applies to Cognos ReportNet( T M ) Version 1.1MR2 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site (http://support.cognos.com).

Copyright
Copyright (C) 2004 Cognos Incorporated. Portions of Cognos(R) software products are protected by one or more of the following U.S. Patents: 6,609,123B1; 6,611,838B1; 6,662,188B1; 6,728,697B2; 6,741,982B2; 6,763,520; 6,768,995. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos Products and Accessibility can be found at www.Cognos.com

Table of Contents
Installing and Configuring ReportNet on One Computer 5 Introduction 5 Plan for Installation 5 System Requirements 6 Supported Environments 7 Create the Database for the Content Store 7 Install ReportNet 10 Update Your JAVA Runtime Environment on UNIX 10 Configuring ReportNet 11 Configuring Your Web Server 11 Set Database Connection Properties for the Content Store 11 Configure a Mail Server Account (Optional) 12 Test ReportNet 13 Install Framework Manager 13 Test Framework Manager 14 Setting Up Samples 14 Restore Backup Files for the Samples Databases 14 Create Data Source Connections to the Samples Databases 15 Modify the Sample Model for Oracle and DB2 16 Import the Samples 17 Whats Next? 18 Index 19

Quick Start Installation and Configuration Guide 3

4 Cognos ReportNet( TM )

Installing and Configuring ReportNet on One Computer

Introduction
This document is available as online help and as an online book.

Installing and Configuring Cognos ReportNet

This document provides the information you need to install and configure ReportNet on a single-server with default settings. This installation is suitable when you are setting up a test or evaluation environment, or for small production environments. This installation is the quickest and easiest way to get started. To follow these instructions, your Web server must be installed on the computer where you install ReportNet. For information about how to upgrade or install and configure ReportNet on more than one computer or in a distributed installation, see the ReportNet Installation and Configuration Guide on the CD.

Books for Printing

The information in each online help system is available in online book format (PDF). However, the information from a given help system may be divided into more than one online book. Use online books when you want to print a document or when you want to search the whole document. You can print selected pages, a section, or the whole book. Cognos grants you a non-exclusive, non-transferable license to use, copy, and reproduce the copyright materials, in printed or electronic format, solely for the purpose of providing internal training on, operating, and maintaining the Cognos software. Online books are available from the introduction to the online help for each component. All online books are available on the Cognos documentation CD. You can also read the product readme files and the installation guides directly from Cognos product CDs.

Plan for Installation

Use the appropriate checklist below as your starting point.

Install
Before you install ReportNet, complete the following tasks: Check the system requirements

Create the database for the content store

Quick Start Installation and Configuration Guide 5

Installing and Configuring ReportNet on One Computer

System Requirements
Before you install ReportNet, ensure that your computer meets ReportNets software and hardware requirements. The hardware requirements depend on your reporting environment. You may require additional resources, such as disk space. The following table lists the minimum hardware and software requirements to run ReportNet. Requirement Operating system RAM Disk space Specification Windows Minimum: 1 GB Minimum: 1 GB of free space on the drive that contains the temporary directory used by the ReportNet A Web server installed and started One of the following databases available to store Cognos data: Oracle (version 8.1.7.2 or later if Oracle Server is on a different operating system from ReportNet) DB2 Microsoft SQL Server TCP/IP connectivity to Microsoft SQL Server Web browser For all Web browsers, the following enabled: Other cookies JavaScript Run ActiveX controls and plug-ins Script ActiveX controls marked safe for scripting Active scripting

Web server Database

For IE only, the following enabled:

Microsoft Data Access Component (MDAC) 2.6 or later for use with product samples If you want to email reports, the ability to use a mail server A Web browser configured to accept cookies

6 Cognos ReportNet( TM )

Installing and Configuring ReportNet on One Computer

Database Connectivity for the Reporting Database

The only service that accesses the query database (also known as reporting database) is the reporting engine that runs reports. Ensure that you install the database API software for your reporting sources on each ReportNet server computer. On Windows, the report server supports either native database connectivity or ODBC. On UNIX and Linux, the report server supports the native database connectivity. Also on UNIX and Linux, for Microsoft SQL Server only, the report server supports the Data Direct ODBC driver for Microsoft SQL Server. This driver is available from Data Direct. ReportNet requires TCP/IP connectivity with the Microsoft SQL Server.

Database Connectivity for the Content Store Database

The database client software for the database that is used as the content store must be installed and configured on each computer where you install Content Manager. For Oracle databases, Content Manager uses the JDBC thin driver, classes12.jar. For DB2 databases, Content Manager uses the JDBC driver that requires DB2 client installation. For Microsoft SQL Server, the JDBC driver is included in ReportNet and no other software is required. ReportNet requires TCP/IP connectivity with the Microsoft SQL Server.

Supported Environments
You can view an up-to-date list of environments supported by Cognos products, such as operating systems, patches, browsers, web servers, directory servers, and database servers on the Cognos support site (http://support.cognos.com). It is important to apply all required operating system patches and to use only the versions of third-party software that are supported for a Cognos product. Otherwise, your product may not work properly.

Create the Database for the Content Store

You must create the database that is used for the content store using either Oracle, Microsoft SQL Server, or DB2 UDB. ReportNet uses this database to store, organize, and retrieve information. An Oracle or Microsoft SQL Server database can use UTF-8 or UTF-16 encoding. A DB2 database must use UTF-8 encoding. All database types must use the TCP/IP protocol, which is required by ReportNet to access data. It is important to note that for each installation, ReportNet uses a single sort order that specifies the rules used by the database to interpret, collect, compare, and present character data. For example, a sort order defines whether the letter 'a' is less than, equal to, or greater than the letter 'b', whether the collation is case-sensitive; and whether the collation is accent-sensitive. Your database administrator must back up the ReportNet content store regularly because it contains all the ReportNet data. To ensure the security and integrity of the content store, it is also important to protect the database from unauthorized or inappropriate access. For Linux, a DB2 database is required.

Steps for Microsoft SQL Server

1. If you performed a Typical installation of Microsoft SQL Server, after you install you must change the authentication mode to SQL Server and Windows. For more information, see the knowledge base article 269587 on the Microsoft Web site. 2. Create the database. Ensure that the database collation sequence for the content store is case-insensitive. 3. Determine which user account ReportNet will use to access the content store. 4. Grant create and drop table privileges for the content store to the user account. Ensure that the user account is a member of the db_ddladmin role.

Quick Start Installation and Configuration Guide 7

Installing and Configuring ReportNet on One Computer

Steps for Oracle

1. If you use Oracle 8.1.7, ensure that the compatibility level parameter of the content store is set to 8.1 and not to the default setting of 8.0. For information about changing an instance configuration parameter, see the Oracle documentation. 2. Determine if the database is Unicode. Tip: One method is to type the following select statement: select * from NLS_DATABASE_PARAMETERS The result set returns NLS_CHARACTERSET is UTF-8 or UTF-16, or AL32UTF8 or AL16UTF16, or not Unicode. 3. If the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database. For Oracle 8.1.7, ensure that you specify UTF-8 or UTF-16 for the database character set parameters. For Oracle 9i and Oracle 10g, specify AL32UTF8 or AL16UTF16 for the database character set parameters.

4. Determine which user account ReportNet will use to access the content store. 5. Ensure that the user account that accesses the content store has permissions to do the following: connect to the database create, alter, and drop tables, triggers, views, procedures, and sequences insert, update, and delete data in the content store tables

8 Cognos ReportNet( TM )

Installing and Configuring ReportNet on One Computer

Steps for DB2

1. Set the appropriate environment variables for DB2. Environment variable DB2DIR Description The top level directory that contains the database client software or the entire database installation. The load library path.You must add driver location. Examples: Solaris and Linux example: LD_LIBRARY_PATH=$DB2DIR/lib: $LD_LIBRARY_PATH AIX example: LIBPATH=$DB2DIR/lib: $LIBPATH HP-UX example: SHLIB_PATH=$DB2DIR/lib: $SHLIB_PATH DB2INSTANCE DB2CODEPAGE The default database server connection. Setting this optional environment variable to a value of 1208 provides support for multilingual databases. For information about whether to use this environment variable, see the DB2 documentation. 2. Determine if the database is Unicode by typing the following at the command prompt: db2 get database configuration for database_name The codepage is Unicode if it has a value of 1208. 3. If the codepage is not Unicode, create a new database that has a codepage value of 1208. 4. Ensure that you set the following configuration parameters. Property Application heap size (applheapsz) Lock Timeout Setting 1024k 4 min. (or 240 sec.)

On Solaris and Linux: LD_LIBRARY_PATH On AIX: LIBPATH On HP-UX: SHLIB_PATH

We recommend that you set the Lock Timeout configuration parameter to a reasonably long timeout value, such as four minutes or 240 seconds. Do not set it to an infinite timeout value. 5. Create a buffer pool with a page size of 16k. 6. Create a system temporary tablespace with a page size of 16k. 7. Create a user temporary tablespace with a page size of 4k. Global temporary tables will be created in the user temporary tablespace. 8. Create a regular user tablespace with a page size of 4k. 9. If you already created the content store and are now creating a logging database, create an additional regular user tablespace with a page size of 8k. Quick Start Installation and Configuration Guide 9

Installing and Configuring ReportNet on One Computer 10. Determine which user account ReportNet will use to access the content store. 11. Grant create and drop table privileges on the content store to the user account. Ensure that the user account has CREATETAB, CONNECT and IMPLICITSCHEMA privileges for the content store. Ensure that the user account has USE privileges for the USER TEMPORARY tablespace and other appropriate tablespaces associated with the content store. For Windows XP, ensure that the user account has GRANT privileges for the USER TEMPORARY tablespace.

Install ReportNet
To install ReportNet, use the installation wizard to copy all the components to your computer.

Steps
1. Set the JAVA_HOME environment variable to point to the installation location of your Java Runtime Environment (JRE). 2. Insert the CD that is appropriate for your operating system. On UNIX, you must mount the CD using Rock Ridge file extensions. The Welcome page of the installation wizard should appear. 3. If no Welcome page appears, do one of the following: On Windows, in the win32 directory on the CD, double-click the xwsetup.exe file. On UNIX and Linux, type ./xstartup

4. Select the language to use for the installation. 5. Copy the required files to your computer. Follow the directions in the installation wizard. For a complete installation of ReportNet, you need all the components that are installed by default. To install only some components, or for a distributed installation, see the Installation and Configuration Guide on the CD. 6. In the Finish page of the installation wizard, click Start Cognos Configuration and then click Finish. 7. On UNIX and Linux, append the crn_location/bin directory to the appropriate library path environment variable: For Solaris and Linux, LD_LIBRARY_PATH For AIX, LIBPATH For HP-UX, SHLIB_PATH

If you will use Oracle or DB2 databases, you must set up the JDBC drivers. For DB2, you must also install the DB2 client on the ReportNet computer. For more information, see the Installation and Configuration Guide on the CD.

Update Your JAVA Runtime Environment on UNIX

Before you can use the cryptographic operations, such as data encryption and key management, implemented by ReportNet, you must check that the required JAR (Java Archive) files are present in your Java Runtime Environment (JRE). On Windows, this is done automatically when you install ReportNet. Before updating your JRE on UNIX and Linux, ensure you have the correct version of a JRE installed: Sun Solaris: 1.3.1_07 HP-UX: 1.3.1_08

10 Cognos ReportNet(TM)

Installing and Configuring ReportNet on One Computer IBM AIX: 1.3.1 (ca131-20030122a) Linux: 1.3.1 SR6

Steps
1. Ensure that the JAVA_HOME environment variable is set to the JRE location. 2. Check that the following JAR (Java Archive) files exist in the JRE_location/lib/ext: sunjce_provider.jar US_export_policy.jar local_policy.jar jce1_2_1.jar jcert.jar jnet.jar jsse.jar bcprov-jdk13-113.jar

Tip: An example of the installation location of a Java Runtime Environment is /directory/java/java_version/jre. 3. If any files are missing, go to crn_location/bin/jre/1.3.1/lib/ext directory and copy the appropriate JAR files to the JRE_location/lib/ext directory. To ensure the security and integrity of ReportNet, it is important to protect the installation directory from unauthorized or inappropriate access.

Configuring ReportNet
After you install ReportNet on your computer, some of the following configuration tasks are required: Configuring your Web server

Set the database connection properties for the content store Configure a mail server account

Configuring Your Web Server

Before you use Web pages generated by ReportNet, you must configure your Web server. You must set up virtual directories, also known as Web aliases, for the directories that contain the HTML and Web files for ReportNet. The virtual directories in the Alias column of the following table are required for all Web servers. Alias crn crn/cgi-bin crn/help Location crn_location\webcontent crn_location\cgi-bin crn_location\webcontent\documentation Permission Read Execute Read

Set Database Connection Properties for the Content Store

You you must specify the database server information to ensure that ReportNet can connect to the database you use for the content store. Content Manager uses the database logon to access the content store.

Quick Start Installation and Configuration Guide 11

Installing and Configuring ReportNet on One Computer

Steps for Oracle and DB2 Databases

1. Start Cognos Configuration. 2. In the Explorer window, under Data Access, Content Manager, right-click Content Store and click Delete. This deletes the default resource. ReportNet must be configured to access only one content store. 3. Right-click Content Manager, and then click New resource, Database. 4. In the Name box, type a name for the resource. 5. In the Type box, select the type of database and click OK. 6. In the Properties window: If you are use a DB2 database, for the Database name property, type the database alias. If you use an Oracle database, type the appropriate values for the Database server and port number and Service name properties.

7. Click the Value box next to the User ID and password property and then click the edit button when it appears. 8. Type the appropriate values in the Value - User ID and password dialog box and then click OK. 9. From the File menu, click Save. The logon credentials are immediately encrypted.

Steps for Microsoft SQL Server

1. Start Cognos Configuration. 2. In the Explorer window, under Data Access, Content Manager, click Content Store. By default, ReportNet uses properties for a Microsoft SQL Server database. 3. If necessary, in the Properties window, change the default value for the Database server and port number. 4. For the Database name property, type the name of the database you previously created in Microsoft SQL Server to use as the content store. 5. Click the Value box next to the User ID and password property and then click the edit button when it appears. 6. In the Value - User ID and password dialog box, type the appropriate values and then click OK. 7. From the File menu, click Save. The logon credentials are immediately encrypted.

Configure a Mail Server Account (Optional)

If you want to send reports by email, you must configure a mail server account.

Steps
1. On each computer where Content Manager is installed, start Cognos Configuration. 2. In the Explorer window, under Data Access, click Notification. 3. In the Properties window, for the SMTP mail server property, type the host name and port of your SMTP (outgoing) mail server. 4. Click the Value box next to the Account and password property and then click the edit button when it appears.

12 Cognos ReportNet(TM)

Installing and Configuring ReportNet on One Computer 5. Type the appropriate values in the Value - Account and password dialog box and then click OK. Tip: If logon credentials are not required for the SMTP server, remove the default information for the Account and password property. When you are prompted for confirmation to leave this property blank, click Yes. Ensure that the default user name has been removed. Otherwise, the default account is used and notifications will not work properly. 6. In the Properties window, type the appropriate value for the default sender account. 7. Identify the database that is used for notification: In the Explorer window, right-click Notification and select New resource, Database. Type a name for the database resource. Select the type of database from the pull-down menu. Click OK.

8. In the Properties window, enter the values for the notification database resource. Ensure that the values match on all Content Manager computers. Tip: To use the default notification database, you do not have to perform this step. 9. From the File menu, click Save.

Test ReportNet
You can test your installation and configuration by starting the ReportNet service and then opening Cognos Connection, the ReportNet Web portal. On Windows, the ReportNet service is configured to start automatically by default. On UNIX and on Linux, to start the ReportNet process automatically, you must configure the process as a daemon. For more information, see your operating system documentation. You must install and configure both ReportNet and Framework Manager before you can use ReportNet for reporting.

Steps
1. Start Cognos Configuration. 2. Ensure that you save your configuration, otherwise you will not be able to start the ReportNet service. If you are upgrading, a message appears indicating that configuration files were detected and upgraded to the new version. 3. From the Actions menu, click Start. It may take a few minutes for the ReportNet service to start. 4. Open a Web browser. 5. Type the following, where crn is the virtual directory you created when you configured the Web server: http://computer_name/crn It may take a few minutes for the Web page to open. If you see the Welcome page of Cognos Connection, your installation is working.

Install Framework Manager

To install Framework Manager, use the installation wizard to copy all the components to your computer.

Quick Start Installation and Configuration Guide 13

Installing and Configuring ReportNet on One Computer

Steps
1. Insert the Framework manager CD, and then open the installation menu. The Welcome page of the installation wizard should appear. 2. If no Welcome page appears, in the win32 directory on the CD, double-click the xwsetup.exe.file. 3. Select the language to use to run the installation wizard. 4. Follow the directions in the installation wizard to copy the required files to your computer. To ensure the security and integrity of ReportNet, it is also important to protect the installation directory from unauthorized or inappropriate access.

Test Framework Manager

Before you can use Framework Manager, you must start the ReportNet service.

Steps
1. Start ReportNet. 2. From the Start menu, click Cognos ReportNet, Framework Manager. Framework Manager starts. You may be prompted to upgrade if the model schema version is older than the currently supported version. 3. Create a new project. 4. Publish the project to the content store.

Setting Up Samples
ReportNet provides sample databases for SQL Server, Oracle, and DB2 that contain sales and marketing information for a fictional company named the Great Outdoors. You can use Cognos sample packages and reports to help you learn how to use ReportNet and Framework Manager. ReportNet also provides commented code samples that you can use as examples when you create your own applications. For more information, see the Developer Guide.

Restore Backup Files for the Samples Databases

To use the sample model, package, and reports, 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 ReportNet. Each database is delivered as a Microsoft SQL Server backup file, Oracle export file (.dmp), and DB2 move files. The DB2 move files are compressed, and you must extract them before you can restore the DB2 databases. Database description Great Outdoors sales

SQL Server file gosl

Oracle file gosl.dmp

DB2 file gosl.tar.gz

14 Cognos ReportNet(TM)

Installing and Configuring ReportNet on One Computer Database description Great Outdoors retailers Great Outdoors sales data warehouse

SQL Server file gort gosldw

Oracle file gort.dmp gosldw.dmp

DB2 file gort.tar.gz gosldw.tar.gz

Important: You must give the restored databases the same names as the backup or export file names for the sample model, package, and reports for them to work. Ensure that you restore the samples databases using the UTF-8 character set. Before you restore the samples databases, ensure that you have 50 MB of disk space available in the target location.

SQL Server Considerations

If you restore the SQL Server backup files, you must use Microsoft SQL Server 2000 or Microsoft SQL Server 7. Ensure that TCP/IP connectivity is used for the SQL server.

DB2 Considerations
Before you restore the DB2 move files on Unix or Windows, extract the DB2 move files by using the gnutar -xcvf DB2_move_file_name or tar -xcvf DB2_move_file_name command. Also, when you set up the Great Outdoors Sales Data Warehouse database in DB2, create a large buffer pool of 16kb and an associated tablespace. If you use WinZip to extract the DB2 move files on Windows, ensure that the TAR file smart CR/LF conversion option is not selected.

Steps
1. On the computer where ReportNet is installed, go to the sqlserver, oracle, or db2 directory located in crn_location/webcontent/samples/db. 2. If required, copy the backup files for the samples databases to your database backup directory. To ensure the security and integrity of ReportNet, copy the files to a directory that is protected from unauthorized or inappropriate access. 3. Restore the four samples databases with 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 Microsft 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. ReportNet uses this information to connect to the samples databases and run the sample reports or use the sample package. The DB2 database names 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.

Quick Start Installation and Configuration Guide 15

Installing and Configuring ReportNet on One Computer Before you create the data source connections, you must restore the backup files for the samples databases. Also, ensure that ReportNet is running. To create data sources, you must have execute permissions for the Administration secured function.

Steps
1. Open Cognos Connection. 2. On the toolbar, click Directory. 3. Click the Data Sources tab. 4. Click the new data source button. 5. In the Name box, type gosales, 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. 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 gosl 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 databases in DB2, in the DB2 database name box, type GOSL using uppercase letters. In the DB2 connect string box, type the DB2 connection string.

8. Under Signons, select the User ID, 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 goretailers and gosldw samples databases. For the goretailers database in SQL Server and Oracle, type goretailers for the data source name and gort for the database name. For DB2, type goretailers for the data source name and GORT for the database name. For the gosldw database in SQL Server and Oracle, type go_data_warehouse for the data source name and gosldw for the database name. For DB2, type go_data_warehouse for the data source name and GOSLDW 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

Modify the Sample Model for Oracle and DB2

The sample model is based on the gosl and gort samples databases. Because the sample model is built in Microsoft SQL Server, if you want to use it with the samples databases in Oracle or DB2, you must modify its data source properties. Before you can modify the sample model, the data source connections to the samples databases must be created.

16 Cognos ReportNet(TM)

Installing and Configuring ReportNet on One Computer

Steps
1. Start Framework Manager. 2. On the Welcome page, click Open a project. 3. Go to the crn_location\webcontent\samples\Models\gosales_goretailers directory, click the gosales_goretailers.cpf file, and then click Open. 4. In the Project Viewer pane, expand the Data Sources folder, and click gosales. The properties of the data source appear in the Properties pane. 5. Click the Content Manager Datasource property, delete the existing setting, type the name of the Oracleor DB2 data source. Tip: To edit a property value, you can click the ellipses button next to the value. 6. Click the Catalog property and delete the existing setting. 7. Click the Schema property, delete any existing setting, and type the name of the schema for Oracle or DB2 that you specified when you set up the data sources. The schema name is the name of the database. The schema name is case sensitive. 8. Double-click the Type property, click the Interface property, delete the existing setting, and type OR for Oracle or D2 for DB2. 9. If you want to test the modified data source properties, in the Project Viewer pane, in the Data Sources folder, right-click gosales, and then click Test Data Source. A message informs you whether the test was successful. 10. Repeat steps 4 to 9 for the goretailers and go_data_warehouse data sources.

Import the Samples

To use the sample package and reports, you must import them from the sample deployment archive using the deployment tool. Before you import the samples, you must restore the databases. For each database, you must create one or more named user with Select permissions for the database tables. You must also create data source connections to the samples databases. To use the deployment tool, you must have execute permissions for the Administration secured function.

Steps
1. Copy the Cognos_Samples.zip file from the crn_location/webcontent/samples/content directory to the directory where your deployment archives are saved. The default location is crn_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. On the toolbar, click Deployment. 4. Click the Import tab. 5. On the toolbar, click the new import button. 6. In the Deployment archive box, click Cognos_Samples and then click Next. 7. If you want, type a description and screen tip for the deployment specification. 8. Select the folder where you want to save the specification, and then click Next. 9. In the Public folders content list, select the check box for the sample package you want to import, either GO Sales and Retailers or Go Data Warehouse.

Quick Start Installation and Configuration Guide 17

Installing and Configuring ReportNet on One Computer 10. If you do not want users to access the sample package and its entries, select the check box in the Disable after import column. This is useful when you want to test the reports before you make them available in the target environment. 11. Click Next. 12. In the Specify the general options page, click Next. The summary information appears. Tip: If you want to change information, click Back and follow the instructions. 13. Click Import Now. ReportNet imports the sample package. This may take a few minutes. 14. When the import is done, click Finish. You can now use the sample package to create reports in Cognos Report Studio and Query Studio. You can also run the sample reports that are available on the Public Folders tab in the portal

Whats Next?
You successfully installed and configured ReportNet. To take a tour of ReportNet, start Cognos Connection and select Quick Tour. For information about using ReportNet, see these documents: Topic How to get started using ReportNet Location ReportNet Getting Started

How to set up security and ReportNet Administration and perform other administrative tasks Security Guide How to create and publish models Framework Manager User Guide using Framework Manager How to author professional reports using Cognos Report Studio How to create ad-hoc reports using Query Studio How to administer and view reports in the Cognos Connection portal How to use the ReportNet software development kit How to identify and troubleshoot problems Cognos Report Studio User Guide

Query Studio User Guide ReportNet User Guide

ReportNet Developer Guide ReportNet Troubleshooting Guide

18 Cognos ReportNet(TM)

Index
C
Cognos documentation finding, 18 configuration testing, 13 configuring content store, 11 mail server, 12 ReportNet, 11 Web servers, 11 content store configuring, 11 creating, 7 creating DB2, 9 creating Microsoft SQL Server, 7 creating Oracle, 8 DB2, 12 Microsoft SQL Server, 12 Oracle, 12 copyright, 2 creating content store, 7 DB2 content store, 9 environments (cont'd) supported operating systems, 7

I
importing samples, 17 installation ReportNet on UNIX, 6 testing, 13 installing Framework Manager, 13 ReportNet, 10

J
JAR, 10 Java Archive files (JAR), 10 updating in UNIX, 10 Java Runtime Environment (JRE), 10 JDBC database connectivity for content store, 7

M
mail server configuring, 12 Microsoft SQL Server configuring content store, 12 creating content store, 7 database connectivity, 7 Microsoft SQL server database connectivity, 7 models modifying for samples, 16 modifying sample models, 16

D
data source connections creating for Cognos samples, 15 database connectivity requirements for content store, 7 requirements for reporting, 7 databases configuring content store, 11 DB2 configuring content store, 12 creating content store, 9 database connectivity, 7 environment variables, 9 document version, 2 documentation, 18

O
ODBC, 7 Oracle configuring content store, 12 creating content store, 8 database connectivity, 7 environment variables, 8

E
environment variables DB2, 9 Oracle, 8 environments supported, 7

P
product version, 2

Quick Start Installation and Configuration Guide 19

Index

R
ReportNet system requirements on UNIX, 6 requirements database connectivity for content store, 7 database connectivity for reporting, 7

S
samples importing, 17 setting up, 14 setting up samples, 14 SQL Server databases creating content store, 7 SQL Server, See Microsoft SQL Server supported environments, 7 system requirements ReportNet on UNIX, 6

T
testing Framework Manager installation, 14 ReportNet configuration, 13 ReportNet installation, 13

U
UDB, See DB2 UNIX updating, 10 updating JRE in UNIX, 10

V
version product, 2

W
Web servers configuring, 11

20 Cognos ReportNet(TM)