Configure Application Server Properties and Deploy Cognos Components 

You must configure application server properties and deploy the Cognos components.

Steps for WebSphere

1. Start the WebSphere Application Server, and then access the WebSphere Administrative Console.

2. Create a new server instance into which the Cognos 8 application will be deployed, if this option is available in the version you are running.

   If you are deploying the Cognos Servlet Gateway, create a second separate server instance.

3. Install a new Enterprise Application using the application file that was built by Cognos Configuration.

   For Cognos 8, the default context root is p2pd, which can be used in most cases. For the Cognos Servlet Gateway, the default context root is ServletGateway. Other default application deployment values, such as the application name, may be changed to better suit your environment. The context root value used to deploy the application must be the same as the context root value entered in Cognos Configuration when running the Build Application wizard.

4. Set the memory used by the JVM.

   Usually, the memory is set by adding or changing the initial and maximum Java heap size. For information about these parameters, see the JVM or application server documentation.

   Tip: A minimum of 256 MB and a maximum of 768 MB are suggested starting values. You can change these values to suit your environment.

5. In the server properties, add an environment variable, as listed in the following table, that references the installation_location/bin directory.

   Operating system	Environment variable
   Windows	PATH
   AIX	LIBPATH
   Solaris	LD_LIBRARY_PATH
   HP-UX	SHLIB_PATH

6. Stop and then restart the WebSphere application server instance used for Cognos components.

7. Verify that Cognos components are running by looking for the following message in the application server admin console or in the application server log file:

   The dispatcher is ready to process requests.

Steps for WebLogic

1. If you used the expanded directory option when building the application in Cognos Configuration, go to step 2. If you created a WAR file, expand the application manually:

   • Create a directory in a location that is accessible to the application server, giving the directory the same name as the context root.

     For Cognos 8, the default context root and application directory name is p2pd, which can be used in most cases. For the Cognos Servlet Gateway, the default context root is ServletGateway. Other default application deployment values, such as the application name, may be changed to better suit your environment. The context root value used to deploy the application must be the same as the context root value entered in Cognos Configuration.

   • From the directory you just created, extract the application WAR file to the WebLogic installation using the following command from a command prompt:

     WebLogic_location/jdk_version/bin/jar xvfm "installation_location/application.war" .

     Important: A space and then a period are required at the end of the command. In this command, the period does not refer to the current directory.

2. Start the WebLogic Administration Server and the WebLogic Managed Server associated with the Cognos domain.

   Node Manager must be started before you can start and stop Managed Server instances using the Administration Console

3. For WebLogic 9, you must modify the environment in the WebLogic Administration Console before deploying Cognos 8. Logon to the Administration Console and navigate to the Managed Server instance that will host the Cognos 8 application. Select the Server Start tab for the Managed Server instance and enable edit mode.

4. In the Java Home box, enter the path for the JVM. This value must be the same as is used for Cognos 8. You must use the JVM that is included with the WebLogic installation.

5. Set the Java arguments.

   The Java arguments include all JVM settings, such as memory settings specified using two JVM parameters: -Xms and -Xmx. For WebLogic 9, the MaxPermSize must also be set. You must also set the appropriate XML parser for Cognos 8.

   For example, in the Arguments box, type

   -Xms768m -Xmx768m -XX:MaxPermSize=128m -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser

   If you use WebLogic Server 9 on AIX, you must also specify the appropriate serial version UID in the Java arguments. If you do not make this update, a serial version UID mismatch occurs when using WebLogic Server 9 with IBM Java 5 because WebLogic 9 requires JDK 1.5.

   For example, in the Arguments box, type

   -Xms768m -Xmx768m -XX:MaxPermSize=128m -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0

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

6. Save and apply the changes.

   You can now start and stop the Managed Server instance from the Control tab.

7. Start the server instance. The server instance must be started before deploying Cognos 8 or or Cognos Servlet Gateway.

8. Deploy the Cognos 8 or Cognos Servlet Gateway application in the WebLogic console using a new Web application as follows:

   • Set the application name.

     For example, cognos8

   • Set the path to the directory where the expanded application files are located.

     Note: Cognos 8 uses a custom loader. You must use the expanded directory option when deploying.

   • Select the target server instance.

     It is recommended that the Administration Server be used only for WebLogic administration tasks and that the Cognos 8 application be deployed to its own Managed Server instance.

9. After the deployment has completed successfully, set the reload period for the Web application to -1 to improve performance. This will prevent WebLogic from checking for updated application files that are used only in a development environment.

10. Stop and then restart the WebLogic Managed Server associated with the Cognos domain to activate the changes.

11. Verify that Cognos components are running by looking for the following message in the application server console window or in the application server log file:

    The dispatcher is ready to process requests.

Steps for SAP Web Application Server 6.40 on Windows

1. Open the configuration tool by typing

   drive:\usr\sap\sapid\JCxx\j2ee\configtool\configtool.bat

   For example, if the SAP ID is J2E and the installation is on drive D, you would type

   D:\usr\sap\J2E\JC00\j2ee\configtool\configtool.bat

2. When prompted to use the default DB settings, click Yes.

3. Under cluster-data, instance_IDxxxxxxx, Dispatcher_IDxxxxxxx, services, where xxxxxxx is the ID number for your installation, highlight http.

4. Under Global Properties, highlight KeepAliveTimeout and type a higher number and then click Set.

   Tip: We suggest an initial KeepAliveTimeout number of at least 60.

