What to use

Hi Tim,

 

 

If source address persistence doesn't meet your requirements and the application is built on a custom TCP-based protocol in which you can't insert a persistence token in the responses, you would most likely want to persist off of some component of the requests/responses. If the persistence token exists in the payload, you'd need to collect the TCP payload and parse the persistence token. You'd probably want to use the TMM persistence or session table to track the persistence token and which node the request went to. The collection can be done using TCP::collect (Click here). Adding a persistence record can be done using 'persist add uie $persist_token $timeout' (Click here). You can use an existing persistence record on subsequent requests using 'persist uie $persist_token $timeout'.

 

 

Although it's based on HTTP, you can use the Codeshare entry for ASP Session ID persistence as a conceptual example:

 

 

ASP Session ID persistence

 

(Click here)

 

 

Here are a few related tech tips:

 

 

Deb's Tech Tip on persist versus persist add:

 

(Click here)

 

 

Colin's Tech Tip on the session command:

 

(Click here)

 

 

Hopefully this gets you started. Let us know if you want clarification on anything.

 

 

Thanks,

 

Aaron