IBM FileNet P8 Content Platform Engine

Product Validation Documentation

ISV: [IBM]

Revision 1.0
Date 03/23/2018
Author Me
Mei-Ling Chang, Shuang Wang
Document History

Revision Date Comments

1.0
2.0 August 22, 2017 Include HCP8.x feature test (Fed Brillantes)

Table of Contents

VALIDATION OUTCOMES ...................................................................................................................... 3

VALIDATION DETAILS............................................................................................................................ 4
VALIDATION LOCATION: ............................................................................................................................ 4
VALIDATION DATES: .................................................................................................................................. 4
VALIDATION TEAM: ................................................................................................................................... 4
PRODUCT RELATIONSHIP ............................................................................................................................ 4
HITACHI CONTENT PLATFORM FIXED CONTENT DEVICE CONFIGURATION PARAMETERS .......................... 5
TESTS RESULTS .......................................................................................................................................... 8
JOINT OPERATION GUIDELINES AND BEST PRACTICES ..............................................................................11
HCP UNIQUE CAPABILITIES UTILIZED ......................................................................................................19
NEXT STEPS...............................................................................................................................................20

Hitachi Vantara Confidential 2

Validation Outcomes
Validation between “IBM FileNet P8 Content Platform Engine (CPE) 5.5.0 and 5.2.1.7”
has been certified against Hitachi Content Platform G10 (HCP) running version [8.0.0] of
the HCP firmware.

Validation took place on [2/23/2018 and 2/28/2018].

The CPE 5.5.0 HCP 8.0 test is deployed on WebSphere 8.5.5.11 running on Windows
2012R2. The IBM FileNet Content Platform Engine uses HCP for content storage
through the Fixed Content Provider feature. Please see the IBM Knowledge Center for
more information:
https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.ce.admin
.tasks.doc/p8pcc093.htm

The CPE 5.2.1.7 for HCP 8.0 test is deployed on WebLogic 12c.13 running on SUSE
Linux 11 SP3.

CPE is developed on JAVA. There is no specific requirement to turn off JAVA’s internal
DNS caching to deploy IBM FileNet P8 Content Platform Engine.

No issue was found during the manual setup or automated regression test.

Hitachi Vantara Confidential 3

Validation Details

Validation Location: IBM SVL Lab

Validation Dates: [2/23/2018-2/2/8/2018]
Validation Team:

Name Role Company

Mei-Ling Chang Function Testing IBM

Product Relationship

The FileNet® P8 family of products includes back-end services, development

tools, and applications that address enterprise content and process management
requirements.

Hitachi Vantara Confidential 4

The Content Platform Engine integrates HCP as an external repository (Fixed
Content Device) through the Fixed Content Provider interface. The fixed content
provider on the Content Platform Engine defines the connection between the
staging area and the HCP Fixed Content Device.

Hitachi Content Platform Fixed Content Device Configuration Parameters

Attribute Name Attribute Value
String
The same value as the HCP Password parameter.
Confirm Password Content Engine uses this parameter and the HCP
Password parameter to confirm that the entered value
is the intended value.
Integer
Default=LARGE
The size of the content storage directory structure
based on the number of directory levels. The
directories at the lowest level store the content. The
Directory Structure number of these content directories equals (23)n where
n is the number of levels as determined by your
selected size:

• SMALL: Two levels

Content is stored in 529 directories.

Hitachi Vantara Confidential 5

 • LARGE: Three levels
Content is stored in 12, 167 directories.

Directories in the directory tree are named FN0 through

FN22 (other than the content root directory).

The directory structure size can be set only when

initially registering the fixed content device with
Content Engine.
Integer
Default=600
FCP Pool Idle Timeout The number of seconds an idle connection can remain
Seconds in the pool before becoming eligible to be closed and
removed from the pool. A value of less than zero for
this parameter is treated as zero.
Integer
Default=200
FCP Pool Max In Use
The maximum number of concurrent connections to
the fixed content device.

Integer
Default=5
The maximum number of seconds to wait for a
FCP Pool Max Wait connection to become available before refusing a
Seconds request for a connection. No connection is available
when the limit on the number of concurrent
connections as specified by the FCP Pool Max In Use
parameter has been reached.

