AquaLogic Ensemble 1.0 MP2 - released June, 2008 for Windows

AquaLogic Ensemble 1.0 MP1 - released September, 2007 for Windows

AquaLogic Ensemble 1.0 - released July, 2007 for Windows

These release notes cover all releases of AquaLogic Ensemble 1.0, 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 edocs.bea.com.

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.

Refer to the Interoperability page in the Product Center at one.bea.com/support for the latest information on supported BEA products.

At the time of release, AquaLogic Ensemble 1.0 MP2 supports the following:

• AquaLogic Interaction: ALI 6.0, 6.0 SP1, 6.1, 6.1 MP1, 6.1 MP2 (ALI is required)
• AquaLogic Analytics 2.1
• AquaLogic IDK 6.0

Note: AquaLogic Ensemble 1.0 MP2 supports the above BEA products regardless of their deployment platform.

Refer to the Interoperability page in the Product Center at one.bea.com/support for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Ensemble 1.0 MP1 supports the following:

• Operating Systems: Windows 2003 SP1 or R2 (x86)
• Databases: MS SQLServer 2000 SP4, MS SQLServer 2005, Oracle 9i (9.2.0.4 and above), Oracle 10g (10.1.0.3 and above) including RAC, Oracle 10g R2 (10.2.0.1 and above) including RAC
• Browsers: Internet Explorer 6.0 and 7.0 (including Windows Vista), Firefox 2.0 and above, Safari 2.0 and above
• Application Servers: n/a

Refer to the Interoperability page in the Product Center at one.bea.com/support for the latest information on supported BEA products.

At the time of release, AquaLogic Ensemble 1.0 MP1 supports the following:

• AquaLogic Interaction: ALI 6.0, 6.0 SP1, 6.1, 6.1 MP1 (ALI is required)
• AquaLogic Analytics 2.1
• AquaLogic IDK 6.0

Note: AquaLogic Ensemble 1.0 MP1 supports the above BEA products regardless of their deployment platform.

The following product documentation is available at edocs.bea.com/ensemble/docs10.

AL Aqualogic Ensemble 1.0 MP1 currently supports upgrade directly from Aqualogic Ensemble 1.0.

