Operate and Manage the Experience Service > Operating Your Experience Service > Start the Experience Service
  
Start the Experience Service
* 
To allow the Experience Service to be shut down gracefully on Windows, it should only be run in the foreground.
1. (Linux Only) If you are a non-root user on Linux starting the Experience Service without using sudo, you must have following file system permissions:
Read (r), write (w), and execute (x) permissions on the installation directory and all the contents of that directory
Ownership of the installation directory and all of the contents of that directory
Read (r), write (w), and execute (x) permissions on the stores directories (projects, reps and upgrade) and all the contents of the directories
Ownership of the stores directories (projects, reps and upgrade) and all the contents of the directories
2. From a terminal window, navigate to the bin directory in the Experience Service installation directory. Based on your operating system, use one of the following commands to start the Experience Service:
Operating System
Command
Linux
start-es.sh <configuration parameters>
Windows Server 2016
start-es.bat <configuration parameters>
Where <configuration parameters> is replaced with any configuration parameters that you choose to pass on the command line.
This starts the Experience Service in either secure HTTPS mode or insecure HTTP mode depending on whether you choose to Use TLS (HTTPS) on the TLS Configuration step of the installer.
If the ThingWorx server is using self-signed certificates, you may need to start the Experience Service in a mode where the self-signed certificate is allowed by passing the --allowssc parameter on the command line. For more information, see Configure Trust for a ThingWorx Certificate.
For example, start-es.sh --allowssc <configuration parameters> or start-es.bat --allowssc <configuration parameters>
If you chose to use TLS, you can override this configuration and start the Experience Service in insecure HTTP mode by passing the --nossl parameter on the command line.
start-es.sh --nossl <configuration parameters> or start-es.bat --nossl <configuration parameters>
3. To verify that the Experience Service is properly configured and running, follow the steps in Validate Installation and Configuration.