If you have custom or modified attributes in Active Directory, these can be used in LDAPSYNC with no additional configuration from the Maximo side.
You can filter on any attribute that objects have. If you want just a '&' use the special character &. The only gotcha is the XML formatting problems with the ampersand. Combined with the basedn, the filter is the other piece that specifies where you want the information from by using a standard LDAP filter. If you're not sure what basedn to use then you will need to contact your system administrator or use Microsoft Active Directory User and Computers tool to find the required users and most ideal location. If there is only a small set of users, then you can go deeper into the container (OU) structure to limit the users synced into Maximo. If you want the whole directory, point it at the DC level. LDAPSYNC connects directly to your directory so this will be the lowest point you want to sync users from. The basedn is the base domain name of your directory. (&(objectCategory=person)(objectClass=user)) What can be removed? This is the simplest user sync that can be used: The out of the box sync XML includes information that isn't required by Maximo. The third is the table mappings: Where do I want the information to go? The second is the attributes: What information do I want?
The first is the basedn and the filter: From where do I want the information? To simplify what usermapping xml does, break down its section. UserMapping - The XML used to choose what users and attributes to sync to maximo.
Default holds the global catalog connection port.