Testing a System Configuration

Testing a system configuration consists of three steps:

  1. Launching remote devices (if any)
  2. Launching the system configuration
  3. Testing and stopping the system

Launching Remote Devices

If any of the devices in the system configuration are remote devices (RMT_DEV, RMT_FRAME, etc), these must be launched before the system configuration so that the FBEditor tool can configure them as part of the system launch process. How this is done depends on the location of the device:

Launching the System Configuration

After starting the remote devices, if any, you launch the system configuration by pressing the button next to the Run item on the menu bar. As the configuration proceeds, a progress indicator, status commands and responses will appear on the status bar.
If the log option is turned ON in the Preferences dialog, the full listing of commands and responses will be logged into the text pane of the Log tab.
If an error occurs during launching, an error message will appear in a popup window. If you need to find out exactly where in the configuration process this error occurred, you can turn on the Log checkbox in the Run menu, which will cause the configuration commands and responses to be output to the command prompt window from which the FBEditor was launched.
Possible error messages include:
For explanations of other error messages, see subclause 6.5 of the Compliance Profile.

Testing and Stopping the System Configuration

After testing to validate the system's operation versus requirements, you can stop the configuration and kill all the locally running processes by exiting the FBEditor. This assumes, of course, that you are happy with the results of the testing and have already saved all your editing work on the system configuration.

In the more usual case that you want to stop the running processes and make changes to correct errors, you can do the following:

  1. Stop the processes in non-workstation hosts with appropriate platform-specific actions.
  2. Stop the processes running in windows on both the local and remote workstations by closing the windows.
  3. Stop the non-window processes in both local and remote workstations by clicking on their identifiers in the Shut Down item of the Run menus.

Last updated: 2011-02-11.
©2011 Holobloc Inc.
Licensed under the Academic Free License version 3.0.