Portal tools - release notes


1.0 Supported software and specifications
2.0 Limitations
   2.1 JSR 168 portlets should have ID attribute
   2.2 Relational Records and Portal V5.1
   2.3 Cooperative portlet limitation
   2.4 Person tag limitation
   2.5 EIS tools limitations
   2.6 Configuring SAP JCo on a WebSphere Portal server
   2.7 Cooperative portlet limitation on RedHat Enterprise Linux 3.0
   2.8 Broken link warning messages are shown in the Problems view
   2.9 Markup support in Portal Designer
   2.10 Internal URL cannot be set
   2.11 Do not select Admin themes as default
3.0 Known problems
   3.1 (Creating portlets) Incorrect servlet reference error when creating a portlet in an existing IBM API portlet project
   3.2 (Debugging and testing portlets) Cannot start the WebSphere Portal Test Environment
   3.3 (Portlet deployment descriptor) Editing with the JSR 168 Portlet Deployment Descriptor editor
   3.4 When <f:subview> is used instead of <f:view>, Faces portlets do not work correctly.
   3.5 Click-to-Action does not work in a Faces portlet that is maximized.
   3.6 (Importing, Exporting & Deploying) Cannot create Import, Export & Deploy server that targets "localhost"
   3.7 (Importing portal) Cancelling the import operation causes the new portal project to be unavailable
   3.8 (Importing portal) WSRP related errors are shown in the Problems view of an imported portal project
   3.9 (Customizing portals) Can not open license.html and privacy.html files in an imported portal project
   3.10 The newsgroup (forum) for Rational Software Architect

1.0 Supported software and specifications

Portal Projects support WebSphere Portal v5.0.2.2.

2.0 Limitations

2.1 JSR 168 portlets should have ID attribute

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:

2.2 Relational Records and Portal V5.1

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 loaders
You can ignore this error.

2.3 Cooperative portlet limitation

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.

2.4 Person tag limitation

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:

<pa:person value="CN=John Smith,OU=SALES,O=ACME" />John Smith<pa:person>

The person tag is not supported for JSR 168 portlets.

2.5 EIS tools limitations

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.

2.6 Configuring SAP JCo on a WebSphere Portal server

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:

  1. Download SAP's JCo adapter directory from SAP at SAP Service Marketplace.
  2. 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.
  3. 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:
    1. Copy sapjco.jar and sapjcorfc.dll to <wps_51>\shared\app.
    2. Copy librfc32.dll to c:\windows\system32\.
    3. You must restart the WebSphere Portal 5.1 server.

      For Linux:
    1. Copy sapjco.jar and libsapjcorfc.so to <wps_51>\shared\app.
    2. Add the folder that contains the file librfccm.so to environment variable LD_LIBRARY_PATH.
    3. You must restart the WebSphere Portal 5.1 server.

2.7 Cooperative portlet limitation on RedHat Enterprise Linux 3.0

Cooperative portlets are not supported by the Rational Developer internal browser for RedHat Enterprise Linux 3.0. If you need to use cooperative portlets in RedHat Enterprise Linux 3.0, use Netscape Communicator.

To use Netscape Communicator as the default browser, configure Rational Developer to use an external browser. To do this, select Window > Preferences from the menu bar. Expand the Internet node on the left, and select Web Browser. In the main section, select any browser but Internal Web Browser.

For more information, refer to the "Known issues and restrictions with cooperative portlets" topic in the WebSphere Portal information center.

2.8 Broken link warning messages are shown in the Problems view

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.

2.9 Markup support in Portal Designer

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.

2.10 Internal URL cannot be set

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.

2.11 Do not select Admin themes as default

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.

3.0 Known problems

3.1 (Creating portlets) Incorrect servlet reference error when creating a portlet in an existing IBM API portlet project

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:

Solution: You must re-open the portlet project using the following method:

  1. Right-click the portlet project and select Close Project from the pop-up menu.
  2. Right-click the portlet project and select Open Project from the pop-up menu.
  3. Right-click the portlet project and select Run Validation from the pop-up menu.

3.2 (Debugging and testing portlets) Cannot start the WebSphere Portal Test Environment

Problem: The WebSphere Portal Test Environment fails to start.

Solution:

3.3 (Portlet deployment descriptor) Editing with the JSR 168 Portlet Deployment Descriptor editor

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.

3.4 When <f:subview> is used instead of <f:view>, Faces portlets do not work correctly.

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.

3.5 Click-to-Action does not work in a Faces portlet that is maximized.

If you maximize a Faces portlet that contains Click-to-Action tags, the contents of the portlet does not show.

3.6 (Importing, Exporting & Deploying) Cannot create Import, Export & Deploy server that targets "localhost"

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).

3.7 (Importing portal) Cancelling the import operation causes the new portal project to be unavailable

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.

3.8 (Importing portal) WSRP related errors are shown in the Problems view of an imported portal project

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.

3.9 (Customizing portals) Can not open license.html and privacy.html files in an imported portal project

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.

3.10 The newsgroup (forum) for Rational Software Architect

The "Add SDO runtime" references Rational Software Architect newsgroups. The Rational Software Architect support site (www.ibm.com/software/awdtools/developer/application/support) will be updated to include the link to the newsgroups.

Return to the main readme file