RavenDB Considerations

When you upgrade to Ingeniux CMS 10.6, the database (RavenDB) upgrades to RavenDB 5.x and registers the database instance as a Windows service.

When you upgrade to Ingeniux CMS 10.5, the database (RavenDB) upgrades to RavenDB 4.x and registers the database instance as a Windows service.

Now that the RavenDB ContentStore runs as a Windows service, the ContentStore no longer displays in the IIS Application Pools list.

Also, in previous versions, RavenDB installed on the same server as the CMS. In CMS 10.5–10.6, system administrators can choose to generate the RavenDB instance on a server that does or doesn't contain the CMS instance.

To access RavenDB, the system requires server and client certificate authentication. System administrators can use certificates generated by the upgrade wizard or provide their own.

If you upgrade to CMS 10.5–10.6 and your implementation relies on custom index definitions, then your definitions may require an update to make them compatible with RavenDB 5.x or RavenDB 4.x. See Troubleshooting Custom Indexes After CMS 10.5+ Upgrade for details about common index definition issues and troubleshooting solutions related to CMS 10.5–10.6 upgrades.

Asset Considerations When Upgrading from Earlier CMS Versions to CMS 10.x

When you upgrade to Ingeniux CMS 10.x, pages from an earlier version that contain image/media/document elements become asset elements:

• Document elements converted to asset elements are no longer filtered by the Document folder as in prior releases. Also, you can select any asset type. That is, there is no asset type restriction after the upgrade. For example, CMS 10.x includes a new default asset type called HTML that all HTML files map to upon upgrade from CMS 9.x or CMS 10.x.
• Image elements converted to asset elements are filtered by Image|Binary asset types after the upgrade from CMS 9.x to 10.x.
  Note

  Before an asset migration, the CMS tests if SVG files are valid. If not, a log entry is written to the Asset Migration log that indicates which SVG file(s) is invalid.
• Media elements converted to Asset elements are filtered by Video|Audio|Binary asset types after the upgrade.

Elements with asset type filters can be modified in their respective schemas and then synced to pages. Asset elements on their own have an attribute in XML for type="assets". Upon choosing an asset type, the type attribute is updated to reflect the selected asset schema.

Assets that were commonly located in the Prebuilt asset folder are treated as unmanaged assets upon upgrading from previous versions of the CMS to CMS 10.x.

Managing Default Form Builder XSLT Files in Assets

Form Builder XSLT files in early CMS sites (i.e., CMS 10.0 - 10.2) are unmanaged in Assets. Customers who upgrade early Ingeniux CMS 10.x sites to Ingeniux CMS 10.3+ and utilize Form Builder pages in their site must manage default Form Builder XSLT files within Assets.

DSS Implementation Changes

Prior to CMS 10.x, DSS Preview and DSS site instances contained a virtual directory mapped to the Prebuilt directory. With modern development and site development practices, there has been a shift towards including Prebuilt asset items as a part of the DSS project itself rather than as assets within the CMS. To align with this change, the virtual directory for Prebuilt is no longer created on new CMS 10.x and DSS site configurations, and the virtual directory is removed on upgrades to CMS 10.x from prior versions of the CMS.

If your DSS implementation requires the Prebuilt virtual directory, you need to manually re-add it to your IIS site configuration for both DSS Preview and DSS.

General Upgrade Considerations

For instructions about how to upgrade from version CMS 9.x or 10.x to CMS 10.5–10.6, refer to the following topics.