Using wildcards

The FileInput node resolves any wildcards in its file name or pattern properties, and places the evaluated wildcard expression at $LocalEnvironment/Wildcard/WildcardMatch. The TX Map node uses this result for non-wired input and output cards that contain a wildcard to evaluate the correct source and target name, for example, filename and command line.

If you want more than one input card of the IBM Transformation Extender map to receive data from IBM Integration Bus, you need to use the Collector node. The Collector node can pass wildcard values from the FileInput node to the TX Map node when you set the Correlation path property of the Collector node to $LocalEnvironment/Wildcard/WildcardMatch in the Basic tab of the Properties view.

One way to use wildcards is to represent a portion of a name for an output file that you want IBM Transformation Extender to create, so that it includes the corresponding characters from a message correlation ID that IBM Transformation Extender receives.

One example is if you configured a FileInput node with the c:\*inputdata.txt file name, and a IBM Transformation Extender non-wired output file with the DATA*.txt name. If the FileInput node receives an input file with the 123inputdata.txt name, the wildcard expression evaluates to 123, and the result is that IBM Transformation Extender produces an output file with the DATA123.txt name.

Another example is if you configured a FileInput node with the c:\*input??data.txt file name, and a IBM Transformation Extender non-wired output file with the DATA*.txt name. If the FileInput node receives an input file with the 123inputHQdata.txt name, the wildcard expression evaluates to 123inputHQ, and the result is that IBM Transformation Extender produces an output file with the DATA123inputHQ.txt name.