Configure Oracle Database

These tasks must be completed before HCM ARA is installed.

Note These tasks are relevant to both embedded and external Operations Orchestration, except where indicated.

Create Oracle database instances for HCM ARA

Separate database instances are required for Application Release Automation and the components it uses. You must create a separate database instance for:

  • Embedded Operations Orchestration - only if you use embedded Operations Orchestration
  • Identity Management component
  • Application Release Automation

Work with the database administrator to create a database that is used by the embedded Operations Orchestration, Application Release Automation (if it has not already been created), and the Identity Management component. See the Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.

You must provide the service name (global database name) of these databases when prompted for the database information during the installation of Application Release Automation. For example, when prompted for the Application Release Automation database information, provide the service of the Application Release Automation database. When prompted for the Identity Management component database information, provide the service name of the Identity Management component database. When prompted for the embedded Operations Orchestration database information, provide the service name of the embedded Operations Orchestration database.

Tip You can run the following query to find the SERVICE_NAME on the Oracle 12c/11g systems:

select global_name from global_name;

Configure Oracle database user and role for HCM ARA

A database user is needed when installing HCM ARA. Work with the database administrator to configure the database role and user (or see the manufacturer’s documentation for more information).

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 configure an Oracle database user and role for HCM ARA, complete the following steps:

  1. Create a schema for HCM ARA by creating a database user (for example, codardbuser).

  2. Create a role for this HCM ARA database user (for example, codardbrole) and grant the following privileges to the role:

    • CREATE SESSION
    • CREATE TABLE
    • CREATE VIEW
    • CREATE SEQUENCE
    • CREATE ANY SYNONYM
    • UNLIMITED TABLESPACE
  3. Grant the role to the HCM ARA database user.
  4. Alter the HCM ARA database user by setting this role as the user's default role.

For example, run the following commands to create codardbrole and codardbuser:

Create user codardbuser identified by codardbuser;
Create role codardbrole;
Grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE ANY SYNONYM, UNLIMITED TABLESPACE to codardbuser;
Grant codardbrole to codardbuser;
Alter user codardbuser default role codardbrole;

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

5. Create a user for the Workflow Designer component (for example, codarooddbuser) ) with permissions to create sessions, tables and to store data to the default tablespace. (Replace the <codarooddbuser_password> token with your desired user password.)

create user codarooddbuser

identified by "<codarooddbuser_password>";

grant CREATE SESSION, CREATE TABLE, UNLIMITED TABLESPACE to codarooddbuser;

Provide this username and password when prompted for the Workflow Designer component database information during the installation of Codar.

NOTE: If you are using Oracle 11g R2 or 11g R2 RAC, it is recommended to apply patch 20299013 before installing Operations Orchestration.

Configure a reporting 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 an Oracle 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.

Work with the database administrator to create a role and read-only user to do the following (or see the manufacturer’s documentation for more information).

Caution On Windows, the 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 and configure a reporting database role and read-only user for HCM ARA and Cloud Service Automation, complete the following steps:

  1. Create a database user (for example, CODARReportingDBUser).

  2. Create a role for this HCM ARA database user (for example, CODARReportingDBRole) and grant the CREATE SESSION privilege to the role.

  3. Grant the role to the HCM ARA database user.
  4. Alter the HCM ARA database user by setting this role as the user's default role.

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

Create user CODARReportingDBUser identified by CODARReportingDBUser;
Create role CODARReportingDBRole;
Grant CREATE SESSION to CODARReportingDBUser;
Grant CODARReportingDBRole to CODARReportingDBUser;
Alter user CODARReportingDBUser default role CODARReportingDBRole;

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 Oracle database user and role for Identity Management component

A database user is needed when installing Identity Management component for HCM ARA. Work with the database administrator to do the following (or see the manufacturer’s documentation for more information).

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 configure an Oracle database role and user for Identity Management component, complete the following steps:

  1. Create a schema for the Identity Management component by creating a database user (for example, codaridmdbuser).

  2. Create a role for this HCM ARA database user (for example, codaridmdbrole) and grant the following privileges to the role:

    • CREATE SESSION
    • CREATE TABLE
    • CREATE VIEW
    • CREATE SEQUENCE
    • CREATE ANY SYNONYM
    • UNLIMITED TABLESPACE
  3. Grant the role to the HCM ARA database user.
  4. Alter the HCM ARA database user by setting this role as the user's default role.

For example, run the following commands to create codaridmdbrole and codaridmdbuser:

Create user codaridmdbuser identified by codaridmdbuser;
Create role codaridmdbrole;
Grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE ANY SYNONYM, UNLIMITED TABLESPACE to codaridmdbuser;
Grant codaridmdbrole to codaridmdbuser;
Alter user codaridmdbuser default role codaridmdbrole;

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

Configure Oracle database user and schema for embedded Operations Orchestration

A database user for embedded Operations Orchestration is required when installing HCM ARA. Work with the database administrator to do the following (or see the manufacturer’s documentation for more information):

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.

  1. Create a schema for the embedded Operations Orchestration by creating a database user (for example, codaroodbuser).

  2. Create a role for the user (for example, codaroodbrole) and grant the following privileges to the role:

    • CONNECT
    • CREATE VIEW
    • CREATE SEQUENCE
    • CREATE TABLE
    • CREATE PROCEDURE
    • UNLIMITED TABLESPACE
  3. Grant the role to the HCM ARA database user.

For example, run the following commands to create the codaroodbuser user:

Create user codaroodbuser identified by codaroodbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to codaroodbuser;
Grant CREATE VIEW, CREATE SEQUENCE, CREATE TABLE, CREATE PROCEDURE, UNLIMITED TABLESPACE to codaroodbuser;
Commit;

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

Configure Oracle for FIPS 140-2 compliance (required for FIPS 140-2 compliance)

If you are configuring HCM ARA to be compliant with FIPS 140-2, work with your database administrator to configure your Oracle database to be compliant with FIPS 140-2. You can also see this document for more information: http://docs.oracle.com/cd/B28359_01/network.111/b28530/asoappe.htm

Import Oracle's certificate as trusted certificate (required for FIPS 140-2 compliance)

If you are configuring HCM ARA to be compliant with FIPS 140-2, configure the JRE (that is used exclusively by HCM ARA) so it trusts the Oracle certificate.

  1. Obtain a copy of the Oracle certificate and copy it to the system on which HCM ARA will be installed.
  2. Change to the <codar_jre> directory where CSA_JRE_HOME is the directory in which the JRE used by HCM ARA is installed.

    Run the following command:

    .\bin\keytool -importcert -alias <oracle_alias> -file <oracle_certificate_path_and_filename> -keystore .\lib\security\cacerts -storepass changeit.bin/keytool -importcert -alias <oracle_alias> -file <oracle_certificate_path_and_filename> -keystore ./lib/security/cacerts -storepass changeit

  3. When prompted to trust the certificate, enter yes.

Configure Oracle for localization (required for localization)

If you need to support localization, the Oracle database instance must support UTF-8 character encoding and multi-byte characters. Work with the database administrator to set the following parameters to the specified values (or see the manufacturer’s documentation for more information):

  • NLS_CHARACTERSET = AL32UTF8
  • NLS_LENGTH_SEMANTICS = CHAR

Create Oracle tablespace for HCM ARA (recommended)

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

Note The tablespace must be created before installing HCM ARA and then must be configured immediately after HCM ARA is installed.

Send Help Center feedback