We have started our work on moving to V10 and are looking for information for a mixed deployment strategy.
We are Windows, SQL, IIS, bound to AD and can currently access Portal/EMSS from both our internal and external web servers.
For our V10 instance we would like to have the following capabilities:
A) Use Ming.le for S3 application users (since it is the supported method by Infor)
Use standalone Portal for our external EMSS access (since it is allowed by Infor and we want to keep the interface simple for our non IT centric EMSS users)
C) Maintain the ability for our S3 app users to use Portal without Ming.le using our internal IIS (strictly for business continuity reasons IE: Ming.le or external IIS server are down)
An additional complexity is we have EMSS bookmarks to 3rd party sites that only work on our external IIS which means our S3 users will also need to access EMSS through the external. (Long story but in short it is related to the 3rd parties SSO code to authenticate us)
Questions:
1) Where should Ming.le be installed in this scenario on the DMZ or behind the firewall and what are the pros and cons of each?
2) If Ming.le cannot or should not sit on the DMZ, is it possible for a Ming.le session behind the firewall to render the external Portal (both S3 and EMSS)?
3) If not will end up having to use 2 different URL's - the external for EMSS and the internal Ming.le for apps?
4) Is there a better or simpler way to do accomplish the requirements I have presented above?
Thank you!
