<< Click to Display Table of Contents >> dpPower > Appendix > Configuration options > Tomcat site |
Digpro does not take responsibility for what the customers add themselves to tomcat-site. Also note that the application might work slower. |
Tomcat and tomcat-site must be on the same disk drive. For example, if tomcat is under c:, then you also put tomcat-site there. In the tomcat site, you can place various customer-specific solutions that are not changed during an upgrade and where you can go in and change your own settings yourself.
The most common use of tomcat-site is when you choose to link documents in the attribute form, where you can have a default path filled in. You can change this path yourself by entering the path you want in the file basepath.conf in tomcat-site.
It is also possible to add many other customer-specific things to the tomcat site, but certain configuration changes must be made for it to work, more examples than linking documents are:
•A customer-specific question in the query tool that you want to be able to change yourself and that you don't want to be overwritten during upgrades.
•You want to be able to use the Customer Instructions found under the Help menu, where you can enter instructions for users at your company about various things. Customer instructions then point to a file that is in tomcat site and that cannot be overwritten when upgrading and that can be edited.
•If you have automatic dgn or dxf exports for map sheets, these can be added to the tomcat site to facilitate upgrades and so that they are not affected by the upgrade.
•Logs or images that you use and that you may want to be able to replace for some reason or that should not be able to disappear or change during an upgrade can be under tomcat-site.
A lot that is customer-specific and that you do not want to be affected by an upgrade can be put under tomcat-site, provided that you make some configuration changes first. |
See also:
Configuring paths in Basepath.conf