Web Screen Painter
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
This articles provides an under-the-hood explanation of the Web Screen Painter (WSP) and the Schema Designer introduced in r11.x.
Web Screen Painter
- Located on the Primary Server.
- Uses Tomcat exclusively.
- All published changes are automatically exported to all Secondary Servers.
On SaveWhen initiating a save (File > Save) the following occurs:
- The $NX_ROOT\site\mods\wsp\project directory is created if it does not already exist.
- A new or modified file is stored within the $NX_ROOT\site\mods\wsp\project\... directory which has a structure that mimics the location of the default version of the file.
For example: If editing the bin_form_np.htmpl used by the Analyst Interface which originally resides in $NX_ROOT\bopcfg\www\htmpl\web\analyst, a saved copy will be placed in$NX_ROOT\site\mods\wsp\project\www\htmpl\web\analyst.
- Do not forget that also 2 tables are updated by web screen painter to "remind" the modification. It is possible that some change (made manually for example) are not know by the WSP with all the side effect that can result in case of modification.
On PublishWhen initiating a publish (File > Publish) the following occurs:
- Any saved versions of the files being published that reside within $NX_ROOT\site\mods\wsp\project\... are removed.
- A new or modified file will be stored on the Primary and all Secondary Servers within the $NX_ROOT\site\mods\... directory which has a structure that mimics the location of the default version of the file.
For example: If editing the bin_form_np.htmpl used by the Analyst Interface which originally resides in $NX_ROOT\bopcfg\www\htmpl\web\analyst, a saved copy will be placed in$NX_ROOT\site\mods\www\htmpl\web\analyst. CA ensures that the default files are never altered by your customizations by saving custom files in a dedicated location.
- A deleted file will be removed from the Primary and all Secondary Servers.
- The pdm_webcache command is automatically initiate which clears the cache on the Primary and all Secondary Servers.
Backing outBoth published and unpublished forms can be deleted via the WSP. However, you can also navigate through the directory structure and delete the file.
- For saved but unpublished, navigate through the $NX_ROOT\site\mods\wsp\project\... directory and remove the target file.
- For published files, navigate through the $NX_ROOT\site\mods\... directory on the Primary and all Secondary Servers, delete your file from all servers, and run the pdm_webcache from the Primary Server.
|This page was last modified 05:24, 30 November 2010. This page has been accessed 7,734 times. Content is available under Attribution-Noncommercial-Share Alike 3.0 Unported. Disclaimers|
Powered by IpbWiki: Integration Of Invision Power Board and MediaWiki © GlobalSoft
Powered by MediaWiki © Wikimedia