Filenet Components (WithOut !)

Without Application Engine:

Ø       IBM Enterprise Records is not available.

Ø       FileNet P8 eForms is not available.

Without Content Platform Engine:

Ø       Rendition Engine cannot publish completed requests.

Ø       Application Engine and Workplace XT users cannot log in to Workplace or Workplace XT.

Ø       Application Engine and Workplace XT cannot:

Ø       Cannot access object stores.

Ø       Process component queues.

Ø       Populate Workplace or Workplace XT Task pages.

Ø       Use workflow-related Workplace or Workplace XT applications.

Ø       Update user preferences.

Ø       Transfer or launch workflows.

Ø       Process Simulator cannot access object stores to retrieve or store workflow and scenario definitions and simulation data.

Without IBM Content Search Services:

Ø       Content Platform Engine cannot index new content.

Ø       FileNet P8 applications such as Workplace XT cannot search on content that has been indexed for content-based retrieval.

Without Rendition Engine:

Ø       Content Platform Engine cannot publish in HTML or PDF formats.

Without Workplace XT:

Ø       IBM Enterprise Records is not available.

Ø       FileNet P8 eForms is not available.

What's new in FNet 5.0

Have a look at Filenet 5 new updated features:

1. Content Engine will supoort more object store as u increased JVMs (32 bit---70JVMs and 64bits --- 150)

2. FileNet Deployment Manager changed a lot in terms of multi environment support, more object stores, new functionality to install more components like eForms deployment.Using DM, we can switch object stores from one P8 domain to other without physically movement of data/content

3. Now content can be encrypted to avaoid unauthorized access in filenet storage area.

4. More Java and .Net APIs.

Few Imp things before creating workflow

Precaution while creating workflow

1. Try to use submap in workflow as much as possible....
2. Step name should be same as steps defined in requirement document.
3. 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.This is to optimize processing time for work items.
4. try to put general description on each step to make workflow more descriptive.
5. Try to more business logic should be handled in workflow definition instead of code.
6. Try to use more out of the box functionality, if feasible.
7. Always check sequence of routing condition like first true condition then next

Posted by Friend (Owner of this blog)

P8 4.0 Installation Guide

Download P8 4.0 Installation Guide here:

http://freakshare.com/files/dji41zm0/p8-4.0-install-guide.pdf.html

FileNet 4.0

Get the full understanding of Filenet 4.0, its overview, components and many more.........

download from here: http://freakshare.com/files/whquuegp/Filenet-P8-4.0-overview.pdf.html

About WAT

Learn about FileNet WAT Framework.....

This pdf will explain about WAT Framework, Controllers, Workplace Customization, Preferences and Portlets.........

Complete tutorial: Download from here: http://freakshare.com/files/4bh77uz1/F7561STUD1.pdf.html

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 Web Services counterpart (WS-Security).