5        Installation

Sl. No.

Activity

1

Extract the OFSDF Application Pack software.

2

Configure the OFS_BFND_PACK.xml file.

3

Configure the OFS_BFND_SCHEMA_IN.xml file.

4

Configure the OFS_BFND_SCHEMA_BIGDATA_IN.xml file for Stage and Results on Hive (Only for the Big Data installation).

5

Configure the OFSAAI_InstallConfig.xml file.

6

Configure the Silent.props file.

7

Backup the configuration files.

8

Execute the Schema Creator Utility in Offline, Online, or TCPS modes.

9

Verify the Schema Creator log files.

10

Trigger the OFSDF Application Pack installation.

NOTE

If an error message "uncompress: not found [No such file or directory]" is displayed, contact your UNIX administrator.

NOTE

Do not rename the Application Pack installer folder name on extraction from the archive.

NOTE

For the Big Data mode of installation, enable the option as YES for the APP_ID parameter with the value OFS_AAIB as illustrated in the sample.

Tag Name/ Attribute Name

Description

Mandatory (Y/ N)

Comments

APP_PACK_ID

Unique Application Pack Identifier

Y

Unique Seeded Value. DO NOT modify this value.

IS_OPT_INSTALL VALUE=”TRUE”

Unique Application Entry

Y

Unique Seeded Value. DO NOT modify this value.

APP_PACK_NAME

Unique Application Pack Name

Y

Unique Seeded Value. DO NOT modify this value.

APP_PACK_DESCRIPTION

Unique Application Pack Description

Y

Unique Seeded Value. DO NOT modify this value.

VERSION

Unique release version

Y

Unique Seeded Value. DO NOT modify this value.

APP

Unique Application Entries

Y

Unique Seeded Value. DO NOT modify this value.

APP_ID

Unique Application Identifier

Y

Unique Seeded Value. DO NOT modify this value.

APP_ID/PREREQ

Prerequisite Application/ Product

Y

Unique Seeded Value.

For most applications Infrastructure would be the prerequisite set. For certain other applications, an appropriate Application ID would be set.

DO NOT modify this value.

APP_ID/DEF_SEL_FLAG

Default Selected Flag

Y

The default value is YES.

In all Application Packs, Infrastructure would have this value set to “YES”. DO NOT modify this value.

APP_ID/ENABLE

Enable Application/ Product

YES if installing in the SILENT mode.

The default value is YES for Infrastructure. The default value is NO for Others.

Permissible values are YES and NO.

Set this attribute- value to YES against every APP_ID which is licensed and should be enabled for use.

NOTE: The Application or Product cannot be disabled once enabled.

Only those Applications or Products, which are enabled, are installed. To enable the other licensed Applications or Products, you must reinstall by setting the flag to Y for the APP_ID. However, in case of reinstallation, to enable other Applications or Products, skip the execution of the schema creation utility if it does not include the creation of any additional sandbox.

APP_NAME

Unique Application/ Product Name

Y

Unique Seeded Value. DO NOT modify this value.

APP_DESCRIPTION

Unique Application/ Product Name

Y

Unique Seeded Value. DO NOT modify this value.

VERSION

Unique release version

Y

Unique Seeded Value. DO NOT modify this value.

NOTE

This file must be configured only in the case of the OFSDF Application Pack installation for RDBMS ONLY target. This file is not required to be configured for an HDFS ONLY target installation.

Tag Name/ Attribute Name

Description

Mandatory/ Optional

Default Value/ Permissible Value

Comments

<APP_PACK_ID>

Unique Application Pack Identifier

Y

Unique Seeded Value

Example: OFS_BFND_PACK

DO NOT modify this value.

<IS_TCPS>

Enter if the TCPS configuration is required. This is to create a secure line between the client and server when using the OFSDF application.

Y

Seeded, with FALSE as the default value.

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

<JDBC_URL>

Enter the JDBC URL.

NOTE: You can enter RAC and NON-RAC

enabled database connectivity URL.

Y

Example:

jdbc:oracle:thin:@<HOST>:<PORT>:<SID>

or

jdbc:oracle:thin:@//[HOST][: PORT]/SERVICE

or

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=[HOST])(port=[PORT]))(ADDRESS=(PROTOCOL=TCP)(HOST=[HOST])(PORT=[PORT]))(LOAD_BALANCE=yes)(FAILOVER=yes))(CONNECT_DATA=(SERVICE_NAME=[SERVICE])))

For example: jdbc:oracle:thin:@//dbhost.s

erver.com:<port>/service1

or

jdbc:oracle:thin:@//dbshost.

server.com: <port>/scan-1

