Running the WildcardMatch sample

Before you can run the sample you must have completed the set up steps, see Setting up the WildcardMatch sample, and imported and deployed the sample, see WildcardMatch sample.

Note: The FileInput nodes poll the input directory every 5 seconds, therefore, if you type quickly the expected output might not be visible. Refreshing the directory list 5 seconds later shows the correct result.

If you encounter any problems when you run the sample, see Resolving problems when running samples in the IBM Integration Bus documentation.

Copy the file to send to the Hursley branch to the directory that the FileInput node is monitoring:

The file JohnHillsHursley contains the following text message:

 Hi John, 

 Confirming our meeting for the 24th at 10am 
 We can meet at the Hursley branch
 
 Best Regards,
 
 Paul

To run the sample:

1. Save the contents of JohnHillsHursley as a text file called To_JohnHills@hursley.txt to the to_hursley subdirectory that you created.
2. Check the contents of the output directory, for example c:\MQSIFileInput\hursley. The directory contains a file called JohnHills.txt. Check the contents match the JohnHillsHursley file.

The output shows :

• $LocalEnvironment/Destination/File/Name and $LocalEnvironment/Destination/File/Directory are set in the Compute node by using values that are taken from $LocalEnvironment/Wildcard/WildcardMatch. In this sample $LocalEnvironment/Wildcard/WildcardMatch is set to JohnHills@Hursley because the input file name is To_JohnHills@hursley.txt and the wildcard value that is used in the FileInput node File name or pattern property is To_*.txt.
• The Compute node splits the value JohnHills@hursley in $LocalEnvironment/Wildcard/WildcardMatch and used JohnHills as part of the file name set in $LocalEnvironment/Destination/File/Name and uses hursley as part of the directory name set in $LocalEnvironment/Destination/File/Directory. The Compute node also uses the $LocalEnvironment/Destination/File/Directory to find out the root directory name.
• The FileOutput node has the Request file name property location set to $LocalEnvironment/Destination/File/Name, and this variable is assigned a value in the Compute node. The local environment setting for the destination file name overrides the FileOutput node property setting for File name. The output file name that is used is JohnHills.txt
• The FileOutput node has the Request file directory property location set to $LocalEnvironment/Destination/File/Directory, and this variable is assigned a value in the Compute node. The local environment setting for the destination directory overrides the FileOutput node property setting for Directory. The output directory name that is used is c:\MQSIFileInput\hursley or /tmp/MQSIFileInput/hursley

Back to sample home