10
Using Content Integration Suite CIS 10-1
10
Using Content Integration Suite CIS
This chapter describes how to use the Content Integration Suite CIS, which offers access to Oracle Content Server by exposing its services and data in a unified object
model. The Universal Content and Process Management UCPM API is modeled into a set of services APIs, which are API calls that communicate with the target server, and
the returned value objects from the server.
This chapter includes the following sections:
■
Section 10.1, CIS Architecture
■
Section 10.2, Access Through the UCPM API
■
Section 10.3, UCPM API Methodology
■
Section 10.4, CIS Initialization
■
Section 10.5, Integration in a Web Environment
■
Section 10.6, Class Loading
■
Section 10.7, Object Creation
■
Section 10.8, Interaction with the UCPM API
■
Section 10.9, IContext Interface
■
Section 10.10, ICISObject Interface
■
Section 10.11, Adapter Configuration File
■
Section 10.12, Access to the SCS API
■
Section 10.13, SCS API Objects
■
Section 10.14, SCS API Servlets
■
Section 10.15, SCS APIs
10.1 CIS Architecture
CIS 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.
CIS uses the Universal Content and Process Management UCPM API, which uses the SCS API for communication to Oracle Content Server. The SCS API wraps
communication from Oracle Content Server into an object model that allows access to the individual object metadata.
10-2 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management
The UCPM API enables application developers to focus on presentation issues rather than being concerned with how to access Oracle Content Server services
IdcCommand services. It comprises a set of command objects which encapsulate distinct actions that are passed to the UCPM API and then mapped to Oracle Content
Server. These commands include common content management functions such as search, check-out, 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 leverages the features in
the environment, whether this is a J2EE application server or non-J2EE server.
The UCPM API encapsulates Oracle Content Server business logic and validates the parameters of the incoming calls. It also handles communication with Oracle Content
Server, encapsulates socket communication logic opening, validating, and streaming bits through the socket, and provides a strongly typed API to the available services.
Internationalization and Character Encoding Oracle recommends that encoding for CIS should be set to the same encoding as the
Java Virtual Machine running Oracle Content Server. However, if CIS is communicating with multiple Oracle Content Server instances in different languages,
then the ISCSContext.setEncoding method can be used to set the encoding to match that of the JVM running CIS.
Deprecated FixedAPI The Fixed API available in CIS releases before for communication with the Image
Server has been deprecated. Calling getFixedAPI throws an error.
10.2 Access Through the UCPM API