Integer
FCP Pool Preferred Default=5
Size The minimum size for the pool. A value of less than
zero for this parameter is treated as zero.
String
HCP Password The password for the user account. The user account
is specified by the HCP User parameter.
String
The name of the HCP user account that Content
Engine uses to access the HCP namespace. The user
HCP User
account must have read, write, delete, and purge
privileges. The namespace is specified by the
Namespace URL parameter.
Integer
Default=200
Max Connections
The maximum number of concurrent connections to
the fixed content device for the Java virtual machine

Hitachi Vantara Confidential 6

 (JVM). The value of the JVM http.maxConnections
system parameter is set to the value of this parameter.

Typically, you set the value of this parameter in

accordance with the following formula: parameter
value = FCP Pool Max In Use parameter value * the
number of Content Engine registrations for the Hitachi
fixed content device (FCD). For example, suppose that
you create two FCD objects in Content Engine to
represent the Hitachi FCD. For both FCD objects, this
parameter value must be 400 if the FCP Pool Max In
Use value is 200.
String
The HTTP or HTTPS URL to the HCP server
namespace. If an HTTPS URL is specified, the
Namespace URL
transport between Content Engine and HCP is
encrypted via SSL, but HCP server certificates are not
used.
String
Root Directory Path The fully qualified path to the directory tree in the HCP
namespace where content is stored.

Please include this IBM Knowledge Center link for an overview of IBM FileNet P8
Content Platform Engine:
https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.s
ysoverview.doc/p8sov108.htm

Please include this IBM Knowledge Center links for details of CPE and HCP
integration.

Hitachi Fixed Content Device:

https://www.ibm.com/support/knowledgecenter/en/SSGLW6_5.5.0/com.ibm.p8.c
e.admin.tasks.doc/p8pcc093.htm

Fixed Storage Area:

https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.c
e.admin.tasks.doc/p8pcc090.htm

Retention for Hitachi Fixed Storage Area:

https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.c
e.admin.tasks.doc/p8pcb043.htm

Hitachi Vantara Confidential 7

Tests Results

Test Result Comments

[Pass or
Fail]
Write Tests Pass Automated JAVA API regression test
Read Tests Pass Automated JAVA API regression test
Delete Tests Pass Automated JAVA API regression test
Retention Tests Pass Automated JAVA API regression test
Versioning Tests N/A
MetaData Tests N/A
Setup Test Pass HCP setup is done manually using
HCP administration console.
CPE setup of Fixed Content Device
and Fixed storage area setup are
included in automated test.
Availability Tests N/A
MQE Interface N/A
MAPI Interface N/A
Proc Interface N/A
Replication N/A
Geo-Distributed Erasure N/A
Code Test (v8.x)
Multipart Upload Test (v8.x) N/A N/A

a. Write Test - Pass

a.1 Either 529 (two level of 23 folders) or 12767 (three level of 23 folders)
directories are created during HCP FCD creation depends on the FCD's
Directory Structure property.
(See updated page 6 for HCP FCD properties.)
a.2 The HCP 8.0 qualification test does not include the large content test.
Large content test for Fixed Content Device in general has been validated
on other FCDs.
a.3 FileNet P8 does NOT allow modify/overwrite archived objects
a.4 FileNet P8 does NOT allow file rename of archived objects.
b. Retention Test - Pass
b.1 FileNet P8 does support retention at file level
b.2 Although default retention can be set at namespace level, from P8, only
file level retention is supported.
b.3 FileNet P8 does NOT support decreasing retention period.
b.4 FileNet P8 does support increasing retention period.
b.5 FileNet P8 support setting indefinite retention period, to be reset at future
trigger date (e.g. patient discharge)

Hitachi Vantara Confidential 8

 b.7 FileNet P8 support override of initial event driven retention w/ final value.
