All messages in Sonic ESB are multi-part messages. Currently, the OpenEdge Adapter for Sonic ESB looks for its input message in the first part, and creates a new message with its output. However, there are cases where you want to have flexibility in how messages are handled. You can have this flexibility by using service run-time parameters. The following run-time parameters let you specify an input message part and an output message part:
InputMessagePart — An integer parameter that specifies which message part to use for the input to the OpenEdge service. The message part must be the proper XML that the service is expecting. There is no difference in functionality when using a value of 0 or 1. They will reflect the current functionality of using the first part for the input message. The default is 0.
OutputMessagePart — An integer parameter that specifies which message part to use for the output of the service call. A value of 0 (the default) retains current functionality by returning a new message. A value of 1 retains the original message and replaces the first part with the output. This is useful if you want to retain the message properties of the original message.
You set the values of run-time parameters when you create a process. The values are evaluated when the service is invoked. If you specify an output message part, the original message is kept intact, with the output of the service call placed in the specified part. By default, there is no change in functionality if you do not specify these run-time parameters.
For more information on Sonic run-time parameters, see the Sonic documentation.
InputMessagePart — An integer parameter that specifies which message part to use for the input to the OpenEdge service. The message part must be the proper XML that the service is expecting. There is no difference in functionality when using a value of 0 or 1. They will reflect the current functionality of using the first part for the input message. The default is 0.