Skip Headers

Oracle® Application Server Reports Services Publishing Reports to the Web 10g (9.0.4) Part Number B13673-01 |
| Home | Contents | Index

# 19 Managing and Monitoring OracleAS Reports Services

Oracle Enterprise Manager 10g, included with Oracle Application Server, provides managing and monitoring services for OracleAS Reports Services.

- The Oracle Enterprise Manager 10g Application Server Control Console provides both management and monitoring functions for your Reports Servers.

- The Oracle Enterprise Manager 10g Grid Control Console provides more monitoring functions, but does not provide management functionality.

This chapter describes the managing and monitoring capabilities of Oracle Enterprise Manager 10g as they relate to OracleAS Reports Services and tells you how to configure the Reports Server with Oracle Enterprise Manager 10g. It includes the following main sections:

- Configuring the Reports Server for Oracle Enterprise Manager 10g

- Navigating to the Reports Server Page

- Starting, Stopping, and Restarting Reports Servers

- Viewing and Managing Job Queues

- Monitoring Server Performance

- Viewing and Changing the Reports Server Configuration Files

- Viewing and Linking to Server Cluster Members

- Viewing Port Numbers

- Changing Your Middle-Tier

  Note: The Reports Server pages in Oracle Enterprise Manager 10g include context sensitive online help topics that offer information about the items that appear on each page. In Oracle Enterprise Manager 10g, click the Help link to display help.

  See Also: For more information on Oracle Enterprise Manager 10g, Oracle Application Server 10g Administrator's Guide, available on the Oracle Application Server documentation CD.

## 19.1 Configuring the Reports Server for Oracle Enterprise Manager 10g

Reports Servers are automatically configured in OPMN and registered with Oracle Enterprise Manager 10g during installation of Oracle Application Server. If you add any Reports Servers after installing Oracle Application Server, you must register the new server(s) in:

- The Oracle Enterprise Manager 10g’s `targets.xml` file. Refer to Configuring Reports Server with the Oracle Process Manager and Notification Server and Oracle Enterprise Manager 10g for more information on the `targets.xml` file and its usage.

- The Oracle Process Manager and Notification Server’s `opmn.xml` file. Refer to opmn.xml for more information on the `opmn.xml` file and its usage.

  Note: Use `addNewServerTarget.sh` (UNIX) or `addNewServerTarget.bat` (Windows) to add a Reports Server target to `targets.xml` and `opmn.xml`.

  See Also: For more information: Configuring Reports Server with the Oracle Process Manager and Notification Server and Oracle Enterprise Manager 10g

## 19.2 Navigating to the Reports Server Page

This section describes how to get to the Reports Server page:

- Navigating to the Reports Server Page in the Grid Control Console

- Navigating to the Reports Server Page in the Application Server Control Console

  Note: Before you launch the Oracle Enterprise Manager 10g, you must first install and configure a management server. For instructions on how to do this, see the Oracle Enterprise Manager Configuration Guide, available on the Oracle Application Server documentation CD and on the Oracle Technology Network (`http://otn.oracle.com`).

### 19.2.1 Navigating to the Reports Server Page in the Grid Control Console

You can get to the Reports Server page in a variety of ways. This procedure is just one possible way.

1. Launch the Grid Control Console. For more information on how to launch the console, refer to your Oracle Enterprise Manager 10g documentation. The Grid Control Console should look similar to Figure 19–1. The Home page provides a high-level view of your entire enterprise.

   Figure 19-1 Grid Control Console

   Description of the illustration oem_consmain.gif

2. Click the Targets tab.

3. Click the Application Servers sub tab. It should look similar to Figure 19–2.

   Figure 19-2 Grid Control Console, Targets, Application Servers Tab

   Description of the illustration oem_targets_centcons.gif

4. Click the Oracle Application Server instance that contains the Reports Server you want to view. The page should look similar to Figure 19–3.

   Figure 19-3 Grid Control Console, Application Server Page

   Description of the illustration oem_appserv_cons.gif

