The following functionality is provided:
Archive/recall across architectures.
Data is altered according to architecture (for example: byte-swapping) when recalled (or copied) to a different architecture from the origin.
Automatic configuration.
Every effort is made to automatically generate configuration during the installation process or on first use of components, whichever is appropriate. This is extremely important for software that is distributed across multiple computers. By adhering to Software AG’s recommendations to use a single shared configuration file, installation and first use on each computer can automatically
populate the details of the latest computer into the configuration,
connect these details with all other computers previously installed and
allow you to administer all these components immediately from a single browser session.
Installation changes.
The installation now helps you, as recommended, to share a single configuration file across all computers where the product is to be installed. This allows you to first install on the computer where the configuration file resides in order to create the (or overlay an old) configuration file for first use. The installation for subsequent installs on additional computers allows you to reference the file thereby sharing and combining the configuration for all the computers that will collaborate.
In addition, by following the recommended installation you no longer have to introduce perspectives into the browser before you can administer the archiving computers, this is preconfigured for you.
Browser administration user interface.
All activities are administered online without needing batch-style submissions. This includes live display of all ongoing activities across the system. This is based on the latest System Management Hub (SMH 8) technology from Software AG.
Extractor in classic archive mode.
Classic archive mode means the data is removed from its origin and placed into the archive destination. You can optionally cause filtering of the information at the point of extraction.
Extractor in copy-only mode.
You can instruct the extractor to only copy the information, not to delete it. This may be useful if you wish to create subset test files for example.
Extractor in delete-only mode.
You can instruct the extractor to only delete the information, not to place it into the archive destination. This may be useful if you wish to discard unwanted data that has built up in files, that does not need to be archived.
Flat-file archive destination (a.k.a. The Vault).
The typical destination for archived data is flat-file since the volume of data built up over time can be extremely large.
Separation of archive destinations according to business rules.
You can define more than one archive vault so that different business areas can keep their archived data totally separate.
Adabas as an archive destination.
You can also archive to Adabas, you are not limited to archiving only to the vault.
Note:
This is not a managed archive in the same way as the vault is, it is
more a mechanism to split data from the origin Adabas into another Adabas.
Activity monitor.
The UI comes with an in-built activity monitor so from one browser session you can monitor all archiving activities in all computers (providing firewalls allow).
Automatic (unattended) operation.
You can set a schedule for when archive operations run so that you can run all archive operations, across many computers, without human intervention.
Pacing of archive operations.
You can set the minimum and maximum pace at which your archive operations are to run. If the minimum pace cannot be attained a warning is issued. If the maximum can be exceeded the operation is throttled back to stay at the pace you desire. This means you can have fine control over the resources both needed and consumed.
Recall.
Data previously archived can be recalled to a new or existing Adabas file, with controls for handling duplicate key values, ISNs etc.
Automatic expiry.
Archived data can be automatically discarded when it has been stored for a specified period of time (for example when it has been in the archive for 7 years).
History.
A history trail of all archive operations is kept and is visible in the user interface.
Search of the archive without having to recall information back to the origin.
Selective recall from the archive vault.
Note:
At the moment this will only recall a whole archive operation, not a
partial one.
Product demo.
The product comes equipped with a demo that is ready to run immediately. This is an even greater help in getting started quickly. The demo has been enhanced to contain newer extraction criteria so you should run it again to see how it differs from before.
