Posted Jul 24 by Karen Rudnitski.

This article shows how to configure various Document Store options for Process Platform (AppWorks Platform).

213 views. 0 comments.

Introduction

The following fields are present in the Store Details area of the Configuration page.

Field Description
StoreType Type of server. Select one of the following:
  • Process Platform Repository
  • OpenText Content Server (OTCS)
  • OpenText Archive Center
  • Jackrabbit
  • CMIS
  • OpenText Core
  • Others (use this option to use any other repository for managing documents)
StoreName Type a name for the repository configuration.
Brava Server URL Optional. Type the Brava Server URL to use for viewing documents stored in the repository, for example, http://server:port.

Note: If you configure the Brava Server URL, then in Process Experience after you open an entity instance the Open In Viewer tab displays in the business workspace, business attachment, and contents panels. Upload a document, select it and click Open In Viewer. The document opens in Brava viewer.

Depending on the selected store type, different fields display in the Repository Configuration Details area. These fields are explained below.

Explanation

Process Platform Repository

The following fields display in the Repository Configuration Details - XDS area when you select the Process Platform Repository option:

Field Description
Database configuration Select the database configuration.

Note: The Cordys System option contains the database configuration information that was provided when installing Process Platform.
Repository root Optional repository root folder of the document.


OpenText Content Server (OTCS)

To use OTCS as the document store:

Before you begin:

  • Ensure that OpenText Content Server is installed on your computer and you have administrator privileges to connect to Content Server.
  • Add the Process Platform resource and Content Server resource.

The following fields display in the OpenText Content Server Configuration Details area when you select the OpenText Content Server option:

OTDS Details

Section Description
OpenText Content Server Resource OTDS resource created for Content Server using Managing OTDS Resources.

External Systems

Content Server Details

Field Description
End Point URL HTTP URL, which serves as a base URL to connect to all the Web service operations of OTCS.

For example: http://machinename:portnumber/cws/services/DocumentManagement
Repository Root

Repository root folder, which serves as the base folder within a given workspace. Optional. If no document root is provided, the workspace is treated as the personal workspace.

Note: In case of xECM, this field value is not considered for business workspace creation.


Extended ECM Configuration

Field Description
External System ID Provide the external system ID of Process Platform as configured in Content Server. To enter a value for this field, navigate to Content Server > Admin page > Extended ECM > Configure Connections to External Systems. Read the external system name entered in the Logical External System Name field and type the value in the External System Id field. After the value is provided in this field, other field values are populated automatically.
Support Path

This field is automatically filled based on the URL provided in the End Point URL, for example: http://machine name provided in the End Point URL:port_no/img. This holds CSS, JavaScript files, and images related to the folder browser widget. This comes with the Content Server UI module.

Note: The /img, also known as the virtual directory alias, is mapped to the support directory during the installation of Content Server. By default, the support directory is located at the root installation level:/installation_path/support. It is normally not necessary to change /img; however, if you modify it, you must make the change in Content Server and the Web server.

The default value for this is /img.

CGI Path

This field is filled automatically based on the URL provided in End Point URL, for example: http://machine name provided in the End Point URL:port_no/URL_prefix/livelink.exe. This is the OTCS business workspaces URL.

  • port_no - Port on which your Web server listens.
  • URL_prefix - URL prefix mapped to the Content_Server_Home/cgi/ folder of the Content Server.
  • livelink.exe is the default value. It can be any contentserver.exe, for example, cs.exe.livelink.exe.

Note: The .exe extension is not used for UNIX/Linux or when Content Server works with an application server.

API Web Service URL This is the WSDL URL to access xECM related Web services that are deployed in OTCS, for example: http://machine name provided in the End Point URL :port_no/otsapxecm/services/ECMLink.
Synchronize Workspaces Manually This option is not selected by default. When entity instances are created in runtime, corresponding business workspace instances are created automatically in Content Server. If this option is selected, a business workspace is not created automatically in Content Server. You must select the record and click Synchronize Workspace in your application to create a business workspace in Content Server.


OpenText Archive Center

To use Archive Center as the document store:

Before you being:

  • Ensure that OpenText Archive Center is installed on your computer and you have administrator privileges to connect to the Archive Server.
  • Add the Process Platform resource and Archive Server resource.

