Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
| Library | Service | Index

# 9
Managing Processes

The eMail Server system consists of several types of processes that run in the background to perform functions such as delivering e-mail and scheduling messages.

Managing the processes includes such common tasks as starting and stopping processes and setting parameter values.

Managing processes includes the following tasks discussed in this chapter:

- Displaying the Guardian Process Status

- Starting the Guardian Process

- Registering a New Process

- Starting a Registered Process

- Displaying Process Status Information

- Displaying Database Shadow Processes

- Removing Database Shadow Processes

- Refreshing a Process

- Removing a Registered Process

- Shutting Down a Registered Process

- Shutting Down the Guardian Process

- Displaying Process Parameters

- Modifying a Default Process Parameter

- Setting a Parameter for a Registered Process

- Reverting a Registered Parameter to the Default Value

- Modifying Process Properties

- Creating a Time Slice in a Process Default Schedule

- Modifying a Time Slice in a Process Default Schedule

- Removing a Time Slice from a Process Default Schedule

- Overriding a Default Time Slice for a Process Instance Schedule

- Modifying a Time Slice for a Process Instance Schedule

- Reverting a Process Instance Time Slice to the Default Value

  See Also: Chapter 11, "Process Parameter Reference" for a discussion of the eMail Server processes and how they work

## Displaying the Guardian Process Status

Before you can view or control the guardian process using the Administration Tool, you must tell the tool where the guardian is by specifying the guardian service name. The guardian service name can be found in the tnsnames.ora file on the client where the Administration Tool is installed.

See Also: Oracle eMail Server Installation Guide for more information about this file

### Steps for Displaying the Guardian Process Status

This task can only be performed through the Administration Tool GUI.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Guardians > guardian_instance.

3. In the right pane, enter the guardian service name in the Service text box.

4. Click Apply.

The guardian process status appears in the right pane. If the guardian is running, then it appears in blue in the navigation tree. If it is not running, then it appears in black.

## Starting the Guardian Process

You must start the guardian process before you can start the rest of the eMail Server processes, including the gateway processes, protocol server processes, and LDAP server processes.

### Prerequisites to Starting the Guardian Process

- Before starting the guardian using the Administration Tool, you must specify the guardian service name to tell the tool where to find the guardian process. Refer to "Displaying the Guardian Process Status" for instructions.

- Make sure the guardian process is not already running. In the Administration Tool, a running process appears in blue in the navigation tree. If it is not running, then it appears in black.

  Caution: If you stop the guardian process, then it will automatically stop all processes under its control that are currently running. When you start it back up, it will attempt to start all the processes that were running before it stopped. If you do not want a process to be started again when you start the guardian process, then you should stop that process before stopping the guardian process. Refer to "Shutting Down a Registered Process" for instructions.

### Steps for Starting the Guardian Process

This task can be performed through either the Administration Tool GUI, or through a standard shell tool.

##### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Guardians > guardian_instance.

3. In the toolbar, click (Startup).

##### In a Shell Tool

1. Open a shell tool on the machine or node containing the guardian process that you want to start.

2. Enter the following command at the shell prompt:

       $ ofcguard start connect=<connect_string> instance=<instance_number>

   The connect string and instance number are optional. If you are starting the guardian process on a separate protocol server tier, then you must specify the connect string for the node where the protocol server processes will be administered and the Guardian ID for that guardian.

   See Also: "Logging on to the Administration Tool and OOMGR" for more information about the connect string

## Registering a New Process

When a node is created, the eMail Server installation program registers one instance of each process type. You can register additional instances of some process types, such as postman or replicator processes, to help a node run more efficiently. For example, if your users send many messages around noon each day, then you can create additional postman processes that run during that time to handle the extra message traffic. After you register a process, you must start it before it can perform the desired tasks.

### Steps for Registering a New Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances.

3. In the toolbar, click (Register).

4. Complete the Register an Instance Process dialog box.

   See Also: "Common Process Parameters" for more information about the parameters in this dialog box

5. Click OK.

##### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>register process server=<process_name>
       2>instance=<instance_number>
       3>DefaultStartup=[Enabled | Disable]

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Starting a Registered Process

Starting or restarting a node does not start the processes. You must start the processes explicitly.

### Prerequisites to Starting a Registered Process

- Start the guardian process if it is not already started. Refer to "Starting the Guardian Process" for instructions.

