Forum Discussion
NimbostratusCitrix XML Broker Integration Options
Hi There,
I have implemented webtops to present Citrix applications via interrogating the XML broker service for several sites. This works well (mostly) with no web interface required.
I have a new site that I have implemented that has a specific requirement, multiple user logins with the same username. With the web interface you would normally disable workspace control (and make sure the policies and listeners allow multiple sessions of course), however with the direct interrogation of the XML brokers where is this option kept? I've been through everything I can see in the profiles/policies on the F5 and cannot find anything relating to it. I've also Google'd this to death and cannot find any information on this issue.
Does anybody have any pointers on this or will the web interface be required for this implementation?
Thank you in advance Frazer
9 Replies
Michael_KoyfmanCirrocumulus
This is disabled by default when using APM as the presentation layer. As each user connects, their sessions are separate - is that not happening in your case? If not, can you provide the exact combination of Workspace Control settings on WI that allow for your desired behavior? Thanks.
- Son_of_Tom_1379Thanks Michael, that's interesting that it should happen by default, as it's certainly not on any of our sites we've setup. As soon as the second copy of the application is launched, the session from the first login is stolen. The workspace control settings we would use are simply to turn it off. Usually workspace control would be turned on, more than likely with reconnect to all sessions to enable the individual user account logins (keep in mind we're trying to login concurrently with the same user accounts in our scenario) to reconnect if they are disconnected. In our case we would simply want to create a new session should they be disconnected. Thanks
- Michael_KoyfmanHave you tried to change this setting on your XenApp server? http://discussions.citrix.com/topic/280637-xenapp-6-using-1-login-id-for-multiple-sessions/ I just tried it on my XenApp 6.5 and was able to launch to independent ICA sessions to the same application from two different browsers using the same user account
- Son_of_Tom_1379Thanks Michael, As stated yes policies and listeners are correct. This issue is only apparent when you don't have a web interface, as in our case we're directly addressing the XML brokers. Thanks for the response though!
Michael_Koyfma1Cirrus
This is disabled by default when using APM as the presentation layer. As each user connects, their sessions are separate - is that not happening in your case? If not, can you provide the exact combination of Workspace Control settings on WI that allow for your desired behavior? Thanks.
- Son_of_Tom_1379Thanks Michael, that's interesting that it should happen by default, as it's certainly not on any of our sites we've setup. As soon as the second copy of the application is launched, the session from the first login is stolen. The workspace control settings we would use are simply to turn it off. Usually workspace control would be turned on, more than likely with reconnect to all sessions to enable the individual user account logins (keep in mind we're trying to login concurrently with the same user accounts in our scenario) to reconnect if they are disconnected. In our case we would simply want to create a new session should they be disconnected. Thanks
- Michael_Koyfma1Have you tried to change this setting on your XenApp server? http://discussions.citrix.com/topic/280637-xenapp-6-using-1-login-id-for-multiple-sessions/ I just tried it on my XenApp 6.5 and was able to launch to independent ICA sessions to the same application from two different browsers using the same user account
- Son_of_Tom_1379Thanks Michael, As stated yes policies and listeners are correct. This issue is only apparent when you don't have a web interface, as in our case we're directly addressing the XML brokers. Thanks for the response though!
- Son_of_Tom_1379
I've had a response from F5 technical support, and they have advised that the reconnect setting is hard coded and cannot be overridden (when directly addressing the XML brokers).
They've advised that as this is a replacement mode for WI, they will look into changing this.
