1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Page 1 of 30
1
1
2
2
2
3
3
4
4
5
5
6
6
7
7
7
8
9
11
13
13
13
13
14
15
15
16
16
16
17
18
18
19
22
23
24
27
Page 2 of 30
is
IIOP
ORB
used
by
PE
means
means
to
communicate
'Internet
'Object
with
CE
and
Inter-ORB
Request
AE.
Protocol'
Broker'
Page 3 of 30
Page 4 of 30
Page 5 of 30
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.
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:
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
http://machine_name:port_number/FileNetEngine
ie.
Page 6 of 30
URL:
http://hqdemo1:9080/FileNetEngine
Page 7 of 30
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:
//
Document
//
Mark
doc.delete();
Page 8 of 30
Get
doc
=
the
the
object
Factory.Document.getInstance(os,"Document","/Doc");
document
for
deletion
locally
//
Perform
doc.save(Refresh.NO_REFRESH);
the
delete
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.
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 criterias 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.
Page 9 of 30
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:
Page 10 of 30
ile N e tE n te rp ris
F
e M a n a g e r-R
o o tC la s
e s
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
Page 11 of 30
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
Page 12 of 30
"TYPE=PICT;ALT=FileNet
Enterprise
Manager
Root
Classes"
ile N e tE n te rp ris
F
e M a n a g e r-R
o o tC la s
e s
Question 16:
Is there a method(s) to retrieve all document classes of an object store without using
the SearchSQL/SearchScope API classes?
Answer:
Page 13 of 30
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.
Page 14 of 30
Initializing new Isolated Region creates default structure as Inbox, default roster
and event log.
Question 4:
Why do we need multiple Isolated Regions?
Answer:
An isolated region is a logical subdivision of the workflow database in FileNet Process
Engine.
Different units in an organization who do not want to share workflow data can create
different
isolated
region.
For example the research department and the finance department in an
organization have two all together logically different processes. It is
recommended to have two different isolated regions for these two departments.
Multiple isolated regions also make it easy to maintain the systems. Changes made
into one region dont affect the users of another region.
Question 5:
How to determine if FileNet Process Engine (PE) is running fine?
Answer:
Following things can be checked to find out if FileNet PE is running fine:
Try
http://hqdemo1:32776/IOR/ping
If
If
PE
is
running,
PE is not running,
Page 15 of 30
following
the
PE
server
page
is
an error 'Page not found' is
URL:
displayed.
displayed.
Try
opening
the
FileNet
Workplace
'Tasks'
page.
If
tasks
page
opens,
PE
is
running
fine.
If request to 'Tasks' page get timed out and 'Process Engine Exception' occurred
then PE is not running.
Examine following Windows services for the process Engine and make sure they
are
running.
1.
Process
Engine
IMG
ControlService
2. Process Engine Service Manager
Question 6:
What are different types of Queue's in Process Engine?
Answer:
Process Engine (PE) queues holds the work items waiting to be processed. The queues in
PE can be managed using Process Configuration Console (PCC).
PE has 4 different types of queues:
User
Queues
User queues hold work items assigned to a users or being tracked by a user. There
are two different type of user queues created when an Isolated Region is
initialized:
Inbox
Tracker
Work
Queues
Work queue hold work item which can be processed by one or many users part of
a
group.
i.e. For processing an insurance claim, a work queue 'Claim' can be created and
any employee from claim processing department can pick up the work item and
process it.
Component
Page 16 of 30
Queues
Queues
Internally used by Process Engine, System queues are not accessible to the users
or administrators. Conductor, Delay, and InstructionSheetInterpreter are few of
the examples of system queues.
Question 7:
How to delete a queue in Process Engine?
Answer:
FileNet doesn't provide any mechanism to delete a queue; whether it is a work queue or a
component queue.
The only workaround is to initialize the isolated region in following way:
Export isolated region configuration data to XML - Use Process Configuration
Console (PCC) to export all components of selected isolated region.
Initialize a isolated region.
Take a backup of XML file from the export in step 1 and carefully edit the XML file
to remove the nodes of unwanted queue.
Import the XML file in recently initialized isolated region with the option 'overwrite'.
Validate the configuration.
Note: When an isolated region is initialized, it makes changes to the workflow database
structure and the data in workflow database is deleted.
FileNet developer should design and configure the queues very carefully to avoid a
situation where they will have to delete a queue.
Question 8:
What happens to the work items when a work queue is deleted from PE?
Answer:
Process Engine work queue holds the work items. FileNet P8 doesn't provide any easier
way to delete a queue.
Queues can be deleted by initializing the isolated region. When a queue is deleted all the
work items in it are also deleted.
Question 9:
Page 17 of 30
Question 10:
What is the use of Process Administrator?
Answer:
FileNet Process Administrator allows FileNet administrator to view and manage work in
progress.
Process Administrator is a Java Applet based UI and can be invoked from IBM
Workplace's admin section.
Following tasks can be performed though Process Administrator:
Search workflows, work items, workflow events, and workflow statistics.
It allows the administrator to search in specific area. Following areas are available for
Page 18 of 30
search:
Workflow roster
User queue
Component queue
Work queue
System queue
Change workflow attributes, such as data field values and workflow group
members.
Page 19 of 30
Connection point (or Process Engine Connection Point) allows Process Engine APIs to
connect to an associated isolated region. The router process in FN 3.5 was replaced by
connection
points
in
FN
4.0
onward
releases.
FileNet
CE
uses
connection
points
to
connect
to
PE.
Connection points are defined in CE APIs and persisted in the Global Configuration Data
(GCD) on the Content Engine. The Content Engine's Enterprise Manager UI is used to
create
and
manage
connection
points.
PE
PE
Connection
Server
DNS,
Point
Port,
Isolated
sample:
Region
Number
i.e
hqdemo1,32776,1
Question 13:
What is the difference between Workplace and Workplace XT? What are the
benefits of using FileNet Workplace XT?
Answer:
IBM FileNet Workplace, a part of FileNet Content Manager product suite, is an out-ofbox
web
based
user
interface
for
FileNet
P8
Products.
Workplace XT is the next-generation FileNet P8 platform Web application.
Most of Workplace XT feature are same as Workplace; however, the procedures user
perform
to
complete
an
activity
are
different.
Workplace XT is faster, user friendly and has features like drag and drop to add
documents.
IBM launched Workplace XT to compete with documentum and Alfresco, who has
similar
web
interfaces.
While most of the functionalities of Workplace XT are similar to the Workplace, it cannot
be considered as product upgrade as Workplace XT is built using Java Server Faces (JSF)
technology.
Workplace XT has better folder structure and nicer way to organize favorites.
Workplace XT does not provide a development environment for customization; however,
Workplace continues to provide the Workplace Application Toolkit and related
development
tools
for
Workplace
customization.
Page 20 of 30
Note: IBM has plans to release the Workplace XT development tool kit in future releases.
Question 14:
What are the types of document class?
Answer:
Page 21 of 30
declared
as
record,
we
consider
the
document
record.
Document objects are stored in the Records-enabled content Object Store (ROS) and the
corresponding record objects are stored in the File Plan Object Store (FPOS).
Question 2:
Should all the properties of CE replicated to RM?
Answer:
No. One should avoid duplicating the properties unless and until it represent a specific
requirement.
Properties which have functional need for document management should be used in CE,
while properties which have functional need for records management should be used in
RM. If a property happens to be needed for both, then it should exist in both.
Many ECM architects use the exact same properties in ROS (CE) and FPOS (RM) for
simplicity.
Question 3:
How many document can be stored a Records Manager's Record Category?
Answer:
There is no limit on number of document stored on Records Category. The 'Record' is
simply
a
custom
object
stored
in
database.
A record is a reference to information and provides metadata to manage the information.
Records can electronic or physical (i.e. a document stored in CE or a physical book).
An electronic record points to an electronic document, such as a Content Engine (CE)
document
or
an
email
message.
A physical record, sometimes referred to as a marker, is metadata about a physical
document or other object, such as paper records, tape, or microfilm.
Page 22 of 30
User queues - Each user has an Inbox that holds work items assigned to that user.
A user might also have a queue of Tracker items. The Inbox and Tracker queues are
created automatically during initialization of the isolated region.
You can use Process Configuration Console to modify user queue properties
change the queue's description, add or delete system and data fields, create indexes,
and configure users' privileges for accessing the queue.
Work queues - A work queue holds work items that can be completed by one of a
number of users, rather than by a specific participant, or work items that can be
completed by an automated process. In a workflow definition, the workflow author
can assign steps to a specific work queue.
Page 23 of 30
Lifecycles
Administrators can use document lifecycles to define a sequential set of states that a
document will go through over its lifetime, as well as the actions that are triggered when
it transitions from one state to another.
Search
Content Engine supports property and content-based searching. Key capabilities of search
include the following:
1. A single search can span multiple object stores in different databases.
2. Workplace users can search for documents, folders, and custom objects.
Searches can be designed to specify multiple folders, including a common folder
name used in multiple object stores.
3. Search templates provide a simple user interface for entering search criteria.
Versioning
You can create different versions of content to maintain a history of changes and to
control which users can change the content at a given time. The set of versions for a
single document is called a version series. Content Engine supports a two-level
versioning scheme, in which a document version is either a major or minor version.
Minor versions typically denote an in-progress document, whereas a major version
typically denotes a completed document
Classification
Classification is the process of assigning metadata to content, specifically the selection of
a document class and property values. Classification can also be accomplished by filing
objects into folders that define classification taxonomies. Classification can be
performed:
1 By a user.
2 By an application that uses the FileNet P8 APIs.
3 Automatically by using the content-based classification capability provided in the
platform.
Entry templates
Users can easily add documents, folders, and custom objects to an object store using
entry templates. Entry templates also make it easy to define approval workflows for
these objects. When using the entry template to add a document to the object store, a
user interacts with a wizard, which decreases the chance of invalid data entry by
limiting the number of steps required and providing a more controlled entry process.
Entry templates are created in Workplace. Some of the key capabilities of entry
templates and advantages to using them are as follows:
Page 24 of 30
1
2
3
4
Documents, folders, form data, and custom objects can be created with entry
templates.
Users who are not administrators can create entry templates. For example, a
project manager can create the entry templates used by her project team.
Entry templates support FileNet P8 records management by providing a
simplified and customizable method of declaring a document as a record.
Entry templates can specify the folder in which the object will be filed, can either
prevent or allow the user to change the folder, and can restrict the user to
selecting a particular folder or its subfolders.
Page 25 of 30
Page 26 of 30
4
5
6
Work management
Work management provides users with a set of tasks that they need to perform. Work
is managed in several types of queues, which are database structures that hold work
items. User queues (called My Inbox in Workplace) hold work items waiting to be
processed by a specific user. Public queues hold work items that can be completed by
any user in the assigned group.
Workplace XT and Workplace
FileNet P8 includes two application environments to provide users with enterprise
content management (ECM) functionality:
1 Workplace XT Workplace XT is the next-generation FileNet P8 platform Web
application. Building on a familiar browse and search interface, users can quickly
become productive in their content management environment. Workplace XT
provides the tools (such as Process Designer and entry templates) by which
business application designers can access the document management and
business process management features of FileNet P8.
Page 27 of 30
Page 28 of 30
7. Code module capabilities where Java classes containing event action code are
stored in the object store and as such are easily deployable.
8. Several tools to help you move content between environments, which aid in the
deployment process.
Page 29 of 30