I'm developing an application on top of filenet.
Anyone know HOW the content manager stores properties metadata (class-default & userdefined) on database?
There is a table for each class? There is one big table? The properties are mapped on multipurpose columns or a tablecolumn is created for every added property?
As a developer I don't have access to database to verify my hypothesis, but I have to design the data model for my application.
Any help will be very appreciated!
This topic has been locked.
Pinned topic Filenet Metadata Storing Strategy
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
RuthHildebrand-Lund 270000E6V819 Posts
Re: Filenet Metadata Storing Strategy2013-01-23T22:05:24ZThis is the accepted answer. This is the accepted answer.An object store is made up of several tables. Details about the database schema are in ecm_help → Developing IBM FileNet P8 Applications →
Content Engine Development → Content Engine Java and .NET Developer’s Guide → Reference → Database Reference → Database table schemas. The link to the 5.1 version of the information is http://pic.dhe.ibm.com/infocenter/p8docs/v5r1m0/index.jsp?topic=%2Fcom.ibm.p8.ce.dev.ce.doc%2Fdatabase_table_schemas.htm.
The metadata for the documents is stored in the DocVersion table, with one row for each document.
cwoliveira 270003P29748 Posts
Re: Filenet Metadata Storing Strategy2013-01-23T22:39:01ZThis is the accepted answer. This is the accepted answer.Hi,
You can take a look on this redbook. It contains sample use cases for repository design.
IBM FileNet Content Manager Implementation Best Practices and Recommendations
Also they are a couple references about Classes and Properties concepts on Content Engine. To explore physical database schema is good as reference and DBA tasks such as tuning, but it should not be your primary reference to design the solution.
Administering IBM FileNet P8 > Administering Content Engine > Classes - Concepts:
Administering IBM FileNet P8 > Administering Content Engine > Properties - Concepts: