This topic describes how to create one or more generic ASPs which may be used as a template for Process application ASPs.
Subtopics include:
An Active Server Page (ASP) consists of HTML-formatted text, or other content – such as images, server-side scripting (e.g., JavaScript or VBScript), and in many cases, client-side scripts as well. The ASP's HTML format provides a framework for providing dynamic content (for example, a Process application such as a Step Processor), to a client browser.
Custom ASP-hosted applications establish a session with the Process Engine through the PJAC for FileNet Web Services module. Within the ASP, you can develop a web-based Process application that accesses IDM Foundation objects for document functionality (through the JavaScript API objects: IDMWSC_Document, IDMWSC_Folder, IDMWSC_Library, and IDMWSC_StoredSearch) and/or Process Engine services for workflow functionality (via the JiGlue COM bridge and the Process Java APIs). To provide workflow functionality, you use a scripting language (like VBScript or JavaScript) in an ASP file to log on to the Process Engine, create a Process session (VWSession object), query user and work queues, retrieve and update information, etc. from a Process Engine server. Your script will typically include HTML tags, such as Form tags, to enable the user to interact via the browser and script commands that contain logic for communication with the Process Engine. Since scripting embedded in an ASP file runs on the server, only the HTML content (which may include a client-side script) is returned to the browser on the client system (the FileNet Web Services web server processes the server-side script and sends the HTML output to the client browser). Process Services use the global.asa file to initialize the application state. A single global.asa file is used for all ASP-based applications on the web server.
Note For general information on ASPs and guidelines on scripting ASPs for Process applications, see Active Server Pages (ASP) Process Scripting Overview.
One way to simplify the task of developing custom ASPs for Process applications is to create one or more generic ASPs. A generic ASP may be used as a template for Process ASPs that includes and references the appropriate FileNet Web Services and PJAC for FileNet Web Services scripts and files to create the application and initialize the application state.
To create a web application page (.asp or .htm or .html) for your Process application, use the following procedure:
Note This procedure assumes you are using an IDE or visual development tool.
At this point, you are ready to copy your generic ASP and customize it for your application.