Single Node Setup Instructions:

Pre-requisites:

1. Ensure you have the syndeia-cloud-3.3.${build_number}_setup.zip downloaded to your home directory (or home directory's Downloads folder) from the download/license instructions sent out by our team.

Note: the .ZIP will pre-create a separate folder for its contents when extracted so there is no need to pre-create a separate folder for it.

2. Review Syndeia Cloud's recommendations, ie: (Open|Oracle)JDK/JRE, memory, FS selection, params, etc. in Deployment.

Note: Syndeia Cloud can be deployed on a different machine VS Cassandra but these steps will focus on a single-node deployment.

3. If using a firewall, ensure the following port(s) are accessible (consult your local network admin if required): TCP port 9000 (HTTP), 9443 (HTTPS).

Note: If required by your IT department, perform any other standard configuration, server hardening (ie: enabling & configuring local firewall, etc.)

Downloading & Extracting Syndeia Cloud:

1. SSH to your designated Syndeia Cloud server

2. Set an environment var for the build version, ex: new_build_version=3.3.2021-01-27.SP1 ; export new_build_version

Note: If your version you have is older than the one shown above, please reach out to us to obtain the latest Service Pack.

3. Create a new user and group named syndeia-cloud, ie: sudo useradd --system --user-group syndeia-cloud

4. Run umask to ensure your user umask is set to 0002 and root's umask is set to 0022. If not, set it, ie: umask 0002, and then su && umask 0022

5. cd into the directory where you download the Syndeia Cloud .ZIP.

6. In the download dir, unzip the main package, ie: unzip syndeia-cloud-${new_build_version}.zip

Note: if you don't have unzip installed, you may need to first install it via yum install unzip

Syndeia Cloud Database User Setup:

7. In a new terminal session, launch a CQLSH session (see Appendix C3.3 for instructions) & authenticate (see Appendix C3.1 on how to validate/configure this) with a superuser account (or have the Cassandra administrator authenticate) to do the following for you or your team:

Note1: If you ran the setup script specified in the JanusGraph setup page, this account should already be created and you can skip this section or just validate via LIST ROLES below.

Note2: If you have a user account you can check by running the CQL command LIST ROLES to list all roles to confirm your account has superuser privilege

$./cqlsh -u cassandra cassandra-syndeia-cloud.mycompany.com
Password:
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.0.15 | CQL spec 3.4.0 | Native protocol v4]
Use HELP for help.
cassandra@cqlsh> LIST ROLES;

 role             | super | login | options
------------------+-------+-------+---------
        cassandra |  True |  True |        {}

(1 rows)
cassandra@cqlsh>

8. Create a new syndeia_admin role and provide it with a new strong password, ie:

CREATE ROLE syndeia_admin WITH LOGIN = true AND SUPERUSER = true AND PASSWORD = '<syndeia_admin_strong_password>';

where <syndeia_admin_strong_password> is a strong password, ex: ‘M1Str9ngPass80rd' ( Avoid any of the following special characters: \?*[]+#&.{}$ )

Then, run the following command to list all roles and confirm syndeia_admin has login access (if you get an error from the CREATE command or do not see syndeia_admin listed in the LIST ROLES output, see Appendix C3.4)

LIST ROLES;

cassandra@cqlsh> LIST ROLES;

 role          | super | login | options
---------------+-------+-------+---------
     cassandra |  True |  True |        {}
 syndeia_admin |  True |  True |        {}

Installing, Configuring, and Starting Syndeia Cloud:

9. In the directory you downloaded and extracted the main .zip, run the install script ( DO NOT RUN WITH "sudo"! Doing so will incorrectly create all files with root ownership, requiring one to start over. If you are getting an error running without sudo, please review the previous steps) , ie: ./bin/syndeia-cloud-3.3_install.bash --SC_v ${new_build_version}. This will:

