WebCenter Ensemble 10.3.0.1.0 - released June 2009
WebCenter Ensemble 10.3.0 - released November 2008
These release notes cover all releases of WebCenter Ensemble 10g, including hotfixes and maintenance packs. For information on a particular release, please go to the appropriate section of these release notes.
Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://download.oracle.com/docs/cd/E13158_01/ensemble/docs103/index.html.
Oracle WebCenter Ensemble is a reverse proxy that complements portal installations by "widgetizing" the UI. It allows more content to be consumed by portals and allows portal content to be used in non-portal applications.
Oracle WebCenter Ensemble 10.3.0.1.0 contains these new features:
- Support for ADF-based pagelets: Re-use ADF-based pagelets as widgets in any web application.
- Support for WebCenter Services: Use 11g WebCenter Services as pagelets and consume them in Oracle WebCenter Interaction or other web applications.
- Enhancements to the pt:ensemble.inject tag: Pass request parameters to pagelets and control error handling.
At the time of release, Oracle WebCenter Ensemble 10.3.0.1.0 supports the following:
-
Operating Systems:
- Oracle Enterprise Linux 5.2
- Windows 2003 SP2
- Solaris 9 and 10 (SPARC)
- RedHat Linux 4 Update 3 and 5.2
- SUSE Linux 9 and 10
- Databases:
-
Oracle 9i (9.2.0.7)
- Oracle 10g (10.1.0.3 and above) including RAC
- Oracle 10g R2 (10.2.0.1 and above) including RAC
- Oracle 11g (11.1.0.6 and above)* including RAC
- MS SQLServer 2000 SP4
- MS SQLServer 2005
- MS SQLServer 2005 SP2
-
Browsers:
- Internet Explorer 6.0 and 7.0 (including Windows Vista)
- Firefox 2.0 and above and 3.0 and above
- Safari 2.0 and above
-
Application Servers: n/a
* On Oracle 11g databases, customers must add the following parameter to the bottom of the init$ORACLE_SID.ora file: _optimizer_group_by_placement=false.
At the time of release, Oracle WebCenter Ensemble 10.3.0.1.0 supports the following:
- Oracle WebCenter Interaction: Oracle WebCenter Interaction 10.3.0
- Oracle WebCenter Analytics: AquaLogic Analytics 2.5, Oracle WebCenter Analytics 10.3.0
- AquaLogic Pathways 1.5
Note: Oracle WebCenter Ensemble supports the above products regardless of their deployment platform.
Ensemble 10.3.0.1.0 is a patch to 10.3.0.0.0 and requires a installation of 10.3.0.0.0. Upgrade is not supported from Ensemble 1.x to 10.3.x.
The following product documentation is available on http://download.oracle.com/docs/cd/E13158_01/ensemble/docs103/index.html.
|
Document |
Document Description |
Installation and Upgrade Guide
| Describes how to install the components of Oracle WebCenter Ensemble. |
Administrator Guide |
Describes how to use, manage, and administer Oracle WebCenter Ensemble. |
Development Guide |
Describes how to customize and extend Oracle WebCenter Ensemble. |
Configuration Worksheets
| Provides a printable worksheet to gather the information that you need to install and configure all of the various Oracle WebCenter Ensemble components. |
Online Help |
Describes how to use the administration console that is delivered with Oracle WebCenter Ensemble. |
- When using Ensemble with WCI 10.3.0 (WCI 6.5.x), use the ALUI Directory Service (a.k.a the "BEA ALI LDAP Directory") provided in the WCI installer. Do not install the ALUI Directory Service from the Ensemble installer ("Directory Server" option in the Ensemble Custom installation). (Issue #8728047)
- By default, the installer sets the loginserver URL to localhost. Change this URL to a fully qualified domain name, for example 'http://[FQDN]:20060/loginserver' before any use where the browser and proxy are not on the same machine. (Issue #8288495)
- By default, Oracle WebCenter Ensemble creates its tables if they do not exist in the database.
As a convenience for database administrators, SQL scripts for creating the database are also included. These scripts must not
be run on a database where Oracle WebCenter Ensemble has already created tables. Also, the Microsoft SQL Server script create_tables_mssql.sql, must not be run. (Issue #8254792)
- Multiple ADF-based pagelets cannot be used on the same page without using the javascript inject method with iframe option. (Issue #8264837)
- ADF pages require the doctype to be set in the consumer page in order to render properly in Internet Explorer.
Add this line to the top of the consumer page to fix the problem:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">. (Issue #8400119)
- In order to define a pagelet as the root of a resource (i.e., where the pagelet and resource URLs are identical) a "/" must be entered in the
URL Suffix field on the Location tab in the pagelet editor. (Issue #8369120)
- When Oracle WebCenter Wiki is proxied via Oracle WebCenter Ensemble, clicking the "Insert/Edit" link in the rich text editor causes a status icon to appear. To get past the icon, refresh the page by clicking F5. (Issue #8393222)
- When consuming ADF-based pagelets and Oracle WebCenter Services as portlets in Oracle WebCenter Interaction, you must:
- Use Oracle WebCenter Ensemble's REST API for returning pagelet content.
- Set the content-type parameter in the REST call to "iframe".
- Define the resource hosting the pagelet/service at its root (for example,
http://host/my_adf_app-context-root/ not http://host/my_adf_app-context-root/faces/).
(Issue #8356073)
Oracle WebCenter Ensemble 10.3.0 contains these new features:
- Web Injection: Pagelets can now be injected into any proxied page without altering the source of that page; all markup can be modified as it passes through the proxy, allowing styles to be changed, scripts to be added, content to be removed, and so on.
- JavaScript Injection: Pagelets can now be injected into non-proxied pages by adding a javascript call to the target page.
- Standalone Mode: Oracle WebCenter Ensemble can run as a complement to Oracle WebCenter Interaction or, alternatively, can use any LDAP or Active Directory server as its user store. Oracle WebCenter Ensemble no longer requires Oracle WebCenter Interaction.
- Lightweight Clipping: Clip elements from HTML pages using a new, visual clipper.
- SPNEGO Resource Authentication: Oracle WebCenter Ensemble generates SPNEGO tokens to allow SPNEGO-protected resources to be used behind Oracle WebCenter Ensemble without a second login.
- SSO token forwarding.
- REST access to Resource and Pagelet information.
- Java interface for customizing Credential Vault providers.
- Improved Credential Mapping UI.
- Migration of Resource and Pagelet configuration.
- Support for Solaris and Linux.
- The BEA licensing framework has been removed from this product entirely. There is no need to obtain or use a license key to enable any functionality in this version.
At the time of release, Oracle WebCenter Ensemble 10.3.0 supports the following:
-
Operating Systems:
- Oracle Enterprise Linux 5.2
- Windows 2003 SP2
- Solaris 9 and 10 (SPARC)
- RedHat Linux 4 Update 3 and 5.2
- SUSE Linux 9 and 10
- Databases:
-
Oracle 9i (9.2.0.7)
- Oracle 10g (10.1.0.3 and above) including RAC
- Oracle 10g R2 (10.2.0.1 and above) including RAC
- Oracle 11g (11.1.0.6 and above)* including RAC
- MS SQLServer 2000 SP4
- MS SQLServer 2005
- MS SQLServer 2005 SP2
-
Browsers:
- Internet Explorer 6.0 and 7.0 (including Windows Vista)
- Firefox 2.0 and above and 3.0 and above
- Safari 2.0 and above
-
Application Servers: n/a
* On Oracle 11g databases, customers must add the following parameter to the bottom of the init$ORACLE_SID.ora file: _optimizer_group_by_placement=false.
At the time of release, Oracle WebCenter Ensemble 10.3.0 supports the following:
- Oracle WebCenter Interaction: AquaLogic Interaction 6.1, 6.1 MP1, 6.1 MP2, Oracle WebCenter Interaction 10.3.0
- Oracle WebCenter Analytics: AquaLogic Analytics 2.5, Oracle WebCenter Analytics 10.3.0
- AquaLogic Pathways 1.5
Note: Oracle WebCenter Ensemble supports the above products regardless of their deployment platform.
Upgrade is not supported from Oracle WebCenter Ensemble 1.x to 10.3.0.
The following product documentation is available on http://download.oracle.com/docs/cd/E13158_01/ensemble/docs103/index.html.
|
Document |
Document Description |
Installation Guide
| Describes how to install the components of WebCenter Ensemble. |
Administrator Guide |
Describes how to use, manage, and administer WebCenter Ensemble. |
Online Help |
Describes how to use the administration console that is delivered with WebCenter Ensemble. |
Configuration Worksheets
| Provides a printable worksheet to gather the information required to install and configure all of the various Oracle WebCenter Ensemble components. |
- If you are running AquaLogic windows services before running the Oracle WebCenter Ensemble installer you may encounter two non-fatal errors. In the log file these errors appear as errors replacing wrapper.exe and wrapper.dll. The error message is: "The process cannot access the file because it is being used by another process." These errors can be ignored since the two files to be replaced have not changed since any previous AquaLogic releases. If you wish to ensure that these errors do not occur in the future, stop all Windows services that begin with the name "BEA AL" before running the Oracle WebCenter Ensemble installer. (Issue #61647)
- Only users with ASCII usernames and passwords can log in to the Administration Console. (Issue #62650)
- If Credential Vault acquisition does not work for form-based auto-login, make sure that the Action URL in the configuration is absolute. (Issue #62688)
- When using form auto-login with the credential vault and named form and action URLs, the form and action URLs must match for credential acquisition. (Issue #62846)
- Only single resources can be deleted in one operation. Multi-resource delete fails. (Issue #63160)
- Oracle WebCenter Ensemble must not be installed to a directory path that contains white spaces. (Issue #59328)
- Oracle WebCenter Ensemble must not be installed to a directory that includes an installation of Pages or Pathways. (Issue #69989)
- Oracle WebCenter Ensemble's database tables are created and seeded the first time that either the Administration Console or the proxy starts. The installer explicitly warns that the configuration must be fully complete prior to starting either of these services for the first time. However, if the configuration is incorrect or incomplete for some reason, and the services are started successfully, the seed data created at such first startup may not be accurate. The seed data must be manually reviewed and corrected in Admin UI in such a situation. In a future release, the database should be optionally installable using a SQL script. (Issue #60957)
- Oracle WebCenter Ensemble Proxy Server configurations and Oracle WebCenter Ensemble Proxy Application Settings are required to match per install requirement, so they should be kept in sync automatically. (Issue #63237)
- AquaLogic Interaction 6.1 MP1 must be installed prior to Oracle WebCenter Ensemble. Reversing the order of installation causes Configuration Manager to not launch after install. (Issue #63585)
- Evaluation installations of Oracle WebCenter Ensemble include sample users, resources and pagelets. For security reasons, it is prudent to delete all sample data before using Oracle WebCenter Ensemble in production. (Issue #69783)
- When changing the directory server on which Oracle WebCenter Ensemble depends, a new ALUI Security database must be scripted. Also, the new database needs to be identified in the Ensemble|ALUI Security Database section of Configuration Manager. Scripts for creating the ALUI Security database are in the ensembleadminui/
/sql directory. Instructions are in the Oracle WebCenter Ensemble installation guide. (Issue #69979)
- In evaluation installations, the adminui may sometimes fail to start. In this case, open \settings\configuration.xml. Find the "aluisecurity:StoreServiceProperties" element and change the "database-connection:dbhost" value to localhost. Then restart the adminui service. (Issue #69965)
- Pagelet names and pagelet library names may only include ASCII characters. (Issue #70114)
- Web Injectors can include or "nest" existing injectors. Injectors should not be nested inside themselves. Injectors configured in this manner cannot be deleted until the nesting is removed. (Issue #69183)
- Administrators tabbing through the Basic Credential Mapping screen are shown unmasked static field password entries (Issue #63115)
- Only Oracle WebCenter Ensemble Administrators may delete resources. The Administration Console may present a delete option to a non-Administrator user, but the deletion will not be carried out. (Issue #61194)
- Oracle WebCenter Ensemble may warn that a change is about to be lost, even if no change was made. This occurs when the value of a text field has been copied. Please ignore the warning in this case. (Issue #61700)
- If a resource has Credential Mapping settings for Basic Authentication and the user wants to instead configure form-based Credential Mapping, the Basic Authentication settings must first be removed. (Issue #62264)
- NotSerializableExceptions are sometimes logged in the wrapper.log of the Ensemble Administration Console. These exceptions are do not cause any problems. (Issue #62154)
- If the system clock is incorrect on Ensemble servers, the Credential Vault source might not be able to set cookies. (Issue #63051)
- The Oracle WebCenter Ensemble proxy does not currently forward cookies to the browser. Instead, they are stored on the proxy server. For this reason, the client-side JavaScript will be unable to manipulate cookies. (Issue #56130)
- Occasionally ehcache, the caching mechanism, misses messages from peers about updated rules. The problem is resolved when the object expires from the cache (maximum 10 minutes). If immediate changes are required, the proxy server must be restarted. (Issue #60867)
- Pagelet injection does not change the timestamp of the consuming page. In some instances, therefore, changes to what is being injected will not immediately appear. To see immediate changes, force a browser refresh. (Issue #67667)
- WebCenter Interaction cannot be proxied through Oracle WebCenter Ensemble. (Issue #61234)
- If a resource uses a minimum authentication level that is greater than any which are currently specified in the Proxy Authentication list, an error will be thrown. Only use levels less than or equal to the highest configured level. (Issue #61878)
- When registering WebCenter Services as a resource, the external URL must match the root of the service provider. For example, a service provider running at http:///serviceprovider/ would need to be registered using the external URL /serviceprovider/. (Issue #69871)
- For each service installed by the Oracle WebCenter Ensemble installer (Ensemble Administration UI, Ensemble Proxy, Login Server), there is a directory on the file system. In each service's directory, there is a
\settings\conf folder which contains wrapper.conf. Wrapper.conf controls the environment in which the JVM runs the service. To ensure optimal performance, wrapper.java.initmemory and wrapper.java.maxmemory should be customized for your deployment. Below are typical values:
Development/Evaluation Deployment
| Service Name |
wrapper.java.initmemory |
wrapper.java.maxmemory |
| Proxy |
256 |
384 |
| Login Server |
32 |
64 |
| AdminUI |
128 |
384 |
Medium Deployment (refer to sizing information)
| Service Name |
wrapper.java.initmemory |
wrapper.java.maxmemory |
| Proxy |
384 |
512 |
| Login Server |
32 |
64 |
| AdminUI |
256 |
512 |
Large Deployment (refer to sizing information)
| Service Name |
wrapper.java.initmemory |
wrapper.java.maxmemory |
| Proxy |
384 |
1024 |
| Login Server |
64 |
128 |
| AdminUI |
256 |
512 |
The machine should have sufficient physical memory to accommodate the sum of all chosen max sizes and leave sufficient physical memory for other services and the operating system. Setting too large a maximum without sufficient underlying physical memory can cause paging and severely degrade performance. Above are typical values to provide a rough estimate prior to a more thorough sizing estimate exercise. (Issue #62102)
- The "foreach" and "collectionlength" Adaptive Tags throw an exception if the collection is null. Developers must first check to ensure that the collections are non-null before using them with these tags. (Issue #62536)