Scalable Installation Options

Multiple Servers

Web server:

• Microsoft Windows 2008 server R2;
• Microsoft .NET Framework 3.5 SP1 or better;
• Microsoft IIS 7.

Database/MS Dynamics NAV server:

• Microsoft Windows 2008 server R2;
• Microsoft .NET Framework 3.5 SP1 or better;
• Microsoft SQL Server 2008 Express or Standard edition;
• Optional: Microsoft SQL Management Studio 2008  Express or Standard edition;
• Microsoft Dynamics NAV - Administration database (SQL or native) - the Pebblestone Fashion 9.0 module is required when using the Sana Commerce Fashion add-on;
• Microsoft Dynamics NAV - Application Server for Microsoft Dynamics NAV (SQL or native) in case of using WCF + NAS connection;
• Microsoft Dynamics NAV 2009 Server and Web Services in case of using NAV 2009 three-tier environment;
• Optional: Microsoft Dynamics NAV - Client (SQL or native);
• Optional: Microsoft Dynamics NAV RoleTailored Client (SQL or native).

Web/database server:

• Microsoft Windows 2008 server R2;
• Microsoft .NET Framework 3.5 SP1 or better;
• Microsoft IIS 7;
• Microsoft SQL Server 2008 Express or Standard edition;
• Optional: Microsoft SQL Management Studio 2008 Express or Standard edition.

NAV server:

• Microsoft Windows 2008 server R2;
• Microsoft .NET Framework 3.5 SP1 or better;
• Microsoft Dynamics NAV 5.0 - Administration database (SQL or native) - the Pebblestone Fashion 9.0 module is required when using the Sana Commerce Fashion add-on;
• Microsoft Dynamics NAV 5.0 - Application Server for Microsoft Dynamics NAV (SQL or native);
• Optional: Microsoft Dynamics NAV 5.0 - Client (SQL or native).

• Request a SSL certificate at a certificate authority for the hostname of the server running the WCF service and install this certificate. How to do this, is described in the 'SSL certificate for NAS Service' section;
• Configure the URL for the WCF service as follows (this command is case sensitive!):
  

  Httpcfg.exe set urlacl https://URL:PORTNUMBER/navision /a "O:AUG:AUD:(A;;GA;;;AU)"
  

  #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;
  #PORTNUMBER#: must be replaced by the port number on which the NAS is running.

For more information about routing incoming requests, please check http://msdn.microsoft.com/en-us/library/aa364687(VS.85).aspx.

 

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

More information about the previous steps can be found here: http://msdn.microsoft.com/en-us/library/ms733791.aspx.

• Open the NAV client and connect to the correct administration, open the 'Webshop' menu item and select 'Setup';
  
   
  The 'Sana Commerce Setup' Window 

• Depending on whether you are running a 'Single NAS Setup' or a 'Multiple NAS Setup', open the correct tab;
• Activate 'Use Secure Connection (https)' check box;
• Click 'OK' to save your changes;
• Then open the 'web.config' of the Sana Commerce frontend web application in any text editor;
• Locate the connectionStrings configuration section and update the protocol to 'HTTPS' in the 'connectionString' attribute of the 'NAVService' node. This can be multiple nodes if running multiple NAS'es;
• Now open the 'web.config' of the Sana Commerce backoffice web application and repeat these steps in this location.