5        Installation

1

Configure the OFS_DI_PACK.xml file.

2

Configure the OFS_DI_SCHEMA_IN.xml and Configure the OFS_DI_SCHEMA_BIGDATA_IN.xml file.

3

Execute the Schema Creator Utility in Offline, Online, or TCPS modes and verify the Schema Creator Log Files.

4

Configure the OFSAAI_InstallConfig.xml file.

5

Configure the Silent.props file.

6

Trigger the OFSDI Application Pack installation.

APP_PACK_ID

Unique Application Pack Identifier

Y

Unique Seeded Value

APP_PACK_NAME

Unique Application Pack Name

Y

Unique Seeded Value

APP_PACK_DESCRIPTION

Unique Application Pack Description

Y

Unique Seeded Value

VERSION

Unique release version

Y

Unique Seeded Value

APP

Unique Application Entries

Y

Unique Seeded Value

APP_ID

Unique Application Identifier

Y

Unique Seeded Value

APP_ID/ PREREQ

Prerequisite Application/ Product

Y

Unique Seeded Value

APP_ID/ DEF_SEL_FLAG

Default Selected Flag

Y

Default value: YES

APP_ID/ ENABLE

Enable Application/ Product

Y

Default value:
YES for Infrastructure
NO for Others

Permissible value:
YES or NO

Note: The Application/ Product cannot be disabled once enabled.

Only Applications/Products which are enabled are installed. In order to install a licensed Applications/Products, you need to restart installation process by specifying the ENABLE flag as Y for the application. The execution of Schema Creation Utility must be skipped.

APP_NAME

Unique Application/ Product Name

Y

Unique Seeded Value

APP_DESCRIPTION

Unique Application/ Product Name

Y

Unique Seeded Value

VERSION

Unique release version

Y

Unique Seeded Value

<APP_PACK_ID>

Unique Application Pack Identifier

Y

Unique Seeded Value

DO NOT modify this value.

<JDBC_URL>

Enter the JDBC URL.

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

Y

Example,

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

oror

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.server.com:1521/service1

or

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

or

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost1.server.com)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost2.server.com)(PORT=1521))(LOAD_BALANCE=yes)(FAILOVER=yes))(CONNECT_DATA=(SERVICE_NAME=service1)))

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

<JDBC_DRIVER>

The name of the driver is seeded.

NOTE: Do not edit this attribute value.

Y

Example,

oracle.jdbc.driver.OracleDriver

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 or IP Address

<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, DEV, SIT, PROD

This message appears 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.

<SETUPINFO>/ PREFIX_SCHEMA_NAME

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

N

YES or NO

Default value is YES.

<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

Default – N
Permissible – Y or 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.

<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, or ADDON

NOTE:

SANDBOX AND ADDON schemas are not applicable for OFS AAAI 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 schema. ADDON schema refers to another miscellaneous schema (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 would 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 must 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 modify 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

Default value: USERS
Permissible value: 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

Default value: TEMP
Permissible value: 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/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.

If DI media pack is first media pack installation in the setup, then INFODOM must be specified mandatorily otherwise it is optional.

<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 or 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_OPTIONS>/ DATA_REDACT

Tag to enable or disable the 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>.

<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, 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 must 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 must 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 (or tablespaces) must be encrypted using TDE.

Y

ON or OFF

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

<APP_PACK_ ID>

Seeded unique ID for the OFSAA Application Pack.

Y

Seeded

DO NOT modify this value.

<JDBC_URL>

Enter the JDBC URL.

NOTE: You can enter the RAC/ 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:1521/service 1

or

jdbc:oracle:thin:@//dbsho st.server.com:1521/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 must be of the RDBMS instance that hosts the Application’s METADOM.

<JDBC_ DRIVER>

By default, this driver name is seeded.

NOTE: Do not modify 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 or IP Address

<SETUPINFO>/ PREFIX_ SCHEMA_ NAME

Identifies if the value specified in<SETUPINFO>/ NAME attribute must 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 a maximum of four.

For example,

DEV, SIT, PROD

This message appears 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 (or schemas).

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

Default - N Permissible - Y or N

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

Applies only to the RDBMS type METADOM schema (or schemas).

<SCHEMAS>/ TYPE=RDBMS

Identifies the RDBMS schema details.

Y

Default names for schemas within the pack would be derived in 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 RDBMS schema and the data model entities of the application are stored in the DATADOM (which would be on Hive).

<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, or ADDON.

NOTE: SANDBOX AND ADDON schemas are not applicable for OFS AAAI Application Pack.

Only One CONFIG schema can exist in the file.

This schema identifies as the CONFIGURATION

a 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 other miscellaneous schemas (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 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 would 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 must 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>/ 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 value: USERS

Permissible value: Any existing valid tablespace name.

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

<SCHEMA>/ TEMPTABLESP ACE

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

N

Default value: TEMP

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

N

For example,

600M/m

20G/g

UNLIMITED/unlimited

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

<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 Error! Reference source not found. and krb5.conf, keytab files. Manually copy the preceding listed files from CDH distribution to this identified folder.

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

Y

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

Schema Name must 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>/ DB TYPE

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 value can be HIVE or IMPALA and so on.

<SCHEMA>/<PROPERTY>/CO MMENT

COMMENTS for HIVE schema.

N

<SCHEMA>/<PROPERTY>/LO CATION

You can optionally specify a location for the table data.

N

<CONNECTION_PROPERTIES>/<PROPERTY>/J DBC_DRIVER

HIVE JDBC driver details.

Y

com.cloudera.hive.j dbc4.HS2Driver

The default cloudera HiveServer 2 driver name.

<CONNECTION_PROPERTIES>/<PROPERTY>/J DBC_URL

Enter the HIVE JDBC URL.

Y

Valid Hive JDBC URL to be specified.

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 must be copied to the location specified in <HIVE_LIB_PATH>.

<CONNECTION_PROPERTIES>/<PROPERTY>/ KRB_REALM_ FILE_NAME

REALM configuration file.

Y

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

<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 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 the Hardware and Software Requirements section 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 Secure File Transfer Protocol (SFTP) 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 or Hostname or web application server IPor  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 or 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 profiledirectory>/installedApps/<NodeCellName>.

·        For example, /data2/test//WebSphere/AppServer/profiles/<Profile_Name>/installedApps/aiximfNode01Cell, where aix-imf is the Hostname.

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

APFTP P_LOG_PATH=

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

# Mandatory if this an App Layer Installation and if you want to create a new infodom.

RDBMS

DBFTP_LOG_PATH

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

# Mandatory if this a DB Layer Installation and if you want to create a new infodom.

RDBMS

HIVE_APPFTP_LOG_PATH

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

# Mandatory if this an App Layer Installation and if you want to create a new infodom.

BIGDATA

HIVE_DBFTP_LOG_PATH

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

# Mandatory if this a DB Layer Installation and if you want to create a new infodom.

BIGDATA