The Records Manager (RM) Java™ API provides networked and Java-based access to commonly-used objects and includes methods for performing record-related operations such as declaration, navigation, and disposal. In addition, the RM Java API provides an interface between custom applications and document repositories.
Using the RM Java API, you can perform operations such as relocating, copying, moving, superseding, and deleting records. To perform these operations, the RM Java API uses existing Content Java API classes, such as ObjectStore, Document, Folder, and CustomObject, to exhibit the default behavior of the Content Java API objects. For example, in the RM Java API, the RMFolder interface extends the Folder interface of the Content Java API and inherits the default behavior of this interface. Using the RMFolder interface, you can derive various container objects, such as classification schemes, record categories, and record folders.
For IBM® Enterprise Records to retrieve attachments or other documents from a Content Engine file or object store, you must use the Content Engine COM API. See the Compatibility Layer for the 3.5.x Content Engine COM API section in the IBM FileNet® P8 documentation Developer roadmap located in the Developer Help for information about installing and using this API.
The RM Java™ API requires the Java 2 Standard Edition (J2SE) 1.3.x or higher development environment. In addition, it uses various Java packages such as com.filenet.rm.api, com.filenet.rm.api.exception, and com.filenet.rm.api.util. The following table provides a description of these Java packages:
Java Package | Description |
---|---|
com.filenet.rm.api | Contains interfaces and classes used for record management operations such as copying, moving, filing, and declaring records. |
com.filenet.rm.api.exception | Contains exception classes used by the RM Java API. |
com.filenet.rm.api.util | Contains utility functions for the RM application, such as filtering the File Plan Object Store (FPOS) or Record Object Store (ROS) from an object store. |
The RM Java™ API requires various .jar (Java Archive) files during runtime. These .jar files contain the class implementation files. The supplied versions of these .jar files are required for the RM Java API and you should not substitute other .jar files with the same names. If you are writing a standalone Java application that uses the RM Java API, the required .jar files must be on your class path. A missing .jar file can lead to errors and "class not found" exceptions. The following table lists the required .jar files.
.jar File | Contains |
---|---|
rmapi.jar | The class implementation files for the RM Java API. |
javaapi.jar | The class implementation files for the Content Java API. |
xml-apis.jar | Note: This .jar file contains all standard APIs implemented
by the parser (DOM, SAX, and Java API for XML Processing (JAXP)).
Note: To troubleshoot performance or functional problems, position
this and the xercesImpl.jar file ahead of all other XML parsers in
the classpath.
|
xercesImpl.jar | This .jar file contains all parser class files that implement one of the standard APIs supported by the parser. Both this .jar file and xml-apis.jar must be present in the classpath. Note: To
troubleshoot performance or functional problems, position this .jar
file and the xml-apis.jar file ahead of all other XML parsers in the
classpath. Otherwise, they can appear anywhere in the classpath.
|
soap.jar | The SOAP protocol. |
jakarta-regexp-1.3.jar | The class implementation files for displaying regular expressions used for pattern matching. |
activation.jar | The class implementation files for the JavaBeans Activation Framework standard extension. |
jce1_2_2.jar | The Java Cryptography Extension (JCE) 1.2.2 framework. |
log4j-1.2.8.jar | The LOG4J framework for Content Java API logging. |
mailapi.jar | The JavaMail™ API. This .jar file does not include protocol providers. |
rmsweep.jar | The class implementation files for disposition schedules. |
rmworkflow.jar | The class implementation files for RM workflows. |
rmapiresources.jar | The class implementation files displaying error messages. |
pe.jar,pe3pt.jar,peResources.jar | The class implementation files for the Process Java API. Note: The peResources.jar file is required only for localized
environment.
|
p8cjares.jar | The localizable resource strings for Content Java API classes. |
sunjce_provider.jar | The Sun provider package of the Java Cryptography Extension (JCE). |
The RM Java™ API documentation provides information about commonly-used objects and methods, and includes code examples. You can also refer to the Javadoc files for more information about each interface and class. For this, you need to open the interfacename.html file. For example, you can open the ClassificationScheme.html file for more information about the ClassificationScheme class.
The RM Java API documentation includes information about the following topics:
The RM Java™ API defines various interfaces, such as RMObject, RMObjectStore, RMFolder, and RMRecord, to leverage the existing functionality of the Content Java API.
For more information about RM Java API base objects, refer to Getting started.
Using the RM Java™ API, you can create a file plan hierarchy according to the business processes of your organization. To create a file plan, the RM Java API provides various classes and interfaces such as RMObjectStore, RMObject, ClassificationScheme, RecordCategory, RecordFolder, Volume, RMProperty, RMType, and RMUtil. You can also use the RM Java API to browse a file plan and view its constituents.
For more information about a file plan, refer to Creating a file plan.
The RM Java™ API provides a framework for declaring one or more documents or multiple versions of a document as a single record. You can declare a record using classes and interfaces such as RMObjectStore, RMObject, RecordInfo, RMRecordContainer, RMAutoName, RMDriverManager, DocumentStore, RMProperty, and RMType.
For more information about records, refer to Managing records according to business processes.
The RM Java™ API provides the ability to define, allocate, and execute a disposition schedule. You can define disposal actions such as export, transfer, destroy, and interim transfer. To perform these actions, the RM Java API provides classes and interfaces such as RMObjectStore, RMObject, DisposableObject, RecordCategory, RecordFolder, Volume, RecordInfo, and RMUtil.
For more information about disposition schedules, refer to Initiating a disposition schedule.
Using the RM Java™ API, you can search objects across one or more object stores. For example, you can search and retrieve record categories, record folders, and records. To do so, you use RM Java API classes and interfaces such as RMObjectStore, RMSearch, RMStoredSearch, RMStoredSearches, RMUtil, and RMXSLUtil.
For more information about search, refer to Performing the search operation.
Using the RM Java™ API, you can perform various bulk operations (such as close/open, inactivate/activate, and relocate) to update multiple objects in the same way and at the same time.
For more information, refer to Performing bulk operations.