IBM Support

Debug-Level Options for the IBM Content Navigator Installer

Troubleshooting


Problem

Installation of IBM Content Navigator may fail, hang, or complete with errors, while the standard installer output and default log files do not provide sufficient detail to determine the root cause. Additional debug-level and verbose logging is required to increase log detail and capture internal installer processing information for effective troubleshooting and problem determination.

Diagnosing The Problem

Enable debug‑level logging for the installer and reproduce the problem to generate detailed logs. These logs can then be reviewed locally to analyze installer behavior and failures.

Typical diagnostic goals:

  • Identify the exact installation phase where failure occurs
  • Capture stack traces and internal installer actions
  • Confirm environment detection, prerequisite checks, and file operations

Resolving The Problem

The following sections describe the supported approaches to enable debug‑level output and where to locate the resulting logs.

When to Use Debug Mode

Use installer debug mode when:

  • The installer fails without a clear error message
  • The installation hangs or exits unexpectedly
  • You need detailed logging for IBM Support
  • You are diagnosing environment, permission, or prerequisite issues

What Debug Mode Does

Running the installer in debug mode:

  • Produces verbose console output
  • Generates more detailed installation logs
  • Captures stack traces and internal installer actions

These logs are essential for root cause analysis.

Prerequisites

Before starting:

  • Ensure you have administrative/root privileges
  • Verify Java is installed and accessible (if using a platform‑independent installer)

Enabling Debug Mode:

Option 1: Universal InstallAnywhere Environment Variable (LAX_DEBUG)

The most direct way to enable debugging for an InstallAnywhere‑based installer is by setting the LAX_DEBUG environment variable before launching the installer.

Output to console:

Linux/UNIX:

export LAX_DEBUG=true (or) export IA_DEBUG=true
./IBM_CONTENT_NAVIGATOR*.bin

Windows (Command Prompt):

set LAX_DEBUG=true (or) set IA_DEBUG=true
IBM_CONTENT_NAVIGATOR*.exe

Option 2: Verbose Debug Arguments

Additional debug verbosity can be enabled by passing Java system properties to the installer launcher.

IBM_CONTENT_NAVIGATOR*.exe -Dlax.debug.level=3 -Dlax.debug.all=true

Option 3: Platform‑Specific Startup Methods

Windows – Keyboard‑Triggered Debug Mode
1. Launch the installer.
2. Immediately press and hold the Ctrl key.
3. Continue holding Ctrl until a console window or installer splash screen appears.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB18","label":"Miscellaneous LOB"},"Business Unit":{"code":"BU056","label":"Miscellaneous"},"Product":{"code":"SSEUEX","label":"IBM Content Navigator"},"ARM Category":[{"code":"a8m3p000000LRz9AAG","label":"IBM Content Navigator"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.0.0;2.0.1;2.0.2;2.0.3;3.0.0;3.0.1;3.0.10;3.0.11;3.0.12;3.0.13;3.0.14;3.0.15;3.0.2;3.0.3;3.0.4;3.0.5;3.0.6;3.0.7;3.0.8;3.0.9;3.1.0;3.2.0"}]

Document Information

Modified date:
02 June 2026

UID

ibm17256307

Page Feedback