5. The Reports Server should appear in the list of components for that Oracle Application Server instance. Click on it. This link takes you to the Reports Server page. It should look similar to Figure 19–7.

### 19.2.2 Navigating to the Reports Server Page in the Application Server Control Console

You can get to the Reports Server page in a variety of ways. This procedure is just one possible way.

1. Launch the Application Server Control Console. For more information on how to launch the console, refer to your Oracle Enterprise Manager 10g documentation.

2. The console opens on the Farm page as shown in Figure 19-4, which displays the available Oracle Application Server instances.

   Figure 19-4 Farm Page in Oracle Enterprise Manager 10g

   Description of the illustration oem_standfarm.gif

3. Click the Oracle Application Server instance that contains the Reports Server you want to view. This link takes you to the page for that instance as shown in Figure 19-5.

   Figure 19-5 Oracle Application Server Page in Oracle Enterprise Manager 10g

   Description of the illustration oem_standfarm_inst.gif

4. Choose the Reports Server you wish to view from the list of components. This link takes you to the main page for the Reports Server, which should look similar to the one in Figure 19-6.

   Figure 19-6 Reports Server Main Page in Oracle Enterprise Manager 10g

   Description of the illustration oem_rprtsrver_stand.gif

## 19.3 Starting, Stopping, and Restarting Reports Servers

To start, stop, or restart a Reports Server:

1. Navigate to the Reports Server main page in the Application Server Control Console for the Reports Server you want to start, stop, or restart.

   Note: You can only start, stop, and restart the Reports Server from the Application Server Control Console.

   See Also: Navigating to the Reports Server Page in the Application Server Control Console for more information.

2. On the Reports Server's main page, you should see the following:

   - Click the Start button to start the server.

   - Click the Stop button to stop the server.

   - Click the Restart button to restart the server.

   These buttons appear on a Reports Server main page according to the server's current state:

   - When the server is down, the Stop (disabled) and Start buttons display.

   - When the server is up, the Stop and Restart buttons display.

     Note: Refer to the Oracle Enterprise Manager 10g Application Server Control Console section for more information on the various tabs displayed on the Reports Server home page.

## 19.4 Viewing and Managing Job Queues

You can view and manage your job queues in the Application Server Control Console.

- Viewing and Managing Job Queues in the Application Server Control Console

  Note: If you want to manage the job queue (e.g., cancel jobs or rerun jobs), you must do so from the Application Server Control Console. To get to the Application Server Control Console, return to the Reports Server main page and click Administration under Related Links. Once there, follow the instructions in Viewing and Managing Job Queues in the Application Server Control Console.

### 19.4.1 Viewing and Managing Job Queues in the Application Server Control Console

The following sections describe:

- Viewing and Managing the Current Jobs Queue

- Viewing and Managing the Scheduled Jobs Queue

- Viewing and Managing the Finished Jobs Queue

- Viewing and Managing the Failed Jobs Queue

#### 19.4.1.1 Viewing and Managing the Current Jobs Queue

The reports Current Jobs queue lists all jobs currently running on a particular Reports Server.

Use Oracle Enterprise Manager 10g for:

- Viewing a Reports Server's Current Jobs Queue

- Cancelling a Current Job

##### 19.4.1.1.1 Viewing a Reports Server's Current Jobs Queue

To view a current jobs queue:

1. Navigate to the Reports Server main page in Oracle Enterprise Manager 10g for the Reports Server you want to view.

   See Also: Navigating to the Reports Server Page for more information.

2. On the Reports Server's main page, scroll down to the Jobs section and click the number next to Current Jobs.

   If there are no current jobs, a zero appears next to Current Jobs and there will be no link because the queue is empty.

Table 19-1 lists and describes information provided in the current jobs queue.

Table 19-1 Information provided in the Current Jobs Queue

