Installation guide

Jabber XCP Server Installation Guide Jabber XCP Glossary Page 38
Beta Version Only
Jabber entity
A Jabber entity is any separate and distinct item that has a Jabber ID. Jabber entities
include Jabber users, Jabber XCP servers, gateways, and services.
Jabber ID
A Jabber ID (JID) is used both externally and internally to express ownership or
routing information. Jabber IDs are formed of a domain, node, and resource having
the following format: user@host/resource.
Jabberd Logger
The Jabberd Logger is listed under Plugins in the Router area on the Controller’s
main screen. The Jabberd Logger receives packets from the core router and then logs
these packets to syslog or stderr.
Jabber Directory Suite (JDS)
The Jabber Directory Suite component provides an interface between the Jabber XCP
server and version 3-compliant LDAP or Active Directory Services (ADS). It handles
authentication, and enables the retrieval of vCard information and the use of
Community Groups. If you prefer not to use JDS and LDAP, you can use the Jabber
User Directory for your user search directory.
Jabber Session Manager (JSM)
The Jabber Session Manager is listed under Plugins in the Router area on the
Controller’s main screen. It handles real-time messaging functionality, and contains
state information about every client that sends a packet through the core router.
Jabber User Directory (JUD)
The Jabber User Directory component provides a searchable user directory for all
users who register with the Jabber XCP server. The JUD requires a Jabber-supported
database for user searches. (The JUD is commonly used for a user search directory
when JDS with LDAP is not being used.)
Jabber XCP server
The Jabber XCP server is the software that connects and communicates with other
Jabber clients and servers. All communications for a client are directed to the server
and then passed to the client.
Java LaunchBroker
The Java LaunchBroker component (previously called the Java External Command
Interface (JECI)) performs the same function as the LaunchBroker component, but
allows custom commands to be written in Java. As with LaunchBroker, these
commands must comply with XEP-50: Ad-Hoc Commands.