HOPEX Aquila EN

An Application System Deployment Architecture describes one of the configurations possible for deploying an application system. It contains the deployment architectures of application components and specifies the communication protocols (and port numbers) they use to communicate with each other.

To access Application System Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application System Deployement Architectures sub-tab.

The list of Application System Deployement Architectures of the Enterprise is displayed.

To create an Application System Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application System Deployement Architectures sub-tab.

4. Click New button.

The Application System Deployment Architecture is created and its diagram opens.

To connect an Application to an Application System Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application System Deployement Architectures sub-tab.

The list of Application System Deployment Architecture appears

4. Select the Application System Deployement Architecture that interests you and use the Application System column to connect an applicaiton system.

You can create a Application System Deployment Architecture by creating an ApplicationSystem Deployment Architecture diagram from the application System that interests you. See Application Systems diagrams with HOPEX UAF.

An application system deployment architecture is described by an application system deployment architecture diagram composed of the following elements:

An application system deployment architecture diagram includes the following elements:

• Application Deployment Architecture,

An Application Deployment Architecture describes one possible deployment configuration of an application. It contains the deployment architectures to be hosted, recommends hosting architectures and identifies required communication techniques (communication protocols and port numbers) they use to communicate with each other. . An application may have several deployment architectures (E.g.: autonomous installation, horizontal or vertical deployment, etc.)

For more details on application deployment architectures, see Describing an Application Deployement Architecture with HOPEX UAF.

• Application System Deployment Architectures,

An Application System Deployment Architecture describes one of the configurations possible for deploying an application system. It contains the deployment architectures of application components and specifies the communication protocols (and port numbers) they use to communicate with each other.

• 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.

• 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).

• Technical Server Port and Technical Client Port,

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.).

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.).

• 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.

An Application Deployment Architecture describes one possible deployment configuration of an application. It contains the deployment architectures to be hosted, recommends hosting architectures and identifies required communication techniques (communication protocols and port numbers) they use to communicate with each other. . An application may have several deployment architectures (E.g.: autonomous installation, horizontal or vertical deployment, etc.)

To access Application Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application Deployement Architectures sub-tab.

The list of Application Deployement Architectures of the Enterprise is displayed.

To create an Application Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application Deployement Architectures sub-tab.

4. Click New button.

The Application Deployment Architecture is created and its diagram opens.

To connect an Application to an Application Deployement Architectures:

1. From the navigation menu, select Resources > Taxonomy - Structure (Software).

2. Click the Software tab.

3. Click the Application Deployement Architectures sub-tab.

The list of Application Deployment Architecture appears

4. Select the Application Deployement Architecture that interests you and use the Application column to connect an applicaiton.

You can create a Application Deployment Architecture by creating an Application Deployment Architecture diagram from the application that interests you. See Application diagrams with HOPEX UAF.

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 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.).

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.).

• 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.