On premise entry batch - encrypted credentials

In Administration there is a facility to compile a credentials into encrypted file. This is available through the using the Create Script button.

In this window the user credentials MDB and conditions (which optionally defines the windows users can start the macro, which physical machine can run the macro and a time window in which the macro will work). The input window is the location of the macro to be run by the macro and this output is where script will be created.

This encrypted file can now be called from the DOS script.

"C:\Program Files\AVEVA\product nameX.X\mon.exe" PROD XXX init "C:\Program Files\AVEVA\product nameX.X\launch.init" TTY -macro="$m/<path to encrypted file>"

Entry batch for LaaS – Unencrypted credentials.

Firstly, there are a couple of environmental variable needs to be defined for the LaaS license server.

AVEVA_CONNECT_LOGIN = TRUE

AVEVA_LICENSE_SERVER_LIST = <URL pointing to License Server>

This is an indicator that LaaS is being used instead of AVEVA Licensing Service and will prompt all entries to AVEVA products to use LaaS.

When setting up a unattended batch

To login via batch file the project subscription ID (for example ec56ea4c-0ac9-4550-93f4-34e77e8abd25) has to be supplied instead of the three-letter code.

"C:\Program Files\AVEVA\product nameX.X\mon.exe" PROD XXX init "C:\Program Files\AVEVA\product nameX.X\launch.init" TTY -interactive=false -proj=SUBSCRIPTION ID -user=USERNAME -pass=PASSWORD -mdb=/MDBNAME -macro="$m/<path to macro>"

DOS Batch LaaS – Encrypted credentials

The method for creating encrypted details is the same as used for non-LaaS on-premises projects.