ezazsterrI have read some places that it uses the appserver to actually connect to the database as webclient cannot directly communicate with the database.
That is correct.
ezazsterrHow easy it is to implement, what all changes are need on the application end so that it can work with the webclient Right now we have a shared drive that is having all the application code that is mapped with everyone using the application developed in progress, they are executing the application on their own machine.
That all depends on what your application code currently looks like. Specifically, how well the business logic is seperated from the UI logic, or how easy it is to disentangle those.
ezazsterrWe have the business logic and the ui mingled up together
.. and that probably means that moving to an appserver is no quick fix for you. you'll probably be facing a lot of effort to rework the code so business logic can run on the server, and UI can stay on the client.
ezazsterrRight now we have a shared drive that is having all the application code that is mapped with everyone using the application developed in progress, they are executing the application on their own machine.
What *could* be a quick fix, is to reconfigure this so the client machines run from a local copy of the application code.
Right now it's not just database traffic that goes over the network, it's *everything* the application does. Keeping the application code local means it can load faster, and frees up the network bandwidth that's currently consumed by file sharing protocols.