Before making a deployment, download the current jar files in case we need to go back.

 

There are two parts to a deployment:

  1. Code
  2. Database Changes

NOTE: Database changes should be done first.

Database:

  1. In Layershift copy the database changes defined in the <release>/changes.sql from BitBucket to MountPoints/mt/0_sql/massLoads/changes.sql, make sure to remove any blank or comment lines
  2. In Layershift copy the database changes defined in the <release>/changes.sql from BitBucket to MountPoints/mt/0_sql/newDBStrelv650.sql. This is used by the New Site creation feature of the Admin Portal. Make sure there are no blank lines at the end of the file.
  3. Open browser, go to Admin Portal and login. If Live, select the WEB button ( top right ), Select Utilities from the sidebar, this opens a screen to allow all databases to be updated.
  4. From the Product Load dropdown, select ‘changes.sql’ and the select ‘Load’. This will update all databases, check the log output.

 

Code:

This is the easy bit using Layershift:

  1. Using the Config feature in Layershift for the appropriate environment, Upload 613fpro.jar and Strel1.jar
  2. In the WEB-INF/classes directory, rename directory ‘com’ to ‘com<date>’, this is to prevent these files being found in the classpath before the classes being deployed.
  3. In the webaps/strelitzia rename any jsp files to stop these being found first before those being deployed.
  4. Restart the server.