Chapter 2: Deployment configurations
There are three common deployment configurations for the Microsoft Dynamics GP web client. This chapter discusses these configurations. It is divided into the following sections:
•
Single machine
•
Scale out
•
Multi-tenant
Single machine
The single machine configuration is the simplest configuration to use when deploying the Microsoft Dynamics GP web client. In this configuration, the web site, Session Central Service, Session Service, and Microsoft Dynamics GP web client runtime are all installed on a single server machine.
A typical single machine configuration is shown in the following illustration.
Local Network
Web Server
+
Web Site
Session Central Service
Session Service
Dynamics GP with Web Client runtime
SQL Server with
Microsoft Dynamics GP Data
This configuration is used when the number of users accessing the system is low. It is also commonly used by developers who are creating and testing integrations for the Microsoft Dynamics GP web client.
One limitation of the single machine configuration is that there is no redundancy. If the server machine is down, such as when installing an update, no web client users will be able to access Microsoft Dynamics GP.
The installation process for this configuration is described in Chapter 9, “Single machine installation.”
Scale out
The scale out configuration is used when an organization has a larger number of users that will be accessing the Microsoft Dynamics GP web client. In this configuration, one server contains the web site and the Session Central Service. Two or more session host machines each contain the Session Service and the Microsoft
Dynamics GP web client runtime. The Session Central Service balances the processing load among the session host machines.
W E B C L I E N T I N S T A L L A T I O N A N D A D M I N I S T R A T I O N 11
