Interview Questions depends on ur profile, the area on which u have worked on.....There are few basic qustions, which I got in last 3 Yrs of Interviews :-) 1. What is ECM? 2. What is FIleNet and it's components (AE, CE, PE) 3. How AE n CE or CE n PE communicate with each others? 4. Which protocol got used while communication? 5. Whih version of FileNt u have used? 6. Diff b/w 3.5 and 4.0? 7. Diff b/w Custom Object, n FOlder and Document? 8. Descibe Work Item, Workflow definitions, Queue, Roster and WorkFlow? 9. Document Versioning means? Superseedd means..? 10. Other than this, they can ask for CE/PE APIs? 11. If you have worked on Process Designer, then How to create workFlows, How to route them, where to put security, where to add attachment etc.......... Difference between FileNet 3.5 and 4.5 a) FileNet 3.5 is a COM based application. FileNet 4.5 is java based application. b) The Routers in FileNet 3.5 is replaced by Connection points in FileNet 4.5. Therefore, the routers are no longer started and stopped as a service. c) The Process Engine 4.5 does not have direct communication with the LDAP unlike 3.5 environment. d) All the LDAP communication is via the Content Engine in FileNet 4.5. e) FileNet 4.5 global configuration is stored on a Database unlike the FileNet 3.5 where it is stored on a encrypted file “sysinit.dat” f) FileNet 3.5 relied heavily on passing username and passwords for authentication to both the CE and PE. Due to the architectural changes to the CE 4.5, a much greater set of authentication options are now available. The two authentication standards that are now supported include the Java Authentication and Authorization Service (JAAS) and its FileNet RM (Record Manager) related informations * A document is a file which you'll create/save/retrieve/update. Also you can replac the previous version with new updated version. * A document which is added to an IBM FileNet P8 content repository. user friendly and has features like drag and drop to add documents. * A record is a reference to information and provides metadata to manage the information. The 'Record' is simply a custom object stored in database. not a record.e. * There is no limit on number of document stored on Records Category.5 Workplace XT is faster. it cannot be considered as product upgrade as Workplace XT is built using Java Server Faces (JSF) technology. * 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). however. or microfilm Difference between Workplace and Workplace XT? Workplace XT comes with FileNet P8 4. Workplace continues to provide the Workplace Application Toolkit and related development tools for Workplace customization. such as paper records. * An electronic record points to an electronic document. Workplace XT has better folder structure and nicer way to organize favorites. sometimes referred to as a marker. IBM launched Workplace XT to compete with documentum and Alfresco. client side validation in BPF Use EventHandler. As soon as the document is declared as a record. such as a Content Engine (CE) document or an email message. * A physical record. tape. but it is not yet declared as a record is called as „document‟.e.* A record is a reference to information and provides metadata to manage the information. who has similar web interfaces. Workplace XT does not provide a development environment for customization. file is available in the BPF war file and here is the sample code: Suppose we need to put validation for employee salary . we consider the document a record.js for client side validation. While most of the functionalities of Workplace XT are similar to the Workplace.0 onwards by default while workplace comes with FNet 3. Records can electronic or physical (i. a document stored in CE or a physical book). is metadata about a physical document or other object. Records can electronic or physical (i. a document stored in CE or a physical book). if(employeeSalary < 10000) { alert("Salary too less !"). and test the connection 4) Then move on to FEM and create object store by supplying correct data source name.Step 1: make a eventHandler and call oneBeforeAction on that handler Step 2: eventHandlers. employeeSalary = parseInt(Salary. an Ajax based application provides a user friendly interface to the business . } Create Object Store in FileNet using FEM 1) Must : Create GCD database in separate table space (GLOBAL database) 2) Try to get separate table space for object store DB.value). return false. 5) If the Object store creation wizard fails. make sure you request DBA to drop /clean that table space and then try. resId) { if(resName=="ABC") { if (currentCase != null ) { var employeeSalary=0. configure the XA and Non-XA data source for that user under WAS . } } } return true. This is applicable to GCD too.onBeforeAction = function(resName. 3) Steps : Create the oracle user. 6) make sure you create a folder called jars on CE server and drop the correct version jdbc driver file and update the WAS env What is BPF? FileNet BPF provides a configurable framework for rapid development of BPM application. BPF Web Application. you can connect to an Image Services repository. an administrator can create and manage the classes.users. It is capable of managing enterprise-wide workflow objects. customizable. such as Document. FileNet BPF provides a framework to develop and customize the application to meet business requirement. Using these tools. and documents by offering powerful and easy-to-use administration tools. Content Engine (CE) 2. A Java API provides a rich set of Java classes which map to object store objects. storage. P8 Core Components FileNet P8 core components: 1. extensible metadata model – Enables Content Engine to provide complex and flexible data representation. and a UI container with relevant components for BPF applications. or Property Description. as well as create documents to be stored in the repository. a Web Service API allows customers to author applications in a platform and language independent manner by exposing the object model in a small number of . BPF Explorer: BPF Explorer is a Microsoft Management Console (MMC)-based What is ISRA (Image Services Resource Adaptor)? The Image Services Resource Adaptor (ISRA) is a set of Java classes for interacting with IBM FileNet Image Services. Application Programming Interfaces (APIs) – Provide an extensible platform for development and cross-repository queries. You can then query for and retrieve documents from the Image Services repository. custom objects. Key architectural aspects include: Object-oriented. FileNet BPF has two components: 1. and metadata that form the foundation of an Enterprise Content Management system. Folder. These classes conform to the J2EE Connector Architecture (JCA). Application Engine (AE) and 3. the BPF Web Application is an out-of-the-box. and a rich event framework provides the means to trigger an action in response to activities performed against Content Engine objects. Process Engine (PE) Content Engine Content Engine is designed to handle the heavy demands of a large enterprise. Using this programmatic interface. BPF Web Application: Deployed on a J2EE server. 2. properties. Along with the pre defined screens and functionality. and configurable portal for BPM applications. and lets administrators configure systems programmatically. A process designer or business analyst creates business rules using rules software acquired from another vendor and associates the rules with the steps of a workflow.. The preceding diagram includes the following services and management components: • Process Service – The core of the business process management system. rules management. 3. 7. Process EngineProcess Engine provides software services for managing all aspects of business processes (also called workflows). if feasible. Process Engine sends a request to the Rules Listener to execute a rule set. and it allows data to be transported through many different systems without corruption. enterprise users.NET platform.NET API (which is functionally equivalent to the Java API) provides for development of applications using the . process simulation and modeling. 4. a . 6.generic methods suitable for deployment in a Web environment. and database technologies. scalability. as well as support for a wide range of operating system platforms. If a component step is used at multiple locations in workflow then separate queue should be defined for processing of work items from that queue. Unicode-based – Unicode is a universal character encoding standard that enables Content Engine to be targeted to multiple platforms. and workflow analysis.. Process Engine components allow you to create. and high availability features. try to put general description on each step to make workflow more descriptive. adding. and countries without re-engineering. languages. 5.. You can add members to Web server farms and Content Engine server farms at any time. Always check sequence of routing condition like first true condition then next • E-mail Notification – Enables automatic transmission of e-mail to users when specified processrelated events occur. Step name should be same as steps defined in requirement document. Try to more business logic should be handled in workflow definition instead of code. such as process execution. modify. Scalable – Can be deployed to suit the demands of the enterprise. It provides workflow services on behalf of Process Engine. As the enterprise's needs change. process routing. • Rules Connectivity Framework – Provides a framework for rules integration. J2EE-compliant application server – Offers reliability. you can reconfigure the system by replacing. and manage workflows implemented by applications. or external users (such as partners and customers).This is to optimize processing time for work items. e-mail notification can also be used to track workflows. or removing servers or applications without bringing the system down. Few Imp things before creating workflow: Precaution while creating workflow 1. application servers. 2. Try to use submap in workflow as much as possible. Try to use more out of the box functionality. Rules Listener executes the rules . When a running workflow encounters a rule. and application development tools. Java and JMS adaptors are ready for you to use without modification. Workplace XT protects user credentials passed between Workplace XT and Content Engine and.in the rule set and returns the results to Process Engine. providing access to the process and content functionality of FileNet P8. Directory Services – Directory service functionality is accessed through the Content Engine server. • Component Integrator – Provides an extensible integration framework that allows you to easily create connectors. • Process Task Manager – Provides administrative tools for configuring and managing processrelated services on the Process Engine server. if configured. Workflow database – Contains Process Engine configuration information as well as running instances of workflows. For example. Content Engine supports several LDAP providers and single-sign-on (SSO) functionality. and generate reports and charts to analyze the processes deployed in the Process Engine system. provides SSL security.Workplace also supports extended FileNet P8 capabilities such as forms management. Workplace java applets. records management. find bottlenecks. The services and applications included in Application Engine are: • Workplace – An end-user Web application that provides access to the document management capabilities and is tightly integrated with the business process management capabilities of FileNet P8. Application Engine protects user credentials passed between Workplace and Content Engine and. You can configure this component to launch a specific workflow in response to specific events. The rules engine provider must implement a specific API in order to integrate with Process Engine. It is the presentation layer for both process and content. filing a document in a folder might launch a review process in the Process Engine system. • Process Simulator – Allows you to simulate processes or perform “what-if” scenarios with hypothetical or historical data. Application EngineApplication Engine is the FileNet P8 component that hosts the Workplace Web application. • Process Web Services – Provides a Web services API to Process Engine. provides SSL security. This passthrough approach simplifies directory services configuration by centralizing it for both Content Engine and Process Engine. Rendition EngineRendition Engine converts documents from a variety of formats. if configured. You can install Workplace XT in addition to or in place of Application Engine. Workplace XTWorkplace XT is an optional FileNet P8 component (similar to Application Engine) that hosts the Workplace XT Web application. PowerPoint) to PDF and HTML formats. Multiple Rendition Engines can be configured to support large numbers of conversion requests. and portals. such as those produced by Office programs (Word. Excel. • Workflow auto-launch – Event-driven component that launches workflows in the Process Engine system. • Process Analyzer – Provides analysis capabilities to determine cycle times. An application requests that a document be published by submitting a publish request through one . with new security attributes. and security for your form template. or it might also transform the document content to another format (HTML or PDF). You can use it to: • Create any form. such as conveniently checking form templates in and out and adding form templates to an object store. wizard-based user interface to perform the following tasks: • Create and manage object stores and file stores • Create and manage classes and properties • Create and manage security policies and default security for object authorization • Create and manage lifecycle policies • Create and manage event subscriptions • Import and export objects and metadata definitions as XML • Search and perform bulk updates on search results • Configure XML classification • Perform document management tasks (for example. • Add intelligence such as automatic calculations. A publish request might simply create a copy of the document in a new folder. checkin and checkout) • Configure trace logging What is eForms Designer? FileNet eForms Designer is a powerful forms design application that runs on the client desktop. and formatters to the form template to assist users while they are using the forms and help to prevent data entry errors. The publishing background task dequeues the publish request and calls the appropriate publishing event handler. If a format conversion is a part of the publish request. What is eForms management? . The publish request is queued in the Content Engine server. What is FEM (FileNet Enterprise Manager)? Enterprise Manager is a Microsoft Management Console (MMC) based tool that administrators use to manage Content Engine. data validations. Enterprise Manager provides a graphical. • Configure connectivity with external data sources to enable data lookups that reduce user data entry. version control. You can use the integration features to easily manage form templates in eForms Designer. Integration also provides centralized content management. then the handler sends the document to the Rendition Engine server to perform the necessary transformation.of the FileNet P8 APIs. eForms provides the following features and benefits that are ready for you to use without modification. • Simple customization of the form window’s interface to add HTML banners and sidebars. and stored using Workplace. Online forms created using eForms Designer can reduce data entry time. Form Policy WizardA form policy is an object store document that describes how a particular form is to be used. • Which pages of the form are to be displayed at a particular step. saved. • Incorporate digital signatures. eForms provides the ability to process electronic forms as stand-alone documents or to use an electronic form as the user interface for business process workflow. It is the form policy document that a user clicks when he wants to create a new form. There are two types of form policies: one for document forms and one for workflow forms. and are the first step in streamlining and accelerating transaction processing. • Fields on the form can be linked to workflow data fields without having to write HTML code and JavaScript. for workflow policies you can specify: • Whether the form is the primary content of a step. • Automatically map values in the form to workflow data fields for use in process decisions. The form policy wizard is a point-and-click interface within Workplace that allows you to create form policy documents. • Page display can be controlled at each workflow step. What is Versioning? .FileNet P8 eForms allows customers to create and manage online forms in a Web browser that can appear the same as hard copy paper forms. highly intelligent electronic forms without custom programming. • The mapping of form data to document properties. • Map values from workflow data fields to form fields to pre-fill the form with process-specific data. In addition. This interface requires no coding and allows you to specify many form behaviors including: • Which form template to display. improve data accuracy. • The Entry Template used to store the form data in the object store. • Are tightly integrated with other FileNet P8 features such as document classes and entry templates. displayed directly in the step processor user interface. yet are more advanced. • Act as the user interface to workflow steps: • Features such as data checking and error messages make the workflow process easy to manage for the user and minimize data entry errors. and less costly to implement. easier to use. Forms to process workflows: • Include all of the features of document forms and allow tight integration with Process Engine and workflows. • Use document property mapping to automatically populate form data document metadata with values from the form when the form is saved. eForms allows creation of highfidelity. Forms as a type of document: • Can be filled out. Content Engine supports a two-level versioning scheme. phonetic searching. synonym expansion. • Search results can be ranked by relevancy. in which a document version is either a major or minor version. • Released – A document released as a major version. file. or selected from a set of predefined operations such as delete. Many versions in the version series can be superseded. word stem searching. • Superseded – A version superseded by another version. The set of versions for a single document is called a version series.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 system maintains a state property indicating the current state of each version of the document. and custom objects. folders. . • Content searches return matches on properties and content. Key capabilities of search include the following: • A single search can span multiple object stores in different databases. as follows: • In Process – A work in progress version. unfile. typographical errors. What is Search? Content Engine supports property and content-based searching. Only one version of a version series can be in this state. Search results can optionally be displayed in a “document summary” format. including a common folder name used in multiple object stores. • Bulk operations can be performed on search results in Enterprise Manager. Minor versions typically denote an “in-progress” document. • Searching makes use of the Autonomy multilingual features. Only the latest version of a version series can be in this state. • Workplace users can search for documents. and change security. • Searches can be created and stored for easy execution of common queries. • Reservation – A document currently checked out for modification. • Content-based searching using IBM FileNet P8 Content Search Engine supports extensive content search capabilities that account for misspelled words. whereas a major version typically denotes a completed document. Searches can be designed to specify multiple folders. • Search templates provide a simple user interface for entering search criteria. which includes a brief text summary extracted from result documents. Only one major version of a version series can be in this state. • Shortcuts to searches can be saved so it is easy to find them later. cancel checkout. and wildcard searching. In addition to version numbers. where the operations can be scripted. e. folders. and custom objects in the same search specification. such as paper records. we consider the document a record. while properties which have functional need for records management should be used in RM. A physical record.Read / Post Comments Question Should all the properties of CE replicated to RM? 2: Answer: No. a document stored in CE or a physical book). As soon as the document is declared as a record.Read / Post Comments Question How many document can be stored a Records Manager's ‘Record Category’? 3: Answer: There is no limit on number of document stored on Records Category. Properties which have functional need for document management should be used in CE. Life Cycle Actions are promote or Demote. then it should exist in both. a document stored in CE or a physical book). The 'Record' is simply a custom object stored in database. An electronic record points to an electronic document. not a record. what is Life Cycles? Administrators can use document lifecycles to define a sequential set of states that a document will go through over its lifetime. A record is a reference to information and provides metadata to manage the information. Many ECM architects use the exact same properties in ROS (CE) and FPOS (RM) for simplicity. 0 Comment(s) . as well as the actions that are triggered when it transitions from one state to another. Records can electronic or physical (i. or microfilm. Draft 2. sometimes referred to as a marker. Records can electronic or physical (i. And life cycle states are 1.e. If a property happens to be needed for both. 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). A user or application can “promote” or “demote” an object to move it forward and backward in its lifecycle. Question 1: Answer: A document is a file that you can be create. tape. A document which is added to an IBM FileNet P8 content repository. One should avoid duplicating the properties unless and until it represent a specific requirement. but it is not yet declared as a record is called as ‘document’. Review 3. is metadata about a physical document or other object.• Searches can be expanded to retrieve documents. replacing the old version with the updated version. Publish and 4. and subsequently retrieve and update. A record is a reference to information and provides metadata to manage the information. 0 Comment(s) . such as a Content Engine (CE) document or an email message. Close . save. • Can participate in business processes as workflow attachments. which can be Binary. The properties that are associated with objects can have a single value or multiple values. such as home and cell phone numbers. the system can be configured to restrict the values for the property to a choice list. modified. or deleted. are stored. and Object. • Can generate server events when they are created. Float. Integer. which launches a workflow that approves the new document and posts the approved content to a Web site. ID. These events are then used to customize behavior. such as Date Created. The Customer property shown in the loan example in the previous section illustrates how both the Loan and the Loan Application can point to the same Customer object. • Can have custom properties for storing business-related metadata. In the previous example. DateTime. Many different subscriptions might be associated with a particular event trigger. String. • Are secured. In addition. A subscription is the association of a particular event trigger with an event action. For example. What is Properties ? Content Engine object properties can be used to reference objects that reside in any object stores within the same FileNet P8 domain. an object store. and deleted from. . a customer might be represented in the object store as a custom object because there is no requirement for content. creating a document in an object store triggers a create event. A choice list is a list of possible values that the user can select from when assigning a value to the property. For example.Events provide a mechanism for initiating actions that are invoked when objects are created and modified in. You can then search for objects by creating a search expression that searches for more than one value for the same property. The following diagram illustrates how several events might be triggered when a new loan application document is created in an object store. Properties can also be configured to have default values that are set when a new object is created. What is CustomeObject? A custom object is used to store and manage data that does not have content (and thus doesn’t support versioning) or a lifecycle. Boolean. create is the event trigger and the event action is the workflow launch. Custom objects: • Have system properties that the system manages automatically. Properties have a type. Object-valued properties are useful for defining relationships between objects. you might define a multi-valued property named Telephone Numbers in which multiple telephone numbers. For example. • Can contain documents and custom objects. or deleted. such as Date Created. These events are then used to customize behavior. • Are secured. • Can be searched for and retrieved with an ad hoc query. Folders: • Have system properties that the system manages automatically. but rather creates a logical association between the folder and the document. illustrated at right. • Can have custom properties for storing business-related metadata. modified. Annotations: • Are independently securable. and folders. What is document? . • Are hierarchical. and thus are not versioned when a document version is updated. What is Folder? A folder is a container that is used to group other objects. • Are uniquely associated with a single document version. • Can subscribe to server-side events that fire when an action (such as creating an annotation) occurs.What is Annotation? An annotation object. in the sense that a folder can have subfolders. • Can be annotated. • Can have subclasses. An annotation can optionally have a security policy assigned to it. Users typically think of folders as a place where documents are stored. and the content need not have the same format as its annotated object. • Can be audited. filing documents in multiple folders does not create extra copies of those documents. • Can have zero or more associated content elements. documents.. however. You can associate annotations with custom objects. Default security is provided by the class and by the annotated object. • Can participate in a link relationship. • Can generate server events when they are created. • Can be modified and deleted independently of the annotated object. Folders are the primary mechanism through which users access documents. represents incidental information that can be attached to an object for the purpose of annotating or footnoting that object. • Can participate in business processes as workflow attachments.Most users think of a document as a file they create with an application such as Word. • Can be rendered to different formats. • Can have custom properties for storing business-related metadata about the document. What is Filenet P8? The FileNet P8 family of products includes back-end services. Custom Objects and Folder Return the value of head property referentialContainmentRelationship. • Can be audited. The Architecture section includes an architectural overview of the FileNet P8 platform components. • Can generate server events when they are created. Retreive the annotation of a particular document .get_Head(). A document might be used to maintain a traditional electronic file as well as other types of data. development tools. such as an XML document or content that is managed in an external repository. • Can have content that can be indexed for searching. These events are then used to customize behavior. • Can be annotated. • Can point to content that is outside of the object store (external content). This section presents information about features and product capabilities.z Some imp info abt Content Java API * Annottaion can be added to Documents. • Can be published to a Web site. such as Date Created. and applications that address enterprise content and process management requirements. • Can be versioned to maintain a history of the content over time. modified. such as PDF and HTML. • Can have a lifecycle. Users who design enterprise content management applications and those who manage them will need to understand how documents can be leveraged to support a variety of application needs. Documents: • Have system properties that the system manages automatically. The user stores the document in the document management system so that a history of changes to the document is maintained and the document can be easily found and edited. • Are secured. or deleted. • Can be filed in folders. Can have no content (metadata only). Create an instance of custom object Factory.changeState(LifeCycleChangeFlags. Which VWStepElement methos will unloack a work item w/o updating it's fields doAbort(). Retreive available response from VWStepElements vwStepElement.documentPath).get_ChildDocuments(). Retreive choice List associated with a document Class propertyDescription.getContainees() retreives the collection of Document and CustomObject objects filed in a folder. Fetch name of all workflows within a Isolated Region String names[] = vwSession. first implement the EventActionHandler interface and onEvent(. * SearchScope object determines which ned to be searched Very Useful Code Related Informations for Process Engine How to Ends a PE Session and free all resources: vwSession.CustomObject. Steps to return VWRosterQuery object S1: Create a VWSession object and log on .createWorkflow("Name of the workflow"). Retreive a VWWorkFlowMileStones Collection vwProcess.). Any changes made to original document. How to Retreive launch step info of a specified workflow? vwSession. Retreive the audi history for deleted objects in CE Call searchScope.PROMOTE).. How to write User Response to VWStepElements vwStepElements. * Factory class provide type-specific static inner classes for creating instances of CE classes. * Document.get_ChoiceList().fetchObjects(..."CustomObjclass").fetchWorkClassNames(true).).setSelectedResponse(.createInstance(objectStore. after initial publication will not be reflected in published document.getObject("Annotations". The SearchSQL object that is passed in must have an SQL statement to query the DeletionEvents.get_AccessType() * Auditing for CE Objects can be done using by either CE Java APIs or FEM (FileNet Enterprise Manager) * Publishing mechanism create a new document object.objectStore.. * folder. Promote document from "In Progress" to "Completed" document..logOff(). Method to retreive Event Logs vwSession.getContentElements() to retreive content elements associated with document.fetchreachedWorlflowMilestones(level). * To implement Java Event Handler.getStepResponses().fetchEventLog(eventLogName). Retreive Child Documents from a Compound Documents document. on a folder has allow/deny access::: accessPermission..) * To determine ACE (Access Control Entry). false. null) of VWStepElement will moves a work item to another user Inbox The only Exception thrown by P8 Process Java ApI methos is VWException object . connectionPointName). password.fetchCurrentUserInfo(). doDispatch() is the method of VWStepElement which save changes to work object and advances it to next workflow object To use PE java component. ur java class shld contain public methods and class must have a constructor with no parameter How to logon to PE and make connection testPESession = new VWSession (user name. VWWorkObject provides access to all of the fields of work item doReassign(user id.S2: Retreive the required VWRoster object from Session S3: Perform a query from retreived VWRoster object Retreive current user Info vwSession.