Topic: Wildfire Server HowTo:

[dswillia]

Ok, here is a quick howto on installing Jive Softwares XMPP Server on SME 7.x.  The Software can be downloaded from jivesoftware @ http://www.jivesoftware.org.  Goto the website and download wildfire_2_5_1.rpm.  To install the server type the command:

rpm -ivh wildfire_2_5_1.rpm

The server will be installed in the /opt/wildfire directory.  To start the server for the first time type the command:

/opt/wildfire/bin/wildfire start

(If you want to autostart the server on boot, just include the previous line in the /etc/rc.local file.  There maybe a better way of doing this, I just don't know it)

Once the server has started open a webbrowser and goto http://<your server>:9090

Follow the wizard for installation, for ease of installation, use the embedded database.  Mysql works as well, however you must first configure SME to listen for local connections, this can be done by issuing the following:

config setprop mysqld LocalNetworkingOnly no
signal-event post-upgrade
signal-event reboot

Create you Admin account using the wizard and login.  Thats it.  You now have a working XMPP (Jabber) Server.

[dswillia]

Part 2:  Automagicly creating user accounts

There are a couple different ways to do this, Wildfire supports LDAP connections, however as of SME version 6.0 the the LDAP database did not support authentication so I do not believe this is an option.  That being said if I am wrong or it has changed in 7.x please let me know.

The second way of doing it by using the pop3 auth code in the wildfire.xml file.  This will create a user on the wildfire server whenever a user with a local email account logs into the server.  To accomplish this you need to edit the wildfire.xml file:

pico /opt/wildfire/conf/wildfire.xml

This first thing you will need to do is create a new admin account, the wildfire server auto creates one and this causes a problem when using pop3 auth.  To create a new user account find the line in the xml file that says:

<--  <authorizedUsernames></authorizedUsernames> -->

Change this to:

<authorizedUsernames>USERNAME</authorizedUsernames>[/b]

Insert an active account that you want to have admin rights in the USERNAME area.  This account must exist on your server.

Now, we add the pop3 auth code, goto bottom of the xml file to where you see: (approx Line 70)

 <!-- End example LDAP settings -->

Insert the following after the above line:

<!-- Example POP3 Authentication-->
  <provider>
   <auth>
<className>org.jivesoftware.wildfire.auth.POP3AuthProvider</className>
    </auth>
    <user>
<className>org.jivesoftware.wildfire.user.POP3UserProvider</className>
    </user>
  </provider>
  <pop3>
    <host>Insert Host Here</host>
    <domain>your domain.com</domain>
    <authRequiresDomain>false</authRequiresDomain>
    <ssl>false</ssl>
  </pop3>
  <!-- End example POP3 Authentication-->

Once you have changed your host and domain, save the xml and restart the server.

/opt/wildfire/bin/wildfire stop
/opt/wildfire/bin/wildfire start

Now login to the admin interface http://servername:9090 with the user you specified.  If all is configured correctly you should be able to login.  If successful, any user that tries to sign in with a jabber client will automagicly get created a jabber user account.

[thelinuxfr]

Hi,

And for configuration of PyMSN and wildfire?
And l'install of SME 7?

Thx

[drlizau]

I'd recommend this as an easy to install jabber server.
If you are going to use it across the internet, then a few ports need opening. Forward ports 5222, 5223 and 5269 to localhost, and the port you chose for file transfer if needed.

If, as I did, you installed and configured remotely, then you will need to open 9090 UDP to use the admin web interface. Close this port when the job is done.

[drlizau]

I haven't found this to be a stable running jabber server with it refusing connections form some machines on the LAN. I'm following this up, but if I can't get it working reliably I will remove and replace it.

[brianr]

Any news on this? I am just looking for a jabber server for a customer, to run on an SME6.01 system.

What (Windoze) IM client are you using?

[drlizau]

It's still installed, and behaving itself. When it wouldn't behave, I would look at the logs and it would go properly again. Then I started leaving a machine logged on continuously and it has run properly although sometimes no one is logged on.
For Windows clients I use Psi.

[wifinetguy]

I've just installed Wildfire version 3.0.0 on SME 7RC3 and it seems to be working fine so far. Having a little problem with auto-registering users but for those already in the system, all is good so far. Just FYI...for what it's worth.

[Franco]

I installed 3.0 with mysql and asterisk integration, works as advertised!
Thanks!

[sebastian_sw]

I also installed Wildfire 3.0 and works fine.

Can someone point me how to start the service when the server reboots?

Many Thanks

Seb.-

[drlizau]

I don't remember what I have done, but from jivesoftware.org

If you would like to install Wildfire as a service, two scripts are provided in the bin/extra directory:
redhat-postinstall.sh -- automatically installs Wildfire as a service on Red Hat. It does so by creating a "jive" user and then copying the wildfired script to your init.d directory. This script must be run as root. Please see the comments in the script for additional information.
wildfired -- script to run Wildfire as a service. You must manually configure this script. See the comments in the script for additional details.

[sebastian_sw]

I don't remember what I have done, but from jivesoftware.org

If you would like to install Wildfire as a service, two scripts are provided in the bin/extra directory:
redhat-postinstall.sh -- automatically installs Wildfire as a service on Red Hat. It does so by creating a "jive" user and then copying the wildfired script to your init.d directory. This script must be run as root. Please see the comments in the script for additional information.
wildfired -- script to run Wildfire as a service. You must manually configure this script. See the comments in the script for additional details.

Tryed the Steps discribed in the scripts, but without luck, maybe im mistaken something.

What i done was:
1- ./redhat-postinstall.sh
2- chmod +x /opt/wildfire/bin/wildfire
3- cd /etc/rc6.d
4- ln -s ../init.d/wildfired $90wildfired

When reboot, the service never starts - any suggestions?

Thanks

Seb.-

[ldkeen]

3- cd /etc/rc6.d
4- ln -s ../init.d/wildfired $90wildfired

When reboot, the service never starts - any suggestions?

SMEServer starts in run level 7, so that command probably should be:

Code: [Select]

#cd /etc/rc7.d
#ln -s /etc/rc.d/init.d/wildfired S90wildfire
Note also that it should be a capital S in front of the symlink name NOT a $ .
Regards Lloyd

[william_syd]

From the SME developer manual....

Make sure you have a script that takes start/stop commands.

I don't use wildfire but from the post I gather that the script is titled wildfired.

Copy wildfired from the wildfire/bin/extra directory to /etc/rc.d/init.d/

This will be your starting point.

Code: [Select]

/etc/rc.d/init.d/wildfired

Modify /etc/rc.d/init.d/wildfired as per the instructions at the start of the script. Disregard the following part of those instructions-

Code: [Select]

# This script should be copied into /etc/init.d and linked into
# your default runlevel directory.
# You can find your default runlevel directory by typing:
# grep default /etc/inittab
#
# Link to the directory like follows
# cd /etc/rc<num>.d
# ln -s ../init.d/wildfired $90wildfired
#


then we give SME control over it

Code: [Select]

ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S90wildfired

we then need a database entry to determine if it should start or not

Code: [Select]

/sbin/e-smith/db configuration set wildfired service status enabled

then do the SME tango

Code: [Select]

/sbin/e-smith/signal-event console-save
/sbin/e-smith/signal-event post-upgrade

and finally reboot

Code: [Select]

/sbin/e-smith/signal-event reboot

See how that goes. I don't use it myself.

[jmarcosm]

I followed your instructions and @ when the system start, I can see service wilfire [ok] , but when i try to connect to the admin page, doesn´t work.

I observe when I start wilfire manually the following message:

Starting wildfire

no hup: se añade la salida a <<nohup.out>> (translation: the output is append  to <<nohup.out>>

If have to press the enter key to obtain again the prompt.
If I don´t press the enter key , wildfire never start!

What do you thinK?

Regards Marcos