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://hqdemo1:9080/FileNetEngine
  
  

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 11: Why use custom objects when we have content-less document?

Answer:

Custom objects are for creating composite objects. It can contain content-less document, i.e. only metadata as well as other document classes and/or custom objects as its properties. 

 

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 queues make it possible to process a workflow step using an external entity, such as a Java™ object or Java Message Service (JMS).

Using Process Configuration Console, you configure a component queue with an adaptor, either Java or JMS. The Java adaptor allows you to expose public methods from a Java class as operations on a queue. The JMS adaptor allows you to publish workflow data to a JMS queue, also using operations. Using Process Designer, the workflow author adds a component step to a map and selects operations for that step from the list of component queues. The workflow author also specifies the appropriate expression for each operation parameter.

To create a new component queue

1. In Process Configuration Console, open the isolated region.
2. Select the Component Queues folder icon and click New on the toolbar.
3. Enter a name for the queue in the Queue name box. See Naming conventions for information regarding valid names. The name will appear in the list of component queues in Process Designer.
4. In the Description box, you can optionally enter a brief description of the queue.
5. Click Next to continue.

 

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:

 

 

 

 

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:

FPRIVATE "TYPE=PICT;ALT=FileNet Enterprise Manager - Root Classes"

 

 

 

Question 16: Is there a method(s) to retrieve all document classes of an object store without using the SearchSQL/SearchScope API classes?

Answer:

 

 

Question 17: What is the difference between file store and object store?

Answer:

An OBJECT STORE is a database repository for storing objects.

But FILE STORE deals with at which it stored format type. File systems that are used for file stores must through the NFS or CIFS protocol.