# Release Notes

# BEA AquaLogic SOA Management Release Notes

This document includes the following topics:

- About BEA AquaLogic SOA Management
- Supported Configurations and System Requirements
- Known and Resolved Issues

Note: | Documentation for all BEA products, including BEA AquaLogic® SOA Management documentation, is available on the BEA Product Documentation Web site.

## About BEA AquaLogic SOA Management

BEA AquaLogic SOA Management 2.6 ensures the health and well-being of SOA-based systems. It provides visibility into and control of the services network using a policy-based approach to managing and securing loosely-coupled systems at run time. Run time refers to applications and services that have been deployed to run-time containers, including those in development, QA, and production environments. With AquaLogic SOA Management, organizations can better understand system behavior and implement policies that automate performance management and remedy exceptional conditions.

Organizations can realize the following benefits from their SOA:

- End-to-end visibility across the SOA system
- Control of the services network
- Root cause analysis
- Reduced time to repair
- Faster time to ROI

AquaLogic SOA Management bridges the gap between design-time governance tools and run-time management by integrating with AquaLogic Service Registry or any UDDI v3 compliant registry to bidirectionally exchange design-time metadata and run-time information.

Organizations can use AquaLogic SOA Management to identify system behavior and implement policies that automate performance management, remedy exceptional conditions, and uphold security at the end-points where existing enforcement mechanisms might not already exist.

This level of visibility and control can be achieved without special coding to the services or message tags. AquaLogic SOA Management's non-invasive architecture allows SOA systems to evolve and grow without constantly re-coding application components.

For more information about AquaLogic SOA Management concepts and using them in your SOA environment, see Introduction to AquaLogic SOA Management. and Using AquaLogic SOA Management.

For more information about BEA AquaLogic SOA Management concepts and architecture, see the BEA AquaLogic SOA Management 2.6 home page.

### Highlighted Features

BEA AquaLogic SOA Management incorporates new functionality and enhancements in the following areas:

- Synchronization with UDDI v3 registries, including policy information
- Ability to display UDDI metrics
- Graphical policy viewer for policy management
- Template-based policies, including: load-balancing, failover, versioning, smart-routing, security, and logging
- Policy application through the use of criteria filters, such as: production type, date deployed, and custom profiles
- Ability to develop custom policy templates (this comprehensive policy template mechanism and an automatic policy provisioning system minimize the time and skills required to set policies)
- Integration with LDAP V3 directories
- Integration with Netegrity SiteMinder
- Integration with Tivoli Access Manager
- Creation of user-defined attributes
- Client-side agents
- Nano-agents (lightweight passive observers) for monitoring:

- JAX-RPC services
- Java methods
- EJBs
- RMI components
- JDBC calls

Note: | The BEA AquaLogic Service Bus nano agent is not included in AquaLogic SOA Management 2.6; AquaLogic Service Bus services cannot be monitored by AquaLogic SOA Management.

- Support for JAX-RPC plug-in agents

## Supported Configurations and System Requirements

See the Supported Configurations Guide for a list of operating systems, containers, and other third-party products that work with BEA AquaLogic SOA Management.

For information about installing BEA AquaLogic SOA Management, see AquaLogic Service Management Installation Guide.

## Known and Resolved Issues

The following sections describe known problems in AquaLogic SOA Management 2.6, as well as problems that were resolved in 2.6. Entries include a description of the problem and a workaround or solution where appropriate. A notation in the Fixed In column indicates that the problem has been resolved:

Problem ID | Description | Found In | Fixed In
--- | --- | --- | ---
CR317812 | Switching database for AquaLogic SOA Management components can fail in some situations When an AquaLogic SOA Managementcomponent is switched from one database to another, it internally checks for the presence of some tables. If the tables are missing, the new tables are created. In some cases, if the same database was used by another AquaLogic SOA Management database user account, the database switchover operation for the new user might fail. In other cases, the AquaLogic SOA Management console might accept and display the new database account information. Workaround: Do not share the same database instance for multiple AquaLogic SOA Management components and users, or manually create the tables within each schema (user) and use the `datastoreUtil` command to get the DDL. See the online documentation for more information on how to use the tool. | 2.6 |
No CR | The Readme.pdf file that is created in your <ALSM_install> directory does not contain accurate information Ignore the `Readme.pdf` file that is created in your <ALSM_install> directory. For installation instructions and user documentation, see the AquaLogic SOA Management documentation at http://download.oracle.com/docs/cd/E13172_01/alsm/docs26/. Workaround: Use the installation and user documentation at http://download.oracle.com/docs/cd/E13172_01/alsm/docs26/. | 2.6 |