Calling a Direct Subprocess

In this sample, the MainProcess process uses the Call Process activity to call two direct subprocesses. One subprocess creates a list of movies, and the other subprocess either uses the genre of the movie to determine how to log it, or returns the name of the current movie.

Note: If accessing the sample from the Welcome page of TIBCO Business Studio™ for BusinessWorks™, go directly to Step 3.

    Procedure
  1. In the samples directory, select core > soa > DirectCallProcess and double-click tibco.bw.sample.core.soa.DirectCallProcess. For more information, see Accessing Samples.
  2. In the Project Explorer view, expand the tibco.bw.sample.core.soa.DirectCallProcess.readme project.
  3. Set the default ApplicationProfile to match the OS you are running on. For more information, see Setting the Default Application Profile.
  4. Fully expand the Processes directory and double-click MainProcess.bwp.
  5. Click Run > Debug Configurations.
  6. At the left hand tree of Debug Configuration wizard, expand BusinessWorks Application and select BWApplication.
  7. Click the Applications tab and then click the Deselect All button if you have multiple applications. Select the checkbox next to tibco.bw.sample.core.soa.DirectCallProcess.
  8. Click Debug.
    This runs the sample in Debug mode.
  9. Click the Terminate icon to stop the process.
Result

The output.log file is generated in the C:\tmp\CallProcess\ActionMovie.txt directory. This file contains output from the ActionMovieList direct subprocess and OtherMoviesList direct subprocess.

Understanding the Configuration

This is a hands-on and simple demonstration for the design time experience with the direct subprocess. The MainProcess.bwp process creates a list of movies, then according to the movie genres, calls a direct subprocess to either log outputs to a text file, or to return the name of the current movie.