Hands On With Microsoft Dynamics GP 2016 R2: Install Service Based Architecture Web Components

January 12th, 2017 by

Microsoft Dynamics GPWith the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.

Service Based Architecture (SBA) is a feature introduced in Microsoft Dynamics GP 2015 RTM which provides a REST web service which exposes Dynamics GP business logic as service operations.

The installation is a three part process, the previous post in this seriescovered adding the SBA feature to the desktop client on the web server, this post will cover the installation of the SBA web components and the next will cover the configuration.

To install the SBA Web Components on the web server, launch the Dynamics GP setup utility and, under Additional Products, click on Web Components:

Microsoft Dynamics GP 2016 setup utility

Accept the terms of the License Agreement and click Next:

Microsoft Dynamics GP Web Components: License Agreement

I am planning to only install the web components required for SBA in this post, so have selected Custom:

Microsoft Dynamics GP Web Components: Installation Option

Mark Web Client as not installed, check and confirm the Install Location and click Next:

Microsoft Dynamics GP Web Components: Select Feature

Enter the Server Name (this is the full SQL Server Instance Name of the server which is to hold the database) and Database Name (if you already have the web client installed you could, and probably should, use the same database) for the Web Components Database and select an authentication method.

If using SQL Authentication enter the Login ID and Password.

Click Next:

Microsoft Dynamics GP Web Components: Web Components Database

SBA is maintained via the Web Management Console so the AD Group which has access needs to be specified in the Web Management Console Users field.

Click Next:

Microsoft Dynamics GP Web Components: Windows User Group

I am not doing a multi-tenant installation so have left this stage unchanged and clicked Next:

Microsoft Dynamics GP Web Components: Tenant Configuration

A Web Site for the Web Management Console needs to be selected.

Then enter the domain account which will be used as the application pool identity for the Dynamics GP Web Application. Enter a Domain, User Name and Password and click Next:

Microsoft Dynamics GP Web Components: Web Management Console Configuration

The web components need to connect to the databases using a SQL server login. To do this, supply a SQL Server Login Name and Password and click Next:

Microsoft Dynamics GP Web Components: GP Configuration

Re-Enter the password entered on the previous stage and click OK:

Re-Enter Password

There are a few details required for the configuration of the GP Service.

First, verify you are happy to install using the 443 port; this is the only web type service installed on this server, so I have accepted this default.

Select an SSL certificate and enter the domain account used for the service account; this needs the Domain, User Name and Password.

Click Next:

Microsoft Dynamics GP Web Components: GP Service

The Dexterity Service Control requires the same settings as the GP Service configured in the last stage, except the default port is 48655:

Microsoft Dynamics GP Web Components: Dexterity Service Control

Click Install to begin the installation:

Microsoft Dynamics GP Web Components: Install Program

Once the installation is complete, click Exit:

Microsoft Dynamics GP Web Components: Installation Complete

Click to show/hide the Hands On With Microsoft Dynamics GP 2016 R2 Series Index

Read original post Hands On With Microsoft Dynamics GP 2016 R2: Install Service Based Architecture Web Components at azurecurve|Ramblings of a Dynamics GP Consultant

Source: azurecurve

Leave a Reply