Distinguished names | HCL Digital Experience
If you are using LDAP in your source environment, make sure that the wkplc.properties file is properly configured. You might have a configuration that is working, but it might not be supported after migration. Short distinguished names (DN) are not supported. Make sure that the properties files in your source environment are set with the fully qualified distinguished names.
- PortalAdminId
- This value is the user ID for the WebSphere® Portal administrator. The installation
program sets this value that is based on user input during installation.
The user ID cannot contain a space: for example, user ID.
The user ID cannot be longer than 200 characters.
(UNIX™ only) Some tasks might require you to enter the fully qualified user ID. If your fully qualified user ID contains a space; for example: cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software Group,dc=ibm,dc=com, then you must place the fully qualified user ID in the properties file or into a parent properties file instead of as a flag on the command line. To create a parent properties file called mysecurity.properties, enter the fully qualified user ID, and then run the following task: ./ConfigEngine.sh task_name -DparentProperties=/opt/mysecurity.properties.
(Windows™ only) Some tasks might require you to enter the fully qualified user ID. If your fully qualified user ID contains a space; for example: cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software Group,dc=ibm,dc=com, then you must place quotations around the fully qualified user ID before you run the task, for example: "cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software Group,dc=ibm,dc=com."