Starting a Proxy with an External Host and Port

When the realm service and proxy are running on a subnet that is different from the one on which the client application is running, you must configure the external host and port settings in the configuration file.

You can use a command-line parameter with the tibdgproxy process to specify the external host and port. The -e option followed by the IP address and the port number helps the client reach the proxy on a different subnet. If you specify the command-line option, it overrides the values set for proxy_client_listen_external_host and proxy_client_listen_external_port in the configuration file. For more information about setting proxy_client_listen_external_host and proxy_client_listen_external_port, see Configuration Options when the Proxy and Client are on Different Subnets.
Before you begin
  • The following components must be running and reachable:
    • The realm service
    • The state keeper
    • At least one node of each copyset
  • The data grid definition in the realm service must be complete and valid.
    Procedure
  1. Start the proxy process. 
    tibdgproxy -n name -r realm_service_URL  -e External IP Address:Port

    The name of the Proxy process is required. Supply one of the proxy names you assigned in Defining a Data Grid. The URL of the realm service is required. If the client is trying to reach a proxy on a different subnet, provide the -e option followed by the IP address and the port number. Here is an example to start the proxy and set the external host and port: 

    tibdgproxy -r http://localhost:8080 -e "192.168.1.136:7999" -n p3
    Warning: The command overrides any configuration value that is already defined for this proxy.
    If the proxy is on one of several known external IP addresses, use a semicolon separated list of IP addresses in the command-line parameter. Also, see the docker-compose file in the TIBCO_HOME/as/<version>/samples/docker folder for an example on using different proxy configuration options that allow client applications on the host to communicate with a proxy running in a docker container.

  2. Verify whether the proxy process is ready by checking the status by using the administration tool.
  3. Repeat the previous steps for all the proxy names assigned in the data grid definition.
What to do next

The data grid is ready to support data operations. You can start application program processes.