Configuring Batch Monitoring for the Communications Backbone

This section contains background information about batch tools, and explains how to configure the Communications Backbone (packaged with the software) to allow end users run batches in local and remote mode.

This task shows you how to:

Configure the Communications Backbone on the Remote Machine on Windows

The default port used by the Backbone communication software is 55555. Backbone communication may not work between two remote machines if they use a different backbone port. To get the backbone working correctly, you must ensure that these machines reference the same port.

To perform this check, the BBPortChecker tool is available on this installation. It allows to test the backbone communication between two remote machines (-host option) or between your machine and a list of machines (-l file option). Without any option the BBPortChecker tool display the backbone default port on your machine and tells you how to update it if needed. You can launch this tool by following these instructions.

  1. Open an MS-DOS Window.
    Change to the default folder in which you installed the product.

    For example:

    C:\Program Files\Dassault
          Systemes\B424\win_b64\code\bin

  2. Enter the command:
    BBPortChecker

Start the Server Monitor on the Remote Machine on Windows

This task explains how to start the server monitor on the remote machine on Windows.

To allow end users to run a batch on a remote machine, you first have to start the server monitor on the remote machine.

  1. Log onto the remote machine.
  2. Open a Command Prompt window.
  3. Go to the following installation folder, for example:
    C:\Program Files\Dassault
          Systemes\B424\win_b64\code\bin
  4. Enter the command:
    CATBatSrvMonitorExe BB

    You can use the -allow_visu parameter when launching CATBatSrvMonitorExe in command-line mode.

    Note: DLNames used by a batch executed in remote are those defined in the CATBatSrvMonitorExe environment.