This content has been marked as final. Show 5 replies
Never mind, found the answer
We can stop it from http://OIM_HOST:OIM_PORT/SchedulerService-web/status
In older version, it was a bug and issue is resolved if you are on latest bundle patch.
If it is R2:
See Admin Guide:
Section: Configuring the oim-config.xml File
instanceID Enter a unique string value in this element. This value
represents a string that uniquely identifies an Oracle Identity
Manager scheduler instance.
In a clustered environment, each node of the cluster
must have a unique InstanceId. This can be achieved by
entering a value of AUTO in the instanceId element.
I thought I'll stop the scheduler on servers where I don't need it by following the URL, http://OIM_HOST:OIM_PORT/SchedulerService-web/status
Is that not the correct approach ?
Regarding instanceID under scheduler configuration on oim-config.xml, I was not able to understand this concept, this file is on MDS so whatever value I set here is common to all servers then how do I restrict only certain servers to run scheduler? may be i"m not following it right, if the instanceID is pre-assigned to each node, where can i see it?
It should work but whenever you restart the server then it will start the Schedulers again.
Oh okay. Can you share some doc ref to instanceID and how it works?
I found this ref but its doesn't have much info, http://docs.oracle.com/cd/E27559_01/admin.1112/e27149/scheduler.htm#r6c1-t5