Application Lifecycle Management
The following diagram provides an overview of the Workload Manager application lifecycle:
Further lifecycle details are described in the following sections.
Base OS Images
Base OS images refer to Linux and Microsoft Windows cloud images on which you install your application service. These virtual base images comprise of the underlying operating system and any operations tools that are required or referenced by services. See OOB Base OS Images for a list of supported images.
The Services Framework
When defining a new service, you can use global parameters, tier/step-specific system parameters, or user-defined parameters and add values at deployment time. See Custom Service Definition for additional information.
The Services Framework enables enterprises to create and add enterprise-specific, private services and make these additional services available via the
Workload Manager does not have hard requirements for scripts called by a service. If you configure a script, Workload Manager executes the configuration specified for each.
The script requirements are:
The script must be in a folder with the same name as the service identifier.
Workload Manager, as root, executes the scripts relative to the extracted folder in the zip file
Scripts are called up at various points during your deployment. See Deployment Lifecycle Scripts for additional information.
When modeling applications you may need to call application-specific scripts for functions such as install, start, restart, and so forth. The called upon scripts may have hard-wired values for configuration parameters which may need to be changed at deployment time. See Configuration Files for additional information.
Configuration parameters represent settings that must be reconfigured when your application is deployed on the target cloud. See Using Parameters for more information.
How Does an Application Profile Work?
- No labels