HistoryViewLinks to this page Revision from: 2013 November 13 | 07:06 am
This is the revision from 2013 November 13 at 07:06 amView the current live version of the article.

This page covers the scenarios that are driving the Availability work that the Automation WG is undertaking.

The goals of this workgroup are to describe automation scenarios in the context of availability. The scenarios range from simple operational tasks that are carried out automatically on a day-to-day basis, to high availability scenarios where failover activities ensure that the business recovers quickly or even stays up 24x7 through automation, up to disaster recovery scenarios where automated data replication and site switch procedures help to achieve a continuous or near-continuous availability solution for the business.

Provide service to start and stop workloads

Workloads are single entities or groups of entities executed on a server for the purpose of fulfilling a particular business value. Examples are started tasks on a z/OS system, a middleware subsystem consisting of several processes / address spaces or even multi-tiered business applications that can span multiple servers. This scenario is about starting and stopping such a workload in an automated way.

Replace this header with the second scenario’s name

Replace this paragraph with a description of the scenario, and any other related work/specifications/technology that is relevant.