FAQs
TecCom AWS Migration
Thank you for visiting our page with the frequently asked questions regarding our migration to Amazon Web Services (AWS).
To be ready for the future, we decided to change our service provider and migrate our systems to AWS. Thanks to the migration, we can offer you already in the short term more stability, security and performance, and in the long term more functionality.
After the first part of the migration (implemented in March 2022), which only affected the order customers, all other TecCom solutions(e-Invoicing, CMD, CMI and Returns & Warranty) will be migrated in the second part of the migration to AWS. This also could have impact on order customers using TOM (TecOpenMessaging) webservice if the old URL’s are still used for sending messages to TecCom.
The FAQ page has been adapted and contains information about the entire migration
- e-Invoicing
- CMD
- CMI
- Warranty
- Order
First of all: Your existing business processes will continue to work like they do now. Depending on how you communicate with us it can be necessary, though, to change a few settings on your side. This mainly concerns the IP addresses of our systems to which you send and from which we send. And it concerns the deprecation of support for certain SSL encryption which are too old and are a security risk.
You can find out if you have to change something in the following questions and answers section. We will extend this section as required to make sure that you always can find the most up-to-date information.
What do I have to do?
Once we migrate to AWS our systems will be assigned new public IP addresses. That also means we will send from new public IP addresses.
This is relevant for all TecCom solutions.
- Make sure that you can connect to our new public IP addresses from your corresponding systems. This may require that you modify the settings of your firewall.
- Make sure that your corresponding systems can be reached from our new public IP addresses. This may require that you modify the settings of your firewall.
- Make sure that your corresponding systems support the SSL encryption methods used by us. In the worst case this may require that you change your operating system if, for example, you still use a very old operating system like Windows Server 2003.
In addition, we will try to connect to your systems from our new public IP addresses. If we encounter problems there, we will inform you at once.
Will message contents or formats change?
No. All changes are purely technical and concern exclusively the network communication. There will be no changes of message contents or formats of any kind.
Which solutions are affected?
The following TecCom solutions are affected:
- e-Invoicing (invoices, credit notes)
- CMD (article master, price and inventory data)
- CMI (inventory, sales history and order proposal)
- TecWarranty
- TecOrder/Connect 5 (only sending messages via old TOM webservice address)
Please note: Not affected by this change are our customers only using the TecCom Portal (old names: TecWeb / Order Manager Portal).
When do I have to check and maybe change something?
Not every customer integration is affected by the migration. Please have a look at the following table to see if you have to check and maybe change your communication with TecCom.
Sending:
This concerns all messages that you send to the TecCom Network.
You must ensure that you can reach the new public IP addresses before we migrate the systems.
Please note, pulling data(retrieving messages) from TecCom is triggered by sending a message
Receiving:
This concerns all messages that you receive from the TecCom Network.
Here we will try to connect to your systems from our new public IP addresses. If we encounter problems there, we will inform you at once.
e-Invoicing
| Application / Interface | Sending | Receiving |
|---|---|---|
| Dispatcher |  check needed | n.a. |
| Solution Portal GUI | check needed | n.a. |
| Rest webservice | check needed | n.a. |
| Pull Client | n.a. | check needed |
| TOM SOAP Webservice (TCC / TomConnect / self-developed software = WSDL ) | check needed | check needed |
| AS2 / OFTP / SFTP / X400 / All connections through Retarus |  no check needed | no check needed |
| SMTP | n.a. | no check needed |
CMD
| Application / Interface | Sending | Receiving |
|---|---|---|
| CMD Portal | check needed | n.a. |
| Solution Portal GUI | check needed | n.a. |
| TOM SOAP Webservice (TCC / TomConnect / self-developed software = WSDL ) | check needed | n.a. |
| AS2 / OFTP / SFTP / X400 / All connections through Retarus | no check needed | no check needed |
| FileTransfer Client/SAP | check needed | n.a. |
CMI
| Application / Interface | Sending | Receiving |
|---|---|---|
| RDP | check needed | n.a. |
| TOM SOAP Webservice (TCC / self-developed software = WSDL ) | check needed | no check needed |
| FTP | check needed | no check needed |
TecWarranty
| Application / Interface | Sending | Receiving |
|---|---|---|
| Solution Portal GUI | check needed | n.a. |
| TOM SOAP Webservice (TCC / TomConnect / self-developed software = WSDL ) | check needed | check needed |
Order
| Application / Interface | Sending | Receiving |
|---|---|---|
| TecCom Portal (old name: TecWeb / Order Manager Portal) | no check needed | no check needed |
| TecConnect 4.1 and older / TecLocal | already migrated | already migrated |
| Connect 5 | check needed if URL solutionportal.tecalliance.net or interact.teccom-eu.net is still used. | no check needed |
| TOM SOAP Webservice (TCC / TomConnect / self-developed software = WSDL ) | check needed if URL solutionportal.tecalliance.net or interact.teccom-eu.net is still used. | already migrated |
| AS2 / OFTP / SFTP / X400 / All connections through Retarus | no check needed | no check needed |
| SMTP | – | no check needed |
| FTP | no check needed | no check needed |
| Auto-gration | already migrated | no check needed |
What are the new public IP addresses?
Below you can find our new public IP addresses. Please create exceptions for all of them in your firewall.
For the sake of stability and disaster recovery it is possible that the systems will be switched from main to standby (from one set of IP addresses to the other), so it is very important that you make exceptions for all IP addresses.
In case you do not allow traffic from the Standby IP addresses through your firewall, this could result in unavailability in case of disaster recovery. (Download the new IP overview)
Note that we have different IP addresses for sending and receiving!
Public IP addresses for messages sent to the TecCom Network
For messages sent to the TecCom Network (www.teccom.de, iam.teccom.de, solutionportal.tecalliance.net, interact.teccom-eu.net and teccmd.tecalliance.net) we use the dynamic IP addresses registered from AWS for the regions “eu-central-1” and “eu-west-1”.
At the moment it is not foreseen to use static IP addresses for these connections. If you have the need to for IP address whitelisting for outgoing traffic and cannot use a proxy please contact us.
Public IP addresses for messages received from the TecCom Network
| Region | Main systems | Standby systems |
|---|---|---|
| Frankfurt | 18.198.154.4 | |
| 3.64.249.68 | ||
| 3.65.19.66 | ||
| 3.65.82.255 | ||
| Ireland | 54.171.143.224 | |
| 99.81.17.188 |
Which SSL encryption methods will be supported?
With the migration we will support the following SSL encryption protocols and methods.
Protocols
| Protocol |
|---|
| TLS 1.0 |
| TLS 1.1 |
| TLS 1.2 |
SSL2 and SSL3 are not supported!
Cipher Suites
| TLS 1.2 (highest to lowest priority) |
|---|
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| TLS_RSA_WITH_AES_128_GCM_SHA256 |
| TLS_RSA_WITH_AES_128_CBC_SHA256 |
| TLS_RSA_WITH_AES_128_CBC_SHA |
| TLS_RSA_WITH_AES_256_GCM_SHA384 |
| TLS_RSA_WITH_AES_256_CBC_SHA256 |
| TLS_RSA_WITH_AES_256_CBC_SHA |
| TLS 1.1 (highest to lowest priority) |
|---|
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| TLS_RSA_WITH_AES_128_CBC_SHA |
| TLS_RSA_WITH_AES_256_CBC_SHA |
| TLS 1.0 (highest to lowest priority) |
|---|
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| TLS_RSA_WITH_AES_128_CBC_SHA |
| TLS_RSA_WITH_AES_256_CBC_SHA |
Which operating systems will be supported?
| Client | Operating system | Service Pack needed | TLS version |
|---|---|---|---|
| IE 7 | Windows Vista | SP2 | TLS 1.0 |
| IE 7 | Windows Server 2008 | SP2 | TLS 1.0 |
| IE 8 – 11 | Windows 7 | SP2 | TLS 1.0 |
| IE 8 – 11 | Windows Server 2008 R2 | SP1 | TLS 1.0 |
| IE 11 | Windows 8 | TLS 1.2 | |
| IE 11 | Windows Server 2012 | TLS 1.2 | |
| IE 11 | Windows Server 2012 R2 | TLS 1.2 | |
| IE 11 | Windows 10 | TLS 1.2 | |
| IE 11 | Windows Server 2016 | TLS 1.2 | |
| IE 11 | Windows Server 2019 | TLS 1.2 |
Windows Server 2003 and older will no longer be supported.
Which URL do I have to use in the future?
e-Invoicing
- solutionportal.tecalliance.net or
- interact.teccom-eu.net
CMD
- solutionportal.tecalliance.net or
- interact.teccom-eu.net or
- teccmd.tecalliance.net
CMI
- cmi.tecalliance.net or
- solutionportal.tecalliance.net or
- interact.teccom-eu.net
Warranty
- solutionportal.tecalliance.net or
- interact.teccom-eu.net
Order
- https://iam.teccom.de/tecdirect/tomdirect.svc
TecOrder Messages sent via TOM Webservice should use the new TecOrder URL:
- https://iam.teccom.de/tecdirect/tomdirect.svc
Messages of other TecCom solutions must be sent to the existing URL`s.
How can I test the new connection?
You can open https://iam.teccom.de in the browser (please use the Internet Explorer / Edge as other browsers do not use the Windows SSL Libraries). You should see a website if the connection is successful, and you should not receive any warnings or errors.
But for this test you have to make sure that you execute it on the same server where your TecCom application is running.
Receiving messages from the TecCom Network
We will test the connection to your systems from our side and inform you in case of any problems.
What will happen to my data and configurations?
All your data and configurations in our systems will be migrated to AWS before we go live. We will perform integrity and plausibility checks before going live to ensure the sustainability of all data and configurations.
You can work with TecCom as usual up until shortly before we go live. All changes done up to this point, for example, business relations, will be included in the migration.
Where will the systems be hosted?
Our systems will be hosted with Amazon Web Services in the EU regions Frankfurt and Ireland.
When will the migration be happening?
The migration will take place in Q3 2022.