5. Under cluster-data, instance_IDxxxxxxx, highlight Server_IDxxxxxxx.

6. Set the memory used by the JVM.

   Follow the recommendations from SAP. For more information, see SAP Note 723909 in the SAP Support Portal.

   If your computer has less than 1.5 GB of memory, you may have issues when you run SAP Web Application Server. We suggest a minimum value of 768 MB.

7. In the Java parameters box, set the XML parser as follows:

   -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser

8. For Cognos 8 environments that use Report Studio, under cluster-data, instance_IDxxxxxxx, highlight Server_IDxxxxxxx, services, and highlight http.

9. Under Global Properties, highlight CompressedOthers, type false, and then click Set.

10. Save the changes.

    You are prompted to restart the server.

11. Restart the server by using the SAP Management Console or by restarting the services in Services.

12. Use the Deploy tool to create a new project.

13. Load the Cognos application file you created using Cognos Configuration. By default, the file is named p2pd.ear for Cognos 8 and ServletGateway.ear for Cognos Servlet Gateway.

14. Using the Deploy tool, connect to the Administration tool and deploy the application file.

15. When you are prompted to start the application, click Yes.

16. Save the project.

Steps for Oracle Application Server Release 2

1. Create an OC4J instance for Cognos components to run within.

2. Set the memory used by the JVM.

   Typically, the memory is set by adding or changing 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 information about these parameters, see the JVM or application server documentation.

3. In the server properties, add "-userThreads" to the OC4J Options.

4. In the server properties, add an environment variable, as listed in the following table, that references the installation_location/bin directory.

   Operating system	Environment variable
   Windows	PATH
   AIX	LIBPATH
   Solaris	LD_LIBRARY_PATH
   HP-UX	SHLIB_PATH

5. Deploy the Cognos application file (named p2pd.ear for Cognos 8 or ServletGateway.ear for Cognos Servlet Gateway, by default) created by Cognos Configuration.

   The value of the Map to URL parameter must be the same as the context root value entered in Cognos Configuration.

6. Start the OC4J instance that you created for Cognos components.

7. Verify that Cognos components are running by looking for the following message in the application server console window or in the application server log file:

   The dispatcher is ready to process requests.

Steps for Oracle Application Server Release 3

1. Create an OC4J instance for Cognos components to run within.

2. On Windows only, comment out the following entries in the Oracle_location\j2ee\Cognos_OC4J_instance\config\global-web-application.xml file:

   <welcome-file-list>
   	<welcome-file>index.html</welcome-file>
   	<welcome-file>default.jsp</welcome-file>
   	<welcome-file>index.htm</welcome-file>
   	<welcome-file>index.jsp</welcome-file>
      </welcome-file-list>

3. Open the Oracle_location/opmn/conf/opmn.xml file.

4. Add an environment variable that references the installation_location/bin directory and set variables for data sources.

   Here is an example for for Windows and DB2:

   <environment>
   	<variable id="PATH" value="c8_location/bin" 
   		append="true"/>
   	<variable id="DB2DIR" value="
   location"/>
   	<variable id="DB2INSTANCE value="
   instance_name"/>
   	<variable id="INSTHOME value="
   location"/>
   </environment>

   This table lists the environment variables for each operating system that must reference the c8_location/bin directory.

   Operating system	Environment variable
   Windows	PATH
   AIX	LIBPATH
   Solaris	LD_LIBRARY_PATH
   HP-UX	SHLIB_PATH

5. Set the memory used by the JVM.

   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 information about these parameters, see the JVM or application server documentation.

   Here is an example:

   <data id="java-options" value="-server -Xmx768m -XX:MaxNewSize=384m
   -XX:NewSize=192m -XX:MaxPermSize=128m -classpath 
   c8_location\bin;c8_location\webapps\p2pd\WEB-INF\lib
   -

6. Define the OC4J userThreads setting.

   Here is an example:

   <data id="oc4j-options" value="-properties -userThreads"/>

7. Save and close the Oracle_location/opmn/conf/opmn.xml file.

8. Deploy the Cognos application file (named p2pd.ear for Cognos 8 or ServletGateway.ear for Cognos Servlet Gateway, by default) created by Cognos Configuration.

   The value of the Map to URL parameter must be the same as the context root value entered in Cognos Configuration.

9. Start the OC4J instance that you created for Cognos components.

10. Verify that Cognos components are running by looking for the following message in the application server console window or in the application server log file:

    The dispatcher is ready to process requests.

Steps for JBoss

1. If you do not want to use the default port of 8080, open the JBoss_location/server/instance_name/deploy/jbossweb-tomcat55.sar/server.xml file.

2. In the server.xml file, change the default port number of 8080 used by the server instance to the port specified in Cognos Configuration. For example,

   <Service name="jboss.web"
   	className="org.jboss.web.tomcat.tc5.StandardService">
   <!-- A HTTP/1.1 Connector on port 8080 -->
   <Connector port="8080" address="${jboss.bind.address}"
   	maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
   	emptySessionPath="true"
   	enableLookups="false" redirectPort="8443" acceptCount="100"
   	connectionTimeout="20000" disableUploadTimeout="true"/>

3. Save and close the server.xml file.

4. Put the p2pd application in the JBoss_location/server/instance_name/deploy folder, if it is not already in this location.

5. Start the application server.

   The p2pd application is automatically detected and started by the application server.

6. Verify that Cognos components are running by looking for the following message in the application server console window or in the application server log file:

   The dispatcher is ready to process requests.