Item | Description
--- | ---
Select | Use this radio button to select a particular job. On the Current Jobs Queue page, this function is most useful when you wish to cancel a job. Click the Select radio button next to a job you wish to cancel, then click the Cancel button near the top of the page.
Id | This displays a unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.
Job Name | If you specified a job name in the command line you used to run this job, that name is listed here; otherwise, it is the name of the job provided for the "`report=`" or "`module=`" parameter of the job request.
Owner | This displays the user ID under which this job is running.
Output Type | Lists the destination type (`destype`) specified for this job at runtime.
Output Format | Lists the output format (`desformat`) specified for this job at runtime.
Queued At | Lists the date and time this request was placed in the job queue.
Started At | Lists the date and time when this job was run.
Status | Status of the current job.

##### 19.4.1.1.2 Cancelling a Current Job

To cancel a current job:

1. On the Current Jobs page, click the Select radio button next to the job you want to cancel.

2. Click the Cancel button. This button does not display in Oracle Enterprise Manager 10g if there are no currently running jobs.

If you wish to rerun the job, you can do so from the Finished Jobs page.

#### 19.4.1.2 Viewing and Managing the Scheduled Jobs Queue

The scheduled jobs queue lists all jobs scheduled to run on a particular Reports Server.

Use Oracle Enterprise Manager 10g for:

- Viewing a Reports Server's Scheduled Jobs Queue

- Cancelling a Scheduled Job

##### 19.4.1.2.1 Viewing a Reports Server's Scheduled Jobs Queue

To view a scheduled jobs queue:

1. Navigate to the Reports Server main page in Oracle Enterprise Manager 10g for the Reports Server you want to view.

   See Also: Navigating to the Reports Server Page for more information.

2. On the Reports Server main page, scroll down to the Jobs section and click the number next to Scheduled Jobs.

   If there are no scheduled jobs, a zero appears next to Scheduled Jobs and there will be no link because the queue is empty.

Table 19-2 lists and describes information provided in the scheduled jobs queue.

Table 19-2 Information provided in the Scheduled Jobs Queue

Item | Description
--- | ---
Select | Use this radio button to select a particular job. On the Scheduled Job Queue page, this function is most useful when you wish to cancel a job. Click the Select radio button next to a job you wish to cancel, then click the Cancel button near the top of the page.
Id | This displays a unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.
Job Name | If you specified a job name in the command line you used to run this job, that name is listed here; otherwise, it is the name of the job provided for the "`report=`" or "`module=`" parameter of the job request.
Owner | This displays the user ID under which this job is scheduled to run.
Output Type | Lists the destination type (`destype`) specified for this job.
Output Format | Lists the output format (`desformat`) specified for this job.
Repeat Interval | The frequency at which the job will be run, for example, daily, monthly, and so on.
Last Run At | The time stamp when the scheduled job was previously run.
Next Run At | The time stamp when the scheduled job was run immediately next.

##### 19.4.1.2.2 Cancelling a Scheduled Job

To cancel a scheduled job:

1. On the Scheduled Jobs page, click the Select radio button next to the job you want to cancel.

2. Click the Cancel button.

   This button does not display in Oracle Enterprise Manager 10g if there are no scheduled jobs.

If you wish to rerun the job, you can do so from the Finished Jobs page.

#### 19.4.1.3 Viewing and Managing the Finished Jobs Queue

The finished jobs queue lists all successfully completed jobs on a particular Reports Server.

Use Oracle Enterprise Manager 10g for:

- Viewing a Reports Server's Finished Jobs Queue

- Viewing a Job’s Trace File

- Viewing a Result from Cache

- Rerunning a Finished Job

##### 19.4.1.3.1 Viewing a Reports Server's Finished Jobs Queue

To view a finished jobs queue:

1. Navigate to the Reports Server main page in Oracle Enterprise Manager 10g for the Reports Server you want to view.

   See Also: Navigating to the Reports Server Page for more information.

2. On the Reports Server main page, scroll down to the Jobs section and click the number next to Finished Jobs.

   If there are no finished jobs, a zero appears next to Finished Jobs and there will be no link because the queue is empty.

Table 19-3 lists and describes information provided in the finished jobs queue.

Table 19-3 Information provided in the Finished Jobs Queue

Item | Description
--- | ---
Select | Use this radio button to select a particular job. On the Finished Job Queue page, this function is most useful for selecting a job and: Viewing its output Click the Select radio button next to a job you want to view, then click the View Result button near the top of the page. Viewing its trace results, provided that you included a trace command in the runtime command. Click the Select radio button next to a job with trace results you want to view, then click the View Trace button near the top of the page. Reports Server displays the `No Log File Found` error if the trace file is not found. Refer to trace for more information on how to specify the `trace` options for a job. Rerunning it Click the Select radio button next to a job you want to rerun, then click the Rerun Report button near the top of the page.
Id | Use this link to view the trace files for the job. This displays a unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.
Job Name | Use this link to view the results of the job. If you specified a job name in the command line you used to run this job, that name is listed here; otherwise, it is the name of the job provided for the "`report=`" or "`module=`" parameter of the job request.
Owner | This displays the user ID under which this job was run.
Output Type | Lists the destination type (`destype`) specified for this job.
Output Format | Lists the output format (`desformat`) specified for this job.
Queued At | Lists the date and time this request was placed in the job queue.
Started At | Lists the date and time this job started running.
Finished At | Displays the date and time this job completed.
Status | Displays the finished status of the job. In the Finished Jobs Queue, status is always Finished Successfully.

##### 19.4.1.3.2 Viewing a Job’s Trace File

The trace file contains tracing information about the report’s execution. You set which tracing options you want the Reports Server to use in the job command line via the `traceopts` argument.

See Also: View trace for more information about available tracing options.

To view a job’s trace file:

1. In the Select column on a Finished Jobs page, click the radio button next to the finished job whose trace file you want to view.

2. Click the View Trace button near the top of the page. Alternatively, you can click the ID link.

   Note: Reports Server displays the `No Log File Found` error if the trace file is not found. Refer to trace for more information on how to specify the trace options for a job.

##### 19.4.1.3.3 Viewing a Result from Cache

When monitoring you Reports Server, it can sometimes be useful to quickly check a report’s output to verify that it produced the desired output. To view a job result from the Report Server cache:

1. In the Select column on a Finished Jobs page, click the radio button next to the finished job you want to view.

2. Click the View Result button near the top of the page. Alternatively, you can click the Name link.

   The result opens in a separate browser window.

##### 19.4.1.3.4 Rerunning a Finished Job

In some cases, you may want to quickly resubmit a report for execution (e.g., to refresh the contents of the cache). To rerun a job from the Finished Jobs page:

1. In the Select column, click the radio button next to the finished job that you want to rerun.

2. Click the Rerun Report button near the top of the page.

#### 19.4.1.4 Viewing and Managing the Failed Jobs Queue

The failed jobs queue lists all jobs that were cancelled or terminated with errors on a particular Reports Server.

Use Oracle Enterprise Manager 10g for:

- Viewing a Reports Server's Failed Jobs Queue

- Viewing a Failed Job’s Trace File

- Rerunning a Failed Job

##### 19.4.1.4.1 Viewing a Reports Server's Failed Jobs Queue

To view a failed jobs queue:

1. Navigate to the Reports Server main page in Oracle Enterprise Manager 10g for the Reports Server you want to view.

   See Also: Navigating to the Reports Server Page for more information.

2. On the Reports Server's main page, scroll down to the Jobs section and click the number next to Failed Jobs.

   If there are no failed jobs, a zero appears next to Failed Jobs and there will be no link because the queue is empty.

Table 19-4 lists and describes information provided in the failed jobs queue.

Table 19-4 Information provided in the Failed Jobs Queue