or

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost1.server.com)(port=<port>))(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost2.server.com)(PORT=<port>))(LOAD_BALANCE=yes)(FAILOVER=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's name is seeded.

NOTE: Do not edit this attribute value.

Y

Example:

oracle.jdbc.driver.OracleDriv er

Only JDBC Thin Driver is supported. DO NOT modify this value.

<HOST>

Enter the Hostname/ IP Address of the system on which you are installing the OFSAA components.

Y

Host Name/ IP Address

<SETUPINFO>/NAME

Enter the acronym for the type of implementation. This information is 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 a maximum of four.

Example:

DEV, SIT, PROD

This name would appear in the OFSAA Landing Page as “Connected To: XXXX”

The schemas being created gets this prefix.

For example: dev_ofsaaconf, uat_ofsaaconf etc.

<SETUPINFO>/

PREFIX_SCHEMA_NAME

Identifies if the value specified in

<SETUPINFO>/

NAME attribute should be prefixed to the schema name.

N

The default value is Y.

Permissible values are Y or N.

The default value is Y.

<PASSWORD>/APPLYSAMEFORALL

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

The default value is N

Permissible values are Y and N.

NOTE: Setting this attribute value is mandatory. If the DEFAULT attribute is set.

<PASSWORD>/DEFAULT*

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

NOTE: You also need to set the 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.

Tag Name/ Attribute Name

Description

Mandatory/ Optional

Default Value/ Permissible Value

Comments

<ADV_SEC_OPTIONS>

Parent tag to hold Advance Security Options.

N

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_OPTIONS>/TDE

Tag to enable/disable TDE.

N

The default value is FALSE.

To enable TDE, set this to TRUE.

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

<ADV_SEC_OPTIONS>/DATA_REDACT

Tag to enable/disable the Data Redaction feature.

N

The default is FALSE.

To enable DATA_REDACT, set this to TRUE

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

Tag Name/ Attribute Name

Description

Mandatory/ Optional

Default Value/ Permissible Value

Comments

<TABLESPACES>

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 the tablespace to be created.

Y

Name if specified should be referred to 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 tablespaces do 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 enabling Transparent Data Encryption (TDE) on the Database Server.

Tag Name/ Attribute Name

Description

Mandatory/ Optional

Default Value/ Permissible Value

Comments

<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 OFSDF Application 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. ADDON schema refers to other miscellaneous schemas (not applicable for this Application Pack).

<SCHEMA>/NAME

By default, the schema 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 the 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 is prefixed to the schema name being created. For Example, If the name is set as ‘ofsaaatm’ and setupinfo as

‘uat’ then schema

being created would be ‘uat_ofsaaatm’.

Example for <SCHEMA>/ NAME:

##CONFIG_USER_NAME## or ##ATOMIC_USER_NAME##

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

Example:

For CONFIG schema, OFS_AAI

For ATOMIC schema, OFS_FSDF

Identifies the Application/ Product for which the schema is being created.

DO NOT modify this value.

<SCHEMA>/DEFAULTTABLESPACE

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.

Example:

##OFS_BFND_DATA_TBSP##

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

<SCHEMA>/TEMPTABLESPA CE

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.

Example:

##OFS_BFND_DATA_TBSP##

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

<SCHEMA>/QUOTA

Enter the quota to be set on the DEFAULTTABLESPACE attribute for the schema or 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

(Optional for Atomic and mandatory for sandbox)

Permissible length is 16 characters and only alphanumeric characters allowed. No special characters allowed.

Enter this field in UPPERCASE.

NOTE

This file must be configured only for the OFSDF Application Pack installation for the HDFS ONLY target. Do not configure this file for an RDBMS ONLY target installation.

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

DO NOT modify this value.

<IS_TCPS>

Enter if the TCPS configuration is required. This is to create a secure line between the client and server when using the OFSDF application.

Y

Seeded, with FALSE as the default value.

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

<JDBC_URL>

Enter the JDBC URL

NOTE: You can enter the RAC or NON-RAC enabled database connectivity URL.

Y

Example:

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

or

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

or

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])))

For example, jdbc:oracle:thin:@//dbhos t.server.com:<port>/service 1

or

jdbc:oracle:thin:@//dbsho st.server.com:<port>/scan-1

or

jdbc:oracle:thin:@(DESCRI PTION=(ADDRESS_ LIST=(ADDRESS=(PROT OCOL=TCP)(HOST=dbho

st1.server.com)(port=1521)

)(ADDRESS=(PROTOCO

L=TCP)(HOST=dbhost2.s erver.com)(PORT=1521))( LOAD_ BALANCE=yes)(FAILOV ER=yes))(CONNECT_ DATA=(SERVICE_

NAME=service1)))

For an HDFS ONLY target installation, this URL should be of the RDBMS instance that hosts the Application’s METADOM.

