The IBM® Content Cortex
family
of products provides an extensive collection of development and integration
tools. This section briefly describes these tools and provides links
to more information about them.
Content Services GraphQL API
The Content Services GraphQL API provides a schema and an easy-to-understand query language system that simplifies application development for your Content Platform Engine . The API schema definition of types and fields matches Content Engine Java API object model closely, with necessary and desirable extensions for natural GraphQL developer consumption.
Content Engine Java API
The Java API is an interface-based API that provides access to the full capabilities of Content Engine . The Java API can be configured to run across either the Enterprise Java Beans (EJB) or Web Services Interoperability (WSI) protocols. When running across the EJB listener, the Java API leverages the full capability of the Java 2 Enterprise Edition (J2EE) framework to propagate security and transaction context. The Java API also leverages a Java Authentication and Authorization Service (JAAS) context, if available.
Content Engine .NET API
The .NET API (which is functionally equivalent to the Java API) provides a Microsoft .NET Common Language Runtime (CLR)-compliant API for accessing the full capability of Content Engine . The API accepts username and password credentials for authentication. The .NET API works only with the WSI Listener.
Content Platform Engine Client Download Service Java API
The Content Platform Engine Client Download Service enables you to build version-compatibility checks and automatic updates into Java client applications that use any of the Content Platform Engine APIs. Using the Client Download Service, a client can compare and report on the compatibility between its APIs and the API versions on the Content Platform Engine . If incompatibilities exist, the client can download the latest API components from the server.
Process Java API
The Process Java API provides classes for accessing the workflow definition, administration, configuration, and runtime features of Process Engine . For example, you can use the Process Java API to build a custom step processor, which performs all the operations associated with a step in a workflow.
Process Engine Rest Service
The Process Engine REST Service enables lightweight clients (typically, Javascript/Ajax-based applications) to access Process Engine resources over HTTP, using the HTTP query string format for both request and response data. JavaScript Object Notation (JSON) is used as the data-interchange format.
Web Services
The IBM Content Cortex includes web services for both Content Engine and Process Engine . Both web services are compliant with WS-I Basic Profile 1.0 and WS-Security. Using these web services, you can access most of the same functionality that the Content Engine APIs provide, including all objects and most properties and methods. In addition, you can create and launch workflows as well as perform queue, step, and roster operations. Process Engine also provides process orchestration functionality based on Web Services and workflow standards (BPEL4WS), which you can call from an external client.
Component Integrator
The Component Integrator provides a mechanism for easily interacting with components (such as Java classes) from a workflow. Adapters provide the ability to interact with different types of components from a workflow step. IBM provides a Java and Java Message Service (JMS) adapter for calling Java components and interacting with message queues. You can write custom Java components as well as custom adapters for interacting with other types of components or applications. IBM also provides a Content Engine component (CE_Operations) that includes functions to get and set properties, file and unfile objects from folders, and publish a document.
FileNet System Manager APIs
The System Manager APIs include listener APIs that collect performance data and make the data available, and a manager API for creating client applications that gather the performance data.
Samples
In addition to the samples provided with the various toolkits and APIs, sample code also is available for download.