In the November 2020 release of TIBCO Cloud™  Integration, the commands for log streaming and access to on-premises systems will be merged into the TIBCO Cloud™  Integration - Hybrid Agent (tibagent). Instead of installing TIBCO Cloud - Proxy Agent (tibtunnel), the same functionality is instead included in the TIBCO Cloud™  Integration - Hybrid Agent (tibagent).

The following changes have been made in this release:

• You no longer need to download and install TIBCO Cloud™  - Proxy Agent and the TIBCO Cloud CLI. Tunneling functionality is now included in the TIBCO Cloud™  Integration - Hybrid Agent.

• The tibagent configure monitor command is replaced with tibagent configure agent

• The tibtunnel configure command is replaced with tibagent configure connect. This must be run once after the tibagent configure agent command.

• The tibcli app tibtunnel command is replaced with the tibagent start agent command. This also applies to the --logstream option.

• The documentation has moved to https://integration.cloud.tibco.com/docs/#tci/using/hybrid-agent/index.html

Examples

The following are basic examples using the new commands. See the documentation for specific examples and options:

To start a tunnel using auto-discovery to discover any apps using an access key:

1. Create an access key and copy the access secret.

2. Configure the hybrid agent: tibagent configure monitor <agentName>

3. Configure the hybrid agent for the tunnel: tibagent configure connect --accessSecret <accessSecret> --accessKey <accessKey> <agentName>

4. Start the hybrid agent: tibagent start agent --spec 9998:localhost:9999 <agentName>

To start a tunnel for specific apps:

1. Create an access key and copy the access secret.

2. Configure the hybrid agent: tibagent configure monitor <agentName>

3. Configure the hybrid agent for the tunnel: tibagent configure connect --accessSecret <accessSecret> --app app1 --app app2 <agentName>

4. Start the hybrid agent: tibagent start agent --spec 9998:localhost:9999 <agentName>

To start multiple tunnels for different apps connected with the same access key but different specs:

1. Create an access key and copy the access secret.

2. Configure the first agent: tibagent configure connect --accessSecret <accessSecret> --app app1 <agentName1>

3. Start the first agent: tibagent start agent --spec 9998:localhost:9999 <agentName1>

4. Configure the second agent: tibagent configure monitor -p 7820 <agentName2>

5. Start the second agent: tibagent start agent --spec 3306:MySql:3306 <agentName2>
    

To start a tunnel for dbservice:

1. Create an access key and copy the access secret.

2. Start DB Service: tibcli org dbservice enable --accessKey <accessKey>

3. Configure the Proxy Agent: tibagent configure monitor <agentName>

4. Configure the Proxy Agent for the tunnel: tibagent configure connect --accessSecret <accessSecret> --accessKey <accessKey> <agentName>

5. Start the agent: tibagent start agent --spec 9998:localhost:9999 <agentName>

Streaming logs:

1. Create an access key and copy the access secret.

2. Configure the Proxy Agent: tibagent configure monitor <agentName>

3. Configure the Proxy Agent for the tunnel: tibagent configure connect --accessSecret <accessSecret> --accessKey <accessKey> <agentName>

4. Start the agent: tibagent start agent --logStream --spec 9998:localhost:9999 <agentName>

NOTE: We highly encourage existing TIBCO Cloud Integration - Develop (Flogo) and Integrate (BW) customers to start planning to use TIBCO Cloud™  Integration - Hybrid Agent (tibagent). Instead of using  TIBCO Cloud - Proxy Agent (tibtunnel),  customers can first test in a lower environment and gradually switch over their hybrid connectivity application to use TIBCO Cloud™  Integration - Hybrid Agent (tibagent) Instead of TIBCO Cloud - Proxy Agent (tibtunnel).

For a more detailed example of the Old (tibtunnel) vs New (tibagent) New Approach please refer to PDF/Doc Attach