KB-1847 Issues with static and dynamic content URLs

Jordan Horwat — Thu, 07 Feb 2019 15:26:47 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 2/7/2019 3:26:47 PM

Symptoms

The static and dynamic content URLs are configured in custom.properties, as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the static and dynamic content URLs (like the document viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The static and dynamic content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component cannot render the document and the following error displays:

Cause

Routing for the static and dynamic content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the static and dynamic URLs in DNS.

Workaround

A user needing to access the static and dynamic URLs can do so by editing their computer's hosts file to route for these URLs. This should be a temporary measure until routing for the static and dynamic URLs in DNS can be configured.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to self-managed Appian 18.3 and later.

Last Reviewed: January 2019

Tags: self-managed, web server, infrastructure

KB-1847 Issues with static and dynamic content URLs

Jordan Horwat — Thu, 07 Feb 2019 10:26:47 GMT

Revision 21 posted to Appian Knowledge Base by Jordan Horwat on 2/7/2019 10:26:47 AM

Symptoms

The static and dynamic content URLs are configured in custom.properties, as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the static and dynamic content URLs (like the document viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The static and dynamic content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component cannot render the document and the following error displays:

Cause

Routing for the static and dynamic content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the static and dynamic URLs in DNS.

Workaround

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

KB-1847 Issues with static and dynamic content URLs

Parmida Borhani — Fri, 18 Jan 2019 01:02:50 GMT

Revision 20 posted to Appian Knowledge Base by Parmida Borhani on 1/18/2019 1:02:50 AM

Symptoms

The static and dynamic content URLs are configured in custom.properties, as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the static and dynamic content URLs (like the document viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The static and dynamic content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component cannot render the document and the following error displays:

Cause

Routing for the static and dynamic content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the static and dynamic URLs in DNS.

Workaround

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Thu, 17 Jan 2019 12:35:19 GMT

Revision 19 posted to Appian Knowledge Base by Zach Puderbach on 1/17/2019 12:35:19 PM

Symptoms

The static and dynamic content URLs are configured in custom.properties, as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the static and dynamic content URLs (like the document viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The static and dynamic content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the static and dynamic content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the static and dynamic URLs in DNS.

Workaround

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Thu, 17 Jan 2019 09:22:09 GMT

Revision 18 posted to Appian Knowledge Base by Zach Puderbach on 1/17/2019 9:22:09 AM

Symptoms

The static and dynamic content URLs are configured in custom.properties, as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the static and dynamic content URLs (like the document viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The static and dynamic content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the static and dynamic content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the static and dynamic URLs in DNS.

Workaround

The static and dynamic URLs can be accessed locally or from another computer by editing its hosts file to route for these URLs.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 15:30:22 GMT

Revision 17 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 3:30:22 PM

Symptoms

The Static and Dynamic Content URLs are configured in custom.properties, such as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the Static and Dynamic Content URLs (like the Document Viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by editing its hosts file to route for these URLs.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 15:29:23 GMT

Revision 16 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 3:29:23 PM

Symptoms

The Static and Dynamic Content URLs are configured in custom.properties, such as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the Static and Dynamic Content URLs (like the Document Viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by editing its hosts file to route for these URLs.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 15:26:49 GMT

Revision 15 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 3:26:49 PM

Symptoms

The Static and Dynamic Content URLs are configured in custom.properties, such as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the Static and Dynamic Content URLs (like the Document Viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by editing its hosts file to route for these URLs.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 15:20:58 GMT

Revision 14 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 3:20:58 PM

Symptoms

The Static and Dynamic Content URLs are configured in custom.properties, such as shown below:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

However, some features that rely on the Static and Dynamic Content URLs (like the Document Viewer component) may not work.

All of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by editing its hosts file to route for these URLs.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: January 2019

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 14:58:41 GMT

Revision 13 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 2:58:41 PM

Symptoms

The Static and Dynamic Content URLs are configured in custom.properties, such as shown below:

However, all of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by adding routing for these URLs in its hosts file.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Fri, 04 Jan 2019 14:56:58 GMT

Revision 12 posted to Appian Knowledge Base by Zach Puderbach on 1/4/2019 2:56:58 PM

Symptoms

The Static and Dynamic Content URLs are set in custom.properties but all of the following symptoms are present:

Symptom 1

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available

Symptom 2

The Static and Dynamic Content URLs cannot be accessed over the browser:

Symptom 3

The document viewer component can't render the document and the following error displays:

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by adding routing for these URLs in its hosts file.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 17:37:26 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 5:37:26 PM

The following fields are all configured properly:

```
conf.suite.SERVER_AND_PORT
```
```
conf.suite.STATIC_SERVER_AND_PORT
```
```
conf.suite.DYNAMIC_SERVER_AND_PORT
```

DRAFT KB-XXXX Issues with Static and Dynamic Content URLs

Zach Puderbach — Thu, 27 Dec 2018 16:22:11 GMT

Revision 11 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 4:22:11 PM

Symptoms

The Static and Dynamic Content URLs set in custom.properties but they cannot be accessed over the browser:

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available.

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by adding routing for these URLs in its hosts file.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 16:21:22 GMT

Revision 10 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 4:21:22 PM

Symptoms

The Static and Dynamic Content URLs set in custom.properties but they cannot be accessed over the browser:

The following errors are NOT present in <APPIAN_HOME>/logs/tomcat-stdOut.log:

WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available.

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by adding routing for these URLs in its hosts file.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 13:31:38 GMT

Revision 9 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 1:31:38 PM

Symptoms

The Static and Dynamic Content URLs in custom.properties have been properly configured.

Cause

Routing for the Static and Dynamic Content URLs are not configured properly or have not been set up.

Action

Work with a network administrator to add routing for the Static and Dynamic URLs in DNS.

Workaround

The Static and Dynamic URLs can be accessed locally or from another computer by adding routing for these URLs in its hosts file.

Example:

With the below configuration in custom.properties:

conf.suite.SERVER_AND_PORT=example.appian.comconf.suite.STATIC_SERVER_AND_PORT=example.appian-static.com
conf.suite.DYNAMIC_SERVER_AND_PORT=example.appian-dynamic.com

Add the following lines to the computer's hosts file:

<IP_OF_example.appian.com> example.appian-static.com
<IP_OF_example.appian.com> example.appian-dynamic.com

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 13:11:28 GMT

Revision 8 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 1:11:28 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT URL's are not configured properly or have not been set up.

Action

Routing for the conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT URL's needs to be configured in DNS.

Workaround

Any computer wanting to accesses these URL's can add the routing information in the computer's hosts file.

<IP_OF_conf.suite.SERVER_AND_PORT

Affected Versions

This article applies to on-premise Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, on-premise, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 12:57:47 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 12:57:47 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT are not configured properly or has not been set up.

Action

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT needs to be configured

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 12:50:28 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 12:50:28 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT are not configured properly or has not been set up.

Action

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 12:50:19 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 12:50:19 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT are not configured properly or has not been set up.

Action

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 12:50:11 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 12:50:11 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT

and conf.suite.DYNAMIC_SERVER_AND_PORT are not configured properly or has not been set up.

Action

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, infrastructure

DRAFT KB-XXXX Static and Dynamic URLs Fail to Load with Web Server

Zach Puderbach — Thu, 27 Dec 2018 12:50:04 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 12/27/2018 12:50:04 PM

Symptoms

The following fields are all configured properly in custom.properties:

conf.suite.SERVER_AND_PORT
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT

Cause

Routing for the URL's specified for conf.suite.STATIC_SERVER_AND_PORT and conf.suite.DYNAMIC_SERVER_AND_PORT are not configured properly or has not been set up.

Action

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: December 2018

Tags: web server, infrastructure