CIS Architecture

Content Integration Suite has a layered architecture that allows for its deployment in a number of different configurations. The architecture, at its core, is based on the standard J2EE Command Design Pattern. The layers on top of the commands provide the APIs that are exposed to the end user.

This version of CIS uses the Universal Content and Process Management API (UCPM API) which uses the SCS API for communication to the content server. The SCS API wraps communication from the content server into an object model that allows access to the individual object metadata.

The UCPM API allows application developers to focus on presentation issues rather than being concerned with how to access content server services (IdcCommand services). The UCPM API comprises a set of command objects that encapsulate distinct actions that are passed to the UCPM API and then mapped to the content server. These commands include common functions such as search, checkout, and workflow approval. Each command is tied to one or more service calls. The UCPM API command objects have been developed in accordance with the J2EE Command Design Pattern.

This infrastructure is deployable in any J2EE-compliant application server or stand-alone JVM application. When deployed, the UCPM API will leverage the features in the environment, whether this is a J2EE application server or non-J2EE.

The UCPM API encapsulates content server business logic and validates the parameters of the incoming calls. The UCPM API handles communication to the content server, encapsulates socket communication logic (opening, validating, and streaming bits through the socket), and provides a strongly typed API to the available services.