Error 500 returned when accessing the WebSphere Application Deployment page

Solution:

The war package name should not exceed 25 characters

From: http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp? Topic =/com.ibm.wp.exp.doc/WPS/tbl_dev.html

The war file fails to be installed when the file name is too long.

Solution:Because Windows limits the maximum path length to 260 characters, the war file name length must be less than 25 characters. If the installed war file has more than 25 characters, it will lead to a long path name, which makes the file no longer accessible, resulting in filenotfoundexceptions. Before deploying the war file to the application server, the portal will try to truncate or rename the long file name. But it cannot guarantee that the path name will never exceed the limit. To correct this error, change the file name to less than 25 characters. We recommend that you
The WebSphere product is installed in the root directory, so that the public part of the path name is relatively short. For example, install c: \ WebSphere instead of c: \ Program Files \ websphere.

The war file fails to be installed when web. xml <display-Name> is too long.

Solution:Because Windows limits the maximum path length to 260 characters, the <display-Name> of Web applications in Web. xml must be as short as possible, with less than 25 characters. Application Server uses <display-Name> to construct the application namespace. If the installed war file has <display-Name> of more than 25 characters, the path name is long, which makes the file no longer accessible, resulting in filenotfoundexceptions. Portal
Before deploying the war file to the application server, you will try to truncate or rename the long file name. But it cannot guarantee that the path name will never exceed the limit. To correct this error, change the file name (and related <display-Name>) to less than 25 characters. We recommend that you install WebSphere in the root directory so that the public part of the path name is relatively short. For example, you can install it in c: \ WebSphere instead of c: \ Program Files \ websphere.

LOGIN command customization failed

Solution:When creating your own implementation of a WebSphere Portal express class (for example, logging on to or logging out of the module), you must update IBM WebSphere Application Server so that these classes can be correctly loaded.

1. Open the Management Console of Websphere Application Server.
2. ClickEnvironmentAnd then clickShared LibraryAnd then clickWpslib.
3. Add your jar fileClasspath.
4. ClickOK.
5. ClickSaveTo save the changes to the master configuration.
6. Restart the websphere_portal application server.

Struts Portlet from IBM Workplace solutions catalog in http://catalog.lotus.com/wps/portal/workplace is not imported to WebSphere Studio Application Developer

The new struts Portlet framework war file is available from IBM Workplace solutions catalog (http://catalog.lotus.com/wps/portal/portalworkplace,navcode:
1wp10003n) after the download, it will not be imported to WebSphere Studio application developer. This is because these war files contain two META-INF directories: one in lower case and the other in upper case. These two directories will cause WebSphere Studio to fail during the import.

Solution:This issue will be resolved in the next release of the struts portal framework. As a work und, you can expand the war and select "import" under "file system" to import each file.

When a war file is imported to rational application developer 6.0, an exception that is hard to solve occurs in the operating system console.

When usingWar import wizardWhen you import a war file to rational application developer (RAD) 6.0, the following unsolvable exceptions may occur in the operating system console, rather than 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.xmlat com.ibm.etools.j2ee.commonarchivecore.util.ArchiveUtil.getRoot(Unknown Source)...

Solution:This is a rad 6.0 issue and has been corrected in Rad 6.0.0.1. Rad updates may be on the following product homepage: http://www-128.ibm.com/?works/rational/products/rad /.