Oracle Forms Server Release 6i:
Deploying Forms Applications to the Web with iAS
Patch 2







Oracle Enterprise Manager Forms Support

13.1 Introduction

This chapter describes how to install and configure Oracle Enterprise Manager (OEM) for use with Forms. It also describes the features and functions of OEM. OEM is a system management tool that consist of a graphical Java console, management server, agents, and tools that provide you with an integrated systems management platform for managing Oracle products.

This chapter contains the following sections:

Detailed OEM documentation is located in:

13.2 Why Should I Use OEM?

The OEM Forms administrator interface provides the following basic functions:

13.3 OEM Components

There are three OEM components that you need to install in order to manage Forms Servers:

13.4 Installing and Configuring OEM Components for Use with Forms

The OEM Management Server (OMS), OEM Console, and OEM Agent software are installed as part of Oracle Internet Application Server.

13.4.1 Configuring Forms Support for OEM

After Forms and OMS are installed, do the following. Be sure that the OMS service is not running while performing the following steps.

  1. On the machine where OMS is installed, change directories to $ORACLE_HOME\sysman\admin.

  2. Connect to the OEM repository database using a login that has system privileges (e.g. system).

  3. Run the "createOEMFormsUser.sql" script to create an OEM Forms User who will support Forms specific data in the OEM repository. (You can modify this script to add default tablespace, quota, and so on. However, you cannot change the user name and password in the script.)

  4. Connect to the database as the OEM Forms User. (See the SQL script you just ran for the user name and password.)

  5. Run the "createOEMFormsTables.sql" script to create the necessary tables in the OEM repository.

  6. On the machine where the console is installed, create a TNS entry in the Tnsnames.ora file to connect to the OEM repository database. Use the same TNS alias as the one used to connect to the EM repository on the OMS machine.

13.4.2 Starting the OMS Service

To start the OMS Service, type:

oemctrl start oms

or start the service from the control panel on Windows NT.

13.5 Managing Forms Servers from the OEM Console

You cannot manage a pre-existing Forms Listener from OEM. You must create it first from the OEM console.

13.5.1 Locating Nodes

Before OEM can manage a remote Forms Server machine, it has to locate it. To do this:

  1. In the OEM Console, choose Discover Node from the menu.

  2. Enter the node name. For example, formssrv-pc.

13.5.2 Entering the Administrative User's Credentials in the OEM Console

To enter the administrative user's credentials in the OEM console:

  1. Start the OEM Console.

  2. Choose Preferences from the System menu.

  3. Choose the Preferred Credentials tab.

  4. Find the name of the remote Forms Server machine you want to administer in the Service Name column. Be sure to select a row where the Service Type is Node.

  5. Enter the operating system user name and password for the user that has performed the Oracle Internet Application Server instalation on this node.

    Note: On Windows NT, the user needs to be granted the "Log on as a service" user right in the User Manager.

13.5.3 Viewing Forms Runtime Instances from the OEM Console

To view Forms Runtime Instances from the OEM Console:

  1. From the OEM Console, select Developer Servers, Forms_Listeners_<RemoteMachineName>, .

  2. Right-click and select List Runtime Processes.

13.6 OEM Menu Options

The following menu options are available for managing Forms Listeners, Forms Servers, Load Balancer Servers, and Load Balancer Clients.

13.6.1 Controlling Forms Listeners Group

The commands available from the right mouse menu are:

13.6.2 Controlling Forms Listeners Instance

The commands available from the right mouse menu are:

13.6.3 Runtime Processes List Window

This is a table type listing of all the current Forms Runtime processes on a particular node. Each row represents a Runtime process. The following fields are displayed:

13.6.4 Controlling Forms Runtime Processes

The commands available from the right mouse menu are:

13.6.5 Controlling Load Balancer Server Group

The command available from the right mouse menu is:

Load Balancer Server is also known as Metrics Server.

13.6.6 Controlling Load Balancer Server Instance

The commands available from the right mouse menu are:

Load Balancer Server is also known as Metrics Server.

13.6.7 Controlling Load Balancer Client Group

The commands are exactly the same as the Load Balancer Server object type. The supported parameters are:

<Master Server host name> <Remote port> <Local port> <Scale Factor>

Load Balancer Client is also known as Metrics Client.

13.6.8 Controlling Load Balancer Client Instance

The commands are exactly the same as the Load Balancer Server object instance.

Load Balancer Client is also known as Metrics Client.

13.6.9 Monitoring Functions

Events are listed in the Events Management window of the OEM console. They can be turned on or off by registering or un-registering with OEM. Once an event is created and registered with OEM, OEM can notify the system administrator or run a fixit job when an event occurs.

The following events are available for you to register:


You must schedule a fixit job before you can schedule an event with a fixit job.

Prev Next
Copyright © 2000 Oracle Corporation.

All Rights Reserved.