If you want to install the pages on a computer other than the computer that has ww.dll on it, you need to go through the actual installation of the pages on that computer as described earlier in this document. That computer does need to have IIS, Microsoft .NET Framework 4.0 and ASP.NET installed on it, or the pages do not work.

In order for the pages installed on a separate computer to work with ww.dll, the wwService needs to be installed on the computer with ww.dll as described earlier in this document. Please note that both the pages and wwService have their own web.config file. The web.config file for wwService unzips when you install wwService, while the web.config file for the pages is initially supplied by Siriusware, Inc. It is up to the client to keep these files up to date as new functionality appears in the software. The web.config file for wwService has not had any new settings added to it since its initial release and posting, whereas the web.config file for the pages has new additions on a routine basis. The easiest way to keep up with the settings is to read the release notes or update notices that come out with each posting.

There are several settings in the two site config and the web.config for wwService that must be in place in order for the web pages to communicate with ww.dll via the wwService. For the pages site config file these are the pertinent.

 

 

There is also a setting in the web.config in the E-Commerce directory:

 

 

In order for the pages to use the wwService you must set the value for the key UseWebService to 1. If it is set to 0, then the pages look locally for ww.dll and other web service settings are ignored.

The key localhost.wwSalesSvc lets the pages know the URL for the wwService. Only change the IP address portion (shown in bold above) and leave the rest of the path as it is. Enter the IP address of the computer where wwService and ww.dll are installed.

 

Note: When running in a live production setting, you change http to https in the value for the key localhost.wwSalesSvc if you are using SSL instead of the encryption service. Using SSL, however, requires you to purchase another certificate for the server running ww.dll – a cost that can be avoided if you use the encryption service instead.

 

To encrypt communications between the pages and wwService, set the value for the key EncryptSvcComm equal to 1. This setting must match between the web.config file of wwService and the site config of the pages to work. If you use the Internet for transport between wwService and the pages you must use encryption to protect your client’s personal information and credit card details.

Additionally, the PassPhrase values must match in the web.config file of wwService and the site config pages to work. It is best to set this at the beginning of your E-Commerce module configuration and leave it unchanged after that to avoid potential problems. See To set and configure the passphrase for the web service: for directions on how to configure PassPhrase.

Here are the pertinent settings in the wwService web.config file which are also located in the <AppSettings> section of that file: