Select to view content in your preferred language

Bulk publishing from SDE datastore versus Other publishing methods

1196
4
11-30-2022 11:58 PM
Labels (2)
GeorgieCassar1
Occasional Contributor

Our aim is to publish many feature layers from our SDE geodatabases.   (ArcGIS v 10.9, SQL Server 2017)

We want the portal user to find data easily using tags and categories.   We have applied metadata nicely  within SDE.  (Descriptions, Tags, etc)     These layers are for querying and analysing only (not editing).

How do most large organisations publish their layers for these Portal users ??

1.  Bulk publish (Sync) their SDE datastore connections and share accordingly

2.  Create a few monster map documents and publish those from Pro.

3.   Use a script to publish a single feature service for each layer.  

 

Test so far prove that number 1 works OK.  The tags and descriptions can be searched when finding layers.   

Although I find the administration of the datastore a little cumbersome as I have to ensure the database connection username has access to the layer first.

Approach number 2 is not helpful because all the sub-layers of a feature service do not store their individual Tags or descriptions.  So the user can't search for the individual layers.

Approach number 3.   Is this worth pursuing ?

What do large ArcGIS Enterprise clients normally do here ?

4 Replies
MarlonAmaya
Esri Contributor

@GeorgieCassar1 

You may be able to accomplish option 3 using the Bulk publishing from Portal. There are some considerations that you need to take with this option.

https://enterprise.arcgis.com/en/portal/latest/use/bulk-publish-arcgis-server-feature-layers.htm

 

Marlon

0 Kudos
GeorgieCassar1
Occasional Contributor

Thanks Marlon, this is what we already do so we are on the right track I guess.

Tags and descriptions go through to the metadata in the published services but it seems the metadata tool in ArcPro (ISO19115-3)  does not accept 'custom' topic categories so we will need to maintain those separately in Portal only.  The topic categories in the ISO standard are too broad for local government.

0 Kudos
Raj-Chavada
Regular Contributor

Good topic! We use No.2 for server our authoritative content to end users but struggling to identify a use case of No.1 in our team ever since this functionality was released back in 10.7.1. It seems like No.1 has limitations - no control over styling or pop-up configuration, can't publish spatial views.  Perhaps, No. 1 is better suited for extremely urgent publishing from EGDB to spin up apps that don't requiring any use of APRX for controlling the layer configurations. 

0 Kudos
GeorgieCassar1
Occasional Contributor

It appears there's different limitations with either method.  Method 1 is good for carrying through metadata from the enterprise GDB, allowing users to search but it doesn't maintain links to related tables (eg. the inspection tables we use for field work).  Not so good for defining style but we train our Portal users to modify styles in web maps.

Method 2 is better for defining layer style prior to publishing.

0 Kudos