Oracle® Beehive SOAP Web Services API Reference
Release 2 (2.0.1.7)
All Operations
Access Control
Assigned Role
Role Definition
Sensitivity
Address Book
AddressBook
GroupContact
PersonContact
ResourceContact
Calendar
BookableResource
Calendar
Meeting
MeetingSeries
Reminder
ReminderList
Community
Enterprise
Organization
Conferencing
Content Management
Document
ExternalArtifact
RemoteDocument
RemoteFolder
RemoteRepository
RemoteShare
Version
Directory
AllUsersGroup
DynamicGroup
External Person
Global Directory
Group
Organization User
Preference Profile
Preference Set
Principal
SystemActor
Discussions
Announcement
DiscussThisForum
DiscussionsDraft
DiscussionsMessage
Forum
Topic
Intelligent Collaboration
Expertise Management
ExpertiseConnection
ExpertiseUserScope
RelationshipConnection
Messaging
EmailMessage
Fax Message
Voice Message
Metadata and Relations
Bond
Category
CategoryTemplate
Label
LabelBundle
Link
Lock
Presence
Subscriptions
Subscription
SubscriptionList
Task Management
Utilities
Current User Utilities
Wiki
Wiki Page
Workspaces and Folders
Heterogeneous Folder
PersonalWorkspace
TeamWorkspace
TeamWorkspaceTemplate
Trash
TrashItem
All RepresentationsThe Presence category enables you to control Oracle Beehive's Presence Service, which detects and identifies the status of a user or resource, and then displays that status to other users and resources in one or more clients or applications. For more information, refer to "Presence Service" in the module "Oracle Beehive Services" in Oracle Beehive Concepts.
A presence is ...
A presence subscription is ...
A presence connection is ...
A contact method is ...
A roster is ...
The PresenceConnectionsLimit, a system property of event subscriptions, enables you to set the maximum number of presence connections a single client may establish through the BDK. Setting this property to 0 disables presence connection initiation.
If a particular user has public presence enabled (which it is by default), any user may see that particular user's presence without a subscription.
To enable public presence for a particular user, add the public presence pseudo-user to the roster of the user and set its subscription status to ALLOWED. The ID of the public presence pseudo-user is 0000:0000:user:693446B3D1A9443F74F37D9616DC5B12000030126208. Alternatively, you may enable public presence by removing the public presence pseudo-user from the roster of the user.
To disable public presence, set the subscription status of the public presence pseudo-user to BLOCK.
To add a user to the logged in user's roster, use the PUT method /comb/v1/d/my/roster/{id}, where {id} is the user to be added. Specify the subscription status (such as ALLOWED and BLOCKED) in the state request parameter.
To remove a user from a roster, use the DELETE method /comb/v1/d/my/roster/{id}.