Process Services Directory Structure - FileNet Open Client

Process Engine connectivity with the FileNet Open Client web application is provided by the Process Java Applets and Connectivity (PJAC) component. PJAC enables the Process Engine to work with FileNet Open Client to provide workflow capabilities. Much of this workflow-related functionality relies on the FileNet Open Client architecture and directory structure (see Process Engine Architecture/Components - FileNet Open Client). When they are installed together the Process-related resources of FileNet Open Client, PJAC, and the Process Engine services may be collectively referred to as "Process Services" (this term is loosely used).

During Open Client installation, a Process Services-specific directory structure (...\eprocess) is created as a subdirectory of the overall FileNet Open Client directory. The Open Client directory name and location is user-selectable (the default is the ...\Program Files\FileNet\IDM\Web\FNOpenClient directory).

The FileNet Open Client ...\FNOpenClient web footprint directory contains resources and controls that are used by Process applications, including the out-of-the-box Step Processor applets supplied with your Process Development Environment (for information, see Installing the Process Development Environment - FileNet Open Client). In addition to the general (non-Process-related) Open Client subdirectories, the FileNet Open Client ...\FNOpenClient web footprint directory — or its user-selectable equivalent — also contains a variety of files to provide general Open Client functionality, such as a batch file (build.bat), the Open Client Main.aspx file, a makefile, a license .licx file, a generic Cascading Style Sheet (FnStyleSheet.css) for the HTML pages, and so on, which can be used by Process applications.

Note For additional information on Process Services and Open Client directory structure and files, see the following Help documentation: