7.17 Execution Logs

Case Flow Engine logs (.log and .err) file used to get generated under $FIC_DB_HOME/log/FusionApps.

From v8.0.6.0.0 onwards, the logs are generated in the following folder locations:

Figure 7-42 Folder Structure of Execution Logs

Note:

Here, <Component Name> maps to V_COMPONENT_ID from COMPONENT_MASTER table for specific V_PROG_ID where V_PROG_ID represent App Specific executable name.

To achieve this, follow these steps:

• The installer provides a new environment variable OFSAA_LOG_HOME that points to FTPSHARE/logs folder’s location.
• Engine reads $OFSAA_LOG_HOME value to find the location of the log and creates the folder structure in the following order, if not present.

Figure 7-43 Folder Structure Example of Execution Logs

The log file name is prefixed with the Component name (mentioned above) instead of prefixing the log file name with “<executable>.”

Entry is available in the “.ini” file (e.g. for ALM its ofsrm.ini) named “ComponentName” which is configurable and initially set the same present in COMOPNENT_MASTER table for the respective application. Add this entry in .ini file if it is not available.

Note:

You can make some changes in the .ini file to improve the cash flow engine performance.

Add CursorSharingMode entry in .ini file.

Engine reads the value against Key CursorSharingMode and sets

CURSOR_SHARE at the DB Session level accordingly.

The engine executes the following statement if the value set against CursorSharingMode Key.

ALTER SESSION SET CURSOR_SHARING = <Input Value> in upper case <Input Values>: EXACT, FORCE, SIMILAR

If the value is not supplied, then Engine would NOT set any alter statement. In case of upgrade path, installer takes care of renaming CFE artifacts (log files/folders) from Cash Flow Engine to Asset Liability Management. This allows you to view existing engine log files (generated during 8.1) from View Logger.