Configuration of a!documentViewerField() in On-premise environment

RE: Configuration of a!documentViewerField() in On-premise environment

Stefan Helzle — Mon, 12 Jan 2026 20:22:22 GMT

There are so many things that can be wrong with this. DNS lookup und reverse lookup coming to my mind. Proxies, firewalls, etc. Is this in the open internet? Did you buy the domain names?

RE: Configuration of a!documentViewerField() in On-premise environment

kirankhemnar — Mon, 12 Jan 2026 17:55:14 GMT

configuration -

please let me know if you need any other information

TIA

RE: Configuration of a!documentViewerField() in On-premise environment

Stefan Helzle — Mon, 12 Jan 2026 17:30:11 GMT

You might need to share a bit more info to get some help.

RE: Configuration of a!documentViewerField() in On-premise environment

kirankhemnar — Mon, 12 Jan 2026 16:58:55 GMT

We did same configuration but no luck..

facing below issue

The webpage at devstatic.lawfiles.net:8080/.../ww0ECQMCjLHrOI1Vwm8B0ncBpBjq0MTn_owcl_DT9hpK9hPQ9d4uc6sTam0aa3qQdM-0kzg6AI52vjTNxB_b3i1iKReGqhcsBEJ5i22Y_XXVMNoMOYZ3qvfifLBnhtLONZu5Ni5jUD4HDIDq1Bs50zpS0Uyotbb9Djw6ZiXHb4WavRjbj7w might be temporarily down or it may have moved permanently to a new web address.

RE: Configuration of a!documentViewerField() in On-premise environment

Jackie Jubien — Thu, 28 Mar 2019 22:10:35 GMT

Depending on whether you have a standard or non-standard set-up, you will have to create your URLs similar to the way the documentation explains:

Example when using a standard top-level domain like .com or .co.uk:

conf.suite.SERVER_AND_PORT=www.example.com:8080
conf.suite.STATIC_SERVER_AND_PORT=www.example-static.com:8080
conf.suite.DYNAMIC_SERVER_AND_PORT=www.example-dynamic.com:8080

Example when using a non-standard top-level domain like .corp:

conf.suite.SERVER_AND_PORT=www.example.corp:8080
conf.suite.STATIC_SERVER_AND_PORT=www.example-static.corp:8080
conf.suite.DYNAMIC_SERVER_AND_PORT=www.example-dynamic.corp:8080
conf.suite.conf.suite.DISABLE_STRICT_DOMAIN_SECURITY=true

Keep in mind the port may be different depending on whether you are using HTTP or HTTPS. Another thing to consider, is that since you are setting up two new domains, if you are utilizing white-listing you will have to allow those domains.

RE: Configuration of a!documentViewerField() in On-premise environment

krishnau3863 — Wed, 27 Mar 2019 12:06:15 GMT

Thanks for your response, Jackie Jubien. But they have given,

conf.suite.STATIC_SERVER_AND_PORT, conf.suite.DYNAMIC_SERVER_AND_PORT, and conf.suite.SERVER_AND_PORT are all unique. So how should we give values for static and dynamic port. or can we provide the same as in the SERVER_AND_PORT for both static and dynamic.

RE: Configuration of a!documentViewerField() in On-premise environment

Jackie Jubien — Tue, 26 Mar 2019 23:45:58 GMT

It sounds like you have already updated the static and dynamic content URLs based on the following documentation: docs.appian.com/.../Post-Install_Configurations.html

Also ensure that these are unique values - community.appian.com/.../kb-1821-tomcat-starts-with-misconfigured-static_5f00_server_5f00_and_5f00_port-dynamic_5f00_server_5f00_and_5f00_port-property-in-custom-properties-warning

From that point you will need to restart the app servers for the changes to take affect.