Difference between revisions of "Web Screen Painter"
From SDU
m |
m |
||
| Line 5: | Line 5: | ||
== Overview == | == Overview == | ||
This articles provides an under-the-hood explanation of the Web Screen Painter (WSP) and the Schema Designer introduced in r11.x. | 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 == | == Web Screen Painter == | ||
| Line 12: | Line 11: | ||
*Uses Tomcat exclusively. | *Uses Tomcat exclusively. | ||
*All published changes are automatically exported to all Secondary Servers. | *All published changes are automatically exported to all Secondary Servers. | ||
| − | |||
=== On Save === | === On Save === | ||
| Line 19: | Line 17: | ||
* 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. <br>''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.'' | * 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. <br>''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.'' | ||
| − | |||
=== On Publish === | === On Publish === | ||
| Line 30: | Line 27: | ||
* The [[pdm_webcache]] command is automatically initiate which clears the cache on 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 out === | === Backing out === | ||
| Line 37: | Line 33: | ||
*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. | *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. | ||
| − | |||
== See Also == | == See Also == | ||
[[Schema Designer]] | [[Schema Designer]] | ||
Revision as of 05:24, 26 July 2008
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.
To discuss or ask questions about this article, select the discussion tab above.
Overview
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
WSP Facts:
- Located on the Primary Server.
- Uses Tomcat exclusively.
- All published changes are automatically exported to all Secondary Servers.
On Save
When 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.
On Publish
When 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 out
Both 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.
