5        Installation

1

Extract the OFS BCE application software.

2

Configure the OFS_IBCE_PACK.xml file.

3

Configure the OFS_IBCE_SCHEMA_IN.xml file.

4

Configure the OFSAAI_InstallConfig.xml file.

5

Configure the Silent.props file.

6

Backup the configuration files.

7

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

8

Verify the Schema Creator Log Files.

9

Trigger the application installation.

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, OFS AAAI is the prerequisite set. For all other applications, the default Application ID is set to none. You can set it for the applications you would like to install.

Do not modify this value.

APP_ID/ DEF_SEL_FLAG

Default Selected Flag

Y

In all Application Packs, Infrastructure would have this value set to "YES".

Do not modify this value.

APP_ID/ ENABLE

Enable Application/ Product

Y

YES for OFS_AAI and OFS_IBCE. Do not modify this value.

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

<APP_PACK_ID>

Seeded unique ID for the OFS 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.

You can enter RAC/ NON-RAC enabled database connectivity 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:1111/service 1

or

jdbc:oracle:thin:@//dbsho st.server.com:1111/scan-1

or

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

st1.server.com)(port=1111)

)(ADDRESS=(PROTOCO

L=TCP)(HOST=dbhost2.s erver.com)(PORT=1521))( LOAD_ BALANCE=yes)(FAILOV ER=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 must match with the SID/ SERVICE NAME used in the JDBC URL.

<JDBC_DRIVER>

This driver name is seeded by default.

Y

Example: oracle.jdbc.driver.OracleDriver

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

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

Example: DEV, SIT, PROD

This name appears in the OFSAA Landing Page as "Connected To: DEV".

The schemas being created get this prefix. For example, dev_nameconf, uat_nameconf, 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_IBCE_SCHEMA_IN.xml file is nullified.

<PASSWORD>/ APPLYSAMEFORALL

If you have entered Y in APPLYSAME-

FORALL attribute and also have specified individual passwords for all the schemas, then the specified individual passwords will take precedence.

Y

Default value: N

Permissible value: Y or N

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

If you enter as N, you must provide individual passwords for all schemas.

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

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

Y

ATOMIC/CONFIG/SANDBOX/ADDON

SANDBOX and ADDON schemas are not applicable for OFS_IBCE_PACK.

Only One CONFIG schema can exist in the file.

Do not edit this attribute value.

This schema identifies as the CONFIGURATION schema that holds the OFSAA setup detains and other Metadata information.

Multiple ATOMIC/ SANDBOX/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 are allowed except underscore _.

The 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 being created is 'uat_ofsaatm'.

NAME must be the same where APP_GRP=1 for all SCHEMA tags (not applicable for this Application).

<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 applied 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 by default.

Y

Unique Seeded Value

Identifies the Application/ Product for which the schema is being created. Do not edit 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 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 DB User.

If this attribute is left bank, 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/ 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 are allowed. No special characters are allowed.

<ADV_SEC_OPTIONS>/

Parent tag to hold Advance Security Options.

N

NA

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

<ADV_SEC_OPTIONS>/TDE

Tag to enable/disable TDE feature.

N

Default value is FALSE.

To enable TDE, set this value to TRUE.

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

<ADV_SEC_OPTIONS>/DATA_REDACT

Tag to enable/disable Data Redaction feature.

N

Default value is FALSE.

To enable DATA_REDACT, set this value 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 that follows the table.

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

Y

OFSAA_CONF_TBSP

OFSAA_DATA_TBSP

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(s) 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.

<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 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 a 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 Hostname or web application server IP or 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

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

UPLOAD_MODEL

To perform the Model Upload.

0: No

1: Yes

Mandatory

MODEL_TYPE

The released data model or customized data model.

0: Released

1: Customized

Mandatory only if you want to upload the data model.

DATAMODEL

The path for the customized data model.

Not Applicable

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

DM_DIRECTORY

The file name for the customized data model.

Not Applicable

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

OFS_IBCE_SCHEMA_IN.xml

OFS_IBCE_SCHEMA_BIGDATA_IN.xml

OFS_IBCE_PACK/schema_creator/conf

OFS_IBCE_SCHEMA_IN.OUTPUT.xml

OFS_IBCE_PACK/schema_creator/

Silent.props

OFS_IBCE_PACK/appsLibConfig/conf