Open topic with navigation

TIBCO ActiveSpaces® - Enterprise Edition 5.0.0

# Configuring a Proxy That Can Be Accessed from Different Subnets

The Network Address Translation (NAT) is possible with the use of the options, `proxy_client_listen_external_host` and `proxy_client_listen_external_port`.

The steps to configure the external host and port differ based on your environment. Treat this procedure as a general guideline to help client applications connect to a proxy.

Procedure
1. Set `proxy_client_listen_port` to the internal port for the proxy.
2. Determine the external host IP address that a client can use to connect to the proxy.
   1. Set `proxy_client_listen_external_host` to this external host IP address.
3. Determine if the internal port to which the proxy is listening is the same as the one that is exposed externally.
   Note: If a different port is exposed externally, you must set up port forwarding outside of ActiveSpaces to map the external port to the internal port.
   1. If the external port is different from the internal port, set `proxy_client_listen_external_port` to the external value.
   Note: If you are in a dynamic environment, use the command-line parameter `-e <ip:port>` when you run the tibdgproxy process. For more information, see Starting a Proxy with an External Host and Port.

## An Example of Creating a Proxy That Can Be Accessed from a Different Subnet

    tibdg -r http://localhost:8080 proxy create proxy_client_listen_port=8999
    proxy_client_listen_external_host=192.168.1.136 p2

## An Example of Creating a Proxy with an External Port

    tibdg -r http://localhost:8080 proxy create proxy_client_listen_port=8999
    proxy_client_listen_external_host=192.168.1.136 proxy_client_listen_external_port=7999 p2

In this example, when the client application attempts to connect, it first connects to the realm service (which needs ports 8080 and 8083 opened or forwarded). The realm service notifies the client about the proxies that are running and includes the external host and port (if configured) so that the client can connect to the proxy that is on a different subnet. For the connection to succeed, the administrator must set up port forwarding correctly. In Docker, this might be with the `-p 8999:8999` syntax or `-p 7999:8999` to forward a port on the host to a port in a specific container.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO ActiveSpaces® - Enterprise Edition

Copyright © 2009-2025. Cloud Software Group, Inc. All Rights Reserved.