| Applies To | |
| Product(s): | OpenPlant Modeler |
| Version(s): | CONNECT Edition 10.11.++ |
| Environment: | Windows 10/11 (64-bit) |
| Area: | Bentley Automation Service |
| Subarea: | iModel |
| Original Author: | Joseph Gelacio, Product Advancement Group |
Background
Introduction to Bentley Automation Service:
Bentley Automation Service runs on top of ProjectWise Orchestration Framework Service and uses different extensions to automate various processes, with a focus on publishing i-models.
ProjectWise Orchestration Framework Service provides services to an application that promote high availability, easy scalability, and job control. Here ProjectWise Orchestration Framework Service is described very briefly to make it clear where it can be helpful to an application and how these benefits are realized.
There are 8 processors BAS runs from which Power Platform Processor launches the application (OPM in our case) in NON UI mode. and runs a set of key ins to publish the imodel.
List of key ins are attached to the PBI.
OPM Update 11 added a new addin 'OPSchemaLocatorAddin' to OPM. When running OPM from BAS, define cfg. variable 'OPM_ENABLE_BAS_ADDIN' and set it to either '1' or 'true' to enable it. This would allow locating OPM schemas since BAS doesn't load 'MechAddin' and as a result OPM's standard locator is not available.
This addin has no dependency on any other OPM binary and can be used to load OPM schemas given proper configuration variables are defined pointing to schema names and locations.
Steps to Accomplish
- The new added addin 'OPSchemaLocatorAddin' can be found here by default:
C:\Program Files\Bentley\OpenPlant CONNECT Edition\OpenPlantModeler\Assemblies - Define cfg. variable 'OPM_ENABLE_BAS_ADDIN' and set it to either '1' or 'true' to enable it.
Open the Modeler.cfg file of the Managed workspace and add the variable OPM_ENABLE_BAS_ADDIN=1 at the end:
Save the configuration.
Note: You may need to clear out the temporary local files to make sure any variable change in the Managed configuration will take effect. - Clear out the local cache of the orchestration framework to get the latest configuration from ProjectWise.
- Test and confirm the result
Additional notes:
If the schemas are still not present in the output iModel, check if the "OPSchemaLocatorAddin.ma" was copied out correctly ins the local working area of orchestration framework when we execute the BAS job, see image below for the locations: