Fwd: [AG-TECH] Jabber Server Install [nclassified]
Paul Mercer
mercer at arsc.edu
Mon May 12 11:17:55 CDT 2008
Lassi
I'm forwarding this to you as it has attached all the config files
needed to set up your own jabber server. Chris sent me these files
which only need to be edited to include your local information. They
saved us a lot of time. We are using jabberd14-1.6.11 and mu-
conference-0.7 with our internal AG server.
Good luck.
Paul
Begin forwarded message:
> From: Christoph Willing <willing at vislab.uq.edu.au>
> Date: March 26, 2008 7:04:51 PM AKDT
> To: Paul Mercer <mercer at arsc.edu>
> Subject: Re: [AG-TECH] Jabber Server Install [nclassified]
>
>
> On 27/03/2008, at 8:22 AM, Paul Mercer wrote:
>
>> 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.
>
> Paul,
>
> Sorry for the delay - I've been tied up with other things and the
> jabber stuff is still a bit messy so I knew it would take some time
> to sort out and explain the files & issues.
>
> I've attached the jabber.xml and muc.xml files I'm using at the
> moment. Just change all instances of vislab.uq.edu.au to something
> else that makes sense for your domain. Only
> seivers.vislab.uq.edu.au is an actual machine so change all of
> that. However things like sessions.vislab.uq.edu.au,
> conference.vislab.uq.edu.au should keep the "sessions" or
> "conference" part of the name i.e. should now be
> sessions.your.domain and conference.your.domain respectively.
>
> In jabber.xml, you'll find a reference to a ssl.pem file in the tls
> section. You'll need to provide such a file. I made mine based on:
> http://jabberd.jabberstudio.org/2/docs/app_sslkey.html
> Basically, do:
> openssl req -new -x509 -newkey rsa:1024 -days 3650 -keyout
> privkey.pem -out ssl.pem
> openssl rsa -in privkey.pem -out privkey.pem
> cat privkey.pem >> ssl.pem
> Then copy ssl.pem into /etc/jabberd/ssl.pem (or wherever you've
> specified in jabber.xml).
>
> I think I also used an AG certificate for a while while testing and
> it seemed to work OK, although you'd have to beware of expiry
> times. The AG certs are generally good for 1 year whereas in the
> roll your own version above, I've set it to be valid for 10 years
>
>
> I start my jabber/muc at startup from an rc script which I've also
> attached - you'll need to modify it according to the Linux
> distribution you're running and how you want to things generally.
> You can see that it depends on the existence of a functions file
> and a jabber.cfg file, both of which are expected to be in the /etc/
> jabberd directory - I've attached my versions of them too. You'll
> have to at least change the JABBER_HOSTNAME in jabber.cfg
>
>
> I think thats all of it - let me know if you find something's still
> missing. Good luck!
>
>
> chris
>
>
>
>> 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.
>
>
 
>
>
  
>
>
> Christoph Willing +61 7 3365 8350
> QCIF Access Grid Manager
> University of Queensland
>
>
>
Paul Mercer
Arctic Region Supercomputing Center
907 450 8649
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jabber.xml
Type: text/xml
Size: 51989 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: muc.xml
Type: text/xml
Size: 2917 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0001.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jabberd_rc
Type: application/octet-stream
Size: 2793 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: functions
Type: application/octet-stream
Size: 854 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0001.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0004.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jabber.cfg
Type: application/octet-stream
Size: 702 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0002.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20080512/89626452/attachment-0005.htm>
More information about the ag-tech
mailing list