The following command can be used to encrypt the client message store when you create it.

dbinit -i -s -ek encryption-key database-file

(The -i and -s options are good practice for creating databases on small devices.) When a message store has been initialized with an encryption key, the encryption key is required to start the database server on the encrypted message store.

Use the following command to specify the encryption key to start the QAnywhere Agent with an encrypted message store. The QAnywhere Agent automatically starts the database server on the encrypted message store using the encryption key provided.

qaagent -c "DBF=database-file;DBKEY=encryption-key"

Any application can now access the encrypted message store through the QAnywhere APIs. Note that, since the database server used to manage the message store is already running, the application does not need to provide the encryption key.

If the QAnywhere Agent is not running and an application needs to access an encrypted message store, the QAnywhere APIs automatically starts the database server using the connection parameters specified in the QAnywhere Manager initialization file. To start the database server on an encrypted message store, the encryption key must be specified in the database connection parameters as follows.

CONNECT_PARAMS=DBF=database-file;DBKEY=encryption-key

See also

• Encrypting and decrypting a database
• Initialization utility (dbinit)
• QAnywhere Agent -c option