While I was working on the series of posts for how to install the Web Services for Microsoft Dynamics GP, I encountered a couple of problems which I thought it might be worth covering; in the last post I looked at resolving a problem with the eConnect Integration Service not running. The second error I encountered was after I installed the Management Tools on a client machine and tried to start it;
While I was working on the series of posts for how to install the Web Services for Microsoft Dynamics GP, I encountered a couple of problems which I thought it might be worth covering in this and the next post.
The first was to do with the eConnect Integration Service which is installed as part of the install of Web Services. The basic problem was that the service was not running;
With the web services installed, configured and verified we can install the Management Tools on a client machine so we don;t need to access the server each time we need to make a change; note that the Management Tools can only be installed on a client machine if there is a domain controller on the network.
To install the Web Services Management Tools, open the Microsoft Dynamics GP setup utility and select Web Services Management Tools;
Now that the web services are installed and configured it is time to make sure that they have installed correctly. The Microsoft documentation for Web Services Installation and Administration Guide starts by checking the services are running via the browser and I’ll come to this in a moment, but I always prefer to start with making sure the services are actually running.
This is done in the Services window ().
The first service to check for is the Microsoft Dynamics GP Service Host. If the service has a Status of Started then the service is running correctly;
Microsoft Dynamics GP 2013 was released on December 19th last year which means that not only do I have a new version of GP itself to install and play with but also lots of related products such as Business Analyser and Integration Manager.
I am also going to be taking a look at some more of the related products, included the new Microsoft Dynamics GP 2013 Web Client, over the coming few weeks/months depending on how spread out they get due to other commitments. I am going to cover the Web Services in this and the next few posts (perhaps allowing for a couple of non-sequitur posts to slip in).
The first step in installing the Microsoft Dynamics GP 2013 Web Services is to install the runtime components which is done in the Microsoft Dynamics GP 2013 setup utility by selected the Web Services Runtime;
The next few posts will cover the installation and configuration of the Web Services for Microsoft Dynamics GP 2013, but, first, I thought it might be useful to give an overview of the prerequisites.
First, the operating system; Windows Server 2008 or Windows Server 2008 R2 Standard or Enterprise editions are supported. According the the documentation, Windows Server 2012 is not yet supported although the install does work.
Second, a Microsoft SQL Server 2008 or later to host the security database. This could be the same or different SQL Server which is hosting the Microsoft Dynamics GP 2013 system and company databases.
Third, Microsoft .NET Framework 4 is required and will be installed by the Microsoft Dynamics GP setup utility.
Fourth, a service user account is needed to run as the Microsoft Dynamics GP Service Host which is the Windows service host. If you’re running web services on the SQL Server then you can use a local user account but if the web services are on a different machine to the SQL Server then a domain user account should be used.
Fifth, the is two bits of setup which needs to have been completed in Microsoft Dynamics GP 2013:
- A Functional Currency needs to be configured in the Multicurrency Setup window ( )
- All currencies need to have a unique ISO currency code ( )
The next post will take a look at the installation of the Web Services Runtime
Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The thirty second feature they’ve announced is Mutli Tenant Web Services for Microsoft Dynamics GP.
The Multi-tenant Microsoft Dynamics GP Web Services feature will provide the ability to host multiple tenants (customer organizations) on a single instance of the application. The below diagram shows the current Single Tenant configuration on the left, and the new Multi Tenant configuration on the right;
Connector for Microsoft Dynamics is a tool available from Microsoft which allows Microsoft Dynamics CRM to be integrated with one of the three Microsoft Dynamics ERP products; AX, GP and NAV.
Being a Microsoft Dynamics GP focused blog, it is the integration to Microsoft Dynamics GP I’m going to take a look at over the next couple of weeks or so depending on how quickly I get the posts written and published.
Connector for Microsoft Dynamics provides a two way integration between Microsoft Dynamics CRM and Microsoft Dynamics GP with the below diagram showing the entities which can be integrated from one system to the other;
This is the seventh, and final, post in the series on installing, configuring and preparing the Web Services for Microsoft Dynamics GP for use. So far I’ve covered the prerequisites, installation process, configuration, verification of the install, security configuration and client Management Tools installation.
To configure the Management Tools, launch the Dynamics Security Console (Windows Start menu >> All Programs >> Administrative Tools >> Dynamics Security Console) and select the Microsoft Dynamics Security node;