Is this a valid configuration? Web map on Portal consumed by Story Map on different server

Question

I would like to add a web map from my organization's Portal to a Story Map served on a separate server (still within our network).

Is this a valid (supported) configuration?

Web map and it's layers are shared with everyone and I'm able to pass the web map's ID successfully.  But, the web map won't render in the Story Map app - it's looking for siblings of the mapContainer which is undefined.

This is where it fails (Dev tools debugging):

this.getMapConfig = function(response, mapContainer)
...
legend: new Legend(
  response,
  app.isInBuilder,
  getLegendSettings(
mapContainer, response.itemInfo.item.id)
  ),
...

response

object is populated, so it seems like the web map is being accessed.

AravindatStoryMaps · Answer

Hi Lisa,

Housing it under Portal and outside are both two valid configurations, deployment-wise. As a test, can you try to deploy the same storymap app in the server running Portal to see if it behaves differently?

If it does, then the machine you previously deployed it on isn't able to interact or allow network interactions between the server running Portal and the server deploying the app.

Hope this makes sense.

Thanks,

Aravind

LNelson · Answer

Hello,

I did modify the URL in the config.js file.  Perhaps the issue is that the Story Map template is not on a server running Portal or AGOL. Instead, it's on one of our webservers.

So, for a template to work, does it have to be 'housed' under Portal or AGOL?

Thanks,

Lisa

AravindatStoryMaps · Answer

Hi,

Is the URL to your Organization modified to reflect your Portal for ArcGIS URL in the story maps template javascript file? If you share the template of the story maps it should be easy to determine where to include the Portal URL.

I suppose if the Story Maps application is served on a browser that supports CORS (IE 10 and later, Google Chrome, Microsoft Firefox) then you shouldn't have a problem connecting to the webmap for Portal which contains a different origin URL than the application URL.

Thanks,

Aravind