Although the same Process APIs are available regardless of web application, how you develop a Process application varies according to the FileNet web application (FileNet Workplace, FileNet Web Services, FileNet Open Client, or your own web application) and the platforms on which these web applications were designed to run.
The following table summarizes the platforms and frameworks for Process applications and provides links to related Help for Process Development topics.
FileNet Web Application | Platform/ Framework |
Operating Systems | Description | Related Topics |
FileNet Workplace | J2EE |
Process Engine: Windows 2000, Solaris, AIX J2EE web/ application server: Windows 2000, Solaris |
Process applications for Workplace are developed as either Java or HTML applications/applets within the J2EE MVC model, where, for example, the "C"ontroller layer includes a controller bean and a JSP that maps events to the "M"odel, which is comprised of beans that provide data to the "V"iew component, consisting of a UI JSP and UI bean that render the XML data returned from the Content and Process Engines. An XSL transformation object applies XSLT to render the XML and return an HTML page in response to the client browser's HTTP request. |
Process Engine Architecture/ Components - FileNet Workplace Developer Prerequisites: Required Tools and Languages |
FileNet Web Services | COM/ASP |
Process Engine: Windows 2000, Solaris, AIX, HP-UX Web server: Windows or Unix |
Process applications for FileNet Web Services are developed as either Java or HTML applications/applets normally hosted in ASP pages for FileNet Web Services (ActiveX) clients within the COM framework. Because the Process APIs for Process Engine services are Java, you will need to configure the JiGlue COM Bridge for your COM-based Process applications/applets. |
Process Engine Architecture/ Components - FileNet Web Services Developer Prerequisites: Required Tools and Languages Process Development Environment and Toolkits Setting Up for Process Development Process Java Applets Connectivity (PJAC) |
FileNet Open Client | ASP.NET |
Process Engine: Windows 2000, Solaris, AIX, HP-UX Web server: Windows or Unix |
Process applications for FileNet Open Client are developed as either Java or HTML applications/applets hosted in ASPX pages for open clients within the ASP.NET framework. Because the Process APIs for Process Engine services are Java, you will need to configure the JiGlue COM Bridge for your .NET-based Process applications/applets. |
Process Engine Architecture/ Components - FileNet Web Services Developer Prerequisites: Required Tools and Languages Process Development Environment and Toolkits Setting Up for Process Development Process Java Applets Connectivity (PJAC) |