5         Installation

Sl. No.

Activity

1

Extract the installer kit.

2

Configure the OFS_ALM_PACK.xml file.

3

Configure the Schema Creator Utility.

4

Execute the Schema Creator Utility in Offline, Online, or TCPS modes and verify the log file.

5

Configure the OFSAAI_InstallConfig.xml file.

6

Configure the Manifest.xml file.

7

Configure the Silent.props file.

8

Trigger the OFS ALM Application Pack installation.

9

Install ALM Pack on Pack.

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.

Tag Name or Attribute Name

Description

Mandatory (Y or 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 or Product

Y

Unique Seeded Value.

For most applications, the prerequisite that is set is OFS ALM. For all other applications, the default Application ID is set to none. You can set it for the applications you want to install.

Do not modify this value.

APP_ID/ DEF_SEL_FLAG

Default Selected Flag

Y

In all Application Packs, Infrastructure requires this value to be set to "YES".

Do not modify this value.

APP_ID/ ENABLE

Enable Application or Product

Y

·        Default YES for Infrastructure

·        NO for Others

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

NOTE: The Application or Product cannot be disabled once enabled.  Only Applications/Products which are enabled are installed. In order to enable other licensed Applications/Products, you need to reinstall by making the flag as Y for the App_ID. However, in case of reinstallation to enable the other Applications/Products, execution of the schema creation utility must be skipped if it does not include any additional sandboxes to be created.

APP_NAME

Unique Application or Product Name

Y

Unique Seeded Value. Do not modify this value.

APP_DESCRIPTION

Unique Application or Product Name

Y

Unique Seeded Value. Do not modify this value.

VERSION

Unique release version

Y

Unique Seeded Value. Do not modify this value.

Tag Name or Attribute Name

Description

Mandatory (Y or N)

Default Value or Permissible Value

Comments

<APP_PACK_ID>

Seeded unique ID for the OFSSAA Application Pack.

Y

Seeded

Do not modify this value.

<IS_TCPS>

Enter if the TCPS configuration is required.

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 following JDBC URL types:

1.     RAC or NON-RAC enabled database connectivity URL.

2.     TCPS RAC or NON-RAC enabled database connectivity URL provided the <IS_TCPS> tag value is TRUE.

3.     Wallet-enabled JDBC URL.

Y

Example:

jdbc:oracle:thin:@< DBSERVER IP/ 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=dbhost1.server.com) (port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost2.s erver.com)(PORT=1521))( LOAD_BALANCE=yes)(FAILOV ER=yes))(CONNECT_ DATA=(SERVICE_NAME=service1)))

or

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

or

jdbc:oracle:thin:/@

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.

Ensure that you have configured:

4.     The correct Oracle Wallet with the credentials for stored Sys, Config, and Atomic Users.

5.     The JDBC URL as follows:

jdbc:oracle:thin:/@

For more information on how to configure Oracle Wallets for OFSAA Installation and Data Sources, see the Oracle Financial Services Analytical Applications Infrastructure Administration and Configuration Guide.

<JDBC_DRIVER>

The name of the driver is seeded.

Y

Example: oracle.jdbc.driver.OracleDriver

Only JDBC Thin Driver is supported.

Do not modify this value.

<HOST>

Enter the Host Name 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 whether the value specified in <SETUPINFO>/NAME attribute must be prefixed to the Schema name.

N

Y or N

The default value is Y.

<SETUPINFO>/NAME

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

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

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: DEV".

The Schemas that are created 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.

You also must 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.

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

<PASSWORD>/ APPLYSAMEFORALL

If you have entered Y in APPLYSAMEFORALL attribute and also have specified individual passwords for all the Schemas, then the specified individual passwords will take precedence.

Y

Default N Permissible: Y or N

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

If you enter N,  provide individual passwords for all Schemas.

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

<SCHEMA>/TYPE

The types of Schemas supported in this release are: ATOMIC, CONFIG, SANDBOX, and ADDON.

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

Y

ATOMIC, CONFIG, SANDBOX, or ADDON

SANDBOX and ADDON Schemas do not apply to OFSAAI.

Only One CONFIG Schema can exist in the file.

Do not edit this attribute value.

This Schema identifies as the CONFIGURATION Schema that contains the OFSAA setup details and other Metadata information.

Multiple ATOMIC, SANDBOX, or ADDON Schemas can exist in the file.

<SCHEMA>/NAME

The Schemas’ names are seeded based on the Application Pack by default.

You can edit the Schema names if required.

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

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

Y

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

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

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

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.

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

N

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

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

<SCHEMA>/APP_ID

The Application ID is seeded based on the Application Pack.

Y

Unique Seeded Value

Identifies the Application or Product for which the Schema is being created. Do not modify this attribute value.

Do not modify this value.

<SCHEMA>/DEFAULTTABLESPACE

Enter the available default tablespace for DB User.

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

Enter the available temporary tablespace for DB User.

If this attribute is left bank, 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 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

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

<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 in the comments for the <TABLESPACE>/ENCRYPT tag.

<ADV_SEC_OPTIONS>/TDE

Tag to enable or disable TDE.

N

The 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

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

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

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

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

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

<ADV_SEC_OPTIONS>

<OPTION NAME="TDE" VALUE="FALSE"/>

<OPTION NAME="DATA_REDACT" VALUE="FALSE" />

</ADV_SEC_OPTIONS>

<TABLESPACES>

<TABLESPACE NAME="OFS_AAI_TBSP_1" VALUE="TS_USERS1" DATAFILE="/

scratch/ora19c/app/oracle/oradata/OFSPQA19cDB/ts_users1.dbf" SIZE="500M" AUTOEXTEND="ON" ENCRYPT="ON" />

<TABLESPACE NAME="OFS_AAI_TBSP_2" VALUE="TS_USERS2" DATAFILE="/

scratch/ora19c/app/oracle/oradata/OFSPQA19cDB/ts_users2.dbf" SIZE="500M" AUTOEXTEND="ON" ENCRYPT="ON" />

</TABLESPACES>

<SCHEMAS>

<SCHEMA TYPE="CONFIG" NAME="ofsaaconf" PASSWORD="" APP_ID="OFS_AAI" DEFAULTTABLESPACE="##OFS_AAI_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>

NOTE

For Pack on Pack installation, see the Install OFS ALM Application Pack v8.1.0.0.0 on an Existing OFSAA Instance section.

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_ALM_SCHEMA_IN.xml file 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 My Oracle Support. 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 OFS Analytical Applications Infrastructure Administration Guide.

For example, all the database utils 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

1.     See the log file in OFS_ALM_PACK/Schema_Creator/ logs directory for the execution status.

2.     See the log file sysdba_output_scripts.log for execution status if executed in offline mode. This log will be empty if there are no errors in the execution.

3.     If there are any errors, contact My Oracle Support.

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 host name 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 your 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 your 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 as 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 Host name or Web application server IP or Host name, 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/Host name.

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

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

Property Name

Description of Property

Permissible values

Comments

LOG_MODE

Mode for logging

1= General

0 = Debug

Optional;

Default: 0

SEGMENT_1_CODE

Segment Code

Not Applicable

Mandatory

NOTE: The Segment Code should be in upper case.

In case of upgrade, use the existing Segment Code.

OFS_ALM SEGMENT_2_CODE

Segment Code

Not Applicable

Not required. Specify as blank or ignore it.

OFS_ALMBI SEGMENT_2_CODE

Segment Code

Not Applicable

Not required. Specify as blank or ignore it.

APPFTP_LOG_PATH

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

Not Applicable

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

# That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0

DBFTP_LOG_PATH

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

Not Applicable

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

# That is, you have specified INSTALL_APP=1 and INFODOM_TYPE=0

OBI_HOST

The hostname or IP Address of the OBIEE server.

For example: 10.11.12.13 Or myweb.server.com

Mandatory If you are installing ALMBI.

Else, enter some dummy value.

OBI_PORT

The port number of the OBIEE server.

For example: 9500

Mandatory If you are installing ALMBI.

Else, enter some dummy value.

OBI_CONTEXT

Context Name of the OBIEE Server

For example: Analytics

Mandatory If you are installing ALMBI.

Else, enter some dummy value.

OBI_PROTOCOL

HTTP details of the OBIEE Server

http or https

Mandatory If you are installing ALMBI.

Else, enter some dummy value.

UPLOAD_MODEL

If you want to perform Model Upload

0 = No

1 = yes

MODEL_TYPE

Released data model or Customized data model

0 = released

1 = customized

DATAMODEL

Path  for the customized data model

Not Applicable

# Mandatory only if you want to upload the customized data model.

# That is, you have specified MODEL_TYPE=1

DM_DIRECTORY

File name for the customized data model

Not Applicable

# Mandatory only if you want to upload the customized data model.

# That is, you have specified MODEL_TYPE=1

ETL_APPSRC_TYPE

Create new ETL App or Src pair or use an existing one

0 = New

1 = Existing

# Mandatory if this an App Layer installation.

# That is, you have specified INSTALL_APP=1

# 0 = If you want to create a new ETL app or src pair

# 1 = If you want to use an existing pair

ETL_APP_1_DESC

Description for the ETL App

Not Applicable

# Mandatory if you want to create new ETL app or src pair.

#That is, you have specified ETL_APPSRC_TYPE=0

ETL_SRC_1_1_DESC

Description for the ETL Staging source description

Not Applicable

# Mandatory if you want to create new ETL app or src pair.

#That is, you have specified ETL_APPSRC_TYPE=0

ETL_SRC_1_2_DESC

Description for the ETL Processing source description

Not Applicable

# Mandatory if you want to create new ETL app or src pair.

#That is, you have specified ETL_APPSRC_TYPE=0

ETL_APP_1_NAME

ETL application name

Not Applicable

This is for App Layer installation.

ETL_SRC_1_1_NAME

ETL Staging source name

Not Applicable

This Source must be mapped to the above ETL Application.

ETL_SRC_1_2_NAME

ETL Processing source name

Not Applicable

This Source must be mapped to the above ETL Application.

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_ALM_PACK.xml file

3.     Configure the OFS_ALM_SCHEMA_IN.xml file

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

5.     Execute the Schema Creator Utility 

6.     Configure the Manifest.xml file 

7.     Configure the Silent.props file

ATTENTION

Do not install the new applications in the same segment if the preinstalled applications use run management.

NOTE

While defining the Schema details for the applications, provide exactly the same Schema details given in the previous installation. The output file (OFS_ALM_SCHEMA_OUTPUT.xml) is generated as a result of the Schema creation process.