WAS common document processing

WAS cache leads to modify the file does not take effect problem:
Solution:
First, modify the web.xml file, you need to modify the following three files in the directory:

1. /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/ ${cell 名}/applications/$ {application name} .ear / deployments / $Application name} {/$ {application name} .war / WEB-INF
2. /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/ ${cell 名}/applications/$ {application name} .ear / deployments / $Application name} {/$ {application name} .war / WEB-INF
3. /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/ $Name} {cell /$ {application name} .ear / ${Application name} .war / WEB-INF Second, modifying jsp file, replace jar package, and when other inter web.xml profile of a need to modify the place: / opt / IBM / WebSphere / AppServer / profiles / AppSrv01 / installedApps /${cell
   Name} / ${Application name} .ear /$ {application name} .war / WEB-INF
   out of service, restart after modification
   (ps: Stop according server- "node-" app embodiment; restart startup in reverse direction)
   three, the default WAS the temporary directory
   was default temporary directory as follows, user-initiated was the process under Linux have a default temporary directory
   file permissions (rwx), if not, it may cause jsp compiler is not a class
   / opt / IBM / WebSphere / AppServer / Profiles / AppSrv01 / wastemp
   / opt / IBM / WebSphere / AppServer / Profiles / AppSrv01 / the TEMP
   above default temporary directory delete like, was when the process starts automatically created
   if you want to back up, the direct use cp command, do not use the mv command, Do not create a new wastemp and
   temp, even if also pay attention to the new directory file permissions (rwx)
   If the application is a normal visit, was also to display the console, but the login [size = x-large] was the control
   station when the newspaper Http500 wrong, perhaps the system is the lack of storage space, Linux use df -H view
   , the disc can add or delete useless files.
   If you publish the application environment cluster was found the time to slow or stuck, check the log, perhaps
   DM (Deploy Manager) memory configuration is not set [/ size]
   the JVM memory parameters and character set issues
   1, enter [application servers> server1> Process Definition> Java Virtual Machine] to modify the recommended most
   small virtual memory 256M, the largest 2048M above .
   (this reference items and computer memory size is set)
   . (after modification, etc., need to restart WebSphere)
   -Dfile.encoding = UTF--Ddefault.client.encoding. 8. 8 = UTF-
   view was relevant log
   1 / opt / IBM / WebSphere / AppServer / Profiles / AppSrv01 / logs / server1 /
   SystemErr.log - error log output
   SystemOut.log - console output, you can view the log output system.out
   determine whether the object is still alive