<JDBC_DRIVER>

By default, this driver's name is seeded.

NOTE: Do not edit this attribute value.

Y

Example:

oracle.jdbc.driver.OracleD river

Only JDBC Thin Driver is supported.

DO NOT modify this value.

<HOST>

Enter the Hostname or IP Address of the system on which you are installing the OFSAA components.

Y

Host Name/ IP Address

<IS_HYBRID>/VALUE

Tag to enable/disable HYBRID installation (Stage on Hive and Results on RDBMS).

N

The default value is FALSE

The default value is FALSE for Hive.

<SETUPINFO>/ PREFIX_SCHEMA_NAME

Identifies if the value specified in the <SETUPINFO>/NAME attribute should be prefixed to the schema name.

N

YES or NO.

The 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 a maximum of four.

Example: BFND

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

The schemas being created would get this prefix. For example, dev_ ofsaaconf, uat_ofsaaconf, and so on.

<PASSWORD>/DEFAULT*

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

NOTE: You also need to set the 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.

Applies only to the RDBMS type METADOM schema(s).

<PASSWORD>/APPLYSAMEFORALL

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 need to provide individual passwords for all schemas.

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

Y

The default value is N.

Permissible values are Y and N.

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

Applies only to the RDBMS type METADOM schema(s).

Tag Name/ Attribute Name

Description

Mandatory (Y/N)

Default Value/ Permissible Value

Comments

<SCHEMAS>/TYPE=RDBMS

Identifies the RDBMS schema details.

Y

Default names for schemas within the pack are derived in the absence of any value specified.

In an HDFS ONLY target installation, the Application’s METADOM (that hosts the metadata) for an application is stored in the RDBMS schema and the data model entities of the application are stored in the DATADOM (which is on Hive).

<SCHEMA>/TYPE

The different types of schemas that are supported in this release are ATOMIC, CONFIG.

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

NOTE: Do not edit this attribute value.

Y

ATOMIC/CONFIG.

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 or SANDBOX or 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 other miscellaneous schemas (not applicable for this Application Pack).

<SCHEMA>/NAME

By default, the schema 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 the same for all the ATOMIC Schemas of applications within an Application Pack.

Y

The permissible length is 15 characters and only alphanumeric characters are allowed. No special characters are allowed except the Underscore '_'.

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

For example, if the name is set as 'ofsaaatm' and setupinfo as 'uat' then schema being created would be 'uat_ofsaaatm'.

NAME should be the 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 or Product for which the schema is being created.

DO NOT modify this value.

<SCHEMA>/DEFAULTTABLESPACE

Enter the available default tablespace for DB User.

NOTE:

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

N

The default value is USERS.

Permissible value is any existing valid tablespace name.

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

<SCHEMA>/TEMPTABLESPACE

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

The default value is TEMP.

Permissible value is 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 the DEFAULTTABLESPACE attribute for the schema or user. By default, the quota size is set to 500M. Minimum: 500M or Unlimited on default Tablespace.

N

Example:

600M or 600m

20G or 20g

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

##INFODOM_NAME##

Example:

FSDFINFO

Tag Name/ Attribute Name

Description

Mandatory (Y/N)

Default Value/ Permissible Value

Comments

<SCHEMAS>/TYPE=HDFS

Type of schemas being created.

Y

Refers to the DATADOM of the Application Pack being installed.

<HIVE_SERVER_HOST>

IP or HostName of the server where HIVE is installed.

Y

<HIVE_LIB_PATH>

Folder path where HIVE related drivers or jar files are copied.

Y

Should contain the list of jars mentioned in the section Copying Jars to  OFSAA Installation  Folder and krb5.conf, keytab files. Manually copy the preceding listed files from CDH distribution to this identified folder.

NOTE: The Cloudera administrator will provide these two files krb5.conf and keytab.

<SCHEMA>/NAME

By default, the schema 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.

Y

The permissible length is 20 characters and only alphanumeric characters allowed.

Example:

HIVEHYBDATADOM

Schema Name should not be the same as Schema Name specified for Schema Type ATOMIC.

<SCHEMA>/TYPE

Identifies the type of schema where the data model entities would reside.

Y

By default, the TYPE attribute in this tag is set to DATADOM.

DO NOT modify this value.

<SCHEMA>/APP_ID

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

Y

The supported value is OFS_FSDF.

<SCHEMA>/DBTYPE

Identifies the type of driver to be used for the connection.

Y

By default, the only supported type is HIVE in this release.

In the upcoming releases, the type of value can be HIVE, IMPALA, and so on.

<SCHEMA_PROPERTIES>/<PROPERTY>/COMMENT

COMMENTS for HIVE schema.

N

<SCHEMA_PROPERTIES>/<PROPERTY>/LOCATION

