Describing an Application Deployment Architecture and its diagram
An application deployment architecture allows you to describe the overview elements that must be deployed to implement an application architecture: Deployable Application modules, Deployable Data Modules as well as Package connections used for data exchange.
An deployment architecture diagram includes the following elements:
Deployable Application Packages,
*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).
Deployable Data Packages,
*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.
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 technical communications, see Describing package connections.
 
Creating an Application Deployment Architecture 
To create an application deployment architecture from the Applications navigation menu:
1. Open the Application Deployment page of the concerned application.
The list of application deployment architectures appears.
2. Click New.
A dialog box opens to select an application deployment architectures template.
*For more details on application deployment templates, see Deployment Architecture Templates.
3. Select Empty application deployment architectures template and click OK.
*For more details on application deployment templates, see Deployment Architecture Templates.
A new application deployment architectures is created with its diagram.
*You can also create a Application Deployment Architecture by creating an Application Deployment Architecture diagram directly from the application that interests you.