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?
You may want to talk to Bentley and confirm your mixed installs will actually be cheaper by your contract. By our contract if you open ORD today and use it. Then a few hours later open Microstation we will be billed for both 1 usage of MicroStation and 1 usage of ORD. If, however, ORD was used both times then 1 product is marked as used. (note that license concurrancy will affect the over count in this scenario but unless you have a lot of people moving between the 2 products you're probably going to find it way more expensive to install both.)
Also - Yes, you can point both ORD and MicroStation to the same network configuration.
Unknown said: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.
This seems to be the right direction.
Unknown said:What is throwing me off is that MicroStation comes with an Organization folder, but ORD comes with Organization AND Organization-Civil...
Organization - Civil is really an illusion as it is in an include from the WorkSpace. So Org Civil isn't actually at the Organization level but instead at the WorkSpace Level. It was made up by Bentley Civil and is only a name not a level of configuration.
Unknown said: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?
We have both MSTNCE and ORDCE reading from the same networked configuration. We have things stored at the Organization and Organization-Civil level. WorkSpace is used as our discipline and doesn't store any standards, WorkSet stores our Project settings. So if a user makes a template it is a project template based on our standards and is saved in the WorkSet standards folder. If the file exists then it is loaded as the default.
For delivering our configuration to business partners we will deliver the Org-Cvil folder to them as a workspace. They can use it as either a WorkSpace or a Civil-Org. We would prefer them to use it as the WorkSpace but they can easily make it work as a Civil-Org if they like.
There is an issue with reading Organization - Civil with just MSTN installed. So if you only have MSTN you will need to do some tweaking to get it to work. The error you will get is in regard to CIVIL_ORGANIZATION_ROOT not being defined.
~HTH
John.
yep
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
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...