Product:	All Bentley Products
	Version:	V8, XM, V8i
	Environment:	N\A
	Area:	Administration
	Subarea:	N\A

Overview

Setting up an effective workspace requires a lesson in priority levels

Efficient workspace set-up on a network server really begins with an understanding of the MicroStation start-up process. MicroStation has five different priority levels (directories) in which the configuration files are stored. A configuration file is an ASCII text file that can contain configuration variables and their paths or file names, logical operators (i.e., %ifdef, %ifndef, and %endif) and notes about that particular configuration file to help clarify your reasoning for future system administrators.

These five priority levels include:

 

• System (0). This first and lowest priority level is where MicroStation defines the configuration variables essential to operate properly. The _USTN_SYSTEM variable defines the directory where all the system level configuration files are located. All of the files in the system directory ending with the CFG extension will be read by MicroStation.
  
  
• Application (1). This level's directory is delivered empty. This is where configuration files for other software applications that run on top of MicroStation are stored. The _USTN_APPL variable points to the directory location of the application configuration files. These files also end with a CFG extension and are read by MicroStation at startup.

At the operating system command line, key in

ustation -wa<<MDL application>>

This will initiate <<MDL application>>

• Site (2). The only item in this level after installation is a file called site.txt. System administrators are normally asked to modify the contents of this file and rename it site.cfg when they are using license pooling. This is the best level for establishing the site and corporate standards that are essential for all CAD operators to work efficiently. The site level is a lot like the system level-the system administrator should define only the configuration variables necessary to run MicroStation effectively at his/her site. The _USTN_SITE variable (found in msconfig.cfg) tells MicroStation in which directory to look for the site level configuration files. Again, MicroStation reads all of the files with the CFG extension in the directory.
  
  
• Database (3). This level's directory contains the configuration files for a specific database's configuration variables that are essential for the database to operate correctly. The _USTN_DATABASE variable points to the directory where the database configuration files are located. This directory also contains CFG files, but unlike the previous levels, MicroStation only reads the file you designate. To do this, just key in ustation -wd<<database name>> at the operating system command line when you start MicroStation.
  
  
• Project (3). This level has the same priority level as the database level. The directory contains all of the project configuration files. Variables that are defined on the project level should apply specifically to a certain project, discipline or client. The _USTN_PROJECT variable points to the directory where all of the project configuration files are stored. Unlike the other levels, the project configuration files all end in a PCF extension, and only one project configuration file can be loaded at a time. To do this, key in ustation -wp<<project name>> at the operating system command line.
  
  
• User (4). This has the highest priority of all levels. Any variable set in the user level will override that variable in every other level, unless the variable is locked in another level. System administrators should not have anything to do with the user level-it should remain untouched, allowing the user the flexibility of setting up his/her own environment. If system administrators feel that there are variables that cannot be modified, then they can lock the variable so the user cannot redefine them. The _USTN_USER variable points to the directory where the user configuration files are found. This level also has its own unique file extension, UCF, and only one file can be loaded at a time. To do this, key in ustation -wu<<user configuration name>> at the operating system command line.

Creating a workspace

Now that you have a better understanding of MicroStation's startup process, let's create a workspace so that all individual user configuration files, user interface (palette, menu and dialog modification) files and user preferences are located on the server. This will enable users to control their own environments, no matter which computer is used. First, the system administrator sets a variable on the network so that when a user logs in, the variable USERID = <<the user's name>> (i.e., USERID = MATTS) is defined. Next, define _USTN_SITE=<<directory on the server>> in the system startup file, to point to where the site configuration files are stored. For example, add this line to the autoexec.bat: SET _USTN_SITE=o:\config\site\ This is ideal if you always run MicroStation with the network connected. Or you can create a text file, naming it whatever you want, as long as it has a CFG extension. This file will contain only one variable (_USTN_SITE) and we will place it in the /ustation/config/system directory. The file should look like this:

This tells MicroStation to look at the o:/config/site directory for all of the site configuration files if the USERID variable is defined. It then locks the variable so MicroStation can't redefine it. Otherwise, it's assumed that the network is not loaded and MicroStation will run entirely local. This will be the only file that we add to the local hard drive. Go to the directory defined by _USTN_SITE variable and create another text file-the name is irrelevant, as long as the file has the CFG extension. This file will define all the variables to point MicroStation out to the other server directories. It should look like this:

#---------------------

# Corpsite.cfg

The _USTN_USERINT variable defines the path to the location of all the subdirectories where the user interface modification files are stored. The _USTN_USERINTNAME variable is the name of the user interface that MicroStation is to load, as well as the subdirectory name where the USTN.M** file is located. The system administrator should set a up directory structure similar to this

 

The USERID variable will be defined at startup as one of the user's names. Users should only have full rights to their own subdirectory-that way, they can change their environments without other users disturbing them. The system administrator only needs to put three files in the USERID directory:

• If users already have their own custom interfaces, then copy all of the files from the wsui/<<interface name>> up to the user/$(USERID)/directory. Otherwise, leave those files out, and as users make modifications to their interfaces, the files will be created.
• Put a copy of the default.ucf file delivered with MicroStation into the user/$(USERID)/config/ directory-this file is essential for MicroStation to run.
• If users have their own user preferences already set up, copy the local *.UPF file into the user/$(USERID)/config/ directory and name it Default.upf. It isn't necessary to copy this file into the directory, because if one doesn't exist, MicroStation will create one at startup.

Now that we have setup MicroStation to run its configuration files, user interfaces and user preferences off of the server, all that's left for you to do is fill in the blanks.  

See also

Other language sources

Original Author:

Bentley Technical Support Group