This figure shows the Oracle I/PM internal components for a single instance.

In this figure, the main part of the figure is a large gray square. This gray square contains multiple Oracle I/PM components.

On the left and outside of the gray square are two icons organized vertically. The Input File Directory icon is above the IPM Config storage device icon.

To the right and outside of the gray square are several rectangles organized vertically. Starting from the top, the order of these rectangles is: IPM Applet Viewer, IPM "REST" API, BPEL Web Services, BPEL, and JNDI.

Near the middle of the gray square are three rectangles stacked horizontally. From top to bottom, the rectangles are as follows: IPM Public API, IPM Services, and Repository Abstraction. Inside the IPM Services rectangle is the Annotation Burning rectangle. Everything in the figure has some connection to these three central rectangles.

Five items connect directly to IPM Public API. Their connection to IPM Public API and other components are as follows:

• One-headed arrows point from a group of boxes labeled Input MDBs to IPM Public API. This indicates that the IPM Public API recieves one-way input from the Input MDBs.

  • The Input MDB boxes receive input from an icon labeled Internal JMS Queue. Internal JMS Qgueue is connected to each of the Input MDBs icons by a one-headed arrow. This indicates that a one-way communication exists between the Input MDBs and the Internal JMS Queue.

  • The Internal JMS Queue icon is connected to the Input Agent rectangle above it by a two-headed arrow. This indicates two-way communication between the Internal JMS Queue andthe Input Agent.

  • The Input Agent rectangle at the top left and inside the gray square is connected to the Input File Directory icon outside of the grey square by a two-headed arrow, which indicates two-way communication between the Input Agent and Input File Directory.

• The Web Services rectangle at the top of the grey square connects to IPM Public API through a two-headed arrow. This indicates two-way communication between Web Services and the IPM Public API.

• A UI ADF Layer rectangle located beside the Web Services box also has a two-headed arrow that connects it to IPM Public API. This indicates two-way communication between the UI ADF Layer and IPM Public API.

• BPEL MDB icons to the right of the IPM Public API are connected to it by a two-headed arrow. This indicates two-way communication.

  • Each of the BPEL MDBs icons has a one-headed arrow from it to the BPEL Web Services to its right and outside of the gray square. This indicates that the BPEL MDBs have a one-way communication to BPEL Web Services.

  • BPEL Web Services is connected to a BPEL rectangle below it by a two-headed arrow. This indicates that BPEL Web Services and BPEL have two-way communication with each other.

  • The BPEL rectangle has a two-headed arrow that connects it with the AXF Services rectangle in the center and near the bottom of the gray square. This indicates that BPEL and AXF Services have two-way communication with each other.

• A box labeled Servlet connects to the IPM Public API through a two-headed arrow. This indicates two-way communication between the Servlet and IPM Public API.

  • One-headed arrows point to the Servlet from the IPM Applet Viewer rectangle and the IPM "REST" API rectangles. They are located outside to the right and outside the gray square. The one-headed arrows indicate that the IPM Applet Viewer and IPM "REST" API have a one-way communication to this Servlet.

Three items connect directly with IPM Services. Their connections to IPM Services and other components are as follows:

• The IPM Services rectangle is connected to a BPEL JMS Queue icon with a one-headed arrow. This indicates that the IPM Services have a one-way communication to the BPEL JMS Queue.

  • The BPEL JMS Queue has several one-headed arrows that connect it to the BPEL MDBs above it. This indicates that the BPEL JMS Queue has a one-way communication to the BPEL MDBs.

  • A JNDI rectangle below the BPEL rectangle outside the gray square connects to IPM Services with a one-headed arrow. This indicates that the IPM Services have a one-way communication to JNDI.

    • The JNDI rectangle has a one-headed arrow that connects it with the AXF Services rectangle that near the bottom of the gray square. This indicates that JNDI has a one-way communication to AXF Services.

    • The AXF Services rectangle has two-headed arrows that connects it with the UI ADF Layer rectangle and the Web Services rectangle to its right. This indicates that the AXF Services has two-way communication with UI ADF Layer and Web Services.

• A TopLink rectangle is directly connected to the IPM Services rectangle by a two-headed arrow. This indicates two-way communication between TopLink and IPM Services.

• The TopLink rectangle is connected by a two-headed arrowto an IPM Config storage device outside the gray square.

One item connects to the Annotation Burning box contained inside of IPM Services. Its connections to Annotation Burning and other components are as follows:

• A JOC rectangle to the left of the IPM Services rectangle is connected to the Annotation Burning rectangle by a two-headed arrow. This indicates two-way communication between JOC and Annotation Burning.

  • Below the JOC rectangle is a Temp Files icon. The Temp Files icon is connected to the JOC rectangle above it by a two-headed arrow. This indicates two-way communication between the Temp Files and the JOC above it.

  • The Temp Files icon is also connected to another JOC rectangle below it by a two-headed arrow. This indicates two-way communication between the Temp Files and the JOC below it.

  • The lower JOC rectangle is connected to an AXF Services rectangle that is in the center and near the bottom of the gray square by a two-headed arrow. This indicates two-way communication between this JOC and AXF Services.

  • The AXF Services box connected to the lower JOC box is the same AXF Services box receiving input from the JNDI box and in a two-way communication link with the BPEL box. It also is connected by a two-headed arrow to a TopLink rectangle located beneath the lower JOC icon near the bottom of the gray square. This indicates two-way communication between this TopLink and AXF Services.

  • This TopLink rectangle also connects to the IPM Config storage device icon on the left and outside the gray square by a two-headed arrow. This indicates two-way communication between this lower TopLink and IPM Config.

One Item directly connects to the Repository Abstraction rectangle. Its connections to Repository Abstraction and other components are as follows:

• The UCM Repository rectangle touches the bottom of the Repository Abstraction rectangle. Below the UCM Repository rectangle is a storage device icon labeled "Metadata Content." A two-headed arrow connects the UCM Repository rectangle with the Metadata Content storage device, which indicates two-way communication between the UCM Repository and the Metadata Content.