The SAS Fraud Management SAS OnDemand Decision Engine logs are located in the /<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/logs directory.
SAS OnDemand Decision Engine contains two types of log files: SAS log files and JVM log files.
SAS logs contain names like sas_5018.log, sas_5019.log, sas_5020.log, sas_N.log, and so on.
The first SAS OnDemand Decision Engine SAS log file (for example, sas_5018.log) is for the SAS OnDemand Decision Engine SAS parent/primordial/main process. The other SAS log files are for the child/worked SAS OnDemand Decision Engine SAS processes.
The sas_5018.log is the SAS OnDemand Decision Engine SAS parent/primordial/main process, which contains the start-up logs and information, and is part of a bigger volume when compared with the others.
The SAS OnDemand Decision Engine SAS parent/primordial/main process log file (for example, sas_5018.log) is also called the SAS OnDemand Decision Engine SAS start-up log file.
The SAS OnDemand Decision Engine SAS logs are named per the SAS_SHM_KEY defined in the /<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/etc/ose.properties file.
SAS_SHM_KEY is 5018 by default. Therefore, the SAS OnDemand Decision Engine SAS log file names start with sas_5018.log, sas_5019.log, sas_5020.log, and so on.
In a scenario where you change SAS_SHM_KEY from the default 5018 to 965018 (or a different value), the SAS OnDemand Decision Engine SAS log file names start with sas_965018.log, sas_965019.log, sas_965020.log, and so on.
JVM logs contain names like console.log, ode.log, ode-1.log, ode-N.log, and so on.
These JVM log files are named per the MODE defined in the /<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/etc/ose.properties file in relation to the corresponding logging XMLs.
The console.log, the ode.log, or both will have the SAS OnDemand Decision Engine start-up log messages. Therefore, they are also referred to as the SAS OnDemand Decision Engine JVM start-up log files.
SAS OnDemand Decision Engine contains 50 10MB files (maximum) when run in PROD MODE.
As a result, you need to update the PROD MODE logging XML if it’s expected for SAS OnDemand Decision Engine to be kept running for a long period of time without being stopped or started.
If SAS OnDemand Decision Engine runs with the default PROD MODE 50 10MB files, then the older logs being written over or rolled off is an expected behavior.
The SAS OnDemand Decision Engine logs, both SAS and JVM logs, persist under /<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/logs until you stop or start them.
During SAS OnDemand Decision Engine redeployments, newer logfiles (both SAS and JVM logs) are created in the above directory, and the newer messages are recorded in them.
When you start SAS OnDemand Decision Engine, the logfiles (if any) under /<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/logs are moved to the SAS OnDemand Decision Engine archive directory below:
/<SASConfig>/Lev1/Applications/SASFraudManagement/<SFM Version>/<Authentication Domain>/engine/ServerN/archive/<sub-directories>/
<sub-directories> contain names like 20231212_155735-0500, 20250419_200635-0400, 20250710_050157-0400, and so on.
The SAS OnDemand Decision Engine archive sub-directories contain names in the YYYYMMDD_HHMMSS-<GMT/UTC OFFSET> format.
For example, 20231212_155735-0500 shows that the SAS OnDemand Decision Engine host runs in a time zone with -0500 GMT/UTC OFFSET or in the UTC-5 time zone.
20231212_155735 (that is,YYYYMMDD_HHMMSS) is the time at which SAS OnDemand Decision Engine was shut down.