Initializing and Restoring

From Obsidian Scheduler
Revision as of 21:17, 29 January 2015 by Craig (talk | contribs)
Jump to navigationJump to search

As of Obsidian 3.0.0

At times, you may wish to automate initialization or even restoration of an Obsidian configuration. For example, you may wish to take a known good configuration from a development environment and apply it to a test environment.

In Obsidian 3.0.0, we introduce an expansion of our Initializing Job Schedules support that leverages the system restore functionality of our API.

By default, Obsidian will look for a file on the classpath named /obsidianInitialization.json. You may override the classpath resource name using the system property obsidianInitClasspath. For example, you could add the java system property -DobsidianInitClasspath=/com/mycompany/obsidianInit.json. You can also use a file-based resource by using the system property obsidianInitFile. For example, you could add the java system property -DobsidianInitFile=/var/obsidian/obsidianScheduleInitialization.json.

Note: Initialization only runs on scheduler instances. This means that a standalone Obsidian web application with no scheduler running will not do any initialization based on the presence of the appropriate JSON file.