Portal Projects support WebSphere Portal v5.0.2.2.
When you create JSR 168 portlets using the new portlet wizard, Rational Developer automatically assigns an ID attribute. The ID attribute should be included in the <portlet-app/> element of the portlet.xml file to uniquely identify the portlet to the server. (This attribute corresponds to the UID attribute used by IBM portlet API portlets.)
If you have JSR 168 portlets that do not have an ID attribute on the <portlet-app/> element in the portlet.xml, add the ID attribute with its unique value immediately after importing portlet into workspace. To add the ID attribute, open the portlet deployment descriptor and edit it using the Source view. Do not change the ID value after you have deployed your JSR 168 portlet to a portal server, or after you have used your JSR 168 portlet project in a portal project.
There are limitations on a JSR 168 portlet without an ID attribute:
- If you use a JSR 168 portlet without an ID attribute in a portal project, that portal project cannot be run in Test Environment.
- If you associate two or more JSR168 portlets without an ID attribute to WebSphere Portal 5.1 Test Environment, the Test Environment will fail to start.
- You should not change the project name after you have deployed your JSR 168 portlet to a portal server, or after you have used your JSR 168 portlet project in a portal project.
When running a portlet that contains either a Relational Record List or a Relational Record (SDO), you may see the following error in your server log:
[04/10/07 17:57:27:172 JST] 4942fbd0 SystemOut O java.lang.LinkageError: Class org/eclipse/emf/ecore/EClass violates loader constraints: definition mismatch between parent and child loadersYou can ignore this error.
When you create a cooperative source portlet, you need to add the actionNameParameter and name attributes to the WSDL file manually. For example:
<portlet:action type="standard" name="myActionName" actionNameParameter="ACTION_NAME"/>In this release, portal tool does not generate the caption attribute in the WSDL file. When you use the wire with WebSphere Portal v5.1, you need to specify caption attribute in the WSDL file and caption value in the resource file manually.For example:
<portlet:param name="orderId" partname="order_id" caption="order.id" />For more information, refer to "Developing portlets for cooperation" topic in the WebSphere Portal information center.Note: This has been fixed in V6.0.0.1.
When you use the person tag in an IBM API basic portlet on WebSphere Portal v5.1, you should specify it using the following syntax:
<pa:person value="CN=John Smith,OU=SALES,O=ACME" valueType="LDAPDN" displayName="John Smith" />When you use the person tag in an IBM API Faces portlet on WebSphere Portal v5.1, you should specify it using the following syntax:
Note: This has been fixed in V6.0.0.1. Use the same syntax decribed above for the basic portlet.<pa:person value="CN=John Smith,OU=SALES,O=ACME" />John Smith<pa:person>
The person tag is not supported for JSR 168 portlets.
SAP BAPI and RFM SDO wizard limitation: If you advance past the main and pre/post functions page, and try to return to it after picking a different main function, the Pre/Post mappings page will not work correctly.
Solution: If you need to set new pre- and post-function mappings, you must restart the wizard.
Note: This has been fixed in V6.0.0.1.
Before you test portlets that contain SAP SDO on a Portal server, you must configure the SAP JCo adapter on the WebSphere Portal 5.1 server:
- Download SAP's JCo adapter directory from SAP at SAP Service Marketplace.
- Click Download Software > Download > SAP Connectors > SAP Java Connector. Based on your operating system, select the appropriate file to download. Extract the contents of the ZIP file into a local directory.
- Complete the following steps according to your operating system. Note: <wps_51> refers to the installation directory of WebSphere Portal 5.1 server; for example, C:\WebSphere\PortalServer51TE.
For Windows:
- Copy sapjco.jar and sapjcorfc.dll to <wps_51>\shared\app.
- Copy librfc32.dll to c:\windows\system32\.
- You must restart the WebSphere Portal 5.1 server.
For Linux:
- Copy sapjco.jar and libsapjcorfc.so to <wps_51>\shared\app.
- Add the folder that contains the file librfccm.so to environment variable LD_LIBRARY_PATH.
- You must restart the WebSphere Portal 5.1 server.
When creating a portal project using the New Portal Project wizard, or importing a sample Portal project from the Samples Gallery, broken link warning messages appear in the Problems view.
In this version of Rational Developer, Portal Designer only displays HTML, cHTML, and WML as supported markups. If you have specified other supported markups for a page or label in a project that you import, they are maintained in Rational Developer; however, you cannot change those markups, and they will not be displayed in the Properties view.
In this version of Rational Developer, you can set external URLs only in Portal Designer. If you have internal URLs on the portal server, they will be maintained in an imported project, but you cannot change them. You can only deploy the internal URLs back to the original portal server.
Note: This has been fixed in V6.0.0.1.
In this release of Portal Designer, the Admin and AdminLeftNavigation themes will be displayed in the Outline view. However, these themes are for Portal Administration purposes only, and should not be selected as the default theme for a portal project.
Note: This has been fixed in V6.0.0.1.
Problem: The Rational Developer installation fails to install the WebSphere Portal Test Environment.
Solution: Check the install log and carry out the appropriate measures to rectify the problem.
WebSphere Portal 5.0 Test Environment RD_installdir\runtimes\portal_v50\log\wpsinstalllog.txt where RD_installdir is the directory where you installed Rational Developer.
WebSphere Portal 5.1 Test Environment WP51TE_installdir\PortalServer\log\wpsinstalllog.txt where WP51TE_installdir is the directory where you installed WebSphere Portal v5.1 Test Environment.
If the problem cannot be identified from the log files, then try manually uninstalling the WebSphere Portal Test Environment. Then, reinstall it. For information about uninstalling manually, refer to the Rational Developer Installation Guide.
Problem: You can build portlets for WebSphere Portal V5.0 using Rational Developer. If you apply a WebSphere Portal service to your portal server, you may receive compilation errors while building the portlets. In this case, you must manually update the files required by the compilation.
Solution: To compile portlets correctly, follow these steps:
WebSphere Portal v5.0.2.x
Note: You must restore these files to their original state before you can uninstall the WebSphere Portal Test Environment. If you do not do this, then the folder "portal_v50_stub" may not be deleted, and you will have to manually delete it.
- Update all files under the following directory by copying the latest versions from the WebSphere Portal 5.0.2.x PortalServer\*.* directory.
- WS_installdir\runtimes\portal_v50_stub\*.* where WS_installdir is the directory where you installed Rational Developer.
- To debug the portlets, make sure that you have also applied the service to the WebSphere Portal Test Environment. You must apply the service to the WebSphere Portal V5.0.2.x WS_installdir\runtimes\portal_v50 directory.
WebSphere Portal v5.1
Note: You must restore these files to their original state before you can uninstall the WebSphere Portal Test Environment. If you do not do this, then the folder "portal_v51_stub" may not be deleted, and you will have to manually delete it.
- Apply the service to the WebSphere Portal v5.1 Test Environment by following the service's instructions.
- Update all files under the following directory by copying the latest versions from WebSphere Portal 5.1 Test Environment PortalServer\*.* directory.
- RD_installdir\runtimes\portal_v51_stub\*.* where RD_installdir is the directory where you have installed Rational Developer.
The Portlet Deployment Descriptor editor and the Project Explorer view show the portlet icons and their name. The icons indicate the state of the portlets. The portlet states are normal, source enabled, target enabled, and source and target both enabled.
Problem: When you convert a portlet to a Click-to-Action source portlet, only the converted portlet icon should be changed. However, there are cases when more than one portlet icon is changed, such as when multiple portlets are associated with a single servlet. In these cases, icons for portlets other than the intended Click-to-Action portlet icon are incorrectly displayed. The same situation exists when you convert a portlet to a Click-to-Action target portlet.
Solution: More than one portlet icon is changed; however, only one portlet changes. The conversion is successful and the portlet project is not corrupted.
Problem: When you create a new portlet in an existing IBM API portlet project, the following error messages will be displayed if you select the Add Click-to-Action sender portlet sample or Add message sender portlet sample options on the Event Handling page:
- IWAL0008E Incorrect servlet reference for the portlet. (portlet.xml)
- CHKJ4014W: Empty Entry of Type Servlet Name. (web.xml)
Solution: You must re-open the portlet project using the following method:
- Right-click the portlet project and select Close Project from the pop-up menu.
- Right-click the portlet project and select Open Project from the pop-up menu.
- Right-click the portlet project and select Run Validation from the pop-up menu.
Note: This has been fixed in V6.0.0.1.
Problem: The WebSphere Portal Test Environment fails to start.
Solution:
- Verify successful installation: This problem may have occurred because of a failure during installation. Check for problems during the WebSphere Portal Test Environment installation and remedy as required.
- Eliminate excessively long filenames: The server may not start because the portlet project has files with excessively long filenames. To solve this problem, either shorten the project name, the package prefix, and/or the class prefix, so that the generated filename length will be acceptable. Alternately, the individual filenames themselves may be shortened to an acceptable length. Furthermore, if the default directory is used as the workspace, it would also be effective to use a different workspace with a shorter directory name length. You can specify the workspace directory by launching Rational Developer, and change the name in the dialog box provided. If the dialog box to specify the workspace does not appear, go to the command prompt and type -data [workspace_name] after typing the Rational Developer execution command.
Problem: In the WebSphere Portal Test Environment server, installing portlets using the administration portlet fails.
Solution: In the WebSphere Portal Test Environment server, installing portlets using the administration portlet is not supported. To deploy portlets in the WebSphere Portal Test Environment, you must use the "Publish" function in Rational Developer. To use the "Publish" function, right-click the portlet application project and select Run > Run on Server, or right-click the server in the servers view and select Publish.
Problem: An error may occur if your portlet application uses database other than CloudscapeTM.
Solution: You must add the JDBC driver to the WebSphere-specific class paths of the WebSphere Portal Test environment. Follow these steps:
- In the Servers view, double-click the WebSphere Portal Test Environment server. The server editor opens.
- At the bottom of the editor, click the Environment tab.
- In the ws.ext.dirs section, add the JDBC driver. For example, add SQLLIB\java12\db2java.zip file for DB2, where SQLLIB is the directory where you installed DB2.
- Press Ctrl+S to save your changes.
Problem: In the JSR 168 Portlet Deployment Descriptor, you cannot edit a portlet name in the Portlet Collections area.
Solution: Edit the portlet name in the Source page.
Problem: On some configurations using WebSphere Portal v5.0, changes made to a portal or portlet project do not show up automatically in the browser when running or debugging the project using a Remote Server Attach server.
Solution: There are two ways to deal with this:
- Explicitly log out of WebSphere Portal using the browser and log back in. After the login, the changes will be shown. Note that closing the browser window will not work and needs to be performed every time an updated portal project is published.
- Alternatively, configure Rational Developer to use an external browser. To do this, select Preferences... from the Window menu. Expand the Internet node on the left and select Web Browser. In the main section select any browser except Internal Web Browser.
Then, before each Run or Debug On Server, you need to close the external browser prior to performing the operation.
Problem: If you delete the <f:view> tag from a wizard-generated Faces JSP file and insert Faces components in the file, a <f:subview> tag is inserted instead of a <f:view> tag. With this type of JSP file, the Faces portlet will not run correctly. Inputs on the browser are lost in the server-side processing.
Problem: To fix this problem, replace the <f:subview> tag with the <f:view> tag in the JSP file.
If you maximize a Faces portlet that contains Click-to-Action tags, the contents of the portlet does not show.
Note: This has been fixed in V6.0.0.1.
Problem: Changing the Portlet API level fails if the length of the class path is long.
Solution: You need to correct the Java Build Path of the migrated portlet projects. For the required Java Build Path, you can refer to a basic portlet project that is generated by the New Portlet Project wizard. Add the missing required JAR files to the Java Build Path of your migrated portlet project.
Problem: If the Portal UTE is not installed, you cannot create a Portal Import, Export & Deploy server that targets "localhost" or "127.0.0.1".
Solution: If you need to create such a server, then use the fully qualified name of the machine instead of "localhost" (example: myhost.mydomain).
Note: This has been fixed in V6.0.0.1.
Problem: If you cancel the import of a new portal project before it is complete, the incomplete portal project is not removed and becomes unavailable.
Solution: You need to import the portal configuration and files again using the Delete on overwrite option in the Import Portal wizard.
Note: This has been fixed in V6.0.0.1.
Problem: When importing an existing portal site from WebSphere Portal to Rational Developer, validation errors related to WSRP show up in the Problems view against the imported portal project.
Solution: Apply the APAR PQ95638 to WebSphere Portal before importing to Rational Developer.
Note: This has been fixed for WP5.1, but not fixed for WP5.0.
Problem: Can not open license.html or privacy.html files in an imported portal project using Page Designer due to incorrect encoding.
Solution: Apply APAR PQ93681 to your Portal server, then re-import the project from the Portal server.
Note: This has been fixed for WP5.1, but not fixed for WP5.0.
Problem: The WebSphere Portal 5.0 Test Environment fails to start when you try to do following:
- Start the test environment with a portal project that has no portlet projects associated with it, then
- Add portlet projects to the portal project and try run that portal project in the test environment again.
Solution: You need to re-configure the WebSphere Portal 5.0 Test Environment.
You should now be able to run your portal project and its newly associated portlet projects in the test environment.
- In the Servers view, right-click the server and select "Add and remove projects...".
- Remove the "wps" project from "Configured projects".
- Right-click the portal project and select Run > Run on Server.
Note: This has been fixed in V6.0.0.1.
The "Add SDO runtime" references Rational Application Developer newsgroups. The forum for Rational Application Developer is available from the IBM developerWorks site (www.ibm.com/developerworks/forums/dw_forum.jsp?forum=430&cat=24&hideBody=true).
Return to the main readme file