- Make sure the process is not already running. In the Administration Tool, a running process appears in blue in the navigation tree. If it is not running, then it appears in black.

  In OOMGR, display the process status. Refer to "Displaying Process Status Information" for instructions.

### Steps for Staring a Registered Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. To perform this task: | Follow these steps:
   --- | ---
   2. Start one process instance | In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance. In the toolbar, click (Startup).
   Start all registered processes on a node | In the menu, select Message System > Start All Processes...

   Perform one of the following actions:

#### In OOMGR

1. Start OOMGR.

2. Enter one of the following commands at the OOMGR prompt:

   To perform this task: | Use this command:
   --- | ---
   Start one process instance |
       IOFCMGR>startup server=<process_name>
       2>instance=<instance_number>;
   ##### Example: To start a single postman process, you would use this command:
       IOFCMGR>startup server=postman
       2>instance=1;
   Start all registered processes on a node |
       IOFCMGR>startup all;

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Displaying Process Status Information

You can display the following status information for registered processes:

- Process name and instance number

- Database session ID

- Operating system process ID

- Last wakeup time

### Steps for Displaying Process Status Information

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes.

3. In the right pane, select the Running Processes tab. A running process appears in blue. If it is not running, then it appears in black.

##### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>display processes;

## Displaying Database Shadow Processes

You can list all database shadow processes that are running on the node. Shadow processes are subprocess created by the database. If a client does not exit the system properly, then some database shadow process may be left running on the system and should be removed.

### Steps for Displaying Database Shadow Processes

This task can only be performed through the OOMGR command-line interface.

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>display shadows user=<username>;

   See Also: "Parameters for Displaying Database Shadow Processes" for more information about the values to enter

### Parameters for Displaying Database Shadow Processes

Parameter | Description
--- | ---
`user` | The username associated with the connection that you think may have unneeded shadow processes.

## Removing Database Shadow Processes

You can remove all database shadow processes that are not associated with a messaging client because shadow processes often remain if the client does not exit the system properly.

### Steps for Removing Database Shadow Processes

This task can only be performed through the OOMGR command-line interface.

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>cleanup shadows;

## Refreshing a Process

You should refresh a process if you change a parameter value while the process is running. Refreshing a process causes it to read its parameters again and then to restart using the new parameters.

### Prerequisites to Refreshing a Process

Make sure the process is running. In the Administration Tool, a running process appears in blue in the navigation tree. If it is not running, then it appears in black.

### Steps for Refreshing a Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. Perform one of the following actions:

   To perform this task: | Follow these steps:
   --- | ---
   2. Refresh one process | In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance. In the toolbar, click (Restart).
   Refresh all processes on a node | In the menu, select Message System > Re-Activate All Processes...

#### In OOMGR

1. Start OOMGR.

2. Enter one of the following commands at the OOMGR prompt:

   To perform this task: | Use this command:
   --- | ---
   Refresh one process |
       IOFCMGR>refresh server=<process_name>
       2>instance=<instance_number>;
   Refresh all processes on a node |
       IOFCMGR>refresh all;

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Removing a Registered Process

You can remove a process instance if you no longer use the process. Removing a process removes the process parameters and all other related information from the system.

### Steps for Removing a Registered Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance.

3. In the toolbar, click (Deregister).

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>deregister process server=<process_name> instance=<instance_number>;

   Do not deregister a process with `instance=0`. This is the set of default parameters for the process type.

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Shutting Down a Registered Process

You can shut down either a single process, or all processes on a node. When you shut down all processes on a node, you:

- Stop all active processes, except the guardian

- Prevent any inactive processes from starting until you restart that process, or all processes

### Prerequisites to Shutting Down a Registered Process

Make sure the process is running. In the Administration Tool, a running process appears in blue in the navigation tree. If it is not running, then it appears in black.

### Steps for Shuttung Down a Registered Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. Perform one of the following actions:

   To perform this task: | Follow these steps:
   --- | ---
   2. Shut down one process | In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance. In the toolbar, click (Shutdown).
   Shut down all eMail Server processes on a node | In the menu, select Message System > Stop All Processes...

##### In OOMGR

1. Start OOMGR.

2. Enter one of the following commands at the OOMGR prompt:

   To perform this task: | Use this command:
   --- | ---
   Shut down one process |
       IOFCMGR>shutdown server=<process_name>
       instance=<instance_number>;
   Shut down all eMail Server processes on a node |
       IOFCMGR>shutdown all;

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Shutting Down the Guardian Process

