Central Deployment Process

Central Deployment Process

  1. Run SQL scripts in http://sourcecontrol.fullcount.net/repos/internal/trunk/at-fullcount-model/src/main/resources/sql/nextDeploy
  2. Pause TeamCity test for fullcount-uptime-production-overnight.
  3. Download release war file from archiva for all applications.
    1.     Touchscreen - at-fullcount-touchscreen
    2.     Resident Portal / Resident Portal Consolidated - at-selfservice-portal
    3.     Back Office - backoffice
    4.     Client Access - fullcount-client-access
    5.     Model API - model-api
    6.     Authorization - authorization

  4. Copy war file over to /home/<your username>/deployment_wars for staging on the appropriate server. Do this step prior to deployment to save time waiting for files to upload.
  5. Run each instance separately in accordance with our current maintenance policies.
  6. Log into tomcatprod01 via ssh with your account (i.e. not "root"!).
  7. Move war file from staging directory to tomcat instance war directory.

    1.     Touchscreen - /srv/tomcat/instances/POSWebApplication/wars/POSWebApplication.war
    2.     Back Office - /srv/tomcat/instances/backoffice/wars/backoffice.war
    3.     Resident Portal - /srv/tomcat/instances/ResidentSelfServicePortal/wars/ResidentSelfServicePortal.war
    4.     Resident Portal Consolidated - /srv/tomcat/instances/ResidentSelfServicePortalConsolidated/wars/ResidentSelfServicePortalConsolidated.war
    5.     Model API - /srv/tomcat/instances/model-api/wars/model-api.war
    6.     Authorization - /srv/tomcat/instances/authorization/wars/authorization.war

  8. Restart the tomcat instance.
    1.     Touchscreen
      # sudo /sbin/service POSWebApplication restart
    2.     Back Office
        # sudo /sbin/service backoffice restart
    3.     Resident Portal
              # sudo /sbin/service ResidentSelfServicePortal restart
    4.     Resident Portal Consolidated
              # sudo /sbin/service ResidentSelfServicePortalConsolidated restart
    5.     Model API
              # sudo /sbin/service model-api restart
    6.     Authorization
              # sudo /sbin/service authorization restart
  9. Log into tomcatintegrationprod01 via ssh with your account (i.e. not "root"!).
  10. Move war file from staging directory to tomcat instance war directory.
    1.     Client Access - /srv/tomcat/instances/client-access/wars/client-access.war

  11. Restart the tomcat instance.
    1.     Client Access
              # sudo /sbin/service client-access restart
  12. Confirm application has redeployed.
  13. Activate TeamCity test for fullcount-uptime-production-overnight.


    • Related Articles

    • Post Central Deployment Tasks

      Post Central Deployment Tasks Objectives Complete necessary post-deployment tasks Prerequisites Access to Redmine Access to production database Access to fcadmin Access to deployment test server Instructions Send release docs Release docs are located ...

    • Remote Deployment Process - Java

      Deployment Process Determine if a valid argument has been passed in Only continue if downloadOnly, postDownload, fullDeployment, handleSuccess, checkHash, verifyApplications passed through. Lock file to stop deployment from running more than once ...

    • Run Remote Deployment Process - Java

      Remote Server Configuration This has already been completed for all existing remote servers. Java 1.8 installed Tomcat located at /srv/tomcat XE database installed and running with fc_obj_owner user Directory /home/deployment exists Database backup ...

    • Overview of Deployment Process for Remote Servers

      Overview of Deployment Process for Remote Servers Introduction The process for updating the Touchscreen and Back Office applications is known as the deployment process. The deployment process is only used for updating applications and databases on ...

    • Pre Central Deployment Tasks

      Pre Central Deployment Tasks Objectives Complete necessary pre-deployment tasks Prerequisites Access to Redmine Access to production application server Access to Subversion Access to TeamCity Instructions Update Semantic Version Information See ...