. . . . . . . . . . . . . . . . . . . . . . . 409 65.4. Configuring Asynchronous Connection Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 66. Configuring the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url’s or just to an individual connector, so where you have • (tcp://remote-host1:5445

. . . . . . . . . . . . . . . . . . . . . . . 409 65.4. Configuring Asynchronous Connection Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 66. Configuring the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url’s or just to an individual connector, so where you have • (tcp://remote-host1:5445

. . . . . . . . . . . . . . . . . . . . . . . 407 65.4. Configuring Asynchronous Connection Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 66. Configuring the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url’s or just to an individual connector, so where you have • (tcp://remote-host1:5445

. . . . . . . . . . . . . . . . . . . . . . . 407 65.4. Configuring Asynchronous Connection Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 66. Configuring the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url’s or just to an individual connector, so where you have • (tcp://remote-host1:5445

mybroker A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

mybroker A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

Server 18 A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds The username (Default: input) --verbose Adds more information on the execution -- This option can be used to separate command-line options from the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port? key1=value1&key2=value2 ) to customize the underlying transport

mybroker A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds The username (Default: input) --verbose Adds more information on the execution -- This option can be used to separate command-line options from the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport

mybroker A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds The username (Default: input) --verbose Adds more information on the execution -- This option can be used to separate command-line options from the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport

mybroker A broker instance directory will contain the following sub directories: bin : holds execution scripts associated with this instance. etc : hold the instance configuration files data : holds The username (Default: input) --verbose Adds more information on the execution -- This option can be used to separate command-line options from the server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport