Table of Contents

Search

  1. Preface
  2. Product Overview
  3. Security
  4. Applications
  5. Partner and Account Information
  6. Events
  7. Event Archiving
  8. User Policies
  9. Schedules
  10. B2B Data Exchange Administrative Tasks
  11. On-boarding Checklist Template
  12. System Properties
  13. Repository Management
  14. Document Management
  15. B2B Data Exchange Utilities
  16. Dashboard and Reports Management

Administrator Guide

Administrator Guide

Event Archiving Process with Data Archive

Event Archiving Process with Data Archive

Use Data Archive to define archive projects
,
schedule standalone and recurring archive jobs
, and browse archived events and documents
in
B2B Data Exchange
or Data Archive.
You can also archive documents that
B2B Data Exchange
passes by reference.
The archive process with Data Archive typically includes the following stages:
  1. Install and configure the
    B2B Data Exchange
    accelerator in Data Archive. The accelerator accesses the
    B2B Data Exchange
    repository and
    retrieves events
    based on the archive project settings that you define in Data Archive. For installation instructions, see the
    B2B Data Exchange
    Installation and Configuration Guide
    .
  2. Determine the locations of the source and target database. You must store the production database and history database on the same type of database. For example, you cannot archive events from an Oracle database to a Microsoft SQL Server database.
  3. Configure the connections to the source and target archive locations. Define general connection properties and database-specific properties based on the archive method that you want to use. You configure the source and target connection properties to archive documents that are passed by reference to the
    B2B Data Exchange
    document store.
  4. Set up user roles and configure secured access. Create access roles and assign security groups to the source
    and target
    archive locations to determine which users can run archive jobs
    and access archived events
    in Data Archive. You must create an access role even for a single user.
    You do not need to create a security group for the target connection.
  5. Configure seamless access to the history database. For short-term archiving, create a seamless access layer to link the production database and the history database to view the archived events in the Operation Console.
  6. Create the file archive folder. For long-term archiving, create the file archive user, and run a standalone archive job to create the file archive folder.
  7. Create and publish the archive project. In the archive project, you define the parameters according to which you want the archive job to
    archive
    the events
    and documents
    from the source
    archive
    location. For example, you can define to
    archive
    events of a specific
    type, status, or partner
    . Although you can only
    archive
    whole event hierarchies, some archive parameters only apply to the root event in the hierarchy.
  8. Schedule and run the archive job. The archive job uses the parameters from the archive job that you create and
    moves
    the events and documents from the source location
    to the target location
    . You can schedule a single immediate job or a recurring job.
    Each archive scenario requires additional jobs that you run after the main archive job.
  9. View the archived events and documents. For short-term archiving, use the
    Archived Events
    page of the Operation Console to view events that you archive to the history database. For long term archiving, use the Data Discovery portal in Data Archive to browse and search for events that you archive to the file archive.
  10. Periodically, rebuild the indexes of the
    B2B Data Exchange
    repository schema. You can use the
    ALTER INDEX <index name> REBUILD ONLINE
    syntax.

0 COMMENTS

We’d like to hear from you!