Limitations in administering the IBM BPM document store

There are some limitations in administering the IBM BPM document store. In most situations, you can successfully work around these limitations.

Some known limitations of the IBM BPM document store are:

The document store is not available for IBM BPM for z/OS
The document store is not available for an IBM BPM installation that uses IBM DB2 for z/OS as its database
The document store is only available when Federated Repositories is used as the user registry
An exception may be thrown during document store logging and tracing operations

These limitations are described in the following sections.

Although the IBM BPM document store is not available in these situations, you can continue to work with your document attachments in the IBM BPM database or you can configure an external ECM system for storing your documents. In either situation, the legacy document APIs will continue to be used. Any ECM operations that specify the IBM BPM document store as a server will fail.

The document store is not available for IBM BPM for z/OS

The IBM BPM document store is not available for use with IBM Business Process Manager for z/OS.

The document store is not available for an IBM BPM installation that uses IBM DB2 for z/OS as its database

The IBM BPM document store is not available for use with an IBM Business Process Manager installation that uses IBM DB2 for z/OS as its database.

The document store is only available when Federated Repositories is used as the user registry

The IBM BPM document store is only available when Business Process Manager is configured to use Federated Repositories as the user registry. If you are using a different user registry configuration, you should disable the autostart mechanism of the IBM_BPM_DocumentStore application.

To use the IBM BPM document store with your LDAP users and groups, configure LDAP as a repository in Federated Repositories instead of using stand-alone LDAP as the user registry. Additional information is found in the topic "Configuring external security providers."

An exception may be thrown during document store logging and tracing operations

When the server is started or the IBM BPM document store commands maintainDocumentStoreTrace or updateDocumentStoreApp are run, the following SystemErr exception may be logged:

[3/19/13 23:31:12:548 PDT] 00000084 SystemErr     R log4j:WARN No appenders could be found for logger (filenet_error.api.com.filenet.apiimpl.util.ConfigValueLookup).
[3/19/13 23:31:12:548 PDT] 00000084 SystemErr     R log4j:WARN Please initialize the log4j system properly.
[3/19/13 23:31:14:482 PDT] 00000084 SystemErr     R log4j:WARN Configuring default logging to the file E:\IBM\WebSphere\AppServer\profiles\Custom01\FileNet\
testDE1.AppCluster.WIN-E6GDL89KDJDNode01.0\p8_server_error.log
[3/19/13 23:31:49:536 PDT] 00000084 SystemErr     R log4j:WARN No appenders could be found for logger (filenet_error.api.com.filenet.apiimpl.util.ConfigValueLookup).
[3/19/13 23:31:49:536 PDT] 00000084 SystemErr     R log4j:WARN Please initialize the log4j system properly.
[3/19/13 23:33:25:867 PDT] 00000108 SystemErr     R SLF4J: Class path contains multiple SLF4J bindings.

The exception is caused by the tracing and logging mechanism that is used with the IBM BPM document store. The exception does not result in any operational problems and can be safely ignored.