Customizing › Web Interface Customization › The Web Screen Painter (WSP) › Test to Production Migration

Test to Production Migration

One of the design goals for WSP was to make it safe to develop and test forms modifications on a production database. Such features as a Web Screen Painter‑only directory tree on the server, dedicated Web Screen Painter server processes, and read‑only preview sessions support this goal. However, many users prefer to develop their forms modifications in an independent test system and then migrate the forms to a separate production system after they are complete as follows:

1. Copy any HTMPL forms to be migrated from the appropriate subdirectory of site/mods/www/htmpl on the test system to the same subdirectory of site/mods/wsp/project on the primary server of the production system.
2. Copy any CSS, JavaScript, and HTML files to be migrated from the appropriate subdirectory of site/mods/www/wwwroot on the test system to the same subdirectory of site/mods/www/wwwroot/wsp/project on the primary server of the production system.
3. Use WSP on the production system to publish the forms. Using WSP for publishing ensures that the new or updated forms are distributed to all production servers.

You can use any file copying method supported by your operating system to perform the copying described in steps 1 and 2 above. Windows users should substitute backslash (\) for slash (/) in the directory paths shown.