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 are: 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 IPM Public API, IPM Services, and Repository Abstraction. Inside the IPM Services rectangle is the Annotation Burning rectangle. Touching the bottom of the Repository Abstraction rectangle is the UCM Repository 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.

The Input File Directory icon on the left and outside the gray square is connected to the Input Agent rectangle at the top left and inside the gray square by a two-headed arrow, which indicates two-way communication between the Input File Directory and Input Agent. The Input Agent rectangle is connected to the Internal JMS Queue icon below it by a two-headed arrow. This indicates two-way communication between the Input Agent and Internal JMS Queue. To the right of the Internal JMS Queue are several Input MDBs icons. The Internal JMS Queue is connected to each of the Input MDBs icons by a one-headed arrow. This indicates that the Internal JMS Queue has a one-way communication to the Input MDBs. Each of the Input MDBs icons has a one-headed arrow that points to the IPM Public API rectangle in the middle of the gray square. This indicates that the Input MDBs have a one-way communication to the IPM Public API.

At the top and in the middle section of the gray square is a Web Services rectangle with a UI ADF Layer rectangle to the right of it. The Web Services rectangle has a two-headed arrow that connects it to the IPM Public API rectangle in the middle of the gray square. This indicates two-way communication between Web Services and the IPM Public API. The UI ADF Layer rectangle also has a two-headed arrow that connects it to the IPM Public API rectangle in the middle of the gray square. This indicates two-way communication between the UI ADF Layer and IPM Public API.

The IPM Config storage device icon on the left and outside the gray square is connected to the TopLink rectangle to its right inside the gray square by a two-headed arrow. This indicates two-way communication between the IPM Config and TopLink. The TopLink rectangle is connected to the IPM Services rectangle to its right in the middle of the gray square by a two-headed arrow. This indicates two-way communication between TopLink and IPM Services.

Below the TopLink rectangle is a JOC rectangle to the left of the IPM Services rectangle. This JOC rectangle is connected to the IPM Services rectangle by a two-headed arrow. This indicates two-way communication between JOC and IPM Services.

Below the JOC rectangle is a Temp Files icon, and below the Temp Files icon is another JOC rectangle. 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 the 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 also 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.

Below the lower JOC icon near the bottom of the gray square is another TopLink rectangle. This lower TopLink rectangle is also connected to the 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 TopLink and AXF Services. This TopLink rectangle is also connected 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.

The IPM Applet Viewer rectangle and the IPM "REST" API rectangles on the right and outside the gray square each have a one-headed arrow to the Servlet inside the gray square. This indicates that the IPM Applet Viewer and IPM "REST" API have a one-way communication to this Servlet. The Servlet is connected to the IPM Public API rectangle in the middle of the gray square by a two-headed arrow. This indicates two-way communication between the Servlet and IPM Public API.

The IPM Public API rectangle in the middle of the gray square is connected to several BPEL MDB icons to its right with a two-headed arrow. This indicates two-way communication between the IPM Public API and the BPEL MDBs. 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 Web Services have a one-way communication to BPEL Web Services.

The IPM Services rectangle below the IPM Public API rectangle in the middle of the gray square is connected to the 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.

The BPEL rectangle below the BPEL Web Services rectangle on the right and outside the gray square are connected to each other by a two-headed arrow. This indicates that BPEL and BPEL Web Services have two-way communication with each other. The BPEL rectangle also has a two-headed arrow that connects it with the AXF Services rectangle that is 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.

The IPM Services rectangle in the middle of the gray square is connected to the JNDI rectangle below the BPEL rectangle on the right and outside the gray square with a one-headed arrow. This indicates that the IPM Services have a one-way communication to JNDI.

The JNDI rectangle on the right and outside the gray square has a one-headed arrow that connects it with the AXF Services rectangle that is in the center and near the bottom of the gray square. This indicates that JNDI has a one-way communication to AXF Services.

To the right of the AXF Services rectangle that is in the center and near the bottom of the gray square are the UI ADF Layer rectangle and the Web Services rectangle.

The AXF Services rectangle has a two-headed arrow that connects it with the UI ADF Layer rectangle to its right. This indicates that the AXF Services and UI ADF Layer have two-way communication withe each other.

The AXF Services rectangle has a two-headed arrow that connects it with the Web Services rectangle to its right. This indicates that the AXF Services and Web Services have two-way communication with each other.