Set up an ASP eProcess Services Development System

Panagon eProcess does not require that you use Visual InterDev to develop new or modify existing ASP files; however, Visual InterDev provides a robust ASP development environment. This topic describes how to use Microsoft Visual InterDev to create a new solution, add the necessary Panagon Web WorkFlo components, and begin developing for eProcess Services in an ASP environment.

Note This section covers developing for the ASP environment. For information on developing eProcess for the ASP.NET framework, see the "Developing for eProcess Open Client" section in the Panagon Open Client Developer's Guide.

One alternative to using an IDE or ASP development tool, like Visual InterDev, is to work directly in the <drive>...\Program Files\FileNET\IDM\Web\IDMWS directory structure on your eProcess Services web server. If you know HTML and ASP and you want to make only minor changes to specific files, working in the directory structure may be the simplest approach. (Since you will be working in an active web server directory structure, it is good practice to make a fallback copy of the directory before you start). If you are developing a larger application with multiple changes across many files, you should consider using a more sophisticated development tool, such as an IDE.

These procedures assume you have a WorkFlo Services server and a web server dedicated to development and configured with the following:

Note Refer to the Web Server setup section of the Panagon Web Administrator's Help and the Configuration section of the IDM Web Administrator's Help for installation requirements.

Additionally, these procedures assume you will be developing your ASP-based applications on a development system, rather than a production web server. In order to remotely develop your application, using Visual InterDev, you must install the FrontPage Extensions. If you choose develop your application directly on your production web server, you need not install the FrontPage Extensions. Refer to the Panagon eProcess Services architecture topic for more detailed information on the server configuration.

Note If you have not already installed IIS on your Windows NT Server, refer to the appropriate Microsoft documentation for the proper installation sequence. For information on installing Panagon Web Services, refer to the IDM Web Administrator's Help help.

Perform the following general steps to set up a Panagon Web WorkFlo server for development:

  1. If you have not already done so, install the Panagon Web Services Web Application 3.x. (Refer to the Web Server setup section of the Panagon Web Administrator's Help for more information on installing Web Services and the Web Application.)
  2. Using the IDM Configure application, add at least one library to your server. Refer to the Configuration section of the IDM Web Administrator's Help for more information on configuring your server to access Image Services (IS) and Content Services (CS) libraries. (If desired, eProcess can be configured without a requirement for Content Services library access. For information on configuring eProcess without Content Services, refer to the Panagon WorkFlo Services Installation Handbook.)
  3. Install the Web WorkFlo Services software on your web server. (Refer to the Panagon Web WorkFlo Installation Handbook for installation instructions.)
  4. On your WorkFlo Services server, configure the administration and user accounts to match your expected implementation. (Refer to the Help for eProcess Administrators for configuration instructions.)
  5. Start the eProcess Router and PPM processes on your workflow server and web server (respectively).
  6. Using a web browser (on a client system), verify that you can reach the Panagon Web Services home page by entering a command similar to the following address:

http://<web server name>/idmws/home.asp

where <web server name> is the host name of the server running IIS.

  1. Click the eProcess bar in the left pane.
  2. If the client system does not have the correct ActiveX components, the browser will be redirected to the client ActiveX component download page automatically. Depending on the client, you might need to reboot after installing the ActiveX components. Additionally, if the client system does not have the appropriate Java Runtime Environment installed (for details, see Panagon eProcess Services Architecture), the JRE will download from the server automatically the first time the client accesses the server.

You are ready to create a new solution in Visual InterDev.