WorkplaceXT document Add Wizard Related issue:In WorkplaceXT document add wizard showing initilizing.....

Sol-Check out java version if both 6 and 7 installed.Unistalled java 7

Filenet Interview Question: What is Record Disposition Process in FileNet?facebook

Filnet Interview Question :Discuss the Best Practices for FileNet P8 Records Manager?facebook

Answer:-

IBM Enterprise Record is an add-on component of FileNet P8 which enables organizations to create and maintain accurate, secure, and reliable records for both electronic and physical information.

Following are some of the best practices of FileNet Records Manager:

• As FPOS, the object store for record management, only holds custom objects (i.e. RecordCategory, RecordFolder, Volume, and RecordInfo objects), it is recommended to use a database store as the content store for the FPOS.
  
  Custom objects, unlike documents, do not have any content associated with them. Content Engine retrieves small objects such as records objects (less than 1 MB in size) quicker from a database store.
• It is recommended to install Disposition Sweep component on the FileNet CE server where FPOS is located. This improves the performance of resource intensive disposition sweep process.
• Assign security settings to well defined groups rather than individual users. This makes it simple and easy to maintain.
• Eliminate as much user decision making as possible when declaring records into the system, which results in the records declaration process being more efficient and less error-prone.
• For Records Manager Auditing, only enable the events that require auditing to avoid huge amount of audit data created which affect the performance of the system. Do not turn on auditing for all events on the root classes and inherit it to the children.

Filnet Interview Question: Explain Records Manager Audit?facebook

IBM FileNet Records Manager provides a framework to capture audit events known as RMAudit events. The RMAudit events can be configured for the record classes in File Plan Object Store (FPOS).

The RMAudit event records audit entries whenever any of the following actions are performed on an entity:

• Delete, when record is deleted before a defined records disposition policy.
• Relocate, when a RM object is moved to a different location in the file plan hierarchy.
• Destroy, when record is deleted as a result of a defined records disposition policy.
• Transfer, when a RM object are transfered to an external system for permanent archiving
• Interim Transfer, when records are temporarily transferred to some other location at the end of the retention period of a phase
• Export, when records are exported or copied to another repository.
• Review, Enables us to retrieve records reviewed by an authorized person. Review involves examining the disposal status of the entity to determine whether it can be disposed of.

The audit log stores the following information in FPOS database:

• The action that was performed
• The entity on which the action was performed
• The user who performed the action
• The date and time of the action
• Whether the action succeeded or failed

The audit logs can be access by the FileNet administrator using following tools:

• IBM FileNet Records Manager application (Web application)
• IBM FileNet Enterprise Manager (Windows application)

In order to capture audit events, the RMAudit should be enabled for the CE FPOS object store specified for Records Manager

Key facts about FileNet P8 RM Audit:

• By default, auditing is not enabled for an object store; therefore, in order to capture audit events (whether system or RMAudit), auditing on the object store must be enabled.
• A best practice for Records Manager auditing is to only enable the events that require auditing to avoid huge amount of audit data created which affect the performance of the system.
• RM Audit can be performed on all RM Objects including Record Category, Record Folder, Volume, and RecordInfo objects.

Filenet Interview Question:How many object stores does FileNet Content Engine (CE) support?

IBM FileNet P8 5.1 Content Engine supports up to 750 object stores with sufficient system and database resources are available, IBM WebSphere Application Server 7.0 with the 64-bit IBM JVM and WebSphere Compressed Reference Technology.

But for a CE application server (i.e. WebSphere Application Server) running on 32 bit JVM, IBM recommend no more than 75 Content Engine object stores and for a CE application server running on 64 bit JVM, IBM recommend no more than 150 Content Engine object stores.

Filenet Interview Questions.................What is the length of GUID in FileNet CE?

Ans:- Each object stored (including documents, custom objects etc) in FileNet P8 Content Engine repository has a global unique identifier (GUID). GUID is a system generated unique identifier for the object added to repository. These GUID's are used for reference purposes by other FileNet products as well as 3rd party applications. The length of GUID is 36 characters. GUID Example: E9B46C4F-B75C-46BD-87C3-037A38E6BDF3 Regular Expression for a GUID: "^(\{{0,1}([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){12}\}{0,1})$" In projects where FileNet P8 is only used as document repository, the GUID is send back to the 3rd party application build around those documents through notification after the document is added successfully. 3rd Party application can store the GUID in their own database and use them to retrieve the document and its metadata using MQ or API calls to FileNet CE.