Anyone have some guidance for creating a second or more instance(s) of Openfire in a Windows environment.
not really possible unless you have separate NICs in the computer or run the servers in separate Virtual Machines with dedicated IP. This is because of conflicting protocol ports.
Hi dhollas,
sorry, for the moment i do not have exprience of Openfire for Windows environment.
However for the moment we are runnign multiple intances on linux environment. If you change the environment, I’m happy to give some help/guidance if needed.
Koski,
We are running Openfire on CentOS.
Could you give us some tips for hosting multiple domains on the same server?
-Thermal
Hi thermalwetland,
did you try to set up the OpenFires (OFs) already? Anyway setting up multiple instances is very straight forward.
First what you’ll need is own IP’s for each OF instance. Best practise is that you have domain names that resolv to these IP’s. However I do not know what are your needs for the instances so maybe only IP’s are enough.
Second you need own DB for each instance.
Third you need to extract as many instances of OF to your filesystem as you need isntances of.
Let’s say now that you have domain names “of1.example.com” resolving to IP 88.22.33.01 and “of2.example.com” resolving to IP 88.22.33.02.
After extracting the OFs to your filesystem for example from tar -files (you’ll need to untar those as many as you need instances), you need to modify conf/openfire.xml -file for each installation before starting up the initial configuration. What is needed is to specify a network OF will bind to because by default OF will bind to all network interfaces found.
In the openfire.xml you’ll find following lines where you can specify a specific network interfaces that the OF instance will listen on:
For example for the first instance you would uncomment the element and add the IP/domain wanted:
of1.example.comAfter this you can start the instance and continue with the installation.
Let me know if this was any help. If you have any problems, don’t hesitate to write back
This is not true. Windows can do this as well.
Hi,
i’m completely sorry, i have made a mistype in the post. Todd Getz is right.
I ment to write that I do not have experience of Openfire on Windows environment. Not that it’s not possible. Sorry for all misundertsandments my previous mail caused.
Hi Koski,
Do you know if I could modify the conf/openfire.xml file to set (for example) xmpp.socket.plain.port for client to server communication? I’d like to do it from a script rather than from the admin console.
Thanks!
tamien wrote:
Hi Koski,
Do you know if I could modify the conf/openfire.xml file to set (for example) xmpp.socket.plain.port for client to server communication? I’d like to do it from a script rather than from the admin console.
Thanks!
Hi Tamien,
i don’t know if this is possible and sorry, i have no time to test now. But I know that the openfire.xml tries to load the properties from the openfire.xml in format:
value
So you can try adding the following to the openfire.xml:
5225
If this does not work you can add this property directly to the database to the table ofProperty.
Hope this helps.
br,
–
Tuomas
Hi Todd, Thanks for the reply . We are using seperate NIC with dedicated IP. How do we accomplish this with these inplace?
-D
Tuomas,
I’m currently using the embedded db so I was hoping to use the xml file to set the properties. The file is read at startup, but it does not seem to make any difference when including the new tags. Back to the drawing board for me and thanks for your reply!
Tamien
Hi tamien,
tamien wrote:
The file is read at startup, but it does not seem to make any difference when including the new tags.
ok, sorry to hear.
Just to verify, did you add the:
5225
element inside the root element ?
Sorry, I admid my previous mail was again a bit misleading.
Hey Tuomas,
Here is a portion of the config file (I use the one you get with a fresh install):
5225 9090 9091I the save the file, and start the OF server. When I check through the admin console my xmpp.socket.plain.port is still set to 5222. Also, from the info log: 2008.11.03 13:53:46 Started plain (unencrypted) socket on port: 5222
cheers,
t
Hi,
tamien wrote:
I the save the file, and start the OF server. When I check through the admin console my xmpp.socket.plain.port is still set to 5222. Also, from the info log: 2008.11.03 13:53:46 Started plain (unencrypted) socket on port: 5222
I just got home and checked the code. It seems that it does not read the port from the XML file at all but only from properties or uses the default value 5222. (src/java/org/jivesoftware/openfire/spi/ConnectionManagerImpl.java:677)
Sorry I did not check that right from the start.
Once again sorry for the noise.
br,
–
Tuomas