When using the Web-Activator, you have the option of logging its activity to a log file on the server for your analysis later. You may specify a number of fields which are available for logging as well as some formatting details of the log file itself.

This allows you import the log file into your favourite spreadsheet program for analysis.

The log files size can be controlled as well as what happens when the log file reaches the capacity you set.

Although the log file can be helpful for analysis, be careful with its use. If you are expecting extremely high traffic to the Web-Activator (thousands of Activation Codes a day or numerous simultaneous hits) we recommend that you do not log activity. Although the Web-Activator creates a new instance of itself for each hit, so it can work in a multi-threaded manner, access to the log file must be serialized since it is a shared resource. Each thread must wait its turn to access the log file. This serialization can cause slight delays if you expect extremely high traffic to the generator. Some payment processing merchants do not allow you to control the time-out on Activation Code generation, so it is always best to respond immediately. Again, this is not a concern if you do not anticipate thousands of Activations Codes to be generated per day.

If you anticipate a fair amount of activations per-day, you should consider using the CheckPoint License Server instead because it is much more feature rich, and far higher-performance. See: CheckPoint Central Server Controlled Licensing

More Information

For information about actually using and configuring the Web-Activator log file, see Web-Activator Configuration File Specifiers in the SoftwareShield Web-Activator Reference.