| Property |
Default / Example |
Description |
Implemented |
| plugin/xmlrpc/hostname |
localhost |
Specify a hostname where the XMLRPC server runs
|
 |
| plugin/xmlrpc/port |
7607 |
The XMLRPC server port
|
|
| plugin/xmlrpc/localHostname |
localhost |
The local address the xmlrpc is bound to.
Usually this is dynamically choosen by your operating system and you don't need
to specify it.
|
|
| plugin/xmlrpc/localPort |
8900 |
The local port the xmlrpc is bound to.
Default is -1 and the operating system chooses an arbitrary port.
|
|
| plugin/xmlrpc/useCDATA |
false |
Encapsulates all parameters with a CDATA. Note that you can use this only if
you are sure that your Messages do not contain already a CDATA (the key, qos and
content), otherwise you will get an exception. This flag is only used for systems
which need to validate the content of the message on a protocol layer, for example
proxies or firewalls. If unsure leave this untouched. If you set this flag on the
server it will modify all updates and callback pings, if you set it on the client
it will influence all requests coming from the client.
|
|
| plugin/xmlrpc/customProxyClass |
null |
The name of the class to use for proxying requests coming from the client.
This class shall only be specified if you have some non-standard behaviour,
i.e. if your client is sending xmlrpc commands which are not the normal
subscribe, publish ... methods internally defined by xmlBlaster.
Suppose you want to send the HTTP Requests over a proxy, a firewall or a proprietary
security gateway which does not allow these methods, then you could tunnel these
inside other methods which are defined by a proprietary client protocol. On the
server side these requests have to be extracted and decoded before invoking the
original xmlBlasterImpl and authenticate requests.
|
|
| plugin/xmlrpc/responseTimeout |
0 |
The time it shall wait in milliseconds before interrupting the request. If zero
or negative it is not set.
|
|
| plugin/xmlrpc/SoTimeout |
0 |
If zero or negative it is not set. It has the same meaning as for the SOCKET Protocol.
|
|
| plugin/xmlrpc/compress/type |
|
Its only possible value is either an empty string (unset) or 'zlib'. Compression will be
done on the protocol layer. You only need to define this on the client side, the server
will then recognize if the client is expecting compressed or uncompressed data.
|
|
| plugin/xmlrpc/proxyHost |
null |
If you use a proxy this specifies the hostname or IP of the host to use. Note that if
you have not specified this property, it will be implicitly set to localhost if you
specified proxyPort.
|
|
| plugin/xmlrpc/proxyPort |
null |
If you set this property the protocol will use a proxy, even if you did not explicitly
specify a proxyPort or the proxySet property. If you set this property and the proxyHost
property is not explicitly set, the later will be set to localhost.
|
|
| plugin/xmlrpc/proxyHostSSL |
|
You specify this property only if you want HTTPS Traffic to be directed to a proxy
different from the HTTP Proxy. If you do not specify anything here, then the same
host will be used for HTTP and HTTPS.
|
|
| plugin/xmlrpc/proxyPortSSL |
|
You specify this property only if you want HTTPS Traffic to be directed to a proxy
port different from the HTTP Proxy port. If you do not specify anything here,
then the same port will be used for HTTP and HTTPS.
|
|
| plugin/xmlrpc/basicUserName |
|
If basic authentication is activated on the server side (for example in a reverse proxy),
then you can pass that username here.
|
|
| plugin/xmlrpc/basicPassword |
|
If basic authentication is activated on the server side (for example in a reverse proxy),
then you can pass the password to be used here.
|
|
| plugin/xmlrpc/basicEncoding |
|
If basic authentication is activated on the server side (for example in a reverse proxy),
then you can pass the encoding to be used here.
|
|
