KB-1004 "Premature end of file" error returned during application server startup

Parmida Borhani — Mon, 30 Jul 2018 03:43:54 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:43:54 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

As part of running the configure script, there will be appian-topology.xml files generated in <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf. These files are copies of the appian-topology.xml.example file. The default configuration is commented out within this example file. This causes the appian-topology.xml files to be created without the proper configuration.

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: known issues, application server, fixed issues, infrastructure

KB-1004 "Premature end of file" error returned during application server startup

Nick Vigilante — Thu, 13 Jul 2017 16:32:20 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 7/13/2017 4:32:20 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: known issues, application server, fixed issues

KB-1004 "Premature end of file" error returned during application server startup

Nick Vigilante — Fri, 10 Feb 2017 10:59:04 GMT

Revision 4 posted to Appian Knowledge Base by Nick Vigilante on 2/10/2017 10:59:04 AM

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: known issues, application server, fixed issues

KB-1004 "Premature end of file" error returned during application server startup

Nick Vigilante — Thu, 09 Feb 2017 22:17:08 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/9/2017 10:17:08 PM

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

15:50:25,072 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

As part of running the configure script, there will be appian-topology.xml files generated in <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf. These files are copies of the appian-topology.xml.example file. The default configuration is commented out within this example file. This causes the appian-topology.xml files to be created without the proper configuration.

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: application server

KB-1004 "Premature end of file" error returned during application server startup

Nick Vigilante — Thu, 09 Feb 2017 17:43:09 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 2/9/2017 5:43:09 PM

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: application server

KB-1004 "Premature end of file" error returned during application server startup

Nick Vigilante — Thu, 09 Feb 2017 17:17:55 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 2/9/2017 5:17:55 PM

Symptoms

Application server fails to start during the deployment of Appian. The logs indicate a parse exception due to Premature end of file.

The following error message appears in the logs:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 70) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: java.lang.ExceptionInInitializerError
at com.appiancorp.process.security.InitializeAdministrator.finish(InitializeAdministrator.java:68) [appian-process.jar:]
at com.appiancorp.common.config.ConfigObject.init(ConfigObject.java:65) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:372) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.initConfigObject(ConfigObjectRepository.java:263) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.init(ConfigObjectRepository.java:223) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:95) [appian-common.jar:]
at com.appiancorp.common.config.ConfigObjectRepository.create(ConfigObjectRepository.java:89) [appian-common.jar:]
at com.appiancorp.common.config.ConfigurationLoader.contextInitialized(ConfigurationLoader.java:47) [appian-common.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException; Premature end of file.]

Cause

Action

This issue has been corrected in Appian 7.9 Hotfix Package B. Please apply the latest cumulative hotfix package to resolve this issue.

Workaround

Use either of the following options:

Remove the appian-topology.xml files from <APPIAN_HOME>/ear/suite.ear/conf and <APPIAN_HOME>/search-server/conf to use the default topology configuration.
Modify the files to include the desired engine and search server configuration.

Affected Versions

This article applies to Appian 7.9.

Last Reviewed: February 2017

Tags: application server