Scalable Installation Options

Multiple NASes

Every NAS requires its own MS Dynamics NAV license! So when you use multiple NAS, you should also have multiple MS Dynamics NAV licenses. In the previous chapter you have been able to see the use of multiple servers, which improves the performance of Sana Commerce. Another way to achieve this, is the use of multiple NAS. If required, multiple NAS can also be combined with multiple servers.

• Catalog subsystem;
• Customer subsystem;
• Order/Shop subsystems. 

Step 1: Copy all files that belong to the previously installed NAS to another target folder. By default, the first NAS is installed in C:\Program Files\Microsoft Dynamics NAV\Application Server. We recommend you to place the additional NAS in the same root directory, something like: C:\Program Files\Microsoft Dynamics NAV\Application Server X.

Step 2: Open a command prompt (Start > Run > 'cmd').

Step 3: Navigate to the NAS directory (using the cd command).

Step 4: Run the following command (replace the parameter values with your settings):

nassql installasservice, appservername="server name-SQL", servername="sqlServerName", nettype=tcp, database="database name", company="company name"

Step 5: Make sure a MS Dynamics NAV license file is located in the NAS directory.

Step 1: Open the NAV client, connect to the right administration, open the 'Webshop' menu and select 'Setup'.

Step 2: Open the 'Multiple NAS Setup' tab:

 
The 'Multiple NAS Setup' Tab in the 'Sana Commerce Setup' Window 

Step 3: In this case, there are two NAS. The first one will be used to handle catalog and customer subsystem requests and is configured in the SCCATALOG section. The second one is used by the order and shop subsystems and is configured in the SCORDER section.

Step 4: Specify different port numbers for all NAS to avoid conflicts.

Step 5: When you have finished specifying the port numbers, click OK to save your changes.

Step 6: Open the Application Server Manager tool under 'Start > Programs > Microsoft Dynamics NAV'.

Step 7: When not all NAS are listed, add the missing ones by right clicking the Application Server for Microsoft Dynamics NAV Manager-node, then select 'New > Application Server'.

Step 8: Select the first NAS node, click the 'Stop Service' button, change the 'Start-Up Parameter' to SCCATALOG and click the 'Apply these settings' button.

Step 9: Select the second NAS node, click the 'Stop Service' button, change the 'Start-Up Parameter' to SCORDER and click the 'Apply these settings' button:

 
Configuring the NAS Service 

Step 10: Now the NAS are properly configured and they are running on different port numbers.

 

To be able to complete this step in Windows XP, you need the Windows XP Service Pack 2 Support Tools. Make sure 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 a command prompt and navigate to C:\Program Files\Support Tools.

Step 2: Run the following command to set access rights for the WCF service as follows (this command is case sensitive!):

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

#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;
#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.

 

Step 1: Open the web.config of the Sana Commerce frontend web application in any text editor.

Step 2: Locate the connectionStrings configuration section and make sure a node for every NAS is available. In the example mentioned earlier, the following configuration is applicable:

<connectionStrings>
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=server\SQL2005;Initial Catalog=database;User  Id=user;Password=pwd;" providerName="System.Data.SqlClient"/>
    <add name="CatalogCustomerNas" connectionString="http://127.0.0.1:6002/nav"/>
    <add name="OrderShopNas" connectionString="http://127.0.0.1:6001/nav"/>
</connectionStrings>

Step 3: Select an appropriate name for these configuration nodes.

Step 4: Then locate the sanaCommerceLive/modules section. All Sana Commerce subsystems are listed here.

Step 5: Specify the name of the connection string in the Catalog and Customer subsystem, this name already has been specified in the connectionStrings section in the serviceConnection attribute of the provider node. In the example mentioned earlier, the name is 'CatalogCustomerNas'.

Step 6: Specify the name of the connection string in the Order and Shop subsystems, also this name already has been specified in the connectionStrings section in the serviceConnection attribute of the provider node. In the example, it is 'OrderShopNas'.

Step 7: Also a serviceConnection must be specified for the common subsystem. You can select either one of the NAS'es, It does not have any influence on the performance.

Step 8: Open the 'web.config' of the Sana Commerce backoffice web application in any text editor.

Step 9: Since the backoffice only uses the catalog and content subsystems (content subsystem is not relevant at the moment), only one NAS has to be configured here; the Catalog and Customer NAS.

Step 10: Change or add a configuration node for this NAS in the same way as you have done in the frontend web.config. For consistency, you should give it the same name as used earlier, here this is 'CatalogCustomerNas'.

Step 11: Locate the 'sanaCommerceLive/modules/catalog' configuration section and update the 'serviceConnection' attribute to the name of the connection string specified in the connectionStrings section. In the example this is 'CatalogCustomerNas'.