The CSD Software installation now includes a batch registration tool that can be used to attempt on-line registration via the command line. This tool (located in the Mercury installation directory) can assist in registration on servers where no display is present, or in automating the registration of installations across a site.
The batch registration tool can attempt to register the current machine online and append the resultant licence to the csd_licence.dat file in your current working directory. It is therefore advised to run the tool from the main CSD database directory, where it will be automatically picked up by all users. You will require write permission to the current working directory and csd_licence.dat file if one already exists. The instructions below assume the database is installed in the default location – if located elsewhere then the command line instruction will require the correct path to the batch_register tool.
From the CSD_2017\CSD V5.38 directory run:
..\Mercury\batch_register.exe –current_machine –site_id XXXX –conf_code YYYYY -email firstname.lastname@example.org –auto_accept_licence
From the CSD_2017\csd directory run:
../bin/batch_register –current_machine –site_id XXXX –conf_code YYYYY -email email@example.com –auto_accept_licence
Mac OS X
From the CSD_2017/DATA/CSD 538 directory run:
../../mercury.app/Contents/MacOS/batch_register –current_machine – site_id XXXX –conf_code YYYYY -email firstname.lastname@example.org –auto_accept_licence
In cases where online registration is not possible (for example a compute cluster that has no direct internet access), then it is also possible to use the batch registration tool to collect registration information from any systems you want to register and then use that information to create a licence file valid for those systems on another system that does have internet access. As such, in this scenario registration is a two step process:
Collecting Registration Data
On each system you need to register, run the batch_register command with the arguments "-serial_dir <dir> -write_serial" where <dir> is some common/shared folder location that all systems can access. If there isn't a common location, you can later copy all the node*.txt files that are produced to a common location as a separate step. For example:
batch_register -serial_dir /home/myaccount/serialfiles -write_serial
Registering with the collected data
On a system that does have internet access (and this need not be one of the systems you are attempting to register on), run batch_register with the arguments "-serial_dir <dir> -write_licence -site_id <site id> -conf_code <confirmation code> -email <your email>". This will write a csd_licence.dat licence file that is valid for all the registration data collected in the previous step. For example:
batch_register -serial_dir /home/myaccount/serialfiles -write_licence -site_id XXXX -conf_code YYYYYY -email email@example.com
To use this file, copy it to the database directory of the CSD install on each system - for Windows this is the CSD_2017\CSD V5.38 folder of your installation, on linux it is the CSD_2017\csd directory - in all cases it is the folder containing the as538be.inf file. If you already have a valid csd_licence.dat then the two files can be merged to be valid for all systems (simply append the new licence file text to the end of the existing licence file).
These are just two example uses of the batch_register tool - it is designed to be flexible in how it can be used to complete registration in a more automated manner for multiple deployment scenarios. To see what options the tool allows, run batch_register with the "-help" argument. For help in registering on a system where the above scenarios will not work for you, please contact CCDC support for further assistance.