24.1

OpenText InPlace Connector

Introduction

The OpenText InPlace importer takes the objects processed in migration-center and imports them back in an OpenText repository. OpenText InPlace importer works together only with OpenText scanner.

OpenText InPlace adaptor supports a limited amount of OpenText features, specifically changing documents categories and category attributes.

Supported Versions

OpenText InPlace is compatible with the version 10.5, 16.0, 16.4 and 20.2 of OpenText Content Server.

It does requires Content Web Services to be installed on the Content Server. In case of setting classifications to the imported files or folders the Classification Webservice must be installed on the Content Server. For supporting Record Management Classifications the Record Management Webservice is required.

Importer Configuration

To create a new OpenText InPlace Importer job specify the respective adapter type in the importer’s Properties window – from the list of available connectors, “OpenText InPlace” must be selected. Once the adapter type has been selected, the Parameters list will be populated with the parameters specific to the selected adapter type, in this case, OpenText InPlace.

The Properties window of an importer can be accessed by double-clicking an importer in the list, by selecting the Properties button from the toolbar or from the context menu.

Importer parameters

The common adaptor parameters are described in Common Parameters.

The configuration parameters available for the OTCS InPlace importer are described below:

  • username* User name for connecting to the target repository. A user account with super user privileges must be used to support the full OpenText functionality offered by migration-center.

  • password* The user’s password.

  • authenticationMode* The OpenText Content Server authentication mode. Valid values are: CWS for regular Content Server authentication RCS for authentication of OpenText Runtime and Core Services RCSCAP for authentication via Common Authentication Protocol over Runtime and Core Services Note: If this version of OpenText Content Server Import Adaptor is used together with together with “Extended ECM for SAP Solutions”, then ‘authenticationmode’ has to be set to “RCS”, since OpenText Content Server together with “Extended ECM for SAP Solutions” is deployed under “Runtime and Core Services”. For details of the individual authentication mechanisms and scenarios provided by OpenText, see appropriate documentation at OpenText KnowledgeCenter.

  • webserviceURL* The URL to the Authentication service of the “les-services”: Ex: http://server:port/les-services/services/Authentication

  • rootFolder* The id of node under the documents will be imported. Ex. 2000

  • overwriteExistingCategories When checked the attributes of the existing category will be overwritten with the specified values. If not checked, the existing categories will be deleted before the specified categories will be added.

  • numberOfThreads The number threads that will be used for importing objects. Maximum allowed is 20.

  • loggingLevel* See Common Parameters.

Parameters marked with an asterisk (*) are mandatory.

Categories

OpenText InPlace importer allows assigning categories to the imported documents and folders. A category is handled internally by migration center client as target object type and therefore the categories has to be defined in the migration-center client in the object types window ( <Manage> <Object types> ).

Since multiple categories with the same name can exist in an OpenText repository the category name must be always followed by its internal id. Ex: BankCustomer-44632.

The sets defined in the OpenText categories are supported by migration-center. The set attributes will be defined within the corresponding object type using the pattern <Set Name>#<Attribute Name>. The importer will recognize the attributes containing the separator “#” to be attributes belonging to the named Set and it will import them accordingly.

Only the categories specified in the system rules “target_type” will be assigned to the imported objects.

For setting the category attributes the rules must be associated with the category attributes in the migration set’s |Associations| tab.

Since version 3.2.9 table key lookup attributes are supported in the categories. This attributes should be defined in migration-center in the same way the other attributes for categories are defined. Supported type of table key lookup attributes are Varchar, Number and Date. The only limitation is that Date type attributes should be of type String in the migration-center Object types.

Overwriting existing categories

If the importer parameter overwriteExistingCategories is checked, only the specified category and category attributes associated in the migset will be updated when importing, leaving the rest of the categories the same as they were before the import.

If left unchecked, the categories and category attributes associated in the migset will be updated but any unspecified category in the migset will be removed from the document.