3.1.1 Mandatory Post-Installation Steps
This section describes the mandatory post-installation steps.
- If the deployment environment is Solaris, follow the these mandatory steps to
set
gnu bin
directory in the PATH environment variable. For example: exportPATH=/usr/gnu/bin:$PATH.Note:
If thegnu bin
directory is different, replace/usr/gnu/bin
with the correct directory path. - Check the DB builder logs for successful execution of
mantas8.1.2.9.0_delta.cfg
anddelta_plat8.1.2.9.0.cfg
.If these did not run, then execute them manually. To do so, navigate to
$FIC_HOME/database/ mantas_schema/delta/oracle/8.0
and execute the following command:$FIC_HOME/database/db_tools/bin/run_dbbuilder_utility.sh $FIC_HOME/ database/mantas_schema/delta/oracle/8.0/mantas8.1.2.9.0_delta.cfg
When prompted, enter the Atomic user name and password. Then, navigate to
$FIC_HOME/ database/bus_mkt_schema/delta/oracle/8.0
and execute the following command:$FIC_HOME/database/db_tools/bin/run_dbbuilder_utility.sh $FIC_HOME/ database/bus_mkt_schema/delta/oracle/8.0/delta_plat8.1.2.9.0.cfg
.When prompted, enter the Atomic user name and password.
- Load BD scenarios in the Database from
$FIC_HOME/Database/db_tools/bin
with the sm_load.sh utility. For scenarios that are provided in this patch, see .Upgrade ScenariosNote:
Contact My Oracle Support in case of any errors. - Downgrade the
commons-logging
jar file from version 1.3.1 to 1.1.3 to fix the following issues:- Bug 37558428 - BD8129: Tomcat Deployed Side Logs Folder is Almost Blank No Log Files Getting Printed Like UMMSERVICELOG.
- Bug 37590204 - FCCM: Web Server Deployed Side Logs Folder is Almost Blank No Log Files Getting Printed Like UMMSERVICELOG.
- After installing the BD 8.1.2.9.0, perform the following steps:
- Copy
commons-logging-1.1.3.jar
from$FIC_HOME/database/db_tools/lib
to the following folders:$FIC_HOME/ficweb/webroot/WEB-INF/lib
$FIC_HOME/ficdb/lib
- Delete
commons-logging-1.3.1.jar
from the following folders:$FIC_HOME/ficweb/webroot/WEB-INF/lib
$FIC_HOME/ficdb/lib
- Copy
- Optional step: If you have a TBAML License, load scenarios
in the Database from
$FIC_HOME/ Database/db_tools/bin
with the sm_load.sh utility. For TBAML-specific scenarios, see TBAML Scenarios. - Once the above steps are done, create the following EAR/WAR file and redeploy
this new WAR on the Web Application server. Refer to the Oracle Financial Services Behavior Detection Applications
Pack Installation Guide Release 8.1.2.0.0 for steps related to
deployment.
Note:
For using Websphere Server, remove all thejackson*
Jars from the following folder before creating theOFSAAI EAR/WAR
file:$FIC_HOME/ficweb/webroot/externalib/WEB-INF/lib
. - Restart the OFSAAI services