The following table provides a checklist of prerequisites for setting up your development system(s) for Process application development. Before starting development of a custom Process applet/application, be sure you have completed all relevant steps for your environment.
Step
|
Task | For information, see: |
1.
|
Review Process development conceptual and planning information, including the Process Engine architecture and components for your FileNet web application. Be sure you understand which Process-related components (FileNet and non-FileNet) you will need to have available for the FileNet web application you plan to use (Workplace, FileNet Web Services, or FileNet Open Client), how these components interface, which FileNet functional expansions and add-ons you plan to implement (if any), which DBMS you plan to use for the underlying Process database, which Process applications you plan to develop, and which tools and languages are prerequisites for application development within the context of your operating system, platform (J2EE, ASP, ASP.NET), and FileNet web application. If you are new to Process development, it is recommended that you review the introduction to Process applications and understand the basics of how to develop a Process solution, including planning and designing the business process and workflows, determining which users and departments are to perform which steps in the workflow, whether business rules are to be applied and if so, which ones, and so on. |
Process Engine Architecture/Components - FileNet Workplace Process Engine Architecture/Components - FileNet Web Services Process Engine Architecture/Components
- FileNet Open Client Process Functional Expansions/Add-ons Developer Prerequisites: Required Tools and Languages Development/Production Environments/Platforms |
2.
|
Set up your development system(s) to mirror your production environment. Install the FileNet P8 Baseline Platform or FileNet Image Manager, including the Process Engine (remembering to start the Process Engine Pooled Process Manager [PPM] and to initialize an isolated region for Process development separate from any production isolated regions and to start a local Process Router), and if applicable, the FileNet Content Engine/Content Services and/or Image Services components, plus those FileNet Functional Expansions and optional add-ons you plan to use. Be sure to include existing applications, legacy, and third-party products that are to be interfaced with the workflow or from which Process applications are to be accessed, and representative clients. |
Process Installation Guide: Installation Tasks.
|
3.
|
If you are developing Process applications for FileNet Web Services and/or FileNet Open Client, or do not plan to use any FileNet-provided web application, you must run the Process Java Applets Connectivity (PJAC) installer. The PJAC installer installs the PJAC components that provide connectivity to the Process Engine. These are selectable, as follows:
|
|
4.
|
Set up the Java Runtime Environment (JRE) on all Process Engine servers (if there are more than one), on each client, and also, if used, on the Process Analyzer and Process Simulator in your development setup. | |
5.
|
Determine whether you plan to develop HTML or Java applets/applications or both. If developing in Java, determine whether to develop your Java applications, such as Step Processors, as applets or applications. Review the Process Development Environment (provided by FileNet for developers). Also review the different FileNet developer toolkits to determine which ones are appropriate for your application development depending upon which FileNet web application you are using and whether you are developing an HTML or a Java application/applet. |
Developing Custom Java Processors - Applications vs. Applets. |
6.
|
Install and review the contents of the appropriate Process Development Environment for your FileNet web application (FileNet Workplace, FileNet Web Services, or FileNet Open Client). |
Installing the Process Development Environment - FileNet Workplace. Installing the Process Development Environment - FileNet Web Services. Installing the Process Development Environment - FileNet Open Client. |
7.
|
If you are developing COM-based Process applications, you will need to set up the JiGlue COM Bridge (required for all Process applications with FileNet Web Services and FileNet Open Client; with FileNet Workplace only required for a COM-based application). If you have not used the JiGlue COM Bridge before, there are a number of JiGlue-related programming guidelines and issues you should review before starting development. Note If you have installed PJAC, you must configure and register the JiGlue COM Bridge. |
Setting Up for JiGlue COM Development. Developing with the JiGlue COM Bridge (provides guidelines, examples, and issues). |
8.
|
If you are developing ASP-hosted Process applications for FileNet Web Services (with ActiveX clients), you will need to set up your system for Process ASP development. If you are using Visual InterDev or Visual Studio to develop your application, you will need to create a new Process project. | Setting Up and Developing for ASP. |
9.
|
If you are developing Process applications for FileNet Open Client on the ASP.NET platform, you will need to set up your system for Process ASPX-hosted development. Be aware that there are a number of issues associated with developing ASPX pages with the JiGlue COM Bridge. | |
10.
|
Before you start, it is recommended that you familiarize yourself with the:
At this point, you are ready to begin developing your application. |
Process Services Directory Structures (for FileNet Workplace, FileNet Web Services, and FileNet Open Client). Process Java Applets Connectivity (PJAC). |