Skip to main content

The deployment of migrated data in VertiGIS Networks

Updated

Aim

After the successful migration of data (e.g. GEONIS / UT for ArcGIS) into the VertiGIS Networks data models using the VertiGIS Networks Migration Tools, the migrated data can be deployed manually in the VertiGIS Networks Solutions.

 

Prerequisites

The required software components and system requirements can be found here. You will also need:

  • a user for Portal for ArcGIS with the user type "Creator", the role "Publisher" and the ArcGIS Advanced Editing Add-On license,
  • ArcGIS Pro (connected to Portal for ArcGIS),
  • Utility Network Package Tools,
  • a SQL Server, PostgreSQL or Oracle installation with the necessary authorizations to create a database, a user, a role, etc.,
  • the migrated data as an "Asset Package",
  • the VertiGIS Networks Domain Packages and Solution Packages (Explorer, Editor, Simulator) provided to you by your local sales representatives.

 

Preparation

The "Asset Package" will be published manually via ArcGIS Pro.

  1. In the VertiGIS Networks Domain Package open the project file e.g. "VN_Core-DataModel.aprx" with ArcGIS Pro.
  2. Log in to your Portal for ArcGIS.

 

Overview of the process

Create a database 

The Enterprise Geodatabase can be created with the following database management systems: Oracle, PostgreSQL and SQL Server. This instruction describes the creation of the geodatabase with SQL Server and PostgreSQL.

SQL Server

  1. Preparation of the Enterprise Geodatabase

    In this step, an Enterprise Geodatabase and a database user (geodatabase administrator) are created. 

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Enterprise Geodatabase

    Parameters:

    Database Platform "SQL-Server"
    Instance e.g., server.domain.com
    Database name of the database e.g., berlin_un
    Operating System  don't check
    Database Administrator usually "sa"
    Database Administrator Password set a password
    Sde Owned Schema check
    Geodatabase Administrator Password respect Windows password policies
    Authorization File file path

     

  2. Connect to SQL Server Enterprise Geodatabase with database administrator

    A connection will now be established between ArcGIS and the SQL Server Enterprise Geodatabase with the administrator.

    See: Connect to Microsoft SQL Server from ArcGIS

    Catalog> Databases > Right-click > New Database Connection

    Parameters:

    Database Platform "SQL-Server"
    Instance e.g., server.domain.com
    Authentication Type "Database authentication"
    User Name database administrator e.g., "sa"
    Password the database administrator password set in step 1
    Connection File Name is generated automatically, adjust if necessary

     

  3. Create Database Role

    In preparation for step 4, the creation of a database user, a database role must first be created. 

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Role

    Parameters:

    Input Database Connection the .sde connection file (administrator) created in step 2 e.g., SQLServer-servername-berlin_un(sa)
    Role name of the role e.g., R_SDE_OWNER

     

  4. Create Database User

    Creates a database user with privileges sufficient to create data in the database.

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Database User

    Parameters:

    Input Database Connection the .sde connection file (administrator) created in step 2 e.g., SQLServer-servername-berlin_un(sa)
    Create Operating System Authenticated User leave empty
    Database User enter a name e.g., berlin_un_owner
    Database User Password respect Windows password policies
    Role the role defined in step 3 e.g., R_SDE_OWNER
    Tablespace Name leave empty

     

  5. Connect to SQL Server Enterprise Geodatabase with database user

    A connection is now established with the user between ArcGIS and the SQL Server Enterprise Geodatabase.

    See: Connect to Microsoft SQL Server from ArcGIS

    Catalog> Databases > Right-click > New Database Connection

    Parameters:

    Database Platform "SQL-Server"
    Instance e.g., server.domain.com
    Authentication Type "Database Authentication"
    User Name the database user defined in step 4
    Password the database user password set in step 4
    Connection File Name is generated automatically, adjust if necessary

     

  6. Activate Branch Versioning

    As the utility network does not support traditional versioning, branch versioning is required.

    See: Connect to a branch version

    Catalog > Databases > Right-click on the user's database connection file created in step 5 > Geodatabase Connection Properties > select versioning type "Branch" 

 

PostgreSQL

Prerequisite

