In Interact, a database profile table exists per audience level for your interactive channel. This profile table contains a column that stores unique Interact IDs for customers.
You must import a copy of these Interact IDs into the LDAP directory that populates the portal user registry or into the portal Member Manager lookaside repository. Before you import a copy of this profile data, create a new attribute in the portal user profile that can contain the imported values to map the portal user to the Interact profile data.
For example, for an audience level that is set to the individual, you might see a column in your profile table labeled Indiv_ID. You must import a copy of the values of the Interact IDs listed in the Indiv_ID column into your LDAP directory or into the Member Manager lookaside repository. Before you import a copy of this profile data, create a new attribute to add to the portal user profile that can contain the Indiv_ID value that you imported from the Interact profile table for the user that is logged in to the site.
Import Interact IDs for WebSphere
Portal and extend the portal user profile.
- Import a copy of the values for the unique Interact ID into a repository that is used by your user registry to store data. You can store data in the LDAP directory of the user registry or into the Member Manager lookaside repository as appropriate.
- Before you import the Interact IDs from the Interact profile table, add an attribute to your user registry to extend the portal user profile. Select one of the following options for updating your user registry.
Parent topic: IBM Interact Spot
- If you plan to import the Interact IDs into the LDAP directory, see your user registry documentation for instructions on how to create a new attribute for the Interact IDs.
- If you plan to import the Interact IDs into the Member Manager lookaside repository, you can create the user attribute for the copy of the Interact IDs without touching your backend user registry. This process is referred to as a Property Extension (formerly known as the lookaside database). You can use the Property Extension when your LDAP is read-only but you have a requirement for an extra attribute, such as the Interact ID. See the WebSphere Portal documentation for instructions on configuring a property extension database.