Steps for oracle 9i configure in reportnet

[phani1979]

hai
previously i had done in mssqlserver 2000 but things changes..
Can anyone tell me the steps for configure in oracle9i for reportnet
how to do  in oracle9i.. and
In cognos.com  ease it possible to download the video clippings for reportnet
tell me how
thank u
sudhakar

[mikegreen]

See the documentation, there is a section for copying the JDBC drivers over and what settings to apply to your Oracle schema.

You have to have a support.cognos.com account to get the videos.  Call your sales rep or the support # to get your customer # to create a login.

Cheers,

Mike

[phani1979]

Hi Thank u for u reply,,
But actually what i did in MsSqlServer200, we create threee virtual dicrectories.. crn, cgi-bin, help in IIS;
2) we create three databses in MSSqlserver2000  ,as , crn,gosl,gort..  and we restore the database,, by giving the path in cognos/crn/webcontent/samples/db/... what ever may be the databasee..
then we go for cognos configuration..
This time It's different for me . I Have to create a connection through Oracle..
can u give me the clear steps for configuring things in oracle for cognos..
thank u
Sudhakar

[BIsrik]

did u check on the installation documents..U don't need to configure ur content store to look into it..

Srik

[Desperado]

Here it is :

1   Purpose
ââ,¬Â¢   This is a brief guide to installing Cognos ReportNet with the Content Store hosted on Oracle.
ââ,¬Â¢   The ReportNet install on Oracle is slightly different to installing with SQL Server. Microsoft allow their JDBC driver to be freely distributed by 3rd parties, so Cognos install it automatically with ReportNet. This makes life easy. Oracle do not allow their JDBC driver to be freely distributed, so it is not installed by ReportNet; you must do so manually. This is straightforward, but an extra twist for you.

2.1   Process Overview

2.2   Preparation
ââ,¬Â¢   Disable any anti-virus services; they'll really slow down the install.
2.3   Installation
2.3.1   Install ReportNet
ââ,¬Â¢   Install ReportNet by selecting crcd\win32\xwsetup.exe
(This script assumes you install in C:\Program Files, but for security reasons youââ,¬â,,¢re better off installing on a non-system drive).
ââ,¬Â¢   When this completes, click Finish, without selecting the Configuration option. Weââ,¬â,,¢ll do this later.
2.3.2   Install Framework Manager
ââ,¬Â¢   Install Framework Manager by selecting fmcd\win32\xwsetup.exe.
ââ,¬Â¢   When this completes, click Finish, without selecting the Configuration option. Weââ,¬â,,¢ll do this later.
2.3.3   Create Content Store Database
2.3.3.1   Make sure your Oracle Install is Unicode.
ââ,¬Â¢   ReportNet requires a Unicode installation of Oracle and will not work without it. This is a parameter that is set when Oracle was installed and cannot be subsequently changed.
ââ,¬Â¢   Open a command prompt and enter the following, replacing user, password, and tnsnamesconnection with values appropriate to your Oracle database.
Sqlplus user/password@tnsnamesconnection
Select * from nls_database_parameters;

ââ,¬Â¢   Scroll to find the character set. It should be a Unicode character set, such as AL32UTF8. If so, you have a Unicode Oracle installation that can be used to host the ReportNet Content Store.

2.3.3.2   Copy your Oracle JDBC class file into ReportNet
ââ,¬Â¢   Copy classes12.zip:
From:   oracle_home\jdbc\lib
To:   crn\webapps\p2pd\web-inf\lib
ââ,¬Â¢   Rename the copied classes12.zip to classes12.jar.
ââ,¬Â¢   If you want an easy life you MUST use the file from the copy of Oracle that you are going to use for the Content Store: it's VERY fussy about versions.
2.3.3.3   Create Oracle bi_contentstore user (you can use an alternate name if you like).
ââ,¬Â¢   Open Oracle Enterprise manager, expand the tree (log in when prompted), click on Schema and select Create in the right pane.

ââ,¬Â¢   Select User in the next dialogue, and click the Create button.
ââ,¬Â¢   In the Create User dialogue, enter the details for the user account that ReportNet will use to access Oracle. We will use a user name of ââ,¬Ëœbi_contentstoreââ,¬â,,¢ and a password of ââ,¬Ëœpasswordââ,¬â,,¢ for this example.

ââ,¬Â¢   On the Role tab, make sure the user has Connect and Resource roles.
ââ,¬Â¢   On the System tab, add alter any/create any /drop any rights for tables, triggers, procedures, and views.

ââ,¬Â¢   Select the Create button at the bottom.
2.3.3.4   Create Great Outdoors users.
ââ,¬Â¢   Expand the Security\Users branch of the tree.
ââ,¬Â¢   Right-click user bi_contentstore & select Create Likeââ,¬Â¦
ââ,¬Â¢   Enter a user name and password for the GOSales database.
ââ,¬Â¢   On the Roles tab, add dba. This is necessary to import the Great Outdoors data, but can be removed after this is done.
ââ,¬Â¢   Select Create.
ââ,¬Â¢   Do the same for:
o   GORetailers
o   GOSalesDW
o   GOResearch
ââ,¬Â¢   You will use these users to hold schemas for the CRN sample databases.
ââ,¬Â¢   Exit Oracle Enterprise Manager Console.
2.3.4   Create IIS Aliases
ââ,¬Â¢   Open Internet Service Manager and create the virtual directories that ReportNet needs.
Alias   Location   Rights
crn   C:\Program Files\Cognos\crn\Webcontent   Read
cgi-bin   C:\Program Files\Cognos\crn\cgi-bin   Script, Execute
help   C:\Program Files\Cognos\crn\Webcontent\Documentation   Read
2.3.5   ReportNet Configuration
ââ,¬Â¢   Open Start > Programs > Cognos ReportNet > Cognos Configuration.
ââ,¬Â¢   Under Data Access \ Content Manager \ Content Store, right-click Content Store and select delete. Cognos Configuration defaults to SQL Server so we need to remove and recreate this.
ââ,¬Â¢   Right-click Content Manager and select New Resource \ Database.
ââ,¬Â¢   Call the new resource Content Store and select Oracle database from the drop-down. Click OK.

ââ,¬Â¢   Complete the Content Store properties, using the same details as used in Oracle.
ââ,¬Â¢   If your Oracle Service Name (found in tnsnames.ora) is multi-segment, you should enter only the first segment. In this example, our full service name is Cognos.Cognos.com, but we are only entering Cognos into ReportNet Configuration.

ââ,¬Â¢   Save the settings in Cognos Configuration using the icon that looks like a floppy disk. Don't hit the start button yet.

2.3.6   Testing
2.3.6.1   Start Tomcat Manually
ââ,¬Â¢   Open a command prompt, navigate to C:\Program Files\crn\bin and run Startup to start Tomcat manually.
ââ,¬Â¢   This sets an environment variable to tell Tomcat how much memory to use, and starts Tomcat in a new command window.
ââ,¬Â¢   Starting Tomcat this way allows you to see any errors & is a good way of debugging to make sure all is well.
ââ,¬Â¢   If you get a bunch of java/JDBC errors you are missing, or using the wrong, JDBC classes12.jar file.
o   Oops, someone forgot to copy & rename the classes12.zip fileââ,¬Â¦

ââ,¬Â¢   Otherwise you should only get fairly self-explanatory errors about:
o   Not being able to see the database (can you connect with Oracle SQL*Plus?)
o   Not having sufficient permissions (in SQL*Plus enter 'select * from user_role_privs;')
ââ,¬Â¢   If your Oracle service name in tnsnames.ora is multi-segment (e.g. wbrajeffrebr.Cognos.com) and Tomcat is giving you an error on startup, try using just the first segment.
ââ,¬Â¢   Once Tomcat is started successfully you get a message saying the dispatcher is ready (ignore the log4j error status message).

2.3.6.2   Test ReportNet by Opening Cognos Connection
ââ,¬Â¢   Open IE & browse to Localhost/crn.
ââ,¬Â¢   This should take you to Cognos Connection - the 'user experience.' If so, your install has worked.
2.4   Install Samples
ââ,¬Â¢   Weââ,¬â,,¢ll install the Great Outdoors samples, so you have something with which to experiment.
2.4.1   Restore Databases
ââ,¬Â¢   Open a command prompt at C:\Cognos\crn\webcontent\samples\db\oracle, where you will see four .dmp files.
ââ,¬Â¢   Enter the following in turn, hitting enter after each one. You should get a bunch of messages telling you how many rows were imported:
o   imp file=gosl.dmp fromuser=gosl (at userid/password prompt enter gosales/gosales)
o   imp file=gort.dmp fromuser=gort (at userid/password prompt enter goretailers/goretailers)
o   imp file=gosldw.dmp fromuser=gosldw (at userid/password prompt enter gosalesdw/gosalesdw)
o   imp file=gomr.dmp fromuser=gomr (at userid/password prompt enter goresearch/goresearch)
ââ,¬Â¢   In Oracle Enterprise you should now see 4 schemae (gosales, etc) with tables.

