Centralized Vendor Metadata Database (CVMD)

You can reduce the database footprint and improve system performance by creating and implementing a Centralized Vendor Metadata Database (CVMD). A CVMD reduces the amount of data required for upgrades by putting all the basic vendor metadata that ships with a Mongoose-based application into a single database. Customer-generated data and metadata continue to exist in a separate database.

When a system is converted to be a CVMD setup, all requests for vendor-level data and metadata are redirected to the CVMD, and that data/metadata in the original application database is then ignored. When being set up for a multi-tenant cloud (MTC) user, this results in a much smaller customer database, because what exists there is only the customer-generated data and metadata.

Although we initially created CVMDs primarily to reduce space demands for multi-tenant cloud (MTC) environments, CVMDs can also be created and implemented in an on-premises installation environment. Although this does not necessarily result in great disk storage savings for the on-premises customer, it does reduce the amount of time required for any future upgrades.

Because the use of CVMDs results in each customer's/tenant's databases requiring less space than with a traditional installation, the total amount of storage space required for the MTC farm is greatly reduced. (How much it is reduced is, of course, dependent on the number of tenants on the farm.) This also reduces the amount of time required for MTC upgrades, because the vendor-level metadata needs to up updated only once for everyone, and not repeatedly, for each individual tenant.

Finally, the maintenance window time required to perform the FormSync portion of upgrades, is also reduced, which provides time-saving benefits for both MTC and on-premises customers.

For on-premises installations, the process to implement a CVMD environment involves these basic steps:

  • You must create a CVMD to hold the master vendor data and metadata.
  • Then you must associate the CVMD with the Mongoose application.

The preferred method of creating a CVMD is with the use of a CLI (Command Line Interface). However, CVMDs can also be created, much like any other database, using the Infor Mongoose Configuration Wizard and selecting the Express Configuration option.

When created, CVMDs contain all the schema for applications, objects, templates, and forms in an All-in-One database. Each CVMD contains all this vendor metadata, as well as having all language packs loaded.