Overview
The Content Engine APIs consist of logical architectural subcomponents that are based on Java™ and Microsoft .NET and the transport between their subcomponents. The API sets provide common functionality for both Java and .NET application development. You can build your own Java applications and applets by using the Java client API, which provides classes for creating, accessing, and manipulating content and objects. The set of .NET framework classes allows high-level access to Content Engine objects through .NET languages such as C#. Using either API, you can develop and customize your applications.
The components are platform neutral and generally provide a thin
wrapping around remote procedure calls. They perform the marshalling
and unmarshalling of parameters for serialization and deserialization.
For specific objects, they can also provide limited, transparent caching
of object property values. The API also provides a Connection object,
which transparently handles authentication and through which batch
operations are performed.
The Content Engine Java API is compatible with Enterprise JavaBeans (EJB) 2.0. For more information, refer to the EJB 2.0 specification. The Content Engine .NET API is compatible with the Microsoft .NET Framework 3.0. For more information about the .NET Framework, refer to your Microsoft documentation.
The Content Engine Java and .NET APIs are installed during Content Engine installation. You can install the API files anywhere, including a non-Content Engine system. The Microsoft .NET Framework and its built-in Windows Communication Foundation (WCF) component is a prerequisite to developing applications by using the Content Engine .NET API. WCF supersedes Web Services Enhancements (WSE) 3.0. WSE support is deprecated and support will be discontinued in a future release. For this reason, the continued use of WSE is discouraged. Refer to IBM® FileNet P8 Hardware and Software Requirements for the latest version requirements of the .NET Framework components.
The Content Engine API documentation includes Java reference documentation, .NET reference documentation, and the Developer's Guide. The Developer's Guide provides conceptual information about some of the most commonly used objects and code snippets in the Working with chapters.
com.filenet.api.
The exposed classes and interfaces in the .NET API are in subnamespaces
of FileNet.Api. Do not use the internal, non-exposed
classes and interfaces, that is, classes and interfaces that are marked
in the reference help as internal use only, and those not documented
in the API reference help. In particular, do not use any classes or
interfaces in Java subpackages
of com.filenet.apiimpl or .NET subnamespaces of FileNet.Apiimpl.
Non-exposed classes and interfaces are subject to change at any time
and without notice; their use is not supported.Release Notes
The Content Manager Release Notes topic contains important information about this release. You can access the release notes from the FileNet P8 Welcome page in IBM Knowledge Center.
Sample code
Sample code for Content Engine Java and .NET development is available from the IBM FileNet P8 Platform publication library . The samples are provided as guidelines for your development effort. IBM policies regarding support and compatibility with earlier versions do not apply to sample code. IBM reserves the right to alter sample code at any time. Also, see "COPYRIGHT LICENSE " in the Notices topic.