The imported policies are taken from the file to which they were exported (
-inputFile parameter), or from stdin if no such file is specified.
Not all files can be imported. Data that you cannot migrate between sphere environments includes the following:
Logging policy data collected by your transaction management database.
You cannot migrate information that has been collected and written to either file or database storage through the application of logging policies on your managed services.
Instance data for exceptional conditions that have occurred in your transactions.
You cannot migrate information that has been collected by the transaction management component of Business Transaction Management.
By default, this command replaces all existing policies that are older than the imported policies.
btmcli importPolicies [-i inputFile] [-replace ALL | all | NEWER | newer | NONE | none] [-v] -s sphereUrl -l username:password
|-i||-inputFile||The name of the file containing the data to be imported.|
|-replace||-replacementLevel||Determines the outcome when an imported policy matches an existing policy in the system:
ALL: replace all existing policies
NEWER: replace existing policies that are older than the imported policies. (Default)
NONE: do not replace any existing policies.
|-v||-verbose||Display more detailed information about command execution.|
|-s||-sphereUrl||The URL of the sphere.
This flag is not required if you have set the AP_SPHERE_URL environment variable for your sphere.
|-l||-userLogin||The username and password associated with the sphere, in the format: username:password. This set of credentials must belong to a user in the btmadmin role.
See Security Options in Accessing CLI Commands for information on furnishing login credentials.
You can encrypt passwords using the
The following example shows the
importPolicies command used to import data from the file
btmcli importPolicies -inputFile MyPolicies -replace ALL -s http://localhost:8080/btmcentral/sphere/ -l admin:abracadabra