Oracle® Process Manager and Notification Server Administrator's Guide 10g Release 3 (10.1.3.1.0) Part Number B28944-01 |
|
|
View PDF |
This chapter describes the new features of Oracle Process Manager and Notification Server (OPMN) available in Oracle Application Server 10g Release 3 (10.1.3.1.0).
This chapter includes the following topics:
In Oracle Application Server 10g Release 3 (10.1.3) and earlier releases, you could not place OC4J instances into groups. Each OC4J instance was a single entity as shown in the following 10.1.3 opmn.xml
file code example:
Example 1-1 10.1.3 and Earlier Release OC4J Instance opmn.xml
<ias-component id="OC4J"> <process-type id="home" module-id="OC4J"> <port id="ajp" range="3301-3400" /> <port id="rmi" range="3101-3200" /> <port id="jms" range="3201-3300" /> <process-set id="default-group" numprocs="1"/> </process-type> </ias-component>
In 10g Release 3 (10.1.3.1.0), you can group OC4J instances. The <ias-component>
element in the opmn.xml
file can be used as a grouping mechanism. For example, an OC4J group called COLORS
can be configured as follows:
Example 1-2 10.1.3.1.0 OC4J Instance opmn.xml
<ias-component id="COLORS"> <process-type id="home" module-id="OC4J"> <port id="ajp" range="3301-3400" /> <port id="rmi" range="3101-3200" /> <port id="jms" range="3201-3300" /> </process-type> <process-type id="oc4j_soa" module-id="OC4J"> <port id="ajp" range="3301-3400" /> <port id="rmi" range="3101-3200" /> <port id="jms" range="3201-3300" /> </process-type> </ias-component>
In the example shown in Example 1-2, the COLORS
group represents a synchronized collection of OC4J instances. This functionality enables simultaneous configuration to all OC4J instances in the Group.
You can select specific OC4J instances and move them to a group. You can also create an empty group and then populate it later by editing the group using Groups View through Oracle Enterprise Manager 10g Application Server Control Console (Application Server Control Console).
Refer to Section 3.2, "OC4J Groups" and the Oracle Application Server Administrator's Guide for more information.
The output for the opmnctl status
command has changed with 10.1.3.1.0. For example, the following output is displayed when executing the opmnctl status
command on an 10.1.3 release Oracle Application Server instance:
Example 1-3 opmctl Status Output for 10.1.3
prompt > opmnctl status Processes in Instance: AppSrv1.comp1.yourcompany.com --------------------+----------------------+--------+--------- ias-component | process-type | pid | status --------------------+----------------------+--------+--------- OC4J | OC4J_Demos | N/A | Down OC4J | home | 29268 | Init HTTP_Server | HTTP_Server | 29099 | Alive
The output of opmnctl status
command for 10.1.3.1.0 labels OC4J Groups and OC4J processes as follows:
Example 1-4 opmctl Status Output for 10.1.3.1.0
--------------------+----------------------+--------+--------- ias-component | process-type | pid | status --------------------+----------------------+--------+--------- OC4JGroup:COLORS | OC4J:home | 16301 | Alive OC4JGroup:COLORS | OC4J:oc4j_soa | 16256 | Alive
In 10g Release 3 (10.1.3.1.0), there is a new opmnctl
option that enables to to execute control and monitor your OC4J groups. The new opmnctl
option for OC4J groups is similar to the commands applicable to the <ias-component>
element in the opmn.xml
file but applies to OC4J components.
For example, using the OC4J group COLORS
as shown in Example 1-2 and Example 1-4:
To obtain the status of the OC4J group COLORS
:
prompt > opmnctl @cluster status oc4j-group=COLORS
To start all of the processes in the OC4J group COLORS
:
prompt > opmnctl @cluster startproc oc4j-group=COLORS