How to switch LSF domain controller
Problem:
If your controller is failing and you need to move the LSF LDAP to another controller
Resolution:
Edit the ldapbind information in the SSOP service and reload it.
- Create a dump of the SSOP service:
- ssoconfig -c
- Option 5 Manage Lawson services
- Option 6 Export service and identity info
- Option 2 for not all services
- Enter SSOP in upper case
- Enter NONE in upper case
- Give a filename (it will write out the file to the directory you are in when you run the ssoconfig -c command.) Example: ssop_prod.xml
- Exit the ssoconfig menu.
- Make a copy of the .xml file that you just created. This is your backup of the SSOP service in its original state.
- Then edit the first .xml file and change the following lines:
<BATCH_LOAD FORMAT=”” OVERRIDE=”false”>
to
<BATCH_LOAD FORMAT=”” OVERRIDE=”true”>
and this line to the new machine name and port:
<PROVIDER>ldap://dc1.lawson.com:3268</PROVIDER>
to
<PROVIDER>ldap://dc2.lawson.com:3268</PROVIDER>
- Save the file.
- Do one of the following to load the modified SSOP service file:
ssoconfig -l ssoconfig_password filename.xml
Exit.
- A stop and start of the Lawson environment and WebSphere application server is required in order for this to take affect.
Leave a Reply
Want to join the discussion?Feel free to contribute!