Testing the FilePoller Application in the Debugger

The debugger provides a simple and fast way of debugging one or more ActiveMatrix BusinessWorks™ applications in a local runtime environment. The applications must be in the workspace and selected before launching the debugger. After starting the debugging session, the debugger does not provide tooling support for deploying and debugging the application on the same runtime instance. The runtime starts when the debugger is started and stops when the debugger is stopped.

Procedure

  1. Right-click in the Process Editor and select the Debug BusinessWorks Applications option from the menu. You can also click to start the debugger or choose Run > Debug.
    The following messages are displayed in the Console view.

    You are running the instance of the FilePoller application. When the debugger is launched, the perspective changes from Modeling to Debug.

  2. After the application starts, the FilePoller and WriteFile activities get triggered and the contents of the fileread.txt will be written to c:\tmp\FilePoller\output.log.
  3. Modify the c:\tmp\fileread.txt file. For example, open the c:\tmp\fileread.txt file and write "Hello BusinessWorks!" and save the changes.
    The FilePoller activity polls every 5 seconds and transitions the contents of the fileread.txt to the WriteFile activity.
  4. Open the file c:\tmp\FilePoller\output.log and verify the updated information, for example, "Hello BusinessWorks!" printed in this file.
    While keeping the application running, explore adding and deleting the words in the fileread.txt file and notice the corresponding changes made to the output.log file.
  5. The path taken by the engine for executing the process is displayed. Transitions turn green to specify that a path was executed.

  6. Click the Businessworks Jobs view on the top left to see the jobs created for the process.

  7. Click a particular activity, then click the Job Data view on the top right to see the input and output data of the activity.
  8. To stop the current job, click the Stop button on the Console view toolbar.