Skip to main content
Version: 4.46.0

FileNet Information

FileNet is an enterprise content management (ECM) platform developed by IBM. FileNet provides a comprehensive set of ECM capabilities, including document management, workflow automation, records management, image management, and compliance solutions. It is designed to help organizations capture, store, manage, and distribute various types of content across the enterprise..

System Specifications and Terminology​

Here are some key FileNet terminology and concepts.

Object store​

An object store refers to a logical storage container where content and associated metadata are stored. It serves as the repository for documents, images, multimedia files, and other types of content managed by the FileNet system

Folder​

Folders are organizational units within the FileNet repository used to group related documents and other content. They provide a hierarchical structure for organizing and accessing content.

Document​

A document is a digital representation of a file or piece of content that is stored within the FileNet repository. Documents can include various types of files such as text documents, spreadsheets, images and videos. When a document is uploaded or created in FileNet and has not yet been filed into a specific folder or location, it is considered unfiled.

Annotation​

An annotation typically refers to a textual or graphical note or mark added to a document or image to provide additional information or context. Annotations can be used for various purposes, such as highlighting important points, adding comments or explanations, marking up documents for review or approval, or drawing attention to specific areas within an image. Both documents and folders can be annotated.

Content element​

Content elements represent the individual pieces of content stored within the FileNet repository, such as documents, images, videos, and other multimedia files. Folders, documents and annotations can have 0 or more content elements.

Custom object​

A custom object refers to a user-defined data structure that extends the capabilities of the FileNet content repository beyond the default content types provided by the platform. Unlike standard content objects like documents and folders, which have predefined structures and properties, custom objects allow organizations to define their own data models and metadata schemas to suit their specific business needs.

FileNet APIs​

SOAP API​

FileNet offers a SOAP-based API (Simple Object Access Protocol) for interacting with its content management system. This API, often referred to as the FileNet Content Engine SOAP API, provides a way for developers to programmatically access and manipulate content, folders, metadata, workflows, and other aspects of the FileNet repository.

Content Engine API​

The Content Engine API allows developers to programmatically interact with content stored in the FileNet repository. It provides methods for creating, retrieving, updating, and deleting documents, folders, metadata, and other content objects. The Content Engine API is typically used for building custom applications, integrating with other systems, and automating content management tasks.

System Limitations​

Invalid Characters​

The following characters are considered invalid and cannot be used in object names in FileNet:

  • \ (backslash)
  • / (forward slash)
  • : (colon)
  • * (asterisk)
  • ? (question mark)
  • " (double quotation marks)
  • < (less than)
  • > (greater than)
  • | (pipe)

Migration Pitfalls​

The migration pitfalls are related to the FileNet features.

Case Sensitivity​

FileNet is case-sensitive when it comes to folder and file names. This means that you can have multiple folders or files with the same name but with different casing, "Document.docx" and "document.docx" for example. When migrating from FileNet to a system that does not support this, use the community accelerators to deduplicate folder and file names within the same folder.

Invalid file or folder names​

Use the community accelerators to clean up the folder and file names of characters that are not allowed.

Versions and content elements with different extensions​

FileNet allows for file versions and its associated content elements to have different extensions. When migrating to a system that does not support this, this will have to be dealt with.

Content with multiple parents​

Content in FileNet can be found in multiple locations with the same identifier. As a result when crawling these locations, the document will be found multiple times. Check if such documents exist in the Content Store (multiple parentIds) after the extraction and deal with those accordingly in the migration.