Creating a Generic ASP for Process Services

This topic describes how to create one or more generic ASPs which may be used as a template for Process application ASPs.

Subtopics include:

Generic Process ASPs

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.

Creating a Generic ASP

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.

  1. If you are using a visual development tool and you have not already done so, open Visual Studio or Visual InterDev.
  2. Locate and open your new project (assumes you have already created the project; if not, for information see Creating a New Process Project in Visual InterDev or Visual Studio).
  3. Highlight the bolded project site address in the Project Explorer pane (for example, your_webserver/your_webproject_name).
  4. From the menu bar, select Project. From the pull-down list, select Add Item.
  5. With Web Projects Files highlighted, select the ASP Page icon. Alternately, if you want to add an HTML page, select the HTML Page icon.
  6. In the Name field, enter the name for your new page. (The .asp or .htm file extension is appended to the name automatically.)
  7. Click Open.
  8. Your new page displays in the Project Explorer pane; file contents display in the main development pane (in the source view).
  9. Include and/or reference the appropriate JS and ASP files in your ASP or HTML page. For details on which files to include and why, see:
  10. Include the appropriate HTML and scripting code. If you require user interaction, create a generic HTML form so the user can enter the necessary information. The ASP application can process the user input (for example, a request for queue names) and provide the appropriate information to the Process Engine server.
  11. Save your ASP page.
  12. Verify or set required web directory permissions to ensure your ASP's access to URLs and COM components and so that your ASP can execute embedded or referenced scripts; for details, see Setting Web Server Directory Permissions.

    At this point, you are ready to copy your generic ASP and customize it for your application.