1. Analytical Applications Infrastructure
  2. Installation Tasks
  3. Configure the Schema Creator Utility
  4. Configure the Schema Creator Utility for RDBMS Installation

Configure the Schema Creator Utility for RDBMS Installation

Configure the OFS_<APP PACK>_SCHEMA_IN.xml file for RDBMS.

Add the Pack specific schema details for the following schema, present in the OFS_<App Pack>_SCHEMA_IN.xml file.

  • CONFIG: This schema holds the entities and other objects required for OFSAA setup configuration information. There can be only one CONFIG schema per OFSAA instance
  • ATOMIC: This schema holds the data model entities. One ATOMIC schema is attached to one Information Domain. There can be multiple ATOMIC schemas per OFSAA Instance.

Configure the OFS_<App Pack>_SCHEMA_IN.xml File

This section describes how to create database schemas, objects within schemas, and assigning appropriate grants.

Specify the database schemas required for the installation in the OFS_<APP PACK>_SCHEMA_IN.xml file. Update the values of the various tags and parameters available in this file before executing the schema creator utility.

This file must be configured only if the database is RDBMS.

To configure the <APP PACK>_SCHEMA_IN.xml file:

  1. Log in to the system as a non-root user.
  2. Navigate to the <APP PACK>/schema_creator/conf directory and configure the <APP PACK>_SCHEMA_IN.xml file based on the following parameters.
  3. Save the file.

    Table 7-2 OFS_<APP PACK>_SCHEMA_IN.xml File Parameters

    Tag /Attribute Name Details Default Value/ Permissible Value
    <APP_PACK_ID> Seeded unique ID for the OFSSAA Application Pack.

    Do not modify this value.

    		 Seeded
    <IS_TCPS> Enter if the TCPS configuration is required.

    Modify this to TRUE if you require the installer to uptake the configuration.

    		Seeded, with FALSE as the default value.
    <JDBC_URL> Enter the JDBC URL.

    You can enter the following JDBC URL types:

    1. RAC/ NON-RAC enabled database connectivity URL.
    2. TCPS RAC/ NON-RAC enabled database connectivity URL provided the <IS_TCPS> tag value is TRUE.
    3. Wallet-enabled JDBC URL.

    Ensure to add an entry (with SID/ SERVICE NAME) in the tnsnames.ora file on the OFSAA server. The entry must match with the SID/ SERVICE NAME used in the JDBC URL.

    Ensure that you have configured:
    1. The correct Oracle Wallet with the credentials for stored Sys, Config, and Atomic Users.
    2. The JDBC URL as: jdbc:oracle:thin:/@
    For more information on how to configure Oracle Wallets for OFSAA Installation and Data Sources, refer to the OFS Analytical Applications Infrastructure Administration Guide.
    		Example 1:

    jdbc:oracle:thin:@< DBSERVER IP/ HOST/ IP>:<PORT>:<SID>

    Example 2:

    jdbc:oracle:thin:@//[HOS T][:PORT]/ SERVICE

    Example 3: 

    jdbc:oracle:thin:@(DESCRI
PTION=(ADDRESS_ LIST=(ADDRESS=(PROT
OCOL=TCP)(HOST=[HO
ST])(port=[PORT]))(ADD
RESS=(PROTOCOL=TCP)
(HOST=[HOST])(PORT=[ PORT]))(LOAD_
BALANCE=yes)(FAILOV
ER=yes))(CONNECT_ DATA=(SERVICE_
NAME=[SERVICE])))

    Example 4: 

    jdbc:oracle:thin:@//dbhos
t.server.com:1521/service 1

    Example 5: 

    jdbc:oracle:thin:@//dbsho
st.server.com:1521/scan-1

    Example 6: 

    jdbc:oracle:thin:@(DESCRI
PTION=(ADDRESS_ LIST=(ADDRESS=(PROT
OCOL=TCP)(HOST=dbhost1.server.com)
(port=1521))(ADDRESS=(PROTOCOL=TCP)(H
OST=dbhost2.s erver.com)(PORT=1521))(LOAD_BALANCE=yes)(FAILOV
ER=yes))(CONNECT_
DATA=(SERVICE_NAME=service1)))

    Example 7: 

    <JDBC_URL>jdbc:oracle:thin:@(DESCRIPTIO
N = (ADDRESS = (PROTOCOL =TCPS)(HOST
= dbhost.server.com)(PORT = 2484))
(CONNECT_DATA =(SERVER = DEDICATED)
(SERVICE_NAME=SERVICEID))(security=(ssl
_server_cert_dn=CN=dbhost)))

    Example 8:

    jdbc:oracle:thin:/@
    <JDBC_DRIVER> This driver's name is seeded by default.

    Only JDBC Thin Driver is supported.

    Do not modify this value.

    		 Example:

    oracle.jdbc.driver.OracleDriver
    <HOST> Enter the Host name/ IP Address of the system on which you are installing the OFSAA components. Host Name/ IP Address
    <SETUPINFO>/PREFIX_SCHEMA_NAME (Optional). Identifies whether the value specified in <SETUPINFO>/NAME attribute must be prefixed to the schema name.

    The default value is YES.

    		YES or NO
    <SETUPINFO>/NAME Enter the acronym for the type of implementation. This information is displayed in the OFSAA Home Page.

    On executing the schema creator utility, this value is prefixed with each schema name. For example: dev_ofsaaconf, uat_ofsaatm.

    This name appears in the OFSAA Landing Page as Connected To: xxxx.

    		Accepts strings with a minimum length of two and a maximum of four. Example: DEV, SIT, PROD
    <PASSWORD>/ DEFAULT* (Optional). Enter the password if you want to set a default password for all schemas.

    You also must set the APPLYSAMEFORALL attribute as Y to apply the default password for all the schemas.

    On successful execution of the utility, the entered password in the OFS_<APP PACK>_SCHEMA_IN.xml file is cleared.

    		The maximum length allowed is 30 characters. Special characters are not allowed.
    <PASSWORD>/ APPLYSAMEFORALL If you have entered Y in APPLYSAMEFORALL attribute and also have specified individual passwords for all the schemas, then the specified individual passwords will take precedence.

    Setting this attribute value is mandatory if the DEFAULT attribute is set.

    		Default N Permissible: Y or N

    Enter Y if you want to apply the password specified in the DEFAULT attribute for all the schemas.

    If you enter as N, you must provide individual passwords for all schemas.

    <SCHEMA>/TYPE The different types of schemas that are supported in this release are ATOMIC, CONFIG, SANDBOX, and ADDON.

    By default, the schemas types are seeded based on the Application Pack.

    Only One CONFIG schema can exist in the file.

    Do not edit this attribute value.

    This schema identifies as the CONFIGURATION schema that holds the OFSAA setup detains and other Metadata information.

    Multiple ATOMIC/ SANDBOX/ADDON schemas can exist in the file.

    		 ATOMIC/CONFIG/SANDBOX/ADDON

    SANDBOX and ADDON schemas do not apply to OFSAAI.
    <SCHEMA>/NAME The schemas’ names are seeded based on the Application Pack by default.

    You can edit the schema names if required.

    The Schema Name will have a prefix of the SETUPINFO/NAME attribute.

    SCHEMA NAME must be the same for all the ATOMIC Schemas of the applications within an Application Pack.

    SETUPOINFO/NAME attribute value is prefixed to the schema name being created.

    For example, if a name is set as ofsaatm and setupinfo as uat, then schema being created is uat_ofsaatm.

    NAME must be the same where APP_GRP=1 for all SCHEMA tags (Not applicable for this Application Pack).

    		The permissible length is 15 characters and only alphanumeric characters are allowed. No special characters allowed except underscore '_'.
    <SCHEMA>/PASSWORD (Optional). Enter the password of the schema to be created.

    If this attribute is left blank, then the password specified in the <PASSWORD>/DEFAULT attribute is applied as the Schema Password.

    It is mandatory to enter the password if you have set the <PASSWORD>/ APPLYSAMEFORALL attribute as N.

    		The maximum length allowed is 30 characters. Special characters are not allowed.
    <SCHEMA>/APP_ID The Application ID is seeded based on the Application Pack by default.

    Identifies the Application/ Product for which the schema is being created. Do not edit this attribute value.

    		 Unique Seeded Value
    <SCHEMA>/DEFAULTTABLESPACE (Optional). Enter the available default tablespace for DB User.

    If this attribute is left blank, then USERS is set as the default tablespace.

    Modify this value to associate any valid tablespace with the schema.

    		 Default USERS

    Permissible Any existing valid tablespace name.
    <SCHEMA>/TEMPTABLESPACE (Optional). Enter the available temporary tablespace for DB User.

    If this attribute is left bank, TEMP is set as the default tablespace.

    Modify this value to associate any valid tablespace with the schema.

    		 Default TEMP

    Permissible Any existing valid temporary tablespace name.
    <SCHEMA>/QUOTA Enter the quota to be set on the DEFAULTTABLESPACE attribute for the schema/ user. By default, the quota size is set to 500M.

    Minimum: 500M or Unlimited on default Tablespace.

    Modify this value to grant the specified quota on the mentioned tablespace to the user.

    Example:

    600M/ m

    20G/ g

    UNLIMITED/ unlimited
    <SCHEMA>/ INFODOM (Optional). Enter the name of the Information Domain to associate this schema.

    The schema creator utility automatically derives an Information Domain Name based on the Application Pack if no value is specified for this attribute.

    		 Permissible length is 16 characters and only alphanumeric characters are allowed. No special characters are allowed.
    <ADV_SEC_OPTIONS>/ (Optional). Parent tag to hold Advance Security Options.

    Uncomment the tag and edit if you want to add security options. For example, TDE and Data Redact.

    For details, see the example in the comments for the <TABLESPACE>/ENCRYPT tag.

    <ADV_SEC_OPTIONS>/TDE (Optional). Tag to enable/disable TDE.

    Ensure this tag is not commented if you have uncommented <ADV_SEC_OPTIONS>

    		 The default is FALSE. To enable TDE, set this to TRUE.
    <ADV_SEC_OPTIONS>/DATA_REDACT (Optional). Tag to enable/disable the Data Redaction feature.

    Ensure this tag is not commented if you have uncommented <ADV_SEC_OPTIONS>

    		 The default is FALSE. To enable DATA_REDACT, set this to TRUE
    <TABLESPACES> (Optional). Parent tag to hold <TABLESPACE> elements

    Uncomment the tag and edit. ONLY if tablespaces are to be created as part of the installation.

    For details, see the example following the table.

    When TDE is TRUE in ADV_SEC_OPTIONS, then it is mandatory for the <TABLESPACES> tag to be present in the XML file.

    		NA
    <TABLESPACE>/NAME Logical Name of the tablespace to be created.

    Name, if specified, must be referred in the <SCHEMA DEFAULTTABLESPACE= "##NAME##"> attribute.

    Note the ## syntax.
    <TABLESPACE>/VALUE Physical Name of the tablespace to be created.

    Value, if specified, is the actual name of the TABLESPACE.

    		 NA
    <TABLESPACE>/DATAFILE Specifies the location of the data file on the server.

    Enter the absolute path of the file to be created.

    		 NA
    <TABLESPACE>/AUTOEXTEND Specifies if the tablespace must be extensible or have a hard limit.

    Set to ON to ensure that the tablespace does not run out of space when full.

    		 ON or OFF
    <TABLESPACE>/ENCRYPT Specifies if the tablespace(s) must be encrypted using TDE.

    Set to ON to ensure that the tablespaces when created are encrypted using TDE.

    Encryption of tablespaces requires enabling Transparent Data Encryption (TDE) on the Database Server.

    Example: The following snippet shows that TDE is enabled and hence the tablespace is shown with encryption ON. 

    <ADV_SEC_OPTIONS>
<OPTION NAME="TDE"
VALUE="FALSE"/>
<OPTION NAME="DATA_REDACT"
VALUE="FALSE" />
</ADV_SEC_OPTIONS>
<TABLESPACES>
<TABLESPACE
NAME="OFS_AAI_TBSP_1"
VALUE="TS_USERS1" DATAFILE="/
scratch/ora19c/app/oracle/orada
ta/OFSPQA19cDB/ts_users1.dbf"
SIZE="500M" AUTOEXTEND="ON"
ENCRYPT="ON" />
<TABLESPACE
NAME="OFS_AAI_TBSP_2"
VALUE="TS_USERS2" DATAFILE="/
scratch/ora19c/app/oracle/orada
ta/OFSPQA19cDB/ts_users2.dbf"
SIZE="500M" AUTOEXTEND="ON"
ENCRYPT="ON" />
</TABLESPACES>

<SCHEMAS>
<SCHEMA TYPE="CONFIG"
NAME="ofsaaconf" PASSWORD=""
APP_ID="OFS_AAI"
DEFAULTTABLESPACE="##OFS_AAI_TB
SP_1##" TEMPTABLESPACE="TEMP"
QUOTA="unlimited"/>
<SCHEMA TYPE="ATOMIC"
NAME="ofsaaatm" PASSWORD=""
APP_ID="OFS_AAAI"
DEFAULTTABLESPACE="##OFS_AAI_TB
SP_2##" TEMPTABLESPACE="TEMP"
QUOTA="unlimited"
INFODOM="OFSAAAIINFO"/>
</SCHEMAS>
    		 ON or OFF