You can optionally specify a location for the table data.

N

hdfs:// ##HIVE_SERVER_HOST_NAME_OR_IP##:NamenodePort/user/hive/warehouse/<<PREFIX>>__<<SCHEMA_NAME>>/

NOTE: The <<PREFIX>> prefix is applicable only if the  <PREFIX_SCHEMA_NAME> tag is "Y" in the <SETUPINFO> tag.

For example: When <SETUPINFO NAME="BFND" PREFIX_SCHEMA_NAME="Y"/>. <<SCHEMA_NAME>> is the DATADOM schema name.

Example:

hdfs:// whf00bsy.in.oracle.com:8020/user/hive/warehouse/BFND_BSYDATADOM/

<CONNECTION_PROPERTIES>/

<PROPERTY>/JDBC_DRIVER

HIVE JDBC driver details.

Y

com.cloudera.hive.j dbc4.HS2Driver

The default cloudera HiveServer 2 driver name.

<CONNECTION_PROPERTIES>/

<PROPERTY>/JDBC_URL

Enter the HIVE JDBC URL.

Y

A valid Hive JDBC URL to be specified.

jdbc:hive2://##HIVE_SERVER_HOST_NAME_OR_IP##:10000/<<PREFIX>>__<<SCHEMA_NAME>>;AuthMech=1;KrbServiceName=hive;KrbHostFQDN=##HIVE_SERVER_HOST_NAME_OR_IP##;KrbRealm=##REALM##

NOTE: <<PREFIX>> Prefix is applicable only if the <PREFIX_SCHEMA_NAME> tag is Y in <SETUPINFO> tag. For example, when <SETUPINFO NAME="BFND" PREFIX_SCHEMA_NAME="Y"/>. <<SCHEMA_NAME>> is the DATADOM schema name.

For example:

jdbc:hive2://whf00bsy.in.oracle.com:10000/BFND_ BSYDATADOM;AuthMech=1;KrbServiceName=hive;KrbHostFQDN=whf00bsy.in.oracle.com;KrbRealm=WHFBSY.ORACLE.COM

Specify the Hive JDBC URL to connect to the Hive Server.

<CONNECTION_PROPERTIES>/

<PROPERTY>/AUTH_TYPE

Authentication Type.

Y

Permissible values: KERBEROS_WITH_ KEYTAB.

Only “Kerberos with keytab” based authentication supported in this release.

<CONNECTION_PROPERTIES>/

<PROPERTY>/AUTH_ALIAS

Alias name for authentication credentials.

Y

An Alias name mapping to a principal and password combination specified in the following tags.

<CONNECTION_PROPERTIES>/

<PROPERTY>/PRINCIPAL

Authentication principal name.

Y

Principal name used in authentication to connect to the Hive Server.

<CONNECTION_PROPERTIES>/

<PROPERTY>/PASSWORD

Authentication password.

Y

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.

Y

This file should be copied to the location specified in <HIVE_LIB_PATH>.

<CONNECTION_PROPERTIES>/

<PROPERTY>/KRB_REALM_FILE_NAME

REALM configuration file.

Y

This file should be copied to the location specified in <HIVE_LIB_PATH>.

InteractionVariable Name

Significance and Expected Value

Mandatory

<Layer name="GENERAL">

InteractionGroup name=”WebServerType”

WEBAPPSERVERTYPE

Identifies the web application server on which the OFSAA Infrastructure web components are deployed.

Set the following numeric value depending on the type of web application server:

·        Apache Tomcat = 1

·        IBM WebSphere Application Server = 2

·        Oracle WebLogic Server = 3

For example, <InteractionVariable

name="WEBAPPSERVERTYPE">3</InteractionVari able>

Yes

InteractionGroup name=”OFSAA Infrastructure Server Details”

DBSERVER_IP 

Identifies the hostname or IP address of the system on which the Database Engine is hosted.

NOTE: For RAC Database, the value must be NA. For example, <InteractionVariable name="DBSERVER_ IP">14.15.16.17</InteractionVariable> or

<InteractionVariable name="DBSERVER_ IP">dbhost.server.com</InteractionVariable>

Yes 

InteractionGroup name=”Database Details”

ORACLE_SID/SERVICE_NAME 

Identifies the Oracle DB Instance SID or SERVICE_NAME

NOTE: The Oracle_SID value must be exactly the same as it is mentioned in JDBC_URL.

For example, <InteractionVariable name="ORACLE_SID/SERVICE_

NAME">ofsaser</InteractionVariable>

Yes

ABS_DRIVER_PATH

Identifies the directory where the JDBC driver (ojdbc<version>.jar) exists. This is typically the $ORACLE_HOME/jdbc/lib directory.

