OAT consists of three utilities. You run each of these utilities in order. The first two steps of the process create a file that gets passed to the next step:
The first command creates the Active Directory User Information file (or the Active Directory Group Information file ) listing the Unix-enabled Active Directory users (or groups) that is passed to oat_match to create a map between Active Directory and local users or groups.
The second command creates the User map file (or the Group map file ) containing mappings between Active Directory and local users (or groups) that is passed to oat_changeowners to align file ownership.
The third command changes UID and/or GID of files and directories on local Unix hosts to the UID/GID maintained in Active Directory. Before you do this step you can manually create special files to pass into oat_changeowner, the Files to Process List file or the Files to Exclude List file . Finally, oat_changeowner produces the Processed Files List file .
Note: One Identity also provides an interactive script, named oat, that calls oat_adlookup, oat_match, and oat_changeowner utilities with appropriate arguments based on responses that you provide. For more information see Changing file ownership using the script.
The /opt/quest/libexec/oat/oat_example.sh script file shows you examples of running OAT without using the interactive script. Having the ability to run the oat utilities manually gives you flexibility when changing ownership. As noted in the example in Changing file ownership using the script, OAT is not limited when hosts do not use the same naming conventions.
Note: To see the arguments and options for each of these utilities, run them with a -h option. For example, to see the syntax for oat_adlookup, enter:
# /opt/quest/libexec/oat/oat_adlookup -h