Features, advantages and benefits
|Customizable out of the box resource monitoring||Out of the box outage detection||Fast outage detection reducing operator requirements for manual monitoring|
|Automatic start, stop and move of your applications||Takes care of cluster-wide relationships, start/stop order and required pre and post start/stop actions||Relieves operator from manual command entry. Improves efficiency by reducing operator errors.|
|Resources can be grouped into applications. Grouping can be cluster-wide||Reduces complexity of operations by automating at the application level, reducing manual intervention and need to remember application components and dependencies||Improves efficiency, reliability and serviceability of the IT Infrastructure enabling a better integration of IT resources with business goals|
|Able to define interdependent resource relationships and associate conditions with resources||Frees operators from remembering application components and relationships. Can use sophisticated knowledge about application components and their relationships to decide corrective actions within the right context.||Reduces operations errors. Improves service levels and optimal IT resource utilization by enabling lower-priority business applications to be shut down while keeping higher-priority business applications running based on business priorities.|
|Policy-based automation||New resources or systems can be added without re-writing scripts||Reduces automation implementation time, and coding and support effort. Leverages manpower through reduced education requirements. No programming skills are required for policy definition. Eases application growth and scaling.|
|Graphical user interface policy editor||Create policies easier with no XML or command line scripting and allows you to quickly visualize dependencies||Lowers the learning curve and enables operators to identify application dependencies quickly|
|Reliable and Scalable||Cluster-wide heart-beating and reliable messaging service||Helps faster cluster implementation to enable a more reliable, dynamic automation|
|Disk Heart beat||This feature adds resilience to the cluster infrastructure. It helps to avoid the trade-off between data integrity and application availability in the majority of cases.||This improves the availability of the applications being managed by System Automation for Multiplatform (SA MP).|
|Integration with GPFS||Seamless integration of GPFS with SA MP||Customers can benefit from GPFS features like data mirroring and information lifecycle management while keeping their application highly available.|
|Support for up to 130 nodes per cluster||Much greater flexibility. DB2 customers in particular have a need to support large clusters.||Supports more of the customer's actual infrastructure as it is today.|
|Operations Console support for Moving Applications||Previously, moving applications to another machine to perform maintenance on the first machine could only be carried out from the CLI. Users can now use the same Operations Console as they use for other functions to perform the move.||Greater user productivity. Less knowledge needed of command-line interface to carry out routine tasks. Improved user interface. Actions to be taken to move the Application can be checked against policies for consistency'.|
|Support for Solaris IP Multipathing||This Solaris feature combines two network adapters to a virtual adapter in order to provide network adapter redundancy for applications.||Solution is more integrated with customer's other high availability strategies. Customers can benefit from network as well as server redundancy.|
|RSCT Resource Harvesting Capabilities||RSCT resources belonging to the classes IBM.NetworkInterface and IBM.AgFileSystem can be harvested (auto-detected). These are the two typical classes for which resources are referenced by customers. All found RSCT resources can be easily selected from a table when defining an SA MP resource.||Improved Time-to-Value through increased productivity and decrease in errors associated with the manual process.|
|Failback of IBM.Application resources||SA MP can start, stop, and monitor arbitrary applications when defined as IBM.Application resources in an SA MP policy. If such an application fails on one system, SA MP re-starts the application on a different system to make it available again. With Failback, SA MP can return the application to the original system once it is available again.||Better productivity, less effort to get an Application back to the primary server. Supports the way customers set up their infrastructure.|
User interface improvements
1) Remove resource name truncation in Policy Editor
2) Auto-Save in Policy Editor
3) Printing graphical policy view in Policy Editor
1) Objects in the Operations Console are shown with their full name instead of a truncated name. As many customer naming conventions led to machines with non-unique character strings at the beginning of the name, truncated names caused confusion.
2) Automatically saves work done in the policy editor which can be recovered should the WebSphere session timeout due to inactivity.
3) Users can print the graphical policy view to share with stakeholders, eg, the Application SMEs whose applications are being made highly available.
1) Improved productivity and usability. Users can tell at-a-glance which component of their infrastructure they are viewing.|
2) Saves user time reworking lost policy changes, and improves user satisfaction.
3) Improved usability facilitates communications of processes and leads to better HA planning.
|Trace File Size Expansion||Trace file size is expanded to provide sufficient first failure data for analysis by the service team.||Improved Serviceability lowers TCO by reducing the time taken to identify product errors.|
|Additional preconfigured policies||New out-of-the-box policies will be provided via OPAL.||Faster Time-to-value. Saves effort in configuring policies for specific situations.|