Configuration banner
Last updated
Last updated
Orbeon Forms requires a few important configuration steps to be performed before it can be used, including:
setting a password for encryption
configuring a separate database
If either of these is not properly configured, Orbeon Forms show a banner at the top of application pages.
You can learn more about the specific configurations that are missing by configuring logging and checking the Orbeon Forms log file. The file will contain something like the following at the ERROR level:
In addition, the following optional features require configuring separate passwords:
You do not have to configure these features if you do not plan to use them. However, the fact that these features are not configured will be logged at the INFO level.
The following subsections cover the individual configurations in more detail.
Out-of-the-box, Orbeon Forms includes an SQLite embedded database with multiple demo forms. This setup is designed for a quick start, but for development or production use, you should configure Orbeon Forms to use a separate relational database.
The reason for considering this an incomplete configuration is that the SQLite database is not suitable for production use with Orbeon Forms at this point. This is not necessarily due to shortcomings of SQLite, but due to the fact that the SQLite database is embedded in the Orbeon Forms WAR file and more likely to be deleted by mistake. In addition, most users want to use a more powerful database for production use.
You are not required to configure a separate database if you are using Orbeon Forms for evaluation purposes only, but in this case the configuration banner will show.
See also Database setup.
You must set the oxf.crypto.password property to something different from the default. This is used for the following:
internal encryption (admin token, operations, internally-submitted data, uploaded URLs)
product version in the URL
cid: URLs and XML metadata format
This password is mostly used for transient data, but you must still change it.
If you plan to use Token-based permissions, also set oxf.fr.access-token.password. If you don't set it and try to use access tokens, an error will be produced when the password is needed.
If you plan to use Field-level encryption, also set oxf.fr.field-encryption.password. If you don't set it and try to use field-level encryption, an error will be produced when the password is needed.
