AuditEvent Understanding Data Objects

1-6 Developers Guide for Imaging and Process Management

1.2.2.6 AuditEvent

Many objects include a section for returning the audit history associated with that object. This history includes the actions taken by various users that have affected that object. Audited actions would include creation, modification, or viewing of that object. The audit history records the action that occurred, the user performing it, and the date upon which it occurred. 2 Getting Started 2-1 2 Getting Started This chapter contains the following sections: ■ Section 2.1, Requirements ■ Section 2.2, Configuring the Class Path ■ Section 2.3, Introductory Sample

2.1 Requirements

Oracle IPM clients not running on an Oracle WebLogic server have the following requirements: ■ JDK 1.6 or higher ■ An installed and operational Oracle IPM system

2.2 Configuring the Class Path

The imaging API is contained in the .jar file imaging-client.jar. This is the only .jar reference required to obtain IPM-specific classes for use in client code. The imaging-client.jar file is dependent on a number of infrastructure classes for JAX-WS web services and Oracle Web Service Manager Security. These dependencies are automatically available when the client API is called from within an Oracle JRF enabled JEE container. For standalone JSE clients, IPM provides a bundled zip file containing all external dependencies required by imaging-client.jar. The procedure for configuring references in a stand alone JSE environment is shown below. This procedure assumes that Enterprise Content Management ECM is installed to ORACLE_HOME on a server system, and the client system has no WebLogic or other ECM components installed. To configure references in a stand-alone JSE environment, do the following: 1. Copy ORACLE_HOMEipmlibecm-client.zip from the server to a temporary directory on the client. 2. Extract ecm-client.zip to a directory on the client. The directory should contain a lib directory accessible to the client working environment. The .jar files contained within it will be referenced on the classpath at both compile and run time. A typical solution is to place it in a lib directory parallel to the client src and classes directories.