Sponsor Link: EAS Training - Get training in the Essential toolset. Register your interest now. Read more
     
Home Application Modelling Deploying Applications to Technology Nodes
Deploying Applications to Technology Nodes PDF Print E-mail

The Application Deployment class is used in the Essential Meta Model to capture the physical applications that exist in the organisation. This tutorial explains how to deploy instances of these Application Deployments to Technology Nodes in the organisation and extended enterprise.

Purpose 

Application Deployments define the package of software components that make up an application in a particular environment, e.g. development or production. Instances of these are deployed onto physical Technology Nodes to capture where that software is executing. Although this is technically an activity in the Technology Layer, it is the logical conclusion of the Application Layer working from the Conceptual, through Logical and the Physical Views. 

By deploying instances of the Application Deployments, we can also record the dependencies on specific Technology Instances that are also deployed to that Technology Node, e.g.:

  • Our Java EAR depends on the instance of Tomcat Application Server on ‘myapp.myorg.com’ 

 

A Technology Node is a locatable Technology device that exists in the organisation or even extended enterprise. Technology Nodes can represent both physical and virtual devices such as virtual servers.

 

Tasks 

Deploying an instance of the Application Deployment in Essential Architecture Manager is done as follows: 

  • Create a new instance from the field ‘Deployed Application Instances’
  • This opens a new, Application Software Instance form window 
  • Give this instance a given name, which could be the name of the software package that is really deployed, e.g. myApp.ear, myApp.exe
  • Give this instance a description if appropriate 
  • The fully qualified name will be automatically generated. 
  • Specify the type of technology that is used to package this deployment, 
    • e.g. Java EAR file, 
    • Windows Executable. 
  • Define the other Technology Instances that this application deployment instance is directly dependent upon. It is worth considering the layer technology architecture and only defining dependencies between adjacent layers. Essential will manage the full chain of dependencies in the model. 
  • Define any pertinent attributes of this instance 
  • Select the Technology Node (this may be a physical or virtual node) to which you wish to deploy this application instance 
  • Specify the deployment status of this instance. e.g. 
    • the live instance
    • a stand-by instance or 
    • a mirror
    • etc. 

 

 

 
Related Articles