| Product(s): | Bentley Raceway and Cable Management |
| Version(s): | 10.03.00.25 |
| Environment: | N/A |
| Area: | Installation Configuration |
| Subarea: | N/A |
Background
There are different methods to store a workspace configuration like, on a server, local folder, or in a ProjectWise Managed environment. This document describes recommended methods to setup BRCM Connect Edition on a local or server folder.
First, let’s get clear about the word WorkSpace, the folder structure where standard datasets are defined and the configuration variable definitions as a collection are commonly referred to as a workspace. In this document, we use the term workspace configuration to describe this folder structure and configuration. New to the CONNECT Edition software is the ability to select a WorkSpace when opening a file. This WorkSpace can optionally contain additional configuration files and is the parent to WorkSets which are essentially Project definitions. A separate WorkSet is required for each project.
There are two methods to deploy workspace on network location:
1. Storing Workspace on Server - Method 1
Steps to Accomplish
1. Create a folder at the server location or local custom location where custom configuration needs to be stored. In that folder add custom workspaces or for test purpose copy the local configuration from C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\
This folder must contain one subfolder Workspaces and one file WorkSpaceSetup.cfg
The file ConfigurationSetup.cfg should only be at the local machine where BRCM is installed.
2. Point BRCM to the server folder by defining the necessary variables in the local .cfg file. This may not be an appropriate choice in larger organizations where changes to individual machines are undesirable. Larger organizations should consider setting the variables using environment variables as described the “Using an Environment Variable” section below.
i. Edit the file
C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\WorkSpaceSetup.cfg
ii. Define the location of the WorkSpaces folder by uncommenting and setting the MY_WORKSPACES_LOCATION variable. The WorkSpaces folder does not need to be a child of the Configuration folder. It can be in a different folder or even a different server.
For example: MY_WORKSPACES_LOCATION = // Server_Name/WorkSpaces/
Using an Environment Variable:
An alternative method for the above steps is to define the variables as Windows environment variables instead of editing the WorkSpaceSetup.cfg file for each product installed on a machine. The advantage is the variables are defined once for all products instead of having to edit and copy individual .cfg files. Windows environment variables can also be defined on a server for each user and then no changes need to be made on the local machines.
- Start the Window Control Panel.
- Select System > Advanced > Environment Variables.
- Define a new variable with the same name as those described above as necessary for your configuration. Be sure to include the trailing slash which is required by MicroStation when defining folder paths.
Open BRCM CE you are able to see the WorkSpaces deployed at network location and all projects/WorkSets are now selected from the same location.
2. Storing Workspace on Server - Method 2
Steps to Accomplish
1. Create a folder at the server location or local custom location where custom configuration needs to be stored. In that folder add custom workspaces or for test purpose copy the local configuration from C:\ProgramData\Bentley\BRCM CONNECT Edition\Configuration\
This folder must contain one subfolder Workspaces and one file WorkSpaceSetup.cfg
The file ConfigurationSetup.cfg should only be at the local machine where BRCM is installed.
2. Point BRCM to the server folder by defining the necessary variables in the local CFG file.
Goto the local BRCM configuration folder C:\ProgramData\Bentley\ BRCM CONNECT Edition \Configuration\ and open file ConfigurationSetup.cfg
Define the server location of the Configuration folder by uncommenting and setting the variable. Here trailing slash is used to Define the address.
For example: _USTN_CUSTOM_CONFIGURATION = //Server_Name/Configuration/
3.Open BRCM and click on WorkSpace. The defined custom configuration will be shown as follows:
| Original Author: | Vikrant Kale |