Skip to main content
Version: 4.61.0

FileNet Hybrid source connector

The FileNet Hybrid connector uses a FileNet proxy to connect to the FileNet web services, as well as a direct connection to the database. Currently, only Db2 and MSSQL are supported. This hybrid approach is used to gain the best balance between performance and functionality.

To setup the FileNet proxy, please contact your Xillio representative.

Supported Features​

  • Exporting content structure (folders, documents and custom objects)
  • Downloading binaries*
  • Exporting versions
  • Exporting annotations
  • Exporting tasks
  • Exporting users and groups
note

*Downloading binaries is not available for annotations on custom objects due to limitations in the FileNet proxy.

note

When exporting users and groups, principal objects for principals that occur in the records and containers as source.created.principal or source.lastModified.principal will be created, a mapping sheet for updating these principals with emails is required in the Transformation (3b. Principal Mapping) accelerator.

Features Currently Not Supported​

  • Relationships (linked objects)
  • Access control lists
  • Records management metadata
  • Audit logs
  • Workflows

Settings​

mongoConnection​

The Mongo connection string including the database name to connect to.

fileNetDBConnectionString​

The connection string to the FileNet database.

Example: db2://USERNAME:PASSWORD@filenet.yourcompany.com:50000/OS_DB

fileNetDBEngine​

The engine of the FileNet database. Currently, only Db2 and MSSQL are supported.

fileNetDBOwner​

The owner of the FileNet database schema. Each object store in FileNet has its own database schema.

fileNetUrl​

The URL of the FileNet web service. Example: http://filenet.yourcompany.com/wsi/FNCEWS40MTOM

fileNetUsername​

The username to use for the FileNet web service.

fileNetPassword​

The password to use for the FileNet web service.

fileNetProxyUrl​

The URL of the proxy server to use for the FileNet web service. Example: http://localhost:8081

fileNetObjectStore​

The name of the FileNet object store.

fileNetStanza​

The stanza to use for the FileNet web service. Example: FileNetP8WSI

exportPath​

The path to export the content to. Example: C:/xill4/filenet. Note that this path must exist. If left empty, binaries will not be retrieved.

retrieveAnnotations​

Enables retrieving all annotations of an FileNet object. Can either be true or false.

retrieveTasks​

Enables retrieving all tasks of an FileNet object. Can either be true or false.

retrieveUnfiledDocuments​

Enables retrieving all unfiled documents. Can either be true or false.

rootIds​

A list of comma-separated object ids.

Example: ["1F1F2D3C-4B5A-6978-8796-A5B4C3D2E1F1", "2F1F2D3C-4B5A-6978-8796-A5B4C3D2E1F2"]

discardMetadata​

Cleans the source.properties object for all stored objects by removing default extracted metadata and unused properties.

Only a minimal set of metadata fields required by schemas and processing logic is retained.

Retained metadata per object type

Containers​

Only custom metadata properties are retained.

Records​

For documents ("migration.flags.fileNetType" : "DocVersion") the properties in source.properties is reduced to:

["filenet.RNAME"]

Furthermore, all custom metadata properties on documents are retained.

For custom objects ("migration.flags.fileNetType" : "Generic") and annotations ("migration.flags.fileNetType" : "Annotation") only custom metadata properties are retained.

For tasks ("migration.flags.fileNetType" : "Task") the properties in source.properties is reduced to:

["filenet.STATE", "filenet.COORDINATOR_ID", "filenet.START_DATE", "filenet.COMPLETE_DATE", "filenet.LAST_FAILURE_DESC"]

Furthermore, all custom metadata properties on tasks are retained.

Binaries​

For binaries the properties in source.properties is reduced to:

["ContentType"]

origin​

Specifies the origin of the document in the Content Store.