(Set final retention value following trigger event)
b.8 FileNet P8 is NOT aware of any retention changes in HCP.
b.9 FileNet P8 when set in Aligned Retention Mode, take control of retention
value and override retention set in HCP. When fixed storage area is set in
Non-Aligned Mode, FileNet P8 will NOT take control of retention value.
See this IBM Knowledge Center link:
https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ib
m.p8.ce.admin.tasks.doc/p8pcb043.htm
c. Delete Test - Pass
c.1 FileNet P8 will check retention period before delete. If the retention period
has not expired, P8 will reject the deletion request. If the retention period
has passed, delete request will be sent to HCP.
c.2 FileNet P8 deleting object after retention expire - depends on the "Delete"
method set in the fixed storage area. Deleting document content that is
stored in a fixed storage area is carried out according to the delete method
setting for that file storage area. The method that Content Engine uses to
remove content element files from the storage area.
You can choose one of the following methods:
• Clear: The file is deleted.
• Destructive: The file is written over with zeros and deleted.
• Purge: The file is written over three times with different characters
and deleted.
d. Setup Test - Pass
d.1 For Incorrect Protocol - FileNet P8 in general returns a message
"The fixed content provider could not establish a connection to the fixed
content device." followed by the URL used and general information. If the
RESTful API returns failed status, it will be included in the error message.
The fixed content provider could not establish a connection to the fixed
content device. Namespace: [http://qa-no-http.cemp.cm-
hcp8.svl.ibm.com/]; URI: [/test12345/]; Username: [daphne]; Root Cause
[FNRCC0092: The configuration is invalid for this provider. The user
[daphne] is unable to perform the requested operation on the HCP
namespace [qa-no-https.cemp.cm-hcp8.svl.ibm.com]. Check that the
namespace is valid, and that this user has been granted
read/write/delete/purge access for this namespace.]
d.2 Incorrect URL – FileNet P8 fixed content provider could not establish a
connection to the fixed content device. Namespace: [http://qa.cemp.cm-
hcp8-1.svl.ibm.com/]; URI: [/test12345/]; Username: [daphne]; Root Cause
[FNRCC0110: The [getResponseCode] operation on the fixed content
provider [Hitachi Content Platform FCD] failed. Namespace: [qa.cemp.cm-
hcp8-1.svl.ibm.com]; URI: [http://qa.cemp.cm-hcp8-
1.svl.ibm.com/rest%2Ftest12345%2F]; Username: [daphne]; Root Cause
[java.net.UnknownHostException: qa.cemp.cm-hcp8-1.svl.ibm.com]

Hitachi Vantara Confidential 9

 The fixed content provider could not establish a connection to the fixed
content device. Namespace: [http://qa.cemp.cm-hcp81.svl.ibm.com/]; URI:
[/test12345/]; Username: [daphne]; Root Cause [FNRCC0092: The
configuration is invalid for this provider. An unexpected status code [503]
was returned from the HCP server: [qa.cemp.cm-hcp81.svl.ibm.com]; URI:
[http://qa.cemp.cm-hcp81.svl.ibm.com/rest%2Ftest12345%2F]]
d.3 Incorrect Tenant/Namespace - The fixed content provider could not
establish a connection to the fixed content device. Namespace:
[http://qa1.cemp.cm-hcp8.svl.ibm.com/]; URI: [/test12345/]; Username:
[daphne]; Root Cause [FNRCC0092: The configuration is invalid for this
provider. The user [daphne] is unable to perform the requested operation
on the HCP namespace [qa1.cemp.cm-hcp8.svl.ibm.com]. Check that
the namespace is valid, and that this user has been granted
read/write/delete/purge access for this namespace.]
e. Availability Test - N/A
FileNet P8 has no error handling specific for node failures. Depends on
when the node failure occurs during a read/write operation, either a
connection error will have occurred, or a REST API will return error code.
For failed write operations, the content will remain in P8 content queue
and the write operation will be retried according to the P8 configurations.

Hitachi Vantara Confidential 10

Joint Operation Guidelines and Best Practices

HCP Administration
HCP supports multiple tenants: virtual stores with independent management and
data access. Each tenant can host multiple namespaces that segregate the data
from different applications and user communities. Think of a tenant like a volume.

Upon Tenant creation, an Admin user is specified along with a quota of storage
space. From there, the administrator for the Tenant can create HCP
Namespaces with quotas carved from the Tenant quota. The Tenant
administrator manages Data Access Accounts that are used to authenticate
users for file manipulation in the name space. The Data Access Accounts are the
actual end user accounts for storing and retrieving data from the Name Space.
Quotas and access rights are inherited from the parent and can be reduced by
the administrator at each level.

• Create HCP Tenant

o Allocate sufficient space for anticipated used by all Namespaces in
the Tenant (typically there will only be a single Namespace)
o Set the Namespace Quota. This is the maximum number of
Namespaces that may be created within the Tenant
o Replication may be set, but discussion is beyond the scope of this
document
o Retention Mode Selection, Search, and Versioning should be left
unchecked
o Service Plan selection is optional and beyond the scope of this
document
o Specify the Userid and Password of the initial Security User of the
Tenant

Hitachi Vantara Confidential 11

• From the Tenant GUI, per local standards, modify Console Security
settings and either create a new administrative user or add administrative
capabilities to the Security User.

• Create an HCP Namespace within the Tenant.

o Allocate sufficient quota for the task out of the overall quota
assigned to the Tenant.

Hitachi Vantara Confidential 12

Create a Data Access User for the HCP Namespace. This may be a new user, or
additional capabilities added to the existing Tenant User.

• From within the HCP Namespace, review specific settings as required by

the application. Most often the Default Values are preferred. In particular,
review the settings on the Protocol Tab, and enable (if desired) the HTTP
protocol in addition to or in lieu of the HTTPS protocol.

Hitachi Vantara Confidential 13

• Any other changes should be done per local requirements by consulting
with your Hitachi Vantara File Services Consultant.

Hitachi Vantara Confidential 14

IBM FileNet P8 Content Platform Engine Administration

Create Hitachi Fixed Content Device from IBM Administrative Console for
Content Platform Engine:

https://www.ibm.com/support/knowledgecenter/SSNW2F_5.5.0/com.ibm.p8.ce.a
dmin.tasks.doc/contentstores/cs_create_a_fixed_content_device.htm

Hitachi Vantara Confidential 15

Create Fixed Storage Area for Hitachi Fixed Content Device:
https://www.ibm.com/support/knowledgecenter/SSNW2F_5.5.0/com.ibm.p8.ce.a
dmin.tasks.doc/p8pcc123.htm

NOTE:
1. FileNet P8 Content was stored in HCP in native format as provided by
client applications. The Directory structure is either 739 directories in two
level or 12167 directories in 3 levels.
2. Recommendations/best practices in deploying FileNet P8 with HCP
a. Do not update/modify/delete P8 managed content directly from HCP
(or outside of P8).
b. If default retention is set on the namespace, make sure the retention
period falls in the default retention range

FileNet P8 Directory and File Structure

The Name is in this format: FN<P8 Content ID><P8 Device ID><Content

Element>

e.g. For a P8 content with 3 content elements, 3 files will be written in the same HCP folder.
FN{D0EE9362-0000-CE1F-B298-81759BEF6F90}{2B789262-F724-4C98-BE96-2A7D10551442}-0
FN{D0EE9362-0000-CE1F-B298-81759BEF6F90}{2B789262-F724-4C98-BE96-2A7D10551442}-1
FN{D0EE9362-0000-CE1F-B298-81759BEF6F90}{2B789262-F724-4C98-BE96-2A7D10551442}-2

Hitachi Vantara Confidential 16

(1) root folder under a namespace:
The "Content" folder is for actual content.
The "System" folder contains a FCD Identifier file.

Hitachi Vantara Confidential 17

(2) Content files written to HCP.

Hitachi Vantara Confidential 18

HCP Unique Capabilities Utilized
I/O Protocol (REST / S3 / NFS / CIFS / WebDAV) REST only
Sets file level retention Yes
Support Audit Lock Implemented but not
officially
documented/exposed.

Supports Conditional Retention No

Supports Retention Categories No
Compatible with Folder Level Retention: No
Sets Shredding: No
Writes Custom MetaData: No
Supports Annotations No
Supports Versioning No
Writes Data in proprietary or native format Native

Writes Data in manner consistent with Duplicate Individual files only

Elimination policy.(Individual files – no instance
headers)
Writes Compressible Data (Not .zip, .jpg, etc) No
Writes Individual Files or Container Files (or both): Individual files only

Supports MAPI (Management API) No

Supports MQE (Metadata Query Engine API) No
Supports ACLs No

NOTE:
1. FileNet P8 writes Data in Native Format - CPE does not manipulate
incoming content other than optional compression and encryption.

Hitachi Vantara Confidential 19

Next Steps

Action Responsibility Timing Comments

© Hitachi Vantara Corporation 2018. All rights reserved. HITACHI is a trademark

or registered trademark of Hitachi, Ltd. IBM is a trademark or registered
trademark of International Business Machines Corporation. Microsoft and
Windows Server are trademarks or registered trademarks of Microsoft
Corporation. All other trademarks, service marks and company names are
properties of their respective owners.

Hitachi Vantara Confidential: Internal use only.

Notice: This document is for informational purposes only, and does not set forth
any warranty, expressed or implied, concerning any equipment or service offered
or to be offered by Hitachi Vantara.

FE- SL-064-00 May 2018.

Hitachi Vantara Confidential 20