You use properties to configure a
Derby system, database, or
conglomerate.
- system-wide
Most properties can be set on a system-wide basis; that is, you set a
property for the entire system and all its databases and conglomerates, if this
is applicable. Some properties, such as error handling and automatic booting,
can be configured only in this way, since they apply to the entire system. (For
information about the Derby
system, see Derby system.)
- database-wide
Some properties can also be set on a database-wide basis. That is, the
property is true for the selected database only and not for the other databases
in the system unless it is set individually within each of them.
For properties that affect conglomerates, changing the value of such
properties affects only conglomerates that are created after the change.
Conglomerates created earlier are unaffected.
Note: Database-wide properties are stored in the database and are simpler for
deployment, in the sense that they follow the database. Database-wide properties
are also recommended for security reasons when you use
Derby BUILTIN user
authentication (see
Derby and security).
System-wide properties can be more practical during the development
process.
Important: Derby's
BUILTIN authentication mechanism is suitable only for development and testing
purposes, and it will no longer be documented in future releases. It is strongly
recommended that production systems rely on NATIVE authentication, an external
directory service such as LDAP, or a user-defined class for authentication. It
is also strongly recommended that production systems protect network connections
with SSL/TLS.