Securing the Web Services Exposed by the Hub
8.1 Overview of Data Transformation
To enable the exchange of information between different types of PIM servers, the Hub defines a schema representation for each connector domain type in a schema XSD file. The data that is extracted from the PIM servers and returned to the Hub is transformed into the format defined by the Hub schema. Connectors transform the data into Hub XML format and also into the format of the PIM server for both inbound and outbound transactions. For every inbound record extracted, the connector must convert it from the native PIM API format to an XML message that conforms to a PIM XML schema defined for the connector domain. After the connector constructs the PIM XML message, it then uses XSLT to transform the message into a Hub XML message. This message conforms to a provided Hub XML schema. To enable data to map between the Hub domain and the connector domain, a connector’s Transformer component includes the schemas for both the Hub and connector domains and also XSLT documents. As described in Appendix D, Connector API, an UpsertRecord is a representation of a Hub record that flows between the Hub and connectors. This data structure includes a member called the hubRecordData, which contains the XML representation of the Hub record. Because the Hub record’s XML must conform to the XSD for the Hub domain, connector developers must create the following: ■ An XSD for a corresponding connector domain that maps to the Hub domain ■ An XSL definition for transforming the Hub XML representation of the record to the PIM XML representation of the record ■ An XSL definition for transforming the PIM XML representation of the record to the Hub XML representation of the record During extractions from the PIM server, a connector must ensure that each extracted record is first converted into a PIM XML message. It then uses the XSLT to convert the message from PIM XML to Hub XML. For record events pushed to the PIM server that is, Create and Update operations, the connector uses XLST to convert the Hub XML record to a PIM XML record before writing to the PIM server.Parts
» Oracle Fusion Middleware Online Documentation Library
» What Is Oracle Business Data Synchronization Server?
» Configuring the Exchange 2007 Connector to Test Domain Synchronization
» BDSS Components Overview of the Oracle Business Data Synchronization Server Architecture
» Hub Transport Transformer PIM Transport
» How the Connector Components Manage Domain Data During Synchronization
» Error Messages Overview of Connectors
» Prerequisites Overview of Installation
» Prerequisites for Deploying the Hub Components
» Installing Java Required Files
» Overview of Installing and Configuring BDSS Select Start.
» Extending the Domain with the BDSS Templates
» Adding Security Credentials Oracle Fusion Middleware Online Documentation Library
» Click Create Key. The Create Key dialog appears.
» Setting SSL Oracle Fusion Middleware Online Documentation Library
» Configuring the Exchange 2007 Connector for Record Transformation
» Configuring the Exchange 2007 Connector to the Active Directory Service
» Configuring Exchange 2007 Connector to Use the Auto Discovery Service
» Configuring the Dispatcher Postinstallation Configuration
» Configuring the Engine Configuring PIM Server Instances Using MBeans
» Select Application Deployment. Managing BDSS Components Using MBeans
» Select System MBean Browser from the list
» Accessing MBeans through JConsole
» To invoke operations: Managing BDSS Components Using MBeans
» Select the Operations node in the tree. All of the operations appear as buttons
» Update the parameter fields as needed for an operation.
» Click the operation button to invoke the operation.
» Expand the Operations node in the tree. The operation nodes appear.
» Select an operation in the tree to display its MBeanOperationInfo and
» Update the MBeanOperationInfo as needed.
» Click the button for the operation to invoke the operation.
» Specifying the Synchronization Direction
» Select the showConnectorDetails operation.
» Adding and Updating Connectors
» Select the updatePimServerInstance operation. Specify the parameters listed in
» Deleting a PIM Server Instance
» Select the updateConnectorInstance operation.
» Specify the parameters listed in
» Deleting a Connector Instance
» Creating a Domain for a Connector
» Setting the Synchronization Levels for a User’s Domains
» Set the updateUserSyncEnablementFlag. Click Invoke.
» Updating a Profile Click Invoke.
» Select the setProfileParameter operation.
» Enter the name of the section.
» Update the parameters as needed.
» Deleting a Parameter from a Profile
» Click Invoke. Managing Profile Parameters
» Creating Connector Configuration Profiles Configuring the FtsKeyFields Profile
» Overview of Exchange 2007 Connector Configuration
» Configuring the Microsoft Exchange 2007 Connector for Data Exchange
» Configuring Record Transformation for the Exchange 2007 Connector
» Configuring the Microsoft Exchange 2007 Connector’s PIM Transport Component
» Configuring Contact Synchronization Configuring Domain Synchronization
» Configuring Task Synchronization Configuring Domain Synchronization
» Configuring Calendar Synchronization Configuring Domain Synchronization
» Configuring Data Filtering Oracle Fusion Middleware Online Documentation Library
» Configuring the Microsoft Exchange 2007 Connector to Use Active Directory
» Configuring Event Receiving for the Exchange 2007 Connector
» Overview of Communication Security
» Securing the Web Services Exposed by the Hub
» Overview of Data Transformation
» Schema Data Types About Domain Schemas
» Hub Schema Documents About Domain Schemas
» Data Model Incompatibility Differing Data Type Facets List Transformations
» Record Collisions Data Side Effects Caused by Synchronization
» Transforming Calendar Records Overview of Calendar Synchronization Support
» Transformations Through Secondary Translation
» Translations Through Java-Based Connectors
» Supporting Calendar Synchronization in Hub Schema
» Creating Custom Calendar Fields
» Extracts all records from the PIM store belonging to a domain for the given
» Any records in the same PIM Domain Target that are not part of the domain
Show more