• For installation, an ALI administrative user with the login name "administrator" must be available and used for SDS login. A new administrator with this name can be created (and locked) if the original administrator's name was changed. (Issue #62671)
• If multiple, unique instances of Ensemble are installed on the same network (which commonly occurs in development environments) the network channel for cache multicast messages should be made unique in each installation to avoid unnecessary database load. Change the network channel by changing the multicast address in ehcache.runneradminui.xml and ehcache.runnerproxy.xml (they should both use the same address). For example, to change the address from 230.5.2.1, one should look for and edit this block: <cacheManagerPeerProviderFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory" properties="peerDiscovery=automatic, multicastGroupAddress=230.5.2.1, multicastGroupPort=15925, timeToLive=255"/>. (Issue #61266). Note: this was fixed by exposing the multicast settings in the Configuration Manager; the user will need to change them in order to resolve this issue
• The "database-connection:url-override" setting of the "runner:opendb:DBConnection/aluirunner" does not appear in the ConfigurationManager UI. Some installations, such as those on Oracle RAC, require this setting. In those instances, configuration.xml must be edited directly. (Issue #61306)
• The image server timeout setting should not be changed from the default setting (-1) for a local image server. (Issue #62452)

• All Credential Mapping configurations must have a name. If a name is not specified, Credential Mapping functionality may not work. For example, the Field Mapper may not be able to detect form fields if a name has not been specified for the configuration. (Issue #62457)
• On saving a new form in Applications / Resources / Credential Mapping, failure to provide a form name may result in an application error. If such an error is encountered, switch to another tab and back to Credential Mapping, then re-save the resource. (Issue #62178)

• On Oracle, sending more than one user profile property in the CSP header may throw an exception. (Issue #60022)
• User preferences of the type DATETIME cannot be passed to proxied resources. An error will occur. (Issue #62490)
• After a user is redirected to an SSO logout page, they must delete cookies before they are able to again login. SSO logout pages should not be used unless the page deletes the cookie for the user. (Issue #62528)

• The error "Admin session was null during init call to ptmockstatemodule" can appear when the "Resource Owner" button is selected. This only occurs if required services, like the ALI API Service, were not running when Ensemble is started for the first time. Refer to the installation guide to install Ensemble properly. (Issue #62310)

• Ensemble Proxy Server configurations and Ensemble Proxy Application Settings are required to match per install requirement, so they should be kept in sync automatically. (Issue #63237)
• ALI 6.1 MP1 must be installed prior to Ensemble 1.0 MP1. Reversing the order of installation causes configuration manager to be not launched after install. (Issue #63585)

• 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 #62868)
• Administrators tabbing through Basic Credential Mapping screen are shown unmasked static field password entries (Issue #63115)
• Only single resources can be deleted in one operation. Multi resource delete fails (Issue #63160)

• If the system clock is incorrect on Ensemble servers, Credential Vault source may be unable to set cookies (Issue #63051)
• When standard cookie timeout is smaller than session timeout and session cookie timeout is disabled, SSO cookie timeouts are not effected (Issue #63241)
• When using COREid authentication with URL rewriting turned off and with HTML form access may result in HTTP Page Not Found error (Issue #63337)

AquaLogic Ensemble is a reverse proxy that integrates with AquaLogic Interaction. It provides security, analytics, and application composition features.

• Injection of UI components as "pagelets" into any proxied page, regardless of platform or language
• Adaptive Tags and the Scripting Framework in non-portal Applications
• Support for the new proxy API in the IDK
• Transparent proxying (support for non-rewriting of URLs)
• Analytics on any web application via BEA AquaLogic Analytics
• Integration with major SSO software packages, plus extension points for custom authenticators
• Credential Mapping to automate login to protected applications
• Step-up authentication to allow different levels of security for different applications
• Login and Logout Experience Definitions
• Role-based access to any web application, augmented with profile-based access rules and populated by portal users and groups
• Auditing of access to webapps and changes to resource configurations and access policies
• Administrative roles that allow flexible segmenting of responsibilities
• Admin Console support for English, German, Spanish, French, Italian, Japanese, Korean, Dutch (no online help for Dutch), Portuguese, Simplified Chinese, and Traditional Chinese

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Ensemble 1.0 supports the following:

• Operating Systems: Windows 2003 SP1 or R2 (x86)
• Databases: MS SQLServer 2000 SP4, MS SQLServer 2005, Oracle 9i (9.2.0.4 and above), Oracle 10g (10.1.0.3 and above) including RAC, Oracle 10g R2 (10.2.0.1 and above) including RAC
• Browsers: Internet Explorer 6.0 and 7.0 (including Windows Vista), Firefox 2.0 and above, Safari 2.0 and above
• Application Servers: n/a

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported BEA products.

At the time of release, AquaLogic Ensemble 1.0 supports the following:

• AquaLogic Interaction: ALI 6.0, 6.0 SP1, 6.1, 6.1 MP1 (ALI is required)
• AquaLogic Analytics 2.1
• AquaLogic IDK 6.0

Note: AquaLogic Ensemble 1.0 supports the above BEA products regardless of their deployment platform.

The following product documentation is available at edocs.bea.com/ensemble/docs10.

• For installation, an ALI administrative user with the login name "administrator" must be available and used for SDS login. A new administrator with this name can be created (and locked) if the original administrator's name was changed. (Issue #62671)
• Ensemble should not be installed into a directory path that contains white spaces. (Issue #59328)
• Ensemble's database tables are created and seeded the first time either the admin 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)
• If multiple, unique instances of Ensemble are installed on the same network (which commonly occurs in development environments) the network channel for cache multicast messages should be made unique in each installation to avoid unnecessary database load. Change the network channel by changing the multicast address in ehcache.runneradminui.xml and ehcache.runnerproxy.xml (they should both use the same address). For example, to change the address from 230.5.2.1, one should look for and edit this block: <cacheManagerPeerProviderFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory" properties="peerDiscovery=automatic, multicastGroupAddress=230.5.2.1, multicastGroupPort=15925, timeToLive=255"/>. (Issue #61266)
• The "database-connection:url-override" setting of the "runner:opendb:DBConnection/aluirunner" does not appear in the ConfigurationManager UI. Some installations, such as those on Oracle RAC, require this setting. In those instances, configuration.xml must be edited directly. (Issue #61306)
• If you are running AquaLogic windows services before running the Ensemble installer you may encounter 2 non-fatal errors. In the log file these errors would appear as errors replacing wrapper.exe and wrapper.dll. The error message will be, "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, please be sure to stop all Windows services that begin with the name "BEA AL" before running installer. (Issue #61647)
• The image server timeout setting should not be changed from the default setting (-1) for a local image server. (Issue #62452)

• Only Ensemble Administrators may delete resources. The UI may present a delete option to a non-Administrator user, but the deletion will not be carried out. (Issue #61194)
• Only users with ASCII usernames and passwords can log into the administration console. (Issue #62650)
• 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 instead to 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 admin console. These exceptions are benign. (Issue #62154)
• All Credential Mapping configurations must have a name. If a name is not specified, Credential Mapping functionality may not work. For example, the Field Mapper may not be able to detect form fields if a name has not been specified for the configuration. (Issue #62457)
• On saving a new form in Applications / Resources / Credential Mapping, failure to provide a form name may result in an application error. If such an error is encountered, switch to another tab and back to Credential Mapping, then re-save the resource. (Issue #62178)

• The ensemble proxy does not currently forward cookies to the browser. Instead, they are stored on the proxy server. This means that client-side JavaScript will be unable to manipulate cookies. (Issue #56130)
• On Oracle, sending more than one user profile property in the CSP header may throw an exception. (Issue #60022)
• 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)
• Occasionally ehcache, the caching mechanism, misses messages from peers about updated rules. The problem is resolved when the object expires from the cache (max 10 minutes). If immediate change is required the proxy server must be restarted. (Issue #60867)
• Currently, only custom web applications are supported for the Ensemble proxy. Web applications that cannot be customized, such as third-party websites, are not yet supported. Also, the current version of Ensemble is intended to be deployed alongside AquaLogic Interaction. ALI itself cannot be proxied through 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)
• User preferences of the type DATETIME cannot be passed to proxied resources. An error will occur. (Issue #62490)
• After a user is redirected to an SSO logout page, they must delete cookies before they are able to again login. SSO logout pages should not be used unless the page deletes the cookie for the user. (Issue #62528)

• On Windows XP, if the Ensemble proxy server is not plugged into a network, errors will appear in the logs related to multicast bind problems. The proxy must be connected to a network. (Issue #61480)
• Ensemble services that run on http (the admin console, proxy and login server) should not be installed on hosts that have underscores in their host names. (Issue #62030)
• For each service installed by the ensemble installer (BEA AL Ensemble Admin UI, BEA AL Ensemble Proxy, BEA AL Security and Directory Service, BEA AL Login Server), there is a directory on the filesystem. 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/Demo Deployment

  Service Name	wrapper.java.initmemory	wrapper.java.maxmemory
  SDS	32	64
  Proxy	256	384
  Login Server	32	64
  AdminUI	128	384

  Medium Deployment (refer to sizing information)

  Service Name	wrapper.java.initmemory	wrapper.java.maxmemory
  SDS	64	128
  Proxy	384	512
  Login Server	32	64
  AdminUI	256	512

  Large Deployment (refer to sizing information)

  Service Name	wrapper.java.initmemory	wrapper.java.maxmemory
  SDS	256	512
  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 for other services and the operating system. Setting too large maximum without sufficient underlying physical memory can cause paging and severely degrade performance. Above are typical values to give a rough estimate prior to a more thorough sizing estimate exercise. (Issue #62102)

• The error "Admin session was null during init call to ptmockstatemodule" can appear when the "Resource Owner" button is selected. This only occurs if required services, like the ALI API Service, were not running when Ensemble is started for the first time. Refer to the installation guide to install Ensemble properly. (Issue #62310)
• 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)