The following fields display in the OpenText Archive Center Configuration Details area when you select the OpenText Archive Center option:

Field Description
OpenText Archive Center Resource OTDS resource created for Archive Center using Managing OTDS Resources.
Binding Type

Select the CMIS binding that must be used. Based on CMIS binding, the Repository URL changes.

Note: To use WebService binding, configure the document store with Apache-CXF.

Repository URL

HTTP URL based on the selected CMIS binding, which serves as a base URL to connect to Archive Center.

Example URLs for various bindings

  • AtomPub: http://archive center server:portnumber/as_cmis/atom
  • WebService: http://archive center server:portnumber/as_cmis/services/cmis?wsdl
  • Browser: http://archive center server:portnumber/as_cmis/browser
Repository ID Unique ID of the repository, which needs to be connected. In Archive Server, this corresponds to the archive name of the collection.
Repository Root

Repository root folder, which serves as the base folder within a given repository denoted by the repository ID.

Optional. If no document root is provided, the default root is considered.

Datasource ID

ID of the data source of type CMIS associated with the collection.

Mandatory for the Archive Center 10.5 cloud edition and later releases.


Jackrabbit

The following fields display in the Repository Configuration Details - Jackrabbit area when you select the Jackrabbit option:

Authentication details

Field Description
User name User name to access the server that stores the document
Password Password to access the server that stores the document

Repository details

Field Description
Repository URL URL of the document within the repository
Repository Root Optional. Repository root folder of the document.


CMIS

The following fields display in the Repository Configuration Details - CMIS area when you select the CMIS option:

Authentication details

Field Description
User name User name to access the server that stores the document
Password Password to access the server that stores the document

Repository details

Field Description
Binding Type

Select the CMIS binding to use. Based on the CMIS binding, the Endpoint Repository URL changes.

Note: To use WebService binding, configure the document store with Apache-CXF

Repository URL

HTTP URL based on selected CMIS binding, which serves as a base URL to connect to the content repository.

Example URLs for various bindings

  • AtomPub: http://archive center server:port number/as_cmis/atom
  • WebService: http://archive center server:port number/as_cmis/services/cmis?wsdl
  • Browser: http://archive center server:port number/as_cmis/browser
Repository ID Unique ID of the repository to be connected
Repository Root Optional. Repository root folder of the document.


OpenText Core

The following fields display in the Repository Configuration Details - OpenText Core area when you select the OpenText Core option:

Authentication details

Field Description
User name User name to access the OpenText Core server
Password Password to access the OpenText Core server
Authentication Handler Name

Type the authentication handler name that is configured in Process Platform OTDS for OpenText Core.

Note: For more information, see the section on Authentication Handlers in the OpenText Directory Services: Installation and Administration Guide

Repository details

Field Description
Binding Type Browser option is selected by default
Repository URL Type the browser URL. For example, http://OpenText Core server:port number/core_cmis_server/browser
Core Base URL Type the OpenText Core URL. For example, http://OpenText Core server:port number
Repository Root Optional. Repository root folder of the document.
Repository ID Unique ID of the repository to be connected


Others

Process Platform provides you with the IDocumentStore interface. Implement this interface to use any repository other than the Process Platform Repository or Jackrabbit.

The code for implementing the IDocumentStore interface is as follows:

public abstract class JSRDocumentStoreClient implements IDocumentStore 
{ 
  public boolean initializeStore(StoreConfiguration configuration) throws DocumentStoreException {} //more methods need to be defined 
} 

public class XDSDocumentStore implements IDocumentStore 
{ 
  //more methods need to be defined 
}

The following fields display in the Repository Configuration Details - Others area when you select the Others option:

Field Description
Implementation Class Name of the class that implements the IDocumentStore interface. For more information about the IDocumentStore class, see the Document Store package in Java documentation.
Classpath Classpath of the class that is implementing the IDocumentStore interface
External Configuration XML

Paste any additional information that is required to access the repository in this field in the XML format. These details are passed to the implementation class. The contents of this field pass to the StoreConfiguration object as displayed in the code above.

The StoreConfiguration object in turn passes to the initialize method of the implementation class. For more information, see the Document Store package in Java documentation.

Repository Root Repository root folder of the document.

Table of Contents

Your comment

To leave a comment, please sign in.