Skip to main content
Version: 7.8

Directory Structure

Navigating the installation directory of Actions Pro might be necessary when looking for log files, scripts, or commands.

The default installation path is /opt/resolve, but it might be different on your system. Under it, you will find the following directories:

  • bin Contains scripts for:
    • Starting, stopping, restarting, and checking the status of Actions Pro core components.
    • Pre- and post-installation setup.
    • Applying configuration changes (config.sh) made in blueprint.properties. Also contains a symbolic link to blueprint.properties (the main configuration file).
  • elasticsearch
    • config Contains elasticsearch.yml. Do not edit this file unless instructed by your Resolve representative.
    • logs Contains the Elasticsearch logs. The current log file is <Cluster Name>.log. It is rotated daily under names in the <Cluster Name>-<date>.log format.
  • rscontrol, rsmgmt, rsremote, or rssync
    • config Contains config.xml for the respective core component. It stores the applied changes from blueprint.properties.
      • log Contains the core component's log file with a naming convention of <core-component-name>.log (such as rscontrol.log).
  • tomcat
    • logs
      • catalina.out Tomcat Logs like:
        • Start/stop messages
        • Error code 500 (Internal Server error) logs
        • Thread dumps generated by stop.sh -k rsview command
    • conf
      • server.xml Tomcat configuration file responsible for things like port usage, listeners, and ciphers. Do not edit this file unless instructed by your Resolve representative.
  • rabbitmq
    • log/rabbit@<IP address>.log General information and error log for the message queue.
    • config/rabbitmq.config Message queue config file. Do not edit this file unless instructed by your Resolve representative.
    • linux64/rabbitmq/sbin/rabbitmqctl Command-line message queue manager. This file is the starting point to run commands if UI based queries are available.