1. Analytical Application Infrastructure User Guide
  2. References
  3. External Scheduler Interface Component
  4. Additional Information on ESIC

Additional Information on ESIC

This section includes the information regarding the miscellaneous details, dependencies, and error logging details for ESIC.

Miscellaneous Details and Dependencies:

  • ESIC resides on App Layer of OFSAAI.
  • ESIC expect the environment variable FIC_APP_HOME to be defined for configuration and log paths.
  • In case the environment variable FIC_APP_HOME is not defined, ESIC will exit with an error message on console.
  • ESIC and ICC Server share a single configuration file, which resides in FIC_APP_HOME/icc/conf.
  • ESIC resides in FIC_APP_HOME/icc/bin and paths to dependencies (ICC API library in this case) need to be set to FIC_APP_HOME/icc/lib.
  • The following processes are Java processes in platform, which contains environment variables as JVM parameters.
    • FIC Server
    • ICC Server
    • Model Upload
    • Rule Execution

Only these processes can be tracked using JVM commands like JCMD and JPS.

Error Logging for ESIC

ESIC opens a file in $FIC_APP_HOME/icc/log for logging and the file descriptor for that file is passed to the ICC API library for logging. The log file name for ESIC for each instance are as follows:

  • ESIC_<Date>_<Time>_<External Unique ID>_<TaskID>.log
ESIC log messages into a file only if the exit status values are -2, -12, -14, and –15. For more information see Exit Status Specifications. In all other cases, ICC Server logs the errors and the causes and ESIC only return the error value as an exit status.

Note:

<External Unique ID> and <Task ID> can be used wherever applicable.