Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Troubleshoot portlet development
This section contains information that can assist you in preventing, identifying, and correcting problems related to IBM® WebSphere® Portal Express. For information related to specific components, see the appropriate troubleshooting topic.
- Installing WAR file fails when file name is too long
- Installing WAR file fails when web.xml <display-name> is too long
- Login command customization fails
- Struts portlets from the IBM Workplace Solutions Catalog at http://catalog.lotus.com/wps/portal/workplace will not import into WebSphere Studio Application Developer
- When importing WAR files into Rational Application Developer 6.0, nuisance exceptions appear in OS console
Install WAR file fails when file name is too long
Solution: Because Windows limits the maximum path length to 260 characters, the name of the WAR file must be less than approximately 25 characters. Installing a WAR file with a name that is more than 25 characters can result in longer pathnames which makes the files not accessible anymore resulting in FileNotFoundExceptions. The Portal tries to truncate or rename long names before it deploys the WAR file into Application Server. However it cannot always circumvent the pathname to exceed the limit. To correct this error, modify the file name to be less than 25 characters. IBM recommends that you install WebSphere products into the root directory to keep the common part of pathname short. For example, install to c:\WebSphere instead of c:\Program Files\WebSphere.
Install WAR file fails when web.xml <display-name> is too long
Solution: Because Windows limits the maximum path length to 260 characters, the <display-name> of the web application in the web.xml must be as short as possible, approximately less than 25 characters. Application Server uses the <display-name> to construct the application name space. Installing a WAR file with a <display-name> that is more than 25 characters can result in longer pathnames which makes the files not accessible anymore resulting in FileNotFoundExceptions. The Portal tries to truncate or rename long names before it deploys the WAR file into Application Server. However it cannot always circumvent the pathname to exceed the limit. To correct this error, modify the file name (and related <display-name>) to be less than 25 characters. IBM recommends to install the WebSphere products into the root directory to keep the common part of pathname short, e.g. c:\WebSphere instead of c:\Program Files\WebSphere.
Login command customization fails
Solution: When creating a implementation of one of the WebSphere Portal Express classes, for example, Login or Logout modules, update IBM WebSphere Application Server so that the classes load correctly.
- Open the Administrative Console for WebSphere Application Server.
- Click Environment, then Shared Libraries, then WPSlib.
- Add your JAR file to Classpath.
- Click OK.
- Click Save to save the changes to the master configuration.
- Restart the WebSphere_Portal application server.
Struts portlets from the IBM Workplace Solutions Catalog at http://catalog.lotus.com/wps/portal/workplace will not import into WebSphere Studio Application Developer
The new Struts Portlet Framework WAR files will not import into WebSphere Studio Application Developer after downloading from the IBM Workplace Solutions Catalog at http://catalog.lotus.com/wps/portal/workplace (http://catalog.lotus.com/wps/portal/portalworkplace, NavCode: 1WP10003N). This is because these WAR files contain 2 META-INF directories: one lower-case and one upper-case. The existence of these two directories causes WebSphere Studio to fail during the import.
Solution: This will be resolved with the next release of the Struts Portal Framework. As a workaround, you can expand the WAR and then select "Import" as "File System" to import the individual files.
When importing WAR files into Rational Application Developer 6.0, nuisance exceptions appear in OS console
When using the WAR import wizard to import WAR files into Rational Application Developer (RAD) 6.0, the following nuisance exceptions may appear in OS console, but not in trace.log.
*** ERROR ***: Sat Apr 16 07:13:27 CST 2005
com.ibm.etools.j2ee.commonarchivecore.exception.ArchiveWrappedException !Stack_trace_of_nested_exce!
com.ibm.etools.j2ee.commonarchivecore.exception.DeploymentDescriptorLoadException:
WEB-INF/web.xml !Stack_trace_of_nested_exce!
com.ibm.etools.j2ee.commonarchivecore.exception.EmptyResourceException:
platform:/resource/<web_app_name>/WebContent/WEB-INF/web.xml at com.ibm.etools.j2ee.commonarchivecore.util.ArchiveUtil.getRoot(Unknown Source)
...
Solution: This is a RAD 6.0 issue and fixed in RAD 6.0.0.1. Updates for RAD can be located on the product homepage: http://www-128.ibm.com/developerworks/rational/products/rad/.