How to connect to onpremise EMS server on TCI via TIBCO Cloud™ Integration - Hybrid Agent (tibagent)
Article ID: KB0070733
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration | - |
Description
TIBCO Cloud™ Integration could connect to services running on-premise in your network via the TIBCO Cloud™ Integration - Hybrid Agent (tibagent). With the Hybrid Agent, your Apps in TIBCO Cloud™ Integration could access the on-premise services without opening ports on the public internet. This article describes how to setup the TIBCO Cloud™ Integration - Hybrid Agent (tibagent) to connect to the local EMS server.
Environment
Resolution
Prerequisites:
1. Download and install Studio for BusinessWorks.
https://integration.cloud.tibco.com/docs/#tci/getstarted/installation/installing-studio.html
2. Download and install TIBCO Cloud - Command Line Interface
https://integration.cloud.tibco.com/docs/#tci/getstarted/installation/installing-cli.html
3. Download the TIBCO Cloud™ Integration - Hybrid Agent (tibagent) t binary and create the access key.
Steps to configure and connect to on-premise EMS server on TCI using Hybrid agent
1.Install TIBCO Enterprise Message Service™ Client Libraries for your Studio environment. To do that run the following command from the <BW_HOME>/bin folder and follow the prompts:
| bwinstall ems-driver |
2. Design your application using JMS pallet in the studio and create Enterprise archive(EAR)
3. Upload the supplement EMS drives using TIBCO Cloud - Command Line Interface.
| NOTE: This is a one time task for the EMS libraries to be available at the Organization level |
A] Zip the contents of required EMS directories at: <EMS_installation_directory>/EMS/components/shared/1.0.0/plugins folder.
B] Name the zip file: ems.zip.
C] Place this zip in a newly created temp folder.
D] Run the following supplement command from inside that temp folder:
|
tibcli bwplugin supplement ems
|
4. Skip this step if you are using an existing accesskey.
To create a new accessKey follow the steps in the documentation https://account.cloud.tibco.com/cloud/docs/proxy-agent/creating_access_key.html and copy accessSecret.
5. Using tibcli push JMS application to TCI cloud by keeping it's scaling instance as '0' (i.e. no auto-scale) and attach the ACCESS_KEY to it at the same time.
|
tibcli app push 0 -accessKey <accesskey name>
Example : tibcli app push 0 --accessKey JMS_ACCESS_KEY |
6. Configure Hybrid agent
tibagent configure agent <agentName>Example : tibagent configure agent tunnelagent |
7. Configure connect and store accessSecret created in step 4 with app names
tibagent configure connect --accessSecret <accesssecret> --app app1 --app app2 <agentName>Example : tibagent configure connect --accessSecret abcdefgh1234567890 --app Proxy_JMStest_2 tunnelagent |
8. Start tibagent using the specs
tibagent start agent --spec 9998:localhost:9999 <agentName>The syntax for a spec is containerPort:onPremiseHost:onPremisePortExample : tibagent start agent --spec 7222:hchapara-T480s:7222 tunnelagent |
9. Scale up the JMS application
|
tibcli app scaleup <instance count> <App name>
Example: tibcli app scaleup 1 Proxy_JMStest_2 |
Issue/Introduction
Additional Information
Documentation links :
- Installing Studio for BusinessWorks: https://integration.cloud.tibco.com/docs/#tci/getstarted/installation/installing-studio.html
- Installing CLI : https://integration.cloud.tibco.com/docs/#tci/getstarted/installation/installing-cli.html
- Installing Hybrid Agent : https://integration.cloud.tibco.com/docs/#tci/using/hybrid-agent/installing-configuring-running-agent.html
- Generating Access key : https://account.cloud.tibco.com/cloud/docs/proxy-agent/creating_access_key.html
- Configuring Hybrid Agent : https://integration.cloud.tibco.com/docs/#tci/using/hybrid-agent/installing-configuring-running-agent.html
- Supplementing drivers : https://integration.cloud.tibco.com/docs/#Subsystems/BW/app-dev-guide/supplementing-driver.html
Feedback
