Troubleshooting
Problem
New code may not be compiled because it has previously been compiled.
Resolving The Problem
Screen Changes, Custom Code, Hot Fix, Patch changes are not Visible After Redeploying New Maximo.ear File. New files may not be compiled and/or cached because they had previously been compiled.
Solution
WebLogic
WebLogic 6,7,8
Before starting the Maximo Server delete the .wlnotdelete folder under the Maximo Server application domain in the correct domain folder.
WebLogic 9,10
Before starting the Maximo Server delete the tmp folder under the Maximo Server application domain in the correct domain folder (i.e. bea\user_projects\domains\mydomain\servers\MAXIMOSERVER\tmp)
WebSphere
Before deploying the new Maximo.ear file, delete the temporary files from the WebSphere folder.
The temporary files are located in the WEBSPHERE\APPSERVER\PROFILES\<profilename>\TEMP\<servername>\<appserver>(i.e. c:\WebSphere\AppServer\profiles\Custom01\temp\prodserverNode01\MAXIMOSERVER)
Delete the App Server folder.
The Maximo.ear file can now be deployed
Before connecting to Maximo delete the temporary files in Internet Explorer.
To delete the temporary files in Internet Explorer
1. From Internet Explorer select Tools/Internet Options...
2. Click the Delete Files... button in the Temporary Internet files section
3. Click OK from the Delete Files dialog box
Historical Number
M03389
Product Synonym
MAXIMO
Was this topic helpful?
Document Information
More support for:
IBM Maximo Asset Management
Software version:
5.1, 5.2, 6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.5, 7.6
Document number:
348089
Modified date:
17 June 2018
UID
swg21262513