Installing and Enabling WS on Microsoft Dynamics NAV Installation
We do not need additional steps to have WS up and running on our environment out from following the installation of Microsoft Dynamics NAV 2013.
WS are thought to be working Out of the box and therefore they are part of the Server installation.
We do have the option of choosing which port will be enabled for both SOAP and OData WS on the installation process just in case we want to change by default (7047, 7048) ones:
Those who have worked with Microsoft Dynamics NAV WS before know that delegation setup and Service Principle Names creation was a key part on WS setup for environments lying on 3 different machines (One for Clients, another one for Microsoft Dynamics NAV Service (Microsoft Dynamics NAV Service Tier) and the last one for SQL Server)
Remember the walkthrough on how to enable WS for Microsoft Dynamics NAV 2009 on 3 tier environments:
However, in Microsoft Dynamics NAV 2013 this setup is much simpler thanks to the changes introduced on which account is connecting to SQL Server.
There is a nice bunch of information about the new setup for delegation on the next document where this is fully covered.
Once The Microsoft Dynamics NAV Service has been installed we will get the next events (Among many orher messages for other Microsoft Dynamics NAV features) on our Event Viewer that confirms us that everything is running as expected:
· SOAP:
· OData:
If we visit the URL’s published there we could see the list of Objects published as WS for both protocols (Remember we haven’t published anyone yet)
· SOAP:
· OData:
Download Videos for more information :