Configure your environment after installation

 

Take additional steps to configure your environment after installing IBM® WebSphere® Dashboard Framework. Follow the steps that are appropriate for configuring your server platform. Parent topic: Installing and configuring WebSphere Dashboard Framework

 

IBM WebSphere Portal

The following additional configurations are required for WebSphere Portal.

  1. Configure Heap Size -- By default, WebSphere Portal 6 sets 512 MB as the maximum allowed size for the heap. This maximum should be raised to 1 GB. If you are using WebSphere Portal 5.x, raise the heap size to 400 MB. Use the WebSphere Administrative console to set the heap size. For more information on configuring the heap size, see the WebSphere Administrative Console Help.

  2. Update the Cookie Path - The default settings on the WebSphere Portal do not include the WebSphere Dashboard Framework root directory in the cookie path. If you are using a development configuration on WebSphere Portal, the root directory must be added to the cookie path in order to save your session information.

    You may experience problems with refresh and caching of Web pages before you update the cookie path. You will not be able to successfully complete the tutorials without changing the cookie path. Use the WebSphere Administrative console to replace "/ wps " with "/" in your cookie path.

  3. (WebSphere Portal 5.1 only) Add " pbportlet.jar " File -- This file is needed only if you plan to build portlets based on the deprecated IBM Portlet API, rather than the Java Standard API (recommended). This JAR file, included in previous versions of WebSphere Portal, is not provided with version 5.1 As a result, procure this file and add it to your system. If you have access to a 5.0 version of WebSphere Portal, we can find this file at: WebSphere\PortalServer\pb\lib. Alternately, we can get a copy of this file from IBM Customer Support.

    The default web.xml used to create Factory Portlet WARs includes a reference to the WebSphere C2A Portlet wrapper ( com.ibm.wps.pb.wrapper.PortletWrapper ). As a result, all Portlet WARs must include the appropriate version of pbportlet.jar. When developing against WebSphere Portal 5.1 server, manually specify the location of the directory that contains the pbportlet.jar file.

    Once you acquire the pbportlet.jar file, place it in an accessible directory on the system on which you are installing WebSphere Portal 5.1.

    Create a project and, when the WebSphere Portlet Settings page is displayed, use the PB Portlet Jar Location input widget and browse to the location of the pbportlet.jar file. Then select the file and complete project creation.

    After you select this file the first time, it will be automatically included in the portlet WAR created by WebSphere Dashboard Framework.

 

WebSphere 5.x Application Server

In a WebSphere Application Server 5 environment, set the class load order on the WebApp project so that the class loader for the Factory application context looks at the JARs in the project's WebContent/WEB-INF/lib before looking at those shipped with WebSphere Portal. This ensures that latest versions of third-party JAR files are correctly picked up.

Follow these steps to set the class load order.

  1. In the WebSphere Application Server administrative console, go to Applications > Enterprise Applications .

  2. Click the enterprise application name for your WebSphere Dashboard Framework installation (for example, "dashboard_framework") to display a list of properties for the application.

  3. In the Related Items list of the Configuration Tab, click the Web Modules link.

  4. Click the wpf.war file, displaying the General Properties for the WPF WAR file.

  5. Change the Class loader Mode to " PARENT_LAST " and click OK.

  6. Save the changes to your local configuration.

  7. Restart the server.

 

Apache Tomcat

After creating a new IBM WebSphere Portlet Factory project, restart Tomcat. This ensures that all libraries are loaded correctly.

Library | Support | Terms of use |

Last updated: Thursday, March 15, 2007 11:57am EST

This information center is powered by Eclipse technology. (http://www.eclipse.org)