To install a database in the Configuration Wizard

1. Start the Configuration Wizard.

2. On the Configuration Wizard's home page, select the Create and install database option and click Next.

3. To install a new database, enter the following database connection data on the Create administrative connection page.

   • Server: Database server.

   • (Optional) Windows Authentication: Specifies whether the integrated Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.

   • User: SQL Server Login name of the installation user.

   • Password: Password for the installation user.

   - OR -

   To use an existing empty database, on the Create administrative connectionpage, select the Use an existing, empty database for installation option and enter the database connection information.

   NOTE: To install the One Identity Manager schema in an existing database in Azure SQL Database, enable the option and enter the database connection credentials.

   NOTE: To install the One Identity Manager schema in an existing database in Amazon RDS for SQL Server, enable the option and enter the database connection credentials.

   • Server: Database server.

   • (Optional) Windows Authentication: Specifies whether the integrated Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.

   • User: SQL Server Login name of the installation user.

   • Password: Password for the installation user.

   • Database: Name of the database.

   TIP: To configure additional connection settings, enable the Advanced option.

4. If you are creating a new database, perform the following tasks on the Create database page.

   1. In the Database properties view, enter the following information about the database.

      Table 17: Database properties

      Data	Description
      Database name	Name of the database.
      Data directory	Directory in which the data file is created. You have the following options: <default>: The database server’s default directory. <browse>: Select a directory using the file browser. <directory name>: Directory in which data files are already installed.
      Log directory	Directory in which the transaction log file is created. You have the following options: <default>: The database server’s default directory. <browse>: Select a directory using the file browser. <directory name>: Directory in which transaction log files are already installed.
      Memory tables directory	Directory for data file group and database file for memory-optimized tables. You have the following options: <default>: The database server’s default directory. <browse>: Select a directory using the file browser. <Directory name>: Directory in which data files for memory-optimized tables are already installed.
      Initial size	Initial size of the database files. You have the following options: <Default>: Default entry for the database server. <custom>: User-defined entry. Different recommended sizes: Depending on the number of identities being administrated.

   2. In the Installation source pane, select the directory with the installation files.

   - OR -

   If you are using an existing database, on the Create database page, Installation source view, select the directory containing the installation files.

5. On the Select configuration module page, select the configuration module .

   • If you started the Configuration Wizard from the install wizard, the configuration modules for the selected edition are already activated. In this case, check over the module selection.
   • Select the configuration module at this point if you started the Configuration Wizard directly. Dependent configuration modules are selected automatically.

6. Error that prevent processing the database are displayed on the Database check page. Correct the errors before you continue with the installation.

7. On the Create a new login for administrators page, decide which SQL server login to use for administrative users. You have the following options:

   • Create new SQL Server logins for the database: Select this option if you want to work with granular permissions.

     This sets up a new administrative login on the SQL Server.

     • Enter the login name, password, and password confirmation for the new SQL Server login.

     Later on in the process, the Configuration Wizard sets up additional SQL Server logins for the configuration user and the end user.

   • Use an existing SQL Server login: Select this option if you have already created an administrative SQL Server login and want to use this. Later on in the process, the Configuration Wizard sets up additional SQL Server logins for the configuration user and the end user.

     1. Enter the login name, password, and password confirmation for the SQL Server login.

     2. Set the Permissions option so that the SQL Server login obtains permissions for the database. If this option is not set, only the permissions are tested.

   • Use the current SQL Server login for the database: When you select this option, no additional SQL Server logins are created for the database. In this case, you cannot work with the granular permissions concept at SQL level. The user you specified is used to connect to the database.

     NOTE: To install the One Identity Manager schema in an existing database in Amazon RDS for SQL Server, select this option. The granular permissions concept is not supported.

     NOTE: If you want to switch to granular permissions at a later time, contact Support. To access the Support Portal, go to https://support.oneidentity.com/identity-manager/.

8. The installation steps are shown on the Processing database page.

   Installation and configuration of the database are automatically carried out by the Configuration Wizard. This procedure may take some time depending on the amount of data and system performance. Once processing is complete, click Next.

   TIP: Set Advanced to obtain detailed information about processing steps and the migration log.

9. On the Create SQL server logins page, enter the login name, the password, and password confirmation for the SQL Server logins for configuration users and end users.

   NOTE: The password must meet the Windows policy requirements for passwords.

10. On the System information page, enter the customer information and create administrative system users for One Identity Manager.

    1. In the Customer information view, enter the full name of the company.

    2. In the System user view, configure the predefined administrative system users and enter your own administrative system users.

       • Enter a password and password confirmation for the predefined system users.

       • To create customer-specific system users, click the button and enter the name, password, and password confirmation.

       TIP: Use the <...> button next to the name of a system user to configure additional settings for that system user. You can also adjust these settings in the Designer at a later time.

    3. (Optional) Create custom permissions groups.

       The Configuration Wizard creates custom permissions groups, which you can use to define permissions for any custom schema extensions you require.

       • For non role-based login, the CCCViewPermissions and CCCEditPermissions are created permission groups. Administrative system users are automatically added to these permissions groups.

       • For role-based login, the CCCViewRole and CCCEditRole permission groups are created.

       To create more permissions groups

       1. Enable the Advanced option and in the Permissions groups view, click the button.

       2. Enter the name of the permissions group. Label custom permission groups with the prefix CCC.

       3. For role-based permissions groups, enable the Role-based option.

11. On the Enable database encryption page, select one of the following options:

    • Skip database encryption: The database is not encrypted. You can encrypt the database at later date using the Crypto Configuration program.

    • Enable database encryption: The database is encrypted in the next step.

      1. In the Private key field, enter the name of the key file (default: private.key).

      2. Click New and, using the file browser, select the where you want to store the key file.

      3. Click Save.

         This generates the key file (*.key). This closes the file browser and displays the path and file name under Private key.

      4. Confirm that you have saved the key file.

         Take the Tips for working with an encrypted One Identity Manager database into account.

12. On the Service installation page, you can create a Job server for the server on which the One Identity Manager database is installed.

    NOTE: If you do not want to set up a Job server with the One Identity Manager Service at this stage, select the Skip service installation option.

    1. In the Installation data pane, enter the following data for installing the One Identity Manager Service.

       • Computer: Select the server, on which you want to install and start the service, from the menu or enter the server's name or IP address.

         To run the installation locally, select Local installation from the menu.

       • Service account: Enter the details of the user account that the One Identity Manager Service is running under. Enter the user account, the user account's password and password confirmation.

       The service is installed using the user account with which you are logged in to the administrative workstation. If you want to use another user account for installing the service, you can enter it in the advanced options.

       You can also change other One Identity Manager Service details in the advanced options, such as the installation directory, name, display name, and the One Identity Manager Service description.

    2. In the Machine roles pane, select the machine role for the service. By default, the Server | Job Server machine role is set. You can add more machine roles.

    3. (Optional) Enable the Advanced option and, in the Configuration pane, check the configuration of the One Identity Manager Service.

       NOTE: The initial service configuration is predefined already. If additional changes need to be made to the configuration, you can do this later with the Designer. For more information about configuring the One Identity Manager Service, see the One Identity Manager Configuration Guide.

    4. Click Next to start installing the service.

       Installation of the service occurs automatically and may take some time.

       NOTE: In a default installation, the service is entered in the server’s service management with the name One Identity Manager Service.

13. The Processing database tasks page only appears if there are still tasks for the DBQueue Processor queued in the DBQueue that are required for installing the database. Once processing is complete, click Next.

14. On the last page of the Configuration Wizard, click Finish.

Related topics

• Tips for setting up a One Identity Manager database
• Error messages when installing and updating the One Identity Manager database
• Editing a One Identity Manager database during setup using the Configuration Wizard
• Encrypting database information
• Tips for working with an encrypted One Identity Manager database