What can be encrypted

Use this feature for native APPXIO indexed files and variable-length consecutive files. One-record files and fixed-length consecutive files cannot be encrypted with this feature.

In the standard DMO application, the nine permanent indexed files used here are ACTIVITY, ACTTYPE, CONTACT, COUNTRY, INDUSTRY, OPPORTUN, PROSPECT, SALESREP, and STAGE. PARAM is a one-record file. STREAM is a disk-subprocess stream definition. Leave PARAM and STREAM out of these conversion selections.

“Encrypt DMO” therefore means encrypt every eligible native datafile in DMO. It does not mean that the entire database directory, every file organization, or every generated output becomes encrypted.

An APPX database can contain files from more than one application. Inventory the database's related applications before starting. Repeat the database exercise for every application with eligible files in DMO. The nine-file selection shown here covers the standard DMO application; additional applications and locally added files require their own selections and checks.

APPX data file encryption is not intended for data held in an external datastore and will not encrypt that data. This includes Oracle and SQL Server tables accessed through an APPX external database interface. Configure encryption for those tables and their backups in the database product that stores them.