Use the "backup" command to export the configuration of objects on a PS+ Broker into a single JSON, then use the "create" or "update" command to restore the configuration.
For example, you could run ./solconfig backup vpn Demo to show the whole configuration on the console, or run ./solconfig backup vpn Demo > Demo.json to save the configuration into a json file, use opaque password like ./solconfig backup -O 12345678 vpn Demo if you want to back up the sensitive information like "password".
# java -jar build/libs/solconfig.jar backup vpn RDP
{
"sempVersion": "2.19",
"msgVpns": [
{
"authenticationBasicProfileName": "",
"authenticationBasicType": "internal",
"enabled": true,
...
"msgVpnName": "RDP",
...
"aclProfiles": [
{
"aclProfileName": "default",
"clientConnectDefaultAction": "allow",
"publishTopicDefaultAction": "allow",
"subscribeTopicDefaultAction": "allow"
}
],
...
"queues": [
{
"egressEnabled": true,
"eventBindCountThreshold": {"clearPercent":60,"setPercent":80},
"eventMsgSpoolUsageThreshold": {"clearPercent":60,"setPercent":80},
"eventRejectLowPriorityMsgLimitThreshold": {"clearPercent":60,"setPercent":80},
"ingressEnabled": true,
"permission": "consume",
"queueName": "aws Queue",
"subscriptions": [
{
"subscriptionTopic": "aws"
}
]
},
],
"restDeliveryPoints": [
{
"enabled": true,
"restDeliveryPointName": "aws",
"service": "API Gateway",
"vendor": "AWS",
"queueBindings": [
{
"postRequestTarget": "/initializer",
"queueBindingName": "aws Queue"
}
],
"restConsumers": [
{
"enabled": true,
"remoteHost": "xxxxx.execute-api.ap-southeast-1.amazonaws.com",
"remotePort": 443,
"restConsumerName": "aws REST Consumer",
"tlsEnabled": true
}
]
}
]
}
]
}
Then run ./solconfig -H http://another-broker:8080 create Demo.json to create the same Message VPN on another broker.
Make sure you have JDK 11 or above installed.
git clone https://github.com/flyisland/solconfig
cd solconfig
./gradlew build
java -jar build/libs/solconfig.jar helpCAUTION: If you encounter into any issues while using native image, please try the jar version before you submit an issues, thanks.
You could build solconfig as native image by following below steps:
- Install Graalvm 11 first.
java -version
openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment GraalVM CE 21.0.0.2 (build 11.0.10+8-jvmci-21.0-b06)
OpenJDK 64-Bit Server VM GraalVM CE 21.0.0.2 (build 11.0.10+8-jvmci-21.0-b06, mixed mode, sharing)
-
Then install the Native Image, make sure you followed the Prerequisites.
-
Run
./native-image.sh, it will create a native image./solconfigwhich could be executed independently without JDK installed.
Run solconfig help and solconfig help sub-command to check the help message carefully before you use it.
$ java -jar solconfig.jar help
Usage: solconfig [-hkV] [--curl-only] [--cacert=<cacert>] [-H=<adminHost>]
[-p=<adminPwd>] [-u=<adminUser>] [COMMAND]
Backing Up and Restoring Solace PubSub+ Broker Configuration with SEMPv2
protocol. Use the 'backup' command to export the configuration of objects on a
PS+ Broker into a single JSON, then use the 'create' or 'update' command to
restore the configuration.
--cacert=<cacert> CA certificate file to verify peer against when
using SSL
--curl-only Print curl commands only, no effect on 'backup'
command
-h, --help Show this help message and exit.
-H, --host=<adminHost> URL to access the management endpoint of the broker
Default: http://localhost:8080
-k, --insecure Allow insecure server connections when using SSL
-p, --admin-password=<adminPwd>
The password of the management user
Default: admin
-u, --admin-user=<adminUser>
The username of the management user
Default: admin
--use-template Whether to support templating
-V, --version Print version information and exit.
Commands:
backup Export the whole configuration of objects into a single JSON
delete Delete the specified objects
create Create objects from the configuration file
update Update the existing objects to make them the same as the
configuration file
Be careful, it will DELETE existing objects like Queues or Client
Usernames, etc if they are absent in the configuration file.
This "update" command is a good complement to "create" command,
especially for the "default" VPN or the VPN of the Solace Cloud
Service instance, since you can only update them.
help Displays help information about the specified command
$ java -jar solconfig.jar help backup
Usage: solconfig backup [-O=<opaquePassword>] <resourceType> <objectNames>...
Export the whole configuration of objects into a single JSON
<resourceType> Type of the exported object [cluster, vpn]
<objectNames>... One or more object names, , "*" means all
-D, --keep-default Whether to Keep attributes with a default value
-O, ---opaque-password=<opaquePassword>
The opaquePassword for receiving and updating opaque
properties like the password of Client Usernames
$ java -jar solconfig.jar help delete
Usage: solconfig delete <resourceType> <objectName>
Delete the specified objects
<resourceType> Type of the object to delete [cluster, vpn]
<objectName> Object name to remove
$ java -jar solconfig.jar help update
Usage: solconfig update <confPath>
Update the existing objects to make them the same as the configuration file
Be careful, it will DELETE existing objects like Queues or Client Usernames,
etc if they are absent in the configuration file.
This "update" command is a good complement to "create" command, especially for
the "default" VPN or the VPN of the Solace Cloud Service instance, since you
can only update them.
<confPath> Configuration file
--no-delete Do NOT perform DELETE actions, only new objects and update
existed objects
Before version 9.6.x (sempVersion 2.17), there is no way to get the value of "write-only" attributes like the password of Client Usernames, so that the backup output is not 100 percent as same as the configuration on the PS+ broker. Means you need to set those "write-only" values in the json file in clear text before you restore the configuration, or update them with the Solace PubSub+ Manager after you restore the configuration.
Since version 9.6.x (sempVersion 2.17), with a password is provided in the opaquePassword query parameter, attributes with the opaque property (like the password of Client Usernames) are retrieved in a GET in opaque form, encrypted with this password.
The backup output is now 100 percent as same as the configuration on the PS+ broker, and the same opaquePassword is used to restore the configuration. So you could restore them with the same opaquePassword.
CAUTION:
- The opaquePassword is only supported over HTTPS, and must be between 8 and 128 characters inclusive!
- The broker to which the request is being sent must have the same major and minor SEMP version as the broker that produced the opaque attribute values.
When running the program with the "--use-template" option, template support will be provided for the input JSON file. Please check the example for more details.
CAUTION:
- The syntax of Substitution Expressions conflicts with the template. Therefore, you should not enable the templating support while there are Substitution Expressions in the JSON file.