3.1. configexport

The configexport subcommand exports all configuration objects to a specified location, enabling you to reuse a system configuration in another environment. For example, you can test a configuration in a development environment, then export it and import it into a production environment. This subcommand also enables you to inspect the active configuration of an OpenIDM instance.

OpenIDM must be running when you execute this command.

Usage is as follows:

$ ./cli.sh configexport /export-location

For example:

$ ./cli.sh configexport /tmp/conf

Configuration objects are exported, as .json files, to the specified directory. Configuration files that are present in this directory are renamed as backup files, with a timestamp, for example, audit.json.2012-12-19T12-00-28.bkp, and are not overwritten. The following configuration objects are exported:

  • The internal repository configuration (repo.orientdb.json or repo.jdbc.json)

  • The log configuration (audit.json)

  • The authentication configuration (authentication.json )

  • The managed object configuration (managed.json)

  • The connector configuration (provisioner.openicf-*.json )

  • The router service configuration (router.json)

  • The scheduler service configuration (scheduler.json)

  • Any configured schedules (schedule-*.json)

  • The synchronization mapping configuration (sync.json )

  • If workflows are defined, the configuration of the workflow engine (workflow.json) and the workflow access configuration (process-access.json)

  • Any configuration files related to the user interface (ui-*.json)

  • The configuration of any custom endpoints (endpoint-*.json)

  • The policy configuration (policy.json)