Does TIBCO Hybrid Connectivity Proxy Agent (tibtunnel) support resource configured behind a corporate proxy like HTTP Proxy?

Does TIBCO Hybrid Connectivity Proxy Agent (tibtunnel) support resource configured behind a corporate proxy like HTTP Proxy?

book

Article ID: KB0078285

calendar_today

Updated On:

Products Versions
TIBCO Cloud N/A

Description

This solution will help answer following questions:

  • Does TIBCO Hybrid Connectivity Proxy Agent (tibtunnel) support resource configured behind a corporate proxy like HTTP Proxy?
  • How to connect TCI App to On-Prem resources running behind HTTP/s Proxy ?

Issue/Introduction

Does TIBCO Hybrid Connectivity Proxy Agent (tibtunnel) support resource configured behind a corporate proxy like HTTP Proxy?

Environment

TIBCO Cloud TIBCO Cloud Integration (TCI)

Resolution



Step 1: Tunnel Agent (tibtunnel) configuration
  • The configure command is used to configure the authentication and save it as a profile. By default, a profile "default" will be used.
 
../tibtunnel configure [--profile <profileName>] [(--basicauth [--user <userName> [--password <password>]]) | --accessKey <accessKeySecret>]

NOTE:
The command will write/update the a file under directory ~/.tibtunnel that stores the profiles in an INI format. A profile has the following format:

  • name - required, in square brackets
  • then, one of:
    • accessKey
    • basicauthUser and basicauthPassword
    Step 2: Establish the tunnel and expose on-premise resources running behind HTTP Proxy
    • Users will have to set an environment variable *before* starting tibtunnel. For example :
    For Linux:
    export HTTP_PROXY=http://http_proxy:port/

    For Window:
    Set HTTP_PROXY=http://http_proxy:port/
    • If we have HTTPS Proxy then
    For Linux:
    export HTTPS_PROXY=http://http_proxy:port/

    For Window:
    Set HTTPS_PROXY=http://http_proxy:port/
    • The tibtunnel establishes tunnels to the application containers when a connect command is executed. The profile is an optional argument, and if not supplied the "default" profile is used.
    ./tibtunnel connect [--profile <profileName>] -s <spec> [-s <spec> ...] <ConnectURL>
    On the above command, the on-premise resources that are to be exposed to the application containers running in TIBCO Cloud are listed as “specifications" or “specs” in the following format:


    -s <containerPort>:<onPremiseHost>:<onPremisePort>
    This means that on-premise resource at <onPremiseHost>:<onPremisePort> will be reachable from the application container as <onPremiseHost>:<containerPort>. Most of the time the onPremisePort and containerPort will be the same (e.g. 443:jira.tibco.com:443). However, if the on-premise port is not available in the container (e.g. the application is using that port), the port can be re-mapped to a different port.

     
    Powered by Wolken Software