|
|
|
As a Service Administrator, you use CA Server Automation to manage and provision services in your physical and virtual server environments. You want to provide Service Consumers with a simple way to provision the applications they require, hosted on the machines that are required to run them.
For Service Administrators, service provisioning consists of defining applications and service templates. Service templates consist of a set of applications, deployed in a defined order, with a set of application actions and machine templates that determine how and where to deploy the service.
Service templates provide Service Consumers with one-click service provisioning. The consumer selects the service template to provision and enters any additional information that is required to deploy the template as a running service.
CA Server Automation deploys an instance of the service to provisioned resources which match the requirements in the service template.
For example, for a two-tier web application and database service:
Service Administrator
Service Consumer
CA Server Automation deploys the applications to the available server resources and informs the Service Consumer that the web service is ready for use at a specified location.
CA Server Automation provides a set of ready-to-use application definitions and service templates, including the following service:
CA Server Automation supports service provisioning to the following environments:
The following process describes a high-level overview of how Service Administrators combine applications to create service templates that enable one-click service provisioning for Service Consumers:
Specify the environment and server resources available to host provisioned services.
Specify default machine configurations to use in service templates.
Specify and create custom licensing and domain configurations to apply to virtual machines in service templates.
Specify applications, any prerequisites and restrictions, and the resource and operating system requirements for the applications.
Define any of the following types of actions to specify the application execution:
Specify an application file from the Staging Directory and any execution action options that are required to deploy it.
Specify any additional commands that are required to enable the successful deployment of an application.
Create or modify any configuration or property files that are required for the successful deployment of an application. For example, silent installation response files.
Deploy CA ITCM software packages, either as standalone application definitions, or as part of the deployment of another application.
Execute a process workflow defined in CA Process Automation, either as a standalone application definition, or as part of the deployment of another application.
Specify a set of applications and other service templates, and the machines that are required to host them, as a deployable service template.
Export application definitions and service templates to files, and then import them to other instances of CA Server Automation.
Create service templates and application definitions from service instances running in VMware vCenter.
Create service templates from CA AppLogic templates.
Deploy an instance of a service to your server environment.
| Copyright © 2013 CA. All rights reserved. |
|