Example: Using the BeanShellPipe Component

You can use the BeanShellPipe component between the AsapSource and FileSink components. BeanShellPipe executes some commands in shell after it receives data from AsapSource, and before publishing data to FileSink.

  1. Set the username and password in the example environment:
    Operating System Step
    UNIX
    1. Edit the set_example_env.sh script
    2. Set the ADAPTER_EXAMPLE_USERNAME and ADAPTER_EXAMPLE_PASSWORD variables to sybase.
    Windows
    1. Edit the set_example_env.bat script
    2. Set the ADAPTER_EXAMPLE_USERNAME and ADAPTER_EXAMPLE_PASSWORD variables to sybase.
  2. Start Event Stream Processor.
    Operating System Step
    UNIX Open a terminal window:
    1. Start the example cluster:

      start_node.sh

    2. Start the project on the cluster:

      start_project.sh
    Windows Open a command window:
    1. Start the example cluster:

      start_node.bat

    2. Add project to the cluster, and start it on the cluster:

      start_project.bat
  3. Start esp_subscriber to subscribe to the project that is running on the cluster.
    Operating System Step
    UNIX Open a terminal window and enter:

    subscribe.sh
    Windows Open a command window and enter:

    subscribe.bat
  4. Start the AsapSource, FileSink and BeanShellPipe components.
    Operating System Step
    UNIX Open a terminal window and enter:

    ./asapToFile.sh
    Windows Open a command window and enter:

    asapToFile.bat
  5. Upload data from the esp_insert.txt file to Server.
    Operating System Step
    UNIX Open a terminal window and enter:

    ./esp_upload.sh
    Windows Open a command window and enter:

    esp_upload.bat
    AsapSource reads this data and passes it to BeanShellPipe, which then passes it to FileSink, which writes it to the out.txt file. BeanShellPipe outputs the text to the command prompt.
Parent topic: Examples
Related reference
BeanShellPipe Properties