After you unzip the Nuxeo DM 5.4 archive file and before starting your first DM session, it's worth identifying the most important files and scripts you'll be dealing with when running DM. So assuming you've moved into the top level of your new DM directory, here's a short list of useful files:
- bin/nuxeoctl: This is the top-level DM control script, responsible for starting, stopping, restarting and examining your DM session, and it should be the only script you use to manage running DM. Earlier (pre-5.4) versions of DM used a different control script, run.sh, but that script is deprecated and should no longer be used. For all normal DM operations, you should restrict yourself to the nuxeoctl script. If there are special circumstances when you need to run other scripts, that will be explained at the appropriate time.
- bin/nuxeo.conf: This is the single configuration file that controls the properties of your DM session. For the time being, we're going to leave it untouched, and cover major configuration only after you've had the chance to run a simple DM session.
- bin/version.sh: Strictly speaking, this script isn't necessary for running your DM session so much as it's a useful feedback script for troubleshooting. If at any point you run into problems and want to submit a bug report or ask a question on any of Nuxeo's forums, the output of that script will describe your server layout in detail to make debugging far easier. And, yes, you can run it now if you want; it has no effect on a DM session and you don't even need to be running DM for it to work.
There's one more point worth making here. The default configuration of a newly-unloaded DM is a completely self-contained directory structure. What that means is that all user data, run-time information, log files and everything else related to this DM installation resides within that directory. This means that, if you want to totally remove your DM installation and start over, you need only remove that directory and unload the zip file again. Obviously, you would never do that with a production installation, but for the purposes of testing, it's convenient to be able to delete every trace of a DM installation and install it fresh.