System settings

 

Note: Replace dbsecret in the examples below with the appropriate database secret.

Scope of system settings

There are two scopes for system settings:

  1. global: Global settings apply to all servers connected in a GRID. If you have a single ISL Conference Proxy installation, you can simply always use global settings.
  2. local: Local settings apply only to one specific server connected in a GRID, so you can override certain global settings for a specific server. If you have a single ISL Conference Proxy installation, you can ignore local settings. There is only one important setting, which is always local and it is not present in global settings - Bind IP.

List of all settings

The list is available in the protocol specification file at http://localhost:7615/xmlmsg/relaxng.xml. Please see the element definitions for GridConfigFields and LocalConfigFields. The mapping from XML element to the setting in web administration is specified in the comment, the two possible forms are:

  1. Settings page :: Setting name or
  2. Settings section :: Settings page :: Setting name

Query system settings

Messages explained here can be used to query ISL Conference Proxy system settings.


Retrieve all global settings

<queryDatabase secret="dbsecret">

<gridConfiguration/>

</queryDatabase>


Retrieve local settings for specific server (-1 means current server)

<queryDatabase secret="dbsecret">

<localConfiguration serverId="-1"/>

</queryDatabase>


Retrieve local settings for all servers

<queryDatabase secret="dbsecret">

<localConfiguration/>

</queryDatabase>

Modify system settings

Messages explained here can be used to modify ISL Conference Proxy system settings.


Set HTTPT ports to "443, 7615"

<manipulateDatabase secret="dbsecret">

<updateGridconfiguration mode="update">

<httptPorts>

<value>443</value>

<value>7615</value>

</httptPorts>

</updateGridconfiguration>

</manipulateDatabase>


Set Bind IP for the current server

<manipulateDatabase secret="dbsecret">

<updateLocalconfiguration mode="update" serverId="-1">

<bindIp>192.168.0.77</bindIp>

</updateLocalconfiguration>

</manipulateDatabase>


Effect of modifications

Not all settings take effect immediately. Some settings require the ISL Conference Proxy service to be restarted. Please check, if the server needs to be restarted, after you modify the settings.


Check, if the server needs to be restarted

<module secret="dbsecret">

<islConferenceProxy>

<isServerRestartRequired/>

</islConferenceProxy>

</module>

response (yes or no):

<moduleResponse>

<islConferenceProxyResponse>

<isServerRestartRequiredResponse>yes</isServerRestartRequiredResponse>

</islConferenceProxyResponse>

</moduleResponse>


Check, if the specific server needs to be restarted

<module secret="dbsecret">

<islConferenceProxy>

<isServerRestartRequired serverId="4"/>

</islConferenceProxy>

</module>


Restart current server

<module secret="dbsecret">

<islConferenceProxy>

<restartServer/>

</islConferenceProxy>

</module>


Restart specific server

<module secret="dbsecret">

<islConferenceProxy>

<restartServer serverId="5"/>

</islConferenceProxy>

</module>


Note: These examples cover only some of the options. For a list of all options, please refer to the protocol specification file that is available at http://localhost:7615/xmlmsg/relaxng.xml.

Tags: isl conference proxy, integration, xmlmsg

Was this article helpful?