For example, <InteractionVariable name="ABS_DRIVER_ PATH">">/oradata6/revwb7/ oracle </InteractionVariable>

NOTE: See Hardware and Software Requirements to identify the correct ojdbc<version>.jar file version to be copied.

Yes

InteractionGroup name=”OLAP Detail

OLAP_SERVER_ IMPLEMENTATION 

Identifies whether the OFSAA Infrastructure OLAP component must be configured. It depends on whether you intend to use the OLAP feature. The following numeric value must be set depending on the choice:

·        YES: 1

·        NO: 0

NOTE: If the value for OLAP_SERVER_IMPLEMENTATION is set to 1, the installer checks if the following environment variables are set in the .profile file:

·        ARBORPATH

·        HYPERION_HOME

·        ESSBASEPATH

No

InteractionGroup name=”SFTP Details”

SFTP_ENABLE 

Identifies if the SFTP (Secure File Transfer Protocol) feature is to be enabled. The following numeric value must be set depending on the choice:

·        SFTP: 1

·        FTP: 0

Yes

NOTE: The default value for SFTP_ENABLE is 1, which signifies that SFTP is used. Oracle recommends using SFTP instead of FTP because SFTP is more secure. However, you can ignore this recommendation and use FTP by setting SFTP_ENABLE to 0. You can change this selection later from the OFSAAI administration interface.

Set SFTP_ENABLE to -1 to configure ftpshare and weblocal path as a local path mounted for the OFSAAI server.

FILE_TRANSFER_PORT

Identifies the port used for the file transfer service. The default value specified is 22 (SFTP). Specify the value like 21 or any other PORT value if the value for SFTP_ENABLE is 0.

For example, <InteractionVariable name="FILE_TRANSFER_ PORT">21</InteractionVariable>

Yes

InteractionGroup name=”Locale Detail”

LOCALE 

Identifies the locale information to be used during the installation. This release of the OFSAA Infrastructure supports only US English.

For example, <InteractionVariable name="LOCALE">en_US</InteractionVariable>

Yes

InteractionGroup name=”OFSAA Infrastructure Communicating ports"

NOTE: The following ports are used internally by the various OFSAA Infrastructure services. The default values mentioned are set in the installation. If you intend to specify a different value, update the parameter value accordingly, ensure that the port value is in the range 1025 to 65535, and the respective port is enabled.

JAVAPORT 

9999

Yes

NATIVEPORT

6666

Yes

AGENTPORT

6510

Yes

ICCPORT

6507

Yes

ICCNATIVEPORT

6509

Yes

OLAPPORT

10101

Yes

MSGPORT

6501

Yes

ROUTERPORT

6500

Yes

AMPORT

6505

Yes

InteractionGroup name="Web Details"

NOTE: If the value for HTTPS_ENABLE is set to 1, ensure that you have a valid certificate available from a trusted CA and it is configured on your web application server.

HTTPS_ENABLE 

Identifies whether the UI must be accessed using HTTP or HTTPS scheme. The default value is set to 0. The numeric value must be set depending on the following options:

·        YES: 1

·        NO: 0

For example, <InteractionVariable name="HTTPS_ENABLE">0</InteractionVariable>

Yes

WEB_SERVER_IP

Identifies the HTTP Server IP/Hostname or Web application server IP/ Hostname, to be used to access the UI. This IP is typically the HTTP Server IP.

If a separate HTTP Server is not available, then the value must be Web application server IP/Hostname.

For example, <InteractionVariable name="WEB_SERVER_ IP">10.11.12.13</InteractionVariable>

or

<InteractionVariable name="WEB_SERVER_ IP">myweb.server.com</InteractionVariable>

No

WEB_SERVER_PORT

Identifies the Web Server Port, which is typically 80 for non SSL and 443 for SSL. If a separate HTTP Server exists, the port value must be the value configured for the Web Server.

Warning: The installer will not accept the port value as:

·        80, if the HTTPS_ENABLE variable is 1

·        443, if the HTTPS_ENABLE variable is 0

For example, <InteractionVariable name="WEB_ SERVER_PORT">80</InteractionVariable>

No

CONTEXT_NAME

Identifies the web application context name which is used to build the URL to access the OFSAA application. You can identify the context name from the following URL format:

<scheme>://<host>:<port>/<context-name>/login.jsp

The following is an example:

https://myweb:443/ofsaadev/login.jsp

For example, <InteractionVariable name="CONTEXT_NAME">ofsaadev</InteractionVariable>

Yes

WEBAPP_CONTEXT_PATH

Identifies the absolute path of the exploded EAR file on the web application server.

·        For Tomcat, specify the Tomcat directory path till /webapps. For example, /oradata6/revwb7/tomcat/webapps/.

·        For WebSphere, specify the WebSphere path as <WebSphere profile directory>/installedApps/<NodeCellName>. For example, / data2/test//WebSphere/AppServer/profiles/<Profile_Name>/installedApps/aiximfNode01Cell, where aix-imf is the Host name.

·        For WebLogic, specify the WebLogic home directory path. For example, /<WebLogic home directory path>/bea/wlserver_10.3

NOTE: For WebLogic, the value specified for this attribute is ignored and the value provided against the attribute WEBLOGIC_DOMAIN_HOME is considered.

Yes

WEB_LOCAL_PATH

Identifies the absolute path to any directory on the web application server that can hold temporary files, which are uploaded as part of the usage of the application.

Set this in the FTPSHARE location.

NOTE: During a clustered deployment, ensure that this path and the directory are the same on all the nodes.

Yes

InteractionGroup name="Weblogic Setup Details”

WEBLOGIC_DOMAIN_HOME 

Identifies the WebLogic Domain Home.

For example, <InteractionVariable name="WEBLOGIC_DOMAIN_HOME">/home/weblogic/bea/user_projects/domains/mydomain</InteractionVariable>

Yes.

Specify the value only if WEBAPPSERVERTYPE is set as 3 (WebLogic)

InteractionGroup name="OFSAAI FTP Details”

OFSAAI_FTPSHARE_PATH 

Identifies the absolute path of the directory that is identified as the file system stage area.

NOTE: The directory must exist on the same system on which the OFSAA Infrastructure is being installed (can be on a separate mount).

The user mentioned in the APP_SFTP_USER_ID parameter in the following example must have RWX permission on the directory.

For example, <InteractionVariable name="APP_FTPSHARE_PATH">">/oradata6/revwb7/ftpshare</InteractionVariable>

Yes

OFSAAI_SFTP_USER_ID

Identifies the user who has RWX permissions on the directory identified for the parameter APP_FTPSHARE_PATH.

Yes

OFSAAI_SFTP_PRIVATE_KEY

Identifies the SFTP private key for OFSAAI.

For example,

<InteractionVariable name="OFSAAI_SFTP_PRIVATE_KEY">/home/ofsaapp/.ssh/id_rsa</InteractionVariable>

By default, the value is NA, which indicates that, for authentication, you are prompted to enter the password for the user <OFSAAI_SFTP_USER_ ID>.

For more information on how to generate an SFTP Private key, see the Set Up SFTP Private Key section.

No

OFSAAI_SFTP_PASSPHRASE

Identifies the passphrase for the SFTP private key for OFSAAI.

For example,

InteractionVariable name="OFSAAI_SFTP_PASSPHRASE">enter a pass phrase here</InteractionVariable>

By default, the value is NA.

If the OFSAAI_SFTP_PRIVATE_KEY value is given and the OFSAAI_SFTP_PASSPHRASE value is NA, then the passphrase is identified as empty.

No

InteractionGroup name="Hive Details"

The default value set for the interaction variables under this group is NA.

NOTE: The following values are required only for Hive Configuration.

HIVE_SERVER_PORT 

Identifies the port used for the file transfer service. The default value is 22 (SFTP). To use this port for FTP, set this value to 21.

For example,

<InteractionVariable name="HIVE_SERVER_PORT">22</InteractionVariable>

Yes

HIVE_SERVER_FTPDRIVE

Identifies the absolute path to the directory identified as the file system stage area of the HIVE server.

For example,

<InteractionVariable name="HIVE_SERVER_FTPDRIVE">/scratch/ofsaa/ftpshare</InteractionVariable>

Yes

HIVE_SERVER_FTP_USERID

Identifies the user who has RWX permissions on the directory identified under the parameter HIVE_SERVER_FTPDRIVE.

For example,

<InteractionVariable name="HIVE_SERVER_FTP_USERID">ofsaa</InteractionVariable>

Yes

HIVE_SERVER_FTP_PROTOCOL

If the HIVE_SERVER_PORT is 21, then set the value to FTP. If not, set it to SFTP.

For example,

<InteractionVariable name="HIVE_SERVER_FTP_PROTOCOL">SFTP</InteractionVariable>

Yes

HIVE_SFTP_PRIVATE_KEY

Identifies the SFTP private key for the HIVE server.

For example,

<InteractionVariable name="HIVE_SFTP_PRIVATE_ KEY">/scratch/testuser/.ssh/id_rsa</InteractionVariable>

By default, the value is NA, which indicates that, for authentication, you are prompted to enter the password for the user <HIVE_SERVER_FTP_USERID>.

For more information on generating SFTP Private key, see the Set Up SFTP Private Key section.

HIVE_SFTP_PASSPHRASE

Identifies the passphrase for the SFTP private key for HIVE.

