Sun Java System Instant Messaging 7.2 Administration Guide

Instant Messaging XMPP/HTTP Gateway Configuration Parameters

Table B–1 describes the configuration parameters in httpbind.conf.

Table B–1 XMPP/HTTP Gateway Configuration Parameters in httpbind.conf


Default Value 




If is set to true, this parameter specifies the full URL for the server node in the server pool. This URL should not point to a load balancer, but to an Instant Messaging server instance.


This parameter defines whether or not the gateway is in a server pool deployment. If no httpbind.pool.nodeId is specified, the value for this parameter is set to false.

The value for this parameter can be: 

  • true – the gateway is part of a server pool deployment. In addition, enable, on, yes, and 1 are also valid values. If you set this parameter to true, you must provide a value for httpbind.pool.nodeId.

  • false – (default) the gateway is not part of a server pool deployment. Leaving the value blank (empty string) is also a valid value.



Contains a comma-separated list of ID keys, or gwdomain-id, which the gateway uses as a configuration key to determine which domains, hosts, host passwords, and component JIDs the gateway should use. See Table B–2 for more information on ID keys.


text/xml; charset=utf-8

The default value for the content-type HTTP header the gateway uses when sending a response back to the client.



Specifies the maximum permissible value for the hold attribute in the client request as defined in JEP 124. If the client specifies a value higher than the gateway in the request, the gateway's value will be used. Otherwise, the value in the client request will be used.



The maximum time in seconds of client inactivity after which the gateway will terminate the connection to the client. 



The location of the log4j configuration file the gateway will use for logging. If you leave this parameter blank, then logging for the gateway is turned off. The logger name is “httpbind” (log4j.logger.httpbind).


1 (second)

The minimum time, in seconds, a client must wait before sending another request. 



The number of concurrent requests a client can make to the gateway. If the value of this parameter is less than the value for the JEP 124 hold attribute in the client request, the value for this parameter will be set to hold+1. Do not set this parameter to 1, as doing so could severely degrade performance. See httpbind.hold for more information.


1 (second)

The amount of time, in seconds, to allow in addition to time-outs for round trips to account for network latencies. Setting this value too high may degrade performance. 


120 (seconds)

The default time, in seconds, within which the gateway will send a response to the client. If the client wait time is set to a value higher than the gateway wait time, the gateway's wait time is used.