Versions Compared

Old Version 2

changes.mady.by.user Dan King

Saved on

compared with

New Version Current

changes.mady.by.user Dan King

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Step-by-step workaround for

...

* * 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

Contents:

Table of Contents

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

1.A. Download

...

Repository

There is one EAS repository to download.Info:

Note

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.

...

Info

The Tags tab will let you select which changeset, and format, that you want to download.

1.A.1. Visit the download page of the repository

1.A.2. Download the .zip file from the most recent branch

The downloaded compressed files will be named something like this (Mercurial):
sfgovdt-sfeas_config-ff939b913451.zip

or this (Git):

sfgovdt-easconfigxsf-fcf152a4111f.zip

1.A.3. Uncompress the zip file.

This will result in three folders, such as this:
sfgovdt-sfeas_config-ff939b913451Uncompress the zip file.

Note

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

1.B. Download Workaround Deployment Scripts

1.B.1 Download the latest version of these 4 files.

From Download from the /eas/geoserver/ source folder at

Tip: Navigate to the workaround deployment script file in the repository with a browser on the target machine, invoke the "... → Open raw" menu command, and then save the file in the directory that is specified below.

1. deploy_geoserver_init.sh

2. deploy_geoserver.py

3. deploy_geoserver_env.sh

From the config/web/settings_env/live/ source folder at

4. environments.py

Part 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 imageExample of uploaded files into the /var/tmp directory of the target server using FTP tool FileZilla:

...

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

Part 3. Connect to server, configure and deploy

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

    Code Block
    cd /var/tmp

  2. Change permissions of shell scripts

    Code Block
    sudo chmod u+x *.sh

  3. Move shell scripts to their correct locations
    TODO

    Code Block
    languagebash
    sudo cp deploy_geoserver_init.sh /usr/share/apache-tomcat-7.0.32/webapps/
sudo cp deploy_geoserver.py /usr/share/apache-tomcat-7.0.32/webapps/
sudo cp deploy_geoserver_env.sh /usr/share/apache-tomcat-7.0.32/webapps/
sudo cp environments.py /usr/share/apache-tomcat-7.0.32/webapps/

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

  1. Run the deployment script as sudo
    TODO

    Code Block
    cd /usr/share/apache-tomcat-7.0.32/webapps/
sudo ./deploy_geoserver_init.sh

Part 4. Confirm deployment with tests

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