Delink ICC Server from FICServer

This section is applicable to 8.1.0.1.0+ versions only.

OFSAA predominantly has been a batch centric application that runs in the Application layer. With the increase in the number of batches running concurrently, the memory usage within the Application layer is adversely affected and this results in the slow performance of the applications. ICC server also has to-and-fro traffic requests to FICServer during batch executions to fetch its own metadata, which further degrades the performance of the application.

A way to improve the performance is to separate or de-link the ICC server from FICServer. ICC Server is enhanced to get its own metadata during batch executions without any dependency with FICServer.

Following are the advantages of delinking the ICC server from FICServer:

1. The load on FICServer during batch execution is reduced.
2. ICC server deployed on a different instance to FICServer helps in controlling the memory surge observed on FICServer.
3. You can execute batches concurrently even when the load on FICSERVER is at the peak level.
4. Execution engines with component types such as Load Data, Transform Data, Data Quality and RULE_EXECUTION can be successfully executed without any dependency on FICServer.
5. In case the FICServer is down:
   • You can create batches using the Manage Run Execution (WSMRERequest.sh) command line utility with any available component types.
   • You can execute batches through the ESIC (External Scheduler Interface Component) command line utility.
   This enhancement is available as a licensed option and the existing architecture of co-existence of ICC and FICServer continues as the default option.