Legacy SEMP api body for config sync command ```assert-master message-vpn default```

harshit12339
harshit12339 Member Posts: 5
edited December 2023 in General Discussions #1
Hello , I am looking for Legacy SEMP api for config sync command ```assert-master message-vpn default```

I was trying this as body
"""<rpc><admin><config-sync><assert-leader><message-vpn><default></default></message-vpn></assert-leader></config-sync></admin></rpc>"""

or

"""<rpc><admin><config-sync><assert-leader><message-vpn><default/></message-vpn></assert-leader></config-sync></admin></rpc>"""

but none of it worked.
please let me know what is exact command to achieve this.

also I am not able to find rpc command syntax documentations to look for appropriate command for use cases like config sync assert leader/master. so please let me know the doc for that

also which is correct asser-master or assert-leader?

Thanks for ur help
Tagged:

Best Answer

  • danbrown
    danbrown Member, Employee Posts: 4 Solace Employee
    edited December 2023 #2 Answer ✓

    Hi, the command is assert-leader.

    The config-sync commands are documented here.

    And legacy SEMP is documented here.

    It is definitely not trivial to find the correct xml body.

    I used the xsd spec semp-rpc-soltr.xsd, which can be downloaded from the Solace product download page, where you can also download the enterprise software broker.

    The command can be executed on system level or on vpn level. The SEMP bodies are:

    <rpc><admin><config-sync><assert-leader><router/></assert-leader></config-sync></admin></rpc>

    <rpc><admin><config-sync><assert-leader><vpn-name>default</vpn-name></assert-leader></config-sync></admin></rpc>

    Instead of the name default you can also use wildcard * for multiple VPNs.

    The trick here is that the message-vpn is called vpn-name in SEMP.

Answers

  • danbrown
    danbrown Member, Employee Posts: 4 Solace Employee
    edited December 2023 #3 Answer ✓

    Hi, the command is assert-leader.

    The config-sync commands are documented here.

    And legacy SEMP is documented here.

    It is definitely not trivial to find the correct xml body.

    I used the xsd spec semp-rpc-soltr.xsd, which can be downloaded from the Solace product download page, where you can also download the enterprise software broker.

    The command can be executed on system level or on vpn level. The SEMP bodies are:

    <rpc><admin><config-sync><assert-leader><router/></assert-leader></config-sync></admin></rpc>

    <rpc><admin><config-sync><assert-leader><vpn-name>default</vpn-name></assert-leader></config-sync></admin></rpc>

    Instead of the name default you can also use wildcard * for multiple VPNs.

    The trick here is that the message-vpn is called vpn-name in SEMP.

  • danbrown
    danbrown Member, Employee Posts: 4 Solace Employee

    And for completeness you can generate the xsd specs as described here:

    To obtain the SEMP v1 Request schema file, perform a GET on the following URI:

    http://<HOST>/SEMP/v1/requestSchema.xsd


    To obtain the SEMP v1 Reply schema file, perform a GET on the following URI:

    http://<HOST>/SEMP/v1/replySchema.xsd

  • danbrown
    danbrown Member, Employee Posts: 4 Solace Employee

    Visualization in wmhelp xmlpad:

  • harshit12339
    harshit12339 Member Posts: 5

    Thanks danbrown , the suggestions were cool