18.2 Configuring OFS_SANC_SCHEMA_IN.xml file

Creating database schemas, objects within schemas and assigning appropriate grants are the primary steps in the installation process of OFSAA Applications. The OFS_SANC_PACK>>_SCHEMA_IN.xml file contains details on the various application schemas that should be created prior to the Application Pack installation.

Note:

This file should be configured only in case of OFS Sanctions Pack installation for RDBMS ONLY target. This file is not required to be configured for an HDFS ONLY target installation.

The following table gives details about the various tags/ parameters available in the file and the values that need to be updated. Prior to executing the schema creator utility, it is mandatory to update this file.

The following table provides list OFS SANC SCHEMA IN xml parameters.

Table 18-2 OFS_SANC_SCHEMA_IN.xml Parameters

Tag Name/ Attribute Name Description Mandatory (Y/N) Default Value/Permissible Value Comments
<APP_PACK_ID> Seeded unique ID for the OFSAA Application Pack Y Seeded -
IS_TCPS Enables the TCPS Y Default - False IS_TCPS
<APP_PACK_ID> Seeded unique ID for the OFSAA Application Pack Y Seeded -
<JDBC_URL>

Enter the JDBC URL

Note: You can enter RAC/ NON-RAC enabled database connectivity URL.

Y

Example,

jdbc:oracle:thin:@<HOS T/IP>:<PORT>:<SID> or jdbc:oracle:thin:@//

[HOST][:PORT]/SERVICE

or

jdbc:oracle:thin:@(DESC RIPTION=(ADDRESS_LIS T=(ADDRESS=(PROTOC OL=TCP)(HOST=[HOST]) (port=[PORT]))(ADDRES S=(PROTOCOL=TCP)(HO ST=[HOST])(PORT=[POR T]))(LOAD_BALANCE=ye s)(FAILOVER=yes))(CON NECT_DATA=(SERVICE_ NAME=[SERVICE])))

For example, jdbc:oracle:thin:@// dbhost.server.com:1521/ service1

or jdbc:oracle:thin:@//dbshost.server.com:1521/scan-1 or

jdbc:oracle:thin:@(DESC RIPTION=(ADDRESS_LIS T=(ADDRESS=(PROTOC OL=TCP)(HOST=dbhost1.server.com)(port=1521))( ADDRESS=(PROTOCOL=TCP)(HOST=dbhost2.ser ver.com)(PORT=1521))(L OAD_BALANCE=yes)(FAI LOVER=yes))(CONNECT_ DATA=(SERVICE_NAME=service1)))

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

used in the JDBC URL.

<JDBC_DRIVER>

By default this driver name is seeded.

Note: Do not edit this attribute value.

Y

Example,

oracle.jdbc.driver.Oracle Driver

Only JDBC Thin Driver is supported.
<HOST> Enter the Hostname/ IP Address of the system on which you are installing the OFSAA components. Y Host Name/ IP Address -
<SETUPINFO>/ PREFIX_SCHE MA_NAME

Identifies if the value specified in

<SETUPINFO>/ NAME

attribute should be prefixed to the schema name.

N YES or NO Default value is YES.
<SETUPINFO>/ NAME

Enter the acronym for the type of implementation. This information will be displayed in the OFSAA Home Page.

Note: On executing the schema creator utility, this value will be prefixed with each schema name. For example: dev_ofsaaconf, uat_ofsaaatm.

Y

Accepts strings with a minimum length of two and maximum of four.

Example,

DEV, SIT, PROD

This name would appear in the OFSAA Landing Page as "Connected To: xxxx"

The schemas being created would get this prefix. For E.g. dev_ofsaaconf, uat_ofsaaconf etc.

<PASSWORD>/ DEFAULT*

Enter the password if you want to set a default password for all schemas.

Note: You also need to set APPLYSAMEFORALL

attribute as Y to apply the default password for all the schemas.

N The maximum length allowed is 30 characters. Special characters are not allowed. -
<PASSWORD>/ APPLYSAMEFO RALL

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

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

Note: In case 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.

Y Default - N Permissible - Y or N Note: Setting this attribute value is mandatory, If DEFAULT attribute is set.
<TABLESPACE>/NAME Enter the tablespace name for the three tablespace attributes. Y OFS_TFLT_DATA_TBSP/ OFS_TFLT_INDEX_TBSP/ OFS_TFLT_CONF_TBSP Do not change this name.
<TABLESPACE>/ AUTOEXTEND Enter the autoextend value. Y OFF -
<TABLESPACE>/SIZE Enter the tablespace size. Y 512M The DBA can change the size as required.
<TABLESPACE>/DATAFILE Update <CHANGE_ME> place holder with the actual DATAFILE creation path Y Example:/scratch/ oracle/app/oracle/ oradata/ -
<TABLESPACE>/VALUE As per naming conventions, User can modify the default values provided under the VALUE attribute Y

For example, RRS_DATA_TABLE_SPAC

E and RRS_INDEX_TABLE_SPA CE

-
<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.

Note: Do not edit this attribute value.

Y

ATOMIC/CONFIG/ SANDBOX/ADDON

Note:

SANDBOX AND ADDON

schemas are not applicable for OFS Sanctions Pack.

Only One CONFIG schema can exist in the file.

This schema identifies as the CONFIGURATION

schema that holds the OFSAA setup details and other metadata information.

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

ATOMIC schema refers to the Information Domain schema. SANDBOX schema refers to the SANDBOX schema.

ADDON schema refers to other miscellaneous schema (not applicable for this Application Pack).

<SCHEMA>/ NAME

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

You can edit the schema names if required.

Note:

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

attribute.

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

Y The permissible length is 15 characters and only alphanumeric characters allowed. No special characters allowed except underscore '_'.

SETUPINFO/ NAME

attribute value would be prefixed to the schema name being created.

For E.g. if name is set as 'ofsaaatm' and setupinfo as 'uat' then schema being created would be 'uat_ofsaaatm'.

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

<SCHEMA>/ PASSWORD

Enter the password of the schema to be created.

Note:

If this attribute is left blank, then the password specified in the

<PASSWORD>/DEFAULT

attribute is applied as the Schema Password.

N The maximum length allowed is 30 characters. Special characters are not allowed.

Note: You need to mandatorily enter the password if you have set the <PASSWORD>/ APPLYSAMEFORALL attribute as N.

<SCHEMA>/ APP_ID

By default, the Application ID is seeded based on the Application Pack.

Note: Do not edit this attribute value.

Y Unique Seeded Value Identifies the Application/ Product for which the schema is being created.
<SCHEMA>/ DEFAULTTABL ESPACE

Enter the available default tablespace for DB User.

Note:

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

N

Default - USERS

Permissible - Any existing valid tablespace name.

Modify this value to associate any valid tablespace with the schema.
<SCHEMA>/ TEMPTABLESP ACE

Enter the available temporary tablespace for the DB User.

Note:

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

N

Default - TEMP

Permissible - Any existing valid temporary tablespace name.

Modify this value to associate any valid tablespace with the schema.
<SCHEMA>/ QUOTA

Enter the quota to be set on DEFAULTTABLESPACE

attribute for the schema/ user. By default, the quota size is set to 500M.Minimum: 500M or Unlimited on default Tablespace

N

Example, 600M/m

20G/g UNLIMITED/unlimited

Modify this value to grant the specified quota on the mentioned tablespace to the user.
<SCHEMA>/ INFODOM

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.

N Permissible length is 16 characters and only alphanumeric characters allowed. No special characters allowed. -
<ADV_SEC_OP TIONS> Parent tag to hold Advance Security Options. N NA

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

For details, see the example following the table.

<ADV_SEC_OP TIONS>/TDE Tag to enable/disable TDE. N Default is FALSE. To enable TDE, set this to TRUE.

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

/
<ADV_SEC_OP TIONS>/ DATA_REDACT Tag to enable/disable Data Redaction feature. N Default is FALSE. To enable DATA_REDACT, set this to TRUE

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

/
<TABLESPACE S>

Parent tag to hold

<TABLESPACE>

elements

N NA

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.

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

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

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

attribute.

Note the ## syntax.

<TABLESPACE>/ VALUE Physical Name of the tablespace to be created Y NA Value if specified will be the actual name of the TABLESPACE.
<TABLESPACE>/ DATAFILE Specifies the location of the data file on the server Y NA Enter the absolute path of the file to be created.
<TABLESPACE>/ AUTOEXTEND Specifies if the tablespace should be extensible or have a hard limit Y ON or OFF Set to ON to ensure that the tablespace does not run out of space when full.
<TABLESPACE>/ ENCRYPT Specifies if the tablespace(s) should be encrypted using TDE. Y ON or OFF Set to ON to ensure that the tablespaces when created are encrypted using TDE.

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

Example: (The following snippet shows that TDE is enabled and hence the tablespace has been 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/ora12c/app/oracle/oradata/OFSPQA12CDB/ts_users1.dbf"
 SIZE="500M" AUTOEXTEND="ON" ENCRYPT="ON" />
<TABLESPACE NAME="OFS_AAI_TBSP_2" VALUE="TS_USERS2" DATAFILE="/scratch/ora12c/app/oracle/oradata/OFSPQA12CDB/ts_users2.dbf"
 SIZE="500M" AUTOEXTEND="ON" ENCRYPT="ON" />
</TABLESPACES>
<SCHEMAS>
<SCHEMA TYPE="CONFIG" NAME="ofsaaconf" PASSWORD="" APP_ID="OFS_AAI" DEFAULTTABLESPACE=
"##OFS_AAI_TBSP_1##" TEMPTABLESPACE="TEMP" QUOTA="unlimited"/>
<SCHEMA TYPE="ATOMIC" NAME="ofsaaatm" PASSWORD="" APP_ID="OFS_AAAI" DEFAULTTABLESPACE=
"##OFS_AAI_TBSP_2##" TEMPTABLESPACE="TEMP" QUOTA="unlimited" INFODOM="OFSAAAIINFO"/>
</SCHEMAS>