You can shut down the guardian process, if necessary. Shutting down the guardian process shuts down all running process under the guardian's control.

### Prerequisites to Shutting Down the Guardian Process

Before shutting down the guardian process using the Administration Tool, make sure the process is running. In the Administration Tool, a running process appears in blue in the navigation tree. If it is not running, then it appears in black.

If you cannot see the guardian process in the navigation tree, then refer to "Displaying the Guardian Process Status".

Caution: If you stop the guardian process, then it will automatically stop all processes under its control that are currently running. When you start it backup, it will attempt to start all the processes that were running before it stopped. If you do not want a process to be started again when you start the guardian process, then you should stop that process before stopping the guardian process. Refer to "Shutting Down a Registered Process" for instructions.

### Steps for Shutting Down a Guardian Process

This task can be performed through either the Administration Tool GUI, or a standard shell tool.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Guardians > guardian_instance.

3. In the toolbar, click (Shutdown).

#### In a Shell Tool

1. Open a shell tool on the machine or node containing the guardian process that you want to start.

2. Enter the following command at the shell prompt:

       $ ofcguard stop connect=<connect_string> instance=<instance_number>

   The connect string and instance number are optional. If you are stopping the guardian process on a separate protocol server tier, then you must specify the connect string for the node where the protocol server processes will be administered and the Guardian ID for that guardian.

   See Also: "Logging on to the Administration Tool and OOMGR" for more information about the connect string

## Displaying Process Parameters

You can display the parameters and their current settings (both default and specific for each process registered on this node) for all processes or a particular type of process.

### Steps for Displaying Process Parameters

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance.

3. In the right pane, select the Parameters tab.

#### In OOMGR

1. Start OOMGR.

2. Enter one of the following commands at the OOMGR prompt:

   To perform this task: | Use this command:
   --- | ---
   Display parameters for all processes |
       IOFCMGR>show process all;
   Display parameters for a specific type of process |
       IOFCMGR>show process server=<process_
       name>;
   Display parameters for a specific registered process |
       IOFCMGR>show process server=<process_
       name> instance=<instance_number>;

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Modifying a Default Process Parameter

You can modify the default parameters that are used when you register a new process. The instance number for default processes is always 0.

### Steps for Modifying a Default Process Parameter

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Defaults > process_name > Parameters > parameter_name.

3. In the right pane, enter the new parameter value in the Value text box.

4. Click Apply.

   See Also: Chapter 11, "Process Parameter Reference", for more information about the parameters in this dialog box

5. Refresh all the registered processes that use the default setting that you modified. Refer to "Refreshing a Process" for instructions.

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>modify paramvalue server=<process_name> instance=0
       2>parameter=<parameter_name>
       3>to value=<new_value>;

   See Also: Chapter 11, "Process Parameter Reference", for more information about the parameters available with this command

3. Refresh all the registered processes that use the default setting that you modified. Refer to "Refreshing a Process" for instructions.

## Setting a Parameter for a Registered Process

You can set a parameter for a specific registered process when the default value is not appropriate. The first time you set a parameter, you have to register the parameter value. If you want to change the value again later, then you can use the command to modify a registered parameter value.

### Steps for Setting a Parameter for a Registered Process

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance > Parameters > parameter_name.

3. Perform one of the following actions:

   To perform this task: | Follow these steps:
   --- | ---
   3. Set a parameter value for the first time, making it independent of the default values for that process type. | In the toolbar, click (Create). In the dialog box, enter the new parameter value in the Value text box. Click OK.
   Change a parameter value that has already been set once using the register command. | In the right pane, enter the new parameter value in the Value text box. Click Apply.

   See Also: Chapter 11, "Process Parameter Reference", for more information about the parameters in this dialog box

##### In OOMGR

1. Start OOMGR.

2. Enter one of the following commands at the OOMGR prompt:

   To do this: | Enter this command:
   --- | ---
   Set a parameter value for the first time, making it independent of the default values for that process type. |
       IOFCMGR>register paramvalue server=<process_
       name>
       2>instance=<instance_number>
       3>parameter=<parameter_name>
       4>value=<new_value>;
   Change a parameter value that has already been set once using the register command. |
       IOFCMGR>modify process server=<process_name>
       2>instance=<instance_number>
       3>parameter=<parameter_name>
       4>to value=<new_value>;

   See Also: Chapter 11, "Process Parameter Reference", for more information about the parameters available with this command

## Reverting a Registered Parameter to the Default Value

You can remove parameter values for registered processes. Removing the registered parameter values for a process reverts that process to the default parameters.

### Steps for Reverting a Registered Parameter to the Default Value

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance > Parameters > parameter_name.

3. In the toolbar, click (Remove).

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>deregister paramvalue server=<process_name>
       2>instance=<instance_number>
       3>parameter=<parameter_name>;

   You cannot revert instance 0 of any process to the default parameters because this instance contains the default process settings.

   See Also: Chapter 11, "Process Parameter Reference", for more information about the parameters available with this command

## Modifying Process Properties

You can modify some of the properties that describe processes, including the `execArguments`, `guardianID`, and `defaultStartUp` properties.

See Also: "Common Process Parameters" for more information about these properties and why you might want to change them

### Steps for Modifying Process Properties

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance.

3. In the right pane, select the Properties tab.

4. In the Properties tab, enter the new information in the text box for the property that you want to change.

5. Click Apply.

   See Also: "Common Process Parameters" for more information about the parameters in this dialog box

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>modify paramvalue server=<process_name>
       2>instance=<instance_number>
       3><property_name>=<value>;

   See Also: "Common Process Parameters" for more information about the parameters available with this command

## Creating a Time Slice in a Process Default Schedule

You can add a time slice (also called a time detail record) to a default process schedule to indicate a period of time during which the process is either active or passive. When you register a new process instance, it automatically inherits the default process schedule, including all the default time slices.

### Steps for Changing a Time Slice in a Process Default Schedule

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Creating a Time Slice in a Process Default Schedule" for more information about performing this task

#### In the Administration Tool GUI

1. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Defaults > process_default > Schedules.

2. In the toolbar, click (Create).

3. Complete the Register Time dialog box.

   See Also: "Schedule Parameters" for more information about the parameters in this dialog box

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>register paramtime server=<process_name>
       2>instance=0
       3>starttime=<integer between 0 and 23>
       4>duration=<whole number of hours>
       5>state=[A | P]
       6>sleeptime=<number of minutes>;

   See Also: "Schedule Parameters" for more information about the parameters available with this command

### Guidelines for Creating a Time Slice in a Process Default Schedule

- You cannot create more than one time slice with the same start time. Instead, change the duration of the existing time slice.

- The time slices in a process default schedule must always add up to at least a full 24-hour period.

- In the Administration Tool, you cannot remove a time slice if it leaves the schedule with less than 24 hours. Therefore, you must first add one or more time slices that overlap the existing time slices. Then, you can remove the time slices you no longer need.

  For example, if you have one time slice that starts at 0 (midnight) and runs for 24 hours, and you want to change it to two time slices that start at 0 (midnight) and 12 (noon) and run for 12 hours each, then use the following procedure:

  - Create a new time slice that starts at 12 (noon) and runs for 12 hours. You now have two overlapping time slices adding up to 36 total hours (the original 24-hour slice, plus the new 12-hour slice).

  - Change the running time of the time slice that starts at 0 (midnight) from 24 hours to 12 hours. You now have two time slices adding up to 24 total hours (the 12-hour slice created to run from noon until midnight, plus the 12-hour slice modified to run from only midnight until noon).

  When finished, the sum of all the time slices should not exceed 24 hours. You should also make sure that your final time slices do not overlap.

## Modifying a Time Slice in a Process Default Schedule

You can change a time slice (also called a time detail record) in a default process schedule to modify the period of time during which the process is either active of passive. When you register a new process instance, it automatically inherits the default process schedule, including all the default time slices.

### Steps for Modifying a Time Slice in a Process Default Schedule

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Modifying a Time Slice in a Process Default Schedule" for more information about performing this task

#### In the Administration Tool GUI

1. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Defaults > process_default > Schedules > time_slice.

2. In the right pane, enter the new information in the appropriate text box.

   See Also: "Schedule Parameters" for more information about the parameters in this dialog box

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>modify paramtime server=<process_name>
       2>instance=0 starttime=<integer>
       3>to sleeptime=<minutes>;

   See Also: "Schedule Parameters" for more information about the parameters available with this command

### Guidelines for Modifying a Time Slice in a Process Default Schedule

- You cannot change the start time of a time slice. Instead, you can remove the time slice and create a new one with the appropriate start time.

- You cannot create more than one time slice with the same start time. Instead, change the duration of the existing time slice.

- The time slices in a process default schedule must always add up to at least a full 24-hour period.

- In the Administration Tool, you cannot remove a time slice if it leaves the schedule with less than 24 hours. Therefore, you must first add one or more time slices that overlap the existing time slices. Then, you can remove the time slices you no longer need.

  For example, if you have one time slice that starts at 0 (midnight) and runs for 24 hours, and you want to change it to two time slices that start at 0 (midnight) and 12 (noon) and run for 12 hours each, then use the following procedure:

  - Create a new time slice that starts at 12 (noon) and runs for 12 hours. You now have two overlapping time slices adding up to 36 total hours (the original 24-hour slice, plus the new 12-hour slice).

  - Change the running time of the time slice that starts at 0 (midnight) from 24 hours to 12 hours. You now have two time slices adding up to 24 total hours (the 12-hour slice created to run from noon until midnight, plus the 12-hour slice modified to run from only midnight until noon).

  When finished, the sum of all the time slices should not exceed 24 hours. You should also make sure that your final time slices do not overlap.

### Example of Modifying a Time Slice in a Process Default Schedule

Suppose a postman process has the following schedule:

StartTime | Duration (Hr.) | SleepTime (Min.) | State (Active/Passive)
--- | --- | --- | ---
0 (midnight) | 2 | 15 | Active
2 | 2 | 15 | Passive
4 | 2 | 15 | Active
6 | 18 | 15 | Passive

To run this postman with a 10-minute sleep time between the first two work cycles instead of 15, enter the following command:

    IOFCMGR>modify paramtime server=monitor instance=1 starttime=0 to sleeptime=10;

## Removing a Time Slice from a Process Default Schedule

You can remove a time slice (also called a time detail record) from a default process schedule to delete a period of time during which the process is either active of passive. When you register a new process instance, it automatically inherits the default process schedule, including all the default time slices.

### Steps for Removing a Time Slice from a Process Default Schedule

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Removing a Time Slice from a Process Default Schedule" for more information about performing this task

#### In the Administration Tool GUI

1. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Defaults > process_default > Schedules > time_slice.

2. In the toolbar, click (Remove).

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>deregister paramtime server=<process_name>
       2>instance=0
       3>starttime=<start_time>;

### Guidelines for Removing a Time Slice from a Process Default Schedule

- The time slices in a process default schedule must always add up to at least a full 24-hour period.

- In the Administration Tool, you cannot remove a time slice if it leaves the schedule with less than 24 hours. Therefore, you must first add one or more time slices that overlap the existing time slices. Then, you can remove the time slices you no longer need.

  For example, if you have one time slice that starts at 0 (midnight) and runs for 24 hours, and you want to change it to two time slices that start at 0 (midnight) and 12 (noon) and run for 12 hours each, then use the following procedure:

  - Create a new time slice that starts at 12 (noon) and runs for 12 hours. You now have two overlapping time slices adding up to 36 total hours (the original 24-hour slice, plus the new 12-hour slice).

  - Change the running time of the time slice that starts at 0 (midnight) from 24 hours to 12 hours. You now have two time slices adding up to 24 total hours (the 12-hour slice created to run from noon until midnight, plus the 12-hour slice modified to run from only midnight until noon).

  When finished, the sum of all the time slices should not exceed 24 hours. You should also make sure that your final time slices do not overlap.

## Overriding a Default Time Slice for a Process Instance Schedule

Process schedules control when a process instance runs and for how long. Each process schedule is made up of one or more time slices (also called time record details) that add up to a 24-hour period. When you register a new process instance, it automatically inherits the default process schedule, including all the default time slices. You can override a default time slice by registering a time slice for the process instance schedule.

### Steps for Overriding a Default Time Slice for a Process Instance Schedule

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Overriding a Default Time Slice for a Process Instance Schedule" for more information about performing this task

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance > Schedules.

3. In the toolbar, click (Register).

4. Complete the Register Time dialog box.

   See Also: "Schedule Parameters" for more information about the parameters in this dialog box

5. In the Administration Tool, time slices that use the default values appear in black. Time slices that override the default values appear in blue.

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>register paramtime server=<process_name>
       2>instance=<instance_number>
       3>starttime=<integer between 0 and 23>
       4>duration=<whole number of hours>
       5>state=[A | P]
       6>sleeptime=<number of minutes>;

   See Also: "Schedule Parameters" for more information about the parameters available with this command

### Guidelines for Overriding a Default Time Slice for a Process Instance Schedule