For example,

<InteractionVariable name="HIVE_SFTP_ PASSPHRASE">NA</InteractionVariable>

By default, the value is NA.

If the HIVE_SFTP_PRIVATE_KEY value is NA, then the passphrase is identified as empty.

ATTENTION

Do not install the new applications in the same segment if the preinstalled applications use Run Management.

NOTE

In an integrated environment, Oracle recommends the customers to use the same Staging source in the Silent.props file for the T2Ts that load data from the Stage tables into the Result tables.

Property Name

Description of Property

Permissible values

Comments

LOG_MODE

Mode for logging

0 = Debug

1= General

# Optional; Default: 0

SEGMENT_1_CODE

Segment Code

Example: BFNDSEG

# Mandatory

Segment Code should not exceed 10 characters and there should not be special characters or extra spaces

APPFTP_LOG_PATH

Information Domain Maintenance log path(to be created) for the new Information Domain for App Layer

Example: /ftpshare/<INFODOM_NAME>/logs

# Mandatory if this an App Layer Installation and want to create a new Information Domain

DBFTP_LOG_PATH

Information Domain Maintenance log path(to be created) for the new Information Domain for DB Layer

Example: /ftpshare/<INFODOM_NAME>/logs

# Mandatory if this an App Layer Installation and want to create a new Information Domain

UPLOAD_MODEL

Whether you want to perform Model Upload

0 = No

1 = Yes

# Mandatory

MODEL_TYPE

Released data model or Customized data model

0 = released

1 = customized

# Mandatory only in the case of UPLOAD_MODEL=1

DATAMODEL

The file name for the customized data model

Not Applicable

# Mandatory only in the case of uploading the customized data model

# Option selected for MODEL_TYPE=1

DM_DIRECTORY

The path for the customized data model

Not Applicable

# Mandatory only in the case of uploading the customized data model

# Option selected for

MODEL_TYPE=1

ETL_APPSRC_TYPE

The ETL application name

0 = New Pair

1 = Existing

# Mandatory

ETL_SRC_1_NAME

ETL FSDF Staging Source Name

Example: STAGING

# Mandatory

ETL_SRC_2_NAME

ETL FSDF CAP ADQ Pack Integration Source Name

Example: FSDF_CAP_SRC

# Mandatory

ETL_SRC_3_NAME

ETL FSDF TR Pack Integration Source Name

Example: FSDF_TR_SRC

# Mandatory

ETL_SRC_4_NAME

ETL FSDF IFRS Pack Integration Source Name

Example: FSDF_IFRS_SRC

# Mandatory

ETL_SRC_1_DESC

ETL FSDF Staging Source Description

Example: STAGING

# Mandatory

ETL_SRC_2_DESC

ETL FSDF CAP ADQ Pack Integration Source Description

Example: FSDF_CAP_SRC

# Mandatory

ETL_SRC_3_DESC

ETL FSDF TR Pack Integration Source Description

Example: FSDF_TR_SRC

# Mandatory

ETL_SRC_4_DESC

ETL FSDF IFRS Pack Integration Source Description

Example: FSDF_IFRS_SRC

# Mandatory

ENABLE_CONCURRENCY

#Support for Parallelism

0 = No

1 = Yes

#Optional

CONCURRENCY_LEVEL

#Support for Parallelism

Example:

CONCURRENCY_LEVEL=10, which means 10 threads are triggered to handle the processing of fsapps.

#Optional

Property Name

Description of Property

Permissible values

Comments

LOG_MODE

Mode for logging

0 = Debug

1= General

# Optional; Default: 0

SEGMENT_1_CODE

Segment Code

Example: FSDFSEG

# Mandatory

Segment Code should not exceed 10 characters and there should not be special characters or extra spaces

HIVE_APPFTP_LOG_PATH

Infodom Maintenance log path(to be created) for the new Infodom

Example:

/scratch/ofsaa/ftpshare/FSDFINFO/logs

# Mandatory to create a new Information Domain

HIVE_DBFTP_LOG_PATH

Information Domain Maintenance log path(to be created) for the new Information Domain for DB Layer

Example:

/scratch/ofsaa/ftpshare/FSDFINFO/logs

# Mandatory to create a new Information Domain

HIVE_UPLOAD_MODEL

Whether you want to perform Model Upload on hive infodom

0 = No

1 = yes

# Mandatory

HIVE_MODEL_TYPE

Released data model or Customized data model for model upload process

0 = released

1 = customized

# Option selected for HIVE_MODEL_TYPE=0

DATAMODEL_HIVE

The file name for the customized data model in Hive

Not Applicable

# Mandatory only in the case of uploading the customized data model

# Option selected for HIVE_MODEL_TYPE=1

DM_DIRECTORY

