OFSAAI Related FAQs

The different components of OFSAAI are illustrated in following figure. For more information, refer to Components of OFSAAI section of the OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

OFSAAI can be installed in two modes- Silent Mode, and GUI mode.

No, OFSAA Infrastructure components (ficapp, ficweb, ficdb) cannot be installed on multi-tier. By default, they will be installed on single-tier. However, OFSAA Infrastructure can be deployed within the n-Tier architecture where the Database, Web Server and Web Application Server are installed on separate tiers.

JDK is not required during installation of OFSAA and only a run time is needed. For details, see Hardware and Software Requirements section in  OFS Advanced Analytical Applications Infrastructure Application Pack Installation and Configuration Guide .

Only JRE (Java Runtime Environment) is required during installation of OFSAA and cannot be uninstalled as the JRE is used by the OFSAA system to work.

Refer to OFSAA Technology Stack Matrices.

The following files are required to install OFSAAI:

·       setup.sh.

·       envCheck.sh

·       preinstallcheck.sh

·       VerInfo.txt

·       OFSAAInfrastructure.bin

·       validatedXMLinputs.jar

·       MyResources_en_US.properties

·       log4j.xml

·       OFSAAI_PostInstallConfig.xml

·       OFSAAI_InstallConfig.xml

·       privileges_config_user.sql

·       privileges_atomic_user.sql

"Execute Permission denied"

Check whether all the files provided for OFSAAI installation have execute permissions.

To give execute permissions, follow these steps:

Navigate to the path OFSAAI_80000 and execute the command

chmod 755

"Graphical installers are not.."

If error resembles "Graphical installers are not supported by the VM. The console mode will be used instead..." then check whether any of the X-windows software has been installed.

Example: Hummingbird Exceed is started and configured to Graphical mode installation.

Note: Type xclock from prompt and this should display clock in graphical mode.

"No Java virtual machine could be..."

If the error message reads "No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program", then

·       Check whether "java path" is set in PATH variable. Refer the  Prerequisite Information section in the document OFS Advanced Analytical Applications Infrastructure Application Pack Installation and Configuration Guide.

·       Check whether sufficient temporary space is available.

·       Ensure that the movement of OFSAAI Installer text files to the target system is done in the Text mode so that setup.sh file does not contain control line feed characters (^M).

Check whether the provided path for Oracle Driver files is correct and whether the user has permissions to access the files.

OFSAAI installer validates the database details provided during installation.

You need to verify the following:

• Verify that the oracle schema user has the required set of privileges for successful installation.

• Verify the oracle schema user has been created with quota privileges on tablespace to create database objects.

For more information, refer Prerequisite Information section in the document OFS Advanced Analytical Applications Infrastructure Application Pack Installation and Configuration Guide .

After successful completion of OFSAAI installation, one has to perform the Post Installation steps. For more information, refer Post Installation Configuration chapter in OFS Advanced Analytical Applications Infrastructure Application Pack Installation and Configuration Guide  .

OFSAAI installer generates log file OFSAAInfrastructure_Install.log in the Infrastructure installation directory. There is also another log file created in the path configured in Log4j.xml. The logs of any of these reported, Warnings/Non Fatal Errors/Fatal Errors/Exceptions should be brought to the notice of the OFSAAI Customer Support. It is recommended not to proceed with installation, until the reported problems are adequately addressed.

OFSAAI can be completely uninstalled by performing the steps provided in the Uninstalling OFSAA Installation section in OFS Advanced Analytical Application Infrastructure Installation and Configuration Guide.

OFSAAI requires both Config and Atomic Schemas to be present on the same database instance.

If you are creating a new information domain, provide a set of privileges (database permissions) to the new Atomic Schema.

To provide the privileges, follow these steps:

• Log into the database as sys and connect as sysdba user.

• Execute the file privileges_config_user.sql available under $FIC_HOME directory

• Enter the database schema for which you want to grant privileges.

Refer to the Multiple Language Select Utility section in OFS Analytical Applications Infrastructure Administration Guide available on OTN.

OFSAAI supports the Oracle Linux versions from 5.5 up to 5.10 and also from 6.0 and above.

To resolve the error, follow these steps:

1. Login as root user on the Unix machine where OFSAAI is being installed.

2. Navigate to the path /etc/security/.

3. Edit the file limits.conf to add or edit a row for the unix user installing OFSAA:

<Unix User> soft nofile 9216

4. After saving the changes, log in as the unix user used for OFSAAI is installation and execute the following command:

ulimit -n

The command should return the value 9216.

To verify the system environment meets the minimum requirements for the installation, a Pre-Install Check utility is available within the Install Kit archive file. This utility can also be obtained separately by contacting Oracle Support.

Refer to the Verifying System Environment section in the OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

The OFSAA Infrastructure installation performs a post install health check automatically on successful installation of the product.

To rerun the post install verification at a later time, follow these steps:

1. Navigate to the path $FIC_HOME (Product Installation Directory).

2. Execute the command:

./piverify.sh

Certain set of configuration steps must be performed during the installation in GUI mode. Verify the steps provided Configuration for GUI Mode Installation section are done correctly. For more information refer, OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

If any errors or exceptions occur during installation, follow these steps:

1. Backup the installation logs.

2. Share the backup logs with Oracle Support Services.

This happens if the time zone is not set, that is NULL or it is set as ’localtime’.

Set the environment variable TZ to a valid time zone region in the .profile file.

For example,

TZ=Asia/Calcutta export TZ

If the installation is abruptly terminated, then the installation will be incomplete.

To recover from this, follow these steps:

1. Drop the DB objects in the config schema created by OFSAAI installation.

2. Open the .profile and remove the entries made by the OFSAAI installation between the comment statements, #Beginning of entries by OFSAA Infrastructure installation and #End of entries by OFSAA Infrastructure installation.

3. Delete the OFSAA install directory created by the OFSAAI installer.

4. Perform the OFSAAI installation again.

No, all the supported softwares and versions are stated in the OFSAA Technology Stack Matrices available at http://docs.oracle.com/cd/E55339_01/homepage.htm.

This happens while running several database intensive tasks in parallel. To correct this error, add the line securerandom.source=file:/dev/./urandom in the java.security configuration file available in $JAVA_HOME/jre/lib/security/ path.

Note: This must be configured on all machines or VMs where the OFSAAI components are installed.

If the issue is not resolved after verifying these settings, check the MTU(Maximum Transmission Unit) settings on the linux box.

For details on how to update MTU settings and updating them, contact your system Administrator.

Syntax or file not found error messages typically appear in the following circumstances:

• The installer was not unzipped correctly or corrupted during unzip.

• The setup.sh file which resides within the install archive was not transferred in ASCII or text mode. This could have corrupted the file.

To correct this, follow these steps:

1. Copy the installer (in BINARY mode) to the system on which the OFSAA Infrastructure components will be installed.

2. Unzip the installer using the command:

unzip <OFSAAI_Installer>.zip

3. The corrupted setup.sh file may have introduced certain ^M characters into the file. You can remove ^M characters from setup.sh file by following these  steps:

   1. Login to the server where the installer is copied.

   2. Navigate to the directory OFSAAI_80000.

   3. Open the setup.sh file in the vi editor using the command: vi setup.sh.

   4. Inside vi editor in Esc mode, type: %s/^M//g
      Note: To enter ^M, hold the CTRL key then press V and M in succession.

1. 5. Save the setup.sh file by typing: wq!

Syntax or file not found error messages typically appear in the following circumstances:

• The installer was not unzipped correctly or corrupted during unzip.

• The setup.sh file which resides within the install archive was not transferred in ASCII or text mode. This could have corrupted the file.

To correct this, follow these steps:

1. Copy the installer (in BINARY mode) to the system on which the OFSAA Infrastructure components will be installed.

2. Unzip the installer using the command:

unzip <OFSAAI_Installer>.zip

3. The corrupted setup.sh file may have introduced certain ^M characters into the file. You can remove ^M characters from setup.sh file by following these  steps:

   1. Login to the server where the installer is copied.

   2. Navigate to the directory OFSAAI_73300.

   3. Open the setup.sh file in the vi editor using the command: vi setup.sh.

   4. Inside vi editor in Esc mode, type: %s/^M//g
      Note: To enter ^M, hold the CTRL key then press V and M in succession.

1. 5. Save the setup.sh file by typing: wq!

Syntax or file not found error messages typically appear in the following circumstances:

• The installer was not unzipped correctly or corrupted during unzip.

• The setup.sh file which resides within the install archive was not transferred in ASCII or text mode. This could have corrupted the file.

To correct this, follow these steps:

1. Copy the installer (in BINARY mode) to the system on which the OFSAA Infrastructure components will be installed.

