you can export the configuration without stopping services since mcf will
lock the operation. that command  just  exports the connection configs and
jobs.

shinichiro abe


2015年9月30日水曜日、Tomoko Uchida<[email protected]>さんは書きました:

> Thank you for the reply, I've missed it. I'll try that.
>
> And excuse me, another question about operational guidelines:
> I can safely import configurations to running production environments w/o
> stopping the service ?
> Or I have to stop the service and / or cleanup all the current
> configurations, and also data, before importing ?
>
> If there are important notices for safe import / export operations,
> comments are much appreciated.
>
> Thank you,
> Tomoko
>
> 2015-09-30 17:54 GMT+09:00 Shinichiro Abe <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>>:
>
>> Hi,
>>
>> Please see Control via Commands in
>> https://manifoldcf.apache.org/release/trunk/en_US/how-to-build-and-deploy.html
>> org.apache.manifoldcf.crawler.ExportConfiguration
>> org.apache.manifoldcf.crawler.ImportConfiguration
>>
>> Regards,
>> Shinichiro Abe
>>
>> > 2015/09/30 17:48、Tomoko Uchida <[email protected]
>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> のメール:
>> >
>> > Hello all,
>> >
>> > Are there any way to  import / export  MCF settings for repository
>> connections, outputs connections, jobs, etc. from / to the database?
>> >
>> > I (my customer) have development/staging/production MCF deployments
>> with many jobs.
>> > So it would be helpful if we can "copy" various MCF settings in dev to
>> staging/production MCFs without re-register very same information via Web
>> UI.
>> >
>> > I think MCF (currently) does not provide such features, but could
>> anyone suggest how to properly handle multiple MCF environments or
>> deployments.
>> >
>> > We use MCF 2.1 and PostgreSQL for the storage.
>> > Sorry if I've missed something.
>> >
>> > Thank you,
>> > Tomoko
>> >
>> >
>>
>>
>

Reply via email to