Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. Cluster Merge Rules
  13. Forced Link and Unlink
  14. System Backup and Restore
  15. Batch Utilities

Restrictions

Restrictions

Siebel Restrictions
  • There must be one primary BC per IO.
  • An IO may not include any secondary BCs.
  • Run-Time Events do not capture batch updates to BCs, leading to a possible loss of synchronization.
  • Run-Time Events only trap data changes made by components. Changes made in the Data Manager level will not trigger Run-Time events.
  • The Siebel HTTP Transport service does not close its connection to the XS Server until the client (Siebel Application user) logs off their Siebel session.
MDM-RE Restrictions
Transaction Sequence Numbers are generated in the order of XML message receipt (necessary due to the lack of Siebel facilities to generate unique sequence numbers).
  • Only one XS Server can be defined to accept XML messages. The use of multiple servers will result in the allocation of duplicate transaction sequence numbers.
  • The maximum IDT record length in the NSA Transaction Table is limited by DBMS limits on the size of a binary column.
  • UDB Unicode is not currently supported. Only the ASCII subset of UTF-8 can be loaded.

0 COMMENTS

We’d like to hear from you!