2.4.2   Define Data Sources in ReportNet
ââ,¬Â¢   In Cognos Connection (http://localhost/crn) select Directory, Data Sources, New Data Source (icon).
ââ,¬Â¢   Set up the four sample databases using the names GOSales, GORetailers, etc. The Framework Manager model expects these names.
ââ,¬Â¢   The Oracle connection string should be the same as the service name in tnsnames.ora on the server (eg. Cognos.Cognos.com)
ââ,¬Â¢   Use the different userids/passwords for each (eg. gosales/gosales), as set up in Oracle.
ââ,¬Â¢   You can leave the collation sequence blank (but make sure you select the password checkbox).
ââ,¬Â¢   Test the connections as you set them up.

2.4.3   Publish Framework Manager Package
ââ,¬Â¢   Open Framework Manager.
ââ,¬Â¢   Open project C:\Program Files\Cognos\crn\webcontent\samples\models\gosales_goretailers
ââ,¬Â¢   Click OK to ignore the message telling you the model was created in US English & youââ,¬â,,¢re using UK English.
ââ,¬Â¢   Select the gosales data source, enter 'gosales' for schema, double-click type, change the interface to 'OR'
ââ,¬Â¢   Do similar for goretailers.
ââ,¬Â¢   Right-click each data source & test them.
ââ,¬Â¢   If the connection fails, select the data source and check that the cmDataSource property matches the name you have defined in Cognos Connection.
ââ,¬Â¢   Once all data sources have tested OK, expand the Packages branch, right-click GO Sales and Retailers and publish the package. You can ignore the package versioning options for now.
ââ,¬Â¢   Save the model and exit Framework Manager.
2.4.4   Import Sample Reports
Now we have databases defined, a connection to them from ReportNet, and the metadata model published. All we need now is the sample reports to run.
ââ,¬Â¢   Copy Cognos_Samples.zip from crn\webcontent\samples\content to crn\deployment
ââ,¬Â¢   In Cognos Connection, select Home (if youââ,¬â,,¢re not already there), Deployment, Import tab, New Import (icon).
ââ,¬Â¢   Cognos_Samples should appear in the list. Select Next, then Next again.
ââ,¬Â¢   On the ââ,¬ËœSelect the Public Folders Contentââ,¬â,,¢ page, select the checkbox to the left of the Cognos_Samples package.
ââ,¬Â¢   Select Next, Next again, then Import Now.
2.4.5   Test Sample Reports
ââ,¬Â¢   Select Home (if youââ,¬â,,¢re not there already), Public Folders, GO Sales and Retailers, Report Studio Report Samples, and select a report (GO Media is a good one to try).
ââ,¬Â¢   It might take a few seconds to run the first report as everything fires up.
ââ,¬Â¢   Run some more reports and queries to check that everything is working, and see whatââ,¬â,,¢s available to you.
2.5   Finishing Up
ââ,¬Â¢   ReportNet is now up and running.
ââ,¬Â¢   The only thing left to do is to run ReportNet from the Service, rather than Tomcat.
2.5.1   Use the ReportNet Service
ââ,¬Â¢   Exit Cognos Connection.
ââ,¬Â¢   Stop Tomcat by going to the command prompt window at crn\bin and typing shutdown. The Tomcat window should close after a few seconds. You can now close all your command prompt windows.
ââ,¬Â¢   Open Cognos Configuration and select the Start button. This may take a couple of minutes as it registers and starts ReportNet services.
ââ,¬Â¢   Once ReportNet has started, you can exit Cognos Configuration and go back to Cognos Connection; you do not need to run Tomcat from a command prompt now.
3   Upgrade
ReportNet upgrades are joyfully simple; you just install the new version over the old. In practice youââ,¬â,,¢re going to want to be a bit more cautious.
3.1   Process Overview

3.2   Backup Your System!
ââ,¬Â¢   You can do this 2 ways.... and should use both.
3.2.1   1. Deployment
ââ,¬Â¢   Log into Cognos Connection as administrator, select deployment, and export.
ââ,¬Â¢   Select the New Export iconÃ, 
ââ,¬Â¢   Follow the prompts: give it a name > select the entire Content Store, do not include user account information > Set the encryption password > Export Now.
ââ,¬Â¢   Once the export has completed, you should have a new zip file in crn\deployment. You might want to check itââ,¬â,,¢s actually there.
ââ,¬Â¢   Copy this file to a backups folder, so itââ,¬â,,¢s out of harmââ,¬â,,¢s way and date-stamp it.
3.2.2   Database Export/Backup
ââ,¬Â¢   Backup your Oracle Content Store database manually, so you can recover the database.
ââ,¬Â¢   You can use the Oracle export command to do this:
exp parfile=crn_backup.par
ââ,¬Â¢   Where the parameter file crn_backup.par looks something like:
USERID=BI_CONTENTSTORE/password@cognos.cognos.com
FILE=D:\Backups\ContentStoreDB.dmp
LOG=D:\Backups\ContentStoreDB.log
COMPRESS=n
GRANTS=y
INDEXES=y
CONSTRAINTS=y
TRIGGERS=y
STATISTICS=NONE
ROWS=y
OWNER=BI_CONTENTSTORE
DIRECT=Y
CONSISTENT=Y
ââ,¬Â¢   (Type ââ,¬Ëœexp help=yââ,¬â,,¢ for help on export parameters)
ââ,¬Â¢   This gives you a second independent means of recovering your system; a good ââ,¬Ëœbelt-and-bracesââ,¬â,,¢ approach.
3.2.3   Backup Customised Files
ââ,¬Â¢   Any XML or other files you have changed or added (e.g. corporate logos) should be saved. Zipping them into an archive is best, as you can them be sure they wonââ,¬â,,¢t be used subsequently by mistake.
ââ,¬Â¢   To be cautious you could zip all XML files under crn\webcontent - maybe all XML files under crn (although there are 600+). Do a Windows search for .XML, select the resultant files, and zip them into an archive.
3.3   Upgrade ReportNet
3.3.1   Stop Services
ââ,¬Â¢   Stop World Wide Web Publishing (IIS).
ââ,¬Â¢   Stop the ReportNet service.
ââ,¬Â¢   This prevents files being locked when the upgrade tries to replace them. If you do not do this, the upgrade will stop halfway through without giving you an error message; itââ,¬â,,¢s failed if you donââ,¬â,,¢t get a ââ,¬Ëœfinishedââ,¬â,,¢ dialogue.
3.3.2   Install ReportNet Upgrade
ââ,¬Â¢   Select the xwsetup.exe file and following the prompts.
3.3.3   Start Services
ââ,¬Â¢   Start World Wide Web Publishing service.
ââ,¬Â¢   Open Cognos Configuration, save settings, and start the service. Whilst not absolutely necessary, itââ,¬â,,¢s probably a good idea to regenerate cryptographic keys, etc.
3.3.4   Test ReportNet
ââ,¬Â¢   Open Cognos Connection, and run some reports.
ââ,¬Â¢   Select About on the home page and confirm the new version of ReportNet.
ââ,¬Â¢   If you hit problems, you might want to stop the ReportNet service and start Tomcat manually to see if it gives you any errors.
4   Other Topics
4.1   How to Check if Oracle is Already Installed
ââ,¬Â¢   Open a Command Prompt and type ââ,¬Å"SQLPlusââ,¬Â
ââ,¬Â¢   You should get one of the following responses.
ââ,¬Â¢   Doesnââ,¬â,,¢t look like we have Oracle installed yet ââ,¬Â¦ you need to install Oracle.

ââ,¬Â¢   Oracle is installed, so you just need to check itââ,¬â,,¢s Unicode.

4.2   Installing Oracle
ââ,¬Â¢   Double-click setup.exe. If this has no effect, double-click install\win32\setup.exe

ââ,¬Â¢   Click Next.
ââ,¬Â¢   At the File Locations screen, you should be able to accept the defaults. Click Next.
ââ,¬Â¢   Available Products. Oracle 9i Database should be selected by default. Click Next.
ââ,¬Â¢   Installation Types. Select Standard Edition (2.80GB). Click Next.
ââ,¬Â¢   Database Configuration. Leave on the default option, General Purpose. Click Next.
ââ,¬Â¢   Oracle Services for Microsoft Transaction Server. Leave on default and click Next.
ââ,¬Â¢   Database Identification. Enter a database name; one that matches your DNS suffix might not be a bad idea, for example ââ,¬Å"Cognos.comââ,¬Â. The SID is filled in for you. Click Next.
ââ,¬Â¢   Database File Location. Leave the default. Click Next.
ââ,¬Â¢   Database Character Set. DO NOT leave the default! Select ââ,¬Å"Use Unicode (AL32UTF8) as the Character Set.ââ,¬Â Click Next.

ââ,¬Â¢   Summary. Click Install.
ââ,¬Â¢   Go get a cup of coffee. Donââ,¬â,,¢t rush back. Youââ,¬â,,¢ll need to be around to give Oracle the location of disks 2& 3.
ââ,¬Â¢   After the install has completed, provide SYS and SYSTEM passwords (Iââ,¬â,,¢ll use ââ,¬Ëœadminââ,¬â,,¢ for both for this example).
ââ,¬Â¢   At the End of Installation screen, note the HTTP port numbers (although you should not need them) and click Exit.
ââ,¬Â¢   Oracle Enterprise Manager Console will now open, and a Command window will be open, running Oracle HTTP server (which we donââ,¬â,,¢t need).
ââ,¬Â¢   In Enterprise Manager, expand the tree until you get a log in window. Enter SYS and your password from earlier, Connect as SYSDBA and select OK. This should log you into the console.
ââ,¬Â¢   Exit Enterprise Manager and the HTTP command window.
ââ,¬Â¢   Open a Command Prompt and type ââ,¬Å"SQLPlusââ,¬Â. You should get the following screen.

[Desperado]

Here it is :

1   Purpose
ââ,¬Â¢   This is a brief guide to installing Cognos ReportNet with the Content Store hosted on Oracle.
ââ,¬Â¢   The ReportNet install on Oracle is slightly different to installing with SQL Server. Microsoft allow their JDBC driver to be freely distributed by 3rd parties, so Cognos install it automatically with ReportNet. This makes life easy. Oracle do not allow their JDBC driver to be freely distributed, so it is not installed by ReportNet; you must do so manually. This is straightforward, but an extra twist for you.

2.1   Process Overview

2.2   Preparation
ââ,¬Â¢   Disable any anti-virus services; they'll really slow down the install.
2.3   Installation
2.3.1   Install ReportNet
ââ,¬Â¢   Install ReportNet by selecting crcd\win32\xwsetup.exe
(This script assumes you install in C:\Program Files, but for security reasons youââ,¬â,,¢re better off installing on a non-system drive).
ââ,¬Â¢   When this completes, click Finish, without selecting the Configuration option. Weââ,¬â,,¢ll do this later.
2.3.2   Install Framework Manager
ââ,¬Â¢   Install Framework Manager by selecting fmcd\win32\xwsetup.exe.
ââ,¬Â¢   When this completes, click Finish, without selecting the Configuration option. Weââ,¬â,,¢ll do this later.
2.3.3   Create Content Store Database
2.3.3.1   Make sure your Oracle Install is Unicode.
ââ,¬Â¢   ReportNet requires a Unicode installation of Oracle and will not work without it. This is a parameter that is set when Oracle was installed and cannot be subsequently changed.
ââ,¬Â¢   Open a command prompt and enter the following, replacing user, password, and tnsnamesconnection with values appropriate to your Oracle database.
Sqlplus user/password@tnsnamesconnection
Select * from nls_database_parameters;

ââ,¬Â¢   Scroll to find the character set. It should be a Unicode character set, such as AL32UTF8. If so, you have a Unicode Oracle installation that can be used to host the ReportNet Content Store.

2.3.3.2   Copy your Oracle JDBC class file into ReportNet
ââ,¬Â¢   Copy classes12.zip:
From:   oracle_home\jdbc\lib
To:   crn\webapps\p2pd\web-inf\lib
ââ,¬Â¢   Rename the copied classes12.zip to classes12.jar.
ââ,¬Â¢   If you want an easy life you MUST use the file from the copy of Oracle that you are going to use for the Content Store: it's VERY fussy about versions.
2.3.3.3   Create Oracle bi_contentstore user (you can use an alternate name if you like).
ââ,¬Â¢   Open Oracle Enterprise manager, expand the tree (log in when prompted), click on Schema and select Create in the right pane.

ââ,¬Â¢   Select User in the next dialogue, and click the Create button.
ââ,¬Â¢   In the Create User dialogue, enter the details for the user account that ReportNet will use to access Oracle. We will use a user name of ââ,¬Ëœbi_contentstoreââ,¬â,,¢ and a password of ââ,¬Ëœpasswordââ,¬â,,¢ for this example.

ââ,¬Â¢   On the Role tab, make sure the user has Connect and Resource roles.
ââ,¬Â¢   On the System tab, add alter any/create any /drop any rights for tables, triggers, procedures, and views.

ââ,¬Â¢   Select the Create button at the bottom.
2.3.3.4   Create Great Outdoors users.
ââ,¬Â¢   Expand the Security\Users branch of the tree.
ââ,¬Â¢   Right-click user bi_contentstore & select Create Likeââ,¬Â¦
ââ,¬Â¢   Enter a user name and password for the GOSales database.
ââ,¬Â¢   On the Roles tab, add dba. This is necessary to import the Great Outdoors data, but can be removed after this is done.
ââ,¬Â¢   Select Create.
ââ,¬Â¢   Do the same for:
o   GORetailers
o   GOSalesDW
o   GOResearch
ââ,¬Â¢   You will use these users to hold schemas for the CRN sample databases.
ââ,¬Â¢   Exit Oracle Enterprise Manager Console.
2.3.4   Create IIS Aliases
ââ,¬Â¢   Open Internet Service Manager and create the virtual directories that ReportNet needs.
Alias   Location   Rights
crn   C:\Program Files\Cognos\crn\Webcontent   Read
cgi-bin   C:\Program Files\Cognos\crn\cgi-bin   Script, Execute
help   C:\Program Files\Cognos\crn\Webcontent\Documentation   Read
2.3.5   ReportNet Configuration
ââ,¬Â¢   Open Start > Programs > Cognos ReportNet > Cognos Configuration.
ââ,¬Â¢   Under Data Access \ Content Manager \ Content Store, right-click Content Store and select delete. Cognos Configuration defaults to SQL Server so we need to remove and recreate this.
ââ,¬Â¢   Right-click Content Manager and select New Resource \ Database.
ââ,¬Â¢   Call the new resource Content Store and select Oracle database from the drop-down. Click OK.

ââ,¬Â¢   Complete the Content Store properties, using the same details as used in Oracle.
ââ,¬Â¢   If your Oracle Service Name (found in tnsnames.ora) is multi-segment, you should enter only the first segment. In this example, our full service name is Cognos.Cognos.com, but we are only entering Cognos into ReportNet Configuration.

ââ,¬Â¢   Save the settings in Cognos Configuration using the icon that looks like a floppy disk. Don't hit the start button yet.

2.3.6   Testing
2.3.6.1   Start Tomcat Manually
ââ,¬Â¢   Open a command prompt, navigate to C:\Program Files\crn\bin and run Startup to start Tomcat manually.
ââ,¬Â¢   This sets an environment variable to tell Tomcat how much memory to use, and starts Tomcat in a new command window.
ââ,¬Â¢   Starting Tomcat this way allows you to see any errors & is a good way of debugging to make sure all is well.
ââ,¬Â¢   If you get a bunch of java/JDBC errors you are missing, or using the wrong, JDBC classes12.jar file.
o   Oops, someone forgot to copy & rename the classes12.zip fileââ,¬Â¦

ââ,¬Â¢   Otherwise you should only get fairly self-explanatory errors about:
o   Not being able to see the database (can you connect with Oracle SQL*Plus?)
o   Not having sufficient permissions (in SQL*Plus enter 'select * from user_role_privs;')
ââ,¬Â¢   If your Oracle service name in tnsnames.ora is multi-segment (e.g. wbrajeffrebr.Cognos.com) and Tomcat is giving you an error on startup, try using just the first segment.
ââ,¬Â¢   Once Tomcat is started successfully you get a message saying the dispatcher is ready (ignore the log4j error status message).

2.3.6.2   Test ReportNet by Opening Cognos Connection
ââ,¬Â¢   Open IE & browse to Localhost/crn.
ââ,¬Â¢   This should take you to Cognos Connection - the 'user experience.' If so, your install has worked.
2.4   Install Samples
ââ,¬Â¢   Weââ,¬â,,¢ll install the Great Outdoors samples, so you have something with which to experiment.
2.4.1   Restore Databases
ââ,¬Â¢   Open a command prompt at C:\Cognos\crn\webcontent\samples\db\oracle, where you will see four .dmp files.
ââ,¬Â¢   Enter the following in turn, hitting enter after each one. You should get a bunch of messages telling you how many rows were imported:
o   imp file=gosl.dmp fromuser=gosl (at userid/password prompt enter gosales/gosales)
o   imp file=gort.dmp fromuser=gort (at userid/password prompt enter goretailers/goretailers)
o   imp file=gosldw.dmp fromuser=gosldw (at userid/password prompt enter gosalesdw/gosalesdw)
o   imp file=gomr.dmp fromuser=gomr (at userid/password prompt enter goresearch/goresearch)
ââ,¬Â¢   In Oracle Enterprise you should now see 4 schemae (gosales, etc) with tables.

2.4.2   Define Data Sources in ReportNet
ââ,¬Â¢   In Cognos Connection (http://localhost/crn) select Directory, Data Sources, New Data Source (icon).
ââ,¬Â¢   Set up the four sample databases using the names GOSales, GORetailers, etc. The Framework Manager model expects these names.
ââ,¬Â¢   The Oracle connection string should be the same as the service name in tnsnames.ora on the server (eg. Cognos.Cognos.com)
ââ,¬Â¢   Use the different userids/passwords for each (eg. gosales/gosales), as set up in Oracle.
ââ,¬Â¢   You can leave the collation sequence blank (but make sure you select the password checkbox).
ââ,¬Â¢   Test the connections as you set them up.

2.4.3   Publish Framework Manager Package
ââ,¬Â¢   Open Framework Manager.
ââ,¬Â¢   Open project C:\Program Files\Cognos\crn\webcontent\samples\models\gosales_goretailers
ââ,¬Â¢   Click OK to ignore the message telling you the model was created in US English & youââ,¬â,,¢re using UK English.
ââ,¬Â¢   Select the gosales data source, enter 'gosales' for schema, double-click type, change the interface to 'OR'
ââ,¬Â¢   Do similar for goretailers.
ââ,¬Â¢   Right-click each data source & test them.
ââ,¬Â¢   If the connection fails, select the data source and check that the cmDataSource property matches the name you have defined in Cognos Connection.
ââ,¬Â¢   Once all data sources have tested OK, expand the Packages branch, right-click GO Sales and Retailers and publish the package. You can ignore the package versioning options for now.
ââ,¬Â¢   Save the model and exit Framework Manager.
2.4.4   Import Sample Reports
Now we have databases defined, a connection to them from ReportNet, and the metadata model published. All we need now is the sample reports to run.
ââ,¬Â¢   Copy Cognos_Samples.zip from crn\webcontent\samples\content to crn\deployment
ââ,¬Â¢   In Cognos Connection, select Home (if youââ,¬â,,¢re not already there), Deployment, Import tab, New Import (icon).
ââ,¬Â¢   Cognos_Samples should appear in the list. Select Next, then Next again.
ââ,¬Â¢   On the ââ,¬ËœSelect the Public Folders Contentââ,¬â,,¢ page, select the checkbox to the left of the Cognos_Samples package.
ââ,¬Â¢   Select Next, Next again, then Import Now.
2.4.5   Test Sample Reports
ââ,¬Â¢   Select Home (if youââ,¬â,,¢re not there already), Public Folders, GO Sales and Retailers, Report Studio Report Samples, and select a report (GO Media is a good one to try).
ââ,¬Â¢   It might take a few seconds to run the first report as everything fires up.
ââ,¬Â¢   Run some more reports and queries to check that everything is working, and see whatââ,¬â,,¢s available to you.
2.5   Finishing Up
ââ,¬Â¢   ReportNet is now up and running.
ââ,¬Â¢   The only thing left to do is to run ReportNet from the Service, rather than Tomcat.
2.5.1   Use the ReportNet Service
ââ,¬Â¢   Exit Cognos Connection.
ââ,¬Â¢   Stop Tomcat by going to the command prompt window at crn\bin and typing shutdown. The Tomcat window should close after a few seconds. You can now close all your command prompt windows.
ââ,¬Â¢   Open Cognos Configuration and select the Start button. This may take a couple of minutes as it registers and starts ReportNet services.
ââ,¬Â¢   Once ReportNet has started, you can exit Cognos Configuration and go back to Cognos Connection; you do not need to run Tomcat from a command prompt now.
3   Upgrade
ReportNet upgrades are joyfully simple; you just install the new version over the old. In practice youââ,¬â,,¢re going to want to be a bit more cautious.
3.1   Process Overview

3.2   Backup Your System!
ââ,¬Â¢   You can do this 2 ways.... and should use both.
3.2.1   1. Deployment
ââ,¬Â¢   Log into Cognos Connection as administrator, select deployment, and export.
ââ,¬Â¢   Select the New Export iconÃ, 
ââ,¬Â¢   Follow the prompts: give it a name > select the entire Content Store, do not include user account information > Set the encryption password > Export Now.
ââ,¬Â¢   Once the export has completed, you should have a new zip file in crn\deployment. You might want to check itââ,¬â,,¢s actually there.
ââ,¬Â¢   Copy this file to a backups folder, so itââ,¬â,,¢s out of harmââ,¬â,,¢s way and date-stamp it.
3.2.2   Database Export/Backup
ââ,¬Â¢   Backup your Oracle Content Store database manually, so you can recover the database.
ââ,¬Â¢   You can use the Oracle export command to do this:
exp parfile=crn_backup.par
ââ,¬Â¢   Where the parameter file crn_backup.par looks something like:
USERID=BI_CONTENTSTORE/password@cognos.cognos.com
FILE=D:\Backups\ContentStoreDB.dmp
LOG=D:\Backups\ContentStoreDB.log
COMPRESS=n
GRANTS=y
INDEXES=y
CONSTRAINTS=y
TRIGGERS=y
STATISTICS=NONE
ROWS=y
OWNER=BI_CONTENTSTORE
DIRECT=Y
CONSISTENT=Y
ââ,¬Â¢   (Type ââ,¬Ëœexp help=yââ,¬â,,¢ for help on export parameters)
ââ,¬Â¢   This gives you a second independent means of recovering your system; a good ââ,¬Ëœbelt-and-bracesââ,¬â,,¢ approach.
3.2.3   Backup Customised Files
ââ,¬Â¢   Any XML or other files you have changed or added (e.g. corporate logos) should be saved. Zipping them into an archive is best, as you can them be sure they wonââ,¬â,,¢t be used subsequently by mistake.
ââ,¬Â¢   To be cautious you could zip all XML files under crn\webcontent - maybe all XML files under crn (although there are 600+). Do a Windows search for .XML, select the resultant files, and zip them into an archive.
3.3   Upgrade ReportNet
3.3.1   Stop Services
ââ,¬Â¢   Stop World Wide Web Publishing (IIS).
ââ,¬Â¢   Stop the ReportNet service.
ââ,¬Â¢   This prevents files being locked when the upgrade tries to replace them. If you do not do this, the upgrade will stop halfway through without giving you an error message; itââ,¬â,,¢s failed if you donââ,¬â,,¢t get a ââ,¬Ëœfinishedââ,¬â,,¢ dialogue.
3.3.2   Install ReportNet Upgrade
ââ,¬Â¢   Select the xwsetup.exe file and following the prompts.
3.3.3   Start Services
ââ,¬Â¢   Start World Wide Web Publishing service.
ââ,¬Â¢   Open Cognos Configuration, save settings, and start the service. Whilst not absolutely necessary, itââ,¬â,,¢s probably a good idea to regenerate cryptographic keys, etc.
3.3.4   Test ReportNet
ââ,¬Â¢   Open Cognos Connection, and run some reports.
ââ,¬Â¢   Select About on the home page and confirm the new version of ReportNet.
ââ,¬Â¢   If you hit problems, you might want to stop the ReportNet service and start Tomcat manually to see if it gives you any errors.
4   Other Topics
4.1   How to Check if Oracle is Already Installed
ââ,¬Â¢   Open a Command Prompt and type ââ,¬Å"SQLPlusââ,¬Â
ââ,¬Â¢   You should get one of the following responses.
ââ,¬Â¢   Doesnââ,¬â,,¢t look like we have Oracle installed yet ââ,¬Â¦ you need to install Oracle.

ââ,¬Â¢   Oracle is installed, so you just need to check itââ,¬â,,¢s Unicode.

4.2   Installing Oracle
ââ,¬Â¢   Double-click setup.exe. If this has no effect, double-click install\win32\setup.exe

ââ,¬Â¢   Click Next.
ââ,¬Â¢   At the File Locations screen, you should be able to accept the defaults. Click Next.
ââ,¬Â¢   Available Products. Oracle 9i Database should be selected by default. Click Next.
ââ,¬Â¢   Installation Types. Select Standard Edition (2.80GB). Click Next.
ââ,¬Â¢   Database Configuration. Leave on the default option, General Purpose. Click Next.
ââ,¬Â¢   Oracle Services for Microsoft Transaction Server. Leave on default and click Next.
ââ,¬Â¢   Database Identification. Enter a database name; one that matches your DNS suffix might not be a bad idea, for example ââ,¬Å"Cognos.comââ,¬Â. The SID is filled in for you. Click Next.
ââ,¬Â¢   Database File Location. Leave the default. Click Next.
ââ,¬Â¢   Database Character Set. DO NOT leave the default! Select ââ,¬Å"Use Unicode (AL32UTF8) as the Character Set.ââ,¬Â Click Next.

ââ,¬Â¢   Summary. Click Install.
ââ,¬Â¢   Go get a cup of coffee. Donââ,¬â,,¢t rush back. Youââ,¬â,,¢ll need to be around to give Oracle the location of disks 2& 3.
ââ,¬Â¢   After the install has completed, provide SYS and SYSTEM passwords (Iââ,¬â,,¢ll use ââ,¬Ëœadminââ,¬â,,¢ for both for this example).
ââ,¬Â¢   At the End of Installation screen, note the HTTP port numbers (although you should not need them) and click Exit.
ââ,¬Â¢   Oracle Enterprise Manager Console will now open, and a Command window will be open, running Oracle HTTP server (which we donââ,¬â,,¢t need).
ââ,¬Â¢   In Enterprise Manager, expand the tree until you get a log in window. Enter SYS and your password from earlier, Connect as SYSDBA and select OK. This should log you into the console.
ââ,¬Â¢   Exit Enterprise Manager and the HTTP command window.
ââ,¬Â¢   Open a Command Prompt and type ââ,¬Å"SQLPlusââ,¬Â. You should get the following screen.

//

[phani1979]

Thank for eveyone
I will try these and let u inform
thank u again
sudhakar