10g (9.0.4) for Linux x86
Part Number B12261-03
 Home |
 Contents |
| Oracle® Application Server 10g Release Notes 10g (9.0.4) for Linux x86 Part Number B12261-03 |
|
This chapter describes with OracleAS Portal. It includes the following topics:
This section describes UI related issues and their workarounds for OracleAS Portal:
This problem occurs when using the Rich Text Editor in Internet Explorer only. If you create a Text item containing a relative link, it is converted to an absolute link. This causes problems if your content is to be exported to another site. For example:
<IMG SRC="/images/home.gif" ALT="Home" BORDER=0>
Note that the base has been added to the URL, e.g. <IMG alt=Home src="http://webserver.us.abc.com:5000/images/home.gif" border=0>.
One workaround is to disable the Rich Text Editor. For details, see Oracle Application Server Portal User's Guide. Alternatively, apply the patch to Bug 3009204 (available on the Oracle MetaLink Web site at http://metalink.oracle.com). This patch provides a script that parses text items and converts absolute URLs to relative URLs.
If you are unable to add portlets to a page, it may be due to a provider registration issue. You will not receive an error message if you register a provider that has two portlets with the same portlet ID, portlets with no names, or portlets with no IDs. However, in all these cases you are not able to add portlets from that provider onto pages, and so on.
If you previously upgraded to Oracle9iAS Portal 9.0.2.6 using version 1, 2, or 3 of the Oracle9iAS Portal 9.0.2.6 repository upgrade patch #2981297, and then upgraded to OracleAS Portal 10g (9.0.4), you may encounter a problem where you have two perspective page templates. This problem occurs if you previously upgraded to Oracle9iAS Portal 9.0.2.6, and then created additional perspectives in a page group that contained upgraded perspectives.
If you find that one or more of your upgraded page groups contains two perspective page templates, follow these steps for each affected page group:
For information about these scripts, refer to Oracle Application Server Portal Configuration Guide.
The values of custom attributes revert to their default values when a new version is created in the following situations:
This section describes issues relating to OmniPortlet, Web Clipping and Simple Parameter Form. These portlets are located in the Portlet Repository as follows: Portlet Repository: Portlet Builders.
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:
If you use browser versions older than these, you may encounter JavaScript errors.
If you want to use parameters and events with OmniPortlet, you must first refresh the OmniPortlet provider. To do this, follow these steps:
The News Layout Scroll type in OmniPortlet is supported on Microsoft Internet Explorer and Netscape 7.0. It does not work with Netscape 4.79.
If numeric values in a data source contain formatted strings, commas or currency (e.g. $32,789.00), they are considered to be text and ignored when the chart is generated. As a workaround, remove formatting characters from numerical values.
This section describes issues relating to the search functionality in OracleAS Portal.
These errors are displayed on pages containing search portlets or Basic Search Box items, if the page group of an associated search results page is deleted:
Error: An unexpected error has occurred (WWS-32100) ... The Page Group ID does not exist. (WWS-30641)
Also, you are unable to access the Search Settings page to choose a new search results page. (The Search Settings page is accessible from the Services portlet which is on the Portal sub-tab of the Administer tab on the Portal Builder page.)
To resolve this issue, follow the instructions published in Bug 3263977 (available on the Oracle MetaLink Web site at http://metalink.oracle.com).
You can build a custom search form (using the Custom Search portlet) that lets the user Set the maximum number of results. In this release, this option does not restrict the total number of results returned.
However, if you allow users to Set the number of results per page they can restrict how many results appear on each page.
In Netscape 4.79 you may experience problems saving search results, if your search is based on more than one search term separated by spaces, for example, sales targets. This error is displayed: The request had invalid syntax.
The Custom Search portlet allows you to choose which attributes are displayed with search results. However, some of the available attributes which are listed do not get displayed with search results as expected, that is Base Item Type, Display Parameter Form, Enable Item Check-Out, Link That Displays Item In New Browser Window, Oracle Reports Components, Rollover Image, Item Content, Portlet Content, Portlet Instance Global Unique Id, Provider Name, Updated Item Indicator, New Item Indicator.
If Oracle Text is enabled you can restrict search results by one or more perspective. If Oracle Text is disabled you can restrict search results by a single perspective only. If you restrict your search results by perspective and then switch between Oracle Text being on then off (or off then on), perspective selection may not be as expected.
Search functionality is designed such that one search portlet maps to a single page. Therefore, if you choose to display search results on a page that contains multiple search portlets (Basic, Advanced, Custom or Ultra Search portlets) you will notice that all search portlets on the results page respond, i.e. search results are displayed in every search portlet. To avoid this behavior it is recommended that you display search results on pages that contain a single search portlet.
Similarly, when an Ultra Search portlet returns results, any other search portlets placed on the same page will respond. Therefore, do not place additional search portlets on a page that contain an Ultra Search portlet.
(Oracle Text enabled only.) If you promote a perspective to Shared Objects and then search for items in that perspective, the items are not returned. As a workaround, drop and recreate your Oracle Text indexes after promoting the perspectives. For more information, refer to Oracle Application Server Portal Configuration Guide.
Search functionality can become inconsistent if the search criteria includes a large number of attributes and/or the user chooses a long list of page groups to search. This problem is due to URL size constraints. Here are examples of issues that can occur:
The workaround is to reduce the number of attributes and/or page groups available for user selection.
Oracle Application Server Portal Developer Kit (PDK) version 9.0.4 is included with an OracleAS Portal & Wireless install. Release notes for the JPDK and PL/SQL PDK can be found at these mid-tier $ORACLE_HOME locations:
New versions of the OracleAS PDK are released periodically providing new includes, new API's and additional documentation. To take advantage of all the latest includes, download the latest PDK from Portal Center, http://portalcenter.oracle.com.
Release notes for the latest OracleAS PDK version are available on Portal Center and also at these PDK download locations:
This section describes National Language Support (NLS) related issues in OracleAS Portal:
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:
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.
Header images and some buttons are not aligned properly, due to a Mozilla issue.
When you create an Excel/sylk formatted report, the file encoding is always the same as the database character set. You may not be able to open the file in Microsoft Excel like this. As a workaround, convert the exported files into native encoding.
For example, if the database character set is UTF8, Excel can not open exported reports as they are encoded by the UTF8 database character set. On a Japanese Windows system, Excel can open Shift_JIS encoded files only but to export files in Shift_JIS, the database character set must be JA16SJIS. So, if the database character set is EUC (another Japanese standard character set) or UTF8, the files will not open. You can use Notepad to open and save files in different character sets.
You cannot use a double byte space character to separate two search keywords. You must use a single byte space character.
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 NLS URL Service and Web Clipping.
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:
For details, see Oracle Application Server Portal User's Guide - Section 4.6.1 Creating a Translation.
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.
The Oracle Ultra Search portlet help page is garbled in all languages. To view this problem:
To work around the problem, change the encoding to UTF8 in the appropriate help file in:
ORACLE_HOME/j2ee/OC4J_Portal/applications/UltrasearchPortlet/query/html
This section describes known administration issues for OracleAS Portal:
If the instance name contains any characters other than alphanumeric characters, that is, if the instance name does not consist of letters and numbers only, the Portal Service Monitoring link from Portal Adminster page does not function properly. From the Portal Administer page when you click on Portal Service Monitoring link, a new popup window is displayed with a null instance name and most of the instances are displayed with a status of down. This issue is applicable to Portal and Wireless or Business Intelligence and Forms installation types. To avoid this issue, make sure the instance name contains only alphanumberic characters. If an instance name with special characters is required, do not navigate to the Portal Monitoring section from the Portal Administer page. Instead, navigate to the middle tier Application Server Control page and access Portal from there.
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:
The online help states that clicking the Edit icon allows 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 hasn't 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 (e.g. 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:
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 can not 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 (e.g., 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:
The Web Cache connection error message WWC-40018 was incorrectly listed as WWC-40019 in the Oracle Application Server Portal Error Messages Guide.
This section describes known omissions and additions to the OracleAS Portal documentation. It includes the following topics:
PUBLIC users are unable to search for items on pages where item level security is enabled.
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.
When you create/register a new provider, a page is created in the Portlet Repository under Portlet Staging Area to display portlets for that provider. This page is not visible to all logged in users. It is only visible to the user who published the provider and portal administrator. The publisher or portal administrator can change the provider page properties to grant privileges to appropriate users/groups, as required.
It is recommended that you name custom attributes such that they are unique across page groups. For example, you could include the page group name as a prefix or suffix.
If custom attributes do not have unique names, they appear duplicated when choosing search result attributes. For example, if they are both named 'MyCustomAttribute1' they are listed as:
MyCustomAttribute1 MyCustomAttribute1
This way, it is not possible to establish which attribute belongs to which page group. However, if you name them 'MyCustomAttribute_PG1' and 'MyCustomAttribute_PG2' they can be identified by their unique names:
MyCustomAttribute_PG1 MyCustomAttribute_PG2
Expired items continue to be visible in WebDAV clients until they are permanently removed from the database during a system purge.
You can embed a page containing Portal Smart Text or Portal Smart Link items (published as a portlet) in another page. When you do this, the Portal Smart Text/Portal Smart Link items work within the context of the containing page.
For example, if you add the Edit Portal Smart Link item to Page A, publish the page as Portlet A and then place Portlet A on Page B, the Edit link will allow the user to edit Page B.
|
 Copyright © 2003 Oracle. All Rights Reserved. |
|