d7x Command Line Arguments

d7x Command Line Arguments can be used for scripting d7x or performing other specific functionality.

Arguments for Scripting

Requires v19.5.23.0 or greater!

*** With all options below, a new d7x session is created automatically (if d7x is not already in a session) but the session is not ended automatically.  See “The ‘Session’ Concept (IMPORTANT)” on the main page of the d7x Manual for more information.

Scripting with the d7xRDT (Create one-click automated maintenance/etc.)

When creating a newer d7xRDT you will be prompted to optionally pass command line arguments to the d7x .exe when it is launched.  This now allows you to deploy a d7xRDT.exe to a remote system to perform tasks automatically by using the arguments above.  See the video d7x Quick Tip – Automating the d7xRDT for more on setup and usage.

d7x and .EXE naming

d7x releases are named according to version number (which is based on the date of release.)  This can make scripting difficult if d7x were to update and the filename were changed.  For this reason, d7x can create a batch file “d7x.cmd” which it will update the batch file each time d7x is updated to a new version, replacing the .exe name in the batch file with the latest version.  Therefore, in scripting you would call “d7x.cmd” and not the name changing d7x vx.x.x.x.exe file.

To create the d7x.cmd so that d7x recognizes this, open d7x Config and on the first tab, right side of the page mid way down, you will see a “Create d7x.cmd” button.  Just click that to create the initial d7x.cmd, and as mentioned d7x will update this batch file as it updates itself with the new name, allowing you to use the d7x.cmd file for your scripting in place of the .exe name.

Unsupported Arguments

Arguments below are provided for the curious only; they do NOT work in conjunction with any scripting arguments listed above, and are NOT SUPPORTED, as functionality may be subject to change without notice.