Installation Overview

Refer to Supported Database Platforms for information about the supported platforms on which Oracle Utilities Digital Asset Management is verified to operate.

The following types of installation are available for Oracle Utilities Digital Asset Management:

• Initial Install: A database with no demo data.

• Upgrade Install: A database upgrade to V2.0.0.1.3 from V2.0.0.1.2, V2.0.0.1.1, or V2.0.0.1.0.

• Demo Install: A database populated with demo data.

The database installation requires a supported version of the Java Development Kit Version 8.0 and Oracle 19c 32-bit client installed on the Windows 64-bit or 32-bit desktop where the install package is staged and run.

Creating the Database

For an initial install or demo install you will create an empty database on the Unix or Windows database server on which you operate the production instance of Oracle Utilities Digital Asset Management.

1. Create the database.

a. For traditional on-premise database:

a. Create the database using the Database Configuration Assistant (DBCA).

b. Refer to the article Master Note: Overview of Database Configuration Assistant (DBCA) (Doc ID 1488770.1) on My Oracle Support for more information. Make sure to set character set for database as follows:

• Character set for database as AL32UTF8

• National Character Set (NLS_NCHAR_CHARACTERSET - AL16UTF16)

b. For cloud database (ADB):

The pre-requisites to create an autonomous database are as follows:

a. Access to Oracle Cloud Infrastructure (OCI) is a must.

a. Login using your Cloud Account Name/Tenancy and Identity Provider if Single Sign-on (SSO) or Oracle Cloud Infrastructure Direct Sign-In.

b. Create the database following your organization's standards.

Note: Take note of the administrator credentials. It will be needed upon connecting to the new ADB.

c. Set up the connection to ADB.

a. Download Instance Wallet from OCI.

b. Unzip the downloaded wallet and set the wallet location as TNS ADMIN

export TNS_ADMIN=<wallet location>

c. Modify the files from ADB wallet.

Edit sqlnet.ora and update DIRECTORY parameter.

WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="<wallet location>")))

Edit ojdbc.properties. Update javax.net.ssl.trustStorePassword and javax.net.ssl.keyStorePassword with your wallet password. Comment this line: oracle.net.wallet_location=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=${TNS_ADMIN})))

File should look like this:

# Connection property while using Oracle wallets.

#oracle.net.wallet_location=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=${TNS_ADMIN})))

# FOLLOW THESE STEPS FOR USING JKS

# (1) Uncomment the following properties to use JKS.

# (2) Comment out the oracle.net.wallet_location property above

# (3) Set the correct password for both trustStorePassword and keyStorePassword.

# It's the password you specified when downloading the wallet from OCI Console or the Service Console.

javax.net.ssl.trustStore=<wallet location>/truststore.jks

javax.net.ssl.trustStorePassword=<wallet password>

javax.net.ssl.keyStore=<wallet location>/keystore.jks

javax.net.ssl.keyStorePassword=<wallet password>

d. Verify DB connection using TNSNAMES from tnsnames.ora.

sqlplus USERNAME/password@<tnsname>

2. Enable the mandatory software options.

• Oracle Spatial OR Oracle Locator

• Oracle Text

Note: This step is applicable for on-premises databases only.

3. Run the following SQL to make sure it is successful.

SELECT COMP_NAME,STATUS FROM DBA_REGISTRY WHERE COMP_NAME IN ('Spatial','Oracle Text');

Note: This step is applicable for on-premises databases only.

Note that starting version 4.4.0.0.0, Oracle Utilities Application Framework database users are assigned only the minimum set of privileges needed to be able to perform their required job functions. This privilege assignment is based on 'Principle of Least Privilege' and is implemented with a view to make the application more secure.

4. Enable the Extended Data Types by setting DB parameter, max_string_size = EXTENDED.

Follow the instructions provided in Oracle database documentation.

Note: This step is applicable for on-premises databases only.

5. Create the default tablespace CISTS_01 and the required users and roles.

Note: For ADB, make sure the connection is working. Refer to step 1.b.a.c in this section.

Create required roles:

CREATE ROLE CIS_ADM NOT IDENTIFIED;

CREATE ROLE CIS_USER NOT IDENTIFIED;

CREATE ROLE CIS_READ NOT IDENTIFIED;

Grant privileges to roles:

GRANT CREATE TABLE TO CIS_ADM;

GRANT CREATE VIEW TO CIS_ADM;

GRANT CREATE SYNONYM TO CIS_ADM;

GRANT CREATE MATERIALIZED VIEW TO CIS_ADM;

GRANT CREATE SEQUENCE TO CIS_ADM;

GRANT CREATE INDEXTYPE TO CIS_ADM;

GRANT CREATE ROLE TO CIS_ADM;

GRANT CREATE TRIGGER TO CIS_ADM;

GRANT CREATE PROCEDURE TO CIS_ADM;

GRANT CREATE SYNONYM TO CIS_USER;

GRANT CREATE SYNONYM TO CIS_READ;

Note: Follow the password requirement(s) for ADB user creation and update with the Oracle provided tablespace DATA.

