Single Node Setup Instructions:

...

Pre-requisites:

1.  Ensure you have the syndeia-cloud-3.6-SP1.zip (or the latest service pack) 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. Decide if you wish to configure Java JRE/JDK for JMX monitoring or not (for example, if you wish to monitor via Grafana). 

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

 If you will be using JMX monitoring, the following additional ports will also need to be accessible (NOT necessarily externally) from where you will run monitoring (green = new since SC 3.5!6).  

...

2. Set an environment var for the build version, ex:  new_build_version=3.6 6-SP1 ; export new_build_version

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

...

sudo su # you will be prompted for a password
umask # IF this *isn't* "0022", THEN set it in /root/.profile (at least for the duration of the SC deployment)
echo "umask 0022" > /root/.profile

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

...

In this step we will run the automated SC setup script.  

...

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

...

...

1. 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|sc-aras|sc-artifactory|sc-bitbucket|sc-collaborator|sc-confluence|sc-doors|sc-dscr|sc-dse3|sc-dt|sc-github|sc-gitlab|sc-jama|sc-jira|sc-restful|sc-sysmlv2|sc-tc|sc-testrail|sc-twcloud|sc-volta|sc-wc


2. 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|sc-aras|sc-artifactory|sc-bitbucket|sc-collaborator|sc-confluence|sc-doors|sc-dscr|sc-dse3|sc-dt|sc-github|sc-gitlab|sc-jama|sc-jira|sc-restful|sc-sysmlv2|sc-tc|sc-testrail|sc-twcloud|sc-volta|sc-wc


...

3. 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_impl>.log; where <service_name> = one of auth|store|graph|web-gateway|aras|artifactory|bitbucket|collaborator|confluence|doors|dscr|dse3|dt|github|gitlab|jama|jira|restful|sysmlv2|testrail|twcloud|volta|wcc 

where <service_name_impl> = one of auth-impl|store-impl|graph-impl|web-gateway|aras-impl|artifactory-impl|bitbucket-impl|collaborator-impl|confluence-impl|doors-impl|dscr-impl|dse3-impl|digital-thread-impl|github-impl|gitlab-impl|jama-impl|jira-impl|restful-impl|sysmlv2-impl|teamcenter-impl|testrail-impl|teamworkcloud-impl|volta-impl|windchill-impl 

...

Validating Syndeia Cloud Installation & Configuration:

...