About the Archive Browser

To maintain optimal database performance and comply with strict data retention policies, Automic Automation administrators regularly archive historical data. The Archive Browser is a standalone web application designed to completely transform how you interact with this offline data.

When you extract data using the AE DB Archive utility (ucybdbar), the system generates flat, 7-bit ASCII archive files. Previously, searching through these offline files to find a specific historical record was a time-consuming challenge. The Archive Browser resolves this by utilizing Apache Lucene to index the exported files. This empowers administrators and operators to perform lightning-fast, full-text searches across millions of archived records instantly, all without requiring an active connection to your live Automic Automation database.

Who Should Use the Archive Browser?

The application provides a highly responsive, user-friendly interface that delivers significant value across multiple roles:

Administrators

Audit system events, trace infrastructure issues and Agent disconnects without impacting the performance of the live production environment.
Operators

Troubleshoot historical task failures by reviewing past execution statuses, timestamps, and full output reports.
Support Engineers

Investigate past system behaviors and trace error codes to resolve complex support tickets.
Developers

Analyze historical execution logs and operator notes to optimize future Workflow designs.

Browsable Data Categories

Once your Automic Automation data is archived and indexed, the Archive Browser categorizes it into four primary, easily searchable views:

Executions (Archive Header - AH)

The core archived execution headers. This includes critical run details such as the Run ID, object name, end status, timestamps, the user who triggered it, and the host platform.
Reports (Report Header - RH)

The complete output and log files generated during an execution, such as Activation (ACT) reports, Execution (REP) reports, and other type-dependent logs. The available data for each file includes the report type, the date and time of report creation, and the file size in bytes.
Messages (Meldung - ML)

The archived Automic Automation system messages. Each record provides the date and time of the message, the component that created the message, the message category and type, the originating Client and host, and the full message text.
Comments (Comment - CO)

Any user-entered notes or explanations that were attached to the executions by operators within the Automic Automation Client.

By making these historical records highly accessible and easily searchable, the Archive Browser ensures your offline data remains a valuable asset for troubleshooting and compliance, rather than just a storage requirement.

Important! The Archive Browser does not support UTF-8. Because it indexes the resulting 7-bit ASCII archive files, it can neither display UTF-8/multi-byte characters, nor can you search for UTF-8 strings such as specific archive keys.

How This Documentation is Organized

To help you quickly find the exact information you need, the Archive Browser documentation is structured into the following main sections:

Setup, Installations and Administration

Provides system administrators with the necessary steps to deploy the application, configure LDAP or built-in authentication, manage users, and point the application to your generated archive folders.
Using

Offers a comprehensive, task-based guide for operators and administrators. It covers everything from getting started and navigating the interface to filtering millions of executions, analyzing raw report files, and investigating system-wide messages. It also includes practical scenarios to help you master the tool.
REST API

Explains how developers and administrators can leverage the built-in REST API to programmatically access indexed archive data, enabling custom integrations and automated reporting.
Troubleshooting

Provides actionable solutions to common issues you might encounter while indexing files or searching your historical data.

Whether you are a system administrator setting up the application for the first time or an operator searching for a specific historical failure, these sections are designed to help you extract maximum value from your archived offline data.