Introduction to Oracle Business Data Synchronization Server 1-3
To test Hub synchronization:
1.
Create a second connector. Differentiate this connector by giving a name such as Exchange2007_2.
2.
Create a PIM server instance and a connector instance
for this connector.
3.
Configure the Pim Transport Implementation Class and Extract Response Batch Size parameters for each Exchange 2007 Connector whereby the value for the
Profile is the name of the connector as it appears in the NAME column of the CONNECTORS
table. For example, suppose you have deployed a single Exchange 2007 Connector and want to use the single instance to synchronize two Exchange
2007 users that are mapped to a single
Hub user . Further, assume that
Exchange2007 and Exchange2007_2 are in the NAME column of the CONNECTORS table and both have a SERVER_TYPE_CD corresponding to the
Exchange2007 LOV value.
4.
Add the following four rows to the PROFILES table using the setProfileParameter of the ProfileRuntimeInfo MBean. For more
information, see Section 4.8, Managing Profiles.
5. Create a
connector user for each of the connectors.
Table 1–1 Adding Profiles to Test Synchronization
Profile Section
Parameter Value
Exchange2007 Hub Transport
Pim Transport Implementation
Class oracle.bdss.connectors.exch
ange2007 pimtransport.PimTransport
Adapter Exchange2007
Hub Transport Extract Response
Batch Size 100000
Exchange2007_2 Hub Transport
Pim Transport Implementation
Class oracle.bdss.connectors.exch
ange2007.pimtransport.Pim TransportAdapter
Exchange2007_2 Hub Transport
Extract Response Batch Size
100000
Note: You must use different Exchange users. That is, you cannot
map johnexchange.com to johnexchange.com.
1-4 Administrators Guide for Oracle Business Data Synchronization Server
2
Understanding the BDSS Architecture 2-1
2
Understanding the BDSS Architecture
This chapter provides a high-level description of the Oracle Business Data Synchronization Server architecture.
This chapter includes the following topics:
■
Overview of the Oracle Business Data Synchronization Server Architecture
■
Overview of Connectors
2.1 Overview of the Oracle Business Data Synchronization Server Architecture
Oracle Business Data Synchronization Server BDSS utilizes a hub-and-spoke architecture that enables synchronization between PIM servers. The hub provides the
core synchronization functions and is PIM-server agnostic, enabling connections for any type of PIM server. Connectors, which send data to and retrieve data from the PIM
servers, comprise the spokes of the system.
Figure 2–1 illustrates an example of this
architecture, one that results in fewer connectors between PIM servers. Even in multiserver topologies, this simpler synchronization topology addresses the potential
issue of data feedback looping between the PIM servers.
Figure 2–1 An Example of the BDSS Hub-and-Spoke Architecture
2.1.1 BDSS Components
BDSS consists of the following two main components:
Note: For Oracle Fusion Middleware 11g release 1, BDSS ships with
support for Microsoft Exchange.
2-2 Administrators Guide for Oracle Business Data Synchronization Server
■
Hub
■
Connectors
2.1.1.1 Hub
The Hub, which orchestrates the synchronization of data for the system, includes the following subsystems illustrated in
Figure 2–2 :
■
Dispatcher
■
Engine
Figure 2–2 The Subsystems of the Hub
Dispatcher The Dispatcher first reads the set of users that it must send to the Engine and verifies
that users on the list are available for synchronization. After it is called, the Dispatcher process divides the entire set of users for synchronization into batches and calls the
Engine component. This subdivision of the user list allows for improved scalability of the system, as several Engine components can be made available. Dispatcher calls can
be balanced across the available Engine components as well.
Scheduler An external scheduler runs the Dispatcher at set time intervals. BDSS does not ship
with a scheduler. You can use any scheduling service, such as the Windows scheduler service or the Oracle Enterprise Manager scheduler.
Engine The Engine receives the list of users from the Dispatcher and synchronizes each of
these users at the same time. The Engine contacts each of the connectors to receive from the PIM servers a set of records that have changed for the user. The extraction
Note: The Dispatcher does not send users to the Engine when those
users are currently undergoing synchronization.
Note: Although Oracle suggests a default interval of 5 minutes, you
can select a scheduling interval that provides performance and scalability to suit the environment.
