Chapter 10 – Cloud Service Design using Tivoli Service Automation Manager
When we are building a solution for a certain kind of IT service, the design should cover two important parts.
- The Structural Modeling of the Service
- The Operational Model of the Service
Tivoli Service Automation manager support both these models and concepts that are aligned around the ITSM service life-cycle.
The structural model describes how the service to be managed looks like while the operational model defines what processes can be executed on the service. The structural model of the Tivoli service automation Manager defines all the components that make up a service as well as their relationships between each other.
The Service Topology application allows the representation of the service in terms of hardware servers and their associated software. The primary data the Service Topology application operates on are topology and topology node objects. The application provides a means for viewing and editing the same.
The operational model defines all the management processes that can be run on the service described by the structural mode in particular the processes that are subject to automation. This is done as a process model for a service typically that contains process templates which can be instantiated for various stages of a service's life cycle including creation, modification of a deployed service, etc. Each of the processes defined in the process model – Tivoli Service Automation Manager uses the term Management Plans – which is basically a definition of a sequence of tasks performed on the service's components aimed at achieving a certain management goal. Each management plan represents a specific process or action to be taken with respect to an instance of a service definition. The Management Plan also provides means for describing where input data for each task comes from, and where output data of a task shall be stored for further processing.
Service Definitions are used to capture the design of a service both from a structural point
of view and from a process-centered point of view. Upon an end-user request, new Service Deployment Instances can be built based on the model captured in the respective Service Definitions. Those Service Deployment Instances are used by Tivoli Service Automation Manager to deploy and manage services in the real world.
Finally once the design of a service being automated is completed, offerings can be created and published into Service Catalogs. Services implemented in Tivoli Service Automation Manager can be exposed for end-users so they are accessible in an easy way, based on the notion of service catalogs and service offerings.