FileNet P8 Architecture
The FileNet P8 architecture offers enterprise-level scalability and flexibility to handle the most demanding content challenges, the most complex business processes, and integration to all existing systems. The FileNet P8 architecture provides a framework for functional expansion for managing enterprise content and Web publishing challenges, and provides greater process control and consistency across your enterprise.
The FileNet P8 architecture:
- Integrates with other infrastructures using industry standards (J2EE, XML)
- Integrates with enterprise business applications and the content they contain via SOAP, XML, and EAI
FileNet P8 ECM Suites
FileNet's P8 Enterprise Content Management offering is a comprehensive set of componentized capabilities and technologies that address key customer usage requirements. Each suite is an easy entry point into the broad FileNet ECM architecture, and customers can easily expand the capabilities of their solution by adding specific modules and components. FileNet's ECM product suites include:
- FileNet Business Process Manager is designed to allow companies and government agencies to streamline and automate their business processes. This solution combines real-time and historical tracking with analysis and simulation so processes and resources can be fully optimized.
- FileNet Content Manager is a comprehensive Enterprise Content Management platform that is designed to deliver integrated content, process and system connectivity to manage, control and deliver any digital asset.
- FileNet Web Content Manager is a next-generation Web Content Management solution that offers enterprise scalability and empowers business users to easily contribute and manage Web site content dynamically.
- FileNet Image Manager is designed to provide organizations with the ability to manage billions of fixed objects, such as paper documents, faxes, email and rich media, and make information immediately available to customers, partners and employees, enabling better decisions, faster.
FileNet P8-s modular suite approach offers customers the flexibility to buy only what they need and add additional FileNet P8 components as required. This ensures that the technology can adapt to new and emerging requirements and protects customers- technology investments. All suites are fully interoperable, offering streamlined configuration, design, deployment and lower total cost of ownership.
FileNet-s P8 architecture is designed to provide enterprise-level scalability and flexibility to handle the most demanding and complex content, business process and application integration challenges. It combines the capabilities of FileNet-s popular Panagon platform, Acenza application framework and its Brightspire eBusiness framework and Business Process Management technology into a unified ECM platform. Additionally, the FileNet P8 architecture utilizes a single repository, single user experience, and a single Application Programming Interface (API) set for developers. FileNet is the only ECM vendor delivering this level of functionality in a unified ECM architecture, making it possible for customers to reduce the risks associated with contracting multiple ECM vendors and lowering their total cost of ownership.
The FileNET P8 family of products includes back-end services, development tools, and applications that address enterprise content, process and connectivity requirements.
Overview of the FileNET P8 components:
Applications/User Interfaces:
1. Workplace
2. Web Content Manager
3. Capture
4. Office Integration
5. Enterprise Manager
Development Toolkit:
1. Java API
2. Web Application Toolkit
3. Portal Integrations
4. Solution Templates
5. Case Management API
6. Image Services Resource Adaptor
7. Workplace Application Integration Toolkit
8. Capture Toolkit
Services:
1. Content Engine
2. Rendition Engine
3. Process Engine
4. Process Analyzer
5. Process Simulator
6. Image Services
7. Enterprise Application Integration
8. Component Integrator
Content Engine:
The Content Engine provides software services for managing content and other business-related data, collectively referred to as objects. In addition to managing documents and any customer defined objects, the Content Engine manages a broad range of enterprise content including workflow definitions, stored searches, publishing templates, entry templates, web content management templates, analytical reports, and simulation scenarios. Key services provided by the Content Engine include:
- Distributed repository services (Object stores)
- Distributed content storage services
- Content retrieval and distributed caching services
- Object-oriented, extensible metadata model
- Version management
- Relationship management
- Security services that provide fine-grained object access control
- Server side events and subscriptions
- Content classification framework
- XML content classification
- Content transformation to PDF and HTML(i.e renditions)
- Documents lifecycle model
- Search services
- XML-based import and export
- WebDAV provider
- Integration services
- Administration
Rendition Engine:
The Rendition Engine is responsible for converting documents from a variety of formats (such as Microsoft Office) to PDF and HTML format. Multiple Rendition Engines can be configured to support large number of translation requests.
Process Engine:
The Process Engine provides business process management capabilities. Key services provided by the Process Engine include:
- Distributed process execution
- Isolated process regions
- Individual and group work management
- Routing
- Timers
- Email notification
- Event logging
- Authorization
- Statistics gathering for analysis
- Integration services
- Adiminstration
Process Analyzer:
The Process Analyzer supports monitoring and analyzing business processes by collecting events from workflows running in the Process Engine and generating statistical data and reports. The Process Analyzer leverages OLAP (On-Line Analytical Processing) technology for fast analysis of multi-dimensional information, drill-down from summary view to details, and -slice and dice- for interactively exploring business process data from different perspectives.
The data flows from the Process Engine to the Process Analyzer. The Process Analyzer Connector runs on the Process Engine, collecting information about process execution via events and passing these events plus information about the workflow definitions and configuration to the Data Collector, a Windows 2000 service that runs in the Process Analyzer.
The Data Collector stores the information in the Data Warehouse and Data Mart. The Data Warehouse serves as a staging area for the Data Publisher, which analyzes events and uses the information to populate required information in the Data Mart. The Data Mart maintains raw statistical information, which is used to build OLAP Cubes. Ultimately, the OLAP Cube provides the information required to generate Excel charts for the end user.
Process Simulator:
The Process Simulator is responsible for performing -what-if- scenarios based on data gathered by the Process Analyzer, providing business analysts with important information that helps streamline business processes.
Image Services:
Image Services provides very high volume image acquisition and storage capabilities. Capabilities provides in Image Services include:
- Batch entry and indexing for very high volume image acquisition in an assembly-line fashion
- Hierarchical storage management and high-speed locator database.
- Distributed cache services
- High-volume remote print services for images.
Enterprise Application Integration:
FileNET provides Enterprise Application Integration connectors for integrating process and content with enterprise applications. In addition, FileNet offers an optional EAI server through and OEM agreement for IBM CrossWorlds InterChange Server, Connectors, and Collaborations.
The connectors provided by FileNet provide easy integration with dozens of enterprise applications such as SAP R/3, Siebel, and Clarify as well as technologies such as XML, Web Service, JMS, and MQSeries. The FileNET connectors support the following behavior.
- Object, workflow and queue definitions can be exported from the Content and Process Engines for data mapping and specifying processing logic using the IBM CrossWorlds graphical design tools.
- From CrossWorlds collaboration, you can launch workflows, execute process operations and create, update, and delete documents, folders and custom objects.
- You can initiate a CrossWorlds collaboration from a workflow step or from a Content Engine event, such as when a new object is created or updated.
FileNET plans to provide connectors to other EAI vendors in the future, and customers and partners can use the FileNET P8 Development Toolkit to build additional connectors.
Component Integrator:
The Component Integrator provides a mechanism for easily interacting with components (such as Java Classes) from a workflow.
The FileNET P8 family of products support and leverage XML in many ways across the product, including:
XML content management
- XML content is treated like any other content and therefore can be secured, versioned, have a lifecycle, participate in workflows, generate events, etc.
- XML content can be automatically validated and classified
- XML tags can indexed and full-text searched.
XML as data format
- Many FileNET structures are represented in XML, including workflow definitions, entry templates, search template, publish templates, publishing assemblies, import/export format, and site/user preferences.
XML for data exchange
- XML is used to import and export objects and metadata definitions.
- Programmatic interfaces return XML than can be used to integrate with enterprise applications.
XML for application development
- The FileNET P8 Java APIs return XML, for example the contents of a folder can be returned as an XML document.
- XSL transforms are applied to XML to render user interfaces.
Content Engine related Information
Question 1: In how many databases does FileNet Content Engine (CE) stores data?
Answer: FileNet Content Engine (CE) has two or more databases:
Global Configuration Database (GCD) database (FNGCDDB)
Object Store databases (one or more)
A FileNet P8 domain can contain one or many object stores. Each object store has its own database which could be existing database or can be created by object store creation wizard in FEM.
Question 2: Where FileNet Content Engine (CE) physically stores documents?
Answer: FileNet Content Engine can be configured to store documents at following places:
In Database as blobs (IBM recommended maximum document size to store as blob is 10 KB)
In File Store
In Fixed Storage Devices (like EMC Centera)
Question 3: What is FN P8 domain?
Answer: The FileNet P8 domain represents a logical grouping of physical resources (such as object stores) as well as the Content Engine servers that provide access to those resources. A server can access any resource in the domain, but cannot access any resource that lies outside of the domain.
The CE Global Configuration Data (GCD) database stores information about the resources and services for the FileNet P8 Domain.
The FileNet P8 domain contains the following entities:
Site - A site is a geographical location where resources are connected through a local area network.
Object store - An object store is a repository for storing objects (such as documents, folders, and business objects) and the metadata that defines the classes and properties of objects.
Index area: An index area is a container for one or more indexes, which are used to perform full-text searches against documents in an object store.
Fixed content device: A fixed content device is an external storage device. This device can be associated with a FileNet P8 fixed storage area.
Content cache area: A content cache is a disk area that contains copies of content recently accessed through a Content Engine server. Typically used in a geographically distributed environment, it enhances response time when retrieving content.
Add-on feature: An add-on feature is a module that contains custom metadata and data that support extensions to core Content Engine features.
Marking set: A marking set provides a way to define a level of security on objects in addition to the normal FileNet P8 security model. By using markings, access to objects can be controlled based on specific property values.
Question 4: What is File Store and File Store Policy?
Answer: File Store is the physical folder where FileNet stores documents. Multiple File Stores can be created to store documents at two different places. This type of setup is called File Store Farm.
File Store Policy allows distribution of documents in File Store Farm.
Question 5: What is the use of Content Engine Query Builder?
Answer: CE Query Builder allows FileNet users to find Content Engine objects and to carry out bulk operation on them. Query Builder is part of FileNet Enterprise Manager (FEM) software comes with FileNet Content Engine installable.
The basic functionality of Query Builder includes:
Find objects using property values as search criteria.
Create, save and run simple searches.
Create and save search templates that will prompt for criteria when launched.
Launch search templates that are provided with each Content Engine and Enterprise Manager installation.
Create, save, and run SQL queries.
The Query Builder searches can be combined with bulk operations that include the following actions, available on the Query Builder's Actions tab:
Delete objects.
Add objects to export manifest.
Undo documents checkout.
Lifecycle actions (set exception, clear exception, promote, demote, reset).
File documents and custom objects in folder and unfile them from folder.
Run VBScripts or JScripts.
Edit security by adding or removing users and groups along with allow and deny permissions.
Question 6: What is the significance of Folders in FileNet P8?
Answer: In FileNet, Folders are used to group other objects including documents and custom objects. As folders in windows, FileNet folders provide a way to browse through FileNet objects. Folder's helps in organizing the documents and other items.
A document can be filed to multiple folders. FileNet does create copies of document in this case. It actually creates a logical association between then folder and the document.
Few important facts about folders:
Folders are not versionable; only documents are.
Folders are based on CE folder class.
Content of a folders can be copied to another folder exist in same object store.
It is not mandatory that each document or objects should be filed under a folder. Documents which are not part of any folder remain Unfile.
A Root Folder is created along with a new Object Store. This folder is parent folder for all other folders in the Object Store.
Each Folder has its own custom security.
Folders can generate server events when they are created, modified, or deleted.
Question 7: How to determine if FileNet Content Engine (CE) is running fine?
Answer: Following are few things one can check to find out if FileNet CE is running fine:
Check WebSphere console for 'FileNetEngine' web application status. It should be in running state.
Try connecting to CE using FEM. If connection is fine CE is running. If CE is not running user will get message 'Unable to logon to P8 domain'.
Try logon to FileNet Workplace. If user is able to sign in, CE & directory services are running fine. If not user will get 'credential exception'.
Try following URL:
http://machine_name:port_number/FileNetEngine
ie. http://demo:9088/FNEngine
If 'Startup Context' page is displayed, CE is running fine. If CE is not running, user will get message 'The page cannot be found'.
Question 8: Does FileNet CE provide content compression or encryption?
Answer: No
Question 9: How authentication is handled in FileNet P8?
Answer: Authentication is a process of checking if the user entered credentials are correct. FileNet P8 uses two different standards for authentication:
1. Java Authentication and Authorization Service (JAAS) standard
JAAS provides a policy-based framework to determine who is invoking a Java application. The Content Engine EJB resides within the J2EE Application Server's EJB container. CE therefore uses JAAS pluggable framework for authentication.
2. Web Services Security (WS-Security) standard
FileNet web services uses WS-Security standards for authentication. Like JAAS, WS-Security is an extensible standard which supports multiple security token formats i.e. Username Token, Kerberos Tokens, SSL X.509 Tokens etc.
When the Content Engine server receives a web service request, the Content Engine Web Service Listener extracts the WS-Security header and performs a JAAS login based on its contents. If this JAAS login is successful, then the Web service listener passes the request onto the Content Engine EJB layer within the EJB container.
Question 10: What is Content Engine Web Services (CEWS)?
Answer: Communication with FileNet Content Engine (CE) can occur through the EJB transport or Content Engine Web Services (CEWS) transport.
Web services are commonly used by loosely coupled frameworks like service-oriented architecture for connecting components. IBM FileNet Content Manager provides CEWS for accessing nearly all features available in the CE server.
A Web Services Description Language (WSDL) file is provided by FileNet to use a Web services interface. CEWS clients (stub classes) can be generated from these WSDL files.
As of release 4.5.0, CE supports three Web services endpoints. The difference is in their handling of content attachments. The SOAP endpoint (FNCEWS40SOAP) uses inline content and carries significant performance costs. It should therefore be avoided. Support for the Direct Internet Message Encapsulation (DIME) endpoint (FNCEWS40DIME) is documented as deprecated and will eventually be removed. Therefore, all new code should be written for the Message Transmission Optimization Mechanism (MTOM) endpoint (FNCEWS40MTOM), and existing DIME code should be migrated to MTOM as soon as possible.
Question 12: How do you delete a document using code?
Answer: A document object can be deleted from FileNet Content Engine (CE) using .delete() method.
Following steps can be followed to delete a document:
Instantiate the object using getInstance or fetchInstance.
Call 'delete' method to add delete operation to the objects PendingActions.
Call 'save' to perform the delete operation.
Following Java code demonstrates the deletion of a document stored in FileNet Content Engine:
// Get the object
Document doc = Factory.Document.getInstance(os,"Document","/Doc");
// Mark the document for deletion locally
doc.delete();
// Perform the delete
doc.save(Refresh.NO_REFRESH);
Note: Similar steps can be used to delete other objects in FileNet including folder objects, custom objects etc.
Question 13: What is component queue and how to configure component queue in FileNet?
Answer: Component Queue is required to configure component steps in workflow designing. Suppose at 1 step you have some business and you
want to execute some java code for that. So you will make a java file with all business (various methods) and by combining all java files
you will make a jar file. So while configuring component steps in workflow, you will add that jar to component queue and in workflow design page, you will slect that
component queue and assign that method for that business.
Question 14: What are Stored Search and Search Template?
Answer: Workplace provide object search to help users quickly locate they items they are looking for. Multiple options are available to workplace users for searching objects stored in FileNet Content Engine including simple search, stored search, search templates etc.
By default the simple search is available to users. Using simple search users can create customized searches for documents, folders, and custom objects. The search criteria’s and options can be configured using the Search view of the User Preferences page of workplace.
Both stored searches and search templates are predefined searches configured by administrators using Search Designer tool.
Differences between stored search and search template:
Stored search is complete search.
Search templates are for a partially completed search where users are promoted for search criteria.
Stored search execute automatically when opened.
Search template allows user to fill the search criteria’s and perform search.
Other facts:
Both search templates and stored searches are created and maintained by administrators who have access rights to Search Designer, a part of Author Advanced Tools in FileNet Workplace.
Both the searches are stored in an object store and can be modified or deleted later.
A stored search or search template can search any object stores user select as part of the criteria, regardless of where the search resides.
Search Designer Tool creates and modifies stored searches and search templates that allows Workplace users to run searches. Below is the screen shot of Search Designer Tool:
Note: FileNet Enterprise Manager’s Query Builder Tool also provides CE object search capabilities along with bulk modification / delete feature.
Question 15: What are root classes in FileNet?
Answer: A root class is a class without a parent. FileNet object store has multiple root classes including Document Class, Annotation, Choice List, Event etc. The ‘Parent Class’ property of these root classes is ‘None’ (as shown in below screen shot).
The root classes are created automatically during object store creation. Once the root class is created, subclasses and properties can be added to the object store.
For example, a document subclass can be added under root class (Document Class) by running the Create a Class wizard from Enterprise Manager.
Except the ‘Document Class’, all other root classes are places under ‘Other Classes’ in Enterprise Manager as shown in below screen shot:
Question 16: What is document lifecycle?
Answer: Document lifecycle in FileNet P8 is a sequence of states (like Draft, Review, Publish, close etc) that a document will go though over its lifetime, as well as the action that are triggered when document move from one state to another.
A user or application can move the doc forward or backward in it's lifecycle.
Question 17: Does FileNet component CE, PE, AE support server clustering? What kind of clustering is supported by FileNet P8?
Answer: FileNet P8 platform supports Asymmetric, Symmetric, N + 1, and N to M clusters. This includes FileNet Content Engine, Process Engine and Application Engine.
Asymmetric clusters include both active and passive servers. i.e. In case of Asymmetric 1-to-1 cluster, there is one active and another passive server. This is simplest form of clustering.
Symmetric clusters include all the active servers. In Symmetric clusters different servers run different services but in case of fail over, multiple services are be moved on to one server.
Please note: While FileNet CE, PE, AE supports active/active clustering, FileNet IS supports only active/passive clustering.
Question 18: Which protocol is used by FileNet P8 Process Engine (PE) to connect to Content Engine (CE) or Application Engine (AE)?
Answer: IIOP is used by PE to communicate with CE and AE.
IIOP means 'Internet Inter-ORB Protocol'
ORB means 'Object Request Broker'
As CE is installed on AE, it uses direct API calls to communicate with AE.
