Domain names or IP addresses
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 BIM Server’s usage the following address types can be used:
- FQDN (Fully Qualified Domain Name), example: server.company.com
- fixed public IP address, example: 188.8.131.52
- fixed private IP address, example: 192.168.1.10
|Type of use||v18||v19, v20|
|Mixed (internal, external)||FQDN||FQDN and/or fixed public IP address|
|Only internal||FQDN or fixed private IP address||FQDN and/or fixed private IP address|
|Only external||FQDN or fixed public IP address||FQDN and/or fixed public IP address|
- IPv6 is not supported; always use IPv4 addresses.
- If IP addresses are used, make sure that they are static.
- 127.0.0.1 is a special loopback IP of the localhost. It means “this computer”. You can use it to open BIMcloud or BIM Server Manager on the computer where the server is installed, but you should not use it to share projects in ARCHICAD, or to pair BIMcloud servers
- In version 18 Do not mix different URLs, like domain names and IP addresses. Use the same URL from all locations. Failure to do so may result in unavailable linked content, such as libraries and hotlinks. From version 19 it is possible to use different addresses to access the BIM Server, it can be set up in the BIMcloud or BIM Server Manager Connection settings.
Mixed internal and external use
Scenario: The server is accessed from both the local area network and over the Internet.
In such cases, there is a difference between version 18 and from version 19. In version 18, always create and use a Fully Qualified Domain Name for the server – like bimserver.example.com. Use the address whenever accessing the server, regardless of the location. The DNS server(s) will resolve this name to the appropriate IP address: to private IP from the internal network and to public IP over the Internet.
From version 19, fixed public IP is required and FQDN is recommended for the computer that runs the BIM Server.
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, 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.
Format of URLs
To access the BIMcloud or BIM Server 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:
Use the same format from ARCHICAD as well. From version 19 more addresses can be added in the BIMcloud or BIM Server Manager Connection settings.
Your local IT should be able to answer all of these questions. The following hints can help to cover the basics:
DNS name, host name
- System Preferences > Sharing > Computer name
- This PC > Right click > Properties > Full computer name
- Perform a Google search for “public IP address”. It will return your public IP address.
- System Preferences > Network
- or give the ifconfig command in Terminal
- Control Panel > Network and sharing center > Click on the text next to Connections > Details
- or give the ipconfig command in the Command Prompt
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.
- On the server side you will need to open the incoming ports
- On the client side you will need to open the outgoing ports
If there are more versions of BIM Server installed on the same computer, make sure to set up different ports for the different versions.
The default ports used by the BIMcloud:
|BIMcloud Delta Cache (BIMcloud Proxy) *||9921||9921||9921|
* As the BIMcloud Delta Cache (BIMcloud Proxy) is a local caching service, there is no need to open this port on external firewalls only on the host computer.
The default ports used by the BIM Server:
|BIM Server Manager||1228||19000||20000|
|BIM Server module||18008||19001||20001|
Protocols and encryption
BIMcloud or BIM Server 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:
- Use HTTPS to secure the communication. For this you will need a Reverse Proxy on the server side that will perform the SSL encryption between ARCHICAD and the Reverse Proxy
- Use VPN, which will encrypt the communication
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 the BIMcloud / BIM Server, which can generate a large amount of network traffic. Theoretically BIMcloud / BIM Server 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:
|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|
- The Project size refers to the size of the project database and not the PLN file that was shared. Project database are generally 3-5 times larger than PLN files.
- The Bandwidth values are NOT refering to the theoretical maximum, they are representing the actual measured bandwidth per ARCHICAD user in a general situation – when everyone is working at the office. Therefore for example if 10 users would like to download 10 different projects with 100-300 MB in size at the same time, then they would need at least a 100/100 Mbps connection to have an acceptable download speed.
- At the server side both upload and download speed must be high.
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.
- Good: 1-2 ms
- Average: 10-50 ms
- Acceptable: 50-100 ms
- Poor: 100+ ms (serious performance issues might arise)