# Linux Server Install {% hint style="info" %} Test Data Orchestrator (TDO) has been re-branded to Wayfinder as of Q1 2026. These documents are currently being re-written to reflect that change. Test Data Orchestrator / TDO / Wayfinder all refer to the same product throughout these documents. {% endhint %} ### Linux Install & configuration guide Download links for the software will be provided after initial evaluation Document of Understanding or purchase contracts are signed. Before installing Wayfinder (TDO), ensure MongoDB is running (follow the instructions in the online manual to start MongoDB). Ensure that you are logged in with the Wayfinder (TDO) admin ID or have run sudo to get admin privileges. ### Setup Move tdo\_repo.zip to appdir. Run: *unzip tdo-repo.zip* Run: *cd appdir/ignite* (If ignite subdirectory does not exist, create it using the md command and then change to that directory.) Move ignite.zip to appdir/ignite. Run: *unzip ignite.zip* Run: *cd..* to return to appdir Run: *chmod -R 775 ./* Run: ./setup.sh all Next, you will need to edit files using the vi command (*vi* *filename* to enter edit mode, *:wq!* to save and exit edit mode). · Edit start.sh – remove the first four lines. The file should begin with the line ‘ echo "> Starting ORSON" ‘. · In line 7, replace ‘ mongo.user=root mongo.pass=root ‘ with ‘null null’. · Save file after editing.

start.sh before editing

· Edit run.sh – remove the first five lines. The file should now start with the line ‘ echo "killing " $(jps -mlV | grep PropertiesLauncher) ‘. Save file after editing.

run.sh before editing

· Run: *cd engine* to change to the appdir/engine subdirectory. · Edit run.sh. The first line will begin with: o java -server -Xms1024m -Xmx2048m o the Xmx variable can be increased (in increments of 1024) to increase total memory in use by Wayfinder (TDO). o This value should never exceed total server memory allocated to Wayfinder (TDO). o Increasing this value (ex: 16384 for 16GB) will improve Wayfinder (TDO)’s performance for memory-intensive tasks. o If you edit this value, remember to save the file before proceeding. Run*: cd ..* to return to appdir Run: *nohup ./start.sh all &* to start Wayfinder (TDO). It will take about 30 seconds for the application to fully initialize. To confirm that the application is ready, run *JPS* at the command line. When you see 2 jar processes, 1 jps process, and 1 CommandLineStartup process (a total of 4 processes) then the application is ready to use. ### Initial action You will first need to set up an admin ID to allow initial testing and user maintenance to be done. Once you have set up your initial users, and have at least one admin ID created for your user base, this initial ID can be deleted on the User maintenance screen. To create the initial ID, open a new tab in Chrome and go to http\://\:8080/ui/public/signup. For example, you would enter: . If you have https enabled, then this would be forwarded to port 8443 instead of 8080, and it would look like this: :. If you are running Wayfinder (TDO) on a remote desktop/virtual server and accessing it from that same server, your url would look like this: [http://localhost:8080/ui/public/signup](http://localhost:8080/public/signup). If you are running Wayfinder (TDO) on a remote desktop/virtual server and accessing it from your desktop, you would use the server name instead of the IP address and your url would look like this: . · A new user screen will appear. Fill in the username, password and email and hit the signup button. This will take you to the login screen. \[Note that any user created using this initial signup screen will be an admin user.] · Log in using the ID and password you have created. · Once you have logged in, you can create new users in the User Management section of the tool. See the ‘User Maintenance’ section of this on-line manual for detailed instructions. · While Wayfinder (TDO) can be set up with LDAP authentication, it cannot be done until at least one project is created. We do not recommend LDAP setup during a Proof of Concept/Proof of Technology evaluation as this process requires coordination with your network, AD, and/or security teams and can take several weeks to complete. ### Stopping the application Wayfinder (TDO) runs in three layers – the application, Ignite, and MongoDB. · Only stop MongoDB for a full server restart. It can remain running for an upgrade. · Only stop Ingite to correct an Ignite error or for a full server restart. It can remain running during an upgrade. To shut down the Wayfinder (TDO) application: Run: *./stop.sh all* This will stop the api and engine processes but leave Ignite and MongoDB running. To stop Ignite, you will need to know the process ID. Run *JPS* and write down the process number at the left of the ‘CommandLineStartup’ process. Run: *kill -9 \* where \ is the value you wrote down in the step above. ### Restarting Wayfinder (TDO) Run: *nohup ./start.sh all &* to start Wayfinder (TDO). It will take about 30 seconds for the application to fully initialize. ### Upgrading Wayfinder (TDO) Download the new tdo-repo.zip file from the standard repository location as before. In the appdir, run: *rm -r !(\*ignite\*)* this will remove all files except the ignite subdirectory from appdir. Move tdo\_repo.zip to appdir. Run: *unzip tdo-repo.zip* Run: *chmod -R 775 ./* Run: ./setup.sh all Next, you will need to edit files using the vi command (*vi* *filename* to enter edit mode, *:wq!* to save and exit edit mode). · Edit start.sh – remove the first four lines. The file should begin with the line ‘ echo "> Starting ORSON" ‘. · In line 7, replace ‘ mongo.user=root mongo.pass=root ‘ with ‘null null’. · Save file after editing. · Edit run.sh – remove the first five lines. The file should now start with the line ‘ echo "killing " $(jps -mlV | grep PropertiesLauncher) ‘. Save file after editing. · Run: *cd engine* to change to the appdir/engine subdirectory. · Edit run.sh. The first line will begin with: o java -server -Xms1024m -Xmx2048m o the Xmx variable can be increased (in increments of 1024) to increase total memory in use by Wayfinder (TDO). o This value should never exceed total server memory. o Increasing this value (ex: 16384 for 16GB) will improve Wayfinder (TDO)’s performance for memory-intensive tasks. o If you edit this value, remember to save the file before proceeding. Run*: cd ..* to return to appdir Run: *nohup ./start.sh all &* to start Wayfinder (TDO). It will take about 30 seconds for the application to fully initialize. To confirm that the application is ready, run *JPS* at the command line. When you see 2 jar processes, 1 jps process, and 1 CommandLineStartup process (a total of 4 processes) then the application is ready to use. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/technical-guides/linux-server-install.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.