Complete the Parameter Mapping

This topic covers input and output mapping, and things you should consider when mapping.

You should click the Input To Service and Output From Service tabs to complete the input and output mapping between any parameters or data fields in your process and the Java code.

You can choose to use automapping to map automatically. To do this, use the automap button above the mappings. See "Automapping" in Calling a Web Service for more information.

Mapper Restrictions and Notes

  • If you attempt to map data fields or parameters to parameters of a different type (for example, mapping a String to an Integer), an error is generated in the Problems view.
  • If numbers are being mapped, you must perform a one to one mapping.
  • Floats and doubles are limited in precision and TIBCO Business Studio validates the mapping of these data types as follows:
    Data Type Process to Java Java to Process
    Float 6 maximum 6 minimum
    Double 15 maximum 15 minimum

    From process to Java, errors are generated if these limits are exceeded. From Java to process, warnings are generated if these minimum values are not adhered to.

  • Use of system exit is prohibited.
  • Mapping of process Decimal numbers to Java Integer numbers can lead to a loss of precision (there is a validation rule for this).
  • Mapping of Java Decimal numbers to process Integer numbers can lead to a loss of precision (there is a validation rule for this).
  • There is a validation rule that checks that all the input parameters for the POJO service have been mapped.