Before you can work with Automated Data Capture Systems (ADCS), you have to configure Microsoft Dynamics NAV by modifying the VT100Plugin configuration file.
Important: Modification of the configuration file should only be performed by a system administrator.
To modify and update the ADCS configuration file for the terminal listener
Locate and open the NavisionVT100Plugin.exe.config configuration file. It is typically located in the following location: C:\Program Files (x86)\Microsoft Dynamics NAV\80\Automated Data Capture System.
For the Terminal element, update the attributes in the configuration file using attributes as described in the following table. You specify the attribute values in quotation marks.
| Attribute | Description |
| listenIP | Required. IP address that specifies where to listen for terminal connections. |
| listenPort | Required. Positive integer that specifies the port number to listen for terminal connections. |
| stylesheet | Required. Path to transformation style sheet, which transforms warehouse functions to terminal keycodes. Two style sheets are provided with the ADCS installation. |
| screenLines | Optional. Positive integer that specifies the number of screen lines. The default is 5. |
| screenWidth | Optional. Positive integer that specifies the screen width. The default is 30. |
| codePage | Optional. Positive integer that specifies the codepage. The default is the system codepage defined in HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\Nls\CodePage\ACP. |
| terminalTimeout | Optional. Positive integer that specifies the terminal time-out in milliseconds. The default is 65000 and cannot be fewer than 6000. |
| debugDirectory | Optional. Output directory for debug data. |
For the Endpoints element, update the attributes in the configuration file and modify an endpoint to support your processes. You can also add more endpoints. The following table provides some options.
| Attribute | Description |
| defaultType | Optional. defaultType is an attribute of the Endpoints element. It specifies what type of endpoint to use when no type is specified, if you want to customize it. The default is the NavEndpoint type. |
| name | Required. Endpoint name. The name must be unique. |
| url | Required. Endpoint URL address.
Note: This attribute does not have to be included if the clientEndpointName attribute is specified. |
| type | Optional. Fully qualified name of a non-default endpoint. |
| clientEndpointName | Optional. Windows Communications Foundation client endpoint configuration name. If specified, a WCF configuration with the specified name must exist. |
The following example describes the XML for a Terminal element and the Endpoints element. It adds one endpoint for Microsoft Dynamics NAV.
In my case the config file will be as below:
======================================================================
<?xml version=”1.0″?>
<configuration>
<configSections>
<section name=”VT100″ type=”Microsoft.Dynamics.Nav.Adcs.Configuration.VT100ConfigurationSection, Microsoft.Dynamics.Nav.VT100Plugin”/>
</configSections>
<VT100>
<Warehouse>
<Endpoints>
<add name=”NavWSEndpoint” url=”http://indel-axt5283n1.tecturacorp.net:8047/DynamicsNAV80/WS/CRONUS%20International%20Ltd./Codeunit/ADCS”/>
<!– Azure deployment example: –>
<!–<add name=”NavWSEndpoint” url=”https://CloudService:7047/DynamicsNAV/WS/CRONUS%20International%20Ltd/Codeunit/ADCS” UserName=”NavUser” Password=”NavUserPassword” />–>
</Endpoints>
</Warehouse>
<Terminal listenPort=”6666″ listenIP=”127.0.0.1″ stylesheet=”VT100_W2k_and_OtherClients.xsl”/>
</VT100>
<startup><supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.5″/></startup></configuration>
=============================================================================
Security
By default, the NavEndpoint uses the security settings that you have specified for web services generally. You can configure additional security by changing the configuration of Microsoft Dynamics NAV Server and matching that configuration in the VT100Plugin configuration service.
ARKSD Consultancy Private Limited 
2 thoughts on “How to: Configure ADCS Options”
Comments are closed.