Hello all,
I've been working with MicroStation workspace environments for quite a number of years now. I am finally looking into building a CONNECT environment as our clients are beginning to provide configurations.
I've begun going through the related content on the LEARN Server, but one thing I've ran into while putting things together is that now that the Civil products are a part of MicroStation, each Civil product has a separate install from vanilla MicroStation and a different configuration.
We have a mix of MicroStation and ORD licenses, so I intend to install both products on each of my user's systems so that if they don't need civil functionality, they can use the less expensive MicroStation license, but have the full civil tool set if needed.
Are any of you working in a mixed environment like this? If so, how do you have things configured?
I was going to have the Organization and Workspace level configs on our network, where the Organization would contain our company's specific resource files, and we'd have a Workspace for each of our clients.
What is throwing me off is that MicroStation comes with an Organization folder, but ORD comes with Organization AND Organization-Civil...
Can I put the config in one network location that serves both ORD and MicroStation, or does the config for each product need to be in separate locations?
Thank you both Kevin and John!
Kevin, the licensing note is very interesting, did not realize, I will definitely be chatting with Bentley on this. THANK YOU!!
John, I'll digest what you have here, and dig further into the CFG files to see if I can make sense out of where/how the Organization-Civil folder is used.
Org Civil works by being included from the WorkSpaceName.cfg. Here are the lines that do it.
# <<<< Make Changes Here >>>> CIVIL_ORGANIZATION_NAME = PennDOT Design #==================================================================================== # Load Civil Organization Standards # # When a ProjectWise Managed Workspace is used this variable is not required. # The Organization or Customer standards will be defined using a Customer # Configuration Settings Block. #==================================================================================== # Load Organization standards in this order: # 1. Standard named specified in CIVIL_ORGANIZATION_NAME %if exists ($(CIVIL_ORGANIZATION_ROOT)$(CIVIL_ORGANIZATION_NAME).cfg) % include $(CIVIL_ORGANIZATION_ROOT)$(CIVIL_ORGANIZATION_NAME).cfg %endif
~HTH
John.
yep
Thank you again John, I appreciate it. So, this WorkspaceSetup.cfg file is part of my confusion too, because the one that comes with ORD comes with the lines to custom map to the Org-Civil folder, but it does not include lines to custom map the Organization folder as the MicroStaion WorkspaceSetup.cfg file does.
I was thinking of copying the Organization level lines out of the MicroStation WorkspaceSetup.cfg and pasting it into the civil file, then maybe using some kind of logic in the CFG to find the product name to drive which Org path to map...
Personally we do not specify anything in the WorkSpaceSetup.cfg. I don't think its needed. The only thing I know this file to be good for is so that MSTNce can find the ORG-Civil folder based on the variable CIVIL_ORGANIZATION_ROOT. We just use the ORD based file.
So you want to based on _EngineName determine which Oganization is used? If this is correct I would not do this. It seems to be confusing and changing the logic of which Bentley is using. Remember Organization-Civil is only Organization by name. It is not read at the Organization level and is included from the WorkSpace. I believe Bentley created ORG-Civil so that many WorkSpaces can include one ORG-Civil.
I would use the general logic in the application to find the different items the same as it is delivered and work with that. The easiest way to do this is to install both ORD and MSTNce on a machine and copy the Configuration to the network. In the Organization folder we only store things that are specific to us (plotters, macros, seed preference files, etc.) This folder is not delivered to business partners and we store no design or CADD standards at this level. All Design and CADD standards information is stored in the Organization-Civil (remember ORG-Civil is a workspace item). We use WorkSpaces as the Departments and they all include our ORG-Civil standards. ( So our users work as Roadway (workSpace) on the I95 (WorkSet) When we deliver it to our business partners we deliver them a WorkSpace (not ORg-Civil). So BP's work on PennDOT Design (workSpace) and the Project based workset.
John Frampton said:I believe Bentley created ORG-Civil so that many WorkSpaces can include one ORG-Civil.
That is correct.
Marc