Starting and stopping the system properly is very important for maintaining the highest levels of system availability.
Note: Improper Shutdown
Bootstrap Language: If you want to change the startup language and timezone used by the system, this must be changed prior to the first time you log into the system. The default language for all users remains accessible through the user interface, at all times.
If you are running the Appian components as Windows services, use the Microsoft Management Console to start them in the order listed below instead of using the .bat
script that is listed. When running Windows services, a process named jbosssvc.exe
appears in the task manager for each of these. Use the display name of the service instead of the process name to determine which services are running.
Note: Before starting and stopping the Appian services the first time, you must set a password. See Password Script
<APPIAN_HOME>\services\bin\start.bat -p <password> -s all
to start the Appian services.<APPIAN_HOME>\data-server\bin\start.bat
to start the data service.<APPIAN_HOME>\search-server\bin\start.bat
<APPIAN_HOME>\tomcat\apache-tomcat\bin\start-appserver.bat
.<APPIAN_HOME>/tomcat/apache-tomcat/bin/stop-appserver.bat
.<APPIAN_HOME>\search-server\bin\stop.bat
.<APPIAN_HOME>\data-server\bin\stop.bat
.<APPIAN_HOME>\services\bin\stop.bat -p <password> -s all
. It may take several minutes for all engine services to stop as they conduct a checkpoint procedure as part of the standard shutdown.<APPIAN_HOME>\services\bin\status.bat -p <password>
To verify that all Appian processes have stopped running, complete the following:
q.exe
, k.exe
, or java.exe
processes (and jbosssvc.exe
processes if you're running Windows services).<APPIAN_HOME>\services\bin\checkpoint.bat
. Use the --wait
option so that the script exits only after the checkpoints have completed.<APPIAN_HOME>\services\bin\status.bat -p <password>
Note: Before starting and stopping the Appian services the first time, you must set a password. See Password Script
For Linux, use Bash 3.0 or later.
If restarting, type the following commands to ensure that no Appian processes are active:
1
2
3
ps -ef | grep /k
ps -ef | grep /q
ps -ef | grep /java
<APPIAN_HOME>/services/bin/
../start.sh -p <password> -s all
../status.sh -p <password>
<APPIAN_HOME>/data-server/bin/start.sh
.<APPIAN_HOME>/search-server/bin/start.sh
.<APPIAN_HOME>/tomcat/apache-tomcat/bin/start-appserver.sh
.<APPIAN_HOME>/tomcat/apache-tomcat/bin/stop-appserver.sh
.<APPIAN_HOME>/search-server/bin/stop.sh
.<APPIAN_HOME>/data-server/bin/stop.sh
.<APPIAN_HOME>/services/bin/stop.sh -p <password> -s all
. It may take several minutes for all engine services to stop as they conduct a checkpoint procedure as part of the standard shutdown.Type the following commands to verify that no Appian processes are running:
1
2
3
ps -ef | grep /k
ps -ef | grep /q
ps -ef | grep /java
.kdb
file is not being written.For installations distributed across many servers, the order of operation for starting and stopping Appian remains the same:
--cluster
option if you are running more than one set of Appian enginesIf Appian services are on different servers, for example Kafka & Zookeeper on one server and engines on another, all services should be running before starting the data service and search server. The order of operation does not matter. If the Appian engines are started before Kafka & Zookeeper, the engines will wait for the other services before they become available.
When stopping Appian services on a different servers, use the ./stop -p $PASSWORD -c
script command to have the service manager handle shutdown coordination.
If a distributed installation of Appian is being stopped with the intention of removing a server, follow the directions on How to remove servers from a distributed installation for self-managed installations.
Using one of the supported web browsers, use the following URL to access the Appian Designer interface:
http://SERVER_NAME:8080/suite/design
When logging in for the first time, use the Administrator account with the password admin.
After logging in, you are automatically prompted to change the Administrator password.
If your application server starts and stops abruptly, you may have a port conflict that is preventing the application server from running. You can diagnose and resolve such issues in the following manner:
appian-topology.xml
file.See also: Port Usage and Server Configuration Topologies
Verify your Java configuration settings.
It is possible to experience issues when attempting to run the application server as a Windows service, if the JAVA_HOME location includes a space in the file path (such as C:/<APPIAN_HOME>/java
).
Starting and Stopping Appian