In short-term archiving, you archive events from the production database to the history database. The production database is the main Data Exchange repository. The history database is an intermediate repository that contains the archived events and documents.

You define the source connection properties for the production database and the target connection properties for the history database. You set up the history database user access role and assign the role to users that can access the history database. You add the users to a security group. The history database user must have privileges to create tables, views, and synonyms.

Before you create the archive project and run the archive job, you run the seamless access script to create a seamless access layer that links the production database and the history database. After you run the archive job, you view the archived events on the

Archived Events

page of the Operation Console in the same way you view regular events. You can also assign viewing privileges in B2B Data Exchange to operators based on the policies in your organization. If the history database contains deleted event types, you cannot view the archived events regardless of the viewing privileges.

When you no longer require ongoing access to the archived events and documents, you can use the long term archiving method in Data Archive to archive events from the history database to the file archive. The file archive is a compressed file store that you can access only in Data Archive. Use the long term archiving method to improve performance of the history database and reduce loading time when you view archived events in the Operation Console.