Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Begin
  4. Pre-Installation Tasks
  5. B2B Data Exchange Installation
  6. Post-Installation Tasks
  7. Installing the Partners Portal on Non-B2B Data Exchange Nodes
  8. Upgrading B2B Data Exchange
  9. Starting and Stopping B2B Data Exchange
  10. Optional B2B Data Exchange Configuration
  11. Migrating OEM Managed File Transfer Endpoint
  12. Installing and Configuring the B2B Data Exchange Accelerator for Data Archive
  13. Uninstallation

Installation and Configuration Guide

Installation and Configuration Guide

Limitations

Limitations

The following limitations apply to the Data Archive Accelerator.
  • By-reference document are only moved from the document store if the archive job is configured with the
    Archive and Purge
    option. With the
    Archive Only
    option, the documents reamain in the document store, and are not copied to the history database or the staging area for inclusion in the File Archive.
  • The document store is moved synchronously with the archive task. The property
    Move Attachments in Synchronous Mode
    has no meaning for
    B2B Data Exchange
    repository archive jobs.
  • ·If the document store is moved, then the property
    Source / Staging Attachment Location
    for the source connection must also be updated.
  • Running an archive job with the
    Archive Only
    is not supported, as this can lead to duplicate events in the history database. It might cause the
    B2B Data Exchange
    Operations Console Archived Events view to be unable to show the event details.
  • If the program
    Create Indexes
    is run on the history database, then the archive job might end in an error state. The program
    Create Indexes
    adds uniqueness constraints to simulate indexed primary keys which would causes the error.
  • If the
    drop target indexes
    property is selected for a target connection, then the program
    create indexes
    must be run after each archive job.
  • If you use Oracle databases, the history database user must be able to create tables, views, and synonyms. The user must have the following privileges:
    CONNECT
    ,
    RESOURCE
    ,
    CREATE VIEW
    , and
    CREATE SYNONYM
    .

0 COMMENTS

We’d like to hear from you!