This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments. It also addresses those who are going to deploy and operate applications.
Many of the attributes used to configure SSL, such as the key stores, and the default repertoire configurations have changed. Also, direct references to SSL configurations are no longer stored in the server.xml file. The convertSSLConfig wsadmin task provides an alternative to manually converting an existing pre-Version 6.1 SSL configurations to a Version 6.1 style SSL configuration.
If you already have profiles defined when you install Version 6.1.0.15, or later, you cannot use the administrative console to select the Microsoft SQL Server JDBC driver as a database type for these profiles. However, if you want to use the Microsoft SQL Server JDBC driver for one or more of the already existing profiles, you can add the Microsoft SQL Server JDBC driver as a new user-defined database type, and then associate this user-defined database type with those profiles.
DB2 Performance Expert Extended Insight (PEEI) allows you to monitor, identify, and resolve performance issues for your entire stack and not just the database layer. These features provide results with a granularity to accurately pinpoint the cause and the culprit of the issue, allowing you to quickly resolve the problem and minimize downtime for your environment.
z/OS Version 1.9 and higher includes a reusable ASID function that enables you to permit the use of all ASIDs, including those that are associated with cross-process services. If you run z/OS with this function enabled, you can use the updateZOSStartArgs script to enable or disable this function for a particular server, a particular node, or for all of your servers.
A new feature called session hot failover has been added to this release. This feature is only applicable to the peer-to-peer mode. In a clustered environment, session affinity in the WebSphere Application Server plug-in routes the requests for a given session to the same server. If the current owner server instance of the session fails, then the WebSphere Application Server plug-in routes the requests to another appropriate server in the cluster. For a cluster configured to run in the peer-to-peer mode this feature causes the plug-in to failover to a server that already contains the backup copy of the session, therefore avoiding the overhead of session retrieval from another server containing the backup. However, hot failover is specifically for servant region failures. When an entire server, meaning both controller and server fail, sessions may have to be retrieved over the network.