- install Syndeia Cloud 3.3 to /opt/icx/syndeia-cloud-${new_build_version} ,
- make syndeia-cloud:syndeia-cloud the owner,
- configure the application.conf files if necessary,
- generate a concatenated schema file,
- stop any existing Syndeia Cloud 3.3 processes,
- update/create a "current" symlink to the installed version,
- stop the Janusgraph service,
- stop the Kafka service,
- archive any old Kafka logs,
- drop any old keyspaces & generate the new schema in the DB (Cassandra),
- start Kafka service,
- start Janusgraph service,
- initialize the Janusgraph configuration,
- install a tmpfiles.d .conf file for syndeia-cloud,
- install systemd .target and .service files for syndeia-cloud microservices
- start all Syndeia Cloud microservices,
- create the superuser account, and
- create some sample test data.

Note: you may be prompted for sudo authentication when installing to /opt/... you will also be prompted for your syndeia_admin password set previously

IMPORTANT: If you get an error at the end with the superuser or setup devops actions failing (or the superuser action appearing to succeed but not allowing a user to login to the web dashboard), please run them manually, ie:

export SC_HOME=/opt/icx/syndeia-cloud-current ;
sudo -u syndeia-cloud ${SC_HOME}/devops-1.0-SNAPSHOT/bin/devops -Duser.dir=${SC_HOME} -XX:+UnlockDiagnosticVMOptions -XX:LogFile=${SC_HOME}/logs/devops_JVM.log -DXloggc:devops_JVM_gc.log -Dsyndeia.client.action=superuser ;
sudo -u syndeia-cloud ${SC_HOME}/devops-1.0-SNAPSHOT/bin/devops -Duser.dir=${SC_HOME} -XX:+UnlockDiagnosticVMOptions -XX:LogFile=${SC_HOME}/logs/devops_JVM.log -DXloggc:devops_JVM_gc.log -Dsyndeia.client.action=setup -Dsyndeia.client.username=super.user -Dsyndeia.client.password=syn45ia ;

If you have an environment in which these actions do not succeed, and you have SC v3.3 SP1 or >, you can pass the --skip_devops (or -s) parameter to the end of the script to skip the automatic running of the devops actions at the end, ie: ./bin/syndeia-cloud-3.3_install.bash --skip_devops

10. Validate correct operation and create/update an archive image to use as a new base image if the node needs to be rebuilt or if you wish to create a cluster.

Before making the image you may wish to first stop and optionally disable Syndeia Cloud's services temporarily to prevent auto-start on boot, ie: sudo systemctl disable sc.target

Managing Syndeia Cloud:

11. To check the status of Syndeia Cloud services, use systemctl status <service_name>; where <service_name> = one of sc-auth|sc-store|sc-graph|sc-web-gateway

12. To stop/start the Syndeia Cloud services, use sudo systemctl <action> <service_name>; where <action> = one of start|stop, and <service_name> = one of sc-auth|sc-store|sc-graph|sc-web-gateway

Note: If you wish to ensure the services run on startup, run sudo systemctl enable <service_name>; where <service_name> = one of sc-auth|sc-store|sc-graph|sc-web-gateway. For more information on installing the .service files manually and configuring them to start after Cassandra, see Setting up Services to Start on Boot.

13. To tail or view the logs for any Syndeia Cloud service, use either sudo journalctl -feu sc-<service_name> or less /opt/icx/syndeia-cloud-${new_build_version}/logs/<service_name>.log; where <service_name> = one of auth|store|graph|web-gateway.

Validating Syndeia Cloud Installation & Configuration:

14. Verify if syndeia_admin has all the permissions on the syndeia keyspace, ie:

LIST ALL PERMISSIONS OF syndeia_admin;

15. On the server and/or your local machine, launch a web browser & check the following to validate that the application is correctly running:

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

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

.....Page break.....

Syndeia 3.3

Syndeia Cloud Installation Instructions for RHEL/CentOS7