2. Unzip the installer using the command:

unzip <OFSAAI_Installer>.zip

3. The corrupted setup.sh file may have introduced certain ^M characters into the file. You can remove ^M characters from setup.sh file by following these  steps:

   1. Login to the server where the installer is copied.

   2. Navigate to the directory OFSAAI_73300.

   3. Open the setup.sh file in the vi editor using the command: vi setup.sh.

   4. Inside vi editor in Esc mode, type: %s/^M//g
      Note: To enter ^M, hold the CTRL key then press V and M in succession.

1. 5. Save the setup.sh file by typing: wq!

The OCI client and the jdbc driver do not change depending on whether it is a standard or enterprise edition. OFSAAI will work with standard edition as well.

We do not recommend standard edition because it will not scale and does not support partition pack, database security vault, or advanced analytics.

Follow these steps:

• Ensure JAVA_BIN environment variable path is set on the "unix user" terminal from where the reveleusstartup.sh file is invoked.

• Ensure the .profile where the environment/ path settings are made has been executed successfully.

 

Ensure that, the System Password provided matches with the "Oracle Configuration password" provided during installation. Also check whether the connection to the "configuration schema" can be established through sqlplus.

Ensure OFSAAI servers have been started and are running successfully. For more information about the server start up parameters options, refer Starting Infrastructure Services section in OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

For more details on the issue, refer on to the Revappserver log in $FIC_APP_ HOME/common/FICServer/logs directory or the Web Server log files.

The "Oracle schema" user requires the necessary grants specified before, during, and after the installation process. Grants provided should never be revoked as the application makes use of these grants frequently.

OFSAAI Application server can be scaled out/distributed across different JVM's (machines) based on the various services and Information Domains. In other words, Load balancing could be achieved with distribution of services.

FTPSHARE is a Metadata Repository directory. All the metadata related files used in Infrastructure are stored in the FTPSHARE directory. The FTPSHARE contains folders for each Information Domain, with each Information Domain folders holding Erwin, log, and scripts folder. The transfer of data among the Web, Application, and Database servers in Infrastructure takes place through FTP/SFTP.

You need to configure FTP/SFTP and enable communication between the servers by providing  the App server's FTP/SFTP credentials to the Web server and DB server users.

Yes, you can have FTPSHARE on another machine other than the machines where OFSAAI is installed.

Yes, OFSAAI needs credentials of the user who has complete permissions on the  FTPSHARE directory, and he should be able to independently login to the unix server.

It is recommended to provide permissions on FTPSHARE in case of installations done across different machines or VMs (multi-tier installation).

For single tier installation, 770 permissions can be provided if the Unix users of OFSAAI and web server belong to the same unix group.

Additionally, any new file that is created in the FTPSHARE folder of any installation layer should be granted specific/explicit permission.

Port Change utility could be used to have the Port numbers which are currently being used by the Infrastructure application modified. For more information, refer the Changing IP/ Hostname, Ports, Deployed Paths of the OFSAA Instance section in OFS Analytical Applications Infrastructure Administration User Guide in OTN.

The three in-built system administration users are provided to configure and setup OFSAAI.

• SYSADMN

• SYSAUTH

• GUEST

OFSAAI supports both FTP and SFTP configuration.

Yes, enabling of FTP/SFTP services and its ports is a pre-requisite step towards using OFSAAI.

• Ensure the input User ID, Password, and Share Name are correct.

• Ensure FTP/SFTP services are enabled.

• Have a test FTP/SFTP connection made and confirm if they are successful.

Information Domain is mapped to only one Database; and thus before the creation of Information Domain, at least one database details should exist.

To resolve the error, follow these steps:

• Verify the connection to the Configuration Schema" can be established through SQL*Plus.

• Verify the Configuration Schema password is modified post installation.

• Ensure that the Oracle Database Alias name created for the Oracle Instance and Oracle Service Name are same.

• On multi-tier Installation mode, ensure TNSNAME and SID are same in both the Application and Database Layers.

Ensure that the Reveleus.sec file exist under the $FIC_HOME/conf directory where the Database components are installed.

OFSAAI supports LDAP configuration and authentication.

Yes, OFSAAI supports multiple languages.

OFSAAI does not have built-in back up facility. External Storage Infrastructure is recommended for back-up.

OFSAAI provides security at the following levels:

• Segment Level - Users can access only the segment they are mapped to.

• Application Level - Users can perform an operation only if mapped to appropriate role and functions.

OFSAAI provides configurable parameters to define the number of days after which the user password would expire and then the user is forced to change the password after the expiration period.

OFSAAI enforces a minimum password length with a combination of Upper and Lower case characters and alpha-numeric strings.

OFSAAI now supports ERwin version 9.2 and 9.5 generated xmls in addition to ERwin 4.1, ERwin 7.1, ERwin 7.3 and ERwin 9.0 formats.

OFSAAI provides two mechanisms for business data model upload:

• Easy to use GUI based Model upload mechanism to upload the Business Data Model through Data Model Management -->Data Model Maintenance -->Import Model.

• OFSAAI also provides a model upload utility "upload.sh" for uploading the business data model through the command line parameter by executing this shell script file under the path <FIC_HOME>/ficapp/common/FICServer/bin. For details, see Configuration for Model Upload Utility section of the OFS Analytical Applications Infrastructure User Guide available in OTN.

A modified data model can be uploaded into the system and OFSAAI has the ability to compare the changes within the data model with the data model already present in the system and enables propagation of incremental changes in a consistent manner.

OFSAAI supports uploading of business data model from client desktop and also by picking up the data model from the server location.

The OFSAAI Configuration Schema password can be modified post installation.

To change the Config Schema password, perform the following steps:

1. Change the Config schema User Password in the database.

2. Delete the $FIC_HOME/conf/Reveleus.SEC file.

3. Shutdown the OFSAAI App service:

cd $FIC_APP_HOME/common/FICServer/bin

./stopofsaai.sh

4. Start the Infrastructure Server in foreground directly on the server or through X-Windows software using the command:

./startofsaai.sh

5. At the prompt, enter System Password. Enter the "new Config schema" password. The service will start and initialize itself if it is able to successfully connect to the DB.

6. If you are using Apache Tomcat as Web server, update the <Context> -> Resource tag details in Server.xml file from the $CATALINA_HOME/conf directory. For Tomcat, both Config Schema (FICMASTER resource) and Atomic Schema (<INFODOM_NAME> resource) exist.

If you are using WebSphere as Web server:

5. 1. Login to the WebSphere Administration Console, from the left side menu.

   2. Navigate to Resources >JDBC >Data Sources. A list of data sources will be populated on the right side.

   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic data sources will need to be modified).

If you are using WebLogic as Web server:

1. 1. Login to the WebLogic Administration Console, from the left side menu

   2. Under Domain Structure list box, expand the appropriate Domain and navigate to Services > JDBC >Data Sources. A list of data sources will be populated on the right side.

   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic data sources need to be modified).

7. Post successful startup of the service, if required, the Infrastructure server may be shut down and restarted in the background using nohup mode.

The OFSAAI "Atomic Schema" password can be modified. The OFSAAI application stores the atomic schema password in the database and few configuration files , thus any change to the atomic schema password would necessitate updating the password.

To change the Atomic Schema password, perform the following steps:

1. Change the Atomic Schema User Password in the database.

2. Login to the application from the browser using SYSADMN account or any user id, which has System Administrator role mapped.

3. Navigate to System Configuration > Database Details window. Modify the password as explained in the following steps:

   1. From the Database Master window, select the connection whose password you want to modify and click button from the toolbar.

   2. Click button corresponding to the Alias Name. The Alias Details window is displayed.

   3. Modify the password in the Auth String field.

4. If you are using Apache Tomcat as Web server, update the <Context> -> Resource tag details in Server.xml file from the $CATALINA_HOME/conf directory. For Tomcat, both Config Schema (FICMASTER resource) and Atomic Schema (<INFODOM_NAME> resource) exist.

If you are using WebSphere as Web server:

5. 1. Login to the WebSphere Administration Console, from the left side menu.

   2. Navigate to Resources >JDBC >Data Sources. A list of data sources will be populated on the right side.

   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic data sources will need to be modified).

If you are using WebLogic as Web server:

1. 1. Login to the WebLogic Administration Console, from the left side menu

   2. Under Domain Structure list box, expand the appropriate Domain and navigate to Services > JDBC >Data Sources. A list of data sources will be populated on the right side.

   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic data sources need to be modified).

5. Restart the OFSAAI services.

Note: If the modified passwords are not updated, OFSAAI logs displays the message ORA-28000: the account is locked.

Business data model upload through OFSAAI depends on the Java memory settings on the client and server machines. The Java memory setting varies with the data model size and the available RAM. Contact Oracle Support Services for more details.

The Log file in DynamicServices.xml which resides in $FIC_HOME/conf is continuously being updated/refreshed to cache metadata. This can be observed when you are starting reveleusstartup.sh and if any of the log file (for example, SMSService.log) in DynamicServices.xml are being continuously refreshed for longer time.

By default, the Metadata Log file cache size is set to 1000. If the log is being updated beyond this limit, the preceding entries are overwritten. For example, the 1001th entry is overwritten by deleting the first entry. This results in the application screen taking a longer time to load.

Increase the cache size limit in Dynamicservices.xml located at <FIC_HOME>/conf, depending on the currently logged count for the specific metadata.

1. Generate the Log report by executing the below query in Configuration Schema.

select count(1), t.metadata_name, m.dsn_id

from metadata_master m, metadata_type_master t

where m.metadata_type = t.metadata_type

group by t.metadata_name, m.dsn_id

2. The above query returns a list of codes with their respective metadata count. You can refer to "metadata_type_master" table to identify the metadata name.

3. View the log report to identify the metadata which is being updated/refreshed beyond the specified cache size limit. Accordingly increase the cache size limit in Dynamicservices.xml depending on the currently logged count for the specific metadata.
   For example, if the "MEASURE_CACHE_SIZE" is set to 1000 and total measure reported in log is 1022, increase the limit to 2000 (approximately).

4. Restart Reveleus/OFSAAI servers (Web and APP) and check the issue.

The Java memory should be increased in ejbdeploy.sh file which is present under <WebSphere Install directory>/AppServer/deploytool/itp. For example,

$JAVA_CMD \

-Xbootclasspath/a:$ejbd_bootpath \

Xms256m -Xmx1024m \

In order to upload data model of size greater than 2GB in OFSAAI Unified Metadata Manager- Import Model, you need to configure the required model size in struts.xml file available in the path $FIC_WEB_HOME/webroot/WEB-INF/classes.

Note: The size requirements must always be specified in bytes.

For example, if you need to configure for model size of 2.5GB, then you can approximately set the max size to 3GB (3221225472 bytes) as indicated below, in order to avoid size constraints during model upload.

<constant name="struts.multipart.maxSize" value="3221225472"/>

After configuring struts.xml file, generate the application EAR/WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying EAR / WAR file, refer Creating and Deploying EAR/ WAR File section in OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

In some cases, the Hierarchy Filters do not save the edits correctly if the underlying Hierarchy has been changed. This can occur in hierarchy maintenance, where you have moved a member to another hierarchy branch, and that member was explicitly selected in the Filter and is now a child of a node which is already selected in the Filter.

Refer to Support Note for the workaround.

No, you cannot install an Application Pack on existing Atomic schema/Information Domain created manually. Application Packs can be installed only on Atomic Schemas/Information Domain created using schema creator utility and/ or the Application Pack installer.

Ensure you have created a folder "STAGE" under the path mentioned as "Local Path" in the web server details screen. This folder needs to be created under the local path on every node ,in case of web application server clustering.

Ensure the JRE referred in .profile is not a symbolic link. Correct the path reference to point to a physical JRE installed.

The following table lists the optimized memory settings required for "New" model upload.

Model Upload Options	Size of Data Model XML File	X_ARGS_APP ENV Variable in OFSAAI APP Layer
Pick from Server	106 MB	"-Xms1024m -Xmx1024m
	36 MB	"-Xms2048m -Xmx2048m
	815 MB	"-Xms4096m -Xmx4096m
	1243 MB	"-Xms6144m -Xmx6144m
Model Upload Utility	106 MB	"-Xms1024m -Xmx1024m
	336 MB	"-Xms2048m -Xmx2048m
	815 MB	"-Xms4096m -Xmx4096m
	1243 MB	"-Xms6144m -Xmx6144m
Save New Erwin File In Server	106 MB	"-Xms1024m -Xmx1024m
	336 MB	"-Xms2048m -Xmx2048m
	815 MB	"-Xms4096m -Xmx4096m
	1243 MB	"-Xms6144m -Xmx6144m

 

You should apply the below patch set from Oracle. This is applicable only for 12c. For more information, refer Doc ID 1937782.1.

Yes, follow the instructions explained in the OFS Inline Processing Engine Configuration Guide available on OTN.

Execute the below grant on the appropriate ATOMIC schema

grant olap_user to &database_username

Follow these steps to turn off unused infodoms from caching:

1. Navigate to $FIC_HOME/conf in the APP layer of your OFSAAI installation.

2. In the DynamicServices.xml file, identify the section for <Service code="20">.

3. Modify the value of parameter CACHE_ON_STARTUP to 0 (default is 1).

4. Repeat the same in the WEB layer too. Generate the application EAR/WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying EAR / WAR file, refer to the Creating and deploying EAR / WAR file section in OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

5. Restart the OFSAAI Services (APP and WEB). For more information, refer to the Start OFSAA Infrastructure Services section OFS Advanced Analytical Applications Infrastructure Installation and Configuration Guide.

Note: This setting will cache the Infodom metadata only for the infodoms that get accessed upon user login. Infodoms which do not get accessed, will not be cached.

Sample code is as follows:

<SERVICE CODE="20"

CLASS="com.iflex.fic.metadata.services.MetadataServiceProvider" NAME="BMD"

SERVERID="DEFAULT" PATH=" " LOGGERNAME="UMMLOGGER" LOGGERLEVEL="10">

<PARAMETERS>

<PARAMETER NAME="CACHE_ON_STARTUP" VALUE="0" />

<PARAMETER NAME="BACKUP_XML" VALUE="1" />

<PARAMETER NAME="MAX_BACKUP_XML" VALUE="2" />

<PARAMETER NAME="PC_NONBI_BI_SWITCH" VALUE="2048" />

<PARAMETER NAME="HIERARCHY_NODE_LIMIT" VALUE="2000" />

<PARAMETER NAME="ALIAS_CACHE_SIZE" VALUE="1000" />

<PARAMETER NAME="DATASET_CACHE_SIZE" VALUE="2000" />

<PARAMETER NAME="MEASURE_CACHE_SIZE" VALUE="2000" />

<PARAMETER NAME="HIERARCHY_CACHE_SIZE" VALUE="2000" />

<PARAMETER NAME="DIMENSION_CACHE_SIZE" VALUE="2000" />

<PARAMETER NAME="HIERARCHYATTRIBUTE_CACHE_SIZE" VALUE="1000" />

<PARAMETER NAME="CUBE_CACHE_SIZE" VALUE="1000" />

<PARAMETER NAME="RDM_CACHE_SIZE" VALUE="1000" />

<PARAMETER NAME="BUSINESSPROCESSOR_CACHE_SIZE" VALUE="2000" />

<PARAMETER NAME="DERIVEDENTITY_CACHE_SIZE" VALUE="1000" />

<PARAMETER NAME="LOG_GET_METADATA" VALUE="false" />

<PARAMETER NAME="METADATA_PARALLEL_CACHING" VALUE="0" />

</PARAMETERS>

</SERVICE>

Check if the excel mapping creation is done using Internet Explore 8 with JRE 1.4 plug in enabled on machine. If so, upgrade the JRE plug in to 1.7+.

No, only one OFSAA environment can be installed using one config schema.

OFSAAI requires both config and atomic schemas to be present on the same database instance.

Yes, it can be shared between two OFSAA instances.

The OFSAA Servlet port which is same as Web server port should be open. Also the web application port should be open.

Yes, NLS_LENGTH_SEMANTICS can be modified to BYTE from CHAR if you are not intending to use multi language support.

No, it is not possible to install the same application in two different infodoms.

OFSAA can have active-passive high availability.  For more details, refer Configuration for High Availability- Best Practices Guide available on OTN.

In case the web server is configured, you should enter the Web Server IP Address/Hostname and Port details during OFSAA installation. Here the Servlet port should be same as the Web Server port. 

If Web Server is not configured, the Web Application Server's IP Address/ Hostname and Port is required during the installation process. Here the Servlet port should be same as the Web application Server port.

No, ReveleusAdminConsoleAgent is not applicable starting OFSAAI 7.3.3.0.0. There is a change in the way agentservers are managed through AGENTSTARTUP.SH and AGENTSHUTDOWN.SH.

This error is displayed due to the following reasons:

•  The Config Schema password is already expired.

• If the Config Schema password is going to expire soon and the message like  "ORA-28002: the password  will expire within 6 days" displays while connecting to Config Schema through SQL Plus.

•  The Config Schema password is Modified.

To resolve the error, re-set the Config Schema password to the old password.

Else, if the Config Schema password is modified to something else, then follow the steps:

