1. Installation and Configuration Guide
  2. Installation
  3. Configure the OFSAAI_InstallConfig.xml File

6.5 Configure the OFSAAI_InstallConfig.xml File

To configure the OFS_InstallConfig.xml file, follow these steps:

  • Navigate to the OFS_AAAI_PACK/OFS_AAI/conf/ directory.
  • Open the OFSAAI_InstallConfig.xml file in a text editor.
  • Configure the OFSAAI_InstallConfig.xml file as mentioned in the following table.

You must manually set the InteractionVariable parameter values as mentioned in the table. If a value is not applicable, enter NA. Ensure that the value is not entered as NULL.

Table 6-4 Table 19: OFSAA Infrastructure Installation Tasks and Descriptions

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, <InteractionVariablename="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 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 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/ Host name or Web application server IP/ 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

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