Testing JSP Changes In IBM WebSphere Without ReStarting The Service
Read Time:50 Sec
This is a follow-up to my previous post “Restricting The EnterpriseOne Evironment On The JAS Server“.
While coming up with my solution to how to restrict users to an environment when logging on to a JAS server that hosted a path code with multiple environments attached to it, I wanted to be able to test my changes “on-the-fly”. I didn’t want to restart the service every time.
So, that’s when I found the “temp” directory.
- This is the “production” directory:
C:WebSphereAppServerprofilesdefaultinstalledAppsNode01CellJPD811_HTML.earwebclient.warshare
- This is the “temp” directory:
C:WebSphereAppServerprofilesdefaulttempNode01JPD811_84JPD811_HTMLwebclient.warshare
A file named “_html4env.class” will be placed in there when a user logs in. It is a compiled version of the “html4env.jsp” file. So, if you delete that file and make a change to the “html4env.jsp” file or the “_EnvRestriction.htm” file, when a user tries to login WebSphere will compile the “html4env.jsp” file and create a new “_html4env.class” file with your changes.
Average Rating