9
Runtime Management

This chapter describes how to manage OracleAS InterConnect components using the Oracle Enterprise Manager Central Console.

This chapter discusses the following topics:

• Introduction to Runtime Management

• Features

Introduction to Runtime Management

The Runtime Management Console is an Oracle Enterprise Manager Console-based tool that allows you to manage your integration components at runtime. The OracleAS InterConnect components that can be managed through the Console are as follows:

• Adapters

• Repository Server

To be able to manage your integration components, you must

• Install the Oracle Enterprise Manager Server on your hub machine. When the management server is started it detects the repository in the hub and all associated adapters.

• Install the Oracle Enterprise Manager Console on the machine you wish to manage your integration components from.

  See Also: Oracle Application Server Installation Guide Oracle Enterprise Manager Concepts Guide, Release (9.2.0)

Starting Oracle Enterprise Manager Console

To start the Oracle Enterprise Manager Console:

1. Start the Oracle Enterprise Manager Console with the following command:

   (On UNIX) $ oemapp console

   (On Windows) c:\oemapp console

   You may also start the Oracle Enterprise Manager Console from the Windows Services panel.

2. On the Oracle Enterprise Manager Login page, enter the Administrator name, password, and the Management Server that you want to connect to. Click OK.

3. The Console displays.

   

   Text description of the illustration oemconsole.gif

4. Expand the OracleAS InterConnect subtree, a list of adapters and the repository associated with the particular OracleAS InterConnect hub displays.

   

   Text description of the illustration oemconsolea.gif

5. Right click any of the adapters or repositories to manage or to use its features.

Features

The following are runtime features for adapters and the repository.

Common Features for Adapters and the Repository

The following features are provided for both adapters and repository:

• Get State--Shows the component's status. Red indicates the component is stopped. Green indicates the component is running. Yellow indicates the component state is unknown.

• Start--Starts the component.

• Stop--Stops the component.

• Alert On Shutdown--Allows you to send a page or email if that particular component goes down. Refer to the Oracle Enterprise Manager Administrator's Guide for setting up the alert.

• Get Ini File--Allows you to browse and modify the .ini file for that particular component. If you make changes, the tool prompts you to restart the component. You must restart the component for the changes to take effect.

• Get Log File--Allows you to browse the log files for a particular component. Repositories have one log file each. Adapters have multiple log files. This feature allows you to select the log file you want to view.

• Get Alive Time--Gets the duration that the component has been up for since it was last started.

• Remove--Removes the component from the list of manageable components for this session of the Oracle Enterprise Manager Console.

Repository Specific Features

• Get Repo Sessions--Gets a list of all components connected to the repository, such as adapters and iStudio.

Adapter Specific Features

• Get Throughput--Monitor the adapter throughput in terms of messages/second. The steps to get throughput information are as follows:
  1. Right-click the adapter for which to get throughput information and select Get Throughput.

  2. On the dialog that displays, click Get Throughput. Throughput information is displayed for inbound and outbound message separately. At startup time the adapter starts recording throughput information by default. To record throughput information in a particular interval, click disable timer, then click enable timer. This restarts the recording process and allows new throughput information to be available by clicking Get Throughput.

• Track Messages--Track particular messages at runtime. During design time, in iStudio, you can specify fields in the application view for publish event or invoke procedure with which to track the message. For example, a customer related message could be tracked by an application view field, such as social security number. The following steps utilize this functionality in the runtime management console:
  1. Right-click on any adapter attached to the application that is publishing the event or invoking the procedure to track. On the context menu, select Track Messages. A list of trackable events and procedures is displayed.

  2. Select the event or procedure to track.

  3. A dialog displays asking for the value(s) of the selected tracking field(s) for that particular event or procedure in iStudio. Therefore, in the customer related message example, the dialog asks for the social security number.

• Get Errors--Displays all errors associated with the adapter. Certain errors have a message payload associated with them. These errors are marked with a yes in the Editable column. To modify and resubmit a message:
  1. Double-click the description field for such an error. Depending on the processing state at which the error occurred, a dialog displays an XML message in the application or common view.

  2. If necessary, edit the message. If this is not necessary, go to the next step.

  3. Click Resubmit. The message now re-enters the integration system for reprocessing.