The path for the customized data model

Not Applicable

# Mandatory only in the case of uploading the customized data model

# Option selected for

HIVE_MODEL_TYPE=1

ETL_APPSRC_TYPE

The ETL application name

0=New Pair 1=Existing

# Mandatory

ETL_SRC_5_NAME

ETL FSDF HIVE Staging Source Name

Example: STAGING

# Mandatory

ETL_SRC_5_DESC

ETL FSDF HIVE Staging Source description

Example: STAGING

# Mandatory

ENABLE_CONCURRENCY

#Support for Parallelism

0 = No

1 = Yes

#Optional

CONCURRENCY_LEVEL

#Support for Parallelism

Example:

CONCURRENCY_LEVEL=10, which means 10 threads are triggered to handle the processing of fsapps.

#Optional

File Name

Directory

OFS_BFND_SCHEMA_IN.xml and OFS_BFND_SCHEMA_BIGDATA_IN.xml

OFS_BFND_PACK/schema_creator/conf

OFS_BFND_SCHEMA_OUTPUT.xml

OFS_BFND_PACK/schema_creator/

Silent.props

OFS_BFND_PACK/appsLibConfig/conf

OFSAAI_InstallConfig.xml

OFS_BFND_PACK/OFS_AAI/conf/

NOTE

Explicit Grants to the user are required. Grants assigned through Roles are not supported.

NOTE

If there are any errors during the SQL script execution, reconfigure the OFS_BFND_SCHEMA_IN.xml and/or OFS_BFND_SCHEMA_ BIGDATA_IN.xml files and repeat steps in this procedure to execute the utility. This regenerates the scripts with the correct information.

NOTE

See the sysdba_output_scripts.log file for execution status. If there are any errors, contact Oracle Support Services. If there are no errors in the execution, the log file is empty.

NOTE

You can also use Oracle Wallet to support OFSAA for storing Config and Atomic Schema credentials. To add OFSAA Config and Atomic Schema credentials to Oracle Wallet, see the Oracle Financial Services Advanced Analytical Applications Infrastructure Administration and Configuration Guide Release 8.1.x.

For example, all the database utilities such as sqlplus, tnsping, and sqlldr must work between the Client and the Server.

NOTE

You must use the same config schema user name as the previous Application Pack.

NOTE

See If there are any errors, contact Oracle Support Services.

ATTENTION

Before you begin the installation, configure and execute the following files:

1.     Configure the OS File System Settings and Environment Settings in the .profile File

2.     Configure the OFS_BFND_PACK.xml File

3.     Configure the OFS_BFND_SCHEMA_IN.xml File (for RDBMS installation)

4.     Configure the OFS_BFND_SCHEMA_BIGDATA_IN.xml File (for Big Data installation)

5.     Configure the OFSAAI_InstallConfig.xml File (do not configure this file if an installation of OFSAAI 8.1 already exists.)

6.     Configure the Silent.props File (Silent.template file for RDBMS installation and Silent.BIGDATA.template file for Stage and Results on Hive)

7.     Execute the Schema Creator Utility

NOTE

After the extraction, if you have space issue, delete the .zip file.

NOTE

Enter the password to access the Product Staging/Metadata repository directory FTPSHARE in the application server.

NOTE

Enter the password to access the OFSDF Hive directory FTPSHAREH in the application server.

NOTE

·        The data model upload may take several hours to complete. You can check the installation logs in the /OFS_BFND_PACK/OFS_FSDF/logs/ directory.

·        For the existing customers, with the DB XML, the time taken for the data model upload will be significantly reduced. You can upload the warehouse data from the operational systems to the database schema using the erwin XML or Database XML file. Using the stand-alone command-line utility for the TransformErwin.sh file, you can transform erwin XML into Database XML, and use the DB XML instead of erwin XML to speed up the model upload process. For more information, see the Command Line Utility for Transforming erwin XML to Database XML section in the OFS AAAI User Guide Release 8.1.0.0.0.

NOTE

During both of the Big Data installation processes, for the Big Data SQL to refresh the data, ensure to truncate the Stage tables during the second time and onwards, and then load the data. Truncation is not required during the first time.

NOTE

For the list of CSV files, see the complete-csvs.txt file.

NOTE

For the list of CSV files, see the complete-csvs.txt file.

NOTE

HDFS_TEMP_DIR is not the Hive warehouse directory. Also, ensure that the path is not the Hive Metastore directory.

NOTE

Configuring the OFSAAI_InstallConfig.xml file is not required in this scenario.

NOTE

While defining the schema details for the application packs, provide the same schema details given in the previous v8.1.0.0.0 installation of the other application pack. The output file OFS_BFND_SCHEMA_OUTPUT.xml is generated as a result of the schema creation process.