6       Installation

1

Configure the OFS_DM_PACK.xml file.

2

Configure the OFS_DM_SCHEMA_IN.xml file. 

3

Configure the OFS DM_SCHEMA_BIGDATA_IN.xml file 

4

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

5

Configure the OFSAAI_InstallConfig.xml file. 

6

Trigger the installation. 

7

Apply post-installation mandatory patches

8

Verify the log files

9

Verify the installation

APP_PACK_ID

Unique Application Pack Identifier

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 remove these tags.

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 is the prerequisite set. For certain other applications, an appropriate Application ID would be set.

DO NOT modify this value.

APP_ID DEF_SEL_FLG

Default Selected Flag

Y

Default - YES

In all application packs, Infrastructure would have this value set to YES.

DO NOT modify this value.

APP_ID ENABLE

Enable Application/ Product

Y

Possible Values: YES or NO

·        YES for Infrastructure

·        NO for Others

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

Note: Application/ Product once enabled cannot be disabled. However, Application/ Product not enabled during installation can be enabled later through the Administration UI.

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>

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>

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

<IS_HYBRID>/ VALUE = TRUE

Flag to identify the mode of installation

Y

TRUE

This flag value should be TRUE in case of Hybrid mode of installation only.

<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 name would appear in the OFSAA Landing Page as Connected To: xxxx

The schemas being created would get this prefix. For E.g. 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

YES or NO

The default value is YES.

<PASSWORD>/ APPLYSAMEFORALL

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

If you enter 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

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

<PASSWORD>/ DEFAULT*

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

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

Note: Do not edit this attribute value.

Y

ATOMIC/CONFIG/SANDBOX/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 to 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 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 underscore _.

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

Fore.g., if you set ofsaaatm as the name 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: It is mandatory to 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/ 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.

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, 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 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/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 the OFSAA Reconciliation Framework Pack is the first media pack installation in the setup, then INFODOM has to be specified mandatorily else 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/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/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.

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

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

In the case of an HDFS ONLY target, this URL should be of the RDBMS instance that hosts the applications METADOM.

<JDBC_ DRIVER>

By default, this driver 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/ IP Address of the system on which you are installing the OFSAA components.

Y

Host Name/ IP Address

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

DEV, SIT, PROD

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

<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>/ APPLYSAMEFO RALL

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

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

Note: In case you have entered Y in the 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(s).

<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, the applications 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 schema 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 OFS AAAI Application Pack.

Only one CONFIG schema can exist in the file.

ATOMIC schema refers to the METADOM within the Information Domain.

CONFIGURATION schema holds the OFSAA setup details and other metadata information.

SANDBOX schema refers to the SANDBOX schema.

ADDON schema refers to other miscellaneous schemas (not applicable for this application pack).

Multiple ATOMIC/ SANDBOX/ ADDON schemas can exist in the file.

<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 underscore '_'.

SETUPINFO/ NAME attribute value will 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/ 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 - USERS

Permissible - 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 - 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 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/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/Hostname of the server where HIVE is installed.

Y

<HIVE_LIB_ PATH>

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

Y

Should contain the list of jars mentioned in the sections: Copy Jars to the OFSAA Installation Directory and Copy KEYTAB and KRB5 Files in OFSAAI. Manually copy the preceding listed files from CDH distribution to this identified folder.

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

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>/ 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/ IMPALA, etc.

<SCHEMA>/<P ROPERTY>/CO MMENT

COMMENTS for HIVE schema

N

<SCHEMA>/<P ROPERTY>/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.jdbc4.HS2Driver

The default Cloudera HiveServer 2 driver name.

<CONNECTION_ PROPERTIES>/<PROPERTY>/J DBC_URL

Enter HIVE JDBC URL

Y

JDBC URL format : jdbc:hive2://<FQDN>:<port>/<db>;AuthMech=1;KrbServiceName=<KrbServiceName>;KrbHostFQDN=<FQDN>;KrbRealm=<KrbRealm>

Example: jdbc:hive2://abc.in.oracle.com:10000/GLDATADOM;AuthMech=1;KrbServiceName=hive;KrbHostFQDN=abc.in.oracle.com;KrbRealm=ABC.ORACLE.COM

<db> name should be same as Datadom name given in <SCHEMA>/ NAME

<CONNECTION_ PROPERTIES>/<PROPERTY>/ AUTH_TYPE

Authentication Type

Y

Permissible values: KERBEROS_WITH_ KEYTAB

Only Kerberos with keytab based authentication is 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>

LOG_MODE

Mode for logging

1 = Debug

0= General

Default : 0

SEGMENT_1_CODE

Segment Code

Not Applicable

Provide a new segment code for OFSAA Reconciliation Framework Pack.

APFTP P_LOG_PATH=

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

Not Applicable

DBFTP_LOG_PATH

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

Not Applicable

HIVE_APPFTP_LOG_PATH

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

Not Applicable

Applicable only for Hybrid Installation

HIVE_DBFTP_LOG_PATH

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

Not Applicable

Applicable only for Hybrid Installation

UPLOAD_MODEL

Specify if you want to perform Model Upload for RDBMS

·        0 = If you have already performed Model Upload and want to skip the model upload process

·        1 = If you want to perform Model Upload

MODEL_TYPE

Specify if you want to use the released datamodel or customized datamodel for model upload process for RDBMS

·        0 = If you want to upload the released datamodel

·        1 = If you want to upload the customized datamodel

DATAMODEL

Specify the file (DATAMODEL) name for the customized datamodel for RDBMS

Not Applicable

Mandatory only if you want to upload the customized datamodel i.e. you have specified MODEL_TYPE=1

DM_DIRECTORY

Specify the path (DM_DIRECTORY) for the customized datamodel for RDBMS

Not Applicable

Mandatory only if you want to upload the customized datamodel i.e you have specified MODEL_TYPE=1

HIVE_UPLOAD_MODEL

Specify if you want to perform Model Upload for HIVE

·        0 = If you have already performed Model Upload and want to skip the model upload process

·        1 = If you want to perform Model Upload

Applicable only for Hybrid installation.

HIVE_MODEL_TYPE

Specify if you want to use the released datamodel or the customized datamodel for the model upload process for HIVE

·        0 = If you want to upload the released datamodel

·        1 = If you want to upload the customized datamodel

Applicable only for Hybrid installation.

DATAMODEL_HIVE

Specify the file(DATAMODEL) name for the customized datamodel for HIVE

Not Applicable

Applicable only for Hybrid installation.

Mandatory only if you want to upload the customized datamodel i.e. you have specified MODEL_TYPE=1

DM_DIRECTORY

Specify the path (DM_DIRECTORY)  for the customized datamodel for HIVE

Not Applicable

Applicable only for Hybrid installation.

Mandatory only if you want to upload the customized datamodel i.e. you have specified MODEL_TYPE=1

ETL_APPSRC_TYPE

Specify if you want create a new ETL Src or use an existing one

·        0 = If you want to create a new ETL src

·        1 = If you want to use an existing pair

ETL_SRC_1_NAME

Specify a new ETL Source Name for RDBMS

Not Applicable

ETL_SRC_2_NAME

Specify a new ETL Source Name for HIVE

Not Applicable

Applicable only for Hybrid installation.

ETL_SRC_1_DESC

Specify a new ETL Source Description for RDBMS

Not Applicable

ETL_SRC_2_DESC

Specify a new ETL Source Description for HIVE

Not Applicable

Applicable only for Hybrid installation.

Please enter Infrastructure FTP/SFTP password

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

31605076

Access features owing to the additional license functionality that get installed through the OFS AAI Extension Pack. Download and install this patch from My Oracle Support.

31498038

If you install OFSAA Reconciliation Framework Pack before any other OFSAA application, download and install this patch from My Oracle Support.