Hands On With MDGP 2018 RTM: Configure eConnect Incoming Queue

December 13th, 2017 by Ian Grieve

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With the eConnect Service configured, the next step is to configure the Incoming Queue.

This configuration change is done in the eConnect_Incoming.exe.config file which is located, by default, in C:Program FilesMicrosoft DynamicseConnect 18.0ServiceIncoming Service:

Windows Explorer

Edit the file using Notepad:

Select application

The two sections to change are ringed in red and are:

  1. The value of the data source needs to be changed from 127.0.0.1 to the name of the SQL Server Instance hosting the Microsoft Dynamics GP databases.
  2. The value of the eConnect.Incoming_Queue needs to be set to the server hosting eConnect followed by Private$eConnect_Incoming
eConnect_Incoming.exe.config

Once the file has been edited, open Services and configure the following two queues to be automatic login:

  1. eConnect for Microsoft Dynamics GP 2018 Integration Service
  2. eConnect Incoming Service for Microsoft Dynamics GP 2018
Services

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Configure eConnect Incoming Queue at azurecurve|Ramblings of a Dynamics GP Consultant

Comments >>

Source: azurecurve

Hands On With MDGP 2018 RTM: Configure eConnect Service

December 12th, 2017 by Ian Grieve

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With eConnect installed on the server, there are a couple of pieces of configuration which need to be done. The first is covered in this blog post, and that is the configuration of the eConnect Service.

Perfect Image maintain and support a Dexterity Extension written by a company which is no longer a Microsoft Dynamics partner; this customisation receives transactions via eConnect from an external line of business system. The default configuration results in timeouts if the eConnect service isn’t configured to receive large messages; which basically means adding the following to the Microsoft.Dynamics.GP.eConnect.Service.exe.config file:

receiveTimeout="infinite"

To add this element to the bindings node of the configuration file, open Windows Explorer and navigate to the file in C:Program FilesMicrosoft DynamicseConnect 18.0Service.

Edit the node so it looks like the below and then save the file:

Notepad

Stop and restart the eConnect service to ensure the change is picked up.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Configure eConnect Service at azurecurve|Ramblings of a Dynamics GP Consultant

Comments >>

Source: azurecurve

Hands On With MDGP 2018 RTM: Install eConnect on Server

December 12th, 2017 by Ian Grieve

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With the eConnect prerequisites configured or installed (as appropriate), eConnect can now be installed on the server. eConnect is installed from the setup.exeRun on each one as it appears:

Click Install on the Microsoft Dynamics GP 2018 Bootstrapper Setup:

Microsoft Dynamics GP 2018 Bootstrapper Setup

Under Additional Products, select eConnect and click Install on the popup menu:

Accept the terms of the license agreement and click Next:

eConnect for Microsoft Dynamics GP 2018: License Agreement

On the Select features step, check that Incoming-Outgoing Service is selected for install; if it is not, then the Message Queuing Triggers are not installed.

Click Next to continue:

eConnect for Microsoft Dynamics GP 2018:

Enter the Domain credentials which will be used to run the eConnect services, and then click Next:

eConnect for Microsoft Dynamics GP 2018: eConnect Service User

Enter the Server Name and Dynamics GP System Database name; the former needs to be the full instance name of the SQL Server hosting Microsoft Dynamics GP.

Click Next to proceed:

eConnect for Microsoft Dynamics GP 2018: SQL Connection Information

Click Install to begin the installation:

eConnect for Microsoft Dynamics GP 2018: Ready to Install

Once the installation is complete, click Exit:

eConnect for Microsoft Dynamics GP 2018: Installation Complete

This has eConnect installed, but there is some additional configuration required which will be completed over the next couple of posts in this series.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Install eConnect on Server at azurecurve|Ramblings of a Dynamics GP Consultant

Comments >>

Source: azurecurve