All patches are provided by QAD editor mainly to fix issues, sometimes to provide new minor functionalities.
This upgrade requires meticulous TU and NRT phases before any move to prod.
In the meantime it's crucial to keep one non-prod environment (DEV) in the same version as production. It may help to analyze and fix issues that could occur in production.
PREREQUISITES
PATCHING TEST
Step 1 : Retrieve the patch files from QAD platform
> Open Internet Explorer
> Log on to ftp://ftp.dys.com/ (account : Solvay)
> Get a local copy of the last version of those two files located into Packages directory
- DSCP_2018.xxxx_Dys.Win.exe
- DSCP_2018.xxxx_Dys.Web.zip
Step 2 : Copy patch files to servers
> Copy the *_Dys.Win.exe file into D:\DynaSys\Packages directory of backend and frontend servers
> Copy the *_Dys.Web.exe file into D:\DynaSys\Packages directory of the frontend server only
Now it's time to upgrade DSCP applications !
A good practice is to deploy patches at first in TEST. Keep DEV and PROD in the same version. As soon as all checks have been executed succesfully, the patch can be deployed in PROD, then in DEV.
Consequently the following steps 3 to 7 must be performed for all DSCP applications installed on the target environment (backend + frontend servers).
Step 3 : Check active user connections
> Open Dscp application and check no one is connected
> Stop the service and force startup type to Disabled
Step 4 : Install the non-Web part (Win.exe file)
> Copy DSCP_2018.xxxx_Dys.Win.exe from D:\DynaSys\Packages to D:\DynaSys\<MODULE>\Dscp\Bin directory
> Remove the old DSCP_2018.xxxx_Dys.Win.exe file from D:\DynaSys\<MODULE>\Dscp\Bin directory
> Right-click DSCP_2018.xxxx_Dys.Win.exe file and execute it as an administrator
User connections may block the installation process, so an exclusive access is mandatory
> Open the Task manager and kill each existing dscp.exe process
The execution of DSCP_2018.xxxx_Dys.Win.exe may fail despite the fact that no dscp process is running
> Rename dscpsrv.exe file and re-execute DSCP_2018.xxxx_Dys.Win.exe file
Step 5 : Install the Web part (web.zip file)
> Delete the following files from D:\DynaSys\<MODULE>\WebPortal2018\WebPortal_Deploy directory
> Copy the new patch file DSCP_2018.xxxx_Dys_Web.zip from D:\DynaSys\Packages into D:\DynaSys\<MODULE>\WebPortal2018\WebPortal_Deploy directory
> Unzip DSCP_2018.xxxx_Dys_Web.zip file in order to extract all files into D:\DynaSys\<MODULE>\WebPortal2018\WebPortal_Deploy directory
> Right-click start.exe file and execute it as an administrator
> Starting from this point, two Administrator windows may appear with successive questions or key press to continue :
Insure that no red lines area displayed during the simulation
> In the end, type "Exit" to close the Web installation
Step 6 : Finalize the installation
> Force the startup type of service to Automatic
> Restart the service
If this message error appears, the database version and the server version must be aligned. Apply the following steps :
> Drag D:\DynaSys\<MODULE>\Dscp\Bin\dscpsrv.ini file and drop it on D:\DynaSys\<MODULE>\Dscp\Bin\dscpsrv.exe file
> This windows may appear
> Click OK
> Click YES
> DO NOT CLICK ON EXIT Button until you get this message
> Click OK and restart the service
If this message error appears, no issue. Click on OK and wait for the service to run
Step 7 : Modify IIS Web sites settings
> Go through IIS portal - HTTP redirect for each Webservice/website
> Unselect redirection
Step 8 : Check the installation
> Log on to Dscp and check the version installed
Step 9 : Communication & documentation
> Update the version of patch in Dscp Environments GSheet
> Inform DP & DiP teams by email. Communicate the patch updates (D:\DynaSys\<MODULE>\Dscp\Bin\readme_fix.html file).
GoLIVE
Step 1 (Day-1) : Inform users that DSCP applications won't be available during a specific timeslot
Step 2 (Day D) : Same instructions as TEST. Perform all steps 3 to 7 by PROD application
Step 3 (Day D or D+1) : Once all production applications are patched, do the same in DEV.