ORSON - Test Data Orchestrator
Linux Install & configuration guide
Before installing TDO, ensure MongoDB is running (follow the instructions in the online manual to start MongoDB).
Ensure that you are logged in with the 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.
· 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 TDO.
o This value should never exceed total server memory allocated to TDO.
o Increasing this value (ex: 16384 for 16GB) will improve 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 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://<IP_of_your_server>:8080/ui/public/signup.
· 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 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
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 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 <process_id> where <process_id> is the value you wrote down in the step above.
Restarting TDO
Run: nohup ./start.sh all & to start TDO. It will take about 30 seconds for the application to fully initialize.
Upgrading 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 TDO.
o This value should never exceed total server memory.
o Increasing this value (ex: 16384 for 16GB) will improve 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 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.
Last updated
Was this helpful?
