Cognos installation and configuration (Oracle)
A. Create the Content Store(For One Machine).

The content store is a database that Content Manager uses to store global configuration data, global settings (such as the language and currency formats shown in the user interface), connections to data sources, and product-specific content. Design models and log files are not stored in the content store. By default, Cognos 8 products share the content store database. You must create this database using one of the following: Microsoft SQL Server Oracle DB2 Sybase Adaptive Server Enterprise (ASE)

We will use ORACLE as a database and content store.
Steps for Oracle
1. Ensure that the parameter for the database instance compatibility level of the content store database is set to 9.0.1 or higher. Cognos 8 will not work if Oracle version is below 9.0.1. 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:


The result set returns NLS_CHARACTERSET as UTF-8 or UTF-16, or AL32UTF8 or


AL16UTF16 or not Unicode. Note²This step is basically done to create the reports in the multiple languages.

If the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 or UTF-8 for the database character set parameters.

Note²If the above points are not satisfied (The database is not Unicode) follow the below mentioned steps to uninstall oracle.

3. To uninstall the oracle database follow the following steps.
1. 2. Ensure you are logged in as a user with Administrator privileges. Stop all Oracle services (if any are running): a. b. c. 3. 4. 4. 5. 6. 7. 8. 9. Choose Start > Settings > Control Panel > Services. If any Oracle services (their names begin with Oracle) exist and have the status Started, select the service and choose Stop. Choose Close to exit the Services window.

Start the registry at the MS-DOS command prompt: C:\> REGEDT32 Go to HKEY_CLASSES_ROOT. Delete any key that starts with Oracle or ORCL. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE. Delete the ORACLE key. Delete the Oracle ODBC Driver key under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and remove all keys under here that begin with ORACLE.

10. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \EventLog\Application, and remove all keys under here that begin with ORACLE. 11. Go to HKEY_CURRENT_USER\SOFTWARE\ORACLE and delete keys that start with Oracle or ORCL (if any exist). 12. Go to HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBCINST.INI and delete Oracle keys (if any exist). 13. Close the registry. 14. Go to Start > Settings > Control Panel > System > Environment tab. 15. Choose the system variable path and modify the Path variable. 16. Remove any Oracle entries from the path. For example, if JRE was installed by Oracle, remove the %ORACLE_HOME%\BIN path and the JRE path. You may see a path similar to this one:


17. C:\ORACLE\ORA81\BIN;G:\PROGRAM FILES\ORACLE\JRE\1.1.7\BIN 17. Exit the Control Panel. 18. Go to SYSTEM_DRIVE:\WINNT\PROFILES\ALL USERS\START MENU\PROGRAMS. 19. Delete the following icons: o Oracle - HOME_NAME (The previous Oracle home name)


Oracle Installation Products

Delete SYSTEM_DRIVE:\Program Files\Oracle through Windows NT Explorer.

3. Determine which user account will be used to access the database. Its better to create a new user.

Steps to Create a New User.

Ensure that the user account that accesses the database has permission 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 database tables.

Steps to create a new database in oracle 10g

To create database by using database configuration go to start button and click on programs -> oracle -> configuration and migration tools ->database configuration assistant PRABIR SINGH


You will get a welcome screen as below.

Click the next button to follow the next screen; in this screen you have options, to create a database, configure database options, delete a database, and manage templates.



Click the next button to get the database templates page, select the type of database template to be used in creating the database. You can click show details to see the configuration for each type of database. Choose the template suited to the type of workload your database will support. If you are not sure, select the default general template. Click Next

Click next button to continue, here you have to enter the GLOBAL DATABASE NAME and SID.



Click the next button. By default it select the database with enterprise manager and grid control for database management .or you can choose grid control for database management as it suit to your configuration


PRABIR SINGH . enter the password. or Raw Devices to best suite to system. Automatic Storage Management.7 Click the next button. Select File System. Click the next button.

specify the location for the creation of the datafiles. or Use OracleManaged Files. Use Common Location for All database Files. Choose one of the following: Use database File Locations from Template.8 Click the next button. PRABIR SINGH .

y y y y Install Install Install Install the the the the modeling component of cognos 8.9 Installation Of Cognos 8(For one Machine). On the computer where the Oracle is installed. PRABIR SINGH . analysis component of cognos 8. sever component of cognos 8. Steps for Cognos Content Database 1. samples component of cognos8. go to the ORACLE_HOME/jdbc/lib directory.

Copy the ojdbc14.jar file to the c8_location/webapps/p2pd/WEB-INF/lib directory on computers where Content Manager is installed. PRABIR SINGH .10 2.

1.jar file. that must be located in your Java Runtime Environment (JRE).jar file.jar file from the c8_location/bin/jre/version/lib/ext directory to the Java_location/jre/lib/ext directory.jar. delete it before installing the ojdbc14.11 If the directory contains the classes12. Copy the bcprov-jdknn-nnn. This file includes the driver required by the content store. Update the Java Environment Cognos 8 cryptographic services use a specific . PRABIR SINGH .jar (Java Archive) file. named bcprov-jdknn-nnn.

PRABIR SINGH . 2.12 1.

Alias cognos8 Location c8_location/webcontent Permission Read PRABIR SINGH . for the directories that contain the HTML and Web files for Cognos 8. You must set up virtual directories. Before you use Web pages generated by Cognos 8. you must configure your Web server.13 And to Configuration Of Web Server. The virtual directories in the Alias column of the following table are required for all Web servers. also known as Web aliases.

14 cognos8/cgi-bin c8_location/cgi-bin Execute Go to Control Pannel> Administrative Tools> IIS PRABIR SINGH .



PRABIR SINGH .17 Click next and finish.

18 Again right click on cognos8 and select New Virtual Directory PRABIR SINGH .


and then click on Programs.20 Now your IIS is configured. You¶ll see a link for ³Turn Windows features on or off´ PRABIR SINGH . How to set up IIS in windows 7 Steps: First. go to Control Panel.

you can see that there are a lot of options beneath it. PRABIR SINGH . You will probably want to explore these options.21 If you expand the Internet Information Services tree node. because even if you click on IIS. some of the necessary options for doing development aren¶t checked.

you¶ll see the new default page« slick! Note²Once the IIS set up is complete please follow the above mentioned steps to configure the web server. you¶ll see this dialog for a while«.22 Once you¶ve gone ahead and checked the items you want. Cognos Configuration. Now when you navigate in your browser to localhost. and clicked OK. Create Cognos Content Store PRABIR SINGH .

23 Right click Content Store and click Delete. Click ³YES´ PRABIR SINGH .

24 Now provide user ID and Password that you have created during Oracle installation. PRABIR SINGH .



27 Note²Save the Configuration. PRABIR SINGH .

PRABIR SINGH .28 Click Close Now Click on ACTION> START Let the services start completely.

29 Note²After the Cognos Starts successfully go to Environment and copy the Gateway URI as shown below. PRABIR SINGH .

30 Home URL: http://localhost/cognos8/ Click on MY HOME PRABIR SINGH .

and DB2 that contain sales and Marketing information for a fictional company named the Great Outdoors. Oracle. You can use Cognos Sample packages and reports to help you learn how to use Cognos 8.31 Now point to be noted. PRABIR SINGH . We will deploy sample Reports provided by Cognos. Setting Up the samples Cognos 8 provides sample databases for SQL Server. The Folders are blanks and there are no Sample reports. including Framework Manager and Metric Designer. This action re-creates multilingual versions of the Great Outdoors databases. Restore Backup Files for the Samples Databases To use the samples. you must restore backup files for the samples databases.

and you must extract them before you can restore the databases or schemas.sql to c: drive EXECUTE @C:\gs_or_modify.sql and Event_Studio_ELM_Agent_Modify_GOSALES. For SQL Server and Oracle.32 The following sample databases and associated files are provided with Cognos 8.dmp). the database schemas are delivered in a DB2 move file. each database is delivered as a Microsoft SQL Server backup file and an Oracle export file (. The files are compressed. PRABIR SINGH .sql Note This two execute statements are used for granting of dba permissions.sql EXECUTE @C:\Event_Studio_ELM_Agent_Modify_GOSALES. For DB2. Extracts all files to one folder Copy gs_or_modify.


files> imp PRABIR SINGH .Follow this step only if u get the mentioned error.dmp. Note²Please provide a instance before selecting the import process (ExGOSALES.dmp files.34 Open command prompt and go to the location where you have extracted *.this is done basically to avoid the error (Import terminated abruptly).dmp@prabir). C:\Documents and Settings\ASHISSHA\Desktop\COGNOS 8\SAMPLES.

35 Enter user name GOSALESDW Password: GOSALESDW Enter file name: GOSALESDW.dmp PRABIR SINGH .







42 Repeat the same with all other *dmp files PRABIR SINGH .




y y y y y GOSALES (For Gosales Query).46 Note---Restoring of the database is basically done to create the tables in the oracle database where the Following five users has been created. GOSALESDW (For Gosales Dataware house Query). GOSALESHR (For Human Resource Query). PRABIR SINGH . GOSALESRT (For Retailers Query). GOSALESMR (For Market Research Query).

See step 1 above. Setup Logging Level: 1. Save the Cognos Configuration and restart the Service. Open the Cognos Configuration. 5. 7. From the Tools menu select Server Administration. PRABIR SINGH . 5. From the Type dropdown select Database and click OK. 6. 8. Create database/schema to be used to collect logs from Cognos8. Right-click on Audit (or the name that was given in step 4) and New resource>Database. These steps are specific to the type of database being used. Type a name and from the Type dropdown select they type of database that is used for auditing. Right-click on Logging->New resource->Destination. 4. Cognos___Sqlserver _installation_and_con Configuration of Audit Setup Audit Database: 1. Select the name that is created in step 6 and enter the connection parameters of the database in the Properties window. Type a name for example Audit. click on Category dropdown list and select Logging. Follow the steps of Create the Content Store in the Installation and Configuration Guide. From the Value dropdown list select Request for all the Logging categories. This will create tables required to collect Audit data. On the Configure tab click on Properties on the tool bar (top right). 4. 2. 3. 2. On the Settings tab. Log in to Cognos Connection as member of System Administrators.47 Installation of Cognos with SQL Server 2005. 3.

7. PRABIR SINGH .48 6. Check the box of Audit the native query for batch report service and Audit the native query for report service. Check the box of Delete the configuration settings of all child entries and click OK.

8. click Tools. 13. 5. click the new import button. The New Import wizard appears. In the Public Folders Content box. 12.zip for sample audit reports in installation_location/webcontent/samples/content directory and FrameworkManager model Audit. 10. Set Up the Sample Report Usage Audit Report The report usage audit report lists reports by frequency of use. see the configuration tool online help. In the upper-right corner. On the toolbar.xml file located at c8_location/webapps/p2pd/WEBINF. and add the following XML fragment: <servlet> <servlet-name>DSServlet</servlet-name> PRABIR SINGH . open the Audit.zip follow these steps: 1. For information about changing the location. The default location is c8_location/deployment. The location is set in the Cognos Configuration tool. In the Deployment Archive box. 15. To deploy the Cognos_Audit. 7. Type a unique name and an optional description and screen tip for the deployment archive. Click Next and then Finish. Steps 1. 4. On the toolbar. To edit the package. select Cognos_Audit and click Next. 11. 9. click the new import button. and then click Next. In a text editor. 14. 16. it must be setup.cpf in installation_location/webcontent/samples/Models/Audit directory. Make a backup copy of web. 3. Content Administration.cpf in Framework Manager. open the web. Copy the Cognos_Audit. 6. In the Set the owner to: option selects The user performing the import and click Next. select Audit and click Next. 2.Click Run and then OK.zip file from the c8_location/webcontent/samples/content directory to the directory where your deployment archives are saved.xml located at c8_location/webapps/p2pd/WEB-INF directory. Open Cognos Connection. The New Import wizard appears. Select the folder where you want to save it. 2.49 Import of Audit samples: There is a deployment package Cognos_Audit. Before it can be used.

If it is not already there. Do one of the following in the DSServlet.java file: y If you are allowing anonymous logon..java needs to be modified to reflect the corrent username. and namespace are correct and uncomment the following line: binding.. If JDK is not installed on the server.DSServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>DSServlet</servlet-name> <url-pattern>/cognos/DSServlet.sh for UNIX located in c8_location/webapps/Audit to c8_location/webapps/p2pd/WEBINF/classes/com/cognos/demo. String password = "password". String userName = "username". If you do not have the following directory on your system. Edit the build file to ensure the JAVA_HOME definition points to your JDK and ensure the CRN_HOME definition points to your Cognos 8 location. comment out the following line: binding. create it: c8_location/webapps/p2pd/web-inf/classes/com/cognos/demo.java file from the c8_location/webapps/Audit directory to c8_location/webapps/p2pd/webinf/classes/com/cognos/demo.demo.. then download and install it. namespace and the dispatcher URI.jsp</url-pattern> </servlet-mapping> Note that there two sections in the above xml snippet. 7.bat for Windows or build. 5. The <servlet-mapping> snippet should be added just below the <servlet-mapping> section in web. The Cognos8 will still function. 6.logon (.) The following snippet of code in DSServlet. copy the DSServlet. Copy the file build.. password.50 <servlet-class>com. The <servlet> section of the above snippet should be added just below the <servlet> section in web.xml. 3. PRABIR SINGH . Otherwise errors will be displayed in tomcat. password. make sure that the username. 4.logon (.xml.cognos.) y If you are not allowing anonymous logon.

NamespaceID should be used and not the name of namespace. select XML.bat or build.jsp is not physically created on the drive. and are often used for identifying errors within the Cognos 8 environment. Restart Cognos 8 and open Cognos Connection. run build. Since this is the user which will be used to run the servlet to get the report usage information. 11. The namespaceID can be obtained from Cognos Configuration. click More. 8. At a command prompt. the connection string is http://localhost:9300/p2pd/cognos/DSServlet.51 String namespace = "namespaceID". plain text log files are created under the <c8_install>\logs Directory. Note that DSServlet. The level of detail logged can be controlled. and then click the Data Sources tab. 10. String endpoint = "http://localhost:9300/p2pd/servlet/dispatch/". y Under Type. and then click the Connection tab. Introduction (Logging For Auditing) Most people are familiar with.jsp. If you used the defaults. By Default. for example a system that is running well PRABIR SINGH . 9.sh from c8_location/webapps/p2pd/WEB-INF/classes/com/cognos/demo. the data source connection is pointed to this URI. That is if the user has read and executes privileges on these reports. Set the connection string by doing the following: y Click Tools. Cognos 8 logging. However. y Next to your data source. Restart the Cognos8 service. Now you should be able to run any Audit reports. y Click View connections. Directory. y Click Set properties. or at least aware of. y In the Connection string field. These logs contain various categories of information. Logon to Cognos Connection. the username should be a member of System Administrator¶s group in Cognos Connection. enter the connection string.

but when tracing an issue. ‡ License conformance. To facilitate easier access to this kind of information. by extracting key information. such as unexpected error messages or performance problems. the data can also be used for Auditing purposes ± that is tracking the activity taking place on the system.52 may have a low level of detail. ‡ Performance monitoring. Cognos 8 allows logging to be directed to a relational database where it can be easily queried. then the logging level may be increased to include diagnostic information that is not usually of concern. PRABIR SINGH . ‡ Justifying additional infrastructure requirements. One can change the size of the log file as per requirement. Logging does not need to be exclusively for troubleshooting. Some of benefits of auditing usage include: ‡ Planning down time by identifying quiet periods. Note²By default cognos provides 10 MB of log file. ‡ Identifying unused content. Once the log file is full cognos itself creates a log file of 10 MB by default.

53 Note---As shown in the above diagram one can delete the existing audit and create its own auditing database. PRABIR SINGH .

then ensure that the appropriate JDBC drivers are available.similarly to Content Manager and Notification databases.54 Note ±As shown in the above diagram one need to provide the configuration details in the value field . examining the specified the database you should see the following tables created. DB2 and Sybase are supported) to that of the data stores. If you are using a different database for collecting the audit data (SQL Server. Oracle. The auditing database is populated via a JDBC connection by the Content Manager Service . After saving the settings and starting Cognos 8. Turning on logging to the Database Configuring the database connection In Cognos Configuration. under Environment | Logging right-click and select New resource>Destination of the type Database and set up the connection to your chosen database accordingly. If they are not. check PRABIR SINGH .

Setting the Logging Level The logging level is set in Cognos Connection under Server Administration. PRABIR SINGH .55 the cogserver.log file to see if any errors are indicated. The properties for each Dispatcher should be set to Basic for each component.

Attached below is a list of logging events by a level: 1. To allow this information to be obtained. Full.Trace. there may be a desire to discover content that is not being used ± the very fact that a report is never accessed means that it will never appear in the audit files. y y y y y Minimal(It records only minimal entries). when a user logs in and runs a report. the log in event is stored. Request(It records as per user request). a small SDK application is provided with Cognos 8 that queries Content Manager and provides a list of content. Request. PRABIR SINGH . Details About Logging Level The logging levels are set to specify the events and messages to record in the log file or in the log database. along with the report execution details. runtime usage of IBM Cognos 8. Basic(It records basic entries Ex-User logon). Trace. use requests Basic. Full(It records full entries Ex--Click). ensure that the logging level is set appropriately in all installations. Service requests and responses . even if Select the entire Content Store is chosen. Trace(It records native queries). Trace. Full (all except Minimal) 3.56 The logging levels are not stored in a Cognos 8 Deployment Archive. but what if we want to trace something that DOESN¶T happen? Specifically. All requests to all components with parameter values. Full Use of DS Servlet Information is logged as actions occur. native queries . This allows activities to traced. Request. A different logging level can be set for each dispatcher service. User account management. Full 4. In Cognos 8 there are 5 different logging levels: Minimal. for example. Note²There are basically five types of logging levels.logged on all 5 levels 2. System and service startup and shutdown.Request. runtime errors . Basic. If auditing reports are developed in a test environment and deployed to production.

COGIPF_THRESHOLD _VIOLATIONS: Stores information about threshold violations for system metrics. Active Directory Server 2. 13. COGIPF_NATIVEQUERY: Stores information about third-party queries to Cognos components. COGIPF_AGENTRUN: Stores information about agent activity including tasks and delivery. COGIPF_EDITQUERY: Stores information about query runs. COGIPF_USERLOGON: Stores user logon (including log off) information. 10. COGIPF_VIEWREPORT: Stores information about report view requests. COGIPF_AGENTBUILD: Stores information about agent mail delivery. 11. COGIPF_ACTION: Stores information about the operation performed on an object. COGIPF_RUNJOB: Stores information about job requests. ETrust SiteMinder 4. 9. 6. Security in Cognos 8 There are basically 6 types of security in cognos that we can configure according to the recording. COGIPF_RUNREPORT: Stores information about report executions. LDAP 5. 5.57 The information is returned in the XML format that can be consumed by Cognos 8 as a data source. Description Of Auditing Tables 1. NTLM 6. COGIPF_PARAMETER: Stores custom information logged by a component. 1. SAP NTLM Security²This is windows enabled security. 3. 8. 12. To enable this one need to select the security option in cognos configuration and change the parameters accordingly. IBM Cognos Series 7 3. 1. One need to create users with userid and password in windows and those users will have the cognos access through cognos. COGIPF_SYSPROPS: Stores version information about the schema for upgrade purposes. PRABIR SINGH . COGIPF_RUNJOBSTEP: Stores information about job request steps. 2. 7. 4.

For creating new system users and server users go to Cognos administrator and then add the users and delete the everyone group.58 2. Note--Please refer the image below PRABIR SINGH .

2. open IBM Cognos Configuration. In the Explorer window. Configure an IBM Cognos Series 7 Namespace You can configure IBM Cognos 8 to use one or more IBM Cognos Series 7 namespaces for authentication. under Security. and then click New resource.59 Note²As shown in the above diagram in the default security cognos the Allow anonymous users must be set to false after creating the security otherwise NTLM or other securities will not work. right-click Authentication. PRABIR SINGH . Namespace. Steps 1. On every computer where you installed Content Manager.

ensure that the Path. y y y 8. In the Type list. For example. In the Name box. 5. click Add. Specify the values for all other required properties to ensure that IBM Cognos 8 components can locate and use your existing authentication provider. you must disable the Series7NamespacesAreUnicode setting. specify a unique identifier for the namespace. and Secure flag enabled properties match the settings configured for IBM Cognos Series 7. In the Properties window.0. click Save. 10. If you are publishing from PowerPlay Enterprise Server to IBM Cognos 8. in the Advanced Properties value. 4. PRABIR SINGH . ensure that the Data encoding property is set to UTF-8. Test the connection to a new namespace. From the File menu. In the Explorer window. y In the Properties window. In addition. under Authentication. right-click the new authentication resource and click Test. The new authentication provider resource appears in the Explorer window. In the Properties window. click the appropriate namespace and then click OK. click the edit button. you must also use the computer name in IBM Cognos Configuration for IBM Cognos 8. 9. The host value can be a computer name or an IP address. you must use the same value format used in IBM Cognos Series 7 Configuration Manager for the location of the directory server.2 of the IBM Cognos Series 7 namespace. if the computer name is used in IBM Cognos Series 7 Configuration Manager. under Cookie settings. type False.Advanced properties window. the computers where Content Manager is installed must use the same locale as the data in the IBM Cognos Series 7 namespace. type Series7NamespacesAreUnicode. Domain. and then click OK. In the Value . In the Name box. type a name for your authentication namespace.60 3. 7. If your namespace environment includes version 15. for the Namespace ID property. If your IBM Cognos Series 7 namespace version is 16. under the Authentication component. 6. In the Value box.

2. on the right hand side of the window one has to provide SMTP mail server For Example Smtp server for gmail is smtp.com.gmail. As shown in the above diagram.61 Notification in Cognos 1. PRABIR SINGH . Notification in cognos is basically used for sending the mail to the users or the client.

4. PRABIR SINGH . For outlook 2007 the configuration is automatic. 5.62 3. For configuring the outlook 2003 one need to manually provide the port number for SMTP and POP3 server. Before creating the notification one has the configure the outlook as per the requirement. In the account and password field provide the gmail userid and password and in the default sender provide the email id Ex²prabirsingh52@gmail.com.

Memory Allocation in cognos There are basically there types of memory configuration in cognos y y y Small Configuration. As shown in the figure click more settings and in the connection tab provide the port numbers for SMTP and pop3.63 6. Large Configuration. Medium Configuration. 8. Before applying test account settings. PRABIR SINGH . 7. By default the SMTP server for Gmail is 587 and pop3 server is 995(SSL).

The default memory. Depending upon the requirement one can set the different memory allocation. click the Server Administration link. under Type. Note²Refer the link (http://www-01. click the Services radio button and PRABIR SINGH .com/support/docview. 2. set in cognos is 768 byte. In Cognos Connection.wss?uid=swg21386665) How to save scheduled reports to a location on the local or network file system Steps: 1.64 1. In the Server Administration page.ibm.

Click OK.pdf c:\reportnet\146_1062107695000_desc. 3. In the Explorer window. 5. 2. In the Set advanced settings . select the Override the settings acquired from the parent entry check box. click Save. click Content Manager. On the computer where you installed Content Manager. 4. 3. 5. under Data Access. Note: for the network file system. In the Save report outputs to a file system box. Steps to change from using CGI to ISAPI Steps: 1. A table appears.65 then choose Content Manager in the drop-down menu.xml. use a UNC Path. click in a cell and type CM. in which you can add parameters. Restart the Cognos 8 service. click Edit. The full file names of the output file and descriptor are passed to the script. PRABIR SINGH . eg: \\hostname\share_folders. click True or False. (by default this is "false") 4. c:\reportnet\146_1062107695000. 9. 6.OUTPUTLOCATION 8. Under the Actions column. type the file system location where you want to store report outputs. instead of a mapped drivename. the following steps are also required: 1. start Cognos Configuration.ContentManagerService page. From the File menu. Under Parameter. For example. Click the Settings tab. The Content Manager service appears below the drop-down menu. Open Cognos Configuration on each install that contains the Application Tier. click the set properties button. 7. In the corresponding Value cell. For Cognos 8 MR2 or above. Under the Value column.

. Open your browser and enter the following in your address bar: Customization of Cognos UI Please refer the document below cus mizi g_ he_c g s_8_ui.dll? etc. In Cognos Configuration. open the default...htm and the index. save your settings and restart your services. you will need to remove the ".pdf Configuration. 6.cgi? etc. Click the Environment node. To: url=cgi-bin/cognosisapi.66 2.htm files with an HTML or text editor and in both files. change the following: url=cgi-bin/cognos./" from the beginning of the URL (this is only relevant while that file resides in the subfolder) 5. In the /webcontent directory of each gateway install. Note: if you copied these two files from the ISAPI folder..cgi like in the following example: http://servername:80/c8/cgi-bin/cognosisapi. 3..dll instead of cognos.dll 4. Load balancing and set up of Multiple dispatchers Please refer the documents below ib _cognos8_failove r_and_load_balancing ¡   ¢ ¢ ¡ ¡  £ PRABIR SINGH . Change the Gateway URI setting to referencece cognosisapi.

This allows reporting on the Cognos user base and provides additional information to go with the role/capability audit. some areas such as the auditing of users and capability assignments are not included. created and modified date). etc. Audits can be initiated in three ways. reports.) that it finds. 8. saving information such as time taken to connect.1 and makes use of the IBM Cognos 8 BI SDK to communicate with the various IBM Cognos PRABIR SINGH . portal pages. However. Status Audit An audit of the current state of a server and related dispatchers. from Event Studio) The results of each audit are logged to a database and an IBM Cognos Framework Manager model is provided to help report off the data. as well as some details more specific to the item types (such as the specification XML of reports and queries. 8. any saved parameter values applied to saved reports and the details of report output versions). this audit type should be used in conjunction with the Account Audit (see above).1 MR1.67 Cognos Audit Extension: Introduction Purpose The standard auditing features that come out of the box with IBM Cognos BI cover many aspects of operation. In order to also record the items in the Content Store that are located inside individual users¶ My Folders areas. search path. The aim of the c8AuditExtension application is to provide additional auditing for these areas.4. This type of audit will also by default record the content of users¶ My Folders. 8. For each dispatcher registered in the target system. y y y via the management web interface via a simple URL/web form call via a web services call (i. the configuration and activity will be logged. Content Audit An audit of all the objects that exist in the main Content Store.e. number of active processes and request duration. This audit will process through the content store tree and log all the objects (folders.4 and 8. It will log the basic information (such as name. Applicability This application is designed for IBM Cognos 8 BI versions 8. The application currently covers the following: Account Audit An audit of all the user accounts that are found in all configured namespaces and certain properties of those accounts (basic details.).2. Usage The application is managed via a web front end that allows the configuration of server and namespace information and can be used to turn on or off individual audit types for a given server.3. object permissions. queries. created and modified dates etc.

Generally only one server entry would be used for each group of IBM Cognos 8 servers that makes use of the same Content Store. It is also intended to interact with any third party application that can issue commands via web services. although differences in product features mean that not all audit features are supported. The supported databases for the application are. The reason a local password is used rather than tying to IBM Cognos 8 security is that the application can interact with multiple IBM Cognos 8 installations. y y y y y DB2 8. An appropriate JRE is provided with installations of IBM Cognos 8 BI versions 8. The application and model are provided on a strictly "as is" basis and IBM Cognos Support is not able to offer any support for it. PRABIR SINGH . it generally expects a provider/namespace to require a simple username and password to log on . any feedback. After installation.3 and above.5 or above. Application Details Process overview and architecture The application is a web application and web service written in Java/AXIS. This application will only work within a JRE 1. The application can be secured from the management interface by defining a local password which will subsequently be required to access the interface or run audits. running in either the IBM Cognos 8 Tomcat instance or its own application server.where a custom provider uses some other form of credential. However.1 and 9. This does not affect trusted signon type custom providers. It is intended to be installed on an IBM Cognos 8 machine. Limited support is also provided for IBM Cognos ReportNet 1. the application will create its own database tables if they do not already exist and present an interface to allow the administrator to enter the details of IBM Cognos 8 servers and namespaces. depending on the implementation of the provider ± for example. Exclusions and Exceptions This application may not be compatible with all Custom Authentication Providers. Usage. bug reports or suggestions are welcomed.1 servers. separate server entries are often used for different functional groups such as Production and Development. providing that the underlying provider can be authenticated to in the normal way.x MS SQL Server 2000 and 2005 Oracle 10g MySQL 5 Apache Derby 10 The Status audit depends on some information provided by the IBM Cognos 8 server that is subject to change and may be affected by future upgrades of IBM Cognos 8. support and feedback This application should only be supplied to customers as part of a suitable Services package to ensure successful implementation and interpretation of the results. However.68 8 BI components. so there is no one IBM Cognos 8 security namespace to tie it to. the audit extension may be unable to authenticate to that namespace to audit it.

WAS or other application server for details on how to deploy a web application. war PRABIR SINGH . This is because the application needs to be able to authenticate to the namespace in order to audit its contents. y y y y y y Unpack the installation to an IBM Cognos 8 server Customise any files that you wish to modify Import any third party JDBC drivers that you intend to use Build the WAR file Deploy the WAR file to an application server or servlet container Configure the application using the web user interface. Namespace login details will be encrypted and stored in the application database. If the application cannot authenticate to a namespace that is used for object security or users. The process for installation is as follows. You must first build the WAR file within your IBM Cognos 8 installation using the supplied scripts and then deploy this file to your server. authentication to all namespaces must be made otherwise the application will terminate the audit run. Consult the documentation of the specific application server/servlet container for instructions on deploying a WAR file into alternative destinations. for every namespace that is used for object security or capability assignment in the Content Store so that they can be audited. Unpack the installation and copy to a IBM Cognos 8 server Unpack the zip file containing the Audit Extension application to a suitable temporary location. Installation The application is deployed as a WAR file that can be used with any suitable servlet container or application server such as IBM WebSphere. This contains two main folders. it is desirable for a production environment to run this application within its own Tomcat or WAS instance. It is essential that an entry exists.69 When the administrator enters the details of a new IBM Cognos 8 Dispatcher. Please refer to the documentation of Tomcat. The procedures outlined in this document cover deploying the application into the Tomcat servlet container that is normally installed with an IBM Cognos 8 server. reporting This folder contains materials to allow you to report on the Audit Extension output in Cognos 8 and contains a Framework Manager model and a Cognos 8 deployment archive. These details will be added to the properties page for that Dispatcher and made ready for editing. You do not need to do anything with this at this stage. the application will connect to that Dispatcher and gather details of the configured security namespaces. then its objects cannot be audited. Generally speaking. If multiple namespaces are specified in a single server entry. complete with valid login details.

70 This folder contains the application itself. you can customise the application before building the WAR file.1). PRABIR SINGH . For example. you will not need to install any additional JDBC drivers. Install any required JDBC drivers If you are using an IBM DB2 or Apache Derby database to store the Audit Extension data. The default settings should be fine for most users.properties file (see section 5. the files are located in the <c8install>/war/AuditExt/classes directory. but if you need to make any changes to the configuration settings in the c8AuditExtension. You need to use this to build the WAR file. Take the war/AuditExt directory and place it in your IBM Cognos 8 installation directory under <c8install>/war. as the DB2 Universal Driver is included in the distribution.6) or the logging settings in the log4j. in a subdirectory named AuditExt. At this point. MySQL or Oracle then you will need to obtain the correct driver file and install it.properties file (see section 3. If you plan to use Microsoft SQL Server.

http://www.com/mysqljdbc Once you have obtained the correct jar file(s) for your database.microsoft.mysql. PRABIR SINGH .com/downloads/connector/j/5. http://dev.html or http://tinyurl.bat (Windows) or <c8install>/war/AuditExt/build.jar if using a non-English locale. the application will warn you when you attempt to first configure the database.6-bin. Build and deploy the WAR file Build the war file by running the <c8install>/war/AuditExt/build.jar and can be obtained from.jar and can be obtained from either your Oracle installation or from.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_10201. the illustration below shows the Microsoft SQL Server driver being added.1.jar and can be obtained from.1.com/ojdbc You may also need to obtain orai18n.com/sqljdbc The Oracle driver file is ojdbc14.71 y The SQL Server driver file is sqljdbc. http://www.aspx?FamilyId=6D483869-816A-44CB-9787A866235EFC7C&displaylang=en or http://tinyurl.com/downloads/details.sh (UNIX/Linux) script. y y The MySQL driver file is mysql-connector-java-5. place them in the <c8install>/war/AuditExt/lib directory. For example.oracle.html or http://tinyurl. If you do not install the correct driver at this stage.

After a short time. Place this file in the <c8install>/webapps directory.war.72 This will create the WAR file <c8install>/war/AuditExt/AuditExt. the IBM Cognos 8 Tomcat server will automatically unpack the WAR file. Configure via UI Access the web administration URL at http://servername:9300/AuditExt/. The application is now ready to be configured. PRABIR SINGH . A screen prompting for database connection details will be presented.

you should configure it in the same as described in the IBM Cognos Installation and Configuration Guide as if it were being used for a Content Store. For more information see http://www.73 The c8AuditExtension application can use either an existing IBM Cognos 8 audit database or a separate database created specifically for this application. IMPORTANT: For Oracle. wait for the screen to refresh before continuing ± do not click OK more than once. click on the Reset configuration link on the Manage Servers page. If you are using a database that has already been set up for IBM Cognos 8 audit logging. you may already have done this. You may also use a standard IBM Cognos 8 audit logging database.orafaq. IMPORTANT: The database specified in the Database name field must already exist prior to connecting. PRABIR SINGH . depending on the speed of the server.com/node/758. Reconfiguration To reconfigure the main database connection. Database preparation To prepare the database for use by this application. The process of creating and populating database tables may take some time. which should also have been configured in this way. The default is 50. IMPORTANT: For DB2. you may need to increase the maximum number of open cursors supported by the database. Alternatively. Once OK has been clicked. you must create an additional regular user tablespace with a page size of 16 KB. It is strongly recommended not to use a database that is already in use for a IBM Cognos 8 Content Store. which will probably be insufficient for this application ± a more suitable value would be 500. This allows for the re-entry of the database connection details. The application will create the necessary tables under this database. the main database connection can be reset manually by following these steps.

user jdbc.password= y y Restart IBM Cognos 8.ca.include. Possible values are true and false. the screen prompting for the JDBC connection details will be presented. jdbc. This configuration file contains the following parameters. Configuration file reference The main configuration file is called c8AuditExtension. The default value is true. # JDBC connection details: jdbc.items A Content Audit option that limits the maximum number of items that will be processed by the audit. less database space will be used and the audit may run faster.max.ca.url= jdbc. The default value is true.max. option. option.specifications A Content Audit option that determines if the audit should record the specification XML of any reports/queries/analyses that it finds.user= jdbc.include. Possible values are true and false.ca. Note that the password is stored in an encrypted format. option.duration A Content Audit option that limits the maximum length of time. option. If this parameter is set to false. When IBM Cognos 8 is restarted and the administration URL is accessed again.properties Re-set the JDBC connection details as follows.properties and can be found at <c8install>/webapps/AuditExt/WEB-INF/classes. These are generated by the application configuration interface and should not be edited manually.output A Content Audit option that determines if the audit should record details of report versions and outputs for report objects that it finds. If this parameter is set to false. in seconds. less database space will be used. The default value is 0 (zero) which means no limit will be applied. the audit is terminated and recorded as a failure. that the audit should be run PRABIR SINGH .url jdbc. If the number is exceeded. except to reset to empty values for reconfiguration.ca.password Connection details for the database used by the audit extension application.74 y y y Stop the IBM Cognos 8 service Edit the file <c8install>/webapps/AuditExt/WEB-INF/classes/c8AuditExtension.

Possible values are true and false.aa.max. the calculation will instead be done at runtime.75 for.rawstatus A Status Audit option that specifies if the audit should record the raw status XML of services that the audit finds. the audit is terminated and recorded as a failure. If it is set to a value of 0 (zero).policy. The default value is 10000. no time limit will be applied. If this time is exceeded. If it is set to a value of 0 (zero). If the number is exceeded. less database space will be used. option. If this parameter is set to false.duration An Account Audit option that limits the maximum length of time. less database space will be used. The default value is 900 (15 minutes).sa. that the audit should be run for.filename The location of the keystore file that is used for security. If this time is exceeded.sa. If the file does not exist at this location. option. Possible values are true and false. The default value is true.keystore. Note that this must be a writeable location otherwise the application will fail. option. a new one will be generated. If set. This includes such information as the maximum number of processes.items An Account Audit option that limits the maximum number of items that will be processed by the audit.include.content An Account Audit option that determines if the audit should process the content of users My Folders. If it is set to a value of zero.include. The default value will place the keystore in the configuration directory of the IBM Cognos 8 installation using PRABIR SINGH . Possible values are true and false.aa. Possible values are true and false. option. no time limit will be applied. Possible values are true and false. security. The default value is true. The default value is true meaning there will be no calculation done at runtime. The default value is true.ping A Status Audit option that specifies if the audit should perform additional basic network tests on the dispatchers registered with a server.aa. no limit will be applied.max.configuration A Status Audit option that determines if the audit should record the configuration information of dispatchers. option.include. option. If this parameter is set to false. the audit is terminated and recorded as a failure. The default value is 900 (15 minutes).include. this will cause a mini-Content Audit to be run for each user s content where it exists.calculation A Content Audit option that determines whether security policy calculation should be done in FM. option.sa. in seconds.ca. The default value is true. If set to false. the audit is terminated and recorded as a failure.

initdays A database option that specifies the number of days (starting from the current date) to pre-populate in the date dimension table when it creates it on first startup. The default value is true. Possible values are true and false. Possible values are true and false. option. Note that any missing dates will be added when the audit for that time runs.audittypes A database option that determines if the application should reset the audit type descriptions in the database to their default values if they have changed. The default value is 730 (2 years).db.db.db.db.statusresulttypes A database option that determines if the application should reset the status result type descriptions in the database to their default values if they have changed. The default value is false. option.pingtypev A database option that determines if the application should reset the ping test type descriptions in the database to their default values if they have changed.pingresult A database option that determines if the application should reset the ping test result descriptions in the database to their default values if they have changed. If this application was deployed anywhere other than the Tomcat servlet container that was installed with IBM Cognos 8.db. option. option. The default value is false. Possible values are true and false. option.setdefault.maxbatch PRABIR SINGH . The default value is false. option.date.setdefault. option.dimension.populate A database option that determines if the application should fully populate the time dimension table when the table is created on first startup. this value will need to be edited.db. Note that any missing times will be added when the audit for that time runs. The default value is false.setdefault. Possible values are true and false.serverversiondesc A database option that determines if the application should reset the server version descriptions in the database to their default values if they have changed. although it is considered better for reporting purposes. although it is considered better for reporting purposes. Possible values are true and false.setdefault. The default value is false.db. so pre-population is not required. option.setdefault.db.76 a relative file path.dimension. Possible values are true and false. so full pre-population is not required.time.

properties. it will no longer be possible to access saved passwords and there may be errors running and administering audits. As the audit extension can communicate with multiple IBM Cognos 8 servers and not just the one it is installed in. option. or a full application server such as the IBM WebSphere Application Server. This applies to all audit types and is designed to reduce overall memory consumption for very large audits. or if your IBM Cognos 8 installation uses a JRE older than 1. Optionally.77 An option that specifies the maximum number of items that should be processed before a database write. you could have a dedicated IBM Cognos 8 instance for running this audit and reporting off it./logs/c8AuditExtension. the keystore file is located at <c8install>/configuration/c8AuditExtension. the keystore file can also be deleted. Remember to use forward slashes for the pathname. The default value is false. the procedure is as simple as deploying any web application ± in the case of Tomcat. you should consider installing into another servlet container. IMPORTANT: If the keystore file is deleted or the application is installed on another machine without copying the keystore file to the new machine.cgi). you may need to change this to either a different relative path or a fully qualified path such as C:/logs/c8AuditExtension. if installing into a heavily used production environment.org/download-55. By default./configuration/c8AuditExtension. delete the database tables created by the application can be deleted. you can just drop the WAR file in the webapps directory as you would with IBM Cognos 8. In WEB-INF/classes/log4j. There are two file path considerations to make though.apache. 1. the log file name is specified using a relative path. Verify that this path works in your environment and if necessary update it.db. This could be a standalone Tomcat instance (http://tomcat.log. While this works with IBM Cognos 8.keystore but this location will be different if the application has been deployed outside of the Tomcat servlet container installed with IBM Cognos 8. .war file the <c8install>/webapps/AuditExt directory Optionally. stop IBM Cognos 8 and delete the following. The default value is 2000.properties contains a relative path in the security. Generally.log.filename property (. 2.5.keystore. y y the <c8install>/webapps/AuditExt. Considerations for deploying into another application server As noted above.. Verify your licensing to determine is this is a viable alternative. Another alternative configuration is to install into a dedicated IBM Cognos 8 installation. PRABIR SINGH . Removal and reinstallation To uninstall the application. The database tables are all prefixed with "AE_".keystore)..random-audit-id An option that controls whether the database ID generated for each audit should be a pseudo-random number (a value of true) or sequential (a value of false). The file WEB-INF/classes/lc8AuditExtension.

This URL could either be directly to a IBM Cognos 8 Dispatcher or to a dedicated gateway for IBM Cognos 8 SDK applications. Version: The IBM Cognos 8 version running on the server. PRABIR SINGH . The initial Manage Servers page will contain no servers. As the value of this identifier may be used to refer to the server for commands. URL: The URL the application will use to connect to IBM Cognos 8. short string with only standard characters. Add a server From the Manage Servers page. it is suggested that this value be a simple. add a new server entry by filling in the fields beside the label Add new server and clicking the Add button. The fields to fill in are. which is accessed via http://servername:9300/AuditExt/. ID: A text identifier for the server.78 Back to top Using The Application Manage servers After the application has been configured. the main interface is the Manage Servers page. This could be a hostname or simple identifier like "PrimaryServer".

79 Once a new server has been added successfully. PRABIR SINGH . the properties page for that apply to the IBM Cognos 8 server just added will automatically be shown.

the configured namespaces will not automatically appear. PRABIR SINGH .80 Any namespaces that have been configured for the new server will have been automatically added to the properties page without passwords. When a new server has been added. the Manage Servers page will contain a list of all the servers that can be audited by this application. NOTE: If using this application in a test or development environment and Anonymous access has been enabled on the IBM Cognos 8 instance. Configured namespaces can be added manually by filling in the fields under the label Add new namespace login.

A page will appear asking the user to confirm or cancel the deletion.81 Delete a server A server can be deleted from the Manage Servers page. If confirmed. click the Set Properties icon beside the targeted server. To access and edit the properties page for any server shown in the list on the Manage Servers page. If a new server has just been added. the properties page will be displayed automatically. click the Delete Server icon next to the server entry. namespaces can be managed from the properties page of the specified server. PRABIR SINGH . To delete a server. Manage server namespaces For each server. the Manage Servers screen will reappear with the deleted server removed from the list. The properties page for a server will look similar to the following page.

PRABIR SINGH . The value for the Namespace ID field is the same value that is specified in the Namespace ID field when the namespace was originally defined in IBM Cognos Configuration. y y y y Update the dispatcher URL Add or modify a description for the server Set which audit types should be run for that server Apply filters to the audits Click on the Update button to save the modified properties. they should be deleted these by clicking the Delete Login icon. For any unwanted namespaces.82 Before a namespace can be included in an audit. To add a new namespace. the login credentials the application is to use must be supplied. additional properties can be set for the server. The properties are. Enter usernames and passwords one namespace at a time. When finished with the server properties page. enter the details in the section labelled Add new namespace login at the bottom of the screen. Note that saved namespaces will display the saved user but will never display the saved password. click the Return button to go back to the Manage Servers page. An example of such a namespace is one that is used only for single signon. Configure server properties and audit types Within the server properties page. only the credentials that correspond to the Save button that was clicked will be saved. If an attempt is made to save multiple namespace credentials at the same time. clicking the Save icon next to that namespace entry after each one.

If no filter is to be applied (the default). the filter term would be. the filter would be. leave the filter values empty. For example. so the first item in the filter will refer to the namespace. the following filter would restrict the content to everything within the "GO Sales and Retailers" package. it is important to remember that the µ/¶ character is a special case and will be treated as a folder separator.info/. For example. Account Audit The filter is assumed to start at the namespace level.83 Set audit filters For Account and Content Audits. the filter term would be. for all configured namespaces. GO* Note that the filter is case sensitive. Alternatively. Content Audit The filter is assumed to start from the top content (package) level. ADNamespace/Accounts/Users The following filter would be slightly less restrictive and pick up all items under Accounts for all namespaces. to restrict the audit to the same set of folders but also restrict to just the namespace with the ID "ADNamespace". use the following. to restrict the audit to members of the Users folder that is within Accounts. GO Sales and Retailers To restrict it further to the "Report Studio Report Samples" folder within that package. the application uses its own security mechanism. Usage is slightly different depending on whether it is a content or account audit. GO Sales and Retailers/Report Studio Report Samples To limit the content audit to all packages that start with "GO".regular-expressions. The filters take the form of a series of regular expressions. Set security As stated earlier. More information about regular expressions can be found at http://www. */Accounts/Users The asterisk in the first item means that all namespaces will be matched. These filters are specified in the filter boxes of the server properties screen. */Accounts Any regular expression can be used. Click the Set admin password link on the main Manage Servers page to specify the password required to run the application. separated by forward slashes to denote folders. However. it is possible to specify a filter to limit the scope of the auditing to a subsection of the namespace/content store. PRABIR SINGH .

84 After a password has been set. users will be prompted to enter it in order to access the application. PRABIR SINGH .

Each server entry has a Run button that will cause the configured audits to be run for that server. click on the Execute button next to the All servers field. To run the audit for all configured servers. the server ID. http://servername:9300/AuditExt/AuditServlet?action=run_audit&server_id=serverId Run audits via web service call The WSDL for the web services interface can be found at the URL. go to the Manage Servers page. http://servername:9300/AuditExt/AuditServlet?action=run_audit&server_id=serverId To run an audit for all servers specified in the Manage Servers page using a URL use the following syntax. runAuditAll Takes no parameters and runs the configured audits for all servers. http://servername:9300/AuditExt/services/AuditService?wsdl There are two methods available in the web services interface: y y runAudit Takes one parameter. and runs the configured audits for that server.85 Run audits via web interface To run an audit via the web interface. This web service can be called from any application but an example will be presented here that uses Event Studio to create a IBM Cognos 8 agent that will call the web service PRABIR SINGH . Run audits via URL To run an audit for a server ID using a URL use the following syntax.

86 interface to run an audit. This will force the event condition to be true and the agent will be guaranteed to run on demand or as scheduled. the first screen that appears is Specify an event condition« Use a measure in the model that is known to be greater than zero or non-null. When Event Studio is invoked to create a new agent. select Advanced > Call a Web service« PRABIR SINGH . From the "Add a Task" list. The example will use the sample package that accompanies this application.

Save the agent. In this instance. PRABIR SINGH .87 Enter the URL to the WSDL and click on the Retrieve button to get the available methods. the runAudit method has been selected. Enter a previously configured server ID as the serverIdentifier argument.

Note that the internal deployment name is Cognos_Audit_Extension. usually <c8_install>/deployment. PRABIR SINGH . click the Configuration tab. the default settings will suffice. where the ver portion of the name is the version(s) of IBM Cognos 8 to use and the yyyymmdd portion of the name represents the date the reporting package was released. follow the instructions and options presented by the New Import wizard. In most instances. From there. Select the deployment archive named AuditExt_deployment_ver yyyymmdd.zip to the IBM Cognos 8 deployment directory. select Content Administration. Sample deployment An IBM Cognos 8 deployment archive consisting of a package containing some sample reports and agents created against the sample Framework Manager model is provided with this application. From IBM Cognos Administration. y y Copy the file AuditExt_deployment_ver_yyyymmdd. To import the sample deployment so that it can be used by the IBM Cognos 8 studios. and click the New Import icon.zip.88 The agent can now be scheduled using IBM Cognos Connection and the IBM Cognos 8 scheduling service. The sample deployment and model are contained within the file AuditExt_reporting_ver_yyyymmdd.

Click on the New Data Source icon and give the new data source the name c8_audit. Sample Framework Manager model A sample Framework Manager model is also supplied with the application as a basis for further development. it is necessary to create a new data source in the IBM Cognos 8 Content Store that will interact with the audit database specified when this application was initially installed y From IBM Cognos Administration. open the project file AuditExt. Before this model can be used.cpf. Unzip the sample model to a suitable directory and from Framework Manager.89 Before the package can be used. follow the instructions and options presented by the New Data Source wizard to create the data source. This data source is the same as the data source described in the section titled Sample deployment.zip where the yyyymmdd portion of the name represents the date the model was released. The sample model is provided in the file AuditExt_model_yyyymmdd. click the Configuration tab and select Data Source Connection. a data source named c8_audit must exist in the IBM Cognos 8 Content Store. PRABIR SINGH . The package can now be used by the IBM Cognos 8 studios. From there.

AE_CONFIG_AUDIT_TYPES Which audit types are configured for each server. AE_AUDIT_TYPES List of possible audit types. Database tables The application creates/uses the following tables: General configuration AE_CONFIG_MAIN Main application configuration containing the configured servers.log.org/log4j/docs/ for more information on how to configure log4j. AE_ACCOUNTAUDIT_PORTALPAGES Records of any user portal pages. AE_CONTENTAUDIT_POLICIES PRABIR SINGH . To change the logging settings.properties. See the log4j documentation at http://logging. Content audit AE_CONTENTAUDIT_MAIN Main detail table. AE_SERVER_VERSIONS List of supported Cognos server versions. Account audit AE_ACCOUNTAUDIT_MAIN Main detail table. The log file defaults to <c8install>/logs/c8AuditExtension. AE_CONTENTAUDIT_PARAMS Record of saved parameters for reports and views. AE_CONFIG_NS The saved namespaces configured for each server. AE_SECURITY Table containing encrypted admin password.apache. edit the file <c8-install>/webapps/c8AuditExtension/WEB-INF/classes/log4j.90 Back to top Other Logging This application uses log4j to provide logging services.

AE_STATUSAUDIT_PING_RESULT_TYPES Possible result codes and descriptions of simple dispatcher network tests. General audit data AE_STATUS History and status of audit runs. AE_STATUSAUDIT_DISP Main audit details for each dispatcher registered in the content store. AE_STATUSAUDIT_DISP_CONFIG Additional configuration details for each dispatcher registered in the content store. AE_STATUSAUDIT_PING_TEST_TYPES Possible types of of simple network tests that can be performed on dispatchers. AE_STATUSAUDIT_DISP_PING Results of simple network tests on dispatchers. Status audit AE_STATUSAUDIT_MAIN Main detail table. AE_CONTENTAUDIT_REPORT_OUTPUTS Record of report outputs saved in the Content Store. AE_CONTENTAUDIT_SPEC Record of report.91 Record of all security policies applied to all objects. AE_STATUSAUDIT_RESULT_TYPES Lookup table for result type codes. AE_STATUSAUDIT_DISP_SERVICES Details on the running services for each dispatcher registered in the content store. AE_CONTENTAUDIT_REPORT_VERSIONS Record of report output versions saved in the Content Store. AE_STATUSAUDIT_DISP Main audit details for each dispatcher registered in the content store. PRABIR SINGH . query and analysis specifications.

AE_DIM_DATE Date dimension table. Permissions You can install using either root or non-root authority.) AE_MAP_DATETIME Table for mapping timestamps (such as the audit start and end times) to date and time dimension table keys. The granularity is minutes.ca. PRABIR SINGH . AE_ITEM_LOOKUP_FAILURES Record of all items that could not be looked up (for example because they were removed from the content store but were found in audits as owners of other items etc. the location of other Content Manager components. The granularity is days.92 AE_AUDIT_TYPE_LOG Log of the audit types run for each audit. How to configure two content manager on single machine Installing and Configuring Content Manager Components You can install more than one Content Manager to ensure failover.calculation option is set to false. AE_SECURITY_MEMBERS Optional data on security policies generated during an Account or Content Audit when the option. and you can install Content Manager in a separate location than other components to enhance performance.policy. AE_DIM_TIME Time dimension table. AE_ITEM_LOOKUP Lookup table mapping item store IDs to names. The Content Manager computers must know the location of the content store. and the database that is used for notification.

The standby Content Manager components are for failover protection. However. such as logs. Copy the bcprov-jdknn-nnn. that must be located in your Java Runtime Environment (JRE). Ensure that the JAVA_HOME environment variable is set to the JRE location. We recommend umask 022 on the installation directory. is available to issue certificates to other IBM Cognos computers. To ensure security. This affects only the installation directories. IBM Cognos 8 requires a 32 bit Java environment. or where Content Manager is located in a separate location. named bcprovjdknn-nnn. This file provides additional encryption and decryption routines that are not supplied as part of a default JVM installation. run-time generated files. This ensures that the certificate authority service. the encryption file must be loaded by the JVM using the java extensions directory. running and accessible before you configure other components in your environment. a standby Content Manager becomes active and requests are directed to it. which is installed with Content Manager.jar file from the c8_location/bin/jre/version/lib/ext directory to the Java_location/jre/lib/ext directory. at least one of the one Content Manager must be configured. PRABIR SINGH . Steps 1. For example. respect the mask. to set JAVA_HOME to the JRE files provided with the installation. The other installations each act as a standby Content Manager. It does not affect the file permissions within the directories. IBM Cognos 8 respects the file mode creation mask (umask) of the account running the installation program.jar. although only one is active at any time.jar (Java Archive) file. the path is c8_location/bin/jre/version. Rules for Configuring In an installation where you have more than one Content Manager components. Update the Java Environment IBM Cognos 8 cryptographic services use a specific . If the active Content Manager is not available because of a software or hardware failure.93 Also. 2. Active and Standby Content Manager Components You can install any number of installations of Content Manager.

When IBM Cognos 8 is started. modify the soft limit (if needed) # ulimit -Sn 1024 d. such as the common symmetric key (used to encrypt and decrypt data). These other Content Manager installations enter standby mode. the first Content Manager installed with IBM Cognos 8 is the active one. If a dispatcher can no longer reach Content Manager. A IBM Cognos 8 server administrator can change the default Content Manager and the active Content Manager at any time. The other installations of Content Manager remain in standby mode for continuing failover support. unsaved session data is lost. the dispatcher signals a standby Content Manager. check the hard limit # ulimit -Hn 65536 b. Run the command: isainfo -v PRABIR SINGH .94 When the active Content Manager fails. The standby Content Managers retrieve cryptographic settings. users may be prompted to log on. verify soft limit changes # ulimit -Sn 1024 Install JRE Note: The isainfo command can be used to determine if a Solaris system has been configured to run in 32 or 64 bit mode. This failover mechanism works because dispatchers and the active Content Manager routinely communicate with each other. check memory size # /usr/sbin/prtconf | grep "Memory size" Memory size: 2048 Megabytes For AIX : use "vmstat" File descriptor limits (for Solaris): Recommended on Solaris = 1024 a. check the soft limit # ulimit -Sn 256 c. the default Content Manager locks the content store from access by all other installations of Content Manager. When another Content Manager becomes active. from the active Content Manager. Steps to Configure Cognos on UNIX Steps:* Done on Sun Solaris system using C shell Check system requirements: Memory Size: Minimum = 1 GB RAM a. By default. which becomes the active Content Manager.

After files have been copied. you'll see: 64-bit sparcv9 applications 32-bit sparc applications Note: when copying files to UNIX boxes.gz # tar xvf crcd-solaris-1. Error! Hyperlink reference not valid.95 If the system is running in 32 bit mode. and 'ozona' is only 32-bit.0.tar. try the file command.510.0. you should type [cph@anna ~]$ getconf -a | grep KERN KERNEL_BITMODE: 64 If that fails or does not return a result. [cph@anna ~]$ file /usr/lib/boot/unix* /usr/lib/boot/unix: 64-bit XCOFF executable or object module not stripped /usr/lib/boot/unix_64: 64-bit XCOFF executable or object module not stripped /usr/lib/boot/unix_mp: executable (RISC System/6000) or object module not stripped /usr/lib/boot/unix_up: executable (RISC System/6000) or object module not stripped [cph@ozona ~]$ file /usr/lib/boot/unix* /usr/lib/boot/unix: symbolic link to /usr/lib/boot/unix_up. The getconf command will return the configuration of your machine.510./xwsetup Note: do NOT configure ReportNet yet Set the JAVA_HOME and LD_LIBRARY_PATH variables: # export # export For AIX: # export # export JAVA_HOME=<path/to/jre> LD_LIBRARY_PATH =<crn location>/bin JAVA_HOME=<path/to/jre> LIBPATH=<crn location>/bin PRABIR SINGH . chmod 777 <filename>). set FTP transfer mode to binary. the executables are under solaris/ directory. don't forget to change permissions to allow execution (ie. /usr/lib/boot/unix_kdb: executable (RISC System/6000) or object module not stripped /usr/lib/boot/unix_up: executable (RISC System/6000) or object module not stripped We can see that 'anna' is a 64-bit capable platform.tar Run the setup For Solaris.1.1. with XWindows: # . Since you are looking only for the kernel parameters. Extract the CRN files # gunzip crcd-solaris-1./xstartup without XWindows: # . you will see the following output: 32-bit sparc applications On a 64 bit Solaris system.

Security in cognos In Framework Manager.1/lib/ext to <jre directory>/lib/ext Note: do NOT overwrite existing .Object Security You secure an object directly by allowing users access to the object. denying users access tothe object. There are different types of security in Framework Manager: 1. and four Sales Managers.96 Update java environment Copy the contents of <crn location>/bin/jre/1. security is a way of restricting access to metadata and data across Cognos 8 products. When the package is available for report authors. 2. or keeping it hidden for all users. Run Cognos Configuration # . and apply the filter to the salary query subject.Data Security You can restrict the data represented by query subjects in a project by creating a security filter.sh Configure as needed and run Please refer the documents below for unix basic commands Note--Rm-fr(For deleting the folder containing files).3. your Sales team consists of a Sales Director. and a report is generated for the Sales Managers and the Sales Director.For example. The security filter controls the data that is shown to the report authors when they set up their reports.jar files or else existing applications may not work.pdf PRABIR SINGH . only the Sales Director can see the salary information for the sales managers. ¤¤ ¤¤ unix co ands./crconfig.pdf unix co ands1. You create a security filter that includes the groups directors and sales managers.

When you add object-based security. all objects in the model will also have security applied to them. You choose to make the object visible to selected users or groups.Package Security You can define metadata security when you create and publish packages in Framework Manager. all objects in your project are visible to everyone who has access to the package. or role directly to the object. group. You can add entries that were created in both third-party authentication providers and Cognos 8 as members of a Cognos group. In Cognos 8 you can do it in three stages 1) Package Level 2) Object level 3) Data level Package level Expand the namespace R click on package > Click on Edit Package Package Access window appears Remove All users from it Click Adds select Cognos Select Report Administrator OK it save the package in Framework Manager (FM) PRABIR SINGH . 3.97 Metadata security can be applied directly to objects in a project. you need to set it for all objects. A package is a secured subset of a project. A package can be published and can be included in other packages. Note---User . If you do not set object-based security. you apply a specific user. You can organize your security by specifying which users. You can also define metadata security after creating the package. Once you set security for one object. and roles have access to certain parts of the published model. They will not be visible to anyone. groups. Group and Roles are the access permissions given. When you apply security to one object. You can do this by setting security on the root namespace.

98 Publish the package ---------------------------------------------------- Object Level Expand the namespace R click on a table > Click on Specify Object Security On specify Object Security window click on ADD On select users and group dialog box select Cognos Select Report Administrator & Consumers Click Add In new window under allow Report Administrator deny consumer Now R click on namespaces click on Specify Object Security Here allow both consumers & Report Admin Right click on packages Explore package window opens Select Object security tab appears You will be allowed see who is allowed and who is not ------------------------------------------------------- PRABIR SINGH .

99 Data level Right click on a table Select query subject select specify security filter specify data security dialog box appear click on ADD select Cognos select consumers Ok it click the first row click on insert In Filters folder select the appropriate filter save the package and publish it Row Level Security You can use session parameters to map a data item to one of the ldap user values. PRABIR SINGH . Now to go one step further let's say you have employee and managers as users if your ldap source has them in different groups you can create a different mapping to equate the employee number of the managers to the manager# query item this will allow the managers to see all of their staff. EX: Your ldap has employee # your data has a table with employee # manager# other columns and this table is joined to you model. This will filter on the users employee number. depending on what you authentication source is and if the necessary values are there. You need to do this to all query subject that you want to secure you map a FM query item to the session parameter employeenumber (from your ldap source).

like the deployed folder. CMOBJPROPS14 Has details regarding the versions. service description etc details about portlets in this table PRABIR SINGH . the cube location etc. This table has the names of all the objects in the content store. phone number. The binary value in CPARMVALUE is XML compressed with gzip. CMOBJPROPS13 It stores the names of parameter passed to the range prompts. such as: Public folders Packages Reports Data sources Distribution lists and contacts Printers The Cognos namespace deployment specifications Cognos Content Store Database Tables Table name CMSYSPROPS CMOBJNAMES CMOBJPROPS1 CMOBJPROPS2 CMOBJPROPS3 CMOBJPROPS4 CMOBJPROPS6 CMOBJPROPS7 CMOBJPROPS10 This table has the Content Store Version. CMOBJPROPS30 Stores the registration . etc This table stores the data about all the packages imported / exported in C8. creation time etc of the objects in the content store. System Service. CMOBJPROPS27 Has the details regarding the data source created in the content store using Cubes. Fax Given name etc are stored in this table Report scheduling information is stored. CMOBJPROPS20 Stores details regarding which are all the reports for which prompting has been enabled. CMOBJPROPS24 Stores the printer configuration details CMOBJPROPS25 CMOBJPROPS26 Stores the data regarding the objects deployed. Users. the number of folders present in the deployment archive. This table has fields like hour. the reports. Event Studio´ etc CMOBJPROPS18 This table stores the drill path from the source to the final target report. This is basically to maintain the metadata about the structure of the reports and models. CMOBJPROPS16 CMOBJPROPS17 This table provides the status of the multiple services of Cognos like Log Service. This table has columns like Contact Email and Contact. Monitor Service. Job Service Stores performance details of each component like ³query Studio. A4 . Report Service. Contact information is stored in this table. Description CMOBJPROPS11 This table stores the data sources configuration details like connect string. Roles \ Group Distribution list and contact information such as Email. And also has the details of which are the reports which has the default report options overridden. letter and 11X17 paper orientations Has the details of the all packages which were published using the FM. This table stores the XML of all reports and models. day week etc Stores Screen Tip and Object description provided while creating the objects are stored here Stores the printer paper setting details like height and width of A3 . Analysis Studio.100 Data contained in Content Store The content store includes all entries in the portal. with the properties selected during the process.

CMOBJPROPS33 Detail related to users.pd high_availabilit _with in_the_application_tie . CMID can be be linked to CMOBJNAMES for the names of each of the services CMOBJPROPS32 Has the details of the stored procedures used as the query items in the FM model. The parameter assign values are present in coded format CMOBJPROPS36 Has the list of all the Models published using framework manager CMOBJPROPS37 CMOBJPROPS38 CMOBJPROPS39 This table has the details of the routing sets configured for server / load balancing for each package published in the content store Configuration details about number of items to retrieve in studios.pdf cognos_8_performan ce_tuning_settings. PROPID can be linked to CMPROPERTIES for property names CMOBJPROPS52 Contains the properties for the connections CMOBJPROPS55 Has the URI for icons for each entry in Cognos Connection CMLOCALES Has the locale ids associated with each language supported by Cognos 8 Performance tuning in Cognos Causes y y y y Zero-footprint web-client Web-tier : one or more web-servers Application tier : one or more application-servers Data tier : o o Connection to content store (JDBC) o o Connection to q ery databases o o Connection to C bes o o Connection to metric store (JDBC ¦ ¥ Please find the attached documents for performance tuning. for a package are saved under this table. PRABIR SINGH § Cognos_8_Arch_and _tune. Has values for properties of reports and views. CMOBJPROPS34 Has the details regarding the drill through parameters of the drill through reports.101 CMOBJPROPS31 Has the custom logging level for each of the Cognos services. user groups user roles.

The join includes data from the first table only if it matches data from the second table. whether or not it matches data from the second. Services in Cognos and their uses PRABIR SINGH . Null is used for the missing values.102 Different types of application servers in Cognos. The join includes data from the second table only if it matches data from the first table. Please find t e doc ment attac ed. whether or not it matches data from the first. LEFT: The join includes all the data from the second table. whether or not FULL-it matches data from the other table. RIGHT The join includes all the data from each table. Joins in Oracle INNER: The returned data must be present in both the joined tables. The join returns data from one or both of the tables even if it does not match data from the other table. ¨ ¨ © © ¨ ¨ applicationser e rs. OUTER: The join includes all the data from the first table.p df  Installation of different types of application servers b a s05_c8.pdf  Please find t e doc ment attac ed.4_installi ng_cognos8.


IBM Cognos services
After you install and configure IBM Cognos BI, one dispatcher is available on each computer by default. Each dispatcher has a set of associated services, listed in the following table. Service Purpose

Agent service

Runs agents. If the conditions for an agent are met when the agent runs, the agent service asks the monitor service to run the tasks.

Annotation service

Enables the addition of commentary to reports via the IBM Cognos Dashboard. These comments persist across versions of the report.

Batch report service

Manages background requests to run reports and provides output on behalf of the monitor service.


Enhances the overall system performance and Content Manager scalability Manager cache by caching frequent query results in each dispatcher. service

Content y Manager service y

Performs object manipulation functions in the content store, such as add, query, update, delete, move, and copy Performs content store management functions, such as import and export

Data movement Manages the execution of data movement tasks in IBM Cognos BI. Data service movement tasks, such as Builds and JobStreams, are created in Data Manager Designer and published to IBM Cognos BI.

Delivery service Sends emails to an external SMTP server on behalf of other services, such as the report service, job service, agent service, or data integration service

Event management service

Creates, schedules, and manages event objects that represent reports, jobs, agents, content store maintenance, deployment imports and exports, and metrics





Graphics service Produces graphics on behalf of the Report service. Graphics can be generated in 4 different formats: Raster, Vector, Microsoft® Excel XML or PDF.

Human task service

Enables the creation and management of human tasks. A human task such as report approval can be assigned to individuals or groups on an ad hoc basis or by any of the other services.

Index data service

Provides basic full-text functions for storage and retrieval of terms and indexed summary documents.

Index search service

Provides search and drill-through functions, including lists of aliases and examples.

Index update service

Provides write, update, delete, and administration functions.

Job service

Runs jobs by signaling the monitor service to run job steps in the background. Steps include reports, other jobs, import, exports, and so on.

Log service

Records log messages generated by the dispatcher and other services. The log service can be configured to record log information in a file, a database, a remote log server, Windows® Event Viewer, or a UNIX® system log. The log information can then be analyzed by customers or by Cognos Software Services, including: y y y security events system and application error information selected diagnostic information

Metadata service

Provides support for data lineage information displayed in Cognos Viewer, Report Studio, Query Studio, and Analysis Studio. Lineage information includes information such as data source and calculation expressions.

Metric Studio

Provides the Metric Studio user interface for monitoring and entering



Service service

Purpose performance information

Migration service

Manages the migration from IBM Cognos Series 7 to IBM Cognos BI.

Monitor service


Manages the monitoring and execution of tasks that are scheduled, submitted for execution at a later time, or run as a background task Assigns a target service to handle a scheduled task. For example, the monitor service may ask the batch report service to run a report, the job service to run a job, or the agent service to run an agent. Creates history objects within the content manager and manages failover and recovery for executing entries



PowerPlay® service

Manages requests to run PowerPlay reports.

Presentation service


Transforms generic XML responses from another service into output format, such as HTML or PDF Provides display, navigation, and administration capabilities in IBM Cognos Connection


Query service

Manages Dynamic Query requests and returns the result to the requesting batch or report service.

Report data service

Manages the transfer of report data between IBM Cognos BI and applications that consume the data, such as IBM Cognos BI for Microsoft Office and IBM Cognos Mobile.

Report service

Manages interactive requests to run reports and provides output for a user in IBM Cognos Connection or a studio.

Definition Of Metric Studio:

A metric. is a key performance indicator (KPI) related to time. In other words you use Metric Studio to monitor KPIs between one period and the next. A data warehouse is essentially a database and is a combination of two sorts of database tables. Fact tables ± a µfact¶ table records the measures that are included in the data warehouse. Metrics have both status (whether the metric is within scope) and trend (performance relative to last period). It helps you ensure that your organization¶s performance is consistent with its targets and goals. Impact diagrams show the relationship between different metrics. depending on what it is measuring. Sometimes it is useful to attach a Cognos 8 report to a metric. Dimension tables ± these contain descriptive information. got worse or stayed the same. Actions can be set up to improve performance of a metric. A scorecard shows graphically whether the metric has improved. to give you more detail about the metric data and this feature is available. and other performance measures within an organization. projects. Data warehouse Design: Data Warehousing Design At Ace star Solutions we design and build star-schema data warehouses following the popular Kimball methodology. A Star Schema PRABIR SINGH . for example quantity sold. revenue etc. For example. Projects track long-term business activities associated with a scorecard. µfact¶ tables and µdimension¶ tables. all revenue measures might have the same type. What µimproved¶ and µgot worse¶ actually mean is defined when the metric is set up. With Metric Studio. Metrics are grouped into types. a bigger number might mean performance has improved or slipped. An example of a dimension table might be called D_Products and contain a list of product codes and descriptions. In other words. performance can be displayed either as a list report or a line chart. so this saves time when defining the metric.106 Metric Studio is a performance tool for managing monitoring and analyzing metrics. all metrics of the same type have the same behavior. as Metric Studio uses the term. Often a chart makes it easier to spot trends.

Product details. transformation. but this will include many data marts. Note that only the details of the actual sale are held in the sales fact table F_Sales.107 A simple star schema is shown above. which speeds up processing when using it for reports and analyses. The staging layer holds the raw data as it comes in. in the presentation layer the dimension and fact tables the end users have access to are created (see diagram above). The star schema warehouse is built in three layers. Each fact table will then have its own star schema (but they usually overlap) and each is called a data mart. load (ETL for short). These will usually be database tables from various systems within an organisation. for example a spreadsheet containing product details would be stored in a table in the staging layer. A large corporation may have only one data warehouse. PRABIR SINGH . So one or more data marts go to make a single data warehouse. each of which is usually a database. The enterprise layer is the place where things are added to the data. Multi-layered design. Data Marts A data warehouse usually has more than one fact table. There is only one table join between each table. but are often supplemented by other files such as spreadsheets and text files. for example revenue might be calculated by multiplying quantity sold and price. customer details and the date are held in separate tables. First we extract the data from its various data sources. Build of data warehouse: The building of a data warehouse is known as extract. Finally.

Snowflake Schema: A snowflake schema is a term that describes a star schema structure normalized through the use of outrigger tables. A good ETL package will provide tools for monitoring the load such as log files. the dimensions can often be updated with changes and additions rather than being completely rebuilt each time. y Hierarchies for the dimensions are stored in the dimensional table itself in star schema.e dimension table hierarchies are broken into simpler tables. In transformation codes must be translated. This monitoring can be done in a number of ways (home-made scripts for example) but should involve some form of automation. y Whereas hierarchies are broken into separate tables in snow flake schema. a shcheduler and reject files for rejected input records. Difference between Star Schema and Snowflake Schema: Star Schema: Star Schema is a relational database schema for representing multimensional data. In most organisations the data warehouse build will need to be monitored to ensure that the data has arrived at its destination and is correct. usually on a daily basis. It is the simplest form of data warehouse schema that contains one or more dimensions and fact tables. For example dates on different systems in the organisation are often stored in different ways. These hierarchies helps to drill down the data from topmost hierarchies to the lowermost hierarchies. It is called a star schema because the entity-relationship diagram between dimensions and fact tables resembles a star where one fact table is connected to multiple dimensions. Apart from adding calculations and data from various tables where necessary. These differences must be resolved in the transformation process. Monitoring the build. PRABIR SINGH .108 In the transformation process we have the opportunity to massage the data into what we want for the data warehouse. In a star schema every dimension will have a primary key. y in a star schema a dimension table will not have any parent table. Even then. The advantage of star schema is slicing down performance increase and easy understanding of data. The center of the star schema consists of a large fact table and it points towards the dimension tables. This is known as data cleansing. this is where we check that the data is consistent. The load process creates the data warehouse. In a dimensional star schema data warehouse this means loading the dimension and fact tables. as this is vital for the star schema to join together properly and have any meaning. This is where most of the action takes place. This involves checking that all records in the fact tables link correctly to the dimension tables. Often the dimensions do not change much ± for example a price list might only change annually ± so not all dimensions need to be loaded every day. Fact tables ± for example your daily sales ± need to be updated more often. y Whereas in a snow flake schema a dimension table will have one or more parent tables. A sophisticated ETL system will be able to send out email alerts when things go wrong. and in some cases correct the problem and reinput the data. i.

Right-click the Cognos ReportNet entry and select delete. 6. or alternatively edit the appropriate startup batch files. PRABIR SINGH . click Save.109 Installing IBM Cognos 8 BI Server Components in Multiple Locations (Distributed Installations) Ins lling IBM C gnos 8 BI er er C     How to set the IBM Cognos ReportNet installation to Small. Stop the Service before making manual changes.sh (UNIX) file to use the right configuration. 3. (2) the Reportnet Dispatcher Service (BiBusTkServerMain). 2. or Large in Cognos Configuration or via the startup. 4. Under Environment. It is also possible to change the setting manually by modifying the startup. and change the Type to the desired configuration of Small. Medium. From the File menu. Restart the Cognos ReportNet services. Right-click the ReportNet Service. and restart it once the changes have been made. find the ReportNet Service. Stop the Cognos ReportNet services. Small.sh file Use Cognos Configuration to set the application size appropriately. Type Cognos ReportNet as the configuration name. Medium and Large refer to the amount of memory (heap size) allocated to the Java process. For ReportNet there are two Java processes: (1) the Content Manager Service (CM). Medium.bat or startup. Steps:To change the setting in Cognos Configuration: 1. select New Resource => Configuration.bat (Windows) or startup. 5. or Large.

sh script. Save the file. Here are the entries for a Small configuration: rem "for machines with 1GB RAM" set CATALINA_OPTS=-Xmx768m -XX:MaxNewSize=384m -XX:NewSize=192m XX:MaxPermSize=128m %DEBUG_OPTS% rem "for machines with 2GB RAM" rem set CATALINA_OPTS=-Xmx1152m -XX:MaxNewSize=576m -XX:NewSize=288m XX:MaxPermSize=128m %DEBUG_OPTS% rem "for machines with 3GB RAM" rem set CATALINA_OPTS=-Xmx1536m -XX:MaxNewSize=768m -XX:NewSize=384m XX:MaxPermSize=128m %DEBUG_OPTS% PRABIR SINGH . and ensure the other configurations are not used by inserting a # at the beginning of the line. and restart the server by using the startup.110 Remove the # from the configuration line in the Startup file that you would like.bat or startup.

Sign up to vote on this title
UsefulNot useful