8.4 Post Installation Steps

Following are the post installation steps:

Note:

Ensure that you take a backup of the realtime_processing folder in the Installed Area.
  1. Navigate to the <INSTALLED_AREA>/realtime_processing/WebContent/conf path and make the following changes in the install.properties file:
    1. Replace the <RTI_INFODOM> placeholder with the existing Infodom value
    2. Replace the <RTI_SEGMENT> placeholder with the value SF
    3. Replace the <RTI_APPID> placeholder with the value OFS_TFLT
  2. Configure IPE in web application servers in real time mode. See section Configuring IPE in Web Application Servers for Real Time Mode in the OFS IPE Configuration Guide on OTN.
  3. Copy the spring-postSacalert.properties file from the path $FIC_HOME/ Transaction_Processing/WebContent/conf/ext to the path $FIC_HOME/ Fedwire_Processing/WebContent/conf/ext and $FIC_HOME/ Sepa_Real_Time_Processing/WebContent/conf/ext.
  4. Execute the ant.sh file from the <INSTALLED_AREA>/Transaction_Processing/path. This generates a WAR file and EAR file. Deploy the EAR file. For more information, see Creating andDeploying EAR/ WAR File.
  5. For information on the post-installation steps for real time mode and replacing the placeholders (jndi_java.naming.provider.url and jndi_java.naming.security.credentials parameters) in the IPE Screen, see Post Installation Steps and Configurations for Real Time Mode. Both these parameters are applicable for the CLEAN RESPONSE Transaction, HOLD RESPONSE Transaction, and TRANSACTION FILTERING FEEDBACK JMS MESSAGE actions.
  6. For information on configurations for Real Time mode, see Post Installation Steps and Configurations for Real Time Mode.
  7. To do an RTI Assessments import, navigate to the <INSTALLED_AREA> / Transaction_Processing/IPEAssessmentImport/ RTIExport_TransactionFiltering_IPE_Assessments.xml path and follow these steps:
    1. Login to the Server where application layer is installed.
    2. Navigate to the <FIC_HOME>/ficapp/common/FICServer/bin path.
  8. Execute the /RTIImport.sh $1 $2 $3 $4 command. In the above command:
    • $1 is the File name which has to be imported along with the absolute path where file exists
    • $2 is the infodom
    • $3 is the APP ID

    Note:

    The value of $4 should always be false.

    For example,

    RTIImport.sh <INSTALLED_AREA>/Transaction_Processing/ IPEAssessmentImport/RTIExport_TransactionFiltering_IPE_Assessments.xml ##TFLTINFODOM## OFS_TFLT false

  9. Make the following changes in the Admin Screen:
    1. Select Audit (Yes for Logging level = DEBUG, No for Logging level = INFO)
    2. Enter EDQ SOAP Url
    3. Enter Feedback Url (For sending the feedback message to the feedback queue)
    4. Enter Refresh Interval (Notification Count on the Transaction Filtering Screen will get refresh after these many milliseconds).

      Note:

      Step 4 to Step 8 are only valid for Transaction Filtering (TF).
  10. Copy the config folder from $FIC_HOME/SanctionsCommon folder in to EDQ.local.home.
  11. Create a Wallet on the EDQ server. Using the Wallet, you can establish the database connection and save the database details. For information on creating a wallet, see Creating a Wallet.
  12. Copy the ##EDQ_INSTALLATION_PATH##/edq/oracle.edq/jmxtools.jar file into the ##FIC_DB_HOME##/lib folder. If this step is not done, the EDQ call from the CS run will fail.
  13. Go to the Director.properties file in the /scratch/ofsaebas/Oracle/Middleware/ Oracle_Home/user_projects/domains/base_domain/config/fmwconfig/edq/oedq.local.home path.
  14. In the Director.properties file, comment [expr]management.port = clustered ? -1 : 8090.
  15. In the Director.properties file, add "management.port = 8090".
  16. To configure users in the AAI_EMAIL_CONFIG table in the Config schema, see Oracle Financial Services Analytical Applications Infrastructure Administration Guide , SMTP Server Configurations section.
  17. Add an entry in the Configuration table as shown below:

    insert into CONFIGURATION (PARAMNAME, PARAMVALUE, DESCRIPTION) values ('OFS_OFS_TFLT_ADDHIGHLIGHTSFILTERS', 'TRUE', null)

  18. To enable logger level, run the following query in the Config Schema.

    update aai_dyn_svcs_servers set V_LOGGERLEVEL='0' where v_loggerlevel is NOT NULL;