Installing Your CodeLogic Server on RHEL

The CodeLogic Server is installed from the CodeLogic repository using the RedHat package manager tool (RPM).

You must ensure that your system meets the specifications outlined in the CodeLogic Installation Requirements.

NOTE

Internet access is only needed for installation and upgrading. Once installed, the CodeLogic Server is the package repository for the Linux and Windows agents.

The sample output is for reference only, it may differ on your system.

An ellipsis (…) indicates omitted output.

Before You Begin  If you do not have internet access, see Commands for the command to list the dependencies for the CodeLogic Server. You will need to have the listed dependencies installed before installing CodeLogic.

  1. Install

    Install and Configure the Docker Engine

    NOTE

    If podman, podman-docker or buildah are installed, they must be removed.

    Use dnf erase podman podmandocker buildah to remove them now. Or use dnf install --allowerasing codelogic to allow dnf to remove them when CodeLogic is installed.

     

    Install the Docker Engine, version 20.10 or later, by following the instructions at: https://docs.docker.com/engine/install/centos/

    Although sample output is included, please refer to the instructions at Docker Docs.

    Configure the Docker engine to start on boot by following the instructions at:
    https://docs.docker.com/engine/install/linux-postinstall/#configure-docker-to-start-on-boot.

    Install Docker Compose, version 1.29.2 or later, by following the instructions at: https://docs.docker.com/compose/install/#install-compose-on-linux-systems.

  2. Add the CodeLogic Repository to the Package Database

    Command

    Copy
    sudo dnf config-manager --add-repo http://repo.codelogic.com/redhat/codelogic-server.repo
  3. Install the CodeLogic Server

    Command

    Copy
    sudo dnf install --assumeyes codelogic
  4. Run the Configure Script

    1. Run the following command:

      Command

      Copy
      sudo /opt/codelogic/pre_start_codelogic.sh

      The script will confirm the protocol (http or https), hostname or IP address, and create a self-signed certificate for testing purposes.

    2. If a signed certificate is available now, answer N to the Allow HTTP? question.

      NOTE

      A self-signed certificate will be created regardless of the answer. The answer to this question determines the protocol (http or https) used for the software repository.

      For example, if http://myserver.com is entered, the package repositories will use http. If https://myserver.com is entered, the package repositories will use https.

      See Install a signed TLS certificate on the server below for more information.

    3. Create a CodeLogic Administrator Account with an email address and password.

      NOTE

      The password must be between 8 and 256 characters in length (numbers, symbols, and mixed-case letters allowed).

    4. When prompted, Would you like to install demo data? [Y/N] enter Y or N.

      Demo data is provided as a resource to familiarize yourself with your CodeLogic Server and its features. For more information, see Demo Data.

      NOTE

      Demo data is only available on new installs, not upgrades.

      If CodeLogic detects an existing codelogic_neo4j_data data volume, you will not be able to overwrite the existing volume with the demo data.

  5. Install a signed TLS certificate on the server

    The signed TLS certificate and key file names must be named codelogic.crt and codelogic.key.

    Copy the signed TLS certificate and key to /opt/codelogic/certs/ and restart the CodeLogic Server.

    IMPORTANT

    The certificate must be signed by a certificate authority. Although a self-signed certificate allows access to the GUI, the agents will not accept a self-signed certificate. For more information, see Using Internally Generated Certificates.

    The self-signed certificate created by pre_start_codelogic.sh may be used for product evaluation.

    Copy
    sudo cp -p /path/to/signed/certificate.crt /opt/codelogic/certs/codelogic.crt
    sudo cp -p /path/to/signed/certificate.key /opt/codelogic/certs/codelogic.key
    sudo systemctl restart codelogic
  6. Verify that the CodeLogic Server is Running

    The server is controlled via standard Linux facilities. For example, to view the status, use the systemctl command. Root permission is not needed to view the status.

    Command

    Copy
    systemctl status codelogic
  7. Log in to the Server

    Log in to the CodeLogic Server with the CodeLogic Administrator Account you created above.

    If a signed TLS certificate has been copied to /opt/codelogic/certs, use https to log in the server using the default credentials.

    If “y” was the response to the “Allow HTTP?” question, use http.

    Copy
    URL (https): https://your_server/
    URL (http):  http://your_server/
    Email:       <email address>
    Password:    <password>
    NOTE

    You MUST replace your_server with the actual address of your CodeLogic Server.

    NOTE

    It may take 2-3 minutes after restarting CodeLogic before login is available.