ColleenMcCretton 270002FD5R Visits (4701)
With the added security features and functions available in TPAE/Maximo version 7 configuring your security to work just the way you want it can be extremely complex and time consuming. Once you get it configured in dev/test you then need to move it to production – you don’t want to start from scratch. Fortunately, Migration Manager comes with some pre-defined object structures and a migration group to facilitate this. There are some important considerations to help you be successful.
The APPSECURITY Migration Group is dependent on other Migration Groups
· DATADICTIONARY – all of the conditions used in data restrictions, conditional option access, conditional UI and conditional domain values migrate in this group and need to be there before security can be migrated
· RESOURCES – this group contains the Person information. Every User has an associated Person record so this group also needs to be migrated before security, which contains User information.
The APPSECURITY migration group uses object structures for
and migrates this data from dev/test to production.
If you use LDAP and synchronize user and/or group and group membership information from a corporate directory you should synchronize before you migrate. Synchronization does not negate the need for security migration as there are elements such as user default insert site and security group authorizations that will not be able to be sync’d from the directory. Depending on your configuration you may need to make modifications to the default object structures and migration groups to most effectively move the data.
Our customer, UGL Services presented on this an other topics at PULSE this year. Follow this link to see their presentation: