| Define Application Deployment |
|
|
|
|
Application Deployments are part of the Physical View of the Application Layer of the Essential Meta Model. Each environment of an application in the organisation is captured using an Application Deployment, e.g. the 'Production MyApplication'. This tutorial introduces Application Deployments and describes how to capture them in Essential Architecture Manager. PurposeApplication Deployments provide the Physical View of the Application Layer and are modelled as packaged-up collections of Software Components from the high-level software architecture of an Application Provider. The relation between an Application Provider and its physical deployments is managed through its Software Architecture (reflecting the reality of how applications are delivered). Application Deployments are used to represent things such as the Production deployment of 'MyApp', as opposed to the Test instance of 'MyApp'. The Application Deployment Role is used to determine this and forms part of the fully-qualified name of the Application Deployment. Essential Architecture Manager manages the fully-qualified name for you, you need only specify the 'local name' of the Application Deployment
For deployments of e.g. desktop applications, where it is impractical to create an instance of the deployment for each real physical instance, we can use the Application Deployment Group to capture the number of instances of that really exist.
TasksTo create a definition of an Application Deployment in Essential Architecture Manager, follow these steps:
This allows us to have different technology architectures for, e.g. the Production environment and the Test environment – maybe a different server specification.
|