Create schema owner (CISADM):

• On-premises:

CREATE USER CISADM IDENTIFIED BY CISADM DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP PROFILE DEFAULT;

ALTER USER CISADM QUOTA UNLIMITED ON CISTS_01;

• ADB:

CREATE USER CISADM IDENTIFIED BY CISADM DEFAULT TABLESPACE DATA TEMPORARY TABLESPACE TEMP PROFILE DEFAULT;

ALTER USER CISADM QUOTA UNLIMITED ON DATA;

Grant privileges and roles to schema owner (CISADM):

GRANT CREATE SESSION TO CISADM;

GRANT CREATE TABLESPACE TO CISADM;

GRANT READ on DBA_TABLESPACES TO CISADM;

GRANT ALTER TABLESPACE TO CISADM;

GRANT UNLIMITED TABLESPACE TO CISADM;

GRANT DROP TABLESPACE TO CISADM;

GRANT EXECUTE on DBMS_UTILITY TO CISADM;

GRANT SELECT_CATALOG_ROLE TO CISADM;

GRANT CIS_ADM TO CISADM;

GRANT EXECUTE_CATALOG_ROLE TO CISADM;

Enable DBMS_CRYPTO package:

Execute the following command as SYS for on-premises and as ADMIN for ADB.

Grant execute on dbms_crypto to CISADM;

Enable DBMS_RLS package:

Execute the following command as SYS for on-premise and as ADMIN for ADB.

grant execute on dbms_rls to CISADM;

Create Read Write user (CISUSER):

• On-premises:

CREATE USER CISUSER PROFILE DEFAULT IDENTIFIED BY CISUSER DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

ALTER USER CISUSER QUOTA UNLIMITED ON CISTS_01;

• ADB:

CREATE USER CISUSER PROFILE DEFAULT IDENTIFIED BY CISUSER DEFAULT TABLESPACE DATA TEMPORARY TABLESPACE TEMP;

ALTER USER CISUSER QUOTA UNLIMITED ON DATA;

Grant privileges and roles to Read Write user (CISUSER):

GRANT CIS_USER to CISUSER;

GRANT CREATE SESSION TO CISUSER;

Create Read Only user (CISREAD):

• On-premises:

CREATE USER CISREAD IDENTIFIED BY CISREAD DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

ALTER USER CISREAD QUOTA UNLIMITED ON CISTS_01;

• ADB:

CREATE USER CISREAD IDENTIFIED BY CISREAD DEFAULT TABLESPACE DATA TEMPORARY TABLESPACE TEMP;

ALTER USER CISREAD QUOTA UNLIMITED ON DATA;

Grant privileges and roles to Read Only User (CISREAD):

GRANT CIS_READ to CISREAD;

GRANT CREATE SESSION TO CISREAD;

Create Operational User (CISOPR):

CREATE USER CISOPR PROFILE DEFAULT IDENTIFIED BY OPRPLUS DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT CREATE SESSION,EXP_FULL_DATABASE TO CISOPR;

Note: Oracle Utilities Application Framework and Oracle Utilities Digital Asset Management do not use the database edition feature. Hence, the product does not make schema (CISADM) explicitly editionable.

6. Review the Storage.xml file under the FW45013\Install-Upgrade folder prior to an initial install or upgrade install.

This file allocates all base tables and indexes to the default tablespace CISTS_01 and the required users and roles. Information in this file is used by spl-oradbi-4.5.0.1.3.jar while installing the Oracle Utilities Digital Asset Management database objects. Refer to Updating Storage.xml for more details on updating this file.

Note: Review the Storage.xml file, prior to an initial install, to update the default values to custom values (example: TableSpace Name). spl-oradbi-4.5.0.1.3.jar can be executed by a non- schema owner in order to upgrade the database. The Initial Install still needs to be done by the schema owner.

If you decide to allocate some tables or indexes outside of the default tablespace, change the tablespace name from the default value to a custom value in the Storage.xml file.

For instance, if you decide to allocate table CI_ACCT in a tablespace MyTablespace, change Storage.xml as shown:

<CI_ACCT>

<TABLESPACE>MyTablespace</TABLESPACE>

</CI_ACCT>

Note: For ADB, tablespaces cannot be created manually. Storage.xml file should be updated with the Oracle provided tablespace DATA.

<CI_ACCT>

</CI_ACCT>

For optimum storage allocation, database administrators should create multiple tablespaces with extents sized to store different types of tables/indexes. They can then edit the storage.xml file before install process, to spread tables and indexes across these tablespaces. Tables and indexes can be created in parallel by editing degree of parallelism. Tablespace, storage options, secure file options, Advanced Compression, and parallel information are used only for new objects. Therefore, for initial installs, information for each object should be reviewed. Be careful while editing this file. Make sure that tablespace names being used exist in the database. Do not change the basic format of this file.

Note: Prior to the installation of the database schema for the product, please ensure that the Database Management System software is installed according to your site standards and the installation guide provided by the database vendor. Also, make sure that you have necessary licenses to use some of the advanced database features such as Advanced Compression.