Network Configuration Elements Network Configuration File

8-68 Publishing Reports to the Web with Oracle Reports Services

8.5.1.3 namingService

The namingService element is defined in rwnetwork.xsd as follows: xs:element name=namingService xs:complexType xs:attribute name=name use=required type=xs:string xs:attribute name=host use=required type=xs:string xs:attribute name=port use=required xs:simpleType xs:restriction base=xs:integer xs:minInclusive value=1 xs:restriction xs:simpleType xs:attribute xs:complexType xs:element Example namingService name=Cos host=mymachine.mydomain.com port=14021 RequiredOptional Conditional. The namingService and multicast elements are mutually exclusive; that is, only one of these elements can be configured at a time. Description The namingService element contains the necessary information required to be able to identify the host name and the port where the COS naming service is running. Specify this element only 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. retry Retry count The Reports Client will retry for the specified number of times, if there is no response from the Reports Server after the timeout period. Note: It is strongly recommended that you do not change the default channel and port unless it is absolutely necessary. The default port value for rwnetwork.conf is assigned when you install Oracle Fusion Middleware. If you want to customize rwnetwork.conf, you must specify a valid port range reserved for Reports Server 14021 to 14030. If you are using the Oracle Reports Bridge for discovering Reports Servers across subnets, you should set the timeout and retry values carefully for the bridge to function correctly. Refer to Table 8–31 for setting the timeout value. Table 8–31 Cont. Attributes of the multicast Element Attributes Valid Values Description Configuring Oracle Reports Services 8-69 For more information, see Section 2.3.4.2, Server Discovery Using the COS Naming Service . The namingService element attributes are described in Table 8–32 .

8.6 Configuring the URL Engine

Reports Server includes a URL engine that can take the contents of any URL and distribute them. The URL engine enables you to leverage the powerful scheduling and distribution capabilities of Reports Server to distribute content from any publicly available URL to various destinations such as e-mail, Oracle Portal, and WebDAV. Since Reports Servers destinations are pluggable, you can also add your own custom destinations for the URL content. Furthermore, if you use the URL engine in conjunction with Reports Servers event-based APIs, database events can trigger the content distribution. For example, suppose you have created a JSP report for high fidelity Web publishing of data stored in a table containing employee expense data. You could then use the URL engine and the event-based API to e-mail that JSP whenever the expense application stores new or updated employee expense data in the table. If the URL engine is not activated, you can activate it by doing the following:

1. Add an

engine element for the URL engine to the server configuration file. For example, your engine element might be as follows: engine id=rwURLEng class=oracle.reports.engine.URLEngineImpl initEngine=1 maxEngine=1 minEngine=0 engLife=50 maxIdle=30 callbackTimeOut=60000

2. Add a

job element that associates the appropriate job types with the URL engine to the server configuration file. For example, your job element might be as follows: job jobType=rwurl engineId=rwURLEng

3. Stop and restart Reports Server.

Table 8–32 Attributes of the namingService Element Attributes Valid Values Description name Cos The descriptive name of the naming service. host Host nameIP The host name of the machine where the naming service is running. port Port number The port number of the machine where the naming service is running. 8-70 Publishing Reports to the Web with Oracle Reports Services To learn about sending requests to the URL engine, refer to Chapter 18, Running Report Requests .

8.7 Entering Proxy Information

Some features of Oracle Reports Services support retrieving or sending information through a firewall. For example, the URL engine, the XML data source, the Text data source, and the mail destination features all retrieve or send information through the firewall. For these features to function properly, Reports Server requires certain proxy information. In Oracle Reports 11g Release 1 11.1.1, proxy information is stored in the Reports Server configuration file rwserver.conf. You can specify proxy information in either of the following ways: ■ Using Oracle Enterprise Manager recommended ■ Editing the Server Configuration File

8.7.1 Using Oracle Enterprise Manager

To specify proxy information using Oracle Enterprise Manager, refer to Section 7.14, Configuring Proxy Information .

8.7.2 Editing the Server Configuration File

To specify proxy information by editing the server configuration file rwserver.conf directly, add the proxyServer element, as described in Section 8.2.1.24, proxyServer . 8.8 Configuring Reports Server with the Oracle Process Manager and Notification Server and Oracle Enterprise Manager The best way to start, shut down, monitor, and manage Reports Server is through the Oracle Process Manager and Notification Server OPMN and Oracle Enterprise Manager. OPMN provides a centralized mechanism for initializing, maintaining, and shutting down your Oracle Fusion Middleware components, including Reports Server. Out-of-the-box, Oracle Reports components are managed with OPMN for death detection and recovery, providing an enhanced health check mechanism in Oracle Reports 11g Release 1 11.1.1. You can conveniently monitor your Reports Servers through Oracle Enterprise Manager and, if the process fails for any reason, OPMN restarts Reports Server for you automatically. During installation of Oracle Fusion Middleware, Reports Servers are automatically configured in OPMN and registered with Oracle Enterprise Manager. Note: When you restart your Reports Server with these new elements, you should see the number of engines increase accordingly in the Reports Server status message box. In the preceding example, the number of engines would increase by one the value of initEngine when you restart Reports Server. Configuring Oracle Reports Services 8-71

8.8.1 opmn.xml

Components are configured with OPMN in the opmn.xml file located in INSTANCE_ HOMEconfigOPMNopmnopmn.xml This section describes how to configure the following components through OPMN: ■ Module Specification ■ Standalone Reports Server Specification ■ Oracle Reports Bridge Specification ■ COS Naming Service Specification

8.8.1.1 Module Specification

The module tag is included by default in opmn.xml and tells OPMN to load a particular module. In the case of Reports Server, the OracleAS Reports Services module must be loaded. This module is loaded with the following information, by default, in opmn.xml: module path=privateoraclehomeopmnliblibopmnreports module-id id=ReportsServices module

8.8.1.2 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=ServerName process-type id=ReportsServerComponent module-id=ReportsServices process-set id=ServerName restart-on-death=true numprocs=1 environment variable id=PATH value=PATH environment variable 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 start timeout=75 retry=2 stop timeout=120 restart timeout=75 ping timeout=30 interval=30 process-set process-type ias-component See Also: For a detailed description of OPMNconfiguration and the contents of opmn.xml: ■ Oracle Fusion Middleware Administrators Guide Note: The timeout values in the preceding example are all in number of seconds.