[jdev] Integrating XMPP with enterprise applications

[Norman Rasmussen]

You have to make users of the rich internet client appear of users of
the component.  This is the easiest way - make the xmpp users have
xmpp server jid, and make the rich internet client users have a
different server jid.

You wouldn't be able to overlay both the main xmpp domain, and the
component domain and make it look like both sets of users were on the
same server - That's much harder - the easy way to do this is to make
one c2s connection per user to the xmpp server.

On 15/09/05, Raffaele Sena <raff at aromatic.org> wrote:
> 
> Thanks to everybody that answered the question.
> 
> I started looking at the component protocol but there are a couple of
> things I don't understand.
> 
> It is clear to me that if I send messages from a client to the component
> JID the component will get the message. But I didn't see anywhere in the
> component protocol how to make the component process all the messages the
> server get (that would be the way for me to forward some of those requests
> to my application server).
> 
> I think jabberd has a configuration option to make the component get some
> of the messages (a <bcc> tag) and I saw that with Jive a could write a
> plugin that can accomplish a similar effect. But is there a "standard" way
> to configure a component to do do what I need ?
> 
> Thanks!
> 
> -- Raffaele
> 
> 
> On Wed, 14 Sep 2005, Norman Rasmussen wrote:
> 
> > On 14/09/05, Raffaele Sena <raff at aromatic.org> wrote:
> > > What I would really like to do is have a single connection between the
> > > application server and the XMPP server and some state information in the
> > > application server for the connected clients. I thought that I could use the
> > > server-to-server protocol to talk between the application server and the
> > > XMPP server but there is no standard "server" library available (JSO seems
> > > to support have some support for s2s but there are no examples of how to use
> > > it).
> >
> > Why don't you make the application server connect to the xmpp server
> > as a jabber component?  It's pretty much give the same functionality
> > as s2s without all the dialback requirements.  That way you get a
> > lightweight single connection that can have several users behind it.
> > (and you get several good examples of how to go about coding it)
> >
> >
> 
> 


-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/