By default, Sterling B2B Integrator writes its logs to the logs directory under the installation directory. Each time the system starts, the logs created since the previous start are moved to a time-stamped subdirectory, so logs from before a restart are archived on the file system and do not appear as current entries in the user interface. Components that run as separate processes keep their own output apart from the main logs. Each adapter container, which runs as its own JVM and acts like a cluster node, writes its logs into a separate subdirectory named for that container. The external purge process, which runs outside the main server, writes its log files to a separate PURGE subdirectory, for example logs/PURGE/extpurge.log. These facts make statements B and C correct. Statement A is wrong because the interface shows only part of what exists on disk: it displays the most recent lines of current log files, and old logs are removed once the configured maximum number of files is exceeded. Statement D is wrong because external purge logs are read from the file system rather than the Operations > Logs page, and statement E conflicts with the archiving behaviour described above.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit