-
-
Notifications
You must be signed in to change notification settings - Fork 3
HSLynk Deployment information
Eric Jahn edited this page Jul 10, 2020
·
1 revision
Web server (www.hslynk.com)
Apache Instance :ec2-52-37-128-99.us-west-2.compute.amazonaws.com
- Application Server (Tomcat): ec2-52-36-2-74.us-west-2.compute.amazonaws.com
- DB : hmisdb1.ct16elltavnx.us-west-2.rds.amazonaws.com
- Application Server 1: ec2-52-38-189-237.us-west-2.compute.amazonaws.com
- Application Server 2: ec2-52-37-76-153.us-west-2.compute.amazonaws.com
- DB : hmis-multischema-db.ct16elltavnx.us-west-2.rds.amazonaws.com
- Release 1.1 Home - http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Release%201.1/
- Build Release 1.1 (Builds all projects and generate artifacts)
- http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Release%201.1/job/Build-All_HMIS_Projects/
- Deployment - There are specific deployment jobs for each micro services, you can find the jobs under http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Release%201.1/
- Multi schema Home - http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Multi%20Schema/
- Build Multi schema (Builds all projects and generate artifacts)
- http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Multi%20Schema/job/Multi-schema-hmis-build/
- Deployment - There are specific deployment jobs for each micro service and you can find the jobs under Multi schema Home - http://ec2-52-39-104-238.us-west-2.compute.amazonaws.com:9090/view/Multi%20Schema/
https://www.hmislynk.com/hmis-authorization-service /test.html
https://www.hmislynk.com/hmis-authorization-service-v2015/test.html
No, Release 1.1 Production has its own instance (see deployment diagram).
Why do we have to change admin application to point to hmis-authorization-service-v2015 , to test multi schema?
Because www.hmislynk.com/hmis-authorization-service/ should always refer to production and it should be as is until we take multi schema to production. Changes to admin application to point to hmis-authorization-service-v2015 should be temporary and for testing purposes (only). During this testing, we should still have admin application pointing to release 1.1 up and running without any interruption (just like any other services)