My recommendation would be to do the following:
- Set up your infrastructure so that the WildFly server is the front-line HTTP server.
- Configure WildFly as a reverse-proxy which forwards all requests for your legacy IIS-based application to your IIS infrastructure (possibly even on a separate private subnet; that's up to you).
- Once you finish migrating all your applications off of IIS, you can just shut down that server and no other infrastructure changes are necessary.
There's a very good amount of information about configuring a WildFly-based reverse proxy online; Google turned up lots of references.
1 of 1 people found this helpful
02 Hi David,
Finally got it worked.. just followed as is here HOWTO: Set Up IIS and the Jakarta isapi_redirect Connector - Techstacks HOWTO's and I got it
worked. Now IIS is front-end and Wildfly is back end.