SA for Multiplatforms automation basics and pre-canned policies
BerndJostmeyer 110000B97C Visits (1503)
SA for Multiplatforms (SAMP) automates applications and ensures their availability in a so called "High Availability Cluster". The product itself delivers the framework to create such an High Availability Cluster and to manage any kind of resource in it. In simply words - anything what can be started, stopped and monitored by an operator using commands can also be managed as so called "resources" by System Automation for Multiplatforms on those systems. You need to configure SAMP and tell the product which resources to manage on the systems within the cluster. In a first step you define the resources (tell SAMP how to start, stop and monitor). I a second step you group the resources logically together and create relationships. This allows you to define the scope of automation (start a group of resource by one command) and control (observe the status of all resources by just checking the group state). In addition SAMP knows in which sequence resources (and therefore the represented applications) should be started or stopped. An operator does not have to remember this ans last but not least SA for Multiplatforms can do it automatically after an unexpected outage was detected without having an operator to react manually.
Creating resources, defining groups and relationships takes a considerable amount of time - more than just the installation of SAMP. In order to help our users to create those policies we provide a set of so called "pre-canned policies" for free. They can be downloaded from the IBM Integrated Service Management Library (also known as OPAL).
Find a link to the pre-canned policies in our WIKI: http