Before installing any server products, consider how the server(s) will be accessed by clients (Archicad, BIMx) and other servers (BIMcloud). Plan for a long-term solution to avoid any unnecessary work. If there is a chance of having communication over the Internet, make sure you have the needed setup.
Depending the type of the BIMcloud's usage the following address types can be used:
Type of use | from 2020.2 |
---|---|
Mixed (internal, external) | FQDN and/or fixed public IP address |
Only internal | FQDN and/or fixed private IP address |
Only external | FQDN and/or fixed public IP address |
Mixed internal and external use
Scenario: The server is accessed from both the local area network and over the Internet.
From version 19, fixed public IP is required and FQDN is recommended for the computer that runs BIMcloud.
Only internal use
Scenario: The server is accessed only from the local area network.
In this case, you can use either the FQDN of the computer or the fixed private IP.
Only external use
Scenario: A typical example is a computer hosted in the cloud (Microsoft Azure, Amazon, Google etc.) which is thus always accessed over the Internet.
In this case, use either the FQDN of the computer or its fixed public IP address.
To access the BIMcloud Manager, open a web browser and type the combined address and port into the browser's address bar. For the default port numbers see the "Ports" section. Examples of the address format:
http://server.company.com:port
Use the same format from Archicad as well. From version 19 more addresses can be added in the BIMcloud Manager Connection settings.
The GRAPHISOFT server products use the following default ports. Open these ports on all related firewalls and forward them in the router's settings if necessary for public access over the Internet.
If there are more than one BIMcloud Basic installed on the same computer, make sure to set up different ports for the different versions.
The default ports used by BIMcloud:
Application | from 2020.2 |
---|---|
BIMcloud Manager | 22000 |
BIMcloud Server | 22001 |
BIMcloud Delta Cache * | 9921 |
* As the BIMcloud Delta Cache is a local caching service, there is no need to open this port on external firewalls only on the host computer.
BIMcloud components are web-servers communicating over the standard HTTP protocol with Archicad and BIMx.
If you have an HTTP Forward Proxy setup in your office, make sure to configure it to allow Teamwork related communication through.
To encrypt the network traffic, the following alternatives are available:
Related versions: BIMcloud v19 and newer, BIMcloud as a Service
The proper operation of Teamwork requires high-speed network connections. Although the amount of Teamwork traffic is kept as low as possible, during a joining process all Archicad users have to download the whole project and the affected libraries from BIMcloud, which can generate a large amount of network traffic. Theoretically BIMcloud can work on very low bandwidth networks but more patience is needed when working with Teamwork over a low bandwidth connection.
See our bandwidth recommendation based on project sizes below:
Project size | Bandwidth (upload/download) | Upload / Download speed |
---|---|---|
100 - 300 MB | 10/10 Mbps | ~1 MB per second |
300 MB - 2 GB | 100/100 Mbps | ~12 MB per second |
2+ GB | 1/1 Gbps | ~125 MB per second |
Related versions: BIMcloud v19 and newer, BIMcloud as a Service
The higher the latency, the slower the round-trip between the server and the client computer. Slow round-trips vastly effect operations that require many packet exchanges between the client and server for example Send&Receive operations. If the latency is high, it can impair Teamwork performance even if the bandwidth itself is high.