Migrating the IdP Server Database - Identity and Access Management Services - 4.2 - 4.2 - Public - Other - external

Identity and Access Management Services
Platform
Other
Product
Identity and Access Management Services
Release
4.2
License

When upgrading to a Hyland IdP version of 2.11.0 or above, you must run the DatabaseMigration command to ensure database compatibility with the Hyland IdP version you are upgrading to.

To migrate the IdP Server database:

  1. Open a command prompt with administrator privileges.
  2. In the command prompt, navigate to the location of the Hyland Identity Provider Server Database Migration Utility folder. In a default installation, this is located at C:\Program Files\Hyland\Hyland Identity Provider Server Database Migration Utility
  3. Type the DatabaseMigration command, but do not run it yet:
    dotnet .\Hyland.Identity.Migration.Utility.dll DatabaseMigration
  4. Append the following switches and their values to the DatabaseMigration command. Be sure to enclose the values in double quotation marks.

    Switch

    Value

    --connectionString

    The valid ADO.NET connection string you created for the operational database. The connection string should contain the following variables in double quotations:

    • Data Source

    • Database

    • User Id

    • Password

    An example SQL connection string may look like this:

    Data Source=PROD-MACHINE\SQLInstance;database=MyDatabase; User Id=UserName;Password=UserPassword;

    An example Oracle connection string may look like this:

    Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=PROD-MACHINE)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=MyDatabase)));User Id=hsiidp;Password=UserPassword;direct=true;

    Tip:

    ADO.NET connection strings are a method of connecting applications to databases. Complete details on connection strings and how to create them are available from Microsoft.

    --databaseProvider

    The provider type of the database.

    Enter SqlServer for a SQL database, or Oracle for an Oracle database.

    Note:

    The values are case sensitive.

    For example, a completed DatabaseMigration command for a SQL database may look like this:

    dotnet Hyland.Identity.Migration.Utility.dll DatabaseMigration --connectionString "Data Source=PROD-MACHINE\SQLInstance;database=MyDatabase;User Id=UserName;Password=UserPassword;" --databaseProvider "SqlServer"

  5. Press Enter to run the DatabaseMigration command.
    If any errors are displayed, correct the errors and run the command again. Success messages are displayed if no errors are encountered.
  6. Close the command prompt window.