Installation guide

Jabber XCP Server Installation Guide Jabber XCP Glossary Page 41
Beta Version Only
optimize stanza traffic between Jabber XCP servers, thus providing a higher degree of
scalability for large numbers of users. This feature allows a single stanza to be sent to
multiple recipients rather than one stanza being sent per recipient, as was the case in
previous versions of the server.
Text Conferencing (TC)
Text Conferencing allows multiple users to communicate with each other in online
chat rooms. The TC component that is set up by default during installation is
configured to allow basic conferencing functionality using ad-hoc rooms. You can
configure many other TC features, including persistent conference rooms, which
remain on your server until they are deleted.
vCard
vCards automate the exchange of personal information typically found on a
traditional business card.
Wait List Service
The Wait List Service component allows Jabber users to place a contact on a waiting
list by specifying information about the contact (such as a telephone number or an
email address) and to be notified when that contact creates an IM account. (For more
information, see XEP-130.)
Web command processor
The Web command processor, configured within a Connection Manager component,
handles HTTP requests, and translates and transfers data between clients and the
Jabber XCP core router over the Web. This command processor is installed with the
Web Services component, which is included in the Jabber XCP developer extensions
installation package.
Web Services
The Web Services component provides the capability for customers to create
applications and custom components that use Messaging, Router/Presence, and
InfoBroker services. The Web Services component is included in the developer
extensions installation package.
Web services handler
The Web services handler is configured within a Web command processor. It allows
users to access XCP services using SOAP over HTTP, and configures a Uniform
Resource Indicator (URI) path, over which messages are sent from Web Services
applications to the handler via HTTP. The handler performs HTTP basic
authentication and, if passed, forwards the message to the Web Services component.