2.1 Displaying the Fusion Middleware Control User Interface

Fusion Middleware Control is a web browser-based interface that you can use to monitor and administer a farm. A farm is a collection of components managed by Fusion Middleware Control. It can contain Oracle WebLogic Server domains, one Administration Server, one or more Managed Servers, clusters, and the Oracle Fusion Middleware components that are installed, configured, and running in the domain.

Fusion Middleware administrators can use Fusion Middleware Control to access and manage a Content Server instance.

To access Fusion Middleware Control:

Fusion Middleware Control is configured for a domain and it is automatically started when you start the Oracle WebLogic Server Administration Server.

Enter the Fusion Middleware Control URL in your web browser. The URL must include the name of the host and the port number assigned during the installation. The following shows the format:

http://hostname.domain:port/em

For example: http://host.example.com:7001/em

You can find the exact URL, including the administration port number, in the config.xml file:

On Windows: DOMAIN_HOME\config\config.xml

On UNIX: ORACLE_INSTANCE/config/config.xml

If the port number is not listed in the file, the default port number is 7001.

A default user name for the administrator user is provided with the software. This is the account you can use to log in to Fusion Middleware Control for the first time. The password is the one supplied during the installation of Oracle Fusion Middleware.

The first page Fusion Middleware Control displays is the farm home page. You can also view this page at any time by selecting the name of the farm in the navigation pane.

2.4.1 Modifying Server Configuration Parameters for Content Server

Manage the HTTP address, which is the server address used to formulate full URLs in the Content Server user interface. This prevents users from being prompted to log in again because the domain name used to enter the server is not changed when links on pages are relative. Example setting: pc.idc.example.com.

Manage the Intradoc server port, which is the port number listened to by the Content Server instance. This is a trusted connection where only the user ID is required to authenticate. Example setting: 4056.

Manage the IP address filter, which is a list of IP addresses that are allowed to communicate to the Content Server instance through the Intradoc Server Port. The field accepts both IP and IPv6 addresses, with a pipe as the separator between addresses. This list must be well defined because it is a trusted connection. Example setting: 10.131.123.*.

Choose whether or not to use Secure Sockets Layer (SSL), which is related to the HTTP server address and indicates that the full URL uses the secured HTTP nomenclature. For example, it generates an address with https://(HttpServerAddress)/... instead of http://(HttpServerAddress)/...

2.4.2 Modifying E-mail Configuration Parameters for Content Server

Specify the mail server, which is the name of the mail server that the content server uses to send SMTP based e-mail. Example: mailserver.example.com.

Specify the SMTP port, which is the port number used to connect to the mail server. Example: 25.

Specify the admin mail address, which is the administrator e-mail address that receives error messages. Such messages are generally logged, but this is an additional method of notification. Example: mymail@example.com.

From the Content Server menu on the Home page, choose Configuration. The General Settings page displays.

In the Email Configuration section, in the Mail Server field, enter the name of a mail server.

In the Email Configuration section, in the SMTP Port field, enter a port number.

In the Email Configuration section, in the Admin Mail Address field, enter an e-mail address.

Click Apply.

The General Settings page updates with the configuration changes.

If you do not want to apply changes, click Revert to return to the previous configuration settings.

2.5 Viewing Performance Information for Content Server

You can monitor performance information for the Content Server instance. Information includes a graphic of metrics, a summary of the most recent metric values, and a listing of recent service requests.

To select which metrics to display in performance graphs, click the Show Metric Palette button on the Performance Summary page. The Metric Palette lists available options for metrics to display in graphs on the Performance Summary page.

To view metrics in a table format, select Table View.

Check the box for each metric you want to display:

Active Threads: The number of active threads.

Active Database Connections: The number of active database connections made by the Content Server instance.

Search Queries Cached: The number of search queries cached (rows).

Hit to Miss Ratio: The hit to miss ratio for the number of search queries performed.

Documents in GenWWW State: The number of documents waiting for Inbound Refinery in a GenWWW state.

Documents Waiting to be Indexed in Done State: The number of documents waiting to be indexed in a Done state.

Average Requests Per Sec: The average number of Services requested per second.

From the Content Server menu on the Home page, choose System MBean Browser.

The System MBean Browser page displays. This page shows the navigation pane with the Content Server name highlighted, and shows configuration MBean application deployment information for the Content Server instance.

You can use the MBean browser to view or modify individual MBean attribute values, and to invoke MBean operations. Select the MBean and the attribute you want to view or modify. If you change an attribute value, click Apply.