Janie, as Randall stated above we officially support "JBoss Enterprise Application Platform 7": ArcGIS Web Adaptor 10.5.x system requirements—ArcGIS Enterprise system requirements | ArcGIS Enterpr...
- While the innards of WildFly should more or less be the same as JBoss it's important to state that only JBoss is supported by name and so there may exist certain limitations on Technical Support should you run into issues.
That being said, it is technically possible to do so and I have deployed on Wildfly 11 on numerous occasions for setup of test environments. There are some quirks (for example, certain pages in Server Manager not appearing correctly) but these are usually browser-specific.
I have to agree with Randall that the performance boost is probably negligible in this case as you should also consider the hit you'll take if you're running the full-blown JEE stack version. I'm not sure about your needs but if you're set on not using Apache Tomcat, I would recommend:
- Reaching out to Esri Support Services to clarify the scope of support for WildFly - there's no point in spending the time to set up the environment if you can't get support for it. Since from our documentation JBoss EAP 7 is listed as supported and it is also stated that "Future updates on these application/web servers are supported unless otherwise stated," I can see WildFly 10/11 lying in the grey area as these should roughly equate to JBoss EAP 7/7.1. WildFly 13 might be pushing it as this one I think marks the development of EAP 8 (although it runs on 7 by default).
- If you find that it is acceptable to run a WildFly configuration, I'd suggest using the servlet-only distribution if you'd don't need all the extra functionality - this will cut back on both file size and CPU usage.
- Considering another Java EE Application Server which is supported by name. I have deployed on GlassFish 4.1.1 and the setup and configuration for that was quite simple.
