| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for AIX Part Number B32414-05 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for AIX Part Number B32414-05 |
|
|
View PDF |
This chapter describes issues associated with Oracle WebCenter Suite. It includes the following topics:
This section describes issues and workarounds related to Oracle WebCenter Suite. This section includes the following topic:
Section 6.1.3, "Standalone OC4J Requires Configuration to Run Java Object Cache"
Section 6.1.4, "Use of Portal Adapter Requires Patch Update"
Section 6.1.5, "JAZN Migration Tool Incorrectly Prefixes ADFRolePrincipal"
Section 6.1.6, "Rich Text Portlet Customization Not Supported in Safari"
Section 6.1.7, "Portlets with ADF Data Binding on the Same Page Cannot Be Customized"
Section 6.1.8, "Issue with SES Securely Crawling Content in Oracle ContentDB"
Section 6.1.9, "Language Setting Issue with the Federated Portal Adapter"
Section 6.1.10, "Using the Search Feature with the File System Adapter"
Section 6.1.15, "Incorrect Query Execution in Oracle WebCenter Adapter for IBM Lotus Domino"
Section 6.1.17, "Testing a JCR SharePoint Repository Connection"
Section 6.1.19, "Log Messages While Starting Preconfigured OC4J"
Section 6.1.20, "Error When Compiling JSP with PDK Struts Components"
If you install Oracle WebCenter Suite 10g (10.1.3.2) on the same host machine as an Oracle database, version 10.1.x or 10.2.x., Oracle Process Manager and Notification Server (OPMN) may consume a significant percentage of the machine's CPU time, and the OPMN log file will rapidly increase in size with messages, such as the following:
06/06/07 06:22:52 [ons-connect] Passive connection 127.0.0.1,6100 missing connect.
To prevent this issue from occurring, you can perform one of two actions:
Install Oracle WebCenter Suite 10g (10.1.3.2) on a different machine than your Oracle database 10.1.x or 10.2.x, including the database you use for Oracle ContentDB, or
Locate ORACLE_HOME/opmn/conf/ons.config in your database installation and change the port number to 6150 or higher.
If you clone an Oracle Home that contains an OC4J_WebCenter instance, the Java Object Cache configuration for the instance, located in ORACLE_HOME/portal/conf/javacache.xml, is not automatically cloned. You must manually copy this file to the cloned Oracle Home.
When running WebCenter applications or WSRP producers on a standalone OC4J version 10.1.3.1.1 (specifically, the version that ships on the Companion CD with Oracle Application Server 10g Release 3 (10.1.3.2.0), Java Object Cache may not be correctly configured. In this situation, the WebCenter application or WSRP producer will run, but caching will be disabled and the application may run more slowly.
To determine whether this issue is occurring, check the log file in ORACLE_HOME/bin/javacache.log for the entry “java.lang.ArrayIndexOutOfBoundsException: -1."
To address this issue, create two directories: ORACLE_HOME/javacache/admin and ORACLE_HOME/javacache/persistence. Copy ORACLE_HOME/j2ee/home/config/javacache.xml to ORACLE_HOME/javacache/admin. Then, restart your standalone OC4J.
The Oracle WebCenter Suite Portal Adapter enables you to view and search content in OracleAS Portal. To use the Portal Adapter, you must ensure that you are using OracleAS Portal Release 10g (10.1.4), then apply patchset 10.1.4.1 and patch 5697918. The patchset and patch are both available on Oracle Metalink (http://metalink.oracle.com).
For more information on installing the patch, refer to the patch install notes included with the patch ZIP file.
When executed with the destination type LDAP (-dt ldap), the JAZN Migration Tool incorrectly prefixes the ADFRolePrincipal in the LDIF file with the realm root determined from Oracle Internet Directory. An example of the incorrect prefix is "us/".
To fix this issue, after creating the LDIF file with the JAZN migration tool, remove the incorrect prefix, for example “us/", from all occurrences of the grantee anyone, before uploading the entries of the LDIF file to the LDAP server.
When customizing the Rich Text portlet in a Safari browser, users can only perform basic HTML editing. To take advantage of rich text editing, users should customize the portlet in another browser.
When a JSF page contains both ADF data binding and portlets, the portlets cannot be customized. When you click Customize in the portlet, an error occurs.
The workaround for customizing the portlets is as follows:
Click the Back button of your browser.
Click Refresh.
The portlet switches to the customize mode in a shared screen and you can customize it.
Currently, SES can crawl public content from Oracle ContentDB. However, there is an issue with crawling the secured content in Oracle ContentDB. Therefore, the search may not display files even when the user has the appropriate rights to view them.
When using the Federated Portal Adapter, ensure the Oracle JDeveloper environment matches the available languages installed in the OracleAS Portal instance.
When using the File System Adapter, multibyte keywords in a search operation only work with UTF-8 encoded files.
When using Oracle ContentDB or the Federated Portal Adapter, the search feature cannot distinguish among the four versions of the Turkish character I.
The Oracle WebCenter adapters for Microsoft SharePoint, EMC Documentum, and IBM Lotus Domino enable you to retrieve content from SharePoint, Documentum, and Domino repositories. To use the adapters you must ensure that you have applied the 10.1.3.3 patchset, or are using JDeveloper 10.1.3.3, and have applied patch 6447083. The patchset and patch are both available on Oracle Metalink (http://metalink.oracle.com). The patch 6447083 applies to both JDeveloper, Oracle Application Server, and Microsoft Windows (32bit) and Linux platforms. To locate this patch on Metalink, from the Quick Find dropdown, select Patch Number and then enter the patch number in the field next to it. Then click Go.
For more information on installing the patch, refer to the patch install notes included with the patch ZIP file.
Keyword and namePattern search for the & (ampersand) symbol is not supported.
Reexecuting a page in JDeveloper that uses either the Oracle WebCenter adapter for Microsoft SharePoint, EMC Documentum, or IBM Lotus Domino throws an error.The workaround is to stop the OC4J before reexecuting the page.
The query /jcr:root/VIEWS/element(*, nt:base) will return all documents in the Lotus Domino database and not just the names of the views within the database. A query such as /jcr:root/views/MyView/element(*, nt:file) will return all documents visible through the view.
For the Oracle WebCenter adapter for EMC Documentum, supplying a domain name as part of admininstrator credentials, for example EM\alison, may fail the repository connection.
The workaround is to omit the domain name, if the Documentum repository is configured such as to not require domain names.
The Test button in the Create Data Control wizard does not work for the JCR SharePoint adapter.
If you run the Predeployment tool repeatedly in a script, you may experience intermittent failures of the tool. To avoid this problem, allow a minute or two to elapse between executions of the tool.
When you start the Preconfigured OC4J in Oracle JDeveloper, the following may occur:
You may see a notification as follows:
Executing: C:\jdev_4044\jdk\jre/..\bin\java Note the odd path containing forward slashes, backslashes, and "..".
You may see a warning message as follows:
WARNING WARNING: No Repository Type selected, deferring initialization
You can safely ignore these log messages.
A JSP containing Portal Development Kit (PDK) struts components does not compile. It fails with the following error:
java.lang.NoClassDefFoundError: org/apache/struts/taglib/html/FormTag
This happens when using the Oracle PDK struts extension from JDeveloper 10.1.3.2.0. It happens only for the following components:
FormTag
ImgTag
LinkTag
RewriteTag
TextTag
This section describes known errors in Oracle WebCenter Suite documentation. It includes the following topics:
In the Enterprise Manager Application Server Control Console, the HTTP-response code categories HTTP2xx, HTTP3xx, HTTP4xx, and HTTP5xx are used to present performance information for WebCenter applications. However, not all WebCenter application metrics relate to HTTP requests, so successful requests without an associated HTTP request are also logged as HTTP2xx, and unsuccessful requests without an associated HTTP request are logged HTTP5xx.
For example:
Cache hits are logged as HTTP2xx
Timeouts before an HTTP request started are logged HTTP5xx
Timeouts after a cache hit are logged HTTP5xx
Accurate descriptions for all performance metrics are documented in the Oracle WebCenter Framework Developer's Guide, Chapter 10.3 "Interpreting the Information in Enterprise Manager". The online Help implies that all WebCenter application metrics relate to HTTP requests and this is no longer accurate.
Steps 13 to 16 in the Manually Creating and Editing the orion-application.xml File section of the Deploying Your WebCenter Application chapter are required to be performed only if the program uses data-sources.xml or jazn-data.xml, that is, these files need to be created either manually or automatically by choosing to deploy to an OC4J platform in the deployment descriptor profile. If the program does not use data-sources.xml or jazn-data.xml files, then performing these steps (13 to 16) can cause errors.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
