How to Identify and Retrieve 360Eyes Job Logs in 360Suite Tomcat

How to Identify and Retrieve 360Eyes Job Logs in 360Suite Tomcat

How to Identify and Retrieve 360Eyes Job Logs in 360Suite Tomcat

Overview

When a 360Eyes job fails, the execution log stored in the Tomcat logs folder is the fastest way to diagnose the issue.
This guide explains how logs are named, where they are stored, and how to quickly find the right file.

Task Logs vs. Full Job Logs

The 360Suite interface displays task logs, and users can also download them directly from the UI.
These task logs include useful information such as:

  • Basic job steps
  • High‑level status messages
  • Some warnings or execution notices

However, task logs are not complete. They represent only a subset of what actually happened during execution.

For effective troubleshooting, especially when collaborating with Wiiisdom Support, you must provide the full job log file stored in the Tomcat logs directory.
This file contains:

  • Full job arguments
  • REST/API calls
  • Internal engine operations
  • Detailed error stack traces
  • Timing information
  • Full extraction, audit, or parsing steps

The full log is the authoritative source required to analyze failures and performance issues.

Where 360Eyes Logs Are Stored

All 360Eyes job logs are located inside the Tomcat logs directory used by 360Suite.

Typical paths:

  • /opt/360suite/tomcat/logs/ (Linux)
  • C:\Program Files\360Suite\tomcat\logs\ (Windows)

The folder contains both standard Tomcat logs and job‑specific logs.

How 360Eyes Log Files Are Named

360Eyes log files follow a clear naming pattern based on your system’s behavior:

<JobType>-<CMSHost>_<CMSPort>-<YYYYMMDD-HHMMSS>.log

Meaning:

  • JobType: CMS, UNIVERSE, WEBI, AUDIT, SNAPSHOT
  • CMSHost: BO/360Eyes target system, e.g. BOBJPROD
  • CMSPort: CMS port number, e.g. 6400
  • Timestamp: Job start time

Example:

AUDIT-BOBJPROD_6400-20260203-162128.log

This corresponds to:

  • An AUDIT job
  • Running on BOBJPROD:6400
  • Started on 2026‑02‑03 at 16:21:28

How to Find the Right Log File

To locate the log for a failing job:

  1. Identify the job details in 360Suite Admin Console:

    • Job type
    • Target CMS
    • Execution timestamp

  2. Open the Tomcat logs folder or download the Tomcat log .zip by running this process: 360Suite | Downloading Tomcat Logs

  3. Filter files by job type and CMS name:

    • Example: WEBI-BODEV_6400-*.log

  4. Match the timestamp with the execution time shown in the console.

  5. Open the file to view:

    • Job parameters
    • Line‑by‑line execution information
    • Error messages
    • Document extraction indicators

Why These Logs Matter

Sharing this file with Wiiisdom Support is mandatory to accelerate troubleshooting.

Summary

  • Logs are stored in the Tomcat logs directory.
  • Log names follow: <JobType>-<CMSHost>_<CMSPort>-<timestamp>.log
  • Use job type + CMS + timestamp to locate the correct file.
  • Logs provide everything needed for fast diagnosis.

    • Related Articles

    • Read Tomcat Logs after 2025.1 upgrade

      Context 2025.1 made a lot of changes regarding log generation. Allowing users and support agent to be more efficient in the search of issues. The 360Suite Tomcat will now generate new files if old one are getting too large, this will only happen on ...

    • 360Suite database configuration is not set when restarting Tomcat server

      Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

    • 360Eyes evolution: from "standalone" to 360Suite web application

      Context On the meta-level, 360Eyes is part of 360Suite, a suite a modules working with BusinessObjects environments to help BI administrators with their day-to-day activities. On a practical level, the 360Eyes module itself has known changes over ...

    • Change Tomcat after 2025.1 upgrade

      Context To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21. This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 ...

    • How to configure 360Suite's Tomcat with HTTPS

      ? Purpose This article provides high‑level guidance for enabling HTTPS/SSL on Apache Tomcat 10.1.x. Because Tomcat is a third‑party application server, SSL configuration is outside the scope of our product support. The content below summarizes and ...