This step can be further divided into two phases:
$INSTALL_DIR/patches/Patcher.jar is missing. Xeams will not be able to move
from Phase I to Phase II if this file is missing.
- Location of the JRE is important when spawning Patcher (Phase I) as well as spawning the
new instance of Xeams (Phase II). The actual path for the JRE is stored in the
$INSTALL_DIR/config/AppConfig.xml. Ensure the value for
vmPath refers to the
- Phase II also reads the
ntServiceCommand in the
AppConfig.xml file. If this
parameter is blank, Xeams will try to dynamically build the command line. However, Xeams will not be able to
restart itself if the value is invalid. Therefore, having a blank value is fine but an invalid value will break
the restart logic.
Manually Launching Patcher
It is often helpful to start the Patcher manually and see if it display errors on the console. This is equivalent to
jumping directly to Phase II.
The following steps demonstrate this:
- Open an Elevated Command Prompt if
you're using Microsoft Windows or
log in as root if you're using Linux.
- Ensure Xeams is NOT running. Terminate the process if it is running
- Change the current directory to $INSTALL_DIR folder.
- Run the following command:
jre/bin/java -cp patches/Patcher.jar com.synametrics.xeams.util.EngineStarter
Note: Change / to \ on Windows.
Ideally, this should patch the files (move Xeams.jar and webfront.zip) and finally should
start Xeams. The terminal window and/or
log/starterOut.log should display messages if it runs into errors.