Hi Miguel, you should avoid doing that, each instance will have its own database cache. If another instance writes in the same database this will lead to inconsistency between the caches.
If you are using the SOAP API you should be able to use different Openmeetings servers each one with its own database. The only remaining problem is that you cannot use the private-folder feature as this folder will look different depending on which server you are connecting to. There is another clustering option. The Edge/Orion Clustering of Red5. This solution would fix the database problem as only the "Origin" server would handle the database connection, while all "Edges" only act as Streaming Servers. However this requires some background knowledge, a testing environment with 2-3 servers and some changes in the Source Code. If you are interested in trying that I can try to assist you. Sebastian 2011/10/17 Miguel Carro Pellicer <[email protected]> > Hi subscribers! > > I want to ask a question about a new implementation that we have done. We > installed 4 app servers with the same version of OM, and we connected the 4 > instances to the Same Oracle DB server (Same schema, same user, same > server). Do you think this can cause problems? We have a lots of users and > we need to use different servers to distribute the load, our integration > using WebServices distributes the rooms in different servers. > > > Example: Rooms created in server 1 always goes to server 1. > > This is not for high availability, only to distribute the load between > servers. > > If it can cause problems, we can use different schemas and different users. > > Thanks in advance for the tips, Miguel. > -- > > [image: cid:[email protected]]**** <http://www.samoo.es/> > > ** ** <http://www.samoo.es/> > > *Miguel Carro Pellicer* > > *Technical Manager - Director técnico* > > [email protected]**** > > +34 - 96 393 69 15**** > > www.samoo.es**** > > ** ** > > Este correo y sus archivos asociados son privados y confidenciales y va > dirigido exclusivamente a su destinatario. Si recibe este correo sin ser > el destinatario del mismo, le rogamos proceda a su eliminación y lo ponga > en conocimiento del emisor. La difusión por cualquier medio del contenido > de este correo podría ser sancionada conforme a lo previsto en las leyes > españolas, Ley Orgánica 15/1999 de Protección de Datos de Carácter > Personal. No se autoriza la utilización con fines comerciales o para su > incorporación a ficheros automatizados de las direcciones del emisor o del > destinatario.”**** > > ** ** > > This mail and its attached files are confidential and are only and > exclusively intended to their addressee. In case you may receive this mail > not being its addressee, we beg you to let us know the error by reply and to > proceed to destroy it. The circulation by any mean of this mail could be > penalised in accordance with the Spanish legislation. Is not allowed the use > of both, the transmitter and the addressee’s, address with a commercial aim, > or in order to be incorporated to automated data process or to any kind of > files. **** > > ** ** > > P Antes de imprimir este correo electrónico piense bien si es necesario > hacerlo. El medioambiente es cosa de todos.**** > > ** ** > > ** ** > > -- > You received this message because you are subscribed to the Google Groups > "OpenMeetings developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/openmeetings-dev?hl=en. > -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
<<image002.jpg>>
