User Data from BIM Server for ARCHICAD 18 or 19
User Data from BIM Server for ARCHICAD 17 and Earlier
Upgrade BIM Server to BIMcloud
ARCHICAD Network Installation(Instructions for BIM Managers)
–
|
24)
|
Using a CodeMeter Server
•
|
4)
|
•
|
–
|
Avoid Conflicting Work Sessions in Teamwork Projects
•
|
Discard Changes and re-Open: Open the project, losing the changes.
|
•
|
Save solo Project: If you do not want to lose the changes, your only option is to save this version of the project as a solo project. Your edits will remain, but you can no longer send them in directly to the BIM Server. You can, however, manually paste your elements into the Teamwork project.
|
Wall Tool Settings
•
|
Optionally, define an offset for the Wall top from its top linked story (the Wall height changes accordingly). This offset value can be positive, negative or zero.
|
•
|
The current story: The Wall’s Home Story will be the current story, on which it is placed.
|
•
|
Choose a story to which to link the bottom of the Wall. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Optionally, define an offset for the Wall bottom from its Home Story. (For a top linked Wall, the Wall height changes accordingly.)
|
•
|
For a Basic Wall: use the pop-up to choose its Building Material.
|
•
|
For a Composite Wall: use the pop-up to choose its Composite structure.
|
•
|
•
|
The thickness of a composite Wall is the total value of the individual skins as set in Options > Element Attributes > Composites. If you are creating a composite Wall, the thickness field is consequently not editable here.
|
•
|
All Relevant Stories: A multi-story wall will be displayed and editable on all stories which it intersects. Multi-story walls will be correctly joined with other elements on all stories where the multi-story wall is present.
|
•
|
Home Story Only: This wall will be displayed only on its Home Story.
|
•
|
Projected: shows cut part of Wall’s 3D model, plus its uncut (downward) part.
|
•
|
Projected with Overhead: shows cut part of Wall’s 3D model (i.e. as cut at the level of the Floor Plan Cut Plane), plus the Wall’s overhead part (i.e. the part of the Wall that is above the Floor Plan Cut Plane.
|
•
|
Cut Only: displays only the cut part, as cut with the Floor Plan Cut Plane.
|
•
|
Symbolic Cut: Available only for simple straight Walls. This option is available only if the Show on Stories control is set to “Current/Home Story only”.
|
•
|
Outlines Only: the entire Wall’s outline is shown using its uncut attributes.
|
•
|
Overhead All: the entire Wall’s outline is shown using its overhead attributes.
|
•
|
To Floor Plan Range: Choose to show the Wall on a range of stories (the current story, plus a given number of stories above and below it.)
|
•
|
To Absolute Display Limit: Set a fixed lower limit (by default, this is Project Zero), then show all parts of the Wall above this limit.
|
•
|
Entire Element: The Wall will be displayed on all relevant stories.
|
•
|
For a basic Wall:
|
•
|
•
|
If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
In this case, the Reset Texture button is also activated. Click to restore the origin of the Texture of the selected wall.
|
•
|
Use Log Wall: Check this box to use a Log Wall. If it is unchecked, no logs will be displayed.
|
•
|
Start with half log: If this checkbox is active, the wall will start with a half-height log at the bottom.
|
•
|
Square logs: Use square logs on both sides of the wall.
|
•
|
Rounded on Outside Face: Use logs that are cambered on the outside face. The inside wall face will remain flat.
|
•
|
Rounded on Inside Face: Use logs that are cambered on the inside. The outside wall face will remain flat.
|
•
|
Log Radius: choose an option for measuring log radius: either from the log centerpoint, or from the middle point of the opposite log.
|
•
|
As in Wall Settings: Click this radio button to apply the Building Material’s surface to Log walls.
|
•
|
Override with Outside Face Surface: Click this radio button to use the outside face surface on horizontal surfaces of Log walls.
|
•
|
Override with Inside Face Surface: Click this radio button to use the inside face surface for horizontal surfaces of Log walls.
|
•
|
Zone Boundary: This option means that a wall located inside a zone will not be included in the zone area. In every case, including slanted or complex walls, the zone boundary is drawn at the base of the wall. Multi-story elements in automatic display mode can serve as zone boundaries on any story on which they exist, not just their Home Story.
|
•
|
Reduce Zone Area Only means that the 2D zone will encompass the wall, but the wall area will not be included in the zone area. (Zone Volume, however, will include the wall.)
|
•
|
Subtract from Zones means that when calculating the zone’s 3D volume, the volume will not include the volume of any wall located inside the zone.
|
•
|
No Effect On Zones means that the wall has no effect on the zone; the zone area and volume will include the area covered by the wall.
|
Roof Tool Settings
•
|
Current: The Roof’s Home Story will be the Current Story.
|
•
|
Select Home Story: Choose a story to which to link the Roof. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
For a Basic Roof: use the pop-up to choose its Building Material.
|
•
|
Roof Thickness: Enter a value for the thickness of the roof pane, measured either perpendicularly or vertically to the face of the roof. Click the pop-up arrow to choose a way to measure the roof thickness.
|
•
|
For a Composite Roof: use the pop-up to choose its Composite structure.
|
•
|
All Relevant Stories: A multi-story roof will be displayed and editable on each story it intersects.
|
•
|
Home Story only: The outline of the entire multi-story roof will be displayed and editable on its Home Story only.
|
•
|
All Stories: The outline of the entire Roof will be displayed (using its uncut and overhead line settings) on every story of the project, with overhead attributes.
|
•
|
Custom: Choose this option if you wish to show the Roof on any other combination of stories. The Show on Stories: Custom Settings dialog box appears, where you can set separate story display options for the roof’s outline and its fill.
|
•
|
Projected with Overhead: shows cut part of element (i.e, as cut at the level of the Floor Plan Cut Plane), plus the element’s overhead part (i.e. the part of the element that is above the Floor Plan Cut Plane.
|
•
|
Projected: shows cut part of element’s 3D model, plus its uncut (downward) part.
|
•
|
Cut Only: displays only the cut part, as cut with the Floor Plan Cut Plane.
|
•
|
Outlines Only: the entire element’s outline is shown using its uncut attributes. The line type will vary depending on the Roof’s location with respect to the Floor Plan Cut Plane:
|
•
|
Overhead All: the entire element’s outline is shown using its overhead attributes.
|
•
|
to Floor Plan Range: Choose to show the element on a range of stories (the current story, plus a given number of stories above and below it.)
|
•
|
to Absolute Display Limit: Set a fixed lower limit (by default, this is Project Zero), then show all parts of the element above this limit.
|
•
|
Entire Element: The element will be displayed on all relevant stories.
|
•
|
For a basic Roof: define the cut line type and pen.
|
•
|
For a basic or composite: If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
Use Fill from Surface: Check this box if you want your cover fill to resemble the element’s top surface (vectorial 3D hatch), either as defined in the Building Material or (if the override is on) its top surface override
|
•
|
Link to Project Origin: The fill pattern will start at the Project Origin, and the part of the pattern that falls within the Fill’s boundary will be displayed. No fill handle appears.
|
•
|
Link to Fill Origin: If you choose this option, then the cover fill will show a fill handle when you place the roof on the Floor Plan. You can then manipulate the fill orientation by selecting and moving the fill handle. (Use the “Move Sub-Element” command from the pet palette.)
|
•
|
•
|
Distort with Pitch (available only if you have checked Align with Pitch): Check this box to distort the cover fill. This effect stimulates the effect of a sloped roof as seen from above on the Floor Plan.
|
•
|
In the table, adjust the pitch of any roof level as needed.
|
•
|
Elevation refers to the point at which the new level begins:
|
•
|
Offset: Enter a value for the distance of the eaves overhang from the pivot polygon. This value is applied to the Roof as a whole.
|
•
|
Manual: The overhang value control changes to “Manual” if you edit the roof contour graphically.
|
•
|
By arc: Divides the curved plane(s) into the given number of segments.
|
•
|
By circle: Divides a full circle into the given number of segments, and applies that geometry to the curved plane(s) of the Roof.
|
Shell Tool Settings
•
|
Current: The Shell’s Home Story will be the Current Story.
|
•
|
Select Home Story: Choose a story to which to link the Shell. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
For a Basic Shell: use the pop-up to choose its Building Material.
|
•
|
For a Composite Shell: use the pop-up to choose its Composite structure.
|
•
|
•
|
•
|
•
|
Revolution angle: Angle of revolution of the Shell around its axis.
|
•
|
Distortion angle: Angle of the axis of the revolved Shell, measured to the Shell plane angle. Modifying the distortion angle will affect the Shell profile. (Changing the slant angle alone, which is available through graphical editing, will not change the Shell profile, only “tip” it over.)
|
•
|
By circle: Divides a full circle into the given number of segments, and applying that geometry to the existing arc of the Shell.
|
•
|
By arc: Divides the existing arc of the Revolved Shell into the given number of segments.
|
•
|
All relevant stories: The Shell will be displayed and editable on each story it intersects.
|
•
|
Home Story only: The outline of the Shell will be displayed and editable on its Home Story only.
|
•
|
Projected: shows cut part of element’s 3D model, plus its uncut (downward) part.
|
•
|
Projected with Overhead: shows cut part of element’s 3D model (i.e, as cut at the level of the Floor Plan Cut Plane), plus the element’s overhead part (i.e. the part of the element that is above the Floor Plan Cut Plane.
|
•
|
Cut Only: displays only the cut part, as cut with the Floor Plan Cut Plane.
|
•
|
Outlines Only: the entire element’s outline is shown using its uncut attributes. The line type will vary depending on the Shell’s location with respect to the Floor Plan Cut Plane:
|
•
|
Overhead All: the entire element’s outline is shown using its overhead attributes.
|
•
|
to Relative Floor Plan Range: Choose to show the element on a range of stories (the current story, plus a given number of stories above and below it.)
|
•
|
to Absolute Display Limit: Set a fixed lower limit (by default, this is Project Zero), then show all parts of the element above this limit.
|
•
|
Entire Element: All visible parts of the element will be displayed.
|
•
|
For a basic Shell: define the cut line type and pen.
|
•
|
For a basic or composite: If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
Use Fill from Surface: Check this box if you want your cover fill to resemble the surface material (vectorial 3D hatch) assigned to this Shell, either as defined in the Building Material or (if the override is on) its top surface override in the Model panel
|
•
|
Link to Project Origin: The fill pattern will start at the Project Origin, and the part of the pattern that falls within the Fill’s boundary will be displayed. No fill handle appears.
|
•
|
Link to Fill Origin: If you choose this option, then the cover fill will show a fill handle when you place the Shell on the Floor Plan. You can then manipulate the fill orientation by selecting and moving the fill handle. (Use the “Move Sub-Element” command from the pet palette.)
|
•
|
Distorted: This option will distort the cover fill, simulating the 3D view of a curved surface on the Floor Plan.
|
•
|
Slab Tool Settings
•
|
Current: The Slab’s Home Story will be the Current Story.
|
•
|
Select Home Story: Choose a story to which to link the Slab. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Click the pop-up arrow to change the Reference level, if needed. Reference levels are defined at Options > Project Preferences > Reference Levels.
|
•
|
For a Basic Slab: use the pop-up to choose its Building Material.
|
•
|
For a Composite Slab: use the pop-up to choose its Composite structure.
|
•
|
Home Story only: The outline of the entire slab will be displayed and editable on its Home Story only.
|
•
|
All Stories: The outline of the entire slab will be displayed on every story of the project.
|
•
|
•
|
Custom: Choose this option if you wish to show the slab on any other combination of stories. The Show on Stories: Custom Settings dialog box appears, where you can set separate story display options for the slab outline and its fill.
|
•
|
For a basic Slab:
|
•
|
•
|
If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
Use Fill from Surface: Check this box if you want your cover fill to resemble the element’s top surface (vectorial 3D hatch), either as defined in the Building Material or (if the override is on) its top surface override
|
•
|
Link to Fill Origin: If you choose this option, then the cover fill will show a fill handle when you place the slab on the Floor Plan. You can then manipulate the fill orientation by selecting and moving the fill handle. (Use the “Move Sub-Element” command from the pet palette.)
|
•
|
Link to Project Origin: The fill pattern will start at the Project Origin, and the part of the pattern that falls within the Fill’s boundary will be displayed. No fill handle appears.
|
•
|
Distorted Fill: The Fill pattern can be distorted by altering the lengths and directions of its double fill handle.
|
•
|
In this case, the Reset Texture button is also activated. Click to restore the origin of the Texture of the selected slab.
|
Column Tool Settings
•
|
Optionally, define an offset for the Column top from its top linked story. (For a top linked Column, the Column height changes accordingly.) This offset value can be positive, negative or zero.
|
•
|
The current story: The Column’s Home Story will be the current story, on which it is placed.
|
•
|
Choose a story to which to link the bottom of the Column. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Optionally, define an offset for the Column bottom from its Home Story (the Column height changes accordingly).
|
•
|
•
|
If you choose the slanted column, enter the slant value in degrees into the Slant angle field to the right.
|
•
|
All Relevant Stories: A multi-story column will be displayed and editable on all stories which it intersects. Multi-story columns will be correctly joined with other elements on all stories where the multi-story column is present.
|
•
|
Home Story Only: This column will be displayed only on its Home Story.
|
•
|
Projected: shows cut part of element’s 3D model, plus its uncut (downward) part.
|
•
|
Projected with Overhead: shows cut part of element’s 3D model (i.e., as cut at the level of the Floor Plan Cut Plane), plus the element’s overhead part (i.e. the part of the element that is above the Floor Plan Cut Plane.
|
•
|
Cut Only: displays only the cut part, as cut with the Floor Plan Cut Plane.
|
•
|
Symbolic Cut: Available only for vertical columns. The whole floor plan projection of a vertical column (either simple or complex) will be displayed as cut, using its cut line and Building Material attributes, regardless of the column’s vertical position. This option is available only if the Show on Stories control is set to “Home Story only”. The Floor Plan Cut Plane settings do not affect the display of such a column.
|
•
|
Outlines Only: the entire element’s outline is shown using its uncut attributes.
|
•
|
Overhead All: the entire element’s outline is shown using its overhead attributes.
|
•
|
to Floor Plan Range: Choose to show the element on a range of stories (the current story, plus a given number of stories above and below it.)
|
•
|
to Absolute Display Limit: Set a fixed lower limit (by default, this is Project Zero), then show all parts of the element above this limit.
|
•
|
Entire Element: The element will be displayed on all relevant stories.
|
•
|
If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
Symbol Type: Choose this parameter, then activate its arrow pop-up to choose one of four crossing symbols: Plain (no cross), Slash, X, and Crosshair.
|
•
|
In this case, the Reset Texture button is also activated. Click to restore the origin of the Texture of the selected column.
|
•
|
Zone Boundary (not available for slanted columns): This option means that a vertical column located inside a zone will not be included when the zone area or zone volume is calculated. The zone boundary is drawn at the base of the column. Multi-story elements in automatic display mode can serve as zone boundaries on any story on which they exist, not just their Home Story.
|
•
|
Reduce Zone Area Only means that the2D zone will encompass the column, but the column area will not be included in the zone area. (Zone Volume, however, will include the column.)
|
•
|
Subtract from Zones means that when calculating the zone’s 3D volume, the volume will not include the volume of any column located inside the zone. The 2D Zone will not include the Column area either.
|
•
|
No Effect On Zones means that the column has no effect on the zone; the zone area and volume will include the area covered by the column.
|
Beam Tool Settings
•
|
Beam Height: Enter a value for the height of the Beam.
|
•
|
Reference Axis Offset to Home Story: Enter a value here for the Beam’s elevation from the Home Story.
|
•
|
Bottom Elevation [to Reference level]: Calculates the current elevation of the Beam’s reference axis, as measured from the Reference level (by default, this Reference level is Project Zero). Click the pop-up arrow to change the Reference level, if needed.
|
•
|
The current story: The Beam’s Home Story will be the current story, on which it is placed.
|
•
|
Choose a story to which to link the Beam’s reference axis. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Enter a value for the Beam width.
|
•
|
Use the pop-up to choose its Building Material.
|
•
|
All Relevant Stories: A beam will be displayed and editable on all stories which it intersects. Beams will be correctly joined with other elements on all stories where it is present.
|
•
|
Home Story Only: This beam will be displayed only on its Home Story.
|
•
|
Other options are to display the beam on All Stories; or its Home story plus one story up and/or down.
|
•
|
Projected: shows cut part of element’s 3D model, plus its uncut (downward) part.
|
•
|
Projected with Overhead: shows cut part of element’s 3D model (i.e., as cut at the level of the Floor Plan Cut Plane), plus the element’s overhead part (i.e. the part of the element that is above the Floor Plan Cut Plane.
|
•
|
Cut Only: displays only the cut part, as cut with the Floor Plan Cut Plane.
|
•
|
Outlines Only: the entire element’s outline is shown using its uncut attributes.
|
•
|
Overhead All: the entire element’s outline is shown using its overhead attributes.
|
•
|
to Floor Plan Range: Choose to show the element on a range of stories (the current story, plus a given number of stories above and below it.)
|
•
|
to Absolute Display Limit: Set a fixed lower limit (by default, this is Project Zero), then show all parts of the element above this limit.
|
•
|
Entire Element: The element will be displayed on all relevant stories.
|
•
|
For a rectangular Beam:
|
•
|
•
|
If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Overhead Lines will be displayed if the Floor Plan Display pop-up is set to “Projected with Overhead” or “Overhead All”.
|
•
|
Uncut Lines will be displayed if the Floor Plan Display pop-up is set to “Projected” or “Outlines Only.”
|
•
|
Beam End Lines: These options let you show or hide one or both end lines of the beam. (The end line is the contour line perpendicular to the longitudinal axis of the beam.)
|
•
|
Show Reference axis: Check this box to display the beam’s centerline in the 2D window.
|
•
|
In this case, the Reset Texture button is also activated. Click to restore the origin of the Texture of the selected beam.
|
Zone Tool Settings
•
|
Optionally, define an offset for the Zone top from its top linked story (the Zone height changes accordingly). This offset value can be positive, negative or zero.
|
•
|
The current story: The Zone’s Home Story will be the current story, on which it is placed.
|
•
|
Choose a story to which to link the bottom of the Zone. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Optionally, define an offset for the Zone bottom from its Home Story (When top linked, the Zone height changes accordingly.) The subfloor thickness remains constant.
|
•
|
Net: Zone polygon will not be displayed beyond the inner edge of the boundary walls.
|
•
|
Gross: Full zone polygon is displayed.
|
–
|
•
|
Fixed Angle: To keep the Zone Stamp Angle fixed relative to the screen, even if you rotate the view, check the Fixed Angle checkbox. To allow the Zone Stamp to rotated along with the view, leave the checkbox empty.
|
•
|
Link to Project Origin: The fill pattern will start at the Project Origin, and the part of the pattern that falls within the Fill’s boundary will be displayed. No fill handle appears.
|
•
|
Link to Fill Origin: If you choose this option, then the cover fill will show a fill handle when you place the zone on the Floor Plan. You can then manipulate the fill orientation by selecting and moving the fill handle. (Use the “Move Sub-Element” command from the pet palette.)
|
•
|
Use this Surface on All Zone Faces: Click this option to display all zone faces of the 3D zone shape using the single surface you selected with the pop-up above.
|
•
|
Inherit Boundary Walls and Cropping Elements Surfaces: Click this option to have individual surface polygons of the zone inherit the corresponding surfaces of boundary walls and any elements that you cropped the Zone with.
|
•
|
Freestanding Walls and Columns within the zone area: The space occupied by Walls and Columns can be partly or entirely subtracted from the zone area, using controls in the Wall/and Column Settings dialog boxes.
|
•
|
Fills: From the total zone area, you can subtract part of the surface occupied by Fills, as set in the Fill’s own settings dialog box.
|
•
|
Low ceilings: If the zone is cut by a roof, the zone area can be reduced accordingly, depending on the settings in Options > Project Preferences > Zones.
|
Mesh Tool Settings
•
|
Current: The Mesh’s Home Story will be the Current Story.
|
•
|
Select Home Story: Choose a story to which to link the Mesh. Click Select Story to bring up the full list of stories in the project, if they are not all shown in the list.
|
•
|
Home Story only: The outline of the entire Mesh will be displayed and editable on its Home Story only.
|
•
|
All Stories: The outline of the entire Mesh will be displayed on every story of the project.
|
•
|
•
|
Custom: Choose this option if you wish to show the Mesh on any other combination of stories. The Show on Stories: Custom Settings dialog box appears, where you can set separate story display options for the slab outline and its fill.
|
•
|
If needed, override the fill foreground/background pens of this element (defined by default in the Building Material). To do this, choose Foreground, Background or Both from the Override Cut Fill Pens pop-up to access the respective controls.
|
•
|
Ridge Selection: Define whether to Show all Ridges or Show User-Defined Ridges (i.e., only those that you have defined when drawing the Mesh.)
|
•
|
Ridge Pen: Use the pop-up to assign a pencolor to both user-defined and generated ridges.
|
•
|
Use Fill from Surface: Check this box if you want your cover fill to resemble the element’s top surface (vectorial 3D hatch), either as defined in the Building Material or (if the override is on) its top surface override
|
•
|
Link to Fill Origin: If you choose this option, then the cover fill will show a fill handle when you place the mesh on the Floor Plan. You can then manipulate the fill orientation by selecting and moving the fill handle. (Use the “Move Sub-Element” command from the pet palette.)
|
•
|
Link to Project Origin: The fill pattern will start at the Project Origin, and the part of the pattern that falls within the Fill’s boundary will be displayed. No fill handle appears.
|
•
|
Distorted Fill: The Fill pattern can be distorted by altering the lengths and directions of its double fill handle.
|
•
|
In this case, the Reset Texture button is also activated. Click to restore the origin of the Texture of the selected beam.
|
•
|
All Ridges Sharp: Show the mesh in the 3D window with sharply connecting triangles.
|
•
|
User Defined Sharp: Show the mesh surfaces with sharply connecting User Defined Ridges, and with smoothly connecting surfaces everywhere else.
|
•
|
All Ridges Smooth: Show the mesh with smoothly connecting surfaces.
|
Curtain Wall Settings
Start and stop BIMcloud manually
Start and stop BIMcloud services using the BIMcloud Control Icon
From version 19 there is an application named BIMcloud Monitor which helps monitoring and managing BIMcloud services. When this application is running, BIMcloud Control Icon appears in the Menu bar/Taskbar which grants quick access to manage BIMcloud services.
To control BIMcloud services click/right click on the BIMcloud Control Icon in the Menu bar/Taskbar. In the pop-up panel it is possible to start/stop/restart all services at once or one by one.
Important notes:
- Although this application has come with version 19, BIMcloud Control Icon can handle BIMcloud Server 18 and newer version services too.
- BIMcloud Control Icon only can manage services which are installed on the same computer as BIMcloud Monitor.
- Both BIMcloud Server and BIMcloud Manager contains BIMcloud Monitor, there is no difference so it does not matter which one is running.
- A second BIMcloud Monitor needs to be run to manage BIMcloud Delta Cache service.
Start and stop BIMcloud services directly
By default BIMcloud is set to start with the computer when it boots. If for any purpose you would like to stop or restart the server or the manager without restarting the computer, follow the description below.
Windows
Overview of services and processes that belong to BIMcloud sorted by versions
v18 | Services | Processes |
---|---|---|
BIMcloud Manager 18 | Graphisoft BIMcloud Manager 18.0 | TeamworkPortalServerManager.exe Node.exe LicenseManager.exe |
BIMcloud Server Module 18 | Graphisoft BIMcloud Server 18.0 | TeamworkApplicationServerMonitor.exe TeamworkApplicationServer.exe Mongod.exe |
BIMcloud Proxy 18 | Graphisoft BIMcloud Proxy 18.0 | TeamworkBlobCacheServer.exe Mongod.exe |
v19 | Services | Processes |
---|---|---|
BIMcloud Manager 19 | Graphisoft BIMcloud Manager 19.0 | TeamworkPortalServerManager.exe Node.exe LicenseManager.exe |
BIMcloud Server Module 19 | Graphisoft BIMcloud Server 19.0 | TeamworkApplicationServerMonitor.exe TeamworkApplicationServer.exe Mongod.exe |
BIMcloud Delta Cache 19 | Graphisoft BIMcloud Delta Cache 19.0 | TeamworkBlobCacheServer.exe Mongod.exe |
v20 | Services | Processes |
---|---|---|
BIMcloud Manager 20 | Graphisoft BIMcloud Manager 20.0 | TeamworkPortalServerManager.exe Node.exe LicenseManager.exe |
BIMcloud Server Module 20 | Graphisoft BIMcloud Server 20.0 | TeamworkApplicationServerMonitor.exe TeamworkApplicationServer.exe Mongod.exe |
BIMcloud Delta Cache 20 | Graphisoft BIMcloud Delta Cache 20.0 | TeamworkBlobCacheServer.exe Mongod.exe |
Monitor, start, restart, stop services
In order to control or check the services open ‘Services’:
- Type either in the run prompt or in the Windows 8 interface’s (Start Menu’s) search field: services.msc
- The same settings can be accessed through the Computer Management (Services and Applications/Services)
There you will find a list of all services. The BIMcloud component (BIMcloud Manager, BIMcloud Server, BIMcloud Proxy/Delta Cache) runs if its service is running. Each service can also be started, stopped and restarted here. To manage the BIMcloud components, simply select the one you are looking for and stop, restart or start.
To control whether the BIMcloud component is automatically started with the computer
- Select the service on the list
- Right click and select properties
- Startup type – change it to Manual
If the services are set to start manually, you will need to start them each time the computer is rebooted.
The best is keeping these settings on automatic, but in some situations the manual setting may be useful:
- if Projects and Libraries (Project and Attachment folder) are stored on external storage, which might be unavailable when the computer boots
- for troubleshooting purposes
OS X
Overview of services (daemons) and processes that belong to BIMcloud sorted by versions
v18 | LaunchDaemons | Processes |
---|---|---|
BIMcloud Manager 18 | Graphisoft BIMcloud Manager 18.0 | TeamworkPortalServerManager Node LicenseManager |
BIMcloud Server Module 18 | Graphisoft BIMcloud Server 18.0 | TeamworkApplicationServerMonitor TeamworkApplicationServer Mongod |
BIMcloud Proxy 18 | Graphisoft BIMcloud Proxy 18.0 | TeamworkBlobCacheServer Mongod |
v19 | LaunchDaemons | Processes |
---|---|---|
BIMcloud Manager 19 | Graphisoft BIMcloud Manager 19.0 | TeamworkPortalServerManager Node TicketProvider |
BIMcloud Server Module 19 | Graphisoft BIMcloud Server 19.0 | TeamworkApplicationServerMonitor TeamworkApplicationServer Mongod |
BIMcloud Delta Cache 19 | Graphisoft BIMcloud Delta Cache 19.0 | TeamworkBlobCacheServer Mongod |
v20 | LaunchDaemons | Processes |
---|---|---|
BIMcloud Manager 20 | Graphisoft BIMcloud Manager 20.0 | TeamworkPortalServerManager Node TicketProvider |
BIMcloud Server Module 20 | Graphisoft BIMcloud Server 20.0 | TeamworkApplicationServerMonitor TeamworkApplicationServer Mongod |
BIMcloud Delta Cache 20 | Graphisoft BIMcloud Delta Cache 20.0 | TeamworkBlobCacheServer Mongod |
Monitor, start, restart, stop services
In order to control the daemons a terminal command named launchctl needs to be used.
- as a first step start Terminal, it can found in Applications/Utilities folder
On Mac the services are represented as so called Daemons. For each LaunchDaemon the configuration is stored in .plist (Property List) format. The following LaunchDaemons belong to the BIMcloud components:
v18 | Path of LaunchDaemons |
---|---|
BIMcloud Manager 18 | /Library/LaunchDaemons/com.graphisoft.PortalServerService-v18.0.plist |
BIMcloud Server Module 18 | /Library/LaunchDaemons/com.graphisoft.TeamworkApplicationServerMonitor-v18.0.plist |
BIMcloud Proxy 18 | /Library/LaunchDaemons/com.graphisoft.BlobCacheService.plist |
v19 | Path of LaunchDaemons |
---|---|
BIMcloud Manager 19 | /Library/LaunchDaemons/com.graphisoft.PortalServerService-v19.0.plist |
BIMcloud Server Module 19 | /Library/LaunchDaemons/com.graphisoft.TeamworkApplicationServerMonitor-v19.0.plist |
BIMcloud Delta Cache 19 | /Library/LaunchDaemons/com.graphisoft.BlobCacheService.plist |
v20 | Path of LaunchDaemons |
---|---|
BIMcloud Manager 20 | /Library/LaunchDaemons/com.graphisoft.PortalServerService-v20.0.plist |
BIMcloud Server Module 20 | /Library/LaunchDaemons/com.graphisoft.TeamworkApplicationServerMonitor-v20.0.plist |
BIMcloud Delta Cache 20 | /Library/LaunchDaemons/com.graphisoft.BlobCacheService.plist |
Note that this is the Library folder in the system root, not within the user’s home folder.
Example terminal command to list all running GRAPHISOFT services:
- sudo launchctl list | grep com.graphisoft
Example terminal command to start BIMcloud Manager:
- sudo launchctl load /Library/LaunchDaemons/com.graphisoft.PortalServerService-v19.0.plist
Example terminal command to start BIMcloud Server module:
- sudo launchctl load /Library/LaunchDaemons/com.graphisoft.TeamworkApplicationServerMonitor-v19.0.plist
Example terminal command to start BIMcloud Delta Cache:
- sudo launchctl load /Library/LaunchDaemons/com.graphisoft.BlobCacheService.plist
Example terminal command to stop BIMcloud Manager:
- sudo launchctl unload /Library/LaunchDaemons/com.graphisoft.PortalServerService-v19.0.plist
Example terminal command to stop BIMcloud Server module:
- sudo launchctl unload /Library/LaunchDaemons/com.graphisoft.TeamworkApplicationServerMonitor-v19.0.plist
Example terminal command to stop BIMcloud Delta Cache:
- sudo launchctl unload /Library/LaunchDaemons/com.graphisoft.BlobCacheService.plist
Note: each command needs to be given on the computer where the product is installed. To restart a component, first stop it and then start it again.
To control whether the BIMcloud is automatically started with the computer
- Navigate to the folder of the LaunchDaemons (Library/LaunchDaemons) in Finder
- Drag and drop the .plist files to your desktop (you can only edit the files there using command line editors, this trick helps to avoid using those)
- Open the .plist files in a Property List Editor or in any text editor
- Change the RunAtLoad to No (Property List Editor) or change the RunAtLoad key to false as on the pictures below
- Drag and drop the files back to the original location (authentication will be required)
The best is keeping the settings on automatic, but in some situations the manual setting can be useful:
- if the Projects and Libraries (Project and Attachment folder) are stored on external storage, which might be unavailable when the computer boots
- for troubleshooting purposes
How to migrate to BIM Server 20
New features of BIM Server 20
In version 20 there have been several BIM Server and ARCHICAD side developments which increase the Teamwork performance and stability.
- Optimized data handling on the Server side to offer better performance
- Teamwork communication optimization in ARCHICAD
- More responsive and more stable Teamwork
Migration from older versions
As a first step choose a computer you would like to install the new BIM Server on. This can be either:
- the computer that runs your current BIM Server
- any other computer that meets the System Requirements
It is not possible to install BIM Server 20 on top of your current BIM Server. This means it can be installed on the same hardware alongside with older versions, but it will be a separate application and has to be installed into a separate folder.
It is strongly recommended to have the least possible number of BIM Server versions running simultaneously on the same computer. After migrating all data remove/uninstall the older versions to keep all resources available for the latest server.
Before migration make sure that you have a full backup and appropriate time for the migration process.
Install BIM Server v20
Install the BIM Server using the installer from the DVD/downloaded from the web.
At the end of the installation, the configuration will be done in your default web browser. If you face any difficulties within the browser, try an alternate supported one. You can copy paste the url over to the new browser.
During the server set up you can add a primary address which can be used to connect to the server from ARCHICAD. You can add this address manually or you can use the ‘Show current addresses…’ button where you can choose from existing addresses which the application automatically detected.
Note that BIM Server v20 Module cannot be started until the BIM Server is not activated after the configuration.
Firewall, network
Open the new ports on all related firewalls and forward them in the router’s settings if necessary for public access over the Internet.
The new default ports:
- BIM Server Manager: 20000
- BIM Server v20 Module: 20001
Make sure to set up different ports for different BIM Server versions!
A fixed IP address is required and a DNS name is recommended for the computer that runs the BIM Server. If the server is accessed from both the local area network and over the Internet make sure to add all the different addresses (internal IP, external IP, domain name) in the BIM Server Manager Connection settings.
Address input
Once BIM Server 20 is installed, to access the BIM Server Manager, open a web browser and type combined address and port into browser address bar. Default port is 20000. Examples of the address format:
http://server.company.com:20000 or http://IP address:20000
Migrate Users and Roles
Use BIM Server Manager to create Users and/or Roles. You can also import previous role and user databases.
Export data in v18 and v19
- Open the browser based management interface
- Navigate to ‘Users’ page
- Click on the tick icon above the users
- Click on ‘Select all’
- Export
- Repeat the same with ‘Roles’
Export data in v17 and older versions
- Open BIM Server Manager application that belongs to v17 version
- Go to ‘Users’
- Export, All users…
- Go to ‘Roles’
- Export
Import data in BIM Server 20
- Open the browser based management interface
- Navigate to ‘Users’ page
- Click on ‘+’ next to the ‘Users’
- Import
- Browse for the user database you exported previously
- Repeat the same with ‘Roles’
Please note that the Server Administrator and Project Administrator management roles are not coming over during the migration. These have to be set up manually after the import process.
Upload Libraries
First upload the latest ARCHICAD Library 20 and the migration libraries:
- Open ARCHICAD 20
- File>Libraries and Objects>Manage BIMcloud / BIM Server Libraries…
- Connect to your BIM Server – make sure you use the the full url when connecting, example: http://server.company.com:20000
- Click on the ‘Upload…’ button
- Browse for the ARCHICAD Library 20 in your ARCHICAD 20 folder
- Upload all migration libraries from the ARCHICAD 20 folder you might need for your projects
Upload the libraries from your previous BIM Server
- Open the previous ARCHICAD version you were using like ARCHICAD 19
- File>Libraries and Objects>Manage BIM Server Libraries…
- Select each library and check the ‘Source Folder’ or use ‘Extract…’ to download the library from the Server
- Go over to ARCHICAD 20 and upload all libraries based on the previous ‘Source Folders’
Migrate Projects
To Migrate Projects from BIM Server 13 through 19, please follow the migration guide. Alternatively you can do it manually:
- Open project in its current version of ARCHICAD
- Save as a .PLN (ARCHICAD Solo Project)
- Open the PLN and change library source from a BIM Server to a Linked library which resides on your workstation or a common file server
- Save the file and open it in ARCHICAD 20
- Use the Library Migration service if prompted
- Share the project from version 20 using Teamwork>Projects>Share…
To share or join projects from ARCHICAD 20 go to Teamwork>Project>Share… or Open/Join Teamwork Project… and enter the combined server address and port, same format as shown above. (server.company.com:20000)
Network requirements
Addresses
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: 195.144.20.210
- 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 |
Important notes:
- 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:
http://server.company.com:port
http://IP address:port
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.
How to identify the address of the computer
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
- Mac
- System Preferences > Sharing > Computer name
- Windows
- This PC > Right click > Properties > Full computer name
Public IP
- Perform a Google search for “public IP”. It will return your public IP address.
Private IP
- Mac:
- System Preferences > Network
- or give the ifconfig command in Terminal
- Windows:
- Control Panel > Network and sharing center > Click on the text next to Connections > Details
- or give the ipconfig command in the Command Prompt
Ports
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:
Application | v18 | v19 | v20 |
---|---|---|---|
BIMcloud Manager | 1228 | 19000 | 20000 |
BIMcloud Server | 18008 | 19001 | 20001 |
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:
Application | v18 | v19 | v20 |
---|---|---|---|
BIM Server Manager | 1228 | 19000 | 20000 |
BIM Server module | 18008 | 19001 | 20001 |
Communication
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
BIM Server system components
In case of the following system components, both the network communication and file related operations need to be on the exclusion list if any antivirus/firewall/network monitoring application is used.
Components
BIM Server Manager
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v18 | Graphisoft BIMcloud Manager 18.0 (PortalServerService-v18.0) |
TeamworkPortalServerManager.exe Node.exe TicketProvider.exe |
v19 | Graphisoft BIMcloud Manager 19.0 (PortalServerService-v19.0) |
|
v20 | Graphisoft BIMcloud Manager 20.0 (PortalServerService-v20.0) |
Folders and files
Folder / File | Operating System | Path |
---|---|---|
Installation folder * | Windows | C:\Program Files\GRAPHISOFT\BIM Server <version>\BIMcloud Manager\ |
OS X | System drive/Applications/GRAPHISOFT/BIM Server <version>/BIMcloud Manager/ | |
Configuration folder | Windows | …\BIMcloud Manager\Config\ |
OS X | …/BIMcloud Manager/Config/ | |
Manager’s database folder ** | Windows | …\BIMcloud Manager\Data\ |
OS X | …/BIMcloud Manager/Data/ | |
Logs folder | Windows | …\BIMcloud Manager\Logs\ |
OS X | …/BIMcloud Manager/Logs/ |
BIM Server Module
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v18 | Graphisoft BIMcloud Server 18.0 (TeamworkApplicationServerMonitor-v18.0) |
TeamworkApplicationServerMonitor.exe TeamworkApplicationServer.exe Mongod.exe |
v19 | Graphisoft BIMcloud Server 19.0 (TeamworkApplicationServerMonitor-v19.0) |
|
v20 | Graphisoft BIMcloud Server 20.0 (TeamworkApplicationServerMonitor-v20.0) |
Folders and files
Folder / File | Operating System | Path |
---|---|---|
Installation folder * | Windows | C:\Program Files\GRAPHISOFT\BIM Server <version>\BIMcloud Server <version>\ |
OS X | System drive/Applications/GRAPHISOFT/BIM Server <version>/BIMcloud Server <version>/ | |
Configuration folder | Windows | …\BIMcloud Server <version>\Config\ |
OS X | …/BIMcloud Server <version>/Config/ | |
Projects folder ** | Windows | …\BIMcloud Server <version>\Projects\ |
OS X | …/BIMcloud Server <version>/Projects/ | |
Attachments folder ** | Windows | …\BIMcloud Server <version>\Attachments\ |
OS X | …/BIMcloud Server <version>/Attachments/ | |
BlobCache database folder ** | Windows | …\BIMcloud Server <version>\BlobCache\ |
OS X | …/BIMcloud Server <version>/BlobCache/ | |
Session database folder | Windows | …\BIMcloud Server <version>\Sessions\ |
OS X | …/BIMcloud Server <version>/Sessions/ | |
Messaging database folder | Windows | …\BIMcloud Server <version>\Mailboxes\ |
OS X | …/BIMcloud Server <version>/Mailboxes/ | |
Logs folder | Windows | …\BIMcloud Server <version>\Logs\ |
OS X | …/BIMcloud Server <version>/Logs/ |
BIMcloud Monitor
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v19 | Graphisoft Service Process Manager Agent 19.0 (TeamworkServiceProcessManagerAgent-v19.0) |
TeamworkServiceProcessManagerAgent.exe BIMcloudMonitor.exe |
v20 | Graphisoft Service Process Manager Agent 20.0 (TeamworkServiceProcessManagerAgent-v20.0) |
Folders and files
From version 19 both BIM Server components contain the BIMcloud Monitor application.
Folder / File | Operating System | Path |
---|---|---|
BIMcloud Monitor Application | Windows | …\BIMcloud Manager\BIMcloudMonitor.exe …\BIMcloud Server <version>\BIMcloudMonitor.exe |
OS X | …/BIMcloud Manager/BIMcloudMonitor.app …/BIMcloud Server <version>/BIMcloudMonitor.app |

* The path can be modified during the installation phase.
** The path can be modified either at the configuration phase or later by reconfiguring the affected BIM Server component.
Communication
Communication between the client and the server side components
Source | Destination | Port Number | Protocol |
---|---|---|---|
ARCHICAD 18 | BIM Server Manager | 1228 | HTTP |
BIM Server v18 Module | 18008 | ||
ARCHICAD 19 | BIM Server Manager | 19000 | HTTP |
BIM Server v19 Module | 19001 | ||
ARCHICAD 20 | BIM Server Manager | 20000 | HTTP |
BIM Server v20 Module | 20001 |
Communication between the server side components
Note that in case of BIM Server the server side components can only be installed on the same computer, so this communication is local.
Source | Destination | Port Number | Protocol |
---|---|---|---|
BIM Server Manager | BIM Server v18 Module | 18008 | HTTP |
BIM Server v19 Module | 19001 | ||
BIM Server v20 Module | 20001 |

BIMcloud system components
In case of the following system components, both the network communication and file related operations need to be on the exclusion list if any antivirus/firewall/network monitoring application is used.
Components
BIMcloud Manager
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v18 | Graphisoft BIMcloud Manager 18.0 (PortalServerService-v18.0) |
TeamworkPortalServerManager.exe Node.exe LicenseManager.exe |
v19 | Graphisoft BIMcloud Manager 19.0 (PortalServerService-v19.0) |
|
v20 | Graphisoft BIMcloud Manager 20.0 (PortalServerService-v20.0) |
Folders and files
Folder / File | Operating System | Path |
---|---|---|
Installation folder * | Windows | C:\Program Files\GRAPHISOFT\BIMcloud\BIMcloud Manager\ |
OS X | System drive/Applications/GRAPHISOFT/BIMcloud/BIMcloud Manager/ | |
Configuration folder | Windows | …\BIMcloud Manager\Config\ |
OS X | …/BIMcloud Manager/Config/ | |
Manager’s database folder ** | Windows | …\BIMcloud Manager\Data\ |
OS X | …/BIMcloud Manager/Data/ | |
Logs folder | Windows | …\BIMcloud Manager\Logs\ |
OS X | …/BIMcloud Manager/Logs/ |
BIMcloud Server
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v18 | Graphisoft BIMcloud Server 18.0 (TeamworkApplicationServerMonitor-v18.0) |
TeamworkApplicationServerMonitor.exe TeamworkApplicationServer.exe Mongod.exe |
v19 | Graphisoft BIMcloud Server 19.0 (TeamworkApplicationServerMonitor-v19.0) |
|
v20 | Graphisoft BIMcloud Server 20.0 (TeamworkApplicationServerMonitor-v20.0) |
Folders and files
Folder / File | Operating System | Path |
---|---|---|
Installation folder * | Windows | C:\Program Files\GRAPHISOFT\BIMcloud\BIMcloud Server <version>\ |
OS X | System drive/Applications/GRAPHISOFT/BIMcloud/BIMcloud Server <version>/ | |
Configuration folder | Windows | …\BIMcloud Server <version>\Config\ |
OS X | …/BIMcloud Server <version>/Config/ | |
Projects folder ** | Windows | …\BIMcloud Server <version>\Projects\ |
OS X | …/BIMcloud Server <version>/Projects/ | |
Attachments folder ** | Windows | …\BIMcloud Server <version>\Attachments\ |
OS X | …/BIMcloud Server <version>/Attachments/ | |
BlobCache database folder ** | Windows | …\BIMcloud Server <version>\BlobCache\ |
OS X | …/BIMcloud Server <version>/BlobCache/ | |
Session database folder | Windows | …\BIMcloud Server <version>\Sessions\ |
OS X | …/BIMcloud Server <version>/Sessions/ | |
Messaging database folder | Windows | …\BIMcloud Server <version>\Mailboxes\ |
OS X | …/BIMcloud Server <version>/Mailboxes/ | |
Logs folder | Windows | …\BIMcloud Server <version>\Logs\ |
OS X | …/BIMcloud Server <version>/Logs/ |
BIMcloud Delta Cache (BIMcloud Proxy)
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v18 | Graphisoft BIMcloud Proxy 18.0 (BlobCacheService) |
TeamworkBlobCacheServer.exe Mongod.exe |
v19 | Graphisoft BIMcloud Delta Cache 19.0 (BlobCacheService) |
|
v20 | Graphisoft BIMcloud Delta Cache 20.0 (BlobCacheService) |
Folders and files
Folder / File | Operating System | Path |
---|---|---|
Installation folder * | Windows | C:\Program Files\GRAPHISOFT\BIMcloud\BIMcloud Proxy\ |
OS X | System drive/Applications/GRAPHISOFT/BIMcloud/BIMcloud Proxy/ | |
Configuration folder | Windows | …\BIMcloud Proxy\Config\ |
OS X | …/BIMcloud Proxy/Config/ | |
BlobCache database folder ** | Windows | C:\ProgramData\Graphisoft\BlobCacheServer\CacheFolder\ |
OS X | System drive/Library/Preferences/Graphisoft/BlobCacheServer/CacheFolder/ | |
Logs folder | Windows | C:\Program Files\GRAPHISOFT\BIMcloud\BIMcloud Proxy\Logs\ C:\ProgramData\Graphisoft\BlobCacheServer\LogFolder\ |
OS X | System drive/Applications/GRAPHISOFT/BIMcloud/BIMcloud Proxy/Logs/ System drive/Library/Preferences/Graphisoft/BlobCacheServer/LogFolder/ |
BIMcloud Monitor
Services and Processes
Version | Service / LaunchDaemon | Processes |
---|---|---|
v19 | Graphisoft Service Process Manager Agent 19.0 (TeamworkServiceProcessManagerAgent-v19.0) |
TeamworkServiceProcessManagerAgent.exe BIMcloudMonitor.exe |
v20 | Graphisoft Service Process Manager Agent 20.0 (TeamworkServiceProcessManagerAgent-v20.0) |
Folders and files
From version 19 all BIMcloud components contain the BIMcloud Monitor application.
Folder / File | Operating System | Path |
---|---|---|
BIMcloud Monitor Application | Windows | …\BIMcloud Manager\BIMcloudMonitor.exe …\BIMcloud Server <version>\BIMcloudMonitor.exe …\BIMcloud Proxy\BIMcloudMonitor.exe |
OS X | …/BIMcloud Manager/BIMcloudMonitor.app …/BIMcloud Server <version>/BIMcloudMonitor.app …/BIMcloud Proxy/BIMcloudMonitor.app |

* The path can be modified during the installation phase.
** The path can be modified either at the configuration phase or later by reconfiguring the affected BIMcloud component.
Communication
Communication between the client and the server side components
Source | Destination | Port Number | Protocol |
---|---|---|---|
ARCHICAD 18 BIMcloud Team Client 18 |
BIMcloud Manager | 1228 | HTTP |
BIMcloud Server 18 | 18008 | ||
BIMcloud Proxy | 9921 | ||
ARCHICAD 19 BIMcloud Team Client 19 |
BIMcloud Manager | 19000 | HTTP |
BIMcloud Server 19 | 19001 | ||
BIMcloud Delta Cache | 9921 | ||
ARCHICAD 20 BIMcloud Team Client 20 |
BIMcloud Manager | 20000 | HTTP |
BIMcloud Server 20 | 20001 | ||
BIMcloud Delta Cache | 9921 |
Communication between the server side components
If the server side components are installed on the same computer, the communication is local.
Source | Destination | Port Number | Protocol |
---|---|---|---|
BIMcloud Manager BIMcloud Delta Cache (BIMcloud Proxy) |
BIMcloud Server 18 | 18008 | HTTP |
BIMcloud Server 19 | 19001 | ||
BIMcloud Server 20 | 20001 |
