How to trigger the installation wizard or otherwise configure a direct connection through command line?

Deadline
1

Title.

I want to install a repository or change its configs using the command line, preferably in -nogui mode. Something like ./deadlinecommand -ConfigureDirectConnection <bunch_of_params>

Is there a way to do that?

2

You can install the Repository silently through the command line. The arguments are not in the docs but they’re all documented if you do installer.run --help.

3

All the commandline flags the installers take are in the advanced install steps - Database and Repository Installation (Advanced) — Deadline 10.3.0.15 documentation

And for deadlinecommand you’re looking for if you want to change which repository the client is point to use ChangeRepository.

4

Hmm, yeah I got that far, but this still isn’t quite helping me.

So let me be a bit more specific:

I want to automate the deployment of deadline using ansible, an IT automation tool.
This means, deadline will be deployed in unattended mode.

So far so good, using the flags –mode unattended --unattendedmodeui minimal , I can deploy the client, but in that case, the configs aren’t setup and most of the .ini files are empty/defaulted.

Things that are filled out during the manual installation process through the wizard mainly.

-ChangeRepositorySkipValidation , at first glance, looks l promising, but I am not 100% if that is the end of the story or if I will still be missing a bunch of config steps.

Also, I saw a flag –optionfile < optionfile>. Maybe that one is one piece of the puzzle, but I am not sure how that optionfile is supposed to look like, what params it accepts and what it is actually able to affect, I can’t find anything about this in the docu.

5

Got it, for setting up the client it’s got its own set of silent install flags. Detailed here on the advanced client install page.

The ChangeRepositorySkipValidation is good if you’ve already got the client set up, but it’s simpler to get it right the first time.

The option file doesn’t have any extra functionality, it’s just a way to collect all the command line flags into a single spot. To format the optionfile it needs to be formatted as key/value pairs each on their own line.

Example:
prefix=/tmp
validateLicense=0
installDocumentation=1
…

This file can be passed to the installer using the --optionfile command line flag:
$> myInstaller.run --optionfile path/to/configuration.options

Full docs here in the installbuilder website.