Clear out the WAS temporary directories and cached files

If the IBM WebSphere Application Server deployment manager, node agent, or application server will not start, you can try clearing out the temporary directories and cached files.  Here are the steps to complete this procedure:

1. Stop the deployment manager, node agent, and application server
2. Back up the existing configurations
   1. Open a command line window as admin
   2. Navigate to PROFILE_ROOT\bin (i.e. D:\IBM\WebSphere\AppServer\profiles\profile1\bin)
   3. Run the command “backupConfig <backup file>”
   4. Repeat this backup step for every profile (Dmgr, AppSrv01, etc)
3. Rename or archive the following directories
   1. PROFILE_ROOT/wstemp
   2. PROFILE_ROOT/temp
   3. PROFILE_ROOT/config/temp
   4. Repeat this step for every profile
   5. These folders will be recreated when the servers are restarted
4. Delete the javasharedresources directory located at C:\Windows\System32\config\systemprofile\AppData\Local\javasharedresources
5. Initialize the OSGI configuration and clear the OSGI cache
   1. Open a command line window as admin
   2. Navigate to PROFILE_ROOT/bin
   3. Run command “osgiCfgInit”
   4. Run command “clearClassCache”
   5. Repeat this step for every profile
6. Start the deployment manager, node agent, and application servers