|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
|
Previous |
Next |
This chapter describes issues with Oracle Application Server Portal. It includes the following topics:
This section describes upgrade related issues and their workarounds:
When you upgrade from OracleAS Portal 9.0.4, you may see the following errors after upgrading the middle-tier to 10.1.2, but before upgrading the OracleAS Portal repository:
Error: General invalidation message processing exception: An error occurred while closing the HTTP connection after receiving an error while getting the invalidation response from Web Cache ORA-29273: HTTP request failed ORA-06512: at "SYS.UTL_HTTP", line 1380 ORA-29261: bad argument ORA-29273: HTTP request failed ORA-06512: at "SYS.UTL_HTTP", line 1222 ORA-12547: TNS:lost contact (WWC-40018) ORA-29259: end-of-input reached
This problem occurs more frequently when OracleAS Web Cache runs in a Linux environment. Once the OracleAS Portal repository is upgraded to 10.1.2, this problem no longer occurs. As a workaround, if you do not want to upgrade the OracleAS Portal repository to 10.1.2 immediately, you must update it to 9.0.4.1 by following the instructions in the Oracle Application Server 10g (9.0.4) Patch Set 1 (9.0.4.1.0) Patch Set Notes:
For OracleAS Portal repositories residing in an OracleAS Metadata Repository, refer to the Metadata Repository Update section.
For OracleAS Portal repositories residing outside an OracleAS Metadata Repository, refer to the Manual OracleAS Portal Repository Update section.
It is desired behavior for all components to be functional post-upgrade if they are configured in the destination installation, even if they were not configured in the source installation. However, the OracleAS Portal component will only be functional once the middle-tier upgrade is completed if the component was configured both in the source and in the destination middle-tier installations.
The OracleAS Portal Patch Configuration Assistant may fail to complete successfully during an OracleAS Infrastructure upgrade to 10g Release 2 (10.1.2) when the OracleAS Metadata Repository contains a Virtual Private Portal. If this happens, examine the installation log file and compare your error stack with the one in Bug 4076643 and apply the corresponding patch if they match.
If, after upgrading, your OmniPortlet, Web Clipping, Simple Parameter Forms, and JPDK Web Cache sample portlets are not updated or fail to display properly, you can search the application.log file for the following error message:
Bad "authorization" value in configuration element "invalidation."
When you upgrade from OracleAS Portal 9.0.2.6 to OracleAS Portal 10.1.2, the ORACLE_HOME/portal/conf/cache.xml file is copied to the 10.1.2 middle-tier without obfuscating the username and password, which can cause Web Cache invalidation errors. The copied cache.xml file looks similar to this:
<?xml version="1.0">
<webcache>
<invalidation
host=cache.mycompany.com
port=4001
authorization="invalidator:welcome"/>
</webcache>
As a workaround, perform the following steps:
Convert the username and password into an obfuscated string in the format required by the JAWC API, using the oracle.webdb.provider.v2.cache.Obfuscate Java utility. For example, if the invalidation port username is "invalidator" and the password is "welcome," you must run the following command:
ORACLE_HOME\jdk\bin\java -classpath ORACLE_HOME\portal\jlib\pdkjava.jar oracle.webdb.provider.v2.cache.Obfuscate invalidator:welcome
If successful, the command prints a hexadecimal string such as the following:
0510198d5df8efd5779406342be2528aa0cccb179ea6b77baf49f019f5075a3a11
Append the hexadecimal string to the authorization attribute, replacing the <username>:<password> value, in your JAWC configuration file, cache.xml. For example:
<?xml version="1.0">
<webcache>
<invalidation
host=cache.mycompany.com
port=4001
authorization=
"0510198d5df8efd5779406342be2528aa0cccb179ea6b77baf49f019f5075a3a11"/>
</webcache>
This section describes UI related issues and their workarounds for OracleAS Portal:
When you add a region to a page displayed in a generic page portlet, the new region is not displayed immediately as expected. As a workaround, manually invalidate the cache by clicking the Clear Cache link (Access tab) for the page containing the generic page portlet.
If a page displays a page portlet (Portlet A) with a sub-page link to a page with tabs and portlets (Portlet B), the portlets under tabs in Portlet B are not displayed if you use the sub-page link to navigate to Portlet B, from Portlet A. This is a known issue.
If you use the List View to set access privileges for one or more pages, privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the sub-page.
This section describes issues related to OmniPortlet, Web Clipping, and Simple Parameter Form. These portlets are located in the Portlet Repository as follows: Portlet Repository: Portlet Builders.
Section 8.3.2, "Error Exporting and Importing OmniPortlet and Web Clipping Customizations"
Section 8.3.3, "OmniPortlet Error After Middle-Tier Cloning"
To edit OmniPortlet, Web Clipping, or Simple Parameter Form portlets, that is, set properties in Edit Defaults mode, you must use the following browser versions:
Netscape 7.0 or higher
Microsoft Internet Explorer 5.5 or higher for Windows 2000
Microsoft Internet Explorer 6.0 for Windows XP
If you use browser versions older than these, you may encounter JavaScript errors.
During the import or export of OmniPortlet or Web Clipping provider customizations, an error message similar to the following may display:
[Warning: (WWU-74505)] context = Import of one of the web provider customization failed user = PORTAL An error occurred importing data to the web provider OMNIPORTLET.
As a workaround, refresh the OmniPortlet and Web Clipping providers in the portlet repository on both the source and the target portals before export.
After middle-tier cloning, some of your OmniPortlet instances may display errors such as:
Check the following: is the URL is active; is there a valid proxy setting or, if HTTP authentication is required, check user name and password. [http://<host>:<port>/portalTools/webClipping/webData/ omniPortlet/wcserver/jsp/show.jsp?...]
where <host> and <port> refer to the old middle-tier host and port.
These errors indicate that the OmniPortlet instance is using a Web Page Data Source and the connection between the OmniPortlet and the Web Page Data Source is lost. This is because, after middle-tier cloning, the OmniPortlet instance on the new middle-tier is still using a URL on the old middle-tier. To fix this problem, edit each OmniPortlet instance for which you see this error as follows:
Access the Portal page containing the OmniPortlet instance.
Click the Edit Defaults icon for the portlet. Typically, a Page Designer has these permissions.
Click Select Web Page to display the home page of the Web Clipping Studio.
Without doing anything else, click OK to return to the Edit Defaults mode for the OmniPortlet.
Click OK again to exit the Edit Defaults mode.
For OmniPortlet instances with customizations, perform the following additional steps:
Click the Customize link for the portlet (in View mode). Typically a Page Viewer has these permissions.
Copy all the values (parameter values or title) that are customized and save them (in a text editor).
Click Reset to Defaults to synchronize the customized data with the Edit Defaults data. The corrections made previously are mirrored in the customized data.
Click the Customize link and enter the custom values (saved in step 2), and click OK.
Oracle Application Server Portal Developer Kit (PDK) version 10.1.2 is included with a Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at these middle-tier ORACLE_HOME locations:
PDK-Java: ORACLE_HOME/portal/pdkjava/v2/pdkjava.v2.releasenotes.html
PDK-PL/SQL: ORACLE_HOME/portal/pdkjava/v2/pdkplsql.release.notes.html
Latest Version of OracleAS PDK
New versions of the OracleAS PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/portal/pdk.html.
Release notes for the latest OracleAS PDK version are available on Oracle Application Server Portal on OTN and also in these PDK download locations:
pdk\plsql\pdkplsql.release.notes.html
pdk\jpdk\v2\pdkjava.v2.release.notes.html
This section describes Globalization Support related issues in OracleAS Portal:
Section 8.5.1, "Oracle Text Searching Limitation (Text Files and HTML Files)"
Section 8.5.2, "Text Entry Always Right to Left in BiDi Languages"
Section 8.5.3, "Non-ISO-8859 Web Page Limitation for URL Items"
Section 8.5.5, "Shared Type Objects Cannot Be Exposed in Non-English Page Group"
Section 8.5.6, "Translations Lost When Item Versioning Enabled"
Section 8.5.7, "Broken Links in Greek, German, and Swedish Built-in Database Portlets"
In some non-ASCII character set environments, you are unable to search non-ASCII character content of plain text files and HTML files.
You can search plain text and HTML files if the document character set is the same as the database character set and the database character set is one of the following:
US7ASCII
WE8ISO8859P1
JA16SJIS
KO16KSC5601
ZHS16CGB231280
ZHT16BIG5
If the database character set is none of those listed but the document is in the WE8ISO8859P1 character set, the search feature also works correctly. In any other non-ASCII character set environment, you can encounter this problem.
Note that there are no issues when searching binary files like Word, PDF, and so on.
The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side 'Ctrl' and 'Shift' keys.
You may not be able to display a Non-ISO-8859-1 Web page using a URL item. Other portlets offer this functionality, so you may want to use one of these instead, that is portlets such as Globalization Support URL Service and Web Clipping.
Non-ASCII XML data is not displayed correctly in the XML Portlet. To display non-ASCII XML data, use OmniPortlet, which has this functionality.
Non-ASCII data from a specified URL is not displayed correctly in the URL Portlet. To display such data in a portlet, use the Web Clipping portlet, which has this functionality.
If you use non-ASCII characters in Web Provider Display Names, they are not displayed correctly. Similarly non-ASCII characters used in Provider Group Display Names cannot be displayed.
You may not use non-ASCII characters in the Name for portlets of Database Providers. However, you can use such characters in the Display Name.
If a portlet name contains non-ASCII characters, the name does not display correctly when the portlet is previewed.
If you use non-ASCII characters when changing folder names using Web Folders, an error message is displayed.
Shared type objects (page types, item types) always have English as the default language. If you create a page group in a language other than English, a shared type cannot be made available to the page group unless a translation exists for the shared type in the default language of the page group.
To create the translation, follow these steps:
Enable the language for the Shared Objects page group.
For details, see Oracle Application Server Portal User's Guide - Section 4.6.1 Creating a Translation.
Switch to the language in the Set Language portlet.
Edit the page type or item type while the session language is set to the non-English language.
This automatically creates a translation of the type in that language.
You can now make the shared type available to the non-English page group.
If versioning is enabled and the page group has two or more translations (for example the default language is English and translations are enabled for German and French), adding a translation as a new version does not display the other translation. For example, if you add or edit a French translation as a new version, the German translation is no longer visible to the page viewers. As a workaround, when multiple translations are required, disable item versioning, or use the "overwrite" mode when adding or updating translations.
The portlets "Database Information," "Database Memory Consumption, Transactions and Locks," and "Database Storage," contain links for generating database reports. These links do not work if the language is set to Greek, German, and Swedish. As a workaround, switch to another language (such as English) to access these reports.
This section describes known errors and omissions in OracleAS Portal documentation:
This section describes known errors in OracleAS Portal documentation. It includes the following topics:
Section 8.6.1.3, "Referencing the Current Version of Images"
Section 8.6.1.5, "Unpublished Items Section Documented Incorrectly"
Section 8.6.1.8, "Defining a Display Style for Results from a Custom Search"
Section 8.6.1.9, "Applying Background Color or Image to Page Portlets"
Section 8.6.1.10, "Incomplete Steps for Securing OracleAS Web Cache"
The online help states that clicking the Edit icon enables you to edit the properties of the item or portlet. While this is true for items, clicking this icon next to a portlet takes you to the Edit Defaults page. To edit the portlet instance attributes (such as display name), click the Actions icon, then click the Edit Portlet Instance link.
Online help for Pending Items: Preview (cawkpend.htm) incorrectly states that the submitter can continue to edit a pending item if it has not yet been approved by the first approver in the approval process.
Image attributes can reference an uploaded source image. The documentation currently states:
To reuse an image that has been uploaded to OracleAS Portal, enter its internal name (not file name) without a path in this field, for example, enter 1645.GIF.
If you are versioning the referenced image item, and you use the internal filename in the reference (for example, 1645.gif), the reference does not use a new, current version of the image if one is created. The image reference continues to show the original version. For example:
In an image attribute, reference an image item by its internal file name, for example, 1645.gif.
Update the image item and create a new version. The new version is given a new internal file name (for example, 1705.gif).
The image attribute still refers to 1645.gif, it has not been updated to refer to the new version of the image.
Therefore, only use the internal filename if you are not using versioning, or if you want the reference to always point to the original version, even if it is no longer the current version.
If you are using versioning and you always want to show the current version, use the durable link to the image item instead of the internal filename. The durable link always picks up the latest version of the image. So, instead of entering 1645.gif, enter:
/pls/<DAD>/url/item/<GUID>
This is the relative URL format of a durable link. For example:
/pls/portal/url/ITEM/A47D41ECA23648A9E030007F0100118A
Relative URLs should always be used in case the host or domain name changes, or the content is exported to another site. For more information on durable URLs, refer to Section 1.1.3.1 Understanding Page and Item URLs in the Oracle Application Server Portal User's Guide.
List View functionality is documented in the online help topic Page Edit Mode: List View (pobpglst.htm). Some information in this topic is incorrect:
Button: Actions List - Options Enable ILS and Disable ILS are not available.
Button: Find - The search is not case-sensitive.
Sub-items - The online help states that the List View does not display sub-items. This is correct, however, sub-items will be listed in search results if they meet the search criteria.
Also, note that in List View, pages based on templates do not show any tabs or items belonging to the template. You must click the Edit Template link to see tabs and items on a template. Therefore, when editing the page in List View, you cannot add items to tabs that are inherited from the template. Likewise, if items are added to these tabs when editing the page using another edit view (for example, Graphical View), you do not see these items in List View.
If you are using Netscape 4.8, you may notice that version information is incorrectly displayed under the Description column. This is not a problem in Internet Explorer.
Online help for the Edit Page Group Items tab (sbrsmit.htm) incorrectly refers to the Expired and Deleted Items section and the Display Expired and Deleted Items and Retain Expired and Deleted Items check boxes. These should be, respectively, the Unpublished Items section and the Display Unpublished Items In Edit Mode and Retain Deleted Items check boxes. Refer to the text on the page itself for details on how to use these check boxes.
The online help incorrectly states that when item level security (ILS) is enabled, page caching is automatically disabled. Page caching is not disabled when ILS is enabled.
Online help for the Edit Portal User Profile tabs, Preferences (secumed1.htm) and Privileges (secgmed3.htm) incorrectly states that there are Reset to Defaults buttons on these pages. This option is not available.
Online help for Edit Defaults: Custom Search - Results Display page (sbrrsres.htm) incorrectly states that style and attribute settings apply only to items returned in search results. The Style and Attribute settings (section Which style and attributes should be used to render the search results?) apply to both items and pages.
If you want page portlets (including navigation pages) to display a background color or background image, follow these steps:
Ensure that the navigation page uses its own style when published as a portlet, that is, do not select Use Style Of Page On Which Portlet Is Placed in the page properties.
In the style for the container page (the page containing the portlet), set Portlet Body Color to null (no value). This step is missing from the documentation.
In section 6.3.2.1.4, "SSL Throughout OracleAS Portal" of the Oracle Application Server Portal Configuration Guide, the following procedure is missing after "Adding Site to Server Mappings of the New Site to the Origin Server" (page 6-73).
Adding Wallet Path for the Origin Server Wallet
You must enter the wallet path in the Origin Server Wallet page:
From the OracleAS Web Cache Administration page, click Origin Server Wallet under Origin Servers, Sites, and Load Balancing.
Select the radio button for the Cache Name to change its wallet path.
Click Edit Selected to display the Edit Origin Server Wallet dialog window.
Enter a valid Wallet Directory. For example, use the wallet directory path specified on the Listen Ports page.
Click Submit to close the dialog window. The new wallet directory path is displayed in the table on the Origin Server Wallet page.
This section describes known omissions and additions to the OracleAS Portal documentation. It includes the following topics:
Section 8.6.2.2, "Expired Items Remain Visible in WebDAV Clients"
Section 8.6.2.4, "Using a Xythos WebFile Client for OracleAS Portal"
Section 8.6.2.6, "Error Removing Subscriber from Virtual Private Portal"
Section 8.6.2.7, "Page Metadata Not Cached in OracleAS Web Cache"
Online help describing Log Registry records (wvlogadm.htm) lists the set of actions that are logged. Since the introduction of OracleAS Web Cache, some of the actions logged in OracleAS Portal Activity Log tables have become inaccurate. Specifically, these actions are View, Execute, Show, and Perform. However, since all other actions logged are still accurate, the Activity Log tables and views still remain in the OracleAS Portal Metadata Repository.
Expired items continue to be visible in WebDAV clients until they are permanently removed from the database during a system purge.
The Rich Text Editor (WYSIWIG editor) that is used in OracleAS Portal to apply formatting to text items is described in a Technical Note OracleAS Portal 9.0.4.1 – Enhanced Rich Text Editor on OTN at http://www.oracle.com/technology/products/ias/portal/content_management.html.
OracleAS Portal supports the Xythos WebFile Client (a WebDAV partner). To learn more about the features and benefits of this integration, see the WebFile Client for OracleAS Portal Data Sheet hosted on the Xythos Web site. For more information, read the Technical Note How to Install and Configure Xythos WebFile Client for OracleAS Portal on OTN at http://www.oracle.com/technology/products/ias/portal/content_management.html.
You cannot delete a tab on a template (even with Manage Template privileges), if other users have placed content on the tab, in pages that are based on this template.
The following error can display when you use the rmsub.csh script to remove a subscriber from a Virtual Private Portal (VPP):
ERROR: Interface Version Specified does not match Profile Interface Version - 1.1 Could not delete Provisioning Profile.
This error does not impact the use of VPP.
If page metadata is not cached in OracleAS Web Cache, it may be because the initial, one-time call from the middle-tier to the OracleAS Portal schema to determine the OracleAS Portal version failed. To resolve this problem, perform the following actions:
Confirm that page metadata is not cached in OracleAS Web Cache by appending _debug=1 to a page URL, refreshing the browser, and verifying that the OracleAS Web Cache page metadata cache status is 'MISS,NON-CACHEABLE'.
Alternately, view the Popular Requests screen in OracleAS Web Cache Manager and verify that page metadata is not cached.
Restart all OC4J_Portal instances.
Perform step 1 again to determine if page metadata is now cached in OracleAS Web Cache.
If the caching problem has not been resolved, perform the actions for error message WWC-40018, as described in the Oracle Application Server Portal Error Messages Guide.
