Bentley Utilities Designer - Model Administrator Documentation

Hi All,

Does anyone know where I can download the updated documentation for the Model Administrator Spreadsheet?  I am trying to setup a project with an Oracle Spatial connection for Water only.

Thanks, Ian

Parents
  • Hi Ian,

    Are you looking for help with something that is not covered in the ModelingAdministratorProcess.pdf that is delivered with the product? If you've run into a specific issue, I can try to help you or have someone get in touch with you to assist.

    Thanks, Mike


    This is a test

  • Hi Mike,

    I am having a problem getting the Oracle connection and feature registration to work.  The script names in the XLS file have changed and this isn't reflected within the documentation.  When ever I export what I think is the correct file, it doesn't show as an Oracle registered feature.

    Cheers,

    Ian

  • Hi Ian,

    Model Administrator generates a non-registered features XFM Schema. The file (XFM Schema generated by Model Administrator) is BUD_OS2T.xml in the %UtilitiesDesignerROOTDATAMODELPATH%\BentleyUD\ directory.  From Geospatial Administrator, you first must register features and save this XFM Schema as something like BUD_OS2T_RegisteredFeatures.xml.  It is important (not mandatory) to rename the XFM Schema after you register features in order to have a before and after registered features XFM schemas.  If register features was not completely successful you are still able to access the non-registered features XFM Schema and try again.

    In registering features with Geospatial Administrator, you need make sure you have a valid oracle user login.  The definition for this login in Model Administrator is defined in the OracleSpatialSettings worksheet.  You register features in Geospatial Administrator via the Graphical Sources folder. (e.g., Graphical Sources > Oracle Spatial Connection > Named Connection > Register Features) using the BUD_OS2T.xml (XFM Schema generated by Model Administrator).  You can also test this connection in Geospatial Administrator (e.g., Graphical Sources > Oracle Spatial Connection > Named Connection > Test Connection) prior to registering features.

    When you register features, you should open Geospatial Administrator with parameters of:

    -expand=false -register_fullname

    You set these parameters by modifying Geospatial Administrator’s Shortcut properties.  For example:

    "C:\Program Files\Bentley\UtilitiesDesigner V8i\Map\bin\GeospatialAdmin.exe" -expand=false -register_fullname

    If you have successfully registered features, Geospatial Administrator will indicate this when viewing the features in Geospatial Administrator.  After this, you then perform an export from Geospatial Administrator.

    Please let me know if you have any other questions.

    Peace, Rodney


    This is a test

  • Hi Rodney

    I have tried your suggestion, and I now get the full table name (including the Oracle schema name).  I am trying to understand how your comments relates to the instructions in section 3.2.2.5.8, 3.2.2.5.9, and 3.2.2.5.10 (pages 53 and 54) of the Modeling Administrator Process PDF document.

    When I run the Export Function from the XLS file with the BUD_OS2T.XML file, it still isn't showing my features as being registered in Oracle.  And I am getting an 'Object Reference not set to an instance of an Object' error for each defined feature when I send a 'GDI CONNECT' KeyIn (which is run by a VBA script). 

    Regards, Ian

Reply
  • Hi Rodney

    I have tried your suggestion, and I now get the full table name (including the Oracle schema name).  I am trying to understand how your comments relates to the instructions in section 3.2.2.5.8, 3.2.2.5.9, and 3.2.2.5.10 (pages 53 and 54) of the Modeling Administrator Process PDF document.

    When I run the Export Function from the XLS file with the BUD_OS2T.XML file, it still isn't showing my features as being registered in Oracle.  And I am getting an 'Object Reference not set to an instance of an Object' error for each defined feature when I send a 'GDI CONNECT' KeyIn (which is run by a VBA script). 

    Regards, Ian

Children
No Data