cancel
Showing results for 
Search instead for 
Did you mean: 

AS Java Update Job suffering from bad performance

Former Member
0 Kudos

My AS Java Update Job is suffering from bad performance and ending with timeout. I was thinking as the users are in LDAP and this SPML request must do a join between Portal roles in UME and users in LDAP as it writes members to different table in destination.

How could I alter the query/source tab so that it only reads information from UME and skips the existing memberships defined in AS Java? Just removing member and distinguishedname attributes? If so should the STARTINGPOINT be altered accordingly if SAPprincipals refers to users?

ATTRIBUTES	displayname,uniquename,objectclass,member,datasource,distinguishedname
STARTINGPOINT	SAPprincipals
FILTER	(&(objectclass=sapgroup)(uniquename=*)(datasource=PRIVATE_DATASOURCE))
SERVLET_URL	%$rep.HTTP_PROTOCOL%://%$rep.APPLICATION_HOST%:%$rep.HTTP_PORT%/spml/provisioning
HTTP_AUTH_USER	%$rep.HTTP_AUTH_USER%
HTTP_AUTH_PWD	%$rep.HTTP_AUTH_PWD%

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Is the timeout caused by the AS Java system or by IDM? If it is the latter, then you could just check 'bootstrap job' in the options of the job.

Edited by: Holger Flocken on May 6, 2010 2:47 PM