Sun Java System Access Manager 7.1 Release Notes

What’s New in This Release

This release includes the following new features:

Java ES Monitoring Framework Integration

Access Manager 7.1 integrates with the Java Enterprise System monitoring framework through Java Management Extensions (JMX). JMX technology provides the tools for building distributed, Web-based, modular, and dynamic solutions for managing and monitoring devices, applications, and service-driven networks. Typical uses of the JMX technology include: consulting and changing application configuration, accumulating statistics about application behavior, notification of state changes and erroneous behaviors. Data is delivered to centralized monitoring console.

Access Manager 7.1 uses the Java ES Monitoring Framework to capture statistics and service-related data such as the following:

Web Service Security

Access Manager 7.1 extends authentication capabilities to web services in the following ways:

Single Access Manager WAR file deployment

Access Manager includes a single WAR file you can use to deploy Access Manager services consistently to any supported container on any supported platform. The Access Manager WAR file can coexist with the Java Enterprise System installer, which deploys multiple JAR, XML, JSP, HTML, GIF, and various properties files.

For more information about staging, configuring, and deploying the Access Manager WAR file, see the Sun Java System Access Manager 7.1 Postinstallation Guide.

Enhancements to Core Services

Web Containers supported

Monitoring Framework Integration

Access Manager can use the Java Enterprise System Monitoring Framework to monitor the following:

  1. Authentication

    • Number of authentications attempted

    • Number of remote authentications attempted (optional)

    • Number of successful authentications

    • Number of failed authentications

    • Number of successful logout operations

    • Number of failed logout operations

    • Transaction time for each module if possible (running and waiting states)

  2. Sessions

    • Size of the session table (hence maximum number of sessions)

    • Number of active sessions (incremental counter)

  3. Profile Service

    • Maximum cache size

    • Transaction time for operations (running and waiting)

  4. Policy

    • Policy evaluation in and out requests

    • Policy connection pool statistics for the subject's plug-in's LDAP server

Authentication module

Policy module

Service Management module

Access Manager SDK

Web Services support

Installation module

Delegation module



Deprecation Notification and Announcement

Sun Java(TM) System Access Manager 7.1 identity management APIs and XML templates enable system administrators to create, delete, and manage identity entries in Sun Java System Directory Server. Access Manager also provides APIs for identity management. Developers use the public interfaces and classes defined in the package to integrate management functions into external applications or services to be managed by Access Manager. Access Manager APIs provide the means to create or delete identity-related objects as well as to get, modify, add, or delete the objects' attributes from Directory Server.

The Access Manager package, commonly known as AMSDK, will not be included in a future Access Manager release. This includes all related APIs and XML templates. No migration options are available now, and no migration options are expected to be available in the future. The user provisioning solutions provided by Sun Java System Identity Manager are compatible replacements that you can start to use now. For more information about Sun Java System Identity Manager, see