End-of-Life (EoL)

Convert a Single Server Deployment to a Distributed Database Deployment

Follow these instructions to convert a single server deployment to a distributed database deployment.
This information is only intended for existing, single-server deployments that you want to convert to a distributed database deployment.
To ensure that you do not lose your existing data, the machine on which Cortex XSOAR is currently installed must be converted into the database server.
Your Cortex XSOAR Engines are currently configured to connect to the previous configuration of the Cortex XSOAR platform, which you have now converted to the database server. You need to change the engine configuration so that it connects to the newly installed Cortex XSOAR application server.
  1. Convert the existing deployment.
    1. Stop the server using the
      sudo service demisto stop
      command.
    2. Optional
      If you have docker images that you want to copy, run the following command:
      docker save -o <name>.tar <image>
      Where:
      • name is the name of the output file to which you want to save the docker image
      • image is the current docker image that you want to save
      Copy the tar file you created to the machine on which you will install the application server.
    3. Run the Cortex XSOAR installation package using the
      sudo ./demistoserver-X.sh -- -db-only -db-secret=<your_db_secret> -y
      command.
      Parameter
      Description
      demistoserver-X
      The name of the Cortex XSOAR installer, where X is the version and build number.
      db-only
      The flag indicating that only the database server is installed.
      db-secret
      A 10-character string that you will need to provide for the app server.
      y
      Answers all remaining installation questions with a yes (using default settings) and enables you to continue the installation silently.
      For example:
      sudo ./demistoserver-5.0-45985.sh -- -db-only -db-secret=9876543210 -external-address=2.2.2.2 -y
  2. Install the Cortex XSOAR app server using the
    sudo ./demistoserver-X.sh-- -server-only -db-secret=<your_db_secret> -db-address=<IP or hostname> -external-address=<IP or hostname> -y
    command.
    Parameter
    Description
    demistoserver-X
    The name of the Cortex XSOAR installer, where X is the version and build number.
    server-only
    The flag indicating that only the appserver is installed.
    db-secret
    A 10-character string that you will need to provide for the app server.
    db-address
    The database server's public IP address or hostname. Do not include the http or https prefix.
    external-address
    The app server's public IP address or hostname. Do not include the http or https prefix.
    y
    Answers all remaining installation questions with a yes (using default settings) and enables you to continue the installation silently.
    For example:
    sudo ./demistoserver--5.0-45985.sh-- -server-only -db-secret=9876543210 -db-address=2.2.2.2 -external-address=3.3.3.3 -y
    1. Optional
      If you copied docker images from the database server to the application server, run the following command:
      docker load -i <name>.tar
      Where name is the name of the file to which you saved the docker image(s).
    2. Verify that your docker images were properly loaded using the
      docker images
      command.
  3. Reconnect all Cortex XSOAR engines.
    1. Connect to the machines on which the engine is installed.
    2. Stop the engine service using the
      sudoservice d1 stop
      command.
    3. Navigate to
      /usr/local/demisto/
      and open
      d1.conf
      in a text editor.
    4. Under
      EngineURLs
      and
      AgentURLs
      , replace the current values with the app server’s external IP address or hostname.
    5. Under
      ServerPublic
      , replace the current value with an updated value.
      • In Cortex XSOAR, go to
        Settings
        Integrations
        Engines.
      • Click
        Create New Engine
        .
      • Under
        Installer Type
        , select
        Zip
        .
      • Download the newly created engine package.
      • Open the
        d1.conf
        file located in the engine package in a text editor.
      • Copy the value of the
        ServerPublic
        field and past it in the
        d1.conf
        file located on your engine machine.
    6. Restart the engine using the
      sudo serviced1 start
      command.
  4. Check the status of the engine using the
    sudo systemctl status d1
    command.
    The engine logs are available at
    /var/log/demisto/d1.log

Recommended For You