1. Within your server's file system, navigate to Ingeniux CMS 10.0 > Ingeniux CMS Site Wizard.
2. In the New Site tab, provide a name identifying the new site instance.

   

3. Optional: If you want to set up a site from a site export:
   1. Click Browse.
   2. Select the site export .zip folder in File Explorer.
   3. Click Open. The path to the export zip file displays in the Site Export Zip field.
   Version Notes: CMS 10.1+

   Setting up a new CMS site export disables replication profiles for all publishing targets, automatically. This feature prevents an accidental publish of test content to production DSS environments. Even though replication profiles are disabled, the replication profile settings are retained.
4. In the Batch Size drop-down list, select the maximum allowable size of the export zip. Servers with 8GB of RAM or less should use the default value of 1024. Servers with larger amounts of RAM can use a larger batch size for faster content import.
5. In the Engine drop-down list, select Voron or Esent.
   Note

   In preparation for future versions of RavenDB, Ingeniux CMS 10.1-10.3 defaults to the Voron storage engine for RavenDB instances.
6. Click Start. The wizard opens.
7. Click Next. The Select Instance Web Application Type dialog displays.
8. Select either Web Site or Virtual Directory.

   

   • If you want to set up a new website:
     1. Select the Web Site radio button.
     2. Click Next. The IIS Site Configuration screen displays.
     3. Configure the following values:
        • IP Address
        • Port Number
        • Host Name
        • Display Name (friendly name)
   • If you want to set up the CMS site as a virtual directory:
     1. Select the Virtual Directory radio button.
     2. Click Next. The IIS Virtual Directory Configuration screen displays.
     3. Choose the site instance under which to run the virtual site from the drop-down list.
     4. Enter the name of the virtual directory (or retain the auto-populated name).

     

9. Click Next. The Select User Provider Type dialog displays.
10. Select either Ingeniux User Provider or Domain Controller (LDAP or Active Directory).

    

    Note

    This step configures the administrative account credentials that must be used to log into the CMS first.

    • If you selected Ingeniux User Provider:
      1. Enter an Administrative User ID.
      2. Enter a password and then confirm your password in the respective fields.

         

    • If you selected Domain Controller:
      1. Enter a Domain Name in the field provided.
      2. Enter an Administrative ID.
      3. Enter an SMTP domain. This is the domain where users receive workflow notifications from the CMS.

         

      4. Click Next. The Authentication Provider Configuration screen displays.

         

         • To configure authentication manually, click Configure Manually. The site instance installation continues; however, you must edit the following configuration files in the installation's site directory before logging in:
           • local-appsettings.config
           • local-connection-strings.config
           • local-membership.config
         • To configure Active Directory from the Wizard, click Active Directory Wizard. The Active Directory Authentication Configuration dialog displays. Use the field examples to help you configure Active Directory for your organization, or click Use Defaults to set the configuration files after installing the CMS site. Click OK to close the wizard.

           

         Note

         Refer to Configure Authentication in Ingeniux CMS for configuration details.
11. When you finish configuring the administrative account, click Next. The Custom Setup dialog displays.
12. The final step in setting up a CMS site instance is to configure which features are installed and where. For most sites, the default settings are adequate. Click Next to begin the installation, unless you want to customize how and where features are installed.
    To customize features in the Custom Setup dialog box:

    

    1. Tree Area: Clicking any server icon in the tree opens a context menu where you can decide to install a feature on a local hard drive or to run from a network. You can also make entire features unavailable if they are not necessary.
       Note

       Keep in mind that in a standard CMS implementation, all features are required.
       • Ingeniux CMS Site Instance:
         • CMS Site: The site to be installed.
         • Preview Site: A rendering of the DSS that users can see to preview their work.
         • Extensions Development Package: Solution and project for developing hooks, apps, and plugins.
       • Content Store Service:
         • Raven DB Plugins: Ingeniux plugins for Raven DB to support custom indexing and other functionality.
    2. Location: This field specifies the path where the CMS instance will be installed. You can change this location via the Browse button.
    3. Buttons: The following table describes each of the remaining buttons in the Custom Setup dialog.

       Button	Description
       Reset	Returns your feature options to their initial, default values.
       Disc Usage	Clicking the Disc Usage button opens the Disc Space Requirements dialog. This dialog shows how much disc space your volumes have and how much disc space is required by the exported CMS. Note A highlighted volume indicates that they do not have enough disc space.
       Back	Returns to the previous dialog box.
       Next	Advances to the next dialog box.
       Cancel	Cancels the Ingeniux CMS site installation.

    When you're finished customizing your site installation, click Next to begin the installation.
13. After the installation completes, click Finish to exit the installer.
    Note

    You can uninstall a site instance through Add or remove programs in your server's System settings.

    Important

    Before installing a new DSS instance, an administrator must first configure a publishing target within the new CMS instance and then execute a publish to the configured target. See Publishing Targets for details.

Next Steps: Once you have published to a target successfully, you can install a new DSS instance.