Versions Compared

Old Version 11

changes.mady.by.user Brian Miller

Saved on

compared with

New Version Current

changes.mady.by.user Brian Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Installing, Configuring, and Starting Syndeia Cloud: step 1: mention cd-ing into bin instead

Table of Contents
outlinetrue
stylenone

...

Pre-requisites:

1.  Ensure you have the syndeia-cloud-3.5.zip (or latest service pack) downloaded to your home directory (or home directory's Downloads folder) from the download/license instructions sent out by our team.  

(info)  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.  

(info)  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). 

(info) 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.  

SC service

JMX port #

sc-auth

31101

sc-store

31102

sc-graph

31103

sc-web-gateway

31100

sc-aras

31112

sc-artifactory

31116

sc-bitbucket

31104

sc-collaborator31118

sc-confluence

31105

sc-doors

31115

sc-github

31106

sc-gitlab

31107

sc-jama

31114

sc-jira

31108

sc-restful31119

sc-sysmlv2

31112

sc-testrail

31113

sc-twcloud

31109

sc-volta31117

sc-wc

31110

...

Downloading & Extracting Syndeia Cloud:

1. Launch a Cygwin Terminal, it should start in your home dir. 

(warning) CAUTION:  To avoid any issues on Windows, it is recommended you do NOT use a path that contains any spaces in any of the directory (or file) names.  

2. Make a download directory for the build & cd into it, ex:  new_build_version=3.5 ; export new_build_version

...

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

Panel
borderColor#eae6ff
bgColor#eae6ff
titleColorblack
borderWidth1
borderStylesolid

  This will: 

- install Syndeia Cloud 3.5 (or latest service pack) 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.X processes,
- update/create a "current" symlink to the installed version,
- stop the Kafka service (on single-node deployments only),
- archive any old Kafka logs (on single-node deployments only),
- drop any old keyspaces & generate the new schema in the DB (Cassandra),
- start Kafka service (on single-node deployments only),
- start Janusgraph service, if needed (on single-node deployments only),
- initialize the Janusgraph configuration (on single-node deployments only),
- install NT SCM services files for syndeia-cloud microservices using Apache Commons wrapper daemon
- start all Syndeia Cloud microservices,
- create the superuser account, and
- create some sample test data.  

1. In the directory you downloaded and extracted the main .ZIP,  run cd into the bin directory and run the install script, ie:  ./bin/syndeia-cloud-3.5_install_windows.bash -SC_v ${new_build_version}. 

...

2.2  Once logged in, please verify you see a bar graph get rendered (and not a never-ending spinner followed by an error message) on the Dashboard home page and the version is shown correctly under Help > About in the sidebar..   



Page break macro