| How to access existing session variables after an application transfer is performed |
| Categories: Audium OpenSDK, Audium Studio (3.4.x) |
| Article ID: | 76 |
| Last updated: | February 19, 2008 |
| User Opinions |
66%
33%
(3 votes)
|
|
Thank you for rating this answer.
|
SUMMARY
This article explains how to access session variables created by Audium application A after it performs an application transfer to Audium application B.
SYMPTOMS
Developer would like to route callers to a new Audium application, but still be able to access session variables created in the first Audium application.
RESOLUTION
First, ensure that all of the session data you would like to transfer to the new application has been listed on the Data tab of the Application Transfer element's configuration. This data will then be sent to the new application when the application transfer is performed.
However, Audium adds, as a prefix, the application's name to any session data being transferred to the new Audium application. The new variable name will be in the form APPNAME_VARIABLENAME. For example, if you have session data named VARIABLE1, and transfer it from Audium application A to Audium application B, in application B your transferred session data will be available as A_VARIABLE1.
Note that the prefix will be added to the existing variable name every time you do a transfer, hence during the next transfer, say from application B to application C, the data will be renamed to B_A_VARIABLE1.
Audium does not limit the amount of session data that can be created, however the size of data can be limited by the Tomcat configuration and/or the memory limitations of the server.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment