...

In this section, the Automated Deployment method for Syndeia Cloud on Linux OS is presented. In the Automated Deployment method, Syndeia admins will run scripts that download and configure Syndeia Cloud and its infrastructure components - Cassandra, JanusGraph, Kafka, and Zookeeper. There is also an option to first download Syndeia Cloud and its infrastructure components, and then run the automated scripts to install. This is useful when working deploying Syndeia in an air-gapped environment. See the Offline Installation Mode (Optional) section below to learn more.

Syndeia admins must use either the Automated Deployment (presented here) or the Semi-Automated Deployment method. See the guidance on the parent page: Deployment Methods.

...

1. Deployment pageread and understanding of:

   • Hardware that meets Requirements

   • Software that meets Version Requirements

2. Supported OS deployed:

   1. Preferred and Recommended - RHEL/CentOS/Alma Linux v7.9+ with Console and/or SSH access enabled

3. Software: Compatibility Layer Components

   1. Linux:

      1. JRE/JDK (automatically installed during Cassandra installation)

4. Software: Infrastructure Components (automatically downloaded OR can use offline mode, see below)

   1. Apache Cassandra

   2. Janusgraph

   3. Apache Zookeeper

   4. Apache Kafka

5. Software: Syndeia Cloud (SC) Components

   1. Syndeia Cloud (SC) media file .ZIPs downloaded : Download .ZIPs from password-protected links provided in the Intercax Helpdesk ticket request where you originally requested received your Syndeia Cloud license. Filenames for each are as follows.

      1. syndeia-cloud-3.5-SP2_cassandra_zookeeper_kafka_setup.zip

      2. syndeia-cloud-3.5-SP2_janusgraph_setup.zip

      3. syndeia-cloud-3.5-SP2.zip

...

1. http://<syndeia_server_FQDN>:9000 should give you:  

   

   To log in as the default administrator and create users, see the User Management section.

2. Once logged in, please verify you see:

   1. a bar graph gets rendered (and not a never-ending spinner followed by an error message) on the Dashboard home page and

   2. the installed version shows correctly under Help > About in the sidebar.

...

How to Manage Services & Check Logs

Services

Linux

Services are all managed using systemd’s systemctl command with a verb, ie: status, start, stop, restart, followed the service name, ie: cassandra, janusgraph, zookeeper, kafka, sc-SC-short-service-name(s) (or sc-* to reference all SC services). For more information run systemctl --help and/or man systemctl .

Example usage for Cassandra, Zookeeper, Kafka, JanusGraph, and Syndeia Cloud follows:

Apache Cassandra

• To check the summary status:

  Code Block
  sudo systemctl status cassandra

• To start the service:

  Code Block
  sudo systemctl start cassandra

• To stop the service:

  Code Block
  sudo systemctl stop cassandra

• To restart the service:

  Code Block
  sudo systemctl restart cassandra

Apache Zookeeper

• To check the summary status:

  Code Block
  sudo systemctl status zookeeper

• To start the service:

  Code Block
  sudo systemctl start zookeeper

• To stop the service:

  Code Block
  sudo systemctl stop zookeeper

• To restart the service:

  Code Block
  sudo systemctl restart zookeeper

Apache Kafka

• To check the summary status:

  Code Block
  sudo systemctl status kafka

• To start the service:

  Code Block
  sudo systemctl start kafka

• To stop the service:

  Code Block
  sudo systemctl stop kafka

• To restart the service:

  Code Block
  sudo systemctl restart kafka

JanusGraph

• To check the summary status:

  Code Block
  sudo systemctl status janusgraph

• To start the service:

  Code Block
  sudo systemctl start janusgraph

• To stop the service:

  Code Block
  sudo systemctl stop janusgraph

• To restart the service:

  Code Block
  sudo systemctl restart janusgraph

Syndeia Cloud

Syndeia Cloud 3.5 is defined by two sets of services:

...

• To stop a service, ex: web-gateway:

  Code Block
  sudo systemctl stop sc-web-gateway

• To restart a service, ex: web-gateway:

  Code Block
  sudo systemctl restart sc-web-gateway

...

Logs & Monitoring

...

Logs on Linux can be viewed using the journalctl command, ex: sudo journalctl -xeu service-name, ie: cassandra, janusgraph, zookeeper, kafka, sc-SC-short-service-name(s)

...

Raw log files are located in the following locations:

Apache Cassandra

/var/log/cassandra/system.log

Apache Zookeeper

Zookeeper creates a log file of the form zookeeper-accountName -server-serverFQDN .log

...

/opt/zookeeper-current/logs/zookeeper.log

Apache Kafka

Apache Kafka generates several files with the extension .log in its logs folder

...

/opt/kafka-current/logs/server.log

JanusGraph

/opt/janusgraph-current/logs/gremlin-server.log

Syndeia Cloud

For single-node deployments, one can use the common logs directory with symlinks to every service’s logs folder (this is useful is say one wishes to quickly archive all logs to submit for troubleshooting)

...