The following table provides a checklist of prerequisites to set
up your development system(s) for Process application development. Before
starting development of a custom Process applet/application, ensure 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 Open Client Web application you plan to use, 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 (e.g., ASP.NET), and FileNet Web application (Open
Client).
If you are new to Process development, it is recommended that you
review the introduction to Process applications in the Help for
Process Developers on the Process Documentation for FileNet
Image Manager CD 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 Open Client.
Process Functional Expansions/Add-ons.
Introduction to Process Applications in Help for Process
Developers on the Process Documentation for FileNet Image
Manager CD.
|
2.
|
Set up your development system(s) to mirror your production environment.
Install FileNet Open Client and 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 Library 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 Open Client
and/or FileNet Web Services, 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:
- PJAC for FileNet Web Services
- PJAC for Open Client
- Stand-alone PJAC install if you plan to run Process applications
without a FileNet Web application.
|
PJAC Installation Guide.
Process Java Applets Connectivity (PJAC).
|
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 server in your
development setup. |
Configuring the Java Runtime
Environment (JRE).
|
5.
|
Determine whether you plan to develop HTML (ASPX-based) 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 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.
|
See the following topics in Help for Process Developers
on the Process Documentation for FileNet Image Manager CD:
Developing Custom Java Processors - Applications vs. Applets.
Process Development Environment and Toolkits.
|
6.
|
Install and review the contents
of the Process Development Environment for FileNet Open Client. |
Installing the Process Development
Environment - FileNet Open Client.
|
7.
|
Configure and register the JiGlue COM Bridge (required for all
Process applications with FileNet Open Client). 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.
Using JiGlue with ASP.NET
- Issues and Guidelines.
Configuring the JiGlue
COM Bridge.
|
8.
|
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 topic in Help for Process Developers on the Process
Documentation for FileNet Image Manager CD. |
9.
|
Before you start, it is recommended that you familiarize yourself
with:
- Open Client Process Services Web footprint directory structure.
- Process Services and Open Client files referenced by the sample
or default Process applications provided with the Process Development
Environment for Open Client; review the FileNet Open Client files
and the PJAC for FileNet Open Client files referenced by the out-of-the-box
Step Processor applications.
- Process Java APIs and the Process API samples (applicable regardless
of which FileNet Web application you use; the Process API samples
provide guidance on how to use each API class).
You are now ready to develop your application.
|
Help for Process Developers on the Process Documentation
for FileNet Image Manager CD.
Process Services Directory
Contents and Structure.
Directories Containing Resources
and Controls Used By Process.
Process Java Applets Connectivity (PJAC).
PJAC Files for Open Client.
The topics: Using the Process Java API Classes and Process
API Samples Overview in Help for Process Developers on
the Process Documentation for FileNet Image Manager CD..
|