WebOffice 10.9 R5 ships custom pages in the folder pub/custom_pages. Values a custom page uses on the server, such as the address of an external source, are maintained under Common > Custom pages (server-side settings) per WebOffice instance instead of in the page or the link. They are kept on updates and can differ between test and production systems.

Changes to the application configuration take effect after a restart of Apache Tomcat.

Custom page xPlanung information

The custom page pub/custom_pages/xPlanung.jsp displays plan content from the XPlanung export of GeoOffice xPlanung. It is added to a query result of a project as a parameterized web integration and passes the parameters PlanId and GmlId from the fields of the result, e.g. pub/custom_pages/xPlanung.jsp?path=https://server/xPlanung. The page loads the plan file <PlanId>.xml on the server and can only be opened from within WebOffice.

The page loads plan files only from the folders entered here. The parameter path of the link only selects one of these folders. If only one folder is entered, this folder is always used.

Property

Description

Plan files folder

A folder with exported plan files. If projects use several folders, add one entry per folder.

Plan files address

Address of the folder from which the page loads the plan files, e.g. https://server/xPlanung. Only http or https, without user name, query parameters or hash sign. Enter the value as it currently appears in the page link (parameter path); the links do not need to be changed. If the server redirects (e.g. from http to https), enter the final address and adjust the links accordingly.

 

icon_comment

After the update: If the custom page xPlanung information is already in use, enter the addresses passed in the link so far (parameter path) once as plan files folders and restart Apache Tomcat. Until then, the page shows a notice and no plan data. Existing links keep working unchanged afterwards.