Why I am not able to create a stateful VSI for the Demo Forward Cars application?

Document ID : KB000093566
Last Modified Date : 16/10/2018
Show Technical Document Details
Why am I not able to create a stateful VSI for the Demo Forward Cars application?
Here is the list of steps performed:
1. List the cars using the car inventory
2. Add a new car
3. List the cars again and response should contain the listed cars
4. Update the cars
5. List the cars which should give the updated car details.
All Supported DevTest releases.
The transactions captured with the ForwardCars application, are all stateless - there are no logical relationships between transactions.
To create a stateful service we need to have the necessary information to create and identify the session.

There is a X-MULE_SESSION in the meta-data response, but this is not an ID that determines a relationship between these transactions. This meta-data key is available only with the responses. To create a conversation, this meta-data key should be available on the conversation starter response and then in the subsequent requests.
In a conversation, a transaction depends on the context that earlier conversations created.

If you still want to create a stateful service from these stateless transactions you can try to use one of the common attributes in the request payloads and set it as LISA session key. Below are the steps:
1. while creating the virtual service image, add the request data manager DPH on the request side.
2. add a new action to the request data manager DPH.
3. set the common attribute as LISA session key, in this case it was the 'HTTP-Segment-ATT-0: inventory'. The Action List will have:
Action: Copy
Source Type: Attribute
Source Name: HTTP-Segment-Attr-0
Target Type: LISA session key

Continue with the virtual service creation.
Additional Information:
For more information regarding Stateless and Conversational VSE Transactions:

For more information regarding the Request Data Manager Data Protocol Hander: