When Maximo 7.6 came out, the yellow background color on required fields was, unfortunately for many users, abandoned. Luckily changing this back is actually a pretty simple task. First, determine what skin you are using. The skin name can be found in the following system property: mxe.webclient.skin. In this example our skin name is tivoli13, […]
Recommended System Specifications (Non-Clustered Environment) – Maximo 7.6 Hardware is the backbone of any Maximo installation. That’s why understanding what the minimum standards for any system are is so important. Without this understanding you could undershoot them and have an incredibly poorly performing system or you could greatly overshoot them and waste resources. In this post, I have […]
Recommended System Specifications (Clustered Environment) – Maximo 7.6 Deciding on the correct hardware for a clustered Maximo environment can be a challenging task. Not all servers in a clustered environment serve the same function, nor are they subject to the same hardware load. This often creates some confusion, as hardware choice is server-type specific. Additionally, […]
The concept of EVERYONE group was introduced in Maximo v7. This brought a whole host of functionality changes which are described in detail here. Luckily though, it only brought with it one new configuration option. The ability to change what group is treated as the EVERYONE group. The reasons you would want to do this are fairly limited. They are almost entirely limited to the desire to use the group name EVERYONE for another purpose in Maximo.
The EVERYONE Security Group Explained Updated March 15, 2019 In Maximo, security group configuration is very important and when your security access is not behaving as expected, it can cause serious disruptions. Most often, issues with security groups can be chalked up to a logical error. However, in newer versions of Maximo security access issues […]