What's new

Learn what's new in this release.

Monitoring IBM FileNet P8

Support for integration with standalone IBM Business Automation Insights

As for IBM Cloud Pak® for Business Automation, IBM® FileNet® P8 now supports integration with standalone deployments of Business Automation Insights. It is supported for containerized and traditional deployments on WebSphere® Application Server, and gives you the possibility to collect, analyze, and categorize certain events.

New information Learn more ... containerized deployments, traditional WAS deployments

Content and Workflow server trace configuration in the administration console

You can use the Administration Console for Content Platform Engine (ACCE) to configure server trace logging output for both the IBM FileNet Process Engine and the Content Platform Engine. Now you can:

  • Set the location of the trace log file for the Content and Workflow servers, the file size before rolling over to a new log file, and number of log files to keep.
    You no longer need to use the JVM options to configure these trace logs, and now new configurations activate without restarting the servers.
  • Enable Content server trace logging for selected subsystem thread types.
    This means you can activate logging just for the subsystems that you want to investigate.
  • Enable Workflow server trace logging for selected trace options.
    You no longer need to use VWTool from the command line, and new configurations activate without restarting the servers.

New information Learn more...

Content retrieval and storage infrastructure

Better search and indexing performance with Elasticsearch and OpenSearch services

You now have better control over indexing when you use Elasticsearch and OpenSearch services for text searches. You can use the Elasticsearch settings to determine the number of shards, replicas, and, maximum results window. New information Learn more...

Specify a storage class for an S3 storage device with a JVM parameter

AWS S3 does not have a bucket default storage class, if no storage class header is set at the upload time, the standard storage class is used. If you do not want to use the standard class you can specify your own, non-standard, storage class.

To set a storage class for an S3 advanced storage device or fixed content device, you set the JVM configuration parameter Content.S3.StorageClass.Value to the storage class you want to use. New informationLearn more... S3 advanced storage device, S3 fixed content device

Move a document with expired retention to a S3 (AWS or ICOS) fixed content storage device

You can now move a document with an expired retention date into an AWS S3 fixed content storage area or an ICOS fixed content storage area, in aligned mode.

For AWS S3 fixed content storage, the S3 bucket must have no default retention set or have a default retention set and the minimum allowed retention to be 0. For ICOS fixed content storage area, the ICOS vault (bucket) must have a minimum retention set to 0.

Traditional deployments

SCIM directory support for WebSphere Application Server

For traditional deployments on WebSphere Application Server, you can now manage your identity data centrally with a SCIM directory.

The SCIM directory has been qualified to work with RedHat Keycloak using a third-party SCIM server plugin (see https://scim-for-keycloak.de/). This integration enables SCIM support with identity providers that can be integrated with Keycloak such as Okta and Entra ID (Azure AD).

Note:

IBM FileNet P8 does not support SCIM for deployments on WebLogic.

New information Learn more...

(V5.6 IF002 and later) Support for Windows authentication with Microsoft SQL Server on Configuration Manager
You can configure the Content Platform Engine GCD and object store to connect to the Microsoft SQL Server data source by using Windows authentication. New information Learn more...
(V5.6 IF002 and later) Support for PostgreSQL data source on Configuration Manager
For traditional WebSphere Application Server deployments, you can configure the Content Platform Engine GCD and object store to connect with a PostgreSQL database by using either an SSL or non-SSL based connection. New information Learn more...

Container deployments

Transport Layer Security (TLS) 1.3 support for internal and outbound communication

Network traffic is encrypted by default. In earlier versions, encryption used TLS 1.2. In this release, most internal communication now defaults to the more modern and secure TLS 1.3 version. The same is true for outbound communication, for example to databases or Content Platform Engine APIs that are used by customized applications.

TLS 1.3 support is available in the following databases:
  • Microsoft SQL Server (MS SQL)
  • Db2®
  • PostgreSQL
Restriction: Oracle does not support TLS 1.3.
New optional components: IBM Enterprise Records and IBM Content Collector for SAP Applications

When you install and configure IBM FileNet P8 in a containerized deployment, you can now optionally include IBM Enterprise Records and IBM Content Collector for SAP Applications in your deployment. New information Learn more ...

Scripts to facilitate deployment and upgrade

A number of scripts have been introduced in this release that guide you through the steps of common operator tasks: load images, deploy an operator, upgrade an operator, and clean-up a deployment and operator. New information Learn more deployment, load images, clean deployment, upgrade operator, upgrade deployment, and must gather

Improvements to the prerequisites script

The prerequisites script has been improved to extend support for Process Engine workflow, IBM Enterprise Records, and IBM Content Collector for SAP Applications. New information Learn more ...

Security

Restrict access to the Administration Console for Content Platform Engine to administrators

You can enable the new JVM flag com.filenet.acce.AdminOnlyMode to limit access to the administration console to GCD administrators.New information Learn more...

Framework for content validation

A new framework is available for validating content. The framework provides an interface that allows you to write a provider that validates content before ingesting it into the IBM FileNet P8 system. A common use case would be to write a provider that integrates with a security vulnerability scanner so that checks content before it is ingested. A reference provider implementation with the ClamAV vulnerability scanner is included. New information Learn more...

Create SSL connections for Microsoft SQL Server on WebSphere Application Server using the Configuration Manager

You can now create SSL connections for Microsoft SQL Server on WebSphere Application Server using the Content Platform Engine Configuration Manager, which allows you to create secure connections to GCD and object store databases that use Microsoft SQL Server.New information Learn more...

API Enhancements

IBM FileNet Content Services Deployment API: an API for handling data definitions

There is now a Python API to help you import and export data definitions, which helps you to setup additional environments faster and more consistently, by copying the assets from a known working deployment to a new target deployment.

You can now deploy content metadata (such as ClassDefinitions, PropertyTemplates, ChoiceLists, and their dependent objects) by exporting from a source environment and importing to a target environment.New information Learn more...

Schema for Content Services GraphQL API published on GitHub

You can import the schema for Content Services GraphQL API into your preferred development environment. To get the schema go to https://github.com/ibm-ecm/ibm-content-platform-engine-samples/tree/master/CS-GraphQL-Schema. New information Learn more...

Simplified deployment of Content Services GraphQL API

The Content Services GraphQL API is now packaged as a separate, standalone ZIP file, that includes a simplified deployment tool that you run from the command line. It is no longer installed using the client installer.

To install the Configuration and Deployment Tool for the Content Services GraphQL API you run a command line tool (configmgr_cl) included in the package for the GraphQL API. New information Learn more...

Content Services GraphQL API improvements for managing large content

The performance of Content Services GraphQL API when you upload and download large amounts of content has improved. For example, you can manage the streaming of large uploads with predefined parts, and you can divide large downloads into chunks to avoid connection time-out errors. New information Learn more...

Content Engine Java API performance improvements for downloading large content

You can improve the performance of downloads by using the ParallelContentStream class in the Content Engine Java API for multi-threaded downloads. New information Learn more...