In this Article, we are going to discuss the Dynamics GP Web Components Installation and the major parts of the installation and also an installation checklist.
The Microsoft Dynamics GP web components include the web client, service-based architecture and web management console. These components can be installed together on the same server or installed separately on the different servers as needed.
The Dynamics GP web client give access to Dynamics GP through the Internet Explorer web browser. The user experience and functionality are given by the Dynamics GP web client closely matches the experience of using the Dynamics GP desktop client.
No client app software is installed on the user ’s local system. The Dynamics GP application process for the user is running on the separate server. For the GP 2018 release, Silverlight is no longer needed as a Web Client is now an HTML web client.
The following illustration shows the Sales area page in Dynamics GP Web Client.
Parts of the GP Web Components
There are several parts of a web components installation that function together to present the web client to the user.
An Internet Information Services (IIS) website is the main entry point for Dynamics GP web client. This is the website that users connect when they access the web client. It displays the login page where the users can supply their credentials to access the system. The site must be configured to use the Secure Sockets Layer (SSL) to help ensure data security.
The server machines that run the sessions of Dynamics GP web client are called session hosts. Each session host machine will have an installation of the Dynamics GP.
The Session Service is running on every session host machine. It manages the new process that is created each time a user logs into Dynamics GP web client.
Session Central Service
The Session Central Service controls the communication between website and the session host machines. When multiple session host machines are available, Session Central Service will balance the processing load among the available machines.
Dynamics GP Web Client Runtime
The Dynamics GP Web Client runtime is the component of the Dynamics GP installation. A web client runtime process is created by the Session Service each time a user logs into Dynamics GP web client. Like the Dynamics.exe process used by a desktop client, the web client runtime process accesses the business logic in the application dictionaries and the data in the SQL database. Instead of displaying the user interface in a Windows app, the web client runtime displays the user interface in a browser.
Web Management Console
The Web Management Console is a separate HTML app that is used to perform administrative tasks for the Dynamics GP web client. These tasks involve actions like removing abandoned web client sessions.
Description of service Based Architecture
The Dynamics GP service-based architecture enables REST based integrations to the Dynamics GP. The functionality existing in a dictionary is exposed as a service call. The functionality is a “base” used for the service as well as the web and desktop clients.
Components of Service-Based Architecture
The components of service-based architecture function are together to expose the service calls to integrating applications. The components include the following:
A WCF web service that serves as a main entry point for the service. The GP Service is responsible for performing the authentication on the incoming request and directing it to the Dexterity Service that can execute the request. The GP Service must be configured to use the Secure Sockets Layer (SSL) to help ensure data security.
The server machines that host the Dexterity Service instances are called as session hosts. Each session host machine will have an installation of the Dynamics GP and the Dexterity Service Control.
Dexterity Service Control
The Dexterity Service Control is running on every session host machine. It manages the Dexterity Service instances that execute the requests.
The Dexterity Service is a component of Dynamics GP installation. The Dexterity Service gets requests from the GP Service and executes them using the Dynamics GP runtime instance. A runtime instance is created by the Dexterity Service as needed to handle the incoming requests. There could be one or more runtime instances for the Dexterity Service on a session host. Like the Dynamics.exe process used by the desktop client, the Dexterity Service runtime instance accesses the business logic in the application dictionaries and the data in the SQL database.
To install Dynamics GP web components, complete the following tasks in the order shown.
|1. Select a deployment configuration.
Specify if you want to install the Dynamics GP web components on a machine or as a scale-out installation.
|2. Check the Dynamics GP installation.
Verify that the Dynamics GP installation is running properly and the required web client runtime components are installed.
|3. Create security groups and user accounts.
Determine which users will access Dynamics GP web client and the Web Management Console.
|Security groups and user accounts|
|4. Verify the prerequisite software.
Install the software needed to help the Dynamics GP web components.
|5. Create and configure websites.
Create and configure websites that will host the Dynamics GP web client and the Web Management Console.
|6. Obtain security certificates and configure SSL.
Determine the group of security certificate you want to use. Configure the website to use SSL.
|Security certificates and SSL|
|7. Install the web components.
Complete the installation procedure based on the type of deployment that you select
In this Article, we dealt with Dynamics GP Web Components Installation and its major parts along with Checklist.