federating LSF and Landmark

We have Landmark and IPA running on windows server: Landmark 10.1.1.25
We have LSF running on AIX server LSF 10.0.7 and Apps 10.0.6
We are using ISS 11.0.0.261
All are running great. All the smoke tests and validation URLs work
This is our last phase of the Lawson 10 Upgrade and we are now trying to federate Landmark with LSF
First question. When they say backup before federating are they referring to the .sso and authen files on each respective system? Or is there more?
Second question. Do we need to do the LDAP bind on the Landmark/IPA server? The assumption is that was for a standalone system. Since we will be federating with LSF using SSOP as the primary authentication service then that is not needed? Note we did the ldapbind with LSF and it's working fine. However, the build of landmark had copies of the .sso, authen.dat, sevice.xml, actors.xml, and services.xml prior the ldapbind performed on LSF. Will that be an issue? The assumption here is once we synch with LSF SSOP as the primary that this would all be corrected and that it would use the ldapbind from LSF.
Third question. Just want to confirm we don't need to load DSP on the Landmark/IPA server.
Fourth question. One set of instructions tells us to use the Landmark lawsec.jar and another set tells us you can use the LSF lawsec.jar. It looks like we would be ok using the LSF lawsec.jar
Fifth question. It tells us to edit the lsservice.properties file and add isprimary=false and server.authservicename=SSOPV2 -- It we are using ISS and we are using SSOP as primary is this necessary?
Any help is greatly appreciated.

Find more posts tagged with

Comments

Legacy Contributor

1. When they say backup I would think they mean your landmark and LSF server because the install and configuration are updated.
2. No LDAP Bind on Landmark.
3.DSP is only on LSF.
4. Everything that needs to be deployed to the LMK web servers is deployed through enterpriseapp so you do not have to deploy anything manually like LSF.
5. Attached is my lsservoce.properties file from LSF and LMK

tcyprys

1. For backups, make sure and backup LSF GEN, LMK GEN, LSF LDAP $LAWDIR/system on LSF and $LASYSDIR on LMK. These are critical. Do not start the federation without them.

2. Before the federation you want both LSF and LMK bound or both systems not bound. If you ultimately want to be bound, I would recommend binding them before you start the federation.

3. The DSP install (keep in mind you are only talking ISS/DSS when it comes to the federation process) only happens on the LSF server

4. Not quite sure what you mean there. Both lawsec apps will already be deployed in WAS on both systems

5. This looks like an old "coupling" reference. The federation process will make changes to lsservice.properties. Other than tuning, you shouldn't need to make any manual changes to this file.

Another item to consider...... Make sure you enable verbose security logging in LSF before you start the federation.

Copyright © 2025 Infor. All rights reserved.