Mapping user data
You can map additional user data to supplemental tables within the Profiles database and then display that data in a user's profile.
When the LDAP directory provides a code or abbreviation for a particular setting, the supplemental table can provide extra data. For example, an employeeType
in the LDAP directory might correspond to Permanent. If the employee-type table is populated with data such as p;permanent
, this extra data can be displayed in the profile.
file stores the settings that determine how the files are formatted.
These properties are supplied in the profiles_tdi.properties
file. The file path specified is relative to the TDI solution directory.
This step is mandatory if one or more entities have been selected as the Group By
filter in Metrics. Otherwise, when you categorize the Metrics report by this entity, the report will show an unknown value, not the descriptive name of the entity in the chart. Metrics have three default Group By
. The country
attributes are in the supported list.
The mapping task for Profiles maps your user data to the following entities:
Add country data to each profile. Use Country code script ./fill_country.sh or fill_country.bat to populate the Country table. Fill departments
Add department data to each profile. Use Department code script ./fill_department.sh or fill_department.bat.Fill organization
Add organization data to each profile. Use Organization code script ./fill_organization.sh or fill_organization.bat.Fill employee types
Add employee-type data to each profile. Use Employee type code script ./fill_emp_type.sh or fill_emp_type.batFill work locations
Add location data to each profile. Use Work location code script ./fill_workloc.sh or fill_workloc.bat.
A CSV (comma separated value) file is required as input for each of these tasks.
The following properties pertain to the CVS files used by these tasks:
The separator character separates the different tokens in each line. The second property is the name of the file, relative to the solution directory.
The first token is the code. The next attributes are read in order for each additional field. No other fields are required.
The data that can be populated in these tables is usually provided as two values per line: code
For the workloc
code, the values can be code
. For example: WSF;FIVE TECHNOLOGY PARK DR;;WESTFORD;MA;01886-3141
Fields that you do not require in your mapping can be omitted from the file; this example uses only one addr field.
The default file name for each codes is shown in the following list:
Sample CSV file
This sample shows some lines from the isocc.csv
file, which can be used to fill countries data:
ad;Andorra, Principality of
ae;United Arab Emirates
af;Afghanistan, Islamic State of
ag;Antigua and Barbuda
You can find more sample CSV files in the wizard_files_directory/TDIPopulation/TDISOL/aix|lin|win/samples
directory, where the wizard_files_directory
is the location of the various Wizard files that you downloaded or received on disk, and aix|lin|win
is the AIX
®, or Microsoft
® version of the directory.
Parent topic: Populating the Profiles database
Understanding how the sync_all_dns process works
Configuring Tivoli Directory Integrator
Adding source data to the Profiles database
Manually populating the Profiles database
Using the Profiles population wizard
Using the CodesConnector
Configuring the Manager designation in user profiles
Tivoli Directory Integrator solution properties for Profiles
The tdisettings.properties file