Looking for the previous version? View v2024.06 documentation →
Middleware Information
Monitor middleware service health, restart the service, and download operational logs.
Overview
The Middleware Information section provides administrators with real-time visibility into the health and status of the Data Trust middleware service. You can view the middleware status, restart the service when needed, and download or view operational logs to diagnose issues. This section is critical for maintaining platform uptime and for troubleshooting connectivity problems.
Prerequisites
- You are logged in to Data Trust with an Admin Pro-User role.
- Admin Console access has been granted by your system administrator.
Navigating to Middleware Information
Path: Data Trust › Admin Console › System Preferences › Middleware Information
Figure 1: System Preferences navigation option
Navigate to Admin Console and select System Preferences to see all platform configuration tiles available for this Data Trust instance. This step requires an Admin Pro-User role; users without admin access will not see the Admin Console menu option. The System Preferences landing page is your starting point for all platform-level configuration and diagnostic tasks.
Figure 2: System Preferences — all options
All System Preferences tiles are displayed on this page, each representing a distinct configuration or diagnostic area. Locate the Middleware Information tile to access the service health check and log management interface. If you are troubleshooting a platform issue, Middleware Information is typically the first place to investigate after checking the application logs.
Figure 3: Middleware Information tile
Click the Middleware Information tile to open the status and log management interface for the Data Trust middleware service. This section shows the real-time service state (running, stopped, or error) and provides access to operational log files. Regular review of this section helps detect connectivity or performance issues before they impact end users.
Middleware Status Tab
Figure 4: Middleware Status tab
The Middleware Status tab shows whether the middleware service is currently running, stopped, or in an error state with a clear visual status indicator. A green status indicates normal operation, while amber or red states require investigation and possibly a restart. Additional metadata such as the middleware version and last restart timestamp may also be visible on this tab for reference.
Restarting the Middleware
- On the Middleware Status tab, click the Restart button.
Figure 5: Middleware Restart button
The Restart button triggers a graceful shutdown and restart of the Data Trust middleware service. Active user sessions and running scenarios may be interrupted during the restart process, so schedule restarts during low-traffic periods. Download the current logs before restarting if you suspect an ongoing issue, as a restart may overwrite diagnostic information.
Figure 6: Middleware restarting
During the restart process, the status indicator transitions to a pending or restarting state — wait until the process completes before navigating away. The restart typically takes between 15 and 60 seconds depending on server resources; avoid clicking Restart again during this period. Monitor the status indicator until it returns to a green running state before informing users that the platform is available.
Figure 7: Middleware up and running
Once the restart completes, the status indicator confirms the middleware service is healthy and actively accepting connections from the Data Trust frontend. Perform a quick smoke test by logging in and running a simple scenario to verify end-to-end platform functionality after the restart. If the service does not return to a running state within two minutes, review the Logs tab for error messages and contact support if needed.
Logs Tab
The Logs tab provides access to middleware and application logs for diagnostics and audit purposes.
Figure 8: Logs tab — view and download options
The Logs tab lists all available middleware log files and provides View and Download action buttons for each log type. Log files are categorised by type (such as rdlog for runtime events and dtlog for database-tier events) to help you locate relevant diagnostic information quickly. Use the View option for a quick inline review, or Download to save the file for offline analysis or sharing with the support team.
Figure 9: rdlog — view and download
The rdlog file contains detailed runtime events from the middleware layer, including connection attempts, query executions, and error messages. Download this file when raising a support ticket as it is the primary source of diagnostic information for middleware-related issues. The file is updated continuously while the middleware is running, so download it promptly after an issue is observed to capture the relevant entries.
Figure 10: Viewing dtlog inline
Click the View button to open the dtlog directly in the browser for quick inline inspection without downloading the file to your local drive. The inline viewer displays the most recent log entries and allows scrolling and text search to locate specific error messages. For large log files, downloading and opening in a text editor will provide a more comfortable reading experience.
Figure 11: Copying rdlog content to clipboard
The Copy button copies the entire visible log content to the clipboard, enabling a quick paste into a support ticket, email, or chat message. This is useful for sharing a short extract of the log without needing to download and attach the full file. Be mindful that log files may contain internal server names, connection strings, or user data — review the content before sharing externally.
Figure 12: Historic Logs archive
The Historic Logs section lists older middleware log files archived by date, allowing you to investigate issues that occurred in previous sessions or days. Each archived file is named with a timestamp so you can quickly locate the log covering the time window of a reported incident. Download the relevant archived log file and compare it with the current log to identify patterns or recurring errors across sessions.