Table of Contents
Advertisement
4. Click Reset to revert to default system specified values.
User intervention for archiving
During some instances, the automatic archiver schedule might cease to work due
to various reasons. In such instances, you can manually archive the required data.
Following sections details the process to manually archive the data.
Initiating the archiver task to run from console
As WebSphere Partner Gateway administrator, you can initiate the archiver task
from the console for immediate execution. This initiation will be irrespective of the
scheduled tasks.
Here are the steps:
1. Navigate to Hub Admin > Hub Configuration > Archiver > Archiver
2. The server starts to execute the task. If the Copy option is selected while
Stopping a running archiver task
Here are the steps to abort a running archiver task:
1. Navigate to Hub Admin > Hub Configuration > Archiver > Archiver
2. Click Stop to abort the task.
3. Click Yes when you get a prompt to confirm your operation. The status will be
4. The server stops the task completely and updates the status in the report tables
5. The scheduler will schedule the archiver task for the next execution and the
v View Raw Message, click to view the raw message details of a particular
record
v Sending Partner, click on the partner name to view the complete partner
profile
v Package
v Protocol
v Document Type
v Subvolume
v Certificate name, click on the certificate name to view the certificate details.
Configuration and click Run Now.
Note: If the task is already running, Run Now link will be disabled.
configuring, the data gets copied to the specified location.
Configuration. The page lists the existing archiver task with the status as
'Running'.
displayed as 'Stopping'.
in the database. It also publishes the event to schedule the next task.
status will be updated to 'Scheduled'.
Note: If you try to stop the running task, it is possible that the data will be
archived and/or purged partially. You will not be able to roll back the
operation. As a result, the database tables may have an inconsistent set of data
for the period before the cutoff date that was specified during the purge
operation. The same will be depicted on the console too. These discrepancies
137
Chapter 13. Archiving
Advertisement
Table of Contents
