Configuring Reports Server with the Oracle Process Manager and

Notification Server and Oracle Enterprise Manager 10g

During installation of Oracle Application Server, Reports Servers are automatically configured in OPMN and
registered with Oracle Enterprise Manager 10g. If you add any Reports Servers after installing Oracle
Application Server, you should register the
new server(s) in two places:
■ The Oracle Process Manager and Notification Server's opmn.xml file.
■ The Oracle Enterprise Manager 10g's targets.xml file.
To register a new Reports Server in both opmn.xml and targets.xml, run the following command line:

On Windows:
ORACLE_HOME\bin\addNewServerTarget.bat reports_server_name

Note: After running this command line, reload the OPMN configuration file for the change to take effect (for
example,
opmnctl reload).

opmn.xml
Components are configured with OPMN in the opmn.xml file located in ORACLE_HOME/opmn/conf. This
section describes how to configure the following components through OPMN:
■ Module Specification
■ Standalone Reports Server Specification
■ In-process Reports Server Specification
■ Oracle Reports Bridge Specification
■ COS Naming Service Specification (optional)

Standalone Reports Server Specification

In the case of the standalone Reports Server, the Reports Server is running in its own component.
Therefore, you must specify a separate component for Reports Server to control the server through OPMN.
For example:

<ias-component id="<RSName>" status="enabled" id-matching="false">

<process-type id="ReportsServer" module-id="ReportsServices">
<process-set id="<RSName>" restart-on-death="true" numprocs="1">
<environment>
<variable id="PATH" value="your_shell_path"/>
</environment>
<module-data>
<category id="general-parameters">
<data id="batch" value="yes"/>
</category>
<category id="restart-parameters">
<data id="reverseping-timeout" value="120"/>
</category>
</module-data>
<dependencies>
<OID infrastructure="true"/>
<database infrastructure-key="portal"/>
<managed-process ias-component="OC4J" process-type="OC4J_BI_Forms"
process-set="default_island" autostart="true"/>
<managed-process ias-component="HTTP_Server"
process-type="HTTP_Server" process-set="HTTP_Server"
autostart="true"/>
<managed-process ias-component="WebCache" process type="WebCache"
process_set="WebCache" autostart="true"/>
</dependencies>
<start timeout="600" retry="2"/>
<stop timeout="120"/>
<restart timeout="600"/>
<ping timeout="30" interval="30"/>
</process-set>
</process-type>
</ias-component>

COS Naming Service Specification

By default, Oracle Reports uses the built-in broadcast mechanism for Reports Server discovery.
Alternatively, Oracle Reports clients can use the Common Object Service Configuring Reports Server with
the Oracle Process Manager and Notification Server and Oracle Enterprise Manager 10g 3-66 Oracle
Application Server Reports Services Publishing Reports to the Web (COS) naming service for Reports
Server discovery to submit report requests when the built-in broadcast mechanism is not suitable for your
environment, as in the following scenarios:
■ Oracle Reports is installed on a machine that is connected to a network using VPN.
■ You want to avoid broadcast traffic on your network.

To control the COS naming service through OPMN, the opmn.xml file must include a
custom ias-component tag, as follows:

<ias-component id="namingservice">
<process-type id="namingservice" module-id="CUSTOM">
<environment>
<variable id="PATH" value="ORACLE_HOME\jdk\bin"/>
</environment>
<process-set id="namingservice" numprocs="1">
<module-data>
<category id="start-parameters">
<data id="start-executable" value="ORACLE_HOME\jdk\bin\orbd"/>
<data id="start-args" value="-ORBInitialPort port"/>
</category>
</module-data>
</process-set>
</process-type>
</ias-component>
where
ORACLE_HOME is your Oracle Home directory. port is the port on which you want to start the COS naming
service. This port must be specified in your rwnetwork.conf file, as described in Section
3.3.1.3,"namingService".
Additionally, to make sure that OPMN starts the COS naming service before it attempts to start Reports
Server, opmn.xml must include the following dependency:

<ias-component id="vin" status="enabled" id-matching="false">

<process-type id="ReportsServer" module-id="ReportsServices">
...
<managed-process ias-component="namingservice" process-type="namingservice"
process-set="namingservice" autostart="true"/>
...
</process-type>
</ias-component>

To use OPMN to control the COS naming service, perform the following steps:
1. Stop Reports Server and OC4J_BI_Forms.
2. Edit the opmn.xml file and add an ias-component tag. For example:
...
<ias-component id="namingservice">
<process-type id="namingservice" module-id="CUSTOM">
<environment>
<variable id="PATH" value="G:\FRHome_2\jdk\bin"/>
</environment>
<process-set id="namingservice" numprocs="1">
<module-data>
<category id="start-parameters">
<data id="start-executable" value="G:\FRHome_2\jdk\bin\orbd"/>
<data id="start-args" value="-ORBInitialPort 8988"/>
</category>
</module-data>
</process-set>
</process-type>
</ias-component>
...
3. Add a dependency to the Reports Server ias-component tag. For example:
...
<ias-component id="vin" status="enabled" id-matching="false">
<process-type id="ReportsServer" module-id="ReportsServices">
<process-set id="vin" restart-on-death="true" numprocs="1">
<environment>
<variable id="PATH" value="C:/OraHome/bin;C:/WINNT/system32;C:/WINNT"/>
</environment>
<module-data>
<category id="general-parameters">
<data id="batch" value="yes"/>
</category>
<category id="restart-parameters">
<data id="reverseping-timeout" value="120"/>
</category>
</module-data>
<dependencies>
<OID infrastructure="true"/>
<database infrastructure-key="portal"/>
<managed-process ias-component="namingservice"
process-type="namingservice" process-set="namingservice"
autostart="true"/>
<managed-process ias-component="OC4J" process-type="OC4J_BI_Forms"
process-set="default_island" autostart="true"/>
<managed-process ias-component="HTTP_Server" process-type="HTTP_Server"
process-set="HTTP_Server" autostart="true"/>
</dependencies>
<stop timeout="120"/>
<restart timeout="600"/>
<ping timeout="30" interval="30"/>
</process-set>
</process-type>
</ias-component>
...
4. Navigate to your ORACLE_HOME/opmn/bin directory.
5. Run one of the following commands:
■ If OPMN is up and running, to reload the changes made to the opmn.xml file:
opmnctl reload

■ If OPMN is not running: opmnctl start

6. Start the COS naming service using either of the following commands:
opmnctl startproc ias-component=namingservice
OR
opmnctl startproc process-type=namingservice
7. Modify the rwnetwork.conf file to use the COS naming service instead of the
default broadcast mechanism, as described in Section 3.3.1.3, "namingService".
8. Start OC4J_BI_Forms and Reports Servers.
To stop the COS naming service, use the following command:
opmnctl stopproc ias-component=namingservice

To restart the COS naming service, use the following command:

opmnctl restartproc ias-component=namingservice

Troubleshooting: If a COMM_FAILURE error displays when Reports Server is started, either the naming
service is not started properly or the port is not specified properly.

To resolve this error, check whether the naming service process orbd is running. If not, start it. If the orbd
process is running, check the port specified for namingService in the rwnetwork.conf file. It should be same
as the port on which orbd is started. When you execute the command opmnctl stopall, Reports Server may
not stop gracefully, and may be killed by OPMN. This is because OPMN does not check the dependency
while stopping the process. If OPMN stops the COS naming service before stopping Reports Server,
Reports Server will not shut down gracefully. This is harmless, and can be ignored.