How to Publish GIS Services Using ArcGIS Pro (Enterprise-Ready Guide)

 

How to Publish GIS Services Using ArcGIS Pro (Enterprise-Ready Guide)

Audience: GIS Engineers | Enterprise GIS | Utility GIS | Data Migration Teams
Platform: ArcGIS Pro + ArcGIS Enterprise / Portal

---

Why Publishing Services Matters in Enterprise GIS

Publishing services allows GIS teams to:

• Share authoritative data across the organization
• Enable web maps, dashboards, and mobile apps
• Support enterprise workflows and integrations
• Maintain a single source of truth

ArcGIS Pro is the primary tool for publishing modern GIS services to ArcGIS Enterprise.

---

Types of Services You Can Publish from ArcGIS Pro

Service Type	Best Use Case
Feature Layer	Editing, web apps, dashboards
Map Image Layer	High-performance visualization
Vector Tile Layer	Fast rendering for large datasets
Scene Layer	3D visualization
Image Service	Raster and imagery data

---

Prerequisites Before Publishing

• ArcGIS Pro signed in to Portal
• Proper publisher/admin role
• Data stored in Enterprise GDB (recommended)
• Clean data (repair geometry, remove duplicates)
• Valid spatial reference

---

Step-by-Step: Publish a Feature Service from ArcGIS Pro

Step 1: Prepare the Map

• Add feature classes to the map
• Apply symbology and labeling
• Remove unnecessary layers

* Tip: What you see in the map is what gets published.

---

Step 2: Share as Web Layer
You can start publishing in two ways:

Method 1

1. Select the layer in the Contents pane
2. Go to Share tab → Web Layer → Publish Web Layer

Method 2

3. Right-click layer → Share As Web Layer

👉 Both methods open the same publishing wizard.

---

Step 3: Configure Service Properties – Field-by-Field Explanation

These settings decide performance, security, and maintainability.

1️⃣ General Section

Name, Summary, Tags & Categories

🔹 Name

What it is:
The official name of your service in Portal & Server.

Best practice examples:

TX_UG_Pipelines_Edit

TX_OH_Lines_View

ENV_Vegetation_ReadOnly

Why important

• Easy to find
• Supports automation
• Avoids confusion between Dev/Test/Prod

---

🔹 Summary

What it is:
Short description of what the service does.

Example

“Enterprise underground pipeline feature service for editing and analysis.”

---

🔹 Tags

What it is:
Keywords to help search in Portal.

Example

Transmission, UG, Pipelines, Utility Network

---

🔹 Categories

What it is:
Portal classification for governance.

Example categories

• Enterprise GIS
• Transmission
• Utilities

---

2️⃣ Data and Layer Type

---

🔹 Reference registered data ✅ (Recommended)

This means:

The service uses data directly from the Enterprise Geodatabase.

Options you see

✔ Map Image

• Best for read-only, high performance
• Good for large datasets

✔ Feature

• Best for:
• Editing
• Web apps
• Dashboards
• Mobile apps

✔ Map Image and Feature

• Publishes both:
• A fast map image layer
• An editable feature layer

* Enterprise recommendation

Use Map Image and Feature for most operational services.

---

🔹 Copy all data ❌ (Avoid for Enterprise)

This means:

Data is copied to the server and becomes separate from the main database.

Only use when:

• You do NOT have access to Enterprise GDB
• Small demo datasets

---

3️⃣ Location Section

---

🔹 Portal Folder

What it is:
Where the item appears in Portal.

Best practice
Create folders like:

Transmission

UtilityNetwork

Environment

---

🔹 Server and Folder

What it is:
Where the service is stored on ArcGIS Server.

Example you showed:

https://gis-dev.test.com/hosting

Best practice
Create folders like:

/Transmission

/UG

/Production

This helps:

• Admins manage services
• Easier troubleshooting
• Cleaner Server Manager view

---

4️⃣ Sharing Level

🔹 Owner

Only you can see the service.

Use when:

• Testing
• Draft services

---

🔹 Organization

Everyone inside your company can access.

Use when:

• Internal apps
• Dashboards
• Enterprise users

👉 Most common enterprise choice

---

🔹 Everyone (Public)

Anyone on the internet can access.

Use when:

• Public maps
• Open data
  ⚠ Use carefully (security risk).

---

🔹 Groups

Share with specific teams only.

Example:

DataTeam

TransmissionEditors

GISAdmins

Best for:

• Controlled editing
• Sensitive datasets

 

🔧 Configuration Tab

Share As Web Layer → Configuration

This tab decides how your service is exposed and which standards/integrations are enabled.

---

1️⃣ Layer(s)

Map Image ✅

Publishes a Map Image Layer.

Use when you need:

• High-performance, read-only maps
• Large datasets
• Enterprise dashboards and base maps

* Recommended for most enterprise visualization services.

---

2️⃣ Additional Layers (Optional – enable only if needed)

These options expose your service to non-Esri systems and open standards.

🔹 WMS (Web Map Service)

• For legacy systems or third-party GIS
• Use when other departments consume maps outside Esri

🔹 WFS (Web Feature Service)

• For external apps that need feature access
• Use when partners need to read GIS features

🔹 OGC Features

• Modern API-based access for enterprise integrations
• Use for web platforms and system-to-system data sharing

⚠ Enable only what is required—each option increases support scope.

---

3️⃣ Capabilities

🔹 WCS (Web Coverage Service)

• Mainly for raster/imagery services
• Not required for most vector layers

🔹 KML

• Allows viewing in Google Earth
• Enable only if business users request it

---

4️⃣ Finish Sharing

Analyze

Always click first to fix:

• Errors
• Warnings
• Unsupported fields

Publish

Deploys the service to:

• Portal
• ArcGIS Server
• Web maps and apps

---

Step 4: Analyze Before Publishing

Click Analyze and resolve:

• Geometry errors
• Unsupported fields
• Projection issues

📌 Never ignore Analyze warnings.

---

Step 5: Publish

Click Publish
Once complete, the service is available in:

• Portal
• Server Manager
• Web maps and apps

---

Best Practices for Enterprise Publishing

• Use registered data stores (avoid copying data)
• Follow naming conventions
• Enable only required capabilities
• Document service purpose and owner
• Test services before production release

---

Common Issues & Fixes

Issue	Solution
Publish fails	Run Repair Geometry
Slow service	Use Map Image Layer
Schema mismatch	Validate fields
Editing issues	Check privileges

---

Automation Tip: Copy Python Command

Every publishing action in ArcGIS Pro provides Copy Python Command.

This allows you to:

• Automate service publishing
• Re-publish services during migrations
• Maintain repeatable deployments

---