Calls the Mapper Service.
ibm.MapPipe retrieves mapinputdata and mapoutputdata from the data bucket, calling the Mapper Service to map the input source to the output source. It then stores the mapped output source back into the data bucket.
Table 1. Table containing expressions and their descriptions for ibm.MapPipe
|map ||service||Identifies which Mapper Service to use for mapping data.|
|pidOutputs.main ||pipe||Triggers the next pipe in the pipeline.|
TX Mapper Configuration
Table 2. Table containing expressions and their descriptions for TX mapper configuration
|key, string||One or more files that are to be used in the mapping operations. The data sub parameter points to the data for that file in the data bucket. The name sub parameter is the name that will be used to refer to the File later.|
data = key:txmap
name = string:FormDataMap.mmc
|mapinputdata.TXMap ||string||The name of the file that is the TXMap that was defined by the mapinputdata.File#.name parameter.|
|mapinputdata.Input Card#.data (optional)||key||TXMaps can have zero or more input cards. If you want the input for any of these cards to come from data in the data bucket you can specify the card number and the key from which you want to get the input.|
InputCard1.data = key:formdata
|mapinputdata.Output Card#.data (optional)||key||TXMaps can have zero or more output cards. If you want the output for any of these cards to be written into the data bucket you can specify the card number and the key to which you want to write the output.|
OutputCard1.data = key:outputdata
TX Mapper Service example
For this example we have some XML instance data in the data bucket called formdata that has been extracted from a Form. We want to use TX to transform this data into an HTML response page that will be returned to the user showing them the results of submitting the Form.
ibm.MapPipe.simpletx.mapinputdata.File1.data = key:txmap
ibm.MapPipe.simpletx.mapinputdata.File1.name = string:FormDataMap.mmc
ibm.MapPipe.simpletx.mapinputdata.TXMap = string:FormDataMap.mmc
ibm.MapPipe.simpletx.mapinputdata.InputCard1.data = key:formdata
ibm.MapPipe.simpletx.mapoutputdata.OutputCard1.data = key:outputdata
In this example there is only one file called FormDataMap.mmc that file is loaded from the data bucket under the name txmap
The next parameter defines which TXMap we are running. In this example it is the file FormDataMap.mmc.
When the map was designed it was created with one inputcard and one outputcard. The inputcard is the XML instance, so we will override our TXMaps first inputcard to get its data from the key formdata in the data bucket.
Lastly we want the output from the Map to be written back into the data bucket so we can use later in the pipeline. We override the output card to write its data to the key outputdata in the data bucket.
There is only one file we are using for our mapping; the main Map file. A Map could have multiple other associated files defined for example: the main Map might use a number of sub maps, and they would need to be loaded into the data bucket and referenced by the ibm.MapPipe for the main Map to run. For example:
Parent topic: Pipes