Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Step-by-step workaround for <environment>_GEO servers (e.g. SF_QA_GEO)

Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, DR_PROD

Text for * * GEO TLS 1.2 workaround page.txt

Workarounds for the 2018 TLS 1.2 Compatibility Issue

https://sfgovdt.jira.com/wiki/spaces/MAD/pages/1036845057/

Step-by-step workaround for <environment>_GEO servers (e.g. SF_QA_GEO)
Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, DR_PROD

  1. Manually download required files to a computer that has FTP access to the EAS servers

A. Download Repositories

There is one EAS repository to download.

Info:
The names of the repository folder is important. It is recommended that the repository be download by using a Web browser in the downloads section of the repository. It is important to accept the default name for the downloaded folder.

Note: Tags Tab
The Tags tab will let you select which changeset, and format, that you want to download.
https://bitbucket.org/sfgovdt/sfeas_config/downloads/?tab=tags
The downloaded compressed files will be named something like this:
sfgovdt-sfeas_config-ff939b913451.zip
Uncompress the zip file.
This will result in three folders, such as this:
sfgovdt-sfeas_config-ff939b913451

Again, the folder name is important, so do not change it.

EXAMPLE OF DOWNLOADED REPOSITORY FOLDERS (COMPRESSED AND UNCOMPRESSED) IN WINDOWS:
Example of downloaded repository names in Windows
TODO: Insert image

B. Download Workaround Deployment Scripts

Download the latest version of these 4 files.

From the /eas/geoserver/ source folder at https://bitbucket.org/sfgovdt/eas/src/default/geoserver/

  1. deploy_geoserver_init.sh

  2. deploy_geoserver.py

  3. deploy_geoserver_env.sh

From the config/web/settings_env/live/ source folder at https://bitbucket.org/sfgovdt/sfeas_config/src/default/web/settings_env/live/

  1. environments.py

  2. FTP the 1 folder and 4 files to the /var/tmp folder of the server to be deployed

EXAMPLE OF UPLOADING THE FILES FROM WINDOWS TO THE /VAR/TMP DIRECTORY OF THE TARGET SERVER USING FTP TOOL FILEZILLA:

TODO: Insert image

See also https://filezilla-project.org/
See also PuTTY and SSH

  1. Connect to relevant server and browse to /var/tmp
    cd /var/tmp

  2. Change permissions of shell scripts
    sudo chmod u+x *.sh

  3. Move shell scripts to their correct locations
    TODO

Leave the 1 repository folder in the directory /var/tmp/

  1. Run the deployment script as sudo
    TODO

  2. Confirm deployment with tests
    The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.

  • No labels