Just some clarifications
- you mention "Changing Server Settings" but then you ask about tasks. Which is it? If it is indeed about the server then you can export 1 task, any task and use the repctl option include_server_settings & task (check out: repctl -d \Replicate\data exportrepository ? ) or you omit the task= option exporting all which always has server settings. Next I would recommend parsing the JSON and removing the 'tasks' and 'databases' sections, just leaving the various server settings. Modify what you need and import just the server settings and not replacing all tasks and databases.
- "export all the tasks in separate JSON files" - not directly. You'll need to either requests a a gettasklist first, and then request exportrepository task= for each of them, or you must parse the overall export. when parsing the overall export, you may want to decide whether to separate in just the bare-bones tasks and separate barebones end-points or tasks with their endpoints. Extracting tasks with their endpoint is handy, but if an endpoint is in use by multiple tasks and that endpoint needs changed then you risk importing a tasks with a stale endpoint definition at some point in time. In that sense a full export with all tasks and endpoint and serversettings is safer. Parsing the complete export is not too hard to script either just simply looking for strings or properly decoding the json using tools provided by languages like java/perl/powershell/python
- Are there other options to modify server settings from a scripting perspective? Yes. The officially recommended method it to use the Enterprise Manager API. Using that, no files are needed, it can all be fetched, modified, and pushed back out from memory structures.
Hein.
