Step 3: configure mandatory settings in config.ini

1. Navigate to the "inc" subfolder and edit the config.ini file stored on your server.

Once again, check that the config.ini file cannot be accessed publicly (the .htaccess prevents end users from accessing it) because this file contains sensitive data for generating activation keys.

The important part of the config.ini file looks like this:

[globals]

; ====== Modify the following parameters for your workbook ======

; ** Your XLS Padlock user ID **

xlspadlockuserid = "xps-xxxxxxxxxxxxxx"

; ** Default maximum number of activations per order allowed (we also take account of order quantity).

; For instance, if the customer bought a quantity of 2 products and with defmaxactivperorder = 2, we would allow 4 activations.

defmaxactivperorder = 2

; ** Your FastSpring API Username - see https://fastspring.com/docs/fastspring-api/ "Access the API"

fsapi_username = "xxxxxxxxxxxxxx"

; ** Your FastSpring API Password - see https://fastspring.com/docs/fastspring-api/ "Access the API"

fsapi_password = "xxxxxxxxxxxxxx"

; ========================

; Do not modify below

DEBUG=0

UI=./inc/app/views/

AUTOLOAD=./inc/app/controllers/|./inc/app/models/|./inc/lib/

2. Change the value of the entry named xlspadlockuserid to your XLS Padlock user ID. This user ID is available in the registration email that you received when you purchased XLS Padlock. Important: remember that the user ID begins with xps-

3. Finally, provide the API username and password you got from FastSpring at step 1.

fsapi_username = "ABCDEF12345"

fsapi_password = "54DEF321ABC"

4. Save modifications to the config.ini file.

The web application is now ready to receive data from the compiled workbook EXE files and communicate with your website.

Step 4: associate your compiled workbook EXE files with the web application