IBM FileNet P8, Version 5.2.1            

Compatibility of document properties

The Content Platform Engine and FileNet® Image Services systems can use different relational database management systems. But if document properties are to be exported from FileNet Image Services to a Content Platform Engine system that uses a different RDBMS, the database administrator must ensure that the FileNet Image Services document properties are compatible with the RDBMS in the Content Platform Engine system.

String Properties
Make sure that the Content Platform Engine string property template is large enough to contain the maximum FileNet Image Services string size.
Numeric Properties
Make sure that the Content Platform Engine data type that is mapped to the FileNet Image Services numeric data type is large enough to hold the value from the FileNet Image Services index. Content Platform Engine integers are signed integers that have a range of -2,147,483,648 to 2,147,483,647. If the FileNet Image Services numeric index has values outside of this range, you must use the Content Platform Engine float data type; otherwise, the import agent logs an overflow error and terminates.

Floating point numbers that are not integers do not necessarily have an exact binary representation. Therefore, you might experience some loss of precision during the conversion process.

Due to the floating point representation in the Content Platform Engine database and implementation limitations, the maximum number of digits for an integer that can be represented is approximately 15. Integers with more than 15 digits experience loss of precision.

Date Properties
Invalid data in date fields can cause the content federation service to stop. For example, the earliest date Content Platform Engine supports is 1/1/1753 00:00:00 UTC. There are two ways to avoid this problem:
  • Use the defaults on the Content Platform Engine document class to populate the corresponding Content Platform Engine date field, rather than mapping the FileNet Image Services date field to the Content Platform Engine date field.
  • Repair the date field on FileNet Image Services before it is exported by changing it manually, or by running SQL scripts or stored procedures.

Dates before 01/01/1601 cause the import agents to stop due to an error from the date conversion routine. Dates between 01/01/1601 and 12/31/1752 are stored as 01/01/1753 by the Content Platform Engine database. Dates after 01/01/1753 are fully supported.

Menu Properties
Only the values in the FileNet Image Services catalog database are transferred to the Content Platform Engine catalog database. Create choices and choice lists on the Content Platform Engine that have corresponding menu property values and descriptions to ensure that applications continue to display similar choices to the user.


Last updated: October 2015
cfsip013.htm

© Copyright IBM Corporation 2015.