Installer properties
This properties are only use for the installation. They are not used afterwards.

url This is the URL that will be used when creating the text of the default notifications. This URL is just to tell your customers where is that you are running jbilling. You can change that default text after the installation.

Run time properties
Ignored by the installer and only read when jbilling is running.

base_dir This directory will have other directories where temporary files, logos, invoices, etc are stored. Typically, this directory is named 'resources' and is created where you installed jbilling. The directory has to end with a '/' character. For example: /usr/local/jbilling/resources/

Email server properties These properties are used as a default when sending email to customers (this can be changed through the application). Emails to billing administrators are sent using these properties.
smtp_server
smtp_port
smtp_username
smtp_password
email_from An email address, where replies will be directed.
email_from_name The name displayed as the sender of the emails. Typically 'JBilling' or 'Billing System from ABC Inc.'.

Super user properties There is one super user account that can login to any company (entity).
internal_username The user name for the super user. No other user will be able to use this user name for any of the companies.

internal_key This key is a string that has to be present in the request when logging in with the super user. This is in addition to the password validation. Use at least 20 characters picked at random.

login_lock This is the name of a file, with its complete path. If this file is present, all the sessions of the currently logged users will be terminated and no new log-ins allowed. This can be useful to simulate a shut down of the system to allow maintenance tasks, such as database backups, mass updated, etc. By just removing the file, you are allowing immediate access to the system. This method is much faster then shutting down the application server and it doesn't empty the cache.

force_https This can be 'true' or 'false'. If set to 'true', any request that uses the 'http' protocol (port 80), will be immediately forwarded to 'https' (port 443). For this to work, Tomcat has to be configured and a key repository present.

Batch process properties
process.time This is the date and time when the batch process is going to take place for the very first time. The format is YYYYMMDD-HHmm (a full date followed by HH is the hours in 24hs format and mm the minutes). The batch process usually should run once per day; it checks if invoices need to be generated, email reminders sent, process payments, etc. If you leave the value empty, and 'process.frequency' is 0, then the process will run once per day at midnight. If you leave the value empty, and 'process.frequency' is greater than 0, then it will assume the current time plus the value of 'process.frequency' as the first time to run.

process.frequency The amount of minutes that will be in between batch runs. In other words, how often do you want the batch to run. Valid values are between 0 and 1440.

Security properties
credit_card_secure This is a boolean values that indicates if the credit card numbers and names will be stored encrypted in the database.

credit_card_password This is the key that will be used to encrypt credit cards if the previous property is equal to 'true'. Use a random, lengthly string to make it secure.

password_encrypt_all If set to 'true', all the user password will be stored using one-way encryption. Otherwise, only those for administrators will be encrypted.

lockout_password If a user is locked-out due to too many retries, her password will be set to the value of this property.