In order to reload virtual domains from the permanent repository other than configuration file you have to send VHOSTS_RELOAD ad-hoc command to the VHostManager on the server.
The reload command request is of the form:
<iq type="set" to="vhost-man@existing.domain.com" id="aac8a"> <command xmlns="http://jabber.org/protocol/commands" node="VHOSTS_RELOAD" /> </iq>
The server sends a response upon successful completion of the command with current number of virtual domains server by the installation:
<iq from="vhost-man@existing.domain.com" type="result" to="cmd-sender-admin@existing.domain.com" id="aac8a"> <command xmlns="http://jabber.org/protocol/commands" status="completed" node="VHOSTS_RELOAD"> <x xmlns="jabber:x:data" type="result"> <field type="fixed" var="Note"> <value>Current number of VHosts: 123</value> </field> </x> </command> </iq>
If the command is sent from other than admin account the server returns an error:
<iq from="vhost-man@existing.domain.com" type="error" to="cmd-sender-admin@existing.domain.com" id="aac8a"> <command xmlns="http://jabber.org/protocol/commands" node="VHOSTS_RELOAD" /> <error type="auth" code="401"> <not-authorized xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en"> You are not authorized for this action. </text> </error> </iq>
The response doesn’t have any special meaning other then informative for the end-user. The client may ignore response as it is sent after the command has been executed.