The utilization of spatial data in a PostgreSQL database requires at least one of the following prerequisites:

 

  1. Preparation of the Enterprise Geodatabase

    In this step, an Enterprise Geodatabase and a database user (geodatabase administrator) are created. 

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Enterprise Geodatabase

    Parameters:

    Database Platform "PostgreSQL"
    Instance e.g., server.domain.com
    Database name of the database e.g., berlin_un
    Database Administrator usually "postgres"
    Database Administrator Password set a password
    Geodatabase Administrator Password respect Windows password policies
    Tablespace Name leave empty
    Authorization File file path
    Spatial Type "ST_Geometry" or "PostGIS"

 

  1. Connect to PostgreSQL Enterprise Geodatabase with database administrator

    A connection is now established between ArcGIS and the PostgreSQL database. The user "sde" (geodatabase administrator) is used for this in order to create roles and assign authorizations to a new user created in the following steps.

    See: Connect to PostgreSQL from ArcGIS

    Catalog> Databases > Right-click > New Database Connection

    Parameters:

    Database Platform "PostgreSQL"
    Instance e.g., server.domain.com
    Authentication Type "Database authentication"
    User Name database administrator e.g., "sde"
    Password the database administrator password set in step 1
    Database the name of the database set in step 1
    Connection File Name is generated automatically, adjust if necessary

 

  1. Create Database Role

    In preparation for step 4, the creation of a database user, a database role must first be created. 

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Role

    Parameters:

    Input Database Connection the .sde connection file (administrator) created in step 2 e.g., PostgreSQL-servername-berlin_un(sde)
    Role name of the role e.g., "R_SDE_OWNER"
    Grant To or Revoke From User(s) "Grant role"
    User Name(s) leave empty

 

  1. Create Database User

    Creates a database user with privileges sufficient to create data in the database.

    Geoprocessing Tool: Geoprocessing> Data Management Tools > Geodatabase Administration > Create Database User

    Parameters:

    Input Database Connection the .sde connection file (administrator) created in step 2 e.g., PostgreSQL-servername-berlin_un(sde)
    Create Operating System Authenticated User don't check
    Database User enter a name e.g., berlin_un_owner
    Database User Password respect Windows password policies
    Role the role defined in step 3 e.g., R_SDE_OWNER

     

  2. Connect to PostgreSQL Enterprise Geodatabase with database user

    A connection is now established between ArcGIS and the PostgreSQL Enterprise Geodatabase with the user.

    See: Connect to PostgreSQL from ArcGIS

    Catalog> Databases > Right-click > New Database Connection

    Parameters:

    Database Platform "PostgreSQL"
    Instance e.g., server.domain.com
    Authentication Type "Database Authentication"
    User Name the database user defined in step 4
    Password the database user password set in step 4
    Database the name of the database set in step 1
    Connection File Name is generated automatically, adjust if necessary

 

  1. Activate Branch Versioning

    As the utility network does not support traditional versioning, branch versioning is required.

    See: Connect to branch version

    Catalog > Databases > Right-click on the user's database connection file created in step 5 > Geodatabase Connection Properties > select Versioning type "Branch" 

 

Import Data

  1. Create ArcGIS Utility Network in the Enterprise Geodatabase

    Before the database can be filled with the content of the Asset Package, the database structure of the ArcGIS Utility Network is created.

    Geoprocessing Tool: Geoprocessing > Utility Network Package Tools > Stage Utility Network

    Parameters:

    Target Geodatabase the .sde connection file (user) e.g., SQLServer-servername-berlin_un(berlin_un_owner) / PostgreSQL-servername-berlin_un(berlin_un_owner)
    Service Territory Feature Class feature class of the asset package
    Feature Dataset Name e.g., UtilityNetwork
    Utility Network Name e.g., UtilityNetwork

 

  1. Populate the Enterprise Geodatabase with the Contents of the Asset Package

    Geoprocessing Tool: Geoprocessing > Utility Network Package Tools > Asset Package > Apply Asset Package

    The duration of this process depends on the amount of data and can take from a few minutes to hours. Only limited information on the progress of the process is displayed via the user interface.

    Parameters:

    Asset Package file path to Asset Package
    Domain networks to apply select domains
    Input Utility Network Utility Network must be selected from the Enterprise geodatabase (via the user's connection file).
    Load data check

 

  1. Enable Branch Versioning of all Feature Datasets

    See: Connect to a branch version

    Catalog > Databases > Expand connection file of the user > Right-click on every feature dataset > Properties > Manage >  check "versioning"

 

  1. Enable Network Topology

    The network topology must be activated in order to trace the network features, apply the network schemas, and to create dirty areas to validate the network.

    Geoprocessing Tool: Geoprocessing > Utility Network Tools > Administration > Enable Network Topology

    Parameters:

    Input Utility Network File from the Enterprise Geodatabase (via the user's connection file) 

 

  1. Save and close the ArcGIS Pro Project

 

Prepare Content for Publishing

  1. Rename the File Geodatabase (.gdb)

    This step is required to trigger the ArcGIS Pro “repair” function of the data sources of the Publisher Map. As soon as the correct data source for the Enterprise geodatabase has been set for the first layer (click exclamation mark) in the next step, the correct data sources for all layers (with exclamation mark) are applied to the map.

     

  2. Start the ArcGIS Pro Project again

     

  3. Open the Publisher Map and Consumer Map(s) in the project

    The symbolization of the consumer map(s) can either be set up or imported via a .stylx file from the VertiGIS Networks Domain Package. The symbolization is not relevant for the Publisher Map.

     

  4. Set data source of the Publisher Map to the Enterprise geodatabase (via the user's connection file)

    See: Repair broken data sources for layers and tables

     

Publish Feature Service and Web Map(s)

  1. Register Data Source with the Server

    To be able to reference and possibly also edit web layer data in an enterprise geodatabase, register the database with the server that is connected to your portal.

    See: Manage Registered Data Stores: Register a database as a data store

    Share ribbon > Manage group > Data Stores > Add > Database

    Parameters:

    Title define a name e.g., Berlin_UN
    Tags optional
    Portal Folder optional
    Publisher database connection Import > select user's connection file (.sde file)
    Server database connection "Same as publisher database connection"
    Select the servers to which you want to add your data store Select server and click "Validate"
    Sharing Level e.g., "ArcGIS Enterprise"

 

  1. Create folder, e.g., "Berlin_un" in Portal for ArcGIS and ArcGIS Server Manager (optional step for a better overview)

 

  1. Publish the Publisher Map as a Web Layer

    See: Share a web feature layer

    Share ribbon > Share as group> drop-down arrow Web Layer > Publish Web Layer

    Name e.g., "Publisher Map"
    Reference registered data select option "Map Image" and check the "Feature" check box
    Portal Folder e.g., "Berlin_un"
    Server and Folder select server, folder e.g., "Berlin_un"
    Share with e.g., "ArcGIS Enterprise"

 

  1. Set data source of the Consumer Map(s) to the Feature Service created in step 3

    See: Repair broken data sources for layers and tables

 

  1. Publish the Consumer Map(s) as Web Map(s)

    See: Share a web map

    Share ribbon > Share as group> Web Map

    Name e.g., "Consumer Map"
    Portal Folder e.g., "Berlin_un"
    Share with e.g., "ArcGIS Enterprise"

 

Deployment of VertiGIS Network Solutions

In this step, the published feature service is first registered as a data source. A new VertiGIS Network Solution can then be deployed.

  1. Start the Solution Manager

     

  2. Register Data Source

    The feature service must be registered as a data source for use in a deployment and thus made accessible.

    See: Manage Data Sources

    Data Sources section > Not registered tab > action menu of the feature service > Register > choose data source name, version and domain(s)

    Now the registered data source will appear in the registered data sources area.

 

  1. Perform Deployment

    See: Perform DeploymentDeployment section > for a new deployment > Choose the solution package, data source, and web map > enter additional Parameters > Validation > complete the Deployment

    For details on the parameter values, see the user manuals of VertiGIS Network Editor, VertiGIS Network Explorer und VertiGIS Network Simulator.

     

  2. Open the Application

    Deployment section > action menu > Start App

     

  3. Optional: Configuration

    VertiGIS Networks Solutions can be customized with all the options offered by VertiGIS Studio Web Designer.

    Deployment section > action menu > Open App in Designer

Related articles

Comments

0 comments

Please sign in to leave a comment.