Hi @Vignesh29332420nfcx ,
What has been tried and what is not working?
Technically this is feasible.
You create a fully functional express react SPA and host onto runtime action as web assets. When you hit the runtime action url, for example https://712511-demo.adobeio-static.net , it must run the react app successfully. Then you load this app into calling application.
I implemented a pattern like this:
- Built the react app and deployed onto App Builder
- At AEM Dispatcher, normal website urls always hit AEM publisher
- But created a reverse proxy, for specific url, request proxies to App Builder (https://712511-demo.adobeio-static.net) instead of publisher.
- And provided link to portal on main website nav.
- So normal browsing, user sees AEM pages.
- Upon clicking portal link, AppBuilder runtime is invoked, web assets served and react page works.