Common
• Built on top of Java Platform Enterprise Edition (Java EE) 5.0 and Java Standard Edition (Java SE) 6.0
• Provides EJB 3.0
• Provides Java Persistence API (JPA) 1.0
• Ease in administration and movement of the applications from one environment to another.
• Better performance than previous versions
• EJB 3.0 API is simpler to code and provides better performance of previous versions.
• Resource efficient features, faster run-time, and new high-performance Web Service Engine
• LTPA Token V2.0 support for SSO
Administration
• Easy administration with Job Manager – remotely manage different environments with Job Manager including standalone servers and clustered environments from one central location across dispersed geographical locations.
• Administer multiple stand-alone nodes using Administrative agent – Single interface to administer multiple application servers, thereby reducing the overhead of running administrative services in every application server.
• Provides support for portable properties files which can be deployed across multiple environments with portable resource identifiers. Improves administration and movement of applications across different environments like dev, test, uat, prod, etc.
• Configure client reroute for applications using DB2 database – Specify alternate DB2 database server in case primary server fails to reroute the client requests to provide high availability.
• Authentication alias can be defined for each server. Server level authentication aliases will not be visible / accessible to other servers in the environment.
• Multiple mail providers and sessions supported. Different versions of the mail provider can co-exist with in the same JVM to provide better control and segregation for different applications.
• Business-level application is a new way of grouping applications together. This is in addition to servers, clusters, cells, EARs, WARs, etc. This way multiple EARs/WARs/JARs can be grouped together into one logical unit and me managed that way like start/stop them all with one command.
• Support of trusted context for DB2 databases to provide fine grained access control.
Security
• Support for Security Domains – Multiple security domains can be configured. Different applications/servers/clusters can be assigned to different security domains to achieve fine grained control over authentication/authorization. Local configuration defined for an application/server/cluster will over-ride global configuration; Following can be configured at local level:
o Application Security
o Java 2 Security
o User Realm (user registry)
o Trust Association (TAI)
o JAAS Login Module (Application, System and J2C Authentication Data)
o Authentication mechanism attributes
o Java 2 Security
o User Realm (user registry)
o Trust Association (TAI)
o JAAS Login Module (Application, System and J2C Authentication Data)
o Authentication mechanism attributes
o Simple and Protected GSS-API Negotiation (SPNEGO) Web Authentication
o Authorization provider
o Other attributes
o Custom properties
• SPNEGO Web Authentication is now supported with enhanced features including dynamic reload of SPNEGO module with the need of server restart.o Authorization provider
o Other attributes
o Custom properties
Development
• Better transaction execution isolation with the provision to specify “commit priority” of the resources contained in a transaction.
• Client reroute for applications that use DB2 databases
• Better handling of data access exception with custom error mapping in DataStoreHelper
