Changes between Version 2 and Version 3 of fms-migration

Timestamp:

Aug 15, 2018, 1:29:19 PM (7 years ago)

Author:

steve.winter

Comment:

--

fms-migration

@@ -1 @@
-1. When configuring the !FileMaker server, 
+1. In the website CMS disable the transfer of orders from the website to FM
+
+2. On the dev server place the site into offline mode by editing `C:\inetpub\wwwroot\assets\includes\config.php` and setting `define('siteOffline', true);`
+
+3. Modify the mapping on the router such that all traffic to payment.solopress.com (IP 194.74.170.116) is directed to the dev server (IP 192.168.0.90). This will display the message 'This site is offline for schedule maintenance. Please try calling back later. We apologise for any inconvenience caused.' to anyone who tries to make a payment while the upgrade is being performed.
+
+4. When configuring the !FileMaker server, 
  - use the new wildcard SSL certificate for the server
- - enable the XML interface using either the CLI or API
- - enable the PHP API using either the CLI or API
+ - enable the XML interface and PHP API using either the CLI `fmsadmin SET CWPCONFIG ENABLEPHP=true ENABLEXML=true` or through the FMS Admin API
 
-2. Ensure that there is a valid DNS entry for the !FileMaker server which the PHP code can connect to the PHP API interface using (e.g. fms.solopress.com).
+5. Ensure that there is a valid DNS entry for the !FileMaker server which the PHP code can connect to the PHP API interface using (e.g. fms.solopress.com). Ideally this should have both an internal and external IP addresses so that traffic from the PHP code doesn't have to exit the LAN to connect. Currently cwp.solopress.com is also configured to connect to the production server.
 
-3. Import the payment.solopress.com EV SSL certificate to the local machine certificate store
+6. Import the payment.solopress.com EV SSL certificate to the local machine certificate store
 
-4. Download and install the subversion command line client from https://msdev.co.uk/windows-svn-client/
+7. Download and install the subversion command line client from https://msdev.co.uk/windows-svn-client/
 
-5. Open a command prompt, run the following commands to export the PHP code from version control into the webroot folder
+8. Open a command prompt, run the following commands to export the PHP code from version control into the webroot folder
 {{{
 cd c:\inetpub\wwwroot
@@ -16 +21 @@
 }}}
 
-6. Create the payment.solopress.com virtual host in the IIS console. 
+9. Create the payment.solopress.com virtual host in the IIS console. 
  - Set the Physical Path to C:\inetpub\wwwroot
  - bind to port 80 with host payment.solopress.com
  - bind to port 443 with host payment.solopress.com, require SNI, and select the payment SSL cert
 
-7. Ensure that the internal DNS entry for payment.solopress.com points to the correct internal IP address
+10. Ensure that the internal DNS entry for payment.solopress.com points to the correct internal IP address
 
-8. Modify `C:\inetpub\wwwroot\assets\includes\config.php` to point to the DNS name of the FMS, including the https protocol (this is a new FM17 requirement)
+11. Modify `C:\inetpub\wwwroot\assets\includes\config.php` to point to the DNS name of the FMS, including the https protocol (this is a new FM17 requirement) which means it must be a fqdn and not an IP address which is used.
 
-9. Switch the payment gateway to test mode in the above config file.
+12. Switch the payment gateway to test mode in the above config file (line 112, set `define('sagePayMode',      'test');`).
 
-10. Conduct end-to-end testing of the payment process to ensure everything functions as expected (e.g. using https://payment.solopress.com/?/order/v9jhQs8TPbFxp8748HUUPi/dfdd16d0b176755c8434754d1d78701b)
+13. Conduct end-to-end testing of the payment process to ensure everything functions as expected (e.g. using https://payment.solopress.com/?/order/v9jhQs8TPbFxp8748HUUPi/dfdd16d0b176755c8434754d1d78701b)
 
-11. Conduct testing of the order submission process
+14. Conduct testing of the order submission process
 
-12. Revert the payment gateway in the config file to production mode
+15. Revert the payment gateway in the config file to production mode (line 112, set `define('sagePayMode',      'production');`).
 
-13. Switch the external DNS for payment.solopress.com to point to the external IP address of the server
+16. Update the router configuration for payment.solopress.com to direct to the production server IP
+
+17. Revert the change to the dev server to place the site back into online mode by editing `C:\inetpub\wwwroot\assets\includes\config.php` and setting `define('siteOffline', false);`
+
+18. In the website CMS re-enable the transfer of orders from the website to FM.
+
+19. Conduct a low-value test of the payment gateway to ensure that the production environment is functional. Refund that payment through the SagePay gateway.