Post-Installation Tasks: Windows

Post-Installation Overview

As part of post-installation, you need to verify the installation or to perform the following general tasks, some of which are based on the architecture of your application, and some of which the installer performs for you. This chapter provides the steps required for each of these general tasks:

Obtaining Panther Licenses

Your Panther software components (client, application server engine, and web application broker) may require licenses. The Panther installation includes a Start-up License, provided on a diskette, that lets you use the software immediately. The temporary license, license.dat, is installed in the licenses subdirectory of the Panther installation directory. Because the temporary license will expire, you must contact the Prolifics License Desk to receive your permanent license file. You can reach the License Desk by fax at (212) 608-6753 or by e-mail at license@prolifics.com.

During installation, the setup program prompts you to provide the information required by the License Desk for obtaining your permanent license file. It also generates license request files (prodev.lcl for the client, proserv.lcl for the application server engine, and proweb.lcl for the web application broker) in the licenses subdirectory of your Panther installation directory.

How to Obtain and Install the License File

  1. Submit the license request files to the Prolifics License Desk. The License Desk returns the password-enabled file via the requested method specified during setup.
  2. Complete the following step.

If you received a license file


Via e-mail

Copy it to the licenses subdirectory on the machine where the software component is installed. Go to Step -4.-

Via fax or mail

Copy the license request files, .lcl, to .lic. Go to Step -3.-

  1. Using a text editor, update prodev.lic , proserv.lic, and proweb.lic with the information provided in the password-enabled file that you received.
  1. Create the license.dat. Choose Start=>Run, and type:

How Panther Locates the License File

Panther searches for the license file in the following order:

Configuring the Client

A Panther client provides the development environment required to build two-tier, three-tier, COM, and/or EJB applications. The environment must contain properly set application variables in order to run Panther. To set up the development environment, complete the following platform-specific tasks. Refer to page -#- in the Developer's Guide for more details on setting up the client environment.

How to Configure Each Client

Set the following variables in the following initialization files: prol4w32.ini for Panther and mbedit32.ini for the menu bar editor.

How to Verify a Client Installation

Select Panther from the Start menu or double-click on the Panther icon in the Panther folder created during installation.

Configuring the Application Server Engine

If necessary, configure the application server engine. For more information on setting up the application server engine for Panther for IBM WebSphere, refer to page -#- in the WebSphere Developer's Studio.

Verifying the Web Application Broker

To ensure that your Panther application can be viewed on a web browser, complete the following platform-specific steps, most of which are applied as part of the Panther setup program. For further information on configuring web applications, refer to page -#- in the Web Developer's Guide.

Confirm that the following web application broker executables reside in your HTTP server's CGI, NSAPI, or ISAPI program directory; otherwise, copy them from the Panther util subdirectory:

Creating a Web Application

Panther provides the Panther Web Setup Manager to guide you through configuring your customized web application. For more information, refer to page -#- in the Web Developer's Guide. Choose Panther Web Setup Manager on the Start Menu.

How to Verify your Web Application Broker Configuration and Licensing

Create a new web application to verify the web application broker installation.

  1. Configure a new application by running Web Setup Manager from the Start Menu.
  2. Start the web application broker from the command line of the util subdirectory by typing:
  1. Run the application in your browser.
  1. Stop the web application broker from the command line of the util subdirectory by typing

Verifying the COM Development Environment

Most of the necessary configuration for COM development is done by the installer. COM components must be registered on a PC before they can be accessed by a COM application. This COM component server can be:

Check that necessary software has been installed:

  1. Confirm that COM and DCOM have been installed on a Windows 98 machine.
  2. Confirm that MTS has been installed on the Windows NT/2000 server.
  3. Check that the appropriate files for creating and deploying COM components have been installed.

For more information on deploying COM components with COM/DCOM, refer to page -#- in the COM/MTS Guide.

For more information on deploying COM components with MTS, refer to page -#- in the COM/MTS Guide. For more information on MTS and creating or exporting component packages, see Microsoft's MTS Documentation.

Creating New Prolifics Executables

As part of the Panther installation package, a set of standard Prolifics executables is provided for the client and the web application server, along with a template COM DLL. Depending on your configuration and on the platform and database being used, you might need to create new executables. Specifically, a new executable is required if you are using a database for which DLLs are not provided or if you are adding C functions to your Panther application.

Alternatively, Prolifics distributes workspace and project files for use with Microsoft Developer Studio. Instructions on how to use the workspace are provided in Appendix -B-.

For more information on creating new client and web application executables, or modifying the Panther COM template DLL, refer to Appendix -#- in the COM/MTS Guide.

Reviewing Sample Applications

Before you begin building your applications, you might want to review the sample applications. The following sample applications are delivered with the Panther software.

How to Configure Web Samples

  1. Confirm that the following initialization file resides in your Windows system directory; otherwise, copy it from the Panther config subdirectory:
  1. Check jwsamp.ini in the Windows directory for the correct setting for each of the following variables:
  1. Select either Start Panther Gallery Server or View Panther Gallery Samples from the Start menu.
  2. Choose Stop Panther Gallery Server on the Start Menu when you are finished.


The information in this section provides you with guidance when you encounter error messages. The messages you may receive may be categorized as follows: graph functionality, Windows PATH settings, or online manuals.

Graph Functionality-Related Messages

Panther's graph capabilities rely upon external programs (for example, DLLs); therefore, it is possible for Panther to be working properly except for the business graph component. If you have problems with the graph functionality, check the following:

Windows PATH Settings-Related Messages

If you are upgrading from JAM or Prolifics, remember that Panther's util directory must be on your PATH. Normally, this is not an issue because the installation process inserts the Panther util directory at the beginning of the PATH variable. However, the PATH might contain the older util directory. If this is the case, manually edit the PATH specification in the autoexec.bat file to remove the older util directory.

Online Manuals-Related Messages

Panther's online manuals are in PDF and HTML format, and require Adobe Acrobat Reader and a web browser, respectively, to view them. Version 4 or greater of Internet Explorer or Netscape is recommended. To verify that you can access the online documents, view the documents.

Installed documents are located in the following directory.


The documents on the Windows documentation CD are located in the following directory.