Select to view content in your preferred language

How to Host an Experience Builder Dev App for AGOL

761
7
03-09-2026 12:33 PM
Labels (1)
cjms
by
Regular Contributor

After creating an Experience Builder App with Developer Edition, how can I host it and then display it in AGOL?

I was following along on this intro video, and after deploying to IIS via a virtual directory, the speaker just says "...depending on your share settings, it could be hit publicly...".

https://www.youtube.com/watch?v=YLBxBio96a8

The documentation also says:

"The experiences you create with developer edition of ArcGIS Experience Builder can be downloaded and hosted on a web server", but no further directions on how to host on a web server.

What are the next steps to get my app viewable to the public from a friendly url (not the server name)?

As someone who is not a developer, tutorials with videos / screenshots are most helpful if possible.

 

This session guides the audience through the setup process and core workflows of ArcGIS Experience Builder Developer Edition. We will cover importing apps from ArcGIS Online or ArcGIS Enterprise, building a basic custom widget, deployment patterns, upgrading apps, and moving apps from one ...
0 Kudos
7 Replies
ToddW_stl
Esri Contributor

Do you have a web server you can host it on?  The solution to a similar question says there is no way to host it on ArcGIS Online.

cjms
by
Regular Contributor

Yes I have a server, I'm just curious what the next steps are from putting it on IIS to making it public and available to navigate to on AGOL

0 Kudos
ToddW_stl
Esri Contributor

@cjms - from my relatively recent experience of getting started with ExperienceBuilder Dev Edition and hosting to an internal web server, this is what I'd review and likely stumble through:

  1. Create a Client ID (Esri docs)
  2. In ExperienceBuilder Dev Edition - Configure the app as desired
  3. In ExperienceBuilder Dev Edition - Save and Publish the app
  4. Create a Web Site (Microsoft docs)
  5. How do I make my website public? (Microsoft docs)
  6. In ExperienceBuilder Dev Edition - Download the experience (do not check clientID box)
  7. In Windows File Explorer and a text editor - Deploy the experience (step 3 in the linked doc was done in step 1 of this bulleted list)
    1. note: when you unzip the folder to the web server, the name of the (bold) folder in  "C:\inetpub\wwwroot\appName" will be the name in the url (i.e. https://www.webServer.com/appName/index.html" (or something similar depending on your web server/network architecture)
  8. If users get some kind of authentication/log in error (I'm unsure if you will have any restricted/protected ArcGIS Online services in the public facing app) - Add the deployed app URL into the ClientID Settings > Redirect URLs section - see step 7 under Create a ClientID
  9. To add the app as an ArcGIS Online item - see Add an app from a URL
    1. I was working in ArcGIS Enterprise 11.5 and chose:  Content > New Item > Application > Web Mapping > paste app URL > give item a name > Save > Mark as authoritative

This is the extent of my (current) knowledge, so let me know how it goes and I'll try to track down some answers!

ToddW_stl
Esri Contributor

I guess I also could have looked at who presented the video you linked...   🤔

I sent this to my friend @PaigeWaterbury  to review!  😁

PaigeWaterbury
Esri Contributor

Thanks for bringing this one to my attention, @ToddW_stl!

@cjms I agree with everything Todd said except for in step 6. Assuming you're working with the latest version of ExB Dev Edition (currently 1.19) I would recommend checking the clientId box, as this removes the need for you to go in and manually manipulate a JSON file.

ToddW_stl
Esri Contributor

Was that broken at 1.18 and fixed for 1.19?  I'll update my notes, if so.  I think i started on 1.18 and struggled with the client ID / Redirect URLs for a while, but whatever I did (above) eventually worked for me.

0 Kudos
PaigeWaterbury
Esri Contributor

I honestly can't speak to 1.18 on the clientId checkbox specifically. But I can confirm that in 1.19 the clientId is properly populated when you check that box.