Synapse Deployment Instructions

Note that all Synapse resources should be created in US East, as Beanstalk is not yet available everywhere.

Crowd (skip if using existing crowd deployment)

If necessary, the instructions are here:

[http://sagebionetworks.jira.com/wiki/display/PLFM/Setting+Up+Production+Crowd|http://sagebionetworks.jira.com/wiki/display/PLFM/Setting+Up+Production+Crowd]

h4. Restarting Crowd

If the server goes down:

To check if Crowd is up, in web browser go to
[https://crowd.sagebase.org:8443/crowd|https://crowd.sagebase.org:8443/crowd]
You should see Crowd log-in page. If not then ssh in to crowd.sagebase.org as ec2-user, using the standard key for 'platform' owned ec2 instances, PlatformKeyPairEast

At the unix prompt:
ps -a

Should show one java process, if not
cd /usr/local/atlassian-crowd-2.2.7/

./start_crowd.sh

Now verify that the log-in page appears in your web browser.

The above instructions apply to 'crowd-dev.sagebase.org' as well as 'crowd.sagebase.org'.

Get the built artifacts from Artifactory

You should not be deploying anything you built yourself on your local machine. Only deploy builds build artifacts generated by Bamboo and stored in Artifactory. See Branching and Tagging for information about managing the build, branch, and tag process. You will need 3 .war files out of artifactory for a deployment: services-repository-<version>.war, services-authentication-<version>.war, and portal-<version>.war. Each must go into its own Beanstalk environment.

Create Beanstalk Environments (Skip this section if using existing Environments.)

...

The configuration of all environments for all Synapse components should be the same, with the exception that we leave port 80 on the web app load balancer open and closed everywhere else.

Configure

...

Server

Click on 'edit configuration' in the Beanstalk UI, start on 'Server' tab:

EC2 Instance Type=t1.micro

EC2 Security Groups=elasticbeanstalk-default

Existing Key Pair=PlatformKeyPairEast

Monitoring Interval=5 minute

Custom AMI ID=ami-524db23b

Configure Load Balancer

Click on 'Load Balancer' tab

For 'HTTP Listener port' choose 'OFF' for the repo and auth services, choose '80' for the portal.

...

Set Email Address to 'platform@sagebase.org'

Configure Container

Click on 'container.'

In the JVM Command Line

...

Options For a production deployment:

-Dorg.sagebionetworks.stack=alpha

...

This is the minimum information needed to bootstrap our system with the information needed to load a configuration via a .properties file. Here, the actual .properties file mushould be loaded in .S3

where <<encryption key>> is found on our unix system in

work/platform/PasswordsAndCredentials/platformPropertyEncryptionKey.txt

Set up Crowd