Connect On-Premise Agent Requirements
If your Connect on-premise agent is running in a virtual machine and you clone that virtual machine, an exact duplicate of the agent is generated with the same internal ID. This can cause incorrect data to display in TIBCO Cloud™ Integration - Connect because the Cloud cannot distinguish between the two agents. On the original virtual machine, shut down the Connect on-premise agent before cloning. In the new virtual machine, install a new Connect on-premise agent, move your apps to that agent, and then delete the copied agent.
Operating Systems
Connect on-premise agents are supported on computers running 64-bit operating systems supported by Microsoft .NET Framework:
When setting up your production environment, best practice is to install agents in a Windows Server environment.
The following Microsoft® components are also required:
- Microsoft .NET Framework 4.7.2 (full version).
- Microsoft Windows Identity Foundation (WIF).
If your site will be using the Dynamics CRM Connector, you may need to enable WIF 3.5.
To Enable WIF:
- Open the Turn Windows features on or off dialog box.
- Scroll to and select the checkbox for Windows Identity Foundation 3.5.
- Select OK.
- Windows will turn on WIF 3.5.
Ports
Make sure that all of the following TCP ports are open. If needed, talk to your IT Administrator:
- Port 443. This port is required for outbound agent communication with TIBCO Cloud™ Integration - Connect. TIBCO Cloud™ Integration - Connect can respond to agent communication using port 443. If this port is not open, the TIBCO Cloud™ Integration - Connect agent is not fully accessible from the TIBCO Cloud™ Integration - Connect website.
- Port 80. This port is required for outbound communication for SSL Certificate validation.
- Ports 5671 and 5672, and 9350 through 9354. These are outbound ports used by the agent to communicate with the Enterprise Service Bus (ESB). The ESB can respond to agent communication using the same port. If your network policies prohibit you from opening these outbound ports, contact TIBCO Support for assistance with an alternate configuration. Warning: Performance is slower when the Enterprise Service Bus (ESB) is not used.
If you have not configured your inbound and outbound ports correctly or if you have not added an exception to your firewall for TIBCO Cloud™ Integration - Connect, the computer where your Connect on-premise agent is installed may experience very high CPU usage.
See the Check Ports In Agent Environment Knowledge Base article for instructions on determining whether or not the appropriate ports can be accessed by the Agent.
Connect On-Premise Agent Performance
Connect on-premise agent performance is influenced by many factors. TIBCO Cloud™ Integration - Connect Agents process apps containing multiple flows that access data from many source and target datastores. Data sets being integrated could be very large, in the millions of records, or smaller, in the thousands of records. Apps can be run manually, on a schedule, or be triggered by an external event, therefore, some apps may attempt to run simultaneously. The speed of the API for those datastores influences the performance of any given flow. In addition, you must consider the capacity of the server where the agent is installed along with other software competing for resources on that server. This complex list of factors varies from customer to customer making it difficult to recommend a one-size-fits-all installation option. Some options for better performance include:
- Upgrade to a more powerful server with the following minimum capacity:
- Quad Core CPU or better with a 24/7 business grade internet connection
- 8 GB of RAM
- At least 8 GB of free hard disk space for each installed Agent
- Use filters in Query and Fetch blocks to reduce the amount of data being processed.
- Merge flows that retrieve the same data so the Query is run only once.
- Update multiple target datastores with a single flow.
- Use an On event app containing a Message flow. This type of app executes only when a message is received from an external application, therefore, it executes and processes records only when needed.
- Use Batch Processing if the Connector supports it. This feature processes data in bulk and speeds up the integration process.