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.
Hello Mr. Schmidt,
I think your request is very important to improve the gateway process.
In my own tests where I moved the Gateway to the Server (see https://community.ptc.com/t5/Integrity-Blog/Integrity-LM-Server-Gateway-and-Reports/ba-p/448480, solution "Integrity Report Gateway"), I also realized that it would be great to be able to stage the gateway-tool-configuration.xml.
(right now its not supported).
This would even more request that the server name inside the XML file is dynamic and is adapted automatically.
My own design for this wold be to move the information into the Integrity database. I dont see any value to have this part (incuding the mapping) in XML files but all other information in the database.
PS: in my own projects I am staging the gateway-tool-configuration.xml too, and I have a scheduled trigger which will make the needed changes in the file according to the current environment. If you are interested, then just let me know.
Hello Mr. Eckardt!
Thanks for your feedback and the insights in how you think about the idea 🙂
Regarding your PS: I'll defenitely contact you! 🙂
the solution i mentioned in my post scriptum is now also here:
Glad that this is what you were looking for.
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.