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.
- Start Event Stream Processor.
Operating System |
Step |
UNIX |
Open a terminal window: - Start the example cluster: start_server_cluster.sh
- Start the project on the cluster: start_project.sh
|
Windows |
Open a command window:- Start the example cluster: start_server_cluster.bat
- Add project to the cluster, and start it on the cluster: start_project.bat
|
- Start esp_subscriber to subscribe to the project above that is running on the cluster.
Operating System |
Step |
UNIX |
Open a terminal window and enter: ./esp-subscribe.sh
|
Windows |
Open a command window and enter: esp-subscribe.bat
|
- 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
|
- 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 to BeanShellPipe, which then passes it to FileSink, which writes it to the out.txt file.
BeanShellPipe outputs the text to the command prompt.