Configuring IBM Cognos BI with WebSphere Portal

If you are using IBM® Cognos® Business Intelligence with WebSphere® Portal, you must update the ProxyServlet_Servlet section of the web.xml file.

1. Export the WebSphere Portal enterprise archive (EAR) file, wps.ear, according to your network configuration. If you have a cluster environment, the WebSphere Portal EAR file must be exported from the WebSphere Application Server Network Deployment machine.
   1. At a command line, change to the application_server_profile_root/bin directory.
   2. Run the following command to export the wps.ear file to a temporary directory (make sure that all commands are entered on one line):
      • wsadmin.bat -user admin_user_id -password admin_password -c "$AdminApp export wps directory/wps.ear"
      • ./wsadmin.sh -user admin_user_id -password admin_password -c '$AdminApp export wps directory/wps.ear'

      where admin_user_id is the administrator's user ID, admin_password is the administrator's password, and directory is the temporary directory.

2. Create the /wps_expanded subdirectory. Use the EARExpander scripting tool to expand the contents of the exported EAR file (make sure that all commands are entered on one line).
   • EARExpander.bat -ear directory\wps.ear -operationDir directory\wps_expanded -operation expand
   • ./EARExpander.sh -ear directory/wps.ear -operationDir directory/wps_expanded -operation expand
3. Make a backup copy of directory/wps_expanded/wps.war/WEB-INF/web.xml.
4. Update directory/wps_expanded/wps.war/WEB-INF/web.xml.
   1. Open web.xml.
   2. Find the following section:

      <servlet id="ProxyServlet_Servlet">
        	<servlet-name>ProxyServlet</servlet-name>
        <servlet-class>com.ibm.wps.proxy.servlet.ProxyServlet</servlet-class>
      </servlet>

   3. Replace the section with the following text:

      <servlet id="ProxyServlet_Servlet">
        <servlet-name>ProxyServlet</servlet-name>
        <servlet-class>com.ibm.wps.proxy.servlet.ProxyServlet</servlet-class>
        <init-param>
          <param-name>useCtxPathForCookies</param-name>
          <param-value>true</param-value>
        </init-param>		 		 
      </servlet>

5. Delete the original wps.ear file from the directory where you initially exported it.
6. Use the EARExpander command to collapse the EAR file directory back into an EAR file.
   • EARExpander.bat -ear directory\wps.ear -operationDir directory\wps_expanded -operation collapse
   • ./EARExpander.sh -ear directory/wps.ear -operationDir directory/wps_expanded -operation collapse
7. Use the wsadmin command to update the WebSphere Portal EAR file.
   Note: If you have a managed cell (with or without a cluster), perform this step on the deployment manager machine.
   • wsadmin.bat -user admin_user_id -password admin_password -c "$AdminApp install directory/wps.ear {-update -appname wps -nodeployejb}"
   • ./wsadmin.sh -user admin_user_id -password admin_password -c '$AdminApp install directory/wps.ear {-update -appname wps -nodeployejb}'

   where admin_user_id is the administrator's user ID, admin_password is the administrator's password, and directory is the temporary directory.

8. Restart WebSphere Portal server. In a cluster configuration, restart the cluster.
9. Add the IBM Cognos BI host name and port number to the list of trusted servers in IBM Cognos BI. Otherwise, you will not be able to view the pages in Business Space.
   1. Open the IBM Cognos BI Configuration client. To open the client, run the cogconfig.bat or cogconfig.sh file located in cognos_installation_root/bin64 .
   2. Select Local Configuration > Security > IBM Cognos Application Firewall.
   3. Click the pencil icon next to Valid domains or hosts and add the IBM Cognos BI host and port number configured in the endpoint from Business Space. For example, add lc2d266009.example.com:9080. If you have multiple hosts, click Add to add more entries.
   4. Click OK. Click Save.
   5. Restart the server that is running IBM Cognos BI.