To use IBM Cognos product documentation, you must enable JavaScript in your browser.

Change the Application Server Startup Script   

Some application servers have specific requirements that you must meet before you can run IBM Cognos 8. Depending on the application server, you may have to define environment variables, copy files, and add or change code in files.

If you are using BEA WebLogic Server 8.1 or Red Hat JBoss, you must make changes to the application server startup script. The startup script must be modified to specify JVM settings. For JBoss, you must also specify a log4j argument. For WebLogic 9, we recommend that you use the Administration Console to modify the WebLogic environment.

If you are using IBM WebSphere Application Server, SAP NetWeaver 6.40, or Oracle Application Server, no changes to its startup script are required unless you want to add the environment variable changes. If you do make changes, the Administrative Console can be used.

For Red Hat JBoss, we recommend that you create a copy of the default server instance so that you can use the original default server instance as a backup. Give the copy a name that does not use spaces, such as cognos.

If your environment contains a JRE that you are using for other products, the JRE folder may contain .jar files that are not compatible with the .jar files that are provided with IBM Cognos 8. This may result in a failure to start IBM Cognos 8 on your application server. In this situation, we recommend that you direct IBM Cognos 8 to use the endorsed .jar files by including the following parameter in the Java command line:

-Djava.endorsed.dirs=${cognos8_home}/tomcat[version]/common/endorsed
Steps for WebLogic
  1. Create a WebLogic Server (WLS) domain for IBM Cognos 8.

    If you are configuring the IBM Cognos Servlet Gateway, create a second domain for this application.

    For information about creating domains, see the WebLogic documentation.

  2. Go to the appropriate directory and open the application server startup script in an editor. The following are possible directories:

    The name of the startup script may vary depending on the type of WebLogic installation performed. For example, in a managed server installation, the name of the startup script is startManagedWebLogic.sh (UNIX) or startManagedWebLogic.cmd (Windows).

  3. For non-IBM JRE versions, select the JVM run mode, and change the default setting from JAVA_VM= to JAVA_VM=-server

  4. Modify the JAVA_OPTIONS to set the appropriate XML parser for IBM Cognos 8. Add the third line, as shown in this example:

    JAVA_OPTIONS=
    -Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
  5. Set the minimum and maximum memory used by the JVM.

    Typically, the memory is set using two JVM parameters: -Xms and -Xmx. A minimum of 256 MB and a maximum of 768 MB are suggested starting values. You can change these values to suit your environment.

    For WebLogic 9, the MaxPermSize parameter must also be set. Here is an example:

    -XX:MaxPermSize=128m

    For information about JVM parameters, see the JVM or application server documentation.

  6. Ensure that the production mode is enabled.

    For WebLogic 8 & 9, change PRODUCTION_MODE= to PRODUCTION_MODE=true

  7. Save and close the file.

Steps for JBoss
  1. Go to the JBoss_location/bin directory and open the application server startup script in an editor. Do one of the following:

  2. Go to the JAVA_OPTS variable and increase the memory used by the JVM.

    Typically, the memory is set using two JVM parameters: -Xms and -Xmx. A minimum of 256 MB and a maximum of 768 MB are suggested starting values. You can change these values to suit your environment.

    Here is an example:

    rem Sun JVM memory allocation pool parameters. Modify
    as appropriate.
    set JAVA_OPTS=%JAVA_OPTS% -Xms192m -Xmx
    768m - 
    Dsun.rmi.dgc.client.gcInterval=3600000 - 
    Dsun.rmi.dgc.client.gcInterval=3600000 - 

    For information about these parameters, see the JVM or application server documentation.

  3. Add a log4j argument, as shown in the following example:

    rem Sun JVM memory allocation pool parameters. Modify
    as appropriate.
    set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m - 
    Dsun.rmi.dgc.client.gcInterval=3600000 - 
    Dsun.rmi.dgc.client.gcInterval=3600000 - 
    DLog4j.defaultInitOverride=true

    For information about these parameters, see the JVM or application server documentation.

  4. Save and close the file.