Oracle I/PM resides within WebLogic Server, connected to a database. Oracle I/PM events are routed through WebLogic Server using Java Messaging Service (JMS) to communicate with its background agents. Custom applications can interact with I/PM through its set of custom Oracle I/PM application programming interfaces (APIs). For more information about Oracle I/PM APIs, see Oracle Fusion Middleware Oracle Imaging and Process Management Developer's Guide.
through standard web services generated with the Java API for XML Web Services (JAX-WS)
through Oracle I/PM Java APIs, a set of portable Java class files
The Remote Java API uses the same API as the Oracle I/PM user interface.
Oracle I/PM provides architectural concepts that are designed to help business managers simplify the process of building imaging solutions. These architectural concepts, such as applications, searches, and inputs, provide convenient constructs around which a business user can organize their solution, grant security to relevant user groups, and finally migrate between differing system instances --development and production for example. Oracle I/PM's public API provides services aligned with these architectural concepts whose implementations reside in I/PM's business logic layer. Although most requests flow directly through these layers producing immediate responses, some tasks are better performed in the background. These tasks are relegated to a collection of Oracle I/PM background processes is known as agents.
Standard Java Management J2EE Beans (or MBeans) are used to configure the operation of Oracle I/PM's business logic as well as its agents. The values of these MBean configuration objects can be manipulated through Oracle Enterprise Manager and WebLogic Scripting Tool, allowing you to choose the best system management tool for your needs.