The URI for FileNet P8 client applications to communicate with Content Engine is incorrectly documented

Release notes


Abstract

The FileNet P8 Information Center incorrectly documents a prefix token in the sample URIs that FileNet P8 client applications can use to communicate with Content Engine.

Content

In the FileNet P8 Information Center topic Content Engine in an application server cluster by using EJB transport, the sample URIs that illustrate how a FileNet P8 client application can communicate with Content Engine contain cemp: as a prefix token. In most cases, this prefix token must be omitted from the URIs.

For example, in the "WebSphere Application Server" section of the topic, omit cemp: from the URI:

cemp:corbaloc::testnode1:9810,:testnode2:9810/cell/clusters/
testwascluster/FileNet/Engine

That is, use the following URI instead:

corbaloc::testnode1:9810,:testnode2:9810/cell/clusters/testwascluster/FileNet/Engine

Omit the prefix token cemp: from the sample URIs in the "Oracle WebLogic Server" and "JBoss Application Server" sections of the topic as well.

Also, replace the "Restriction" paragraph in the topic with the following paragraph:

Restriction: In some older client applications, such as Workplace and Workplace XT, you must retain the cemp: prefix token at the beginning of the URL. Consult the application documentation to determine whether the cemp: prefix is required.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

FileNet Content Manager
Content Engine

Software version:

5.1.0, 5.2.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

7036995

Modified date:

2013-06-24

Translate my page

Machine Translation

Content navigation