Process Engine connectivity with FileNet Web Services is provided by the Process Java Applets and Connectivity (PJAC) component. PJAC enables the Process Engine to work with FileNet Web Services to provide workflow capabilities. Much of this workflow-related functionality relies on the FileNet Web Services architecture and directory structure (see Process Engine Architecture/Components - FileNet Web Services). When they are installed together the Process-related FileNet Web Services components and PJAC modules may be collectively referred to as "Process Services" (this term is loosely used and may, or may not, also include Process Engine services; e.g., PPM).
This topic describes the Process Services-related directory structure within the overall FileNet Web Services directory structure. An understanding of this directory structure is important for Process application development with the FileNet Web Services web application, particularly if you intend to develop an HTML (ASP) application, or extend an existing HTML application, such as the default HTML Step Processor or Launch Step Processor (see Using the FileNet Web Services HTML Step Processor Toolkit) provided with your installation.
Note The directory structure shown here is relative to the <drive>...\Program Files\FileNet\IDM\Web\IDMWS directory on the FileNet Web Services server.
Directory |
Contents |
---|---|
\_ScriptLibrary |
Contains files used for Microsoft Remote Scripting. These library files have been modified by FileNet. |
\Application |
Contains the modules used by Process Services, ASP files used to create the web application, and related Process application panes. Additionally, this directory also contains the on-line Help for both FileNet Web Services and PJAC. |
\CSS |
Contains Cascading Style Sheets (CSS) used by the default HTML Step and Launch Step Processor applications. The CSS's control the text formatting and layout of the HTML content for the default applications. If you are developing a new user interface, you may use the CSS's in this subdirectory, or develop your own. |
\Images |
Contains many of the .GIF-formatted icon graphics used by FileNet Web Services applications (Process and non-Process), including the default email notifications. Images (.GIF files) used by Process Services applications, such as those used in the default HTML Step and Launch Step Processors, are located in the \Redist\WF_Html_Toolkit\Images subdirectory (see below). |
\Redist |
Contains sub-folders which contain redistributeable components (such as ASP, HTML, .JS, and .JAR files). These components provide the core functionality for Process Services. Also contains the default Java and HTML Step and Launch Step Processors included with the Process Development Environment (for additional information, see Installing the Process Development Environment - FileNet Web Services). The following directories were added as a part of PJAC for FileNet Web Services installation:
The remaining directories were created during the FileNet Web Services installation:
Most of the ASP files in the above folders contain #include statements. You will need to examine includes at the beginning of each file to determine dependencies. |
\WSAPI |
Contains ASP files that implement the FileNet Web Services API objects and work with the FileNet IDM Object automation. PJAC for FileNet Web Services extends some of the files in this directory. |
\WSCAPI |
Contains the FileNet Web Services ASP object implementation files and client scripts (.JS) files that are referenced by Process applications, such as Step Processors. PJAC for FileNet Web Services extends some of the files in this directory. Both the default and any custom HTML Process applications will need to reference some or all of these files. For details, see FileNet Web Services Files Referenced by Process Applications. |
The following files are in the root <drive>...\Program Files\FileNet\IDM\Web\IDMWS directory and not in a subdirectory. When developing a Process application you will, in all likelihood, be adding new directories and files. You can reuse the ASP pages, JavaScripts, modules, images, and style sheets available in the directories listed above. However, you should use all of the files in the root directory (do not modify; use as shipped), except for the following, which may be modified:
You can modify the files listed above as needed. If you create your own web application, it is recommended that you locate your start page at the same level as the home.asp file. If you want to keep the home.asp and you have created a different top level page for your web application, then you will need to change the redirection command to reference your new page. |