Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
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:
Chapter 11, "Process Parameter Reference" for a discussion of the eMail Server processes and how they work
See Also:
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.
This task can only be performed through the Administration Tool GUI.
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.
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.
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.
Caution:
This task can be performed through either the Administration Tool GUI, or through a standard shell tool.
$ 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 |
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
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 or restarting a node does not start the processes. You must start the processes explicitly.
In OOMGR, display the process status. Refer to "Displaying Process Status Information" for instructions.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
To perform this task: | Follow these steps: |
---|---|
Start one process instance |
|
Start all registered processes on a node |
In the menu, select Message System > Start All Processes... |
See Also:
"Common Process Parameters" for more information about the parameters available with this command |
You can display the following status information for registered processes:
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
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.
This task can only be performed through the OOMGR command-line interface.
IOFCMGR>display shadows user=<username
>;
See Also:
"Parameters for Displaying Database Shadow Processes" for more information about the values to enter |
Parameter | Description |
---|---|
|
The username associated with the connection that you think may have unneeded 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.
This task can only be performed through the OOMGR command-line interface.
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.
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
To perform this task: | Follow these steps: |
---|---|
Refresh one process |
|
Refresh all processes on a node |
In the menu, select Message System > Re-Activate All Processes... |
To perform this task: | Use this command: |
---|---|
Refresh one process |
IOFCMGR>refresh server=< |
Refresh all processes on a node |
IOFCMGR>refresh all; |
See Also:
"Common Process Parameters" for more information about the parameters available with this command |
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
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 |
You can shut down either a single process, or all processes on a node. When you shut down all processes on a node, you:
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
To perform this task: | Follow these steps: |
---|---|
Shut down one process |
|
Shut down all eMail Server processes on a node |
In the menu, select Message System > Stop All Processes... |
To perform this task: | Use this command: |
---|---|
Shut down one process |
IOFCMGR>shutdown server=< |
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 |
You can shut down the guardian process, if necessary. Shutting down the guardian process shuts down all running process under the guardian's control.
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. |
This task can be performed through either the Administration Tool GUI, or a standard shell tool.
$ 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 |
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Common Process Parameters" for more information about the parameters available with this command |
You can modify the default parameters that are used when you register a new process. The instance number for default processes is always 0.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
Chapter 11, "Process Parameter Reference", for more information about the parameters in this dialog box
See Also:
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 |
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.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
Chapter 11, "Process Parameter Reference", for more information about the parameters in this dialog box |
See Also:
Chapter 11, "Process Parameter Reference", for more information about the parameters available with this command |
You can remove parameter values for registered processes. Removing the registered parameter values for a process reverts that process to the default parameters.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
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 |
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 |
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
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 |
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.
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 |
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 |
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:
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.
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.
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 |
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 |
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:
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.
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;
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.
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 |
IOFCMGR>deregister paramtime server=<process_name
> 2>instance=0 3>starttime=<start_time
>;
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:
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.
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.
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 |
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 |
Executable Arguments = '-s N'
where N represents the number of seconds.
Refer to "Modifying Process Properties" for instructions.
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.
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 |
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 |
Executable Arguments = '-s N'
where N represents the number of seconds.
Refer to "Modifying Process Properties" for instructions.
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;
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.
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 |
IOFCMGR>deregister paramtime server=<process_name
> 2>instance=<instance_number
> 3>starttime=<start_time
>;
|
![]() Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|