|Oracle® Fusion Middleware Administrator's Guide for Oracle Business Data Synchronization Server
11g Release 2 (184.108.40.206.0)
Part Number E24630-03
|PDF · Mobi · ePub|
The process of determining information about a given attendee associated with a calendar meeting in the system where the meeting resides. This resolution is required because user identifiers are not guaranteed to be the same across the systems.
Business Process Execution Language. An XML-based markup language for composing a set of discrete web services into an end-to-end process flow.
A component within the BDSS architecture that sends data to, and retrieves data from, the PIM servers.
The name for a set of configurations for a connector that serve a specific set of PIM server instances.
A representation of a specific installation of a connector. The instance can be a single connector, or it can represent a group of connectors that are accessed from the same load-balanced URI (Universal Resource Identifier).
A record extracted record from a PIM server whose last update was done by a BDSS- initiated change from a prior Synchronization Session (as opposed to a change made by an end user).
For the purposes of this document, a federated PIM is a PIM that stores a single copy of a record and provides one or more users visibility and access to the record. For example, Siebel can be considered a federated PIM because Siebel allows multiple users to share a single Contact, Task or Calendar record. For example, if a calendar meeting (MeetingA) is organized by Siebel UserA with an attendee Siebel UserB, then both UserA and UserB have visibility and access to a single instance of the calendar record. See also non-federated PIM.
An abstract representation of a domain. Each PIM connector has a set of connector domains that are mapped to a central set of HUB domains.
A mapping of PIM server users to other PIM server users. The Hub user does not represent an actual user; it is a key value that represents a collection of PIM server users. There is a one-to-one relationship such that any PIM server can only associate one user to a Hub user; however, an arbitrary number of PIM servers or PIM users can be mapped into the collection. See also Hub User ID.
Hub User ID
A calendar record containing properties that describe the records' recurrence pattern.
Indicates a conceptual mapping of ICAL and PIM fields that have the same semantics, but may have different names. ICalendar (ICAL) RFC 2445 defines a fairly complete and generic set of fields. Because each PIM also has a set of fields defined for a calendar record, its fields may not have the same name as their ICAL counterparts. For example, while the ICAL
LOCATION field would naturally map to the Exchange unindexed field called
Location, the ICAL
DTSTART field would map to the Microsoft Exchange calendar
For the purposes of this document, a non-federated PIM is a PIM that stores individual copies of related records. For example, Microsoft Exchange is a non-federated PIM because each user has their own copy of Contact, Task and Calendar records. If a calendar meeting (Meeting A) is organized by Exchange User A with an attendee Exchange User B, then both User A and User B get a separate, but related, copy of the calendar record. Exchange relates the two copies by ensuring both have the same meeting identifier (in terms of ICalendar, it is the UID). See also federated PIM.
PIM Server Endpoint
A connector-defined value used with configuration metadata to route the synchronization of a given user to a particular cluster of connectors.
PIM User ID
An identifier used by a connector for uniquely identifying a PIM user on the PIM server with which the connector communicates. The PIM User ID can be anything that the connector requires, but it is typically a user account name such as SBROWN or a SMTP e-mail address such as email@example.com.
A calendar occurrence that has undergone a change that applies only to the occurrence and not the entire recurrence series.
Used in development scenarios, reflective synchronization refers to a scenario in which a single PIM server is configured to have 2 connector entries in the BDSS system, so that data can be synchronized from one account in the PIM Server to another account in the server.
An external component that triggers the Dispatcher at set time intervals.
Connector-provided data used by the Engine to track a user's domain records that have been exported successfully from a PIM server.