Nothing Special   »   [go: up one dir, main page]

Plan

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

How LCS is used with on-premises deployments

Microsoft Dynamics Lifecycle Services (LCS) is an application management portal that


provides tools and services for managing the application lifecycle. Customers and
partners use LCS to manage both cloud and on-premises deployments. You can use LCS
for the following tasks:

 Deploy cloud and on-premises environments.


 Service your environments.
 Monitor, diagnose, and analyze the health of the environments that you manage
(cloud only).
 Search for product issues and regulatory features.
 Obtain support.

For more information about LCS, see Lifecycle Services resources.

Environments
There are four types of environments that you need to plan for. This section describes
the four environments and how to access and deploy them.

Demo environment

You can sign up for a demo environment to learn about the system. The demo
environment is applicable to both cloud and on-premises deployments. For more
information, see Sign up for preview subscriptions.

Developer environment

The development experience is the same for cloud and on-premises deployments. To
access a developer environment, see Deploy and access development environments.

Sandbox environment

Business users and functional team members validate application functionality by using
a sandbox environment. This functionality includes customizations and data that was
brought forward from Microsoft Dynamics AX 2012 environments. To deploy an on-
premises sandbox environment, see Set up and deploy on-premises environments home
page.

At a minimum, an on-premises sandbox environment requires:

 3 machines running Environment Orchestrator


 2 machines running Application Object Servers (AOS)
 1 machine running Management Reporter (MR)
 1 machine running SQL Server Reporting Services (SSRS) with a local SQL Server
(Database Engine)
 1 machine running Active Directory
 1 machine running SQL Server (Database Engine)

Production environment

The production environment is the live deployment that your users and customers have
access to. To deploy a production environment, see Set up and deploy on-premises
environments home page.

At a minimum, an on-premises production environment requires:

 3 machines running Environment Orchestrator


 3 machines running Application Object Servers (AOS)
 1 machine running Management Reporter (MR)
 1 machine running SQL Server Reporting Services (SSRS) with a local SQL Server
(Database Engine)
 2 or more machines running SQL Server (Database Engine)
 2 or more machines running Active Directory

Service Fabric
An on-premises deployment uses Azure Service Fabric standalone clusters. Service
Fabric is the next-generation Microsoft middleware platform for building and managing
enterprise-class, high-scale applications. Service Fabric standalone clusters can be
deployed on any computer that is running Windows Server.
An on-premises deployment has a standalone cluster for each sandbox environment
and a standalone cluster for each production environment. The following roles or node
types are deployed into both types of clusters:

 Application Object Servers (AOS) – Provides the ability to run the application
functionality in client, batch, and import/export scenarios.
 Management Reporter (MR) – Provides financial reporting functionality.
 SQL Server Reporting Services (SSRS) – Provides document reporting functionality.
 Environment Orchestrator – Enables on-premises environment management from
LCS.

The following diagram shows the node types deployed in a Service Fabric standalone
cluster.

Service Fabric resources

To learn more about Service Fabric, see the following topics:

 Azure Service Fabric documentation - To learn more about Service Fabric.


 Service Fabric application upgrade - An Azure Service Fabric application is a
collection of services that requires periodic upgrades.
 Plan and prepare your Service Fabric standalone cluster deployment - Additional
information about Service Fabric clusters and antivirus exclusions.

You might also like