1. Delete the $FIC_HOME/conf/Reveleus.SEC file.

2. Shutdown the OFSAAI App service:
   cd $FIC_APP_HOME/common/FICServer/bin ./stopofsaai.sh

3. Start the Infrastructure Server in foreground directly on the server or through XWindows software using the command: ./startofsaai.sh

4. Enter System Password.

5. Enter the new Config Schema password. The service starts and initializes if it is able to successfully connect to the database and generates the Reveleus.SEC file.

6. Post successful startup of the service, if required, the Infrastructure server may be shut down and restarted in the background using nohup mode.

OFSAAI Log files created under $FIC_APP_HOME/common/FICServer/logs & <OFSAAI_DEPLOYED_AREA>/<CONTEXT.war>/logs is configurable in RevLog4jConfig.xml.

The default size of the log files (MaxFileSize) is set to max 5000kb & number of max backup log files (MaxBackupIndex) retained is set to 5, both of which are configurable. Increasing these parameters to a higher value should depend on the server HW configurations and may reduce the performance.

To configure the Logs file size on OFSAA Application server, follow these steps:

1. Navigate to $FIC_HOME/conf where OFSAA is installed.

2. Edit the following parameters in the file RevLog4jConfig.xml.

   1. <param name="file" : Enter the path where the Logs are to be generated.

   2. <param name="MaxFileSize" : Provide the required file size.

   3. <param name="MaxBackupIndex" : Provide the required number of backup files to be created

Example:

<appender name="REVSERVERAPPENDER" class="org.apache.log4j.RollingFileAppender">

<param name="file" value="$FIC_HOME/ficapp/common/FICServer/logs/RevAppserver.log"/>

<param name="Append" value="true" />

<param name="MaxFileSize" value="5000kb" />

<param name="MaxBackupIndex" value="5" />

<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="[REVELEUSLOG] %m%n"/>

</layout>

</appender>

To configure the Deployed area logs file, follow these steps:

1. Navigate to <EAR/WAR Deploy area>/conf folder.

2. Repeat step 2 from the above section.

 Yes, Log file path is configurable, it can be configured in RevLog4jConfig.xml.default log file path (file) is set by the installer . This can be configured to another path .

Follow these steps:

1. Create SSL related certificates and import to respective servers.

2. Enable SSL on a desired Port ( example 9443 ) on your existing and already deployed web application servers.

3. Replace the protocol as https and new ssl port (FIC_SERVLET_PORT) configured and in all the URLs specified on below files .

   1. $FIC_HOME/ficapp/common/FICServer/conf/FICWeb.cfg and $FIC_HOME/ficweb/webroot/conf/FICWeb.cfg

   2. $FIC_HOME/ficapp/icc/conf/WSMREService.properties

   3. $FIC_HOME/ficweb/webroot/conf/ModelExecution.properties

   4. $FIC_HOME/ficdb/conf/MDBPublishExecution.properties

   5. $FIC_HOME/ficdb/conf/ObjAppMap.properties

   6. $FIC_HOME/utility/Migration/conf/WSMigration.properties

   7. $FIC_HOME/utility/WSExecution/conf/WSExecution.properties

   8. $FIC_HOME/EXEWebService/WebSphere/ROOT/WEB-INF/wsdl/EXEWebServiceImpl.wsdl

   9. $FIC_HOME/EXEWebService/Tomcat/ROOT/WEB-INF/wsdl/EXEWebServiceImpl.wsdl

   10. $FIC_HOME/EXEWebService/weblogic/ROOT/WEB-INF/wsdl/EXEWebServiceImpl.wsdl

4. Replace XML attribute/Node values as specified on below files .

   1. $FIC_HOME/ficweb/webroot/WEB-INF/web.xml
             FIC_WEBSERVER_PORT=9443

   2. FIC_WEBPROTOCOL=https
            $FIC_HOME/conf/LookUpServices.xml and $FIC_HOME/ficweb/webroot/conf/LookUpServices.xml
            PORT="9443"
            PROTOCOL="https:"

5. Login to config schema and execute below SQL command to replace protocol and SSL port.

SQL> update configuration cn set cn.paramvalue='9443' where cn.paramname='SERVLET_ENGINE_PORT';

SQL> update configuration cn set cn.paramvalue=replace(cn.paramvalue,'http:','https:') where cn.paramname='FormsManagerCacheReload';

SQL> update web_server_info ws  set ws.servletport='9443',ws.servletprotocol='https';

6. Create EAR/WAR file and Re-Deploy.

This happens if there is a clock skew between the client and the KDC server. To resolve this, there are two solutions:

• Solution 1:

Synchronize the clocks between the servers. For more information, refer http://docs.oracle.com/cd/E19253-01/816-4557/setup-192/index.html

• Solution 2:
• 1. Set clockskew parameter on the server side(KDC) krb5.conf file and replace the same file in  HIVE_LIBRARY_PATH folder. Parameter value should be decided on the basis of the time difference between the two machines.

  2. Get the epoch time on the two servers by firing “date +%s” on the command line.

  3. Clockskew param value should be chosen as a value sufficiently larger than the difference of the above two calculated values.

  4. Set “clockskew = <value>” in the /etc/krb5.conf on the KDC server.

  5. Restart Kerberos services.

This occurs when  HADOOP_HOME environment variable is not set. You can ignore this exception since we do not mandate to install HIVE where OFSAA is installed.

If the metadata cache size is set to a lower value than the actual count of each metadata type ( hierarchy, dataset, dimension etc), then it gets into performance degrade issues. We have to increase the cache size for each  metadata type according to the count in the environment.

Following are the parameters in DynamicServices.xml to be configured depends  on the metadata count in your environment.

<PARAMETER NAME="HIERARCHY_NODE_LIMIT" VALUE="2000"/>

 <PARAMETER NAME="ALIAS_CACHE_SIZE" VALUE="1000"/>

<PARAMETER NAME="DATASET_CACHE_SIZE" VALUE="2000"/>

 <PARAMETER NAME="MEASURE_CACHE_SIZE" VALUE="3000"/>

<PARAMETER NAME="HIERARCHY_CACHE_SIZE" VALUE="2000"/>

<PARAMETER NAME="DIMENSION_CACHE_SIZE" VALUE="2000"/>

<PARAMETER NAME="CUBE_CACHE_SIZE" VALUE="1000"/>

<PARAMETER NAME="BUSINESSPROCESSOR_CACHE_SIZE" VALUE="2000"/>

<PARAMETER NAME="DERIVEDENTITY_CACHE_SIZE" VALUE="1000"/>

Metadata count can be derived based on the following queries:

select count(1) from metadata_master where metadata_version=0  --- for all metadata

select count(1) from metadata_master where metadata_version=0  and metadata_type=1  --- for measure

select count(1) from metadata_master where metadata_version=0  and metadata_type=2  --- for Dimension

select count(1) from metadata_master where metadata_version=0  and metadata_type=3  --- for HCY

select count(1) from metadata_master where metadata_version=0  and metadata_type=4  --- for DATASET

select count(1) from metadata_master where metadata_version=0  and  metadata_type=59  --- for BP's

select count(1) from metadata_master where metadata_version=0  and  metadata_type=54   --- for Alias

select count(1) from metadata_master where metadata_version=0  and  metadata_type=5  --- for CUBES

select count(1) from metadata_master where metadata_version=0  and  metadata_type=856  --- for Derived Entity

For LDAP authentication, the Application server (ficapp) connects with the LDAP server.

You need to import the certificate into the JDK/JVM used by Reveleus server in ficapp layer.

You can run the PortC.jar utility. For more details, refer Changing IP/ Hostname, Ports, Deployed Paths of the OFSAA Instance section in the OFSAAI Admin Guide available on OTN.

1. Navigate to $FIC_HOME folder on Target.
2. Run the PortC.jar utitlity using the command:

java -jarPortC.jar DMP

A file with the name DefaultPorts.properties will be created under $FIC_HOME directory which will contain the ports. For more information, refer Changing IP/ Hostname, Ports, Deployed Paths of the OFSAA Instance section in the OFSAAI Admin Guide available on OTN.

This error occurs while executing envCheck.sh because the user does not have access to V$parameter. This error does not occur due to sysdba or non sysdba privileges provided they have access/grants to V$parameter.

The workaround is:

1. Locate the webserver deployed area webroot/conf/excludeURLList.cfg file.

2. Modify the following entries:

[SQLIA]./dataIntegrator/ to [ALL]./dataIntegrator/

[SQLIA]./ETLExtractionServlet to [ALL]./ETLExtractionServlet

3. Save the changes and restart the webserver.

4. Resave the definition.

This error occurs when OLAP component is not configured and OLAP feature in OFSAA is not used. However, this error can be ignored.