What’s New in This Release

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:

Number of attempted, successful, and failed authentications

Policy caching statistics

Policy evaluation transaction times

Web Service Security

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

Inserts tokens to outgoing messages

Evaluates incoming messages for security tokens

Enables point-and-click selection of Authentication providers for new applications

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 coexists with the Java Enterprise System installer which deploys multiple JAR, XML, JSP, HTML, GIF, and various properties files.

Enhancements to Core Services

Web Containers supported

Sun Java System Web Server 7.0

Sun Java System Application Server 8.2

BEA WL 8.1 SP4

IBM WebSphere 5.1.1.6

Monitoring Framework Integration

Access Manager can use the JES Monitoring Framework to monitor the following:

1.Authentication

Number of authentications attempted

Number of remote authentications attempted (optional)

Sun Java System Access Manager 7.1 Release Notes

7

Page 7
Image 7
Sun Microsystems 819468310 Web Service Security, Single Access Manager WAR file deployment, Enhancements to Core Services