Taskers on Windows

Accelerator can dispatch jobs to taskers running on Windows hosts. Starting the taskers on Windows hosts, however, is less automated than on UNIX hosts.

To prepare the Windows host:

  1. Mount the filesystem with the Accelerator installation on the Windows machine in the form of a drive letter. For example, assume that the installation is mounted as f:\rtda\<version>. Enter the location depending on your network setup.
  2. Start a Windows cmd shell . Initialize it by executing the vovinit.bat script that is in the installation directory under win64/bat.
    For the example, use:
    % f:\rtda\<version>\win64\bat\vovinit.bat

    The vovinit.bat file adds the Altair Accelerator commands to the PATH and sets other environment variables used by the software.

    You may consider adding the following shortcut to your desktop to facilitate this operation in the future:
    cmd /k f:\rtda\<version>\win64\bat\vovinit.bat

    Refer to the Windows documentation to learn how you can add a shortcut to the desktop.

  3. Start the Tasker Server Daemon with:
    % vovtsd -user vncadmin

    where vncadmin should be replaced by the login name of the Accelerator administrator who is running the Accelerator vovserver.

  4. Mount all other drives required to perform the tasks.
    Basically, the Windows host must be capable of performing the tasks that are about to be dispatched by the Accelerator vovserver. This means that the filesystem with the run directory must be mounted at a drive letter, since you may not change directory to a UNC path.

Taskers on UNIX

  1. Declare the Windows host in vnc.swd/taskers.tcl.
  2. Be sure to add the host to the list of Windows hosts, not the UNIX hosts. These hosts need to use special values for the option -serverdir and -vovdir of vtk_tasker_define. All of this is also explained by comments in the sample vnc.swd/taskers.tcl file.
  3. Start the tasker using, for example, a soft reset:
    % ncmgr reset -taskers