Content Integration Suite- Itegrating with Webcenter Content

By | May 26, 2013 | 0 Comment

CIS or Content Integration Suite is a set of APIs that help the users to access the content server services. Through these APIs, the user can actually fetch the UCM services like document check in, workflow, search, full text search etc in a custom application and deploy it in any J2EE compatible container.


The CIS API connects to the content server through the Universal Content and Process Management APIs which in turn communicate to it through the SCS APIs. So the UCPM API wraps the content services and data in a unified object model that is accessed by the SCS API through its classes.


To use CIS, you need to configure adapter in your application. The adapter settings are stored in adapterconfig.xml in your application. You need to specify the following tags in the adapterconfig.xml


  • Name: This specifies the name of the adapter to be used to connect.
  • Adapter Type: This specifies the type of connection to be established. Like in case of RIDC, it is a socket connection. CIS provides the following options:


  • Socket:  A socket connection is established when you trust the connection source. It establishes a direct connection with the content server. The port used to establish a content server is 4444. It requires authentication only at the first call. Hence, it does not prompt you for user credentials at every call.


  • Web: Connection over the web require authentication at every call made to the server. So you connect to the content server through the Sysadmin user which is supposed to be the super user for content server.


  • Host: The IP address of the content server you are trying to connect to.
  • Port: The port through which you connect to the content server.


At the content server end, to make it compatible for communication through CIS connection, we need to enable the CIS_Helper component in the content server. This component needs to be explicitly installed before it is enabled. Moreover, we need to ensure that our application server IP address is included in the UCM security filter.


To allow the IP address, follow the steps below:


  1. Go to Server Administration -> System Properties.
  2. Then select Contact Server and the name of your content server instance.
  3. Go to Utilities -> System Properties and Select Server.
  4. Enter your IP address in the IP Address Filter. Example: 127.90.76.* | 10.42.65.*
  5. Restart the content server to reflect the changes.

To install and enable the CIS_HELPER component, once you download the component as the zip file, follow the steps below:


  1. Go to Administration -> Admin Server.
  2. Click on the server instance name. On the page that opens, click Component Manager in the menu on the left.
  3. The Component Manager page opens. Click Browse next to the Install New Components Field. A file selection dialog opens.
  4. Select file. Click Install. A page appears confirming the component to be installed.
  5. Click Continue. Once the confirmation message appears confirming the successful installation, click Continue.
  6. Now, check the box against this component to enable it.
  7. Restart the server to reflect the changes.




The UCPM API uses the ICISApplication class to gain a reference to the IUCPMAPI Object. The class offers a getUCPMAPI() method to access the object. Since the UCPM API in turn uses the SCS APIs, we take reference to the SCS API using the getActiveAPI() method. The SCS API then acquires the content server services and exposes them to the end user.


SCSActiveAPI activeAPI = m_cisApplication.getUCPMAPI ().getActiveAPI ();


As discussed earlier about creation of adapter in adapterconfig.xml. The sameis then called through code. We initialise CIS using the CISApplicationFactory inside the com.stellant.cis.impl package. This initialization happens only once since we typically connect through the socket. We first set the following properties as it is as shown below and then read the other details defined in the adapterconfig.xml as under:


ICISApplication application;

URL xmlRes = new File (“adapterconfig.xml”).toURL()

Properties properties = new Properties();

properties.setProperty(ICISApplication.PROPERTY_CONFIG_TYPE, “server”);

properties.setProperty(ICISApplication.PROPERTY_CONFIG_SERVER_ADAPTER_CONFIG, xmlRes.toExternalForm());

properties.setProperty(ICISApplication.PROPERTY_CONFIG_SERVER_TYPE, “standalone”);

application = CISApplicationFactory.initialize(properties);


After the CIS instance has been initialize, we call the SCSInitializeServlet to initialize the CISApplication from within our web, typically a J2EE, application. To call the SCSInitializeServlet, the following configuration is required in the deployment descriptor, web.xml:


<servlet id=”scsInitialize”>


<display-name>SCS Initialize Servlet</display-name>







Leave a Reply

Your email address will not be published. Required fields are marked *