In the procedure “Building and deploying the address book portlet”:
In step 8, the initial resource should be /index.jsp, not index.jsp.
In step 16, select these values in these fields:
Default Size – Show All
Content Cache Interval – Real Time
Roles – Everyone
You do not need to perform the “Creating a Servlet Alias” procedure. The necessary aliases are created automatically.
The “Customizing personalization.properties” procedure is not needed. There is not a personalization.properties file in this release. Use the PersDBCache connection pool instead.
It is not necessary to restart EAServer during deployment of this Web application.
In “Application files,” Table D-1, the listed files are contained within the addressbook.jar.
In “Implementation Details”:
It tells you to see the JSP portlets documentation in %EASERVER%\Repository\WebApplication\onepage\docs\javadoc\index-all.html for a list of variables that are accessible from pages through the request object, but there is no relevant information in this documentation for the sample.
In “Accessing the database,” the sentence that says “The personalization APIs use a JDBC connection—the data source, user name and password values are saved in the personalization.properties file.” should say: “The personalization APIs use a jdbc/PortalDatabase JNDI lookup for a JDBC resource to retrieve connections to the database.”
The Enterprise Portal Developer’s Guide, section “Selecting a Web Studio left pane menu option” in chapter 1, omits the Manage | Personalize menu option in the Web Studio left pane. However, the Personalize option is documented in Chapter 7, “Personalizing Portal Content” of the Enterprise Portal Developer’s Guide.
[CR #314150] Chapter 9, “Deploying Portal Objects” in the Enterprise Portal Developer’s Guide, in the section “Deploying portal objects to a remote server” describes functionality that is not yet supported. Currently, you can deploy portal objects only when Web Studio and Portal Interface are running in the same application server.
[CR #318393] When you create a co-brand, portal objects must exist in the new resource. A portal must contain at least one guest page that is approved and active.
After you create and approve the co-brand guest page in Web Studio, select Approved from the Status menu, select the guest page you just created, then click Update on the Page Manager toolbar and follow the instructions that display to update Portal Interface with the new page.
[CR #321959] The Developer’s Guide should instruct the user to perform an Update operation in Web Studio after deleting or changing a page in order for the changes to take effect in Portal Interface. If the Update is not performed, the old or deleted pages still display in Portal Interface.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
