> <Entry key="PutApplicationType">This value is changed Ex: 28 i.e DevTest is not populating from the request</Entry>
> <Entry key="PutApplicationName">This value is changed Ex: exe i.e DevTest is not populating from the request</Entry>
> <Entry key="PutDateTime">This value is changed Ex:1493958792390 i.e DevTest is not populating from the request</Entry>
As far as I know these are not supposed to be copied from the request. Those fields describe the application that is sending that particular message, DevTest in the case of the response message, and the time at which that response message is sent. You can override the first two with meta-data properties, but they will not be copied from the request unless you make modifications to the VSM. The meta-data properties are:
- msg.putApplicationName
- msg.putApplicationType
> <Priority>
> <Persistence>
There are default values for these, and to override those defaults requires you to set meta-data properties in the service image response. Those meta-data properties are:
- msg.priority
- msg.persistence
> <ReplyToQueueName>
> <ReplyToQueueManager>
Why would you set these on a response message? Is there something responding to the response? Again, you can set them in the response with meta-data properties, but copying their values from something in the request requires modifying the VSM. Those meta-data properties are:
- msg.replyToQueueName
- msg.replyToQueueManagerName
> I am not able to control this response selection. Kindly assist me how can I handle this in Respond step.
The way you handle this is by controlling selection. If there is a field that controls whether two responses are sent or three, then that field needs to be part of the request arguments that the VSI was built with. There should be a Data Protocol extracting that field and adding it to the request arguments. That's basically how VSE chooses a response, by using the arguments to differentiate between different transactions.