ISS - LSF S3 10

Is it required to use ISS to federate my Landmark environment to my LSF environment when going to LSF S3 10? We're on Landmark version 9.4.2.5 now and I'm trying to find out of Landmark has to be upgraded to 10 before going to LSF S3 10.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

bob-heitzman

We were on a call with Mark Deutsch a couple weeks ago and he said "You don't want to go through federation to LSF, let ISS synchronize that". So, I take that statement as his way of saying your best approach would be to use ISS to make the task easier but its not mandatory.

unknown

Good to know. Thanks!

robert-canham

We are upgrading now and chose not to do any federation. We went up on IPA 10 last year prior to our upgrade. When we got ready to do the S3 side, we heard lots of horror stories about ISS not working well and being very difficult to get configured. We decided to wait to use it until after Lawson had worked more of the bugs out. We don't have any inbasket users yet though so there was minimal impact to us.

unknown

I heard from a technical consultant that it took him 11 times to get ISS to synchronize successfully. Thanks!

unknown

ISS is a great utility for federation and has come a long way in the past 9 months. Yes, you may have to run the sync utility a few times to get everything synced properly. But what it is doing is cleaning up your LDAP. You should be comfortable using a tool like Apache Directory Studio to clean up LDAP records as errors are flagged. Depending on how many users you have in your LDAP, it will take some time to run through the routines. The last version that I downloaded (early March) is what I used when we went live on LSF10. During part of the migration/upgrade, I re-ran the sync utility (had run it last fall when we upgraded to IPA) and it was fairly clean. It even bypassed errors that I know it would have blown up on in the past.

There may be some cleanup required after the fact, but we've been handling them on a user-by-user basis. About 8,000 employees here, all with RM ID's that needed to be synced to Landmark.

unknown

Thanks! My nightmare is it running fine in test and then in production it crashing. We have 25,000+ employees defined as their employee ID for ESS but haven't been provisioning them out of RM. Are you on ADLS or TDS?

unknown

TDS

unknown

We are currently syncing (in development) 43,000 users. When we finish rolling out ESS we will have over 250,000 users. The ISS tool is getting much better, and with multi-threading support it is much faster.

We have a security automation system that updates users after PA100 runs each night. With a new feature of ESP 9.0.1.13 you are able to provide an xml file of just the users that you want to be synced (those that changed during user automation) and call ssoconfig from a scheduler to get ISS to sync them to Landmark. This greatly reduces the time a sync takes because it only compares those actors in your list.

While there is still a good bit of work to do, ISS is really shaping up into a product we can trust.

unknown

Thanks for the info! So glad to hear about the xml file feature. Good luck on rolling out the ESS users. Do you mind letting me know how it went after you do?
steven.nguyen@sdhc.k12.fl.us

Copyright © 2025 Infor. All rights reserved.