Hi Gregor, Yes we have used LCDS in a clustering environment and what is basically outline is what we have done to get LCDS to work as such: 1) using sticky sessions has nothing to do with LCDS per se, all our apps are configured this way. I would not want to have to review the logs for specific user and need to jump between logs on both servers. 2) For this part, I just added the JGroups JAR file and the jgroups-default.xml file to the application classpath. The only we param in the jgroups-default.xml we changed is the "mcast_port" value which was got from our network admin. That was it, I remember this clearly cause once we added this the clients on server A would get the changes done from clients on server B. Hope that helps! Dimitrios Gianninas RIA Developer and Team Lead Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Gregor Kiddie Sent: Monday, October 22, 2007 11:15 AM To: [email protected] Subject: [flexcoders] Livecycle DS Afternoon all, Does anyone on this list have any experience of deploying Livecycle DS over a clustered environment? This question arises from the 'Adobe LifeCycle Data Services ES Developer's Guide'. The sections around clustering, from page 481, imply that there are only 2 options regarding the deployment of an application attempting to exploit data push: 1) Use a load balancer that is configured to use sticky sessions, and that therefore establishes a stateful connection between a client and only ONE of the application servers in a cluster. 2) Introduce JGroups into your application. The configuration of JGroups requires knowledge of the servers in the target network (which is not known in a 3rd party cluster). This is inflexible and is not a scalable configuration, in that as servers are added or removed each deployment configuration has to be updated to reflect this change. It appears to be another way of replicating some kind of session state which bypasses the transparent clustering capability of (for example) Oracle Application Server, introducing an additional and undesirable bespoke solution. Is our understanding of these options correct. Are these the only options available in relation to configuring Flex for data push from server to client. Can we, for example, use a load balancer that is not configured for sticky sessions and have required state replicated by the application server containers transparently to the deployed application without using JGroups? This is a real sticking point for us, as we really like what DS gives us out of the box, but if it reduces our capabilities in such a manner, it will be a non-starter. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
