IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Defining and transforming data > Create and mapping interfaces > Mapping interfaces (deprecated)
Parameter mappings
Parameter mappings map parameters in the source operation to parameters in the target operation.
The following types of parameter mappings are supported:
- Assign
- This type of parameter mapping is employed when a constant value must be applied to a certain input or output/fault parameter. The Assign parameter mapping does not connect two parameters, it is connected to only one parameter.
- Extract
- This type of parameter mapping is employed when you need to extract a type nested in a complex type.
For example, you could have a business object that contains a string field "Name" and use an Extract parameter mapping to map to a parameter "customerName" that is also of type string. An Extract parameter mapping pulls out the pertinent information from a complex parameter and reconciles it with output parameters. An Extract parameter mapping can have only one input but can feed multiple outputs.
- Map
- This type of parameter mapping is employed when you have two business objects that need to be reconciled. The Map parameter mapping represents the business object map that reconciles different business objects.
For example, one business object might have five fields and one business object might have three fields. In addition, the fields might have different names. You can use the Map parameter mapping to reconcile these differences. A Map parameter mapping can have multiple inputs and multiple outputs.
- Move
- This type of parameter mapping is employed when you need to make a simple connection. You can create a Move parameter mapping only between parameters of the same type.
For example, both the source and target parameters must have the same type, such as "string", "double", or "boolean" for the Move parameter mapping to work. However, note that a Move parameter mapping might also be used between business objects of the same type, not only between simple types. A Move parameter mapping can have only one input but can feed multiple outputs.
- Custom
- This type of parameter mapping is employed so that arbitrary Java code can be introduced (or called out) when an interface map is invoked according to the specification in an IFM file. You can use this flexible parameter mapping as an extension, and it can take any parameters and change them as needed.
For example, you can use the Custom parameter mapping to reconcile a simple type parameter with a business object parameter where the Java code will create an instance of business object and populate it according to the value of the simple type.