| Component | Requirement |
|---|---|
| CPU | At least 2 cores |
| Memory | At least 8 GB |
| Operating System / Components |
|
| Network Connectivity | Outbound connection to specific hosts is required. |
| Remote Access | Remote access (RDP) to the server is required for the project. |
| Database (optional) | For certain implementation scenarios a SQL Server Express database has to be installed on the server. |
If possible, we recommend operating separate instances of the Connect middleware on two separate servers:
- To separate production and test environment;
- To enhance resilience through automatic load balancing should one server need maintenance work or otherwise have issues that prevent correct operation of the Connect middleware.
This setup provides the greatest benefits.
Alternatively, it's possible to have separate instances of the Connect middleware run on the same server which still provides the benefit of point no. 1.
For SQL Server scenarios under Windows 11, this step must be done before installing Connect5 Client (see more details in Prefile configuration section in Connect Configuration page):
The server on which Connect is installed requires access to the following hosts.
If you use a proxy server in your network, then you must make sure that the server on which the Connect is installed can communicate through this proxy server. See below for further details.
| Direction | Host | Protocol(s) | TCP Port(s) | Remark |
|---|---|---|---|---|
| Outbound | iam.teccom.de[1](https://iam.teccom.de/tecdirect/tomdirect.svc) |
HTTPS | 443 | TecCom Web Service (Production) |
| Outbound | solutionportal.tecalliance.net[1:1](https://solutionportal.tecalliance.net/openmessaging.asmx) |
HTTPS | 443 | TecCom Web Service (Production) |
| Outbound | staging-solutionportal.tecalliance.net[1:2](https://staging-solutionportal.tecalliance.net/openmessaging.asmx) |
HTTPS | 443 | TecCom Web Service (Staging) |
| Outbound | tecconnectsbprod.servicebus.windows.net[2] |
AMQP AMQP (HTTPS)[3] |
5671 5672 (443) |
Azure Service Bus |
| Outbound | tecconnectsb2prod.servicebus.windows.net[2:1] |
AMQP AMQP (HTTPS)[3:1] |
5671 5672 (443) |
Azure Service Bus |
| Outbound | tecconnectstorageprod.blob.core.windows.net[4] |
HTTPS | 443 | Azure Blob Storage |
| Outbound | tecconnectstorageprod.table.core.windows.net[4:1] |
HTTPS | 443 | Azure Table Storage |
| Outbound | connect-api.tecalliance.net[5] |
HTTPS | 443 | Connect API |
| Outbound | teccom.tecalliance.net[5:1] |
HTTPS | 443 | TecCom Portal |
For SAP the server on which Connect is installed also requires access to the following hosts.
| Direction | Host | Protocol(s) | Port(s) | Remark |
|---|---|---|---|---|
| Outbound | sapservicedata.iam.teccom.de(https://sapservicedata.iam.teccom.de/tcs/servicecall) |
HTTPS | 443 | BK-IT SAP Portal |
For CMD the server on which the Connect is installed also requires access to the following host.
| Direction | Host | Protocol(s) | Port(s) | Remark |
|---|---|---|---|---|
| Outbound | teccmd.tecalliance.net[1:3](https://teccmd.tecalliance.net) |
HTTPS | 443 | TecCom CMD Web Service (Production) |
For TBC import the server on which the Connect is installed also requires access to the following host.
| Direction | Host | Protocol(s) | Port(s) | Remark |
|---|---|---|---|---|
| Outbound | https://login.tecalliance.net(https://login.tecalliance.net) |
HTTPS | 443 | TecCom Portal login |
| Outbound | https://api.tbc.tecalliance.net(https://api.tbc.tecalliance.net) |
HTTPS | 443 | TBC API |
| Outbound | https://<anything>.s3.eu-central-1.amazonaws.com |
HTTPS | 443 | TBC import URL template |
Bear in mind that the Connect is a .NET application and may use the default proxy server. If this interferes with communication, then this can be disabled in a .NET configuration (e.g. the Connect 5 configuration or the machine configuration) with this directive:
<configuration>
<system.net>
<defaultProxy enabled="false" useDefaultCredentials="false" />
</system.net>
</configuration>
Authenticating against a proxy server with username and password is possible by using a JSON configuration file proxy.settings.json that has to be copied into the Connect installation directory:
{
"Proxy": {
"Enabled": false,
"Uri": "http://127.0.0.1:8888",
"UserName": "proxyUser",
"Password": "",
"PlainTextPassword": "proxyPassword"
}
}
The hosts iam.teccom.de, solutionportal.tecalliance.net, staging-solutionportal.tecalliance.net and teccmd.tecalliance.net don't have static IP addresses. If you are unable to make an exception in your firewall based on the hosts, you will have to make exceptions for all IP addresses of regions eu-central-1 and eu-west-1 as published by Amazon Web Services here: AWS IP address ranges. ↩︎ ↩︎ ↩︎ ↩︎
The hosts tecconnectsbprod.servicebus.windows.net and tecconnectsb2prod.servicebus.windows.net do not have static IP addresses. If you are unable to make exceptions in your firewall based on the hosts, you will have to make exceptions for all IP addresses of tags AzureCloud.westeurope and AzureCloud.northeurope as published by Microsoft here: Download Azure IP Ranges and Service Tags. It is also recommended to make exceptions for the IP addresses of the tags ServiceBus.WestEurope and ServiceBus.NorthEurope in case the two hosts ever get assigned IP addresses from these ranges. ↩︎ ↩︎
It is recommended to open ports 5671 and 5672 to allow Connect 5 the usage of Azure Service Bus' native AMQP protocol. If this is not possible, the Connect 5 falls back on communicating with Azure Service Bus via port 443. ↩︎ ↩︎
The hosts tecconnectstorageprod.blob.core.windows.net and tecconnectstorageprod.table.core.windows.net do not have static IP addresses. If you are unable to make exceptions in your firewall based on the hosts, you will have to make exceptions for all IP addresses of the tag Storage.WestEurope as published by Microsoft here: Download Azure IP Ranges and Service Tags. ↩︎ ↩︎
The hosts connect-api.tecalliance.net and teccom.tecalliance.net do not have a static IP addresses. If you are unable to make an exception in your firewall based on the hosts, you will have to make exceptions for all IP addresses of the tag AppService as published by Microsoft here: Download Azure IP Ranges and Service Tags. ↩︎ ↩︎