on 03-21-2014 8:26 AM
Hi,
we have following Scenario: We have a user interface in .net which inserts Values in custom tables in the idm database. When there is a new entry a job in IDM should start and work with the new Data. I have tried this on dev:
update [dbo].[mc_jobs]
SET[ScheduledTime] = getdate()
jobid = 104066
and it worked fine. Is it OK to do this, or could there be any negative effects?
Hi Andreas,
In general, DO NOT update database tables directly, unless this is explicitly stated in documentation.
Soner or later, you will run into problems doing this.
For your case, you should instead call the stored procedure mc_job_run_now.
Best regards
John Erik Setsaas
Senior Development Architect SAP NW IdM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andreas,
I have done the similar way in my IDM l for one of the scenarios. I was not sure whether or not it is ok to do so or if it has any other effects. All I wanted then was to make it work
But I have not faced any issue till now with this. And I am having this in my production quite from a long time.
Have to see what our mates comment about this.
~ Krishna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Andreas,
Is your intention that your .NET code should also trigger the job?
Have you tried using an Event Agent?
Finally is there a TRUE need to have the job run immediately or can you schedule the job just to run every few minutes?
In my experience, even though there is a requirement for "realtime processing" it doesn't usually really need to happen that way since background processing and sync takes time anyway.
Just a thought....
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
yes there is the need to do immediatly, in this case. It's a firefighter process (we add the firefighter priv with a to identity store pass, so provisiong runs parallel, but we also have a next pass in the job which adds immediatly the firefighter priv in the backendsystem). The implementation only with provsiong is sometimes too slow for this use case(when the provisiong queue is too loaded).
BR,
Andreas
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.