nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Large Number of Different LDAP People Imports

dinger

Hello all,

Due to our AD structure we need to run a large number (say >20) of different people imports on the same server (whilst performing LDAP sync). I could create 20 different even triggers and jobs but this seems a bit clunky. Also, there is a problem running the imports at the same time (database transaction issues). It would be nice to group these jobs up with one trigger and then run them consecutively.

Is there a way to run these jobs in a more elegant way?

Cheers

Rob

Find more posts tagged with

Comments

andy

Hi

There is not other way at the moment.

What is the concurrency issue? Make sure you are not deleting all users in the import. Are you using a common home folder for users?

Andy

dinger

I've been following this up through support.

It would seem that the best way to do it is to write a new class that performs the functionality I want. Basically we want to be able to run lots of seperate people imports at the same time. Support suggested that I write a new class that runs a number of jobs sequentially which will be based on org.alfresco.repo.importer.ImporterJob but accepts a list of ImporterJobSPI objects.

Cheers

Rob

andy

Hi

What is the concurrency issue?

Is the same uid in more than one import?

Andy

dinger

If you try and do more than one people import at the same time you get transaction issues (hibernate exceptions).

If anyone is interested in the code I've created then I'd be more than happy to give it to them.

Rob

andy

Hi

Can you post the exception?

Andy

dinger

I can't replicate it… can I just confirm that multiple people imports should work if run at the same time?

Cheers

Rob

andy

Hi

They should work - unless they both update the same people. (Or they clean out existing people - which you should avoid anyway)

Andy

dinger

Great, that was probably why we were getting the error before.

I'm looking at the LDAPPersonExportSource and it looks like it would be quite easy to modify so it would take more than one search base (that is a list). Would this be the best place to do it?

Cheers

Rob

andy

Hi

That is the correct place.

Andy