Planning the system topology

Environments for development, testing, and production should be carefully optimized for throughput, response time, scalability, and availability. Under this topic, we will learn about the recommended system topologies for production and non-production environments.

The production system topology

The following diagram shows a layered system topology for large-scale implementation projects:

The production system topology

In the preceding diagram, servers are divided among three main layers. The following table explains the different layers, recommended servers, and their purpose:

Layers

Server

Purpose

Perimeter network layer

Terminal service cluster

This provides VPN access to authorized users.

Internet Information Services (IIS)

This provides access to services for AX through the IIS feature.

Internet Information Services cluster (IIS cluster)

This provides Enterprise Portal Support for AX.

Applications layer

AOS cluster

This provides connection to the end users using AX Windows client. Also, it provides functionality for AIF, workflow, and batch processing tasks. It is recommended that separate AOS clusters need to be created for AX client users, EP users, and batch processing.

Integration server clusters

This provides connection to the internal systems.

Dedicated servers

This provides internal client's access to the Enterprise portal, Help server, search server, and project server.

Database and platform layer

Microsoft SQL Server Failover cluster

This provides storage and support for AX databases.

Also, it provides support for additional database requirements.

SQL Server Failover cluster for reporting and BI

This provides support for deployment and execution of Dynamics AX reports and BI cubes.

Storage Area Network

This provides support for data backup.

System Center Operation Manager (SCOM)

This provides support for system monitoring.

Active Directory Domain Controller

This provides support to deploy AX components.

The system topology shown in the preceding diagram is only an example; the solution architect needs to work with the internal IT and network teams and design an appropriate system topology based on the components that you need in your project, and other requirements such as availability, throughput, and scalability. Follow the latest recommendations and best practices from Microsoft and other experts when working on production infrastructure design.

The nonproduction system topology

The following diagram represents non-production environments, such as the test and training environments:

The nonproduction system topology

The following table describes how the computers in this sample topology are used:

Server

Purpose

Active Directory domain controller

This is used to deploy the Dynamics AX components.

Application Object Server (AOS) cluster

This is used to separate server for AX client, batch processes, and enterprise portal.

Web server

This is used to deploy IIS, EP, and Help server.

Database server

This is used as a common database server for Dynamics AX databases, Reporting services, Analysis services, and SharePoint database.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset