Configure the Schema Creator Utility for HDFS Schema

Configure the <APP Pack>_SCHEMA_BIGDATA_IN.xml file for HDFS installation.

Add the pack specific schema details for the following schema, present in the <APP Pack>_SCHEMA_BIGDATA_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. This schema is created only in RDBMS.
METADOM: This schema holds the data model entities. One METADOM schema is attached to one Information Domain. There can be multiple DATADOM schemas per OFSAA Instance. This schema is created only in RDBMS. It has only platform entities that hold the metadata details. However, it does not hold the data model entities.
DATADOM: This schema holds data model entities. One DATADOM schema is attached to one Information Domain. There can be multiple DATADOM schemas per OFSAA Instance.

Configure the <APP Pack>_SCHEMA_BIGDATA_IN.xml file

The primary steps in OFSAA Applications installation involve creating HIVE schemas and objects within the schemas.

The <APP PACK>_SCHEMA_BIGDATA_IN.xml file contains details of the various application schemas. 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 installation is for HDFS. This file is not required to be configured for an RDBMS ONLY target installation.

Table 7-3 <APP Pack>_SCHEMA_BIGDATA_IN.xml File Parameters

Tag Name/Attribute Name	Details	Default Value/ Permissible Value
`<APP_PACK_ ID>`	Seeded unique ID for the OFSAA 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 RAC/ NON-RAC enabled database connectivity URL.	Example 1: `jdbc:oracle:thin:@<HOST/ IP>:<PORT>:<SID>` Example 2: `jdbc:oracle:thin:@//[HOS T][:PORT]/ SERVICE` For an HDFS ONLY target installation, this URL must be of the RDBMS instance that hosts the Application's METADOM. 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=dbhost 1.server.co m)(port=1521) )(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost2 .s erver.com)(PORT=1521))( LOAD_ BALANCE=yes)(FAILOV ER=yes))(CONNECT_ DATA=(SERVICE_ NAME=service1)))`
`<JDBC_ DRIVER>`	By default, this driver's name is seeded. Only JDBC Thin Driver is supported. DO NOT modify this value.	Example: `oracle.jdbc.driver.OracleDriver`
`<HOST>`	Enter the Hostname/ IP Address of the system on which you are installing the OFSAA components.	Host Name/ IP Address
`<SETUPINFO>/ PREFIX_ SCHEMA_ NAME`	(Optional). Identifies if 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. This name appears in the OFSAA Landing Page as `Connected To: xxxx` On executing the schema creator utility, this value is prefixed with each schema name. For example: `dev_ ofsaaconf`,`uat_ofsaaatm`.	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. Applies only to the RDBMS type METADOM schema(s).	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 the DEFAULT attribute for all the schemas. If you enter as `N`, you must provide individual passwords for all schemas. If you have entered `Y` in the `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. Applies only to the RDBMS type METADOM schema(s).	Default N Permissible `Y` or `N`
`<SCHEMAS>/TYPE=RDBMS`	Identifies the RDBMS schema details. In an HDFS ONLY target installation, the Application's METADOM (that hosts the metadata) for an application is stored in RDBMS schema and the data model entities of the application are stored in the DATADOM (which are on Hive).	Default names for schemas within the pack are derived in absence of any value specified.
`<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. Do not edit this attribute value. 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 METADOM within the Information Domain schema. SANDBOX schema refers to the SANDBOX schema. ADDON schema refers to another miscellaneous schema (not applicable for this Application Pack).	ATOMIC/CONFIG/SANDBOX/ADDON The SANDBOX AND ADDON schemas do not apply to the OFSAAAI Application Pack.
`<SCHEMA>/ NAME`	By default, the schema's names are seeded based on the Application Pack. 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 applications within an Application Pack. For example, if the name is set as `ofsaaatm` and setupinfo as `uat`, then the schema being created would be `uat_ofsaaatm`. `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 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`	By default, the Application ID is seeded based on the Application Pack. 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 the DB User. If this attribute is left blank, then 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`	(Optional). 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. 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 allowed. No special characters allowed.
`<SCHEMAS>/TYPE=HDFS`	Type of schemas being created. Refers to the DATADOM of the Application Pack being installed.
`<HIVE_ SERVER_ HOST>`	IP/HostName of the server where HIVE is installed.
`<HIVE_LIB_ PATH>`	The directory path where the HIVE related drivers/jar files are copied. Manually copy the jars mentioned in the Copy_Jars_to_OFSAA_Installation_Folder and Copy_KEYTAB_and_KRB5_Files_in_OFSAAI sections. Select the appropriate versions of the files.
`<SCHEMA>/NAME`	By default, the schema names are seeded based on the Application Pack. You can edit the schema names if required. The Schema Name will have a prefix of the `SETUPINFO/ NAME` attribute. The Schema Name must not be the same as the Schema Name specified for the ATOMIC Schema Type.	The permissible length is 20 characters and only alphanumeric characters allowed.
`<SCHEMA>/TYPE`	Identifies the type of schema where the data model entities reside. DO NOT modify this value.	By default, the `TYPE` attribute in this tag is set to `DATADOM`.
`<SCHEMA>/DB TYPE`	Identifies the type of driver to be used for the connection. In upcoming releases, the type value can be HIVE/ IMPALA, etc.	By default, the only supported type is HIVE in this release.
`<SCHEMA>/<PROPERTY>/COMMENT`	(Optional). COMMENTS for the HIVE schema.
`<SCHEMA>/<PROPERTY>/LOCATION`	(Optional). You can optionally specify a location for the table data.
`<CONNECTION_PROPERTIES>/<PROPERTY>/ JDBC_DRIVER`	HIVE JDBC driver details. The default HiveServer 2 driver name.	`com.cloudera.hive.j dbc4.HS2Driver`
`<CONNECTION_PROPERTIES>/<PROPERTY>/ JDBC_URL`	Enter the HIVE JDBC URL. Specify the Hive JDBC URL to connect to the Hive Server. For example, `jdbc:hive2://ofss- ****:10000/default;principal=hive/ofssxxx@xxx.COM`	Valid Hive JDBC URL to be specified.
`<CONNECTION_PROPERTIES>/<PROPERTY>/AUTH_TYPE`	Authentication Type. Only "Kerberos with keytab" based authentication supported in this release.	Permissible values: `KERBEROS_WITH_ KEYTAB`
`<CONNECTION_PROPERTIES>/<PROPERTY>/ AUTH_ALIAS`	Alias name for authentication credentials. An Alias name mapping to a principal and password combination specified in the following tags.
`<CONNECTION_PROPERTIES>/<PROPERTY>/PRINCIPAL`	Authentication principal name Principal name used in authentication to connect to the Hive Server. For example: `hive/ofss-xxx@xxx.COM`
`<CONNECTION_PROPERTIES>/<PROPERTY>/PASSWORD`	Authentication password Password used in authentication to connect to the Hive Server.
`<CONNECTION_PROPERTIES>/<PROPERTY>/KRB_GSSJAAS_FILE_NAME`	A keytab file containing pairs of Kerberos principals and an encrypted copy of that principal's key. This file must be copied to the location specified in `<HIVE_LIB_PATH>`.
`<CONNECTION_PROPERTIES>/<PROPERTY>/KRB_REALM_FILE_NAME`	`REALM` configuration file. This file must be copied to the location specified in `<HIVE_LIB_PATH>`.