[Anonymous]

Hi,

we have a question regarding the way that MigrationToolPlugins work. According to the description on the Developer Network (https://developers.exlibrisgroup.com/rosetta/sdk/plugins/MigrationTool) a MigrationToolPlugin expects at least one file and an output directory into which the result is to be written. Rosetta then calls up the script and monitors the output directory until a result is available.
The question at hand is: how long does Rosetta monitor the directory for? Is there a configurable timeout after which the monitoring process can be stopped? ZBW is currently developing a new migration plugin and would like to know if such a method exists to improve the process.
In help is greatly appreciated!

Thanks in advance,
ML

[Anonymous]

Hi,

Currently there is no timeout – Rosetta will wait for the transaction to complete and only then access the output directory. Timeouts, where needed, can be implemented within the plugin itself.

Opher

[Anonymous]

Hi Opher,

when does Rosetta know that the transaction completes? Does it look for a special exitcode?
Our plugin exits with an exitcode=0 on success and with any other exitcode on failure. We use it as Migration Plugin in a Preservation Plan. On migration failure it is possible to skip the IEs but they keep locked with the message:
“Currently Adding/Updating Representation By: SYSTEM”.

So does Rosetta wait for a special exitcode on failure? Is Rosetta otherwise still waiting for the plugin? Or is the plugin not responsible anymore, when we skipped the failed IEs?
thx
Konstantin

[Anonymous]

Hi Konstantin,
The plugin behavior you describe is correct; the problem appears to be elsewhere within the application. Can you please open a support case on this (this seems related to your closed case 00545031)?
Thanks,
Opher

[Author]

Posts