At the moment, the server-side configuration of the Gateway exporter (gateway-tool-configuration.xml) requires the template path to point to the export template using an absolute link. This works fine, however, that means, that, if you want to put the templates on the Integriyt server itself, that you need a separate configuration file for each Integrity server, even if the path only differs by the hostname and port.
Therefore, it would make the configuration of the server a lot easier, if the gateway-tool-configuration would support something like relative paths, which would (if used) take the Integrity server hostname and port as a base and request the template from there based on the relative path provided in the template.
For example, the current configuration would look like (some properties are removed for readability):
<export-config>
<exporter id="MSWORD">
<property name="template">https://example.com:443/gateway/export/template.docx</property>
</exporter>
<extension>docx</extension>
</export-config>
while a possible relative URL could look like:
<export-config>
<exporter id="MSWORD">
<property name="template">./gateway/export/template.docx</property>
</exporter>
<extension>docx</extension>
</export-config>
The gateway exporter would need to use the Integrity connection details (hostname, port, protocol) to connect to the server and download the template. If the Integrity Client/server uses https for communication, then the template should be retrieved by https, too, otherwise http should be used.
