Disabling and Enabling the Scheduler on a Node in Cluster Setup

Disabling and enabling the scheduler on a node in cluster setup involves the following:

• Adding the Server-Level Property
• Restarting the Managed Server from the Node Manger

Adding the Server-Level Property

To add the server-level property to disable/enable the scheduler on a node in cluster setup:

1. Log in to the WebLogic Administrative Console.
2. In left pane, click Environment, Servers.
3. Click the name of the managed server in which you want to add the scheduler.disabled=true property.
4. Click Lock and Edit in the left tab.
5. Click Configuration, Server start tab in the right pane.
6. In the Argument Text box, add scheduler.disabled=true, and save.
7. Click Activate Change in the left pane.
8. To ensure that this property is picked, restart the managed server via the node manager. Restarting from script does not work.

Restarting the Managed Server from the Node Manger

To restart the managed server from the node manager:

1. Start the Admin Sever by running the following script:

   MW_HOME/user_projects/domains/base_domain/startWebLogic.sh
   

2. Start the Node Manager by running the following script:

   MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh
   

3. Login to the WebLogic Administrative Console.
4. In left pane, click Environment, Servers.
5. Click the Control tab in the right pane.
6. Select the checkbox against the managed server in which the property has been added, and then click the start button.

After restarting the managed server, scheduler will not start because the value of the scheduler.disabled property is set to true. To verify this, navigate to the following URL and log in:

http://HOST:PORT/SchedulerService-web

Controlling Scheduler Start or Stop in a Clustered Environment

The scheduler.disabled system property is required if you want to control scheduler start or stop on a clustered setup. The scheduler.disabled system property must be set to true if you do not want to start the scheduler service on that node of the cluster.

This section contains the following topics:

• Adding the Server Side Property for Oracle Identity Manager
• Restarting Oracle Identity Manager Managed Servers from the Node Manager
• Modifying the Server Side Property for Oracle Identity Manager

Adding the Server Side Property for Oracle Identity Manager

To add the scheduler.disabled server-level property:

1. Log in to the WebLogic Administrative Console.
2. On the left panel, select Environment, Servers.
3. Click the name of the managed server where you want to add the scheduler.disabled=false property.
4. Select Lock and Edit.
5. Select Configuration, Server Start.
6. In the Arguments box, add the scheduler.disabled=false property, and click Save.
7. Click Activate Change.

Restart the managed server using node manager so that the newly added property is picked up. Restarting from the Command-Line Interface does not work.

Restarting Oracle Identity Manager Managed Servers from the Node Manager

To restart Oracle Identity Manager Managed Servers from the Node Manager:

1. Start the Administration server. To do so:
   1. From your current working directory, go to the MW_HOME/user_projects/domains/base_domain/ directory.
   2. Run the following command:
      For UNIX:

      startWebLogic.sh
      

      For Windows:

      startWebLogic.cmd
      

2. Start the Node Manager. To do so:
   1. From your current working directory, go to the MW_HOME/wlserver_10.3/server/bin/ directory.
   2. Run the following command:
      For UNIX:

      startNodeManager.sh
      

      For Windows:

      startNodeManager.cmd
      

3. Log in to the WebLogic Administrative Console.
4. On the left panel, select Environment, Servers.
5. Select Control from the right panel.
6. Select the option where the property is added, and click Start.

Modifying the Server Side Property for Oracle Identity Manager

To modify the scheduler.disabled system property:

1. Log in to the WebLogic Administrative Console by using the WebLogic administrator credentials.
2. Under Domain Structure, select Environment, Servers. The Summary of Servers page is displayed.
3. Click the Oracle Identity Manager server name, for example, oim_server1. The settings for oim_server1 is displayed.
4. Click Configuration, Server Start.
5. In the Arguments box, change the existing property scheduler.disabled = false/true.
6. Click Save.
7. Click Activate Changes.
8. Restart the Oracle Identity Manager Managed Server.

Note : Copied from Oracle Docs but a good one to share even copied.