An approach that Siriusware Inc. is now recommending for large E-Commerce volume, is to move ww.dll to another computer running the web service (wwService). Then, increase the web service Helper utility processes to 3 - 5 processes and perform an iisreset on the pages IIS server.

 

Note: In exceptionally high traffic environments when the client has powerful hardware, the best performance may be obtained by installing ww.dll, the pages and wwService on one computer (using 127.0.0.1 instead of the “real” IP address).

 

For more information on this configuration, see:

 

ww.dll supports an .INI setting that sets the verbosity for logging of ww.dll activity into the event log. This requires the following setting in the [Preferences] section of the Sales32c.INI: EventLogVerbosity=n where n can be 0, 1, 2, 3, 4 or 5. With this set to 1, only errors are logged. With this set to 2, warnings are also added into the log. With this set between 3 and 5, additional logging of ww.dll startups and stops, calls made to ww.dll and OCV and socket opening/closing information is logged.

Note: Setting this to 4 or 5 is used only for troubleshooting purposes. A large event log is created and there is the possibility of performance degradation.

You can also use the getlog function for troubleshooting. See getlog.

 

The TestCard setting is in the [Data] section of the ww_system.INI. The ww.dll uses this if a valid “test” credit card number is entered (e.g., 5454545454545454), ww.dll bypasses the attempt to get an approval from ProtoBase. ww.dll writes a valid sale string into the ww_sales table with an approval for the sale so that Sales Host is able to process the sale without error provided it is also using a matching TestCard setting (i.e., TestCard=5454545454545454) in the [WebInterface] section of the Sales32c.INI file. For more information on the TestCard setting, see the Salesware .INI Settings Reference. For a complete theory of operation for ww.dll, see the Salesware User Guide for Advanced Users.