Deployment Architecture Templates
Deployment architecture templates are used to simplify the creation of your deployment architecture. The new application deployment architecture components are automatically created using the deployment architecture template components.
Then, the new deployment architecture can be updated or modified.
Some deployment architecture templates are provided with the solution.
Accessing the list of deployment architecture templates
To access the list Deployment architecture templates of a repository:
*From the Administration navigation menu, select Templates > Deployment Architectures.
The list of deployment architecture templates appears.
Describing an Application Deployment Template
Components of an Application Deployment Template 
An application deployment template is described by an application deployment template diagram composed of the following elements:
Application Deployment Templates, used to create the deployable application packages of a new application deployment architecture.
*A deployable application package is a split of application code according to technical criteria for hosting purpose. For example, it may be N tiers, Front End/Back End/… or GUI/Business Logic/Database etc... Each deployable application package is associated to required technologies (for running) and can host code for several IT services. Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).
Data Deployment Templates, used to create the deployable data packages of a new application deployment architecture.
*A deployable data package represents a data part of an application deployment that must be hosted and accessed by application services (code) to run. Each deployable data package is associated to required technologies (for data hosting and access) and can host several data structures. Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model). Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).
microservices,
*A microservice is a software component that can be deployed autonomously, but which does not directly provide an end user service. It can interact with other application services, applications or application systems. This is a deployable software component that uses software technologies. For example: an authentication service, a PDF file printing service.
*For more details on deployable microservices, see Describing a microservice with HOPEX IT Architecture,
Technical Server Port and Technical Client Port,
*A server port is a point used to open communications with a technical architecture or an application technical area in compliance with a particular communication protocol (SMTP, HTTP, etc.).
*A client port is a point used to request the opening of communications from a technical architecture or an application technical area in compliance with a particular communication protocol (SMTP, HTTP, etc.).
*For more details on technical ports, see Adding technical ports.
Package Connections.
*A package connection represents a connection requirement between deployable packages. A client (package) requires a connection to a server (package). The connection is defined by a Connection Type and can be characterized with technical flow measures.
*You can create a Application Deployment Architecture by creating an Application Deployment Architecture diagram directly from the application that interests you.
*For more details on Package Connections, see Describing package connections.
Creating an Application Deployment Template 
To access the list of the application deployment templates of a repository:
1. From the Administration navigation menu,, select Templates > Deployment Architectures.
The list of application deployment Models is displayed.
2. Click New.
The application deployment template appears in the list.
*For more details on the creation of application deployment diagrams, see Using an application deployment architecture diagram.