Introduction to filenet P8 AE

Shows the services and applications of the application engine:

The application engine includes the following services and applications:

The application engine is the filenet P8 platform component that leads workplace network applications, workplace Java applications, flow engine routers, and application development tools. It is the presentation layer of processes and content. The application engine provides protection for user identification between workplace and content engine, and provides SSL security measures (IF configured ).

1. Workplace

This is an end-user network application software that provides access to file management and is closely integrated with the Business Process Management Function of filenet P8. Workplace also supports extended filenet P8 functions, such as form management, record management, and portals.

The workplace is built using the web application toolkit of Hainan University, and runs in the Web iner on the j2ezone application server.

Workplace uses XSL to convert many user interface elements, such as query results and folder content. Most of the functions provided by workplace are zero-download HTML, which can be run on any platform with a large number of browser products. Advanced graphical functions are provided in the form of Java Applet, including: Process designer, Process configuration console, process administrator, situation design, situation console, search design and release design.

2. Integration of Microsoft Office)

Allows you to easily manage Office documents and Outlook mail Information in the filenet P8 content library. You can store, search, and retrieve documents, emails, and attachments directly from the Microsoft Office directory. In addition to protecting and transforming office documents, you can also browse Object Storage and embed properties in Word and Excel documents. You can also use the input template to add documents to an object storage and start the approval workflow.

3. Component Integrator)

Provides a device for automatic processing without the need for customized programming. The component integrator processes the Java class import and processes the communication between the process engine and the interface. For example, in a workflow step, you can call the Java class to request services from some customer entities (such as third-party vendors. The workflow designer of the Graphic Process designer can directly call Java classes without programming. The component integrator includes many adapters, which are interfaces for communication between Process Engine events and external entities (such as Java objects. The adapter interacts with various components from the workflow step. (Java and javatm messageservice (JMS) adapters are provided to call Java components and add information to information queues. Here is just a Java Adapter .)

4. content and process Java API (content andprocess Java API)

A Java class extension set used to compile out-of-the-box applications for custom applications and extensions. These classes provide programmable interfaces for interaction between the content and the process engine. Developers can use these APIs to create different applications, including those based on j2efe-webcontainer (Java Server pagestm and assumervletstm), Enterprise JavaBeans (EJB) container, or discrete j2se Java applications.

5. Web application toolkit)

Provides a scalable framework and Reusable Modules to build network applications. The toolkit allows program developers to access the Content Engine, process engine, and third-party backend servers. Provides behavior and data structures for other features of identity, event scheduling, status information, parameter selection, localization, and solid scalable applications. In addition, the reusable User Interface Component Mode of the Toolkit creates a stable HTML-based application user interface, which does not need or almost does not need DHTML/JavaScript. Microsoft has developed many web applications based on its toolkit, including filenet p8workplace and record management.

6. application integration toolkit)

The Application Integration kit is a full-featured API that allows third parties to integrate their Microsoft Windows-based customer applications with workplace. The toolkit provides integration with Microsoft Excel, PowerPoint, word, and outlook. This toolkit is also used by the filenet eformsdesigner electronic form design software. Customers and partners can use this Toolkit (including reusable user interfaces) to integrate with other applications without coding.

The toolkit contains a set of COM Servers installed on the Windows client and the assumervlets running on the J2EE application server. Integrationservlet-it supports requests from fat client applications and network-based thin clients-Provides reusable workplace JSP pages and Wizard for the Toolkit. These components provide developers with complete content management functions, including interactive user interfaces.

7. Application Integration expressaddin (applicationintegration expressaddin)

Application Integration expressaddin is a developer tool in the application integration toolkit. It enables the application integration infrastructure to be quickly integrated into third-party applications (such as Microsoft Office ).

This tool is a COM server that defines the input and output interfaces. It supports two-way communication between the customer application and application integration framework. Although some aspects are similar to those of the application integration toolkit, expressaddin uses a large number of infrastructure encodings, which can significantly reduce the burden on integrated developers. Expressaddin also comes with sample applications to demonstrate how to use expressaddin to integrate third-party applications and application integration infrastructure. Developers can customize sample codes, quickly integrate their applications into the framework, and easily customize the integration to meet specific needs.

8. integrationservlet

Integrationservlet is an application engine service, many applications use it to access electronic forms, collect content by entering templates, check content, access work tasks and step processors, and select objects by browsing and/or searching. Integrationservlet supports requests from fat client applications and network-based thin clients. (Network-based applications must be built using the network application toolkit. The fat client must be built using the application integration toolkit .)

9. Workplace configuration and customization)

Workplace can be configured by modifying site and user parameters to meet application needs. Workplace can be customized by modifying text input files (such as XML) or modifying open source code. These methods are used in the configuration and customization examples highlighted below.