Filenet P8 stage summary

The architecture of filenet P8 is clear, including three core components ce, PE, and AE. The core of filenet P8 is the understanding of ECM and filenet P8. It can be seen that three of the four suites of filenet P8 are based on these three core components, and the other (IM) can be independent, but it often needs to be used with other suites.

In addition to core components, filenet P8 also includes functional extensions for core systems and third-party OEM products (as described in filenet P8 PE introduction and filenet P8 ce Introduction) and custom applicationsProgram(It uses the web application development kit in AE, which is described in "filenet P8 AE Introduction ), the extensions of filenet P8 are described as follows (simple functional descriptions of these extensions are provided in "Understanding ECM and filenet P8 ):

 

The description of the above content is Abstract:

CE is object and contentmanagement services. Its components and services are as follows:

Where

PE is business processmanagement services and its components include:

AE is the UI component andapplication development services. Its components include:

The application architecture of filenet P8 is as follows:

Connectivity of filenet P8:

Some terms for understanding filenet are as follows:

Isolated region is a subdivision of the workflow database. The workflow database contains transferred workflow and all active workflow data. Work cannot be shared between different isolated regions. Use isolated regions as an appropriate organization to isolate user groups.

Connectionpoint is an isolated region number that represents a specific PE server and workflow database. In the general site preerences of workflow, we can specify the connection point name to specify isolated region for all workplace applications. These applications include process designer and process adminitrator. In a farmed environment in PE servers, connection point specifies the load alance and the isolated number. We can use Enterprise Manager to manage connection points.

Filenetp8 domain is a logical group of physical resources and Ce servers. These physical resources include object store database, full text index areas, file storage areas, and content cache areas, and Ce servers provide access to these physical resources. Each resource and each ce server belong to and belong to only one domain. Each ce server can access any resources in this domain, but cannot access resources other than this domain.

Object store is a set of services provided by Ce to access and manage documents and other objects. An ObjectStore resides on a filenet P8 domain that can contain multiple object stores.

Contentstorage area is a physical storage area of content, including file storage area, database storage area, and content cache area. The difference is that file storage area and database storage areas provide permanent storage, while content cachearea provides temporary hard disk space for a copy of the content found in file and database storage area.

Two major options for storing content: file store and database store. File store places the object (mainly attribute) in the database, and places the content it represents on the file system, while Database store stores the attributes and content in the database.

Filenetenterprise manager is the management unit of the Microsoft console for managing ce. It can access local and remote ce, access to local CE is through COM (Component Object Model), and access to remote CE is through DCOM (Distributed COM ).

The filenetenterprise manager function includes creating object stores, defining lifecycle policies, Ce events, defining classes and attributes, and locating objects.

For more terms, refer to the IBM Website:

Http://mtdoc.moratech.se/ecm_help/glossary/glossary.htm#g-a

The following is a component diagram of the dependency between some filenet components. The red lines indicate the startup sequence, and you still need to learn the incomplete and incomprehensible content.

The core APIs of CE and PE have been used when learning f005 and f009. You can click here to view them (Click here)

The next step is to familiarize yourself with API operations, build custom applications, and be proficient in applying filenet P8 products.

In this training, all the materials are in English, but Computer English is easier to learn than other English, and some translation software can be used to translate unfamiliar words in real time, so it is difficult to imagine. However, after all, the two languages have different backgrounds and are not suitable for the initial understanding process. However, as the usage increases, they gradually adapt to the situation. That is to say, if you are not familiar with it, you will gradually become familiar with it.

Learning things is also a process of getting familiar with things. But first, you must get familiar with things and get familiar with things before learning things, when I am not comfortable with it, I need to ask me if I am close to it and know if I am familiar with it. Then I will know how to do it. I need to work with it in constant practice, achieve the unity of characters.