Chris
We got our internal ag server up and started on the jabber server.  I was able 
to snag one of our linux guys for a few days to configure the xml files but he 
didn't have enough time and is now on vacation.  He said before he left that he 
was very close.  I was wondering if you could make available your jabber.xml 
and muc.xml files so that I might finish setting it up.  Any help at this point 
would be greatly appreciated.  I could include our files if needed.

thanks

Paul


On Mar 8, 2008, at 2:34 AM, Christoph Willing wrote:



   On 08/03/2008, at 6:33 AM, Paul Mercer wrote:


      Chris
      I have been tasked to set up a private AG server to be used only within 
our organization.  The jabber server is the real question mark for me.  Are you 
recommendations below still valid?  Also have you seen any tutorials yet?


   Paul,

   We're currently using jabberd14-1.6.11 and mu-conference-0.7 as the jabber 
component for the APAG venue server. We've been running this way since 29th 
November without any problems - in fact I don't think any of our users are even 
aware of the change.

   I've made a Slackware binary package but since you're you're probably not 
using Slackware, here are the first steps in building from the source code. 
Firstly, download:
     http://www.vislab.uq.edu.au/ag3/distfiles/jabberd14-1.6.1.1.tar.gz
   and
     http://www.vislab.uq.edu.au/ag3/distfiles/mu-conference_0.7.tar.gz

   Unpack them somewhere convenient. Now cd into the mu-conference0.7 directory 
and apply the patch below (it removes a build dependency on mysql, which we're 
not using).Now cd into the src directory and run make.

   Then cd back into the jabber14-1.6.1.1 directory and run:
     ./configure --prefix=/usr --sysconfdir=/etc/jabberd localstatedir=/var
   and:
     make


   There are now some configuration files to take care of. Let me know if you 
get this far and I'll make them available somewhere to download, as well as an 
explanation of how they're used.

   Build dependencies will depend on your platform, however I had to first 
install libgpg-error libgcrypt gnutls libidn and libtasn1 libraries.

   Good luck.


   chris


   muc patch:
   --- src/Makefile.orig   2007-06-09 06:19:48.000000000 +1000
   +++ src/Makefile        2007-11-22 15:37:57.075581000 +1000
   @@ -1,8 +1,7 @@

    CC:=gcc
    CFLAGS:=$(CFLAGS) -O2 -Wall -I../../lib -I../include `pkg-config --cflags 
glib-2.0` -D_JCOMP -D_REENTRANT -DLIBIDN
   -#CFLAGS:=$(CFLAGS) -O2 -Wall -I../../lib -I../include `pkg-config --cflags 
glib-2.0` -D_JCOMP -D_REENTRANT -DLIBIDN -DHAVE_MYSQL
   -LIBS:=$(LIBS) -ljcomp -lm `pkg-config --libs glib-2.0` `pkg-config --libs 
gthread-2.0` -lexpat -lidn `mysql_config --libs`
   +LIBS:=$(LIBS) -ljcomp -lm `pkg-config --libs glib-2.0` `pkg-config --libs 
gthread-2.0` -lexpat -lidn
    LDFLAGS:=-L.

    # Debug/Experimental






      On Nov 25, 2007, at 6:00 PM, Christoph Willing wrote:



         On 26/11/2007, at 11:34 AM, Kivshar, Boris (Contractor) wrote:


            Hello All,

            I know this topic has been covered before but I was unable to find 
a solution anywhere…

            I know there are lots of jabber server software packages found at: 
http://www.jabber.org/software/servers.shtml
            But I’m wondering, has anyone come upon any guides/tutorials for 
any the above and how to configure them to work with AG3 specifically?
            Windows OS preferred but Linux is fine too!



         I've just been looking into this and have some working solutions but 
no tutorials yet. However as a quick summary - I have used both Debian & 
Slackware distros with:
         jabberd-1.4.3 and jabber-muc-0.6.0
         and
         jabberd14-1.6.11 and mu-conference-0.7

         Probably the latter combination will be a better long term bet.

         The jabberd component does the IM style stuff; mu-conference is what 
supports the chat rooms (AG venues).

         Basically, compile the jabber & muc components. Then configure them - 
thats what took me the most time. Each component has its own xml configuration 
file; they know about each other via an additional <s2s> section in jabber.xml. 
You'll also need to enable ssl on port 5223 in jabber.xml and provide a 
certificate location in there too (I used an AG server certificate I happened 
to have on hand which seems to work OK).


         Feel free to email me directly for specific details as you need them.


         chris



         Christoph Willing                       +61 7 3365 8350
         QCIF Access Grid Manager
         University of Queensland






      Paul Mercer
      Arctic Region Supercomputing Center
      907 450 8649






   Christoph Willing                       +61 7 3365 8350
   QCIF Access Grid Manager
   University of Queensland







   Paul Mercer
   Arctic Region Supercomputing Center
   907 450 8649




Reply via email to