The ConfigEngine.sh script is used to add, remove and validate entries in the Portal configuration engine. Refer to IBM Portal - Configuring wkplc.properties for the steps on how to configure the workplace properties file (wkplc.properties) so that ConfigEngine.sh can make a connection to Portal.
The wp-add-property option is used to add a property, such as an LDAP attribute. The ConfigEngine.sh script will get the new property to add from the /opt/WebSphere/AppServer/profiles/<your profile>/ConfigEngine/properties/wkplc.properties file. In this example, the LDAP fullName attribute will be added.
la.propertyName=fullName la.entityTypes=PersonAccount la.dataType=String la.multiValued=false
You would then invoke ConfigEngine.sh like this.
If the update is successful, BUILD SUCCESSFUL should be included at the end of the output.
cleanup-config: [echo] executing post-configuration tasks BUILD SUCCESSFUL update-registry-sync-property: [echo] updated RegistrySynchronized in file wkplc.properties with value: true
If the update is unsuccessful, BUILD FAILED should be included at the end of the output. In this scenario, review the failureyyyy-mm-dd-hh.mm.ss.log to get an idea behind why the update failed. After resolving the issue identified in failureyyyy-mm-dd-hh.mm.ss.log, run the wp-add-property command again until BUILD SUCCESSFUL is returned.
cleanup-config: [echo] executing post-configuration tasks BUILD FAILED print-final-message: isIseries currently set to: null Creating failure log in directory: /opt/WebSphere/AppServer/profiles/<your profile>/ConfigEngine/log traceFile created /opt/WebSphere/AppServer/profiles/<your profile>/ConfigEngine/log/failureyyyy-mm-dd-hh.mm.ss.log basepath = /opt/WebSphere/ConfigEngine
Restart the Portal application servers for this change to take effect.
Then, the ConfigEngine.sh wp-validate-federated-ldap-attribute-config command can be used to ensure the attribute was added to the Portal configuration engine.