How are the HTMPL and XML files in the NX_ROOT\BOPCFG\WWW\HTMPL 'tagged' folder used?
Article ID: 50476
Updated On:
Products
CA Service Management - Service Desk Manager
CA Service Desk Manager
Issue/Introduction
This document explains how the HTMPL and XML files in the NX_ROOT\BOPCFG\WWW\HTMPL 'tagged' folder are used.
NX_ROOT\bopcfg\www\htmpl\web\analyst\xml\*.xml
NX_ROOT\bopcfg\www\htmpl\web\analyst\tagged\*.htmpl
Environment
CA Service Desk Manager - all versions
All Supported Operating Systems
Resolution
These files are used for localization by the CA Service Desk Manager Configure tool (pdm_configure).
When run, pdm_configure checks the tagged folder and the XML folder. Based on the content of these folders, it may regenerate the HTMPL files that exist in the subfolders under the NX_ROOT\bopcfg\www\htmpl\web folder, such as the analyst, customer and employee folders.
For example, let use the detail_in.xml and detail_in.htmpl files.
When run, pdm_configure checks the tagged folder and the XML folder. Based on the content of these folders, it may regenerate the HTMPL files that exist in the subfolders under the NX_ROOT\bopcfg\www\htmpl\web folder, such as the analyst, customer and employee folders.
For example, let use the detail_in.xml and detail_in.htmpl files.
The pdm_configure program uses detail_in.xml in the XML folder to determine how it should translate values in the HTMPL file in the tagged folder. The result is an HTMPL file that includes the translated values.
When run, pdm_configure gets the values from the xml file and uses them with the corresponding tagged HTMPL file to generate the resulting HTMPL file in the NX_ROOT\bopcfg\www\htmpl\web\analyst folder.
The generated HTMPL file is given the same timestamp as the newer of the two source files: detail_in.htmpl in the tagged folder or detail_in.xml in the XML folder. The timestamp does NOT get set to the date and time that pdm_configure is executed.
If you have customized any of the XML files or tagged HTMPL files, be sure to take a backup of your customizations before applying any patches because some patches may replace these files and when pdm_configure is subsequently executed, the HTMPL in the resulting directories is then also replaced.
NOTE: It is necessary to modify the NX_ROOT\site\config.properties file on the environment to set resources.created=0. If this parameter is not set, the HTMPL re-generation process will be skipped.
When run, pdm_configure gets the values from the xml file and uses them with the corresponding tagged HTMPL file to generate the resulting HTMPL file in the NX_ROOT\bopcfg\www\htmpl\web\analyst folder.
The generated HTMPL file is given the same timestamp as the newer of the two source files: detail_in.htmpl in the tagged folder or detail_in.xml in the XML folder. The timestamp does NOT get set to the date and time that pdm_configure is executed.
If you have customized any of the XML files or tagged HTMPL files, be sure to take a backup of your customizations before applying any patches because some patches may replace these files and when pdm_configure is subsequently executed, the HTMPL in the resulting directories is then also replaced.
NOTE: It is necessary to modify the NX_ROOT\site\config.properties file on the environment to set resources.created=0. If this parameter is not set, the HTMPL re-generation process will be skipped.
Additional Information
Feedback
Yes
No
Powered by
