Regardless of which FileNet web application you are using, you will need to consider whether to develop a custom application as an HTML or a Java application (for information, see Developing HTML and Java Step Processors). In addition, for Java applications, you will need to consider whether to develop your custom Step Processor, Launch Step Processor, User Inbox/Task Page/Personal Work Manager, Tracker, etc. as an application or an applet (for information, see Developing Java Step Processors - Applications vs. Applets).
Certain basic considerations and tasks are common to each type of Process application, while others are specific to the FileNet web application you are using (FileNet Workplace, FileNet Web Services, or FileNet Open Client). For example, there are certain basic operations that are required for every Step Processor application (such as logging in to the Process Engine and establishing a Process session, querying queues for Step Elements or Work Objects, updating workflow data, etc.) regardless of whether you develop it as an HTML or a Java application or applet and regardless of whether you are using FileNet Workplace, FileNet Web Services, or FileNet Open Client as your web application. On the other hand, how you create, extend, and deploy your application will obviously vary depending upon whether or not your application is COM-based (requiring the JiGlue COM Bridge), whether you are hosting the application in JSP, ASP, or ASPX, and so on.
Major subtopics include: