copy-rules-to-site
Copies routing rules and schedules from one site to another
copy-rules-to-site
[-b value | --bootstrap-config=value]
[-t value | --tool-password=value]
[-k value | --keystore-file=value]
<-F value | --source-site-name=value>
<-T value | --target-site-name=value>
[-r value | --resource-pool-name=value]
[-u <true|false> | --use-default-resource-pool=<true|false>]
[-d <true|false> | --disabled=<true|false>]
[-R value | --rule-conflict-resolution=value]
[-S value | --schedule-conflict-resolution=value]
[-e <true|false> | --test-run=<true|false>]
Overview
Use this command to copy all the routing rules and schedules from the source site to the target site.
Options
Option | Optional or Required | Default Value | Description |
---|---|---|---|
|
Optional | none | The path to the bootstrap configuration file. See Bootstrap.xml file for more information about this file. |
|
Optional | none | The configuration tool password used to decrypt the database password in the bootstrap.xml file. If the tool password is omitted, the command will prompt the end-user for it on the console. See Bootstrap.xml file help topic for more information. |
|
Optional | none | The location of the keystore containing the certificates used for securing internal communication. |
|
Required | none | The name of the site from which the routing rules and schedules will be copied. |
|
Required | none | The name of the site into which the routing rules and schedules will be copied. |
|
Optional | none | A resource pool name that can be used if the resource pool for a given rule is not found. |
|
Optional | false | If enabled and the resource pool for a given rule is not found, the default resource pool will be used instead, and the instances count will be automatically reset to one instance. |
|
Optional | false | If true, all the rules will be copied in a disabled state. |
|
Optional | fail | Defines how to handle copying a rule if there already exists a rule with the same name and the same file/user/group in the target site. The argument can be one of: fail (default), replace, or skip. |
|
Optional | rename | Defines how to handle copying a shared schedule if there already exists a shared schedule with the same name in the target site. The argument can be one of: rename (default), or replace. If the schedules are identical, the schedule in the target site will remain as it was. |
|
Optional | false | If true, the copy will not actually take place, but the command will produce a preview of the import status of each rule/schedule. |
Parent topic: Command-line reference