Managing Microsoft Dynamics NAV Server Instances
This topic describes how to work with Microsoft Dynamics NAV Server instances in the Microsoft Dynamics NAV Server Administration tool and in the Services MMC snap-in. For more information about how to create a Microsoft Dynamics NAV Server instance, see How to: Create a Microsoft Dynamics NAV Server Instance. For more information about the settings that you can configure in a Microsoft Dynamics NAV Server instance, see Microsoft Dynamics NAV Server Settings.
Each Microsoft Dynamics NAV Server instance on a computer runs as a separate Windows service and can run under a separate computer account, which is the Service Account.
In addition to the Microsoft Dynamics NAV Server Administration tool, you can use the Services snap-in, which is included in Control Panel, to see the Microsoft Dynamics NAV Server instances on the computer. To open the Services snap-in, choose the Start menu, in the Search box type Services, and then choose the related link. Each instance name begins with Microsoft Dynamics NAV Server. The default instance is identified as Microsoft Dynamics NAV Server[DynamicsNAV110]. Any instances that you create are identified by Microsoft Dynamics NAV Server, following by the instance name in brackets. For example, if you create a Microsoft Dynamics NAV Server instance and name it Denmark, the Services snap-in shows the following instances:
Microsoft Dynamics NAV Server[DynamicsNAV110]
Microsoft Dynamics NAV Server [Denmark]
You can also administrate your Dynamics NAV deployment using Windows PowerShell cmdlets. For more information, see Microsoft Dynamics NAV Windows PowerShell Cmdlets.
Server Instances and Service Types
In Microsoft Dynamics NAV Server Administration tool, settings for a server instance are organized into tabs and then organized by service type.
|General||All types of services.|
|Client Services||Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client.|
|OData Web Services||OData web services.|
|SOAP Web Services||SOAP web services|
|NAS Services||Dynamics NAV Application Server (NAS) services.|
|Management Services||Services for managing Microsoft Dynamics NAV Server on the computer.|
For more information about the different service types, see Client Types.
You should recognize and understand the difference between server instances and service types.
A server instance is a distinct service in Windows and is the middle tier in the Dynamics NAV three-tier architecture. For more information, see Product and Architecture Overview.
A service type is a category within a Microsoft Dynamics NAV Server instance.
When you modify a permission set or modify permissions for a user, you must restart all Microsoft Dynamics NAV Server instances in the database for those changes to take effect. The exception is for the current instance—that is, the instance that the client (the Microsoft Dynamics NAV Windows client or the Microsoft Dynamics NAV Web client) is using when the changes are made. There is no need to restart this instance. It is also necessary to restart Microsoft Dynamics NAV Server instances if you modify permissions sets or user permissions using the Dynamics NAV Windows PowerShell cmdlets.
Managing Different Types of Services from a Single Microsoft Dynamics NAV Server Computer
When you change the value of any setting in any service category, you must restart the Microsoft Dynamics NAV Server instance for the change to take effect. Restarting the instance affects all services types within that instance. For example, Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client users are disconnected, and web service applications are interrupted. Therefore, if you plan to run different types of services on a single computer running Microsoft Dynamics NAV Server, we recommend that you run different services types in separate service instances. Your computer should have sufficient memory to run multiple service instances. For example, if you plan to use both the Client Services and OData Web Services on a single computer running Microsoft Dynamics NAV Server, then you should run the Client Services in one server instance and the OData Web Services in a separate server instance. If you have to change an OData web services setting, then you do not affect Microsoft Dynamics NAV Windows client users when you restart the instance to enable the change.
To disable a service type, clear the Enable property on the relevant tab. The only service type that does not have an Enable property is NAS Services. To disable NAS Services, set Startup Codeunit on the NAS Services tab to 0. For more information, see Configuring NAS Services.
Send feedback about: