AC Hosting Environment

AC Hosting Environment Documentation
  • 1 Release Notes
    • 1.1 End-Of-Life (EOL) Notice
    • 1.2 Support Policy
    • 1.3 Differences to CentOS
  • 2 Deployment
    • 2.1 Prerequisites
    • 2.2 Preparing to Install
    • 2.3 Installation
    • 2.4 Post Installation Steps
  • 3 AC Tools
    • 3.1 AC Configure Syslog
      • 3.1.1 Introduction
      • 3.1.2 Un/Installation
      • 3.1.3 Usage
    • 3.2 AC Firewall
      • 3.2.1 Introduction
      • 3.2.2 Un/Installation
      • 3.2.3 Usage
    • 3.3 AC Integrity
      • 3.3.1 Introduction
      • 3.3.2 Un/Installation
      • 3.3.3 Usage
      • 3.3.4 Integration Tips
    • 3.4 Make Bash Installer
      • 3.4.1 Introduction
      • 3.4.2 Un/Installation
      • 3.4.3 Usage
    • 3.5 AC X509 Authority
      • 3.5.1 Introduction
      • 3.5.2 Un/Installation
      • 3.5.3 Command Reference
      • 3.5.4 Certificates For Beginners
      • 3.5.5 CA Management
      • 3.5.6 Server, Client, and User Certificate Management
      • 3.5.7 Reporting Commands
      • 3.5.8 Troubleshooting

3.3.4 Integration Tips

September 13th, 2025

Although AC Integrity can be managed manually by a system administrator, this is not the intended purpose. Generally, it is assumed that applications created specifically to run on ACHE will provide some configuration that has been tailor made by the application developer and then modified by a system administrator only if absolutely necessary.

Integration usually entails just six steps.

  1. Stop the AC Integrity service.
  2. Install application.
  3. As part of any application installation process, place an application specific class file in /etc/ac_integrity/classes/.
  4. Append application specific sensitive files to /etc/ac_integrity/lists.conf which should all point to the newly added class.
  5. Run an AC Integrity database update to record the state of the new application files.
  6. Start the AC Integrity service.

For the best user experience, it is recommended that all of these steps be automated by an application installer program.

The AC Integrity service must be restarted after making changes to a class file, such as providing a new MAILTO value.

Deintegration

Uninstalling an application and deintegrating it from AC Integrity is very similar to the installation steps.

  1. Stop the AC Integrity service.
  2. Uninstall application.
  3. As part of any application uninstallation process, delete any application specific class file in /etc/ac_integrity/classes/.
  4. Parse the /etc/ac_integrity/lists.conf file to remove all lines that contain your class in column 2.
  5. Run an AC Integrity database update to record the state of the new application files.
  6. Start the AC Integrity service.
previous: Usage next: Introduction