The first thing we’re going to want to do once the Connections applications successfully install is test them by logging in as a regular user. To do that the user must have a profile in the PEOPLEDB or Connections will throw an error and the easiest way to ensure that exists is to run the Population Wizard.
The Population Wizard is a simple tool that asks a series of questions such as where is your LDAP directory, where are your DB2 databases, and where is TDI and uses those answers to run a one off script using TDI to import all users into Connections, creating them a profile along the way. It’s designed to work in only one direction (you can pull information from LDAP to databases only, not the other way around).
For a test environment or a very small manually-maintained environment you could run the PopulationWizard to update the databases whenever you want but for production it’s not really workable. However, this is just to ensure we have some data in place that we can use for testing. We will work with the custom TDI scripts later to fine tune what we want.
To run the population wizard look in the “Wizards” directory from the ConnectionsWizards download. The file will be called populationWizard.sh (or populationWizard.bat).
The JDBC drive path must contain the drivers for your database platform. If you aren’t running TDI on the same server as your databases you will need to copy the drivers from the database server to the TDI server to reference them here.
The User ID is the account granted full rights to the PEOPLEDB database. This can often be a custom account and not (as in this case) the instance owner.
Here we tell the wizard where our LDAP server is and how to connect to it. If you are using a secure port such as 636 make sure you check the box for “Use SSL communication”
These are the bind credentials to login and query LDAP. They aren’t stored anywhere in this activity or used for any purpose other than running this one-off wizard so any credentials would do.
This shows the sample mapping of LDAP attributes to database fields. For example “mail” in LDAP will map to the field “Office Email”. On this screen we can choose what attributes to map where and even if we want to map attributes at all. Anything we don’t map won’t be populated with data and will appear as empty in Connections.
Once the populationWizard completes it should report that it imported your users. To do this it wrote instructions to properties files and ran script files stored in the location:
The files it wrote our instructions to are:
The script files it ran were:
The activity is recorded in /Wizards/TDIPopulation/linux/TDI/Logs.
We’ll come back to this later when we start customising our syncing activity.