topic Re: Deploying experience to Apache in ArcGIS Experience Builder Questions

Deploying experience to Apache

MikeSousa — Wed, 03 Apr 2024 12:48:45 GMT

I've created an experience in Experience Builder Developer Edition, it works fine in the builder. I've published it and downloaded it. I then installed Apache (on Windows 11). I tested the Apache installation and it works. I copied the experience over to the area of Apache to display webpages. When trying to view it, it give a box

asking to Sign in. This did not happen in Experience Builder.

When I click OK, it tells me this:

Looks like it's trying to get to the data at Esri

I did fill in config.json with my Esri data:

"attributes": {
"portalUrl": "https://<my company>.maps.arcgis.com",
"isWebTier": false,
"clientId": "#$#$##$$$$",
"title": "feature_info_demo",
"description": "",
"type": "Web Experience",
"thumbnail": null
},

Any suggestions?

Thanks...

Re: Deploying experience to Apache

JeffreyThompson2 — Wed, 03 Apr 2024 13:06:54 GMT

When you were installing Experience Builder did you go through all the steps involving creating your credentials? Check that they are properly configured.

https://developers.arcgis.com/experience-builder/guide/install-guide/#create-client-id-using-arcgis-online-or-arcgis-enterprise

Re: Deploying experience to Apache

MikeSousa — Wed, 03 Apr 2024 13:18:00 GMT

Hi Jeffrey,

I originally went through this inorder to do development with Experience Builder Developer Edition. I'm not sure if I now need to add anything to it, but that may be it, although I don't know what that would be. I was able to run npm ci/start for both the client and server while doing development.

Thanks...

Re: Deploying experience to Apache

JeffreyThompson2 — Wed, 03 Apr 2024 13:45:38 GMT

The credentials wouldn't have anything to do with the npm commands, but if you were able to get past the select your portal/log-in screen, they probably aren't the problem.

Are all of your maps and data layers shared correctly?

Re: Deploying experience to Apache

MikeSousa — Wed, 03 Apr 2024 14:15:23 GMT

I think this solved my issue, I needed to add the additional redirect URL:

Now I see my webapp 🙂

Thanks...