Prepare NAV Server Environment

You need Windows XP Service Pack 2 Support Tools to accomplish this step in Windows XP. Make sure that you have installed the optional tools, which can be downloaded here: http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en.   For Windows Server 2003, the support tools can be downloaded here: http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en.

Step 1: Open the Microsoft Dynamics NAV client, connect to the NAV administration and company.

Step 2: Select the 'Webshop -> Setup' menu item on the left.

For B2X webshop the 'Template Customer' , 'G/L Account No' and 'Payment Method Code' fields  must be set to enable the correct work of B2C scenario. To do this, select the 'General' tab in the 'Webshop Card' and choose the customer template and payment methods which meet your webshop requirements.

Step 3: Select the 'Single NAS setup' tab when using a single NAS setup. If multiple NAS services will be used, select the 'Multiple NAS setup' tab.

Step 4: Mark the 'Use Secure Connection (https)' check box and enter the port number on which the WCF will be running (for NAV with Pebblestone Fashion module, the default port number is 6001, for NAV Standard it is 6002):


Single NAS Setup

Multiple NAS Setup

Step 5: Run the following command (note that this command is case sensitive!): 

httpcfg set urlacl /u PROTOCOL://URL:PORTNUMBER/navision/ /a "O:AUG:AUD:(A;;GA;;;AU)"  

'HttpCfg.exe', which is required for this step, is not available in Windows Server 2008. Use 'Netsh.exe' instead (about which you can read here). In this case, the command will be the following:  netsh.exe http add urlacl url=PROTOCOL://URL:PORTNUMBER/navision/ user=\USER Replace the 'USER' tag with the name of the user that will run the Sana Commerce service. Other tag descriptions are explained below.

Step 6: Replace the following replace tags:

#PROTOCOL#: Protocol type (HTTP or HTTPS)
#URL#: Change to:
     + : when the port registrations in the HTTP Server routing table are placed in the "Strong Wildcard" bucket;
     [hostname] : when the port registrations are placed in the "Explicit" bucket;
     [IP-address] : when the port registrations are placed in the "IP-bound Weak Wildcard" bucket;
     * : when the port registrations are placed in the "Weak Wildcard" bucket.

To see the detailed description of the 'Httpcfg' command syntax, please check http://technet.microsoft.com/en-us/library/cc781601(WS.10).aspx.