ShowTable of Contents
The article is intended for WebSphere Portal developers and members of Portal Quality Assurance.
To get the most from this article, you should have a basic understanding of Windows Active Directory and WebSphere Portal, along with Portal administration.
The attribute to be mapped (TempPlantCode in this case) should be added to Active Directory, and you need to confirm the same by logging in and checking at the Windows Active Directory.
Here are the steps to prepare the WebSphere Portal machine:
- Log in to the Portal machine and locate the wkplc.properties file under the \IBM\WebSphere\wp_profile\ConfigEngine\properties path.
- Edit the wkplc.properties file.
- Search for the string, la.providerURL, and set the values shown below:
la.propertyName = TempPlantCode
la.entityTypes = PersonAccount
la.dataType = String
la.multiValued = false
Figure 1 shows an example.
Figure 1. Example of the edited string values
Executing the mapping
To do this, follow these steps:
- Navigate to the path, \IBM\WebSphere\wp_profile\ConfigEngine, on the command prompt and run the following command:
ConfigEngine.bat wp-la-install-ear -DWasPassword=p@ssw0rd
The command is executed successfully if you see the BUILD SUCCESSFUL and Return Value: 0 messages on the screen (see figure 2).
Figure 2. Command executed successfully
2. Run the ldap update command:
ConfigEngine.bat wp-update-federated-ldap-attribute-config -DWasPassword=p@ssw0rd
3. Log in to the WebSphere Application Server (WAS) admin console of Portal and navigate to WebSphere Portal (see figure 3).
Figure 3. WebSphere Portal on admin console
4. Verify the BOOTSTRAP_ADDRESS as shown in figure 4.
Figure 4. BOOTSTRAP_ADDRESS
5. Edit the wkplc.properties file, replacing the port number for la.providerURL with the port number of BOOTSTRAP_ADDRESS, for example:
Save the file.
6. Navigate back to the command prompt path \IBM\WebSphere\wp_profile\ConfigEngine and run the following command to add the property for the newly added attribute:
ConfigEngine.bat wp-add-property -DWasPassword=p@ssw0rd
7. Verify that you get BUILD SUCCESSFUL
and Return Value: 0
after the command is run to confirm successful execution (see figure 5).
Figure 5. Command executed successfully
8. Once the above changes are made, restart the WebSphere Portal server, log in, and navigate to Users and Groups. Click New User, and click Configure, to verify that the newly added TempPlantCode attribute appears as a field (see figure 6).
Figure 6. TempPlantCode attribute listed
You should now be familiar with the steps to map a newly added attribute in the Windows Active directory to WebSphere Portal. If there are any changes at the Active Directory end, the same steps must be followed for the changes to be reflected at the Portal end. It's assumed that the changes at the AD end are done before executing the steps and, since adding a new attribute at the AD end involves schema changes, you must be diligent while making these changes.
developerWorks WebSphere Portal product page:
WebSphere Portal Forum:
About the author
Amrut Kulkarni has more than five years of experience in software product testing, working on domains like product portfolio management and software configuration management. He currently serves on the Industry Solutions team, based at the India Software Labs in Bangalore. His areas of interest include Exploratory Testing, Portfolio Management, and Business Intelligence. He can be reached at email@example.com