If you can't log in after performing Prashant's answer, make sure you don't have mxe.useAppServerSecurity=1 in your maximo.properties. If this is your problem, remember to set the maximouser role mapping back to Special subject Everyone during or after your deployment.
We came across a similar issue one of our clients. To correctly generate PM work orders with dates in the right timezone you must do two things. Set the time zone for the asset/location/site/org. No need to set for all the object though. In our case we defined the timezone only at org/site level...
Thank you, Steven. That gives me a little more insight into the background of the issues. We requested the newest iFix for Maximo Mobile for EAM. Hopefully, that helps with the immediate mobile need. For the PM example you mentioned, I tried associating a time zone to the asset & generating a PM...
Hoping this group has some detectives or additional ideas to pinpoint and correct time zone issues in our Maximo system. I'm not sure IF or how these are related, but I am including all the time-zone related items. 1) Since our Maximo SaaS Flex Implementation, the PM Target Start Time field PM...
I finally identified the problem: it is a cache shared by multiple modules in the EAR which could contain a different value of useAppServerSecurity than what is traced in the log. Details: every web module config (web.xml) in Maximo ear contains the parameter "useAppServerSecurity" whose value...
Contact us with questions or feedback.
Join CommunityInvite ColleaguesLearn MoreGet Started on MORE
About UsTerms of Use