NAV 2018 SERVICE OPTIONS RECAP
NAV 2018 SERVICE OPTIONS RECAP
In NAV 2018 there are many new options related to the NAV Service; some of them have already been introduced with the latest build \ cumulative updates for NAV 2016 and NAV 2017 and only updated \ modified; others are new and introduced by this release.
NEW POWERSHELL CMDLETS
There are also new powershell commands related to restarting and managing services.
CHANGE NAV SERVICE VALUES WITHOUT RESTARTING
The most interesting thing is as written in the “What’s New” it is now possible to modify the parameters of the service without restarting the instance. Great especially for multi-tenants environments. The product is therefore constantly evolving, under a brief RECAP of the most interesting service options to date.
SOME SERVICE OPTIONS
Like old NAV releases… Windows or SQL Login for Database Authentication mode.
Specifies the authentication mechanism for Microsoft Dynamics NAV users of this Microsoft Dynamics NAV Server instance.
Specifies if Microsoft Dynamics NAV Server must allow, warn or prevent a connection from a client that is built with a different build number.
DEFAULT SERVICE AND CLIENT LANGUAGE
Default Client Language
Specifies which of the installed Dynamics NAV languages on the server instance will be used as the default language in the clients. Set the value to a valid language culture name, such en-US or da-DK.
Specifies the global language version to use for text strings with SOAP and OData web services.
The value must be valid culture name for a language that is available for the Microsoft Dynamics NAV solution, such as en-US and da-DK.
DEVELOPMENT PORT & EXTENSIONS TARGET LEVEL
The listening HTTP port for Microsoft Dynamics NAV Developer web services.
Extensions 2.0 – Target Level
“In Extensions 2.0, we have added a concept of ‘levels’ of extensions that are used to determine different classifications and capabilities of an extension package.
In VSCode development, this is something you can specify in the app.json file using the “target” property. This places a restriction on what is ‘allowed’ within the extension.
On the server side, you are given the ability to set the ‘level’ of 2.0 extensions that you want to allow to be publishable/installable. This gives admins control over what kinds of extension they want to have on their systems.”
In order the ‘level’ progress as follows:
- Lowest current level, only allows for inclusion of UI objects like Profiles/PageCustomizations
- Default level, allows for all of the capabilities you would currently expect from an extension
- Unused at the moment, this (or something very like it) will be used to encompass the capabilities of ‘Embed’ apps in the future.
- Highest level, currently only for internal use à NO EXTENSIONS, USE C/AL
SQL COMMANDS TIMEOUT (AND QUERY)
SQL Command Timeout
The contextual timeout for a SQL command.
SQL Connection Idle Timeout
Specifies the time that a SQL connection can remain idle before being closed. The value has the format HH:MM:SS.
SQL Query Logging Threshold
Specifies the amount of time (in milliseconds) that an SQL query can run before a warning event is recorded in the application log for the server instance.
If this threshold is exceeded, the following event is logged: Action completed successfully, but it took longer than the given threshold.
ODATA V4.0 ENDPOINT
Enable V4 Endpoint
Specifies whether the ODataV4 service endpoint will be enabled.
AZURE KEY VAULT ENCRYPTION
Client Certificate Store Location
Specifies the certificate store location for the Key Vault client certificate.
Stay tuned for next post !
#NAV 2018 #DYNAMICS
One thought on “NAV 2018 SERVICE OPTIONS RECAP”
Pingback: MERRY CHRISTMAS AND HAPPY NEW YEAR ! – Roberto Stefanetti NAV Blog
Comments are closed.