- Define your time slices so that they do not overlap. Overlapping time slices can cause unpredictable behavior.

- Once you create a time slice, you cannot change the start time. To change the start time, you must delete the time slice and add a new one.

- The time slices in a process instance schedule must always add up to at least a full 24-hour period.

- In the Administration Tool, for a process instance, you cannot create a new time slice that overlaps another process instance time slice. However, you can create a new time slice that overlaps or has the same start time as a default time slice. When you create a new time slice that overrides the default values, the remaining default time slices for that instance automatically change their values so that they do not overlap with the new time slices.

- If you want to configure the sleeptime in seconds instead of minutes, then you must modify the Executable Arguments (ExecArguments) property for the postman and gateway process instances as follows:

      Executable Arguments = '-s N'

  where N represents the number of seconds.

  Refer to "Modifying Process Properties" for instructions.

## Modifying a Time Slice for a Process Instance Schedule

You can modify schedules for registered process instances if you want to change the duration of a time slice (also called time record details), its sleep time, or whether it is passive or active. You cannot modify the start time of a time slice.

### Steps for Modifying a Time Slice for a Process Instance Schedule

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Modifying a Time Slice for a Process Instance Schedule" for more information about performing this task

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance > Schedules > time_slice.

3. In the right pane, enter the new information in the appropriate text box.

   See Also: "Schedule Parameters" for more information about the parameters in this dialog box

4. Click Apply.

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>modify paramtime server=<process_name>
       2>instance=<instance_number> starttime=<integer>
       3>to sleeptime=<minutes>;

   See Also: "Schedule Parameters" for more information about the parameters available with this command

### Guidelines for Modifying a Time Slice for a Process Instance Schedule

- You cannot change the start time of a time slice.

- Define your time slices so that they do not overlap. Overlapping time slices can cause unpredictable behavior.

- For a process instance, you cannot change a time slice that uses the default values. In the Administration Tool, time slices that use the default values appear in black. Time slices that override the default values appear in blue.

- The time slices in a process instance schedule must always add up to at least a full 24-hour period. When you modify time slices, you may need to remove or create other time slices to ensure that the records account for a full 24-hour period.

- In the Administration Tool, for a process instance, you cannot change a process instance time slice that overlaps another process instance time slice. However, you can change a process instance time slice that overlaps or has the same start time as a default time slice. When you change a process instance time slice that overrides the default values, the remaining default time slices for that instance automatically change their values so that they do not overlap with the new time slices.

- If you want to configure the sleeptime in seconds instead of minutes, then you must modify the Executable Arguments (ExecArguments) property for the postman and gateway process instances as follows:

      Executable Arguments = '-s N'

  where N represents the number of seconds.

  Refer to "Modifying Process Properties" for instructions.

### Example of Modifying a Time Slice for a Process Instance Schedule

Suppose a postman process has the following schedule:

StartTime | Duration (Hr.) | SleepTime (Min.) | State (Active/Passive)
--- | --- | --- | ---
0 (midnight) | 2 | 15 | Active
2 | 2 | 15 | Passive
4 | 2 | 15 | Active
6 | 18 | 15 | Passive

To run this postman process with a 10-minute sleep time between the first two work cycles instead of 15, enter the following command:

    IOFCMGR>modify paramtime server=monitor
    2>instance=1 starttime=0
    3>to sleeptime=10;

## Reverting a Process Instance Time Slice to the Default Value

You can revert a time slice (also called time record details) for a registered process instance to the default value by deregistering the time slice for that instance.

### Steps for Reverting a Process Instance Time Slice to the Default Value

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Guidelines for Reverting a Process Instance Time Slice to the Default Value" for more information about performing this task

#### In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes > Instances > process_instance > Schedules > time_slice.

3. In the toolbar, click (Deregister).

#### In OOMGR

1. Start OOMGR.

2. Enter the following command at the OOMGR prompt:

       IOFCMGR>deregister paramtime server=<process_name>
       2>instance=<instance_number>
       3>starttime=<start_time>;

### Guidelines for Reverting a Process Instance Time Slice to the Default Value

- The time slices in a process instance schedule must always add up to at least a full 24-hour period.

- For a process instance, you cannot deregister a time slice that uses the default values. In the Administration Tool, time slices that use the default values appear in black. Time slices that override the default values appear in blue.

| Copyright © 2001 Oracle Corporation. All Rights Reserved. |
| Library | Service | Index