Map attributes - i5/OS
Flag attributes as unsupported or required and then map the required attributes between WebSphere Portal and the LDAP server.
To map attributes between WebSphere Portal and your user registry:
- To create...
WP_PROFILE/ConfigEngine/log/availableAttributes.html...run...
cd WP_PROFILE/ConfigEngine directory
ConfigEngine.sh wp-query-attribute-config -DWasPassword=wpsadminThis file lists the available attributes for Users (PersonAccount) and Groups parameters.
- Open the config trace file to review the following output for the PersonAccount and Group entity type:
The following attributes are defined in WebSphere Portal but not in the LDAP server
This list contains all attributes that are defined in WebSphere Portal but not available in the LDAP. Flag attributes that you do not plan to use in WebSphere Portal as unsupported. Map the attributes that you plan to use to the attributes that exist in the LDAP; also map attributes...
- uid
- cn
- firstName
- sn
- preferredLanguage
- ibm-primaryEmail attributes
The following attributes are flagged as required in the LDAP server but not in WebSphere Portal
This list contains all attributes that are defined as "MUST" in the LDAP server but not as required in WebSphere Portal. You should flag these attributes as required within WebSphere Portal.
The following attributes have a different type in WebSphere Portal and in the LDAP server
This list contains all attributes that WebSphere Portal might ignore because the data type within WebSphere Portal and within the LDAP server do not match.
Option | Description |
---|---|
Stand-alone | ConfigEngine.sh wp-update-standalone-ldap-attribute-config -DWasPassword=wpsadmin
... from the... WP_PROFILE/ConfigEngine ...directory |
Federated | ConfigEngine.sh wp-update-federated-ldap-attribute-config
-DWasPassword=wpsadmin
...from WP_PROFILE/ConfigEngine directory |
Option | Description |
---|---|
Stand-alone environment | cd WP_PROFILE/bin
./stopServer.sh server1 -username adminid -password passwd ./stopServer.sh WebSphere_Portal -username adminid -password passwd ./startServer.sh server1 ./startServer.sh WebSphere_Portal |
Clustered environment | cd dmgr_profile_root\bin
./stopManager.sh cd WP_PROFILE/bin ./stopNode.sh -username adminid -password passwd ./stopServer.sh server1 -username adminid -password passwd ./stopServer.sh WebSphere_Portal -username adminid -password passwd cd dmgr_profile_root\bin ./startManager.sh cd WP_PROFILE/bin ./startNode.sh ./startServer.sh server1 ./startServer.sh WebSphere_Portal |
Perform the following steps to flag an attribute as either unsupported or required for the entire WebSphere Portal environment instead of just for the specified LDAP:
...from WP_PROFILE/ConfigEngine.