Item | Description
--- | ---
Select | Use this radio button to select a particular job. On the Failed Jobs Queue page, this function is most useful for selecting a job and: Viewing its trace results, provided that you included a trace command in the runtime command. Click the Select radio button next to a job with trace results you want to view, then click the View Trace button near the top of the page. Rerunning it Click the Select radio button next to a job you want to rerun, then click the Rerun Report button near the top of the page.
Id | This displays a unique job identifier assigned to this job by the Reports Server. This number is strictly under the server's control and cannot be reset by a user.
Job Name | If you specified a job name in the command line you used to run this job, that name is listed here; otherwise, it is the name of the job provided for the "`report=`" or "`module=`" parameter of the job request.
Owner | This displays the user ID under which this job was run.
Output Type | Lists the destination type (`destype`) specified for this job.
Output Format | Lists the output format (`desformat`) specified for this job.
Queued At | Lists the date and time this request was placed in the job queue.
Started At | Lists the date and time this job started running.
Finished At | Displays the date and time this job was cancelled or terminated with error.
Status | Displays the finished status of the job. It informs you whether a job was cancelled by the user or terminated with error. In instances where a job was terminated with error, a brief error message is provided to indicate the cause of termination.

##### 19.4.1.4.2 Viewing a Failed Job’s Trace File

To aid you in determining why a job failed, you can view the trace file for the failed job. To view a failed job’s trace file:

1. In the Select column on a Failed Jobs page, click the radio button next to the failed job whose trace file you want to view.

2. Click the View Trace button near the top of the page. Alternatively, you can click the ID link.

   Note: Reports Server displays the `No Log File Found` error if the trace file is not found. Refer to trace for more information on how to specify the `trace` options for a job.

##### 19.4.1.4.3 Rerunning a Failed Job

In order to quickly check whether the problem with a failed job has been resolved, you can rerun the job from the Failed Jobs page. To rerun a failed job:

1. In the Select column on the Failed Jobs page, click the radio button next to the failed job you want to rerun.

2. Click the Rerun Report button near the top of the page.

## 19.5 Monitoring Server Performance

Each Reports Server registered with Oracle Enterprise Manager 10g has its own main page that summarizes general information about the server's status and performance. You can monitor Reports Server performance from the following places:

- Oracle Enterprise Manager 10g Grid Control Console

- Oracle Enterprise Manager 10g Application Server Control Console

### 19.5.1 Oracle Enterprise Manager 10g Grid Control Console

The Reports Server main page in the Grid Control Console provides a variety of statistics and graphs to help you monitor your Reports Server. The Reports Server main page in the Grid Control Console has three tabs:

- Home, shown in Figure 19-7

- Performance, shown in Figure 19-8

- Jobs, shown in Figure 19-9

  Figure 19-7 Home Tab of Reports Server Main Page

  Description of the illustration oem_repserver_cent.gif

The Home tab contains the following sections:

- General provides the current status of the Reports Server and, if it's up, the date and time the server was started. It also lists the number of active engines, scheduled jobs, availability percentage, average response time, the product version, and the host that owns this particular Reports Server. To drill down for additional detail, you can click the availability percentage, the average response time, or the number of active engines. Note that on all of the drill down pages, you can change the time interval for the displayed statistics (e.g., you can look at numbers for the last 24 hours, the last 7 days, or the last month). Clicking the host name takes you to that host’s main page.

- Response and Load provides a graph that shows the relationship between average response time and the number of jobs being processed. If you click the graph, you drill down to a more detailed page about response time. This drill down page contains additional statistics and a historical graph of the data.

- Alerts displays any recent messages received because a metric exceeded a threshold value. For example, an alert might be raised if average response time goes above a certain level. Clicking on the name of the metric takes you to the detailed page for that metric.

- Host Alerts displays any recent messages received for the host that owns the Reports Server. For example, a host alert might be raised if file system usage exceeds a certain threshold.

- Related Links enables you to jump to other areas.

  - Edit Metric Thresholds lets you change the limit that will result in an alert for various metrics.

  - All Metrics displays an expandable/collapsible listing of all of the metrics available to you. You can also drill into the metrics in the list for more details.

  - Alert History displays a bar graph that summarizes the number of alerts raised per metric. Administration takes you to the Reports Server page in the Application Server Control, where you can perform actions like starting and stopping the Reports Server.

Figure 19-8 Performance Tab of Reports Server Main Page

Description of the illustration oem_repservercent_perf1.gif

The Performance tab contains the following sections:

- The View Data list of values enables you to change the interval of time for the graphs on the Performance tab.

- Response Time graphs response times over the course of some interval (e.g., one hour).Failed Jobs Ratio graphs the ratio of failed jobs to total jobs over the course of some interval (e.g., one hour).

- CPU Usage (%) graphs the percentage of CPU in use over the course of some interval (e.g., one hour).

- Memory Usage graphs the memory in use over of some interval (e.g., one hour).

Figure 19-9 Jobs Tab of Reports Server Main Page

Description of the illustration oem_reptsvrcent_jobs.gif

The Jobs tab contains the following sections:

- The View Data list of values enables you to change the interval of time for the graphs on the Jobs tab.

- Job Load graphs the number of jobs submitted to the Reports Server over the course of some interval (e.g., one hour).

- Job Completion Statistics graphs the number of failed and successful jobs over the course of some interval (e.g., one hour).

- Elapse Time graphs the time taken by the jobs to execute at the time of invoking the graph. For current jobs it is average execution time. The statistics displayed by this graph can be used to find out :

  - The jobs that do not execute quickly.

  - The jobs that stop responding.

### 19.5.2 Oracle Enterprise Manager 10g Application Server Control Console

The Reports Server main page in the Application Server Control Console has two tabs:

- Home, shown in Figure 19-10

- Engines, shown in Figure 19-11

Figure 19-10 Home Tab of Reports Server Main Page

Description of the illustration oem_rprtsrver_stand1.gif

The Home tab contains the following sections:

- General provides the current status of the Reports Server and, if it is up, the date and time the server was started. It also includes the buttons for stopping, starting, and restarting.

  Note: The current status of a Reports Server will be reflected accurately only if you start and stop it by using either Oracle Enterprise Manager 10g or OPMN.

- Configuration provides the selected Reports Server's cluster name, if it is a member of a cluster; the trace option and mode specified in its configuration file; and the maximum number of jobs that can be held at one time in the Reports Server queue (this applies to all three queues, i.e., current, scheduled, and past job queues). All of these are configurable in the Reports Server configuration file.

  See Also: For more information about the configuration file: Reports Server Configuration Elements (rwserverconf.dtd)

- Response and Load provides current statistics for CPU and memory usage, and average response time of the Reports Server.

  - CPU Usage (%) displays the percentage of the host machine's CPU currently utilized by the selected Reports Server.

  - Memory Usage (%) displays the percentage of the host machine's RAM currently utilized by the selected Reports Server. This metric does not apply to in-process servers.

    Note: In-process servers run in an OC4J_BI_Forms instance, and the CPU Usage(%) and Memory Usage(%) metrics are part of the OC4J_BI_Forms instance. Thus, the metrics for an in-process server are always displayed as Unavailable.

  - Average Response Time displays the average number of milliseconds taken by the Reports Server to process a request from the client.

- Jobs provides the number of current (currently running), finished, scheduled, and failed jobs; and the number of jobs transferred from the current server to another server in the same cluster (clustered environment). If a number greater than zero appears, you can click it to drill down to a complete listing of each job in that particular queue (e.g., all failed jobs). If the number is zero, then that queue is empty and no drill down is necessary.

- Other Server(s) Running In This Cluster: Refer to Viewing and Linking to Server Cluster Members for more information on this section.

- Dependent Components lists the status of all of the components (e.g., Oracle HTTP Server and Oracle Application Server Web Cache) upon which the Reports Server depends. By clicking on the component names in this list you can drill into more detailed status information for each dependent component.

- Administration contains links to various administrative functions:

  - Configuration takes you to a page where you can modify the most commonly used Reports Server or engine parameters. The Edit Configuration File button in this page enables you to edit the Reports Server configuration file directly.

  - Edit Configuration File takes you to a page where you can directly edit the Reports Server configuration file. This page provides a useful Check Syntax function so that you can validate your changes before committing them to the configuration file.

  - Server Trace File takes you to a page where you can review the latest report execution tracing information for the Reports Server or download it for further analysis.

  - Server Log takes you to a page where you can review the latest Reports Server log file or download it for further analysis.

    See Also: Oracle Enterprise Manager 10g online help For more information on the available options to search for log / trace files.

Figure 19-11 Engines Tab of Reports Server Main Page

Description of the illustration oem_standfarm_engines.gif

The Engines tab contains the following sections:

- Total Engines lists the number of engines currently up and running on the Reports Server. The table below this field lists the engines by ID with their current status.

- Engine ID lists the type of engines available for processing jobs on the selected Reports Server.

- Engines provides the total number of the specified engine type that is currently active on the selected Reports Server.

- Running provides the total number of this type of engine that is currently running on the selected Reports Server.

- Engine Parameters button to directly take you to the Configuration page where you can view/modify the Engine and Report Server parameters. This page has a link using which you can edit the Report Server Configuration file directly.

## 19.6 Viewing and Changing the Reports Server Configuration Files

You can modify/view the Reports Server Configuration in either of the following ways:

- Configuring Selected Parameters

- Configuring the server_name.conf File

### 19.6.1 Configuring Selected Parameters

To view and modify some of the most commonly used engine and server parameters through Oracle Enterprise Manager 10g:

1. Navigate to the Reports Server main page in Application Server Control Console for the Reports Server you want to view.

2. Click the Configuration link under Administration. The parameters displayed in the Configuration screen are picked up from the Reports Server's configuration file (`server_name`.`conf`).

   1. Reports Engine Parameters:

      - `Engine ID`: Displays the valid Engine IDs for the selected server.

        Select the Engine ID from a drop down menu to edit the engine parameters for the selected engine. Only those engines that are already present in the server configuration file are displayed in the drop down list.

        Note: Click the Edit Configuration File button to add a new engine.

      - `Classpath`(Optional): The directory path to the Java class specified in the class attribute. Refer to engine for more information on the various engine properties available for the Reports Server.

      - Initial Engines`(initEngine)`: The number of engines you want the Reports Server to start at initialization. Refer to engine for more information on the various engine properties available for the Reports Server.

      - Maximum Engines `(maxEngine)`: The maximum number of this type of engine that can run on the server. Refer to engine for more information on the various engine properties available for the Reports Server.

      - Minimum Engines `(minEngine`): The minimum number of this type of engine maintained on the server. . Refer to engine for more information on the various engine properties available for the Reports Server.

      - Maximum Jobs Before Shutdown`(engLife)`: Displays the ceiling of jobs that must be completed before the engine is shut down. Refer to engine for more information on the various engine properties available for the Reports Server.

      - Maximum Idle Before Shutdown `(maxIdle)`(minutes): The number of minutes of allowable idle time before the engine is shut down, provided the current number of engines is higher than `minEngine`. Refer to engine for more information on the various engine properties available for the Reports Server.

      - `JVM Option`(Optional): The Java Virtual Machine (JVM) options to be used by the Reports Server when it starts an engine in the JVM. Refer to engine for more information on the various engine properties available for the Reports Server.

   2. Reports Server Parameters:

      - `Cache Size(MB)`: The file size in mega bytes (MB) for the Reports Server’s cache. Refer to cache for more information on the `cache` properties.

      - `Cache Directory` (Optional): The location of the Reports Server cache. Refer to cache for more information on the `cache` properties.

      - `Maximum Cached Files` (Optional): The ceiling on the number of files allowed in the cache. Refer to cache for more information on the `cache` properties.

      - `Ignore Parameters` (Optional): Any report parameters you want to be ignored when the Reports Server constructs the cache key. (The cache key is used by the Reports Server to determine if an incoming job request matches existing output in the cache.) Refer to cache for more information on the `cache` properties.

      - `Idle Timeout` (minutes) (Optional): Allowable amount of time in minutes the connection can be idle. Refer to connection for more information on the various `connection` properties.

      - `Maximum Connections` (Optional): The maximum number of requests that the server can service simultaneously. Requests in excess of the `maxConnect` value return a Java exception. Refer to connection for more information on the various connection properties.

      - `Maximum Queue Size:` The maximum number of jobs that can be held in a given Reports Server job queue. Refer to queue for more information on the various queue properties.

      - `Trace Options:` Refer to trace for more information on the available `trace` options. The default trace option considered when no option is specified is `trace_replace`.

   3. Click OK to save the changes changes made to the engine and server parameters to the Reports Server configuration file. A Confirmation page is displayed. Click Yes to restart the server.

      Note: You must restart the server for your changes to take effect.

   4. Click Cancel to discard any changes made.

### 19.6.2 Configuring the server_name.conf File

To view and change a Reports Server's configuration file through Oracle Enterprise Manager 10g:

1. Navigate to the Reports Server main page in Application Server Control Console for the Reports Server you want to view.

   See Also: Navigating to the Reports Server Page in the Application Server Control Console for more information.

2. Under Administration, click the Edit Configuration File link.

3. Make your changes in the display window.

4. Click the Check Syntax button to check your XML syntax.

   Note: Clicking this button does not validate the values you enter for configuration elements. For example, if an element requires that you specify a directory path, syntax checking does not validate the accuracy of your path. It just validates the XML syntax.

5. Click the OK button to save your changes or the Cancel button to discard your changes. Clicking Cancel will also return you to the Reports Server main page.

6. If you chose OK in the previous step, Oracle Enterprise Manager 10g prompts you to restart the Reports Server. Changes to the Reports Server configuration file do not take effect until you restart the Reports Server.

   Changes take effect after the next server startup or restart.

   See Also: Chapter 3, " Configuring OracleAS Reports Services" For more information about the attributes and values in the Reports Server configuration file.

## 19.7 Viewing and Linking to Server Cluster Members

When you cluster Reports Servers together, it's reflected on each cluster member's page in Oracle Enterprise Manager 10g under the Other Servers Running in This Cluster heading. Each listed cluster member links to the page for that member.

Table 19-5 lists and describes the information the Other Servers … section provides for each cluster member:

Table 19-5 Information under the Other Servers Running in this Cluster Heading

Row | Description
--- | ---
Server Name | Lists the names of each of the other Reports Servers that are members of the same cluster that the selected Reports Server belongs to. Click a server name to hyperlink to the cluster member's home page in OEM.
Finished Jobs | Provides the total number of finished jobs currently in the listed Reports Server's Job Queue.
Current Jobs | Provides the total number of currently running jobs in the listed Reports Server's Job Queue.
Scheduled Jobs | Provides the total number of scheduled jobs currently in the listed Reports Server's Job Queue.
Failed Jobs | Provides the total number of jobs for the listed Reports Server that were stopped before completion. This includes jobs that were user-terminated or terminated with error.
Average Response Time | Lists the average number of milliseconds it takes for the listed Reports Server to process a request from the client.

## 19.8 Viewing Port Numbers

In many cases, you need to quickly discover the port numbers in use by the Reports Server. The Application Server Control Console lets you quickly find port numbers by following these steps:

1. Launch the Application Server Control Console. For more information on how to launch the console, refer to your Oracle Enterprise Manager 10g documentation.

2. The console opens on the Farm page as shown in Figure 19-4, which displays the available Oracle Application Server instances.

3. Find the Oracle Application Server instance that contains the Reports Server you want to view. Click that instance to go to its main page.

4. From the Oracle Application Server instance main page, click Ports to go to the Ports tab. On the Ports tab, you will find a list of all of the ports currently in use by that Oracle Application Server instance, including the ports used by the Reports Server.

Figure 19-12 Application Server Control Console, Ports Tab

Description of the illustration oem_ports_standalone.gif

## 19.9 Changing Your Middle-Tier

In some cases, you might want to change the Infrastructure Services used by a middle-tier instance. For example, you may want to use a different Oracle Internet Directory or Metadata Repository than the ones you chose during installation. For instructions on how to change the Infrastructure Services used by a middle-tier instance, refer to Oracle Application Server 10g Administrator's Guide.