Allowing endpoints to connect to a broker

To allow the broker to accept connections from controllers and targets you can define and configure inbound connections using the trc_broker.properties file.

About this task

You can configure multiple inbound connections and define a prefix for each connection parameter to allow the broker to find all required settings for each connection.
Note: An additional HTTPS connection can be added into the Broker configuration. It is possible to configure this new connection to the same port of the existing Inbound connection. It is however required to retain the existing Inbound connection in order to allow connection with all the Remote Control components.
Configure any inbound connections when configuring the trc_broker.properties file. For more details about editing this file, see Configuring the broker properties.
Note:
  1. Do not prefix with # or ! as these are reserved for comments in properties files.
  2. If you want to include spaces in the prefix you have to escape them with \ for example : my connection.ConnectionType should be defined as my\connection.ConnectionType
To configure inbound connections complete the following steps:

Procedure

  1. Configure the following parameters within the trc_broker.properties file
    ConnectionType
    Defines the type of connection. Should be set to Inbound or Inbound6 when you are using IPv6 networks. For example: my\connection.ConnectionType=Inbound
    PortToListen
    Defines the TCP port that endpoints should use to connect to this broker. The port for listening for inbound connections. Required parameter.
    AllowEndpoints
    Determines whether endpoints can connect to this broker.
    Yes
    Endpoint connections can be made to this broker. This is the default value.
    No
    Endpoint connections cannot be made to this broker.
    AllowBrokers
    Determines whether other brokers can connect to this broker. Set to No or <blank> means other brokers cannot connect to this broker. If other brokers can connect to this broker, provide a list of brokers that are allowed to connect. For example broker1.company.com,broker2.company.com,broker3.company.com.
    Note: The hostnames listed here must match the certificate and the hostnames used when registering the brokers in the remote control server.
  2. Save the file.

What to do next

If you are configuring multiple brokers in your environment which will connect to each other to complete the connection between the controller and target, you should configure broker connections in the broker properties file. For more details, see Support for multiple brokers. When you have finished creating a broker configuration you can register the brokers in the BigFix® Remote Control Server database to be used for facilitating remote control connections across the internet. For more details, see Registering a broker on the server.