Connect / networked location of Datasets

Still in the process of setting up Aecosim Connect I've run into a problem when trying to setup our networked company workspace.

So far I was able to configure my PC that it reads configuration files from the network.

The problem I have now is that I am unable to define the correct location of the datasets.

  • TF_DATASETS points to the local drive.
    By doing a little research I found out that this variable is defined in the program folder that way:

    TF_DATASETS : $(_TF_WORKSPACEROOT)Datasets/
  • _TF_WORKSPACEROOT also points to a local folder
    The local definition of this variable is:

    _TF_WORKSPACEROOT : ${_USTN_CONFIGURATION}
  • _USTN_CONFIGURATION points to our network drive.

So in theory _TF_WORKSPACEROOT should point to our network drive, which is doesn't

On assuming that something isn't working, I have defined _TF_WORKSPACEROOT in the WorkSpaceSetup.cfg file in that way.

%lock _TF_WORKSPACEROOT = M:/Microstation/Workspace_Connect/Configuration/

The funny thing now is, that this doesn't change anything - the variable still points to a local drive.

Any ideas?

Parents
  • Hi Andreas,

    Create a network configuration as described in the wikis/blogs linked in your other thread (preferably for initial testing create it locally as mentioned in my post to that thread)
    [Replace the ... in the paths below with your own path.]

    Copy the dataset to the network , e.g.: ...\CONFIGURATIONS\CE\Datasets

    In the network WorkSpaces folder: e.g.: ...\CONFIGURATIONS\CE\WorkSpaces create a folder called NM_Projects (just for testing)

    In this folder create new file NM_Projects.cfg, paste the following lines into that file:

    _USTN_WORKSETROOT              = .../ProjectData/$(_USTN_WORKSPACENAME)/$(_USTN_WORKSETNAME)/
    _USTN_WORKSETDGNWS         = $(_USTN_WORKSETROOT)Standards/$(_USTN_WORKSETNAME).DGNWS
    TF_DATASETS = //hal/CONFIGURATIONS/CE/Datasets/

    (The TF_DATASETS definition here will point to the network)

    In ...\CONFIGURATIONS\CE\WorkSpaces\NM_Projects

    a) create a folder called WorkSets

    b) copy the folder and content from C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards

    c) Copy file
    "C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\worksets\BuildingTemplate_NM.cfg"
    into
    ...\CONFIGURATIONS\CE\WorkSpaces\NM_Projects\WorkSets
    and rename to NM_Project_001.cfg. (this file does not need to be edited, it will find Dataset_NM)

    In ...\ProjectData create a folder called NM_Projects

    Copy the example template folder and contents (obviously):
    C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\worksets\BuildingTemplate_NM
    into
    ...\ProjectData\NM_Projects\ and rename to NM_Project_001.

    You should end up with this:

    The only change needed on the c:\ drive is to SetupConfiguration.cfg as previously discussed.

    Note that the DGNWS file is created in the ...\ProjectData\NM_Projects\NM_Project_001\Standards folder where it can be written to by users.

     ...\ProjectData can be on different drive/share, they are only in the same place for simplicity here.

    Hope this helps to clarify things?

    Marc

Reply
  • Hi Andreas,

    Create a network configuration as described in the wikis/blogs linked in your other thread (preferably for initial testing create it locally as mentioned in my post to that thread)
    [Replace the ... in the paths below with your own path.]

    Copy the dataset to the network , e.g.: ...\CONFIGURATIONS\CE\Datasets

    In the network WorkSpaces folder: e.g.: ...\CONFIGURATIONS\CE\WorkSpaces create a folder called NM_Projects (just for testing)

    In this folder create new file NM_Projects.cfg, paste the following lines into that file:

    _USTN_WORKSETROOT              = .../ProjectData/$(_USTN_WORKSPACENAME)/$(_USTN_WORKSETNAME)/
    _USTN_WORKSETDGNWS         = $(_USTN_WORKSETROOT)Standards/$(_USTN_WORKSETNAME).DGNWS
    TF_DATASETS = //hal/CONFIGURATIONS/CE/Datasets/

    (The TF_DATASETS definition here will point to the network)

    In ...\CONFIGURATIONS\CE\WorkSpaces\NM_Projects

    a) create a folder called WorkSets

    b) copy the folder and content from C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards

    c) Copy file
    "C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\worksets\BuildingTemplate_NM.cfg"
    into
    ...\CONFIGURATIONS\CE\WorkSpaces\NM_Projects\WorkSets
    and rename to NM_Project_001.cfg. (this file does not need to be edited, it will find Dataset_NM)

    In ...\ProjectData create a folder called NM_Projects

    Copy the example template folder and contents (obviously):
    C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\worksets\BuildingTemplate_NM
    into
    ...\ProjectData\NM_Projects\ and rename to NM_Project_001.

    You should end up with this:

    The only change needed on the c:\ drive is to SetupConfiguration.cfg as previously discussed.

    Note that the DGNWS file is created in the ...\ProjectData\NM_Projects\NM_Project_001\Standards folder where it can be written to by users.

     ...\ProjectData can be on different drive/share, they are only in the same place for simplicity here.

    Hope this helps to clarify things?

    Marc

Children
  • Andreas, maybe a little bit simpler. I found the same issues when configuring connect for first time. eventually settled on the following lines in my organization standards.cfg. What I found though was that the way default datasets are defined caused a bit of issue. 

    Default or localized, workspace and workset. Because of this  I had to define my company standards dataset as the workspace BB_DATASET_WORKSPACE_FILTER. 

    %ifdef BB_DISCIPLINE

    TF_DATASETS = $(_USTN_CONFIGURATION)/Datasets/
    TF_DATASETNAME = Dataset_UK
    %if exists ($(TFDIR)Dataset.cfg)
    % include $(TFDIR)Dataset.cfg
    %endif

    ORG_DATASETNAME = LDS
    ORG_DATASET = $(TF_DATASETS)DatasetExtensions/$(ORG_DATASETNAME)/
    BB_DATASET_WORKSPACE_FILTER = $(ORG_DATASET)
    %if exists ($(ORG_DATASET)LDS_Dataset.cfg)
    % include $(ORG_DATASET)LDS_Dataset.cfg
    %endif

    DG_CATALOGS_WORKSPACE = $(ORG_DATASET)/DataGroupCatalogs/
    DG_SYSTEMS_WORKSPACE = $(ORG_DATASET)/DataGroupSystem/

    %endif

    Initially I defined the workset dataset here also (like i did in v8i) but this caused a few problems, so moved the below to workset.cfg


    #WORKSET_DATASETNAME = $(WORKSET_NUM)_Dataset
    #WORKSET_DATASET = $(_USTN_WORKSETROOT)/BIM/$(WORKSET_DATASETNAME)/
    #BB_DATASET_WORKSET_FILTER = $(WORKSET_DATASET)/

  • Thanks for the input.

    As I have said, I now have managed to have TF_DATASETS configured correctly, and it more or less does what I want.

    A question which has come up now is, that I don't know what the difference between files in the \DATASETS and the  Workspace\[Workspace]\Standards folder is.

    Probably the first one is for all workspaces, the second one just for a specific one?

    But then I can't see how they are used, e.g. DG_CATALOGS_WORKSPACE points to just the workspace folder.