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 Workspaces and Folders category enables you to control Oracle Beehive's Workspace Service. This service is responsible for consolidating and exposing, in a single location, the collaborative functionality provided by the other Oracle Beehive services.
Refer to the module "Oracle Beehive Workspace Concepts" in Oracle Beehive Concepts for more information.
Oracle Beehive has two kinds of workspaces: team workspaces and personal workspaces. A personal workspace contains a user's own resources such as his or her calendar and inbox. A personal workspace exists for each user. Unlike a team workspace, it cannot be created or deleted outside user creation or deletion.
The following topics are covered:
The workspace object contains the URI of the workspace's logo, logoURI, which you may set through the BDK and other Oracle Beehive user interfaces. If the logo is stored as a workspace artifact, the URI is a URN with the identifier of the logo artifact (for example, urn:120E:486C:adoc:2BA76E50A4FC4974E040578CBC010F900000000000EF). The URN is a reference to an artifact of type Document. To retrieve this document, call the adoc resource with this identifier without the urn prefix. This document is stored in the public folder of the team workspace. This enables other team workspaces whose directorylisted flag set to y to display the logo to non-participants.
If the logo is stored outside the Oracle Beehive system, the URI is a regular URL that refers to an image (for example, http://myserver.com/mypages/mylogo.jpg).
To add participants to a team workspace, including during creation of a team workspace, specify the participants in the participants member (of type workspaceParticipantListUpdater) in teamWorkspaceUpdater.
The following steps outline how to program a simple workspace BDK client that can create a team workspace:
/my/workspace./my/teamworkspaces./my/user./ttws/list/?parent=<EID of parent of the user object>.TeamWorkspaceCreator (either in JSON or XML format):
name property.Specify the team workspace template you want to use in the templateInstantiator property.
Note: If you do not specify a template, a team workspace is created with the default template.
TeamWorkspaceUpdater and attach it to your TeamWorkspaceCreator. Optionally set the Description property in the TeamWorkspaceUpdater.TeamWorkspaceCreator JSON or XML to /wstm.