Archiver task (e.g., Export) stops running when standalone Archiver app is closed
(Doc ID 2637940.1)
Last updated on SEPTEMBER 16, 2022
Applies to:
Oracle WebCenter Content - Version 11.1.1.8.0 and laterInformation in this document applies to any platform.
Symptoms
Opened the standalone Archiver application in <domain>/ucm/cs/bin directory. Ran an export job and closed the Archiver application. The export had stopped as no more files were created in the archives directory (e.g., <domain>/ucm/cs/archives/<Archive>). Noticed this for imports as well. The standalone application Repository Manager can be closed after starting rebuilds, so it was expected that the standalone Archiver behave the same (e.g., same as the applet).
Is it expected for the standalone Archiver application to behave the same as Archiver applet like Repository Manager as mentioned in the below online documentation?
You can run Content Server administration Java applications in standalone mode from the computer where a Content Server instance is deployed. Some of
the applications are the same as the applets accessed using a web browser, such as Configuration Manager and Repository Manager. Some utilities can be
run only in standalone mode, such as System Properties and Batch Loader. The method required to start these programs differs slightly between Windows and
UNIX installations.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |