Configure Microsoft SQL Server

The following tasks must be completed before HCM ARA is installed. Work with the database administrator to complete these tasks, or see the manufacturer’s documentation for more information.

Note These tasks are used with both embedded and external Operations Orchestration, except where indicated.

Enable TCP/IP on Microsoft SQL server

TCP/IP must be enabled on the Microsoft SQL Server forHCM ARA to access the database. By default, TCP/IP may be disabled on the Microsoft SQL Server. Verify the TCP/IP configuration.

From the SQL Server Configuration Manager, complete the following steps:

  1. Select SQL Server Network Configuration > Protocols for <instance_name>.
  2. Double-Click TCP/IP to open the TCP/IP Properties dialog.
  3. From the TCP/IP Properties dialog, select the IP Addresses tab.
  4. Verify that TCP/IP is active and enabled, and verify that the TCP port is set to 1433. Update any properties that are not set correctly.

Configure Microsoft SQL server database user for HCM ARA

A HCM ARA database user is needed when installing HCM ARA.

You must configure HCM ARA with Microsoft SQL internal users. HCM ARA does not support configuring with NT or LDAP users.

Caution On Windows, the database name and user name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

To create a database user for HCM ARA, complete the following steps:

  1. Create a new database for HCM ARA (for example, codardb)

    Caution Use the default database option collation value of SQL_Latin1_General_CP1_CI_AS.

    Do NOT use the collation value SQL_Latin1_General_CP1_CS_AS. HCM ARA does not work with a database that is configured with this collation value.

    1. Add a database user (for example, codardbuser) with the following roles:

      • db_datareader
      • db_datawriter
      • db_owner

        For example, run the following commands to create the codardbuser user with the specified roles:

        Microsoft SQL Server 2012

        USE codardb; -- or connect to codardb in another way
        CREATE LOGIN codardbuser WITH PASSWORD = '<codardbuser_password>';
        CREATE USER codardbuser FOR LOGIN codardbuser;
        ALTER ROLE db_datareader ADD MEMBER codardbuser;
        ALTER ROLE db_datawriter ADD MEMBER codardbuser;
        ALTER ROLE db_owner ADD MEMBER codardbuser;

    3. You must provide this user name and password when prompted for the Codar database user during the installation of Application Release Automation.

  3. Create a new database for the Workflow Designer component and a user (for example, csaooddbuser) within the database with the db_owner role:

    CREATE DATABASE ooddb;

    USE ooddb; -- or you can connect to ooddb in another way.

    CREATE USER codardbuser FOR LOGIN codardbuser;

    ALTER ROLE db_owner ADD MEMBER codardbuser;

    It is recommended to set following parameters on ooddb database:

    ALTER DATABASE ooddb SET ALLOW_SNAPSHOT_ISOLATION ON;

    ALTER DATABASE ooddb SET READ_COMMITTED_SNAPSHOT ON;

    Caution: The Workflow Designer requires 'Case Insensitive' Collation of the database. The Workflow Designer database collation and the tempDB collation in SQL server must be the same. Provide this database name when prompted for the Workflow Designer component database information during the installation of Codar.

Configure Microsoft SQL reporting database role and read-only user for HCM ARA (required for reporting)

If you are using both the Cloud Service Automation and HCM ARA licenses, you can use the Cloud Service Automation reporting capabilities. If you want to use the reporting capabilities, you must add a Microsoft SQL reporting database role and read-only user when installing HCM ARA. For details about the Cloud Service Automation reporting capabilities, see the Cloud Service Automation Reporting and Auditing Whitepaper.

Note You must apply both the Cloud Service Automation and HCM ARA licenses to use the reporting capabilities.

Caution On Windows, the database name and user name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

Add a reporting database user to the HCM ARA database with no roles.

For example, run the following commands to create the CODARReportingDBUser read-only user:

CREATE LOGIN CODARReportingDBUser WITH PASSWORD = '<codarreportingdbuser_password>';
CREATE USER CODARReportingDBUser FOR LOGIN CODARReportingDBUser WITH DEFAULT_SCHEMA = codar;

If you configure this user, you must provide this user's user name and password when prompted for the HCM ARA reporting database user during the installation of HCM ARA.

Configure Microsoft SQL server database user for Identity Management component

An Identity Management component database user is needed when installing HCM ARA.

Caution On Windows, the database name and user name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

To create an Identity Management component database user for HCM ARA, complete the following steps:

  1. Create a new database for the Identity Management component (for example, codaridmdb).

    Caution Use the default database option Collation value of SQL_Latin1_General_CP1_Cl_AS.

    Do NOT use the collation value SQL_Latin1_General_CP1_CS_AS. HCM ARA does not work with a database configured with this collation value.

  2. You can use the existing database user you created for the HCM ARA database (for example, codardbuser) or you may create a new database user for the Identity Management component database (for example, codaridmdbuser). If you create a new user, add an Identity Management component database user with the following roles:

    • db_datareader
    • db_datawriter
    • db_owner

    You must provide this database user name and, user's password when prompted for the Identity Management component database information during the installation of HCM ARA.

Configure Microsoft SQL server database user for embedded Operations Orchestration

An Operations Orchestration database user for embedded Operations Orchestration is needed when installing HCM ARA.

Caution On Windows, the database name and user name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

To create an Operations Orchestration database user for HCM ARA, complete the following steps:

  1. Create a new database for Operations Orchestration.

    As of the release date of the Codar software (found at the beginning of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:

    • Allow Snapshot Isolation: True
    • Is Read Committed Snapshot On: True
    • Auto Shrink: False
    • Auto Create Statistics: True

    Caution You should verify the latest mandatory options and follow the instructions in the Operations Orchestration Database Guide when creating the Operations Orchestration database.

    Note Operations Orchestration recommends using the database option collation value of SQL_Latin1_General_CP1_CS_AS. When creating the database used by Operations Orchestration, this collation value is valid.

  2. Create a new user for Operations Orchestration database (for example, codaroodbuser) and assign the following roles to that user:

    • db_datareader
    • db_datawriter
    • db_owner

You must provide this user name and password when prompted for the Operations Orchestration database user during the installation of HCM ARA.

Create Microsoft SQL Server filegroup with embedded Operations Orchestration

If you chose to install embedded Operations Orchestration, for performance reasons, HPE recommends that you associate a new filegroup with the CSA_DOCUMENT table. Work with the database administrator to configure a filegroup to be used by HCM ARA (or see the manufacturer’s documentation for more information). HPE recommends that the initial filegroup size should be at least 3 GB.

The filegroup is configured after HCM ARA is installed.

Send Help Center feedback