I have been reading the documentation on installing the EWA server, but haven’t found specific instructions on how to just install the EWA onto a separate webserver. Do I have to install the Epicor App onto the webserver with the release ISO first, and only select the supplemental installs? Or do I need to install it on the Epicor server, then move the site over to a different server? Any guidance would be appreciated.
hi
I am also interested to hear what people recommend. i think you would need to install the app Server on the server you intend to use EWA server on. then stop the app pool running for the full client. although not sure the web client will still run after that?
Graeme
I would install the Epicor Application Server and then install EWA. This can be done other ways but I like this way because it has a separate application server (iis & pool). If you ever decide to allow external access via EWA you will be headed in the right direction.
1 Like
That seems to be the only option I found while installing it onto a test server. If I tried referencing the root Application server, it kept erroring out. So I ended up installing a new app server referencing the same database, and it seemed to work. I am testing reporting and other things now to make sure all of that works.
Not sure it existed at the time of this post last year, but we have recently had a consultant deploy EWA on a remote server and he used a remote setup environment including an executable which was essentially a mirror of the Epicor Admin Console.
I know you’ve likely completed your deployment, but figured i’d leave this here for anyone else who comes across it
There is an option “Publish Extension Installers” in the admin console. That option should guide you through publishing EWA to another server.
We have EWA broken out. It does require a separate app server installed. The only real use is for us is to access ECC.
Hi,
I’m trying to install “Publish Extension Installers”.
Do you know “Guide document” about this?
Thanks with regards,