1. Manuals
  2. Brands
  3. Prolifics Manuals
  4. Software
  5. Panter 2Tier
  6. Installation manual

Prolifics Panter 2Tier Installation Manual

2–tier installation
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
2–Tier Installation
April 1999

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Panter 2Tier and is the answer not in the manual?

Questions and answers

Summary of Contents for Prolifics Panter 2Tier

  • Page 1 2–Tier Installation April 1999...
  • Page 2 DynaText is a registered trademark of Inso Corporation. FLEXlm is a registered trademark of GLOBEtrotter Software, Inc. HP is a trademark of Hewlett-Packard Company. INFORMIX and C-ISAM are registered trademarks of Informix Software, Inc. IBM, DB2, and RISC System/6000 are registered trademarks and CICS is a trademark of International Business Machines Corporation.

  • Page 3: Table Of Contents

    About this Guide ..........Organization of this Guide Conventions Text Conventions...
  • Page 4 Installation Procedure Installing a Database Driver Client: Post-Installation for Windows Post-Installation Overview Create New Prolifics Executables Configure the Client Environment Verify the Installation Look at Sample Applications Troubleshooting Chapter 3 Web Application Server: Windows Web Application Server: Pre-Installation for Windows Before Installing Web Application Server: Post-Installation for Windows Post-Installation Overview...
  • Page 5 Web Application Server: Post-Installation for UNIX Post-Installation Overview Configure the Web Application Server Environment Creating Your Web Application Verify the Installation Look at Samples Appendix A Notes for Microsoft Windows DLLs for JPEG Decoding Environment Space Visual C++ Floating-Point Options Using Prolifics Utilities Appendix B Initialization and Databases...

  • Page 6: About This Guide

    The Installation Guide contains complete instructions for installing Panther and for setting up the initial configuration on machines for the supported platforms. It also discusses system requirements, contents of the installation package, licensing, and linking in databases. The guide assumes that the person doing the installation is a system administrator or someone familiar with UNIX and Windows operating systems.

  • Page 7: Conventions

    Conventions In addition, appendices provide information on modifications you can make to the distributed initialization files, background information on licensing including license utility programs, and the format and content of the password-enabled license file. Conventions The following typographical and terminological conventions are used in this guide: Text Conventions Monospace (fixed-spaced) text is used to indicate: expression...

  • Page 8: Panther Documentation

    Panther Documentation Alt+A Physical keys are indicated with initial capitalization, and keys that you press simultaneously are connected with a plus sign. Panther Documentation The Panther documentation set includes the following guides and reference material (available as indicated), as illustrated in Figure NO TAG: Installation —...
  • Page 9 Panther Documentation Database Drivers — Instructions for using Prolifics’s database drivers. Each driver has its own section containing the information specific to that relational database engine. Configuration — Instructions for configuring Prolifics on various platforms and to your preferences. Also includes information on GUI resource and initialization files.

  • Page 10: Online Documentation

    MTS Guide — Instructions for building and deploying COM components in your Prolifics three-tier application. WebLogic Enterprise Guide — Instructions for building and deploying WebLogic Enterprise components in your Prolifics three-tier application. Quick Reference — Easy reference to all Prolifics properties and definitions associated with application objects.
  • Page 11 The annotations are stored in the directory location specified in your (Motif) or Print capability You can print any section of the documentation or its table of contents to a PostScript printer or file. After you choose File⇒Print: • • •...
  • Page 12 For more information on using DynaText, refer to the Using DynaText title in the Collection window. Collateral The following information is also provided with your Prolifics installation: Documentation Online README file. Additional Help Contact Prolifics for more information on the following services: Product Support Consulting Services Educational Services...

  • Page 14: Installation Checklist

    Installation Checklist Use this checklist to ensure that you complete the appropriate steps to install and configure your Prolifics development environment for the chosen architecture. Pre-Installation - Determine the application architecture. - Based on architecture, decide which components to install. - Satisfy hardware and software requirements for the components you plan to install.

  • Page 15: General Information

    In order to help you install the appropriate components, this chapter describes the contents of the Panther installation package, application architectures, and the functionality of the Prolifics software components that make up your Panther distribution. Before you begin the installation process, review the Release Notes for the latest information about Panther, including known problems.

  • Page 16: Application Architecture

    Application Architecture Database drivers for connecting to third-party relational databases, such as Oracle and Sybase. Files for C program development. Files for Java program development. License management software. Online documentation and help system; sample two-tier applications and a tutorial; and the Prolifics Gallery, which includes a variety of sample web applications.

  • Page 17: For More Information

    For More Information After Panther is installed and configured, you can refer to the online documenta- tion for information on specific topics. The preface, About this Guide, contains a suggested reading path and more information about the documentation. Refer to: Getting Started online New Features Guide New features in Panther.

  • Page 18: Client: Windows Installation

    Client: Pre-Installation for Windows This section discusses hardware and software requirements and upgrade informa- tion for Prolifics software running under Windows. Hardware and Software Requirements The full installation of the Panther development environment requires the following: 80486 or better processor; Pentium processor is recommended. A maximum of 137 MB of disk space (of which 35 is for the online documen- tation).

  • Page 19: Upgrading

    Client: Pre-Installation for Windows 32 MB of memory. Database vendor’s client and network software installed if you are using a database other than JDB. For more information, consult the database-specific release notes online. To use Java files, you must have either JDK 1.1 (Java Development Kit) or the JRE (Java Runtime Environment), or compatible versions, installed.

  • Page 20: Client: Installation For Windows

    Client: Installation for Windows These instructions apply to both first-time installations and to upgrades from previous versions of JAM and Prolifics. Before beginning the installation, review the requirements and other pre-installation steps discussed earlier in this chapter. This section discusses running the setup program to install a Prolifics client and database drivers under Windows.

  • Page 21: Installing A Database Driver

    Client: Installation for Windows Installing a Database Driver After you install the Prolifics client and or web application server on a machine, you can begin the database driver installation. To install database drivers: Insert CD-ROM. Choose Start⇒Run. In the Run dialog box, type letter of the drive from which you are installing).

  • Page 22: Microsoft Sql Server

    For more information, refer to If you don’t know your Informix version, check the release number listed in the text files provided in Informix installation. Microsoft SQL Server Windows 95/98 and NT: ODBC Windows 95/98 and NT: If your ODBC version is 2.x or earlier, choose Version 2. ODBC version 1 is compatible with version 2.
  • Page 23 Client: Installation for Windows Oracle supports two development interfaces: a C language API called OCI and an embedded SQL language, Pro*C. Most applications can use Prolifics’s OCI or Pro*C interfaces interchangeably. Typically, Prolifics developers use the OCI interface unless they are linking their own custom Pro*C functions with Prolifics. To use Oracle’s stored procedures, you must use the OCI interface.

  • Page 24: Client: Post-Installation For Windows

    Client: Post-Installation for Windows Post-Installation Overview As part of post-installation, you need to perform the following general steps for client installations, some of which are based on the architecture of your applica- tion. The details of the steps are provided in the pages that follow. Create new Prolifics executables if required.
  • Page 25 Client: Post-Installation for Windows Uncomment the appropriate database in the specific choose the correct version of your database software. For further information, refer to page 15. Type makefile command. the executable file a unique name to distinguish it from the distributed executable or others that you have built differently.

  • Page 26: Configure The Client Environment

    Linking in the If you are using a database for which DLLs are not provided, you must edit the makefile Database To include the appropriate database in your executables: Uncomment the appropriate SOFTWARE By default, JDB is uncommented. If you choose another database, you can leave JDB uncommented (and include it in your executable), or you can comment out JDB and include only your database.

  • Page 27: Verify The Installation

    Client: Post-Installation for Windows JAVA_HOME and event handlers and need to be set to the location where your Java classes sit. Additionally, you can change the defaults for SMJAVAFACTORY Developer ’s Guide. Verify the Installation After you install and configure the Prolifics client, you should verify that it starts up properly.
  • Page 28 Ensure that Windows directory and contains the correct paths in it for the Ensure that directory along the Windows PATH If you are upgrading from JAM or an earlier version of Prolifics, remember that Prolifics’s Settings since the installation process inserts the Prolifics of the PATH this is the case, manually edit the...

  • Page 29: Web Application Server: Windows

    Web Application Server: Windows This chapter contains information for installing the Prolifics web application server. For information about installing Prolifics client software, refer to page 7. Web Application Server: Pre-Installation for Windows Web application servers are only supported on Windows NT, version 4 or higher. To install a web application server, an HTTP server must be configured and running on the same system.

  • Page 30: Before Installing

    Web Application Server: Pre-Installation for Windows If you are installing a Prolifics client and web application server on the same Windows NT machine, it is recommended that you install them in the same directory. This allows them to share common environment settings that point to the location of required files.

  • Page 31: Web Application Server: Post-Installation For Windows

    Web Application Server: Post-Installation for Windows Refer to page 9 for information on running the setup program to install Prolifics software under Windows. You will be prompted during the installation process for the Start-up License, which is provided on a separate floppy disk. If you install the web application server on a separate machine from Prolifics client software, you must also install the database drivers on that machine.

  • Page 32: Installing The License File

    Web Application Server: Post-Installation for Windows During installation, the setup program prompted you to provide the License Desk with the appropriate information to obtain your permanent license file. It also generated license request files ( Prolifics installation directory for each component installed on a given machine. To obtain the license file: Submit the license request file (for each component on a given machine) to the Prolifics License Desk.

  • Page 33: Configure The Web Application Server Environment

    Create the Choose Start⇒Run, and type: SMBASE\licenses\create_license Location of the Prolifics searches for the license file in the following order: License File The pathname given by the setting of prol4w32.ini The pathname given by the initialization. The pathname given by the license.dat (recommended location).

  • Page 34: Creating A Web Application

    Web Application Server: Post-Installation for Windows • • • • • Creating a Web Prolifics provides the Prolifics Web Setup Manager to guide you through configuring your customized web application. For more information, refer to the Application Web Developer’s Guide. Choose Prolifics Web Setup Manager on the Start Menu. Verify the Installation After you install and configure the Prolifics web application server, you should verify that it starts up properly on web application server machines.

  • Page 35: Look At Samples

    Run the application in your browser: http://serverName/program_directory/applicationName If you get the message “No Service Requested!” you were successful. Look at Samples Before you begin building your applications, you might want to look at the following sample applications: QuickStart QuickStart provides step-by-step instructions on building and deploying sample applications on the web.

  • Page 36: Client: Unix Installation

    Client: Pre-Installation for UNIX This section discusses issues to consider before installing Panther on UNIX. They are: Hardware and software requirements. File ownership and protection. Location of files. For web application development, refer to page 43 for information about installing a Prolifics web application server.

  • Page 37: File Ownership And Protection

    Client: Pre-Installation for UNIX Running Prolifics under character mode has no special requirements. The supported version of Motif for AIX 4.3, HPUX 11, and Solaris 7 is Motif 2.1; for all other platforms, it is Motif 1.2.x. For information on obtaining your Motif version number, refer to page 41. Database vendor’s client and network software if you are using a database other than JDB.

  • Page 38: Determine File Location

    Client: Pre-Installation for UNIX Determine File Location After deciding who is going to own the Prolifics files ( or a dummy login ID), root determine where they will be installed (referred to as the Prolifics installation directory or ). Once this directory is set up, do not change it, since users SMBASE are likely to embed the directory name in makefiles, shell scripts, and so forth.

  • Page 39: Client: Installation For Unix

    Client: Installation for UNIX Client: Installation for UNIX These instructions apply to both first-time installations and to upgrades from previous versions of JAM and Prolifics. Before beginning the installation, review the requirements and other pre-installation steps discussed earlier in this chapter. This section discusses installing a Prolifics client, database drivers (if necessary), and the setup requirements for a UNIX client.

  • Page 40: Configuring The Installation

    Mount the CD-ROM device as /usr/prolifics distribution, type: zcat < /cdrom/CompressedTarFilename | tar –xvf – On HPUX, type: zcat < /cdrom/”CompressedTarFilename“ | tar –xvf – Filenames for the Panther distribution are: Filename prlstd2t400.tar.Z prlstdwb400.tar.Z Two-tier Web Application Server 400.tar.Z When Prolifics software is loaded, your normal prompt displays. Configuring the Installation After you copy the distribution from the tape, run the setup program to configure your installation.

  • Page 41: Additional Procedures

    Client: Installation for UNIX while your request for a permanent license is being processed. The Start-up License is provided on a PC floppy disk and on paper. If you wish to install the license from the PC floppy disk, you may need to mount the floppy on another computer and then transfer the Start-up License file to the computer on which you are installing Prolifics software, using a transfer file utility such as ftp.

  • Page 42: Client: Post-Installation For Unix

    Client: Post-Installation for UNIX After successfully installing Prolifics software, there are several post-installation steps required to start using Prolifics. This chapter discusses licensing, building Prolifics executables, setting up the environment for each of the Prolifics components installed, and post-installation issues and troubleshooting tips. Post-Installation Overview As part of post-installation, you need to perform the following general steps, some of which are based on the architecture of your application.
  • Page 43 Client: Post-Installation for UNIX To obtain the license file: Submit the license request file (for each component on a given machine) to the Prolifics License Desk. The License Desk returns the password-enabled file for each component on a given machine via the requested method (as specified during setup).
  • Page 44 Note: After installing the license, if your environment has an old CENSE_FILE Bourne or Korn shell: C Shell: Or you can explicitly set it to the license file. Location of the Prolifics searches for the license file in the following order: License File The pathname given by the initialization (web only).

  • Page 45: Create New Prolifics Executables

    Client: Post-Installation for UNIX Create New Prolifics Executables As part of the Prolifics installation package, a set of standard Prolifics executables is provided. 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 other than JDB.
  • Page 46 Specifying the To indicate the executables to build, edit the directory: Executables Comment or uncomment the appropriate client executables as needed (these are uncommented by default): PRORUN = prorun PRODEV = prodev RWRUN = rwrun For platforms that have been installed with web application server software, comment or uncomment the server executable as needed: JSERVER = jserver To override the value of certain application variables such as...

  • Page 47: Configure The Client Environment

    Client: Post-Installation for UNIX • • Before changing these values, refer to the online Database Drivers for additional information on database engines and on case handling. Configure the Client Environment A Prolifics client provides the development environment required to build two-tier applications.
  • Page 48 • • • • • You can set libraries in the application directory and have them open automatically. To use online documentation, set and export to the file is not copied to the user’s home directory. To automatically set up the environment, execute the setup shell script directly from each users logon script ( •...

  • Page 49: Verify The Installation

    Client: Post-Installation for UNIX This assumes that you are using setup script files in your application directory. If you are using setup script files in the installation directory, replace applicationDir example, Note: If application variables are set in the user’s environment for previous versions of JAM or Prolifics, they should be removed so that they do not interfere with the setup for this version.

  • Page 50: Post-Installation Notes

    Post-Installation Notes The following additional information might be required to configure and run Prolifics software on your system. Implementing Several character-mode specific utilities, showkey.cm Character-Mode directory. You may need to use these if you are running Prolifics using character- Utilities mode and your system does not have Motif installed.
  • Page 51 Client: Post-Installation for UNIX Ensure that the in one of the directories pointed to by Ensure that the files can be found along the search execute these programs). Online Help and Prolifics’s online help and manuals are built and displayed with DynaText by Inso Corporation.

  • Page 52: Web Application Server: Unix

    Web Application Server: UNIX This chapter contains information for installing the Prolifics web application server. For information about installing Prolifics client software, refer to page 27. Web Application Server: Pre-Installation for UNIX To run a Prolifics web application server, an HTTP server must be configured and running on the same system.

  • Page 53: Preliminary Steps

    Web Application Server: Post-Installation for UNIX Preliminary If you plan to install a Prolifics web application server on UNIX, you must create a user account called Steps To prepare your UNIX system for installing a web application server: Add a user called passwd creates a user account for the web application server.

  • Page 54: Look At Sample Applications

    Obtain a permanent license file before the Start-up License file expires (refer to page 33). Create new Prolifics executables if required (refer to page 36). Configure the web server environment (refer to page 45). Verify the web application server installation (refer to page 46). Look at sample applications (refer to page 47).

  • Page 55: Creating Your Web Application

    Web Application Server: Post-Installation for UNIX • • • Determine File Determine the following: Locations The location of your HTTP server’s program directory, such as cgi–bin That the Prolifics Web Setup Manager is installed on your HTTP server and ready to run via a web browser. The default URL location is: Name/program_directory/websetup reference: Creating Your Web Application...

  • Page 56: Look At Samples

    Run the Gallery by entering the following URL in your browser: http://serverName/program_directory/jwsamp/main To verify your web application server configuration (and licensing): Configure a new application by running the Web Setup Manager. Start the application by typing the following on the command line in the Prolifics monitor –start applicationName Run the application in your browser:...

  • Page 57: Appendix A Notes For Microsoft Windows

    Notes for Microsoft Windows The information in this appendix provides troubleshooting notes for installing and running Prolifics on Microsoft Windows. DLLs for JPEG Decoding is a dynamic link library which performs JPEG decoding. There are WECJLIB.DLL two versions of the DLL. The version that comes with Prolifics can be freely distributed.

  • Page 58: Environment Space

    Environment Space Environment Space COMMAND.COM add the following line to your SHELL=C:\COMMAND.COM /E:1000 /P COMMAND.COM accordingly. Visual C++ Floating-Point Options For Microsoft Visual C++ distributions, all the distributed libraries created in the current version of Prolifics are compiled with the /FPc switch, so that you can choose at link time which floating-point library to use.
  • Page 59 Using Prolifics Utilities Run the utilities from DOS. Note: The utilities listed are distributed as Microsoft C QuickWin applications. If you are interested in the behavior of QuickWin applications, refer to the QuickWin chapter in the Programming Techniques manual that comes with Visual C/C++. Appendix Notes for Microsoft Windows...

  • Page 60: Appendix B Initialization And Databases

    Initialization and The installation procedure for Windows automatically modifies work with your database driver or drivers. The settings corresponding to your database and version are added to the Prolifics initialization file. For Windows 95/98 and Windows NT: Database and Version Microsoft Open Database Connectivity (ODBC) Version 2 Microsoft Open Database Connectivity...
  • Page 61 Database and Version Sybase Version 10 using DB-Library Sybase Version 10 using CT-Library Sybase Version 11 using DB-Library Sybase Version 11 using CT-Library For Windows 95/98: Database and Version Informix Version 7.20.TDI Oracle Version 7–7.2 using OCI Oracle Version 7–7.2 using Pro*C Oracle Version 7.3 using OCI Settings [databases]...
  • Page 62 Database and Version Oracle Version 7.3 using Pro*C Oracle Version 8 using OCI Oracle Version 8 using Pro*C For Windows NT: Database and version Informix Version 7.10 Informix Version 7.20TE1 or higher Oracle Version 7.3 using OCI Oracle Version 7.3 using Pro*C Appendix Initialization and Databases Settings...
  • Page 63 Database and version Oracle Version 8 using OCI Oracle Version 8 using Pro*C Settings [databases] installed=oracle [dbms oracle] driver=ora8dmnt.dll model=tmoral132.dll [databases] installed=oracle [dbms oracle] driver=emb8dmnt.dll model=tmora132.dll 2-Tier Installation...

  • Page 64: Appendix C License Administration

    Administration This appendix provides background information on licensing in Prolifics. To manage Prolifics usage, the Flexible License Manager (FLEXlm), a product of Globetrotter Software, Inc., is used. FLEXlm Version 5.0 is installed with Prolifics as part of the installation process only on server machines. The appendix describes the license options file and the following FLEXlm license administration utilities provided with Prolifics.

  • Page 65: Licensing In Prolifics

    Licensing in Prolifics lmstat lmswitchr lmver Licensing in Prolifics Prolifics components use local or remote licensing schemes and are defined as follows: Local licensing is when the license file for the application resides on the same machine as the Prolifics component being used. Remote licensing is when the license file for the application resides on a different machine from the Prolifics component being used.

  • Page 66: License Types

    file. However, there might be other license daemons managing other license files. Vendor daemon ( feature of a floating (development client) license has a limited number of tokens. License Types Two types of licenses are available with Prolifics; each type is specific to the component installed: A Prolifics web application server uses a license type that allows for an unlimited number of application servers to run on a specific computer.
  • Page 67 Options File Contents of the The options file has the following basic format: Options File {INCLUDE|EXCLUDE} feature {USER|HOST|DISPLAY|GROUP} name NOLOG {IN|OUT|DENIED|QUEUED} GROUP group–name member–list LINGER feature checkout-time REPORTLOG filename RESERVE numlic feature {USER|HOST|DISPLAY|GROUP} name TIMEOUT feature idletime Lines beginning with a pound sign (#) indicate comments and are ignored. INCLUDE/EXCLUDE INCLUDE allowed to use a particular feature.

  • Page 68: Flexlm Utilities

    FLEXlm Utilities but is not meant to be human readable. If the filename starts with a plus character (+), the file will be opened in append mode. The line has the following REPORTLOG format: REPORTLOG filename RESERVE reserves the specified number of licenses for the specified user, host, RESERVE display, or group.
  • Page 69 FLEXlm Utilities lmcksum Performs a checksum of a license file lmcksum [–k] [–c license_file] Force the encryption code checksum to be case-sensitive (in general, –k not case-sensitive) and not prompt for any input. –c license_file Name of license file to checksum. By default in the current directory.
  • Page 70 lmdiag Diagnoses licensing problems lmdiag [–c license_file] [–n] [feature] –c license_file Name of license file to diagnose. If this switch is not specified, the environment variable set, lmdiag Non-interactive mode; –n extended connection diagnostics are not available. feature Diagnose only the specified Description If no feature...
  • Page 71 FLEXlm Utilities lmdown Takes down license daemons lmdown [–c license_file] [–q] –c license_file Use the specified environment variable lmdown Quiet mode; –q lmdown Description lmdown cense daemons write out their last messages to the log file, close the file, and exit. All licenses which have been given out by those daemons are rescinded, so that the next time a client program goes to verify its license, it will not be valid.
  • Page 72 lmgrd Starts up the license manager daemon lmgrd [–2] [–b] [–c license_file] [–d] [–l logfile] [–p] [–s interval] [–t timeout] Specify V2 startup arguments, in contrast to the –2 if you intend to use the –b Specify backward compatibility mode. Use this switch if you are running a v2.1 or later lmgrd FLEXlm v2.4 and later.
  • Page 73 – Copyright (C) 1997, Globetrotter Software, Inc. The FLEXlm host ID of this machine is “1700abcd” type must be one of , and is currently used only on HP and SCO systems. On HP, long–uname is similar to the following: lmhostid...
  • Page 74 lmremove Removes a user license and returns it to the license pool lmremove [–c license_file] [feature] [user] [host] [display] –c license_file Use the specified license file. If this switch is not specified, the environment variable set, it looks for the file feature Remove only from the specified user...
  • Page 75 FLEXlm Utilities lmreread Tells the license daemon to reread the license file lmreread [–c license_file] –c license_file Use the specified license file. If this switch is not specified, the environment variable set, it looks for the file Description lmreread license file. This can be useful if the data in the license file has changed; the new data can be loaded into the license daemon without shutting down and restarting it.
  • Page 76 lmstat Reports status on license manager daemons and feature usage lmstat [–a] [–A] [–c license_file] [–f [feature]] [–l [reg_expression]] [–s [server]] [–S [daemon]] [–t timeout] Display everything. –a –A List all active licenses. –c license_file Use the specified license file. If this switch is not specified, environment variable lmstat –f [feature]...
  • Page 77 FLEXlm Utilities lmswitchr Switches the FLEXadmin log file (REPORTLOG) for the specified feature lmswitchr [feature] [new-file] feature feature new-file New file pathname. Description The FLEXlm daemons create an ASCII log file on stdout. There are several pro- cesses in a parent-child hierarchy which share the same file pointer, so this log file cannot be changed after the vendor daemons have been started, since each process has a copy of the current offset, etc.
  • Page 78 lmver Reports the FLEXlm version of a library or binary lmver [filename] filename Use the specified license file. If a filename is not specified, environment variable looks for the file lmver Description If the filename is specified, the FLEXlm version incorporated into this file is dis- played;...

  • Page 79: Appendix D License File

    This appendix describes the basic format and content of the password-enabled license file. If you already have a license file in place, either from a previous version of JAM or Prolifics, or from another application that uses FLEXlm, you can combine license files by inserting the license file information provided by the License Desk.
  • Page 80 Contents of the License File SERVER sname hostid port — Server’s name. sname — Host ID of the server. hostid — TCP/IP port number used by this server. port DAEMON Specifies the name and location of the license manager vendor daemon for the Prolifics development client.
  • Page 81 — Date issued. The license is not valid before this date. date serial number number. hostid — Hostid of the server. Used only if the feature is to be bound to a particular host, whether its use is counted or not. checksum INCREMENT Describes the license for the Prolifics development client.

  • Page 82: Error Messages

    Prolifics Installation Error Messages A Prolifics installation was not successful if you receive an error message and the program terminates. The following messages describe some of the more common error messages and how to resolve them. Recurring errors: Occasionally, errors described in this section seem to recur even though the file smvars binary (...

  • Page 83: Environment Space

    Prolifics Installation Error Messages Filename: No such file or directory Cause: The filename in brackets is specified as the value of the Action: Correct the name, and use the full pathname of the file. If you correct it in [Variable]: Environment variable missing Cause: Prolifics could not find an entry for the cited variable in Note: Most Prolifics setup variables can be set in the environment, rather than depending on values set in an...

  • Page 84: Dll Messages

    SMVARS: No such file or directory Cause: Action: Check that the full pathname (including drive letter under Windows) of DLL Messages The following error messages might occur after a Windows installation and are specific to DLLs required for Prolifics’s database drivers and to DLL version mismatches.

  • Page 85: Odbc-Specific Messages

    DLL Messages ODBC-Specific Messages Cannot load DLL odb2dm32.dll Cannot load DLL odb3dm32.dll Cannot load DLL tmodb132.dll Cause: Windows is unable to find the Prolifics database driver DLLs or the Action: Check that the Prolifics Oracle-Specific Messages Cannot load DLL ora7dm32.dll Cannot load DLL emb7dm32.dll Cannot load DLL or73dm32.dll Cannot load DLL em73dm32.dll...

  • Page 86: Sybase-Specific Messages

    Sybase-Specific Messages Cannot load DLL db10dm32.dll Cannot load DLL ct10dm32.dll Cannot load DLL db11dm32.dll Cannot load DLL ct11dm32.dll Cannot load DLL tmsyb132.dll Cause: Windows is unable to find the Prolifics database driver DLLs or the Action: Check that the Prolifics DLL Version Mismatch Messages Application Error: Call to Undefined Dynalink Cause: Prolifics is picking up an older version of...

  • Page 87: Prolifics License-Related Messages

    License Manager Error Messages Prolifics License-Related Messages The messages described in this section can appear when the screen editor is invoked. All License Prolifics License Manager: Bad date in license file. Cause: The date on one of the Types Action: Verify that the Prolifics License Manager: Bad encryption code in license file.
  • Page 88 Prolifics License Manager: Feature [product], Version [version] has expired. Cause: The expiration date in the license file of [product] has been reached. Action: Obtain a new license file or contact your system administrator. Prolifics License Manager: Initialization failed. Cause: Problems in the license file. Action: Contact your system administrator.
  • Page 89 License Manager Error Messages Prolifics License Manager: Unknown vendor key type Cause: Program’s object file is corrupt. Action: Contact your system administrator. Floating Prolifics License Manager: All [product] licenses are currently in use. Licenses Cause: All available licenses for [product] are in use. If your license request has Action: Try again later or contact your system administrator.
  • Page 90 Prolifics License Manager: Cannot find ethernet device. Cause: On most systems, the license manager must locate an ethernet board to Action: Contact your system administrator. Prolifics License Manager: [product] not authorized for this computer. Cause: [product] is not licensed to run on the current computer. Action: Contact your system administrator.

  • Page 91: Flexlm Informational Messages

    License Manager Error Messages FLEXlm Informational Messages The following messages are generated by FLEXlm license management software, and are provided courtesy of the FLEXlm Programmer’s Guide. Connected to node Cause: This daemon is connected to its peer on CONNECTED, master is name Cause: License daemon logs this message when a quorum is achieved and DENIED: N feature to user (mm/dd/yy hh:mm) Cause:...
  • Page 92 MASTER SERVER died due to signal nnn Cause: License daemon received fatal signal MULTIPLE xxx servers running. Please kill, and restart license daemon Cause: License daemon has detected that multiple copies of vendor daemon Action: Kill all OUT: feature feature by user (N licenses) Cause: Removing clients of children Cause: Top-level daemon logs this message when one of the child daemons dies.

  • Page 93: Flexlm Configuration Problem Messages

    License Manager Error Messages SIGCHLD received. Killing child servers. Cause: Vendor daemon logs this message when a shutdown is requested by the Started name Cause: License daemon logs this message whenever it starts a new vendor Trying connection to node Cause: Daemon is attempting a connection to FLEXlm Configuration Problem Messages hostname: Not a valid server host, exiting...

  • Page 94: Daemon Software Error Messages

    NO DAEMON line for name Cause: Vendor daemon logs this error if it cannot find its own Action: Edit license file. NO DAEMON lines, exiting Cause: License daemon logs this message if there are no Action: Edit license file. No features to serve! Cause: Vendor daemon found no features to serve.
  • Page 95 License Manager Error Messages BAD PID message from nnn: xxx (msg) Cause: Top-level vendor daemon received an invalid PID message from one of its BAD SCONNECT message: (message) Cause: An invalid Cannot create pipes for server communication Cause: The Action: Report error to Prolifics technical support. Can’t allocate server table space Cause: A malloc error.
  • Page 96 Not enough descriptors to re-create pipes Cause: Top-level daemon detected the death of one of its sub-daemons. In trying Action: This is a fatal error. The daemons must be restarted. read: error message Cause: An error in a recycle_control BUT WE DIDN’T HAVE CONTROL Cause: The hierarchy of vendor daemons has become confused over who holds return_reserved: can’t find feature listhead Cause: When a daemon is returning a reservation to the free reservation list, it...

  • Page 97: Index

    Application, samples, 16, 40 Windows, 25 autoexec.bat, 8 C compiler, 28 Character–mode, 28 Client configuring environment of UNIX, 38 Windows, 15 executables, 14, 37 license–related messages, 84 licensing, 59 supported platforms, 4 CONFIG.SYS, 50 Create license, error messages, 85 create_license utility, 23, 34 Index Database driver Informix, 10...
  • Page 98 File protection, 28 FLEXlm, 57 configuration errors, 88 error messages, 86 utilities, 61 Floating license, 59 messages about, 84 Graph widget, error messages, 81 HTTP server on UNIX, 43 on Windows, 19 Informix error messages, 79 versions supported, 10 Installation error messages, 77 verifying, 40 on UNIX, 46...
  • Page 99 Node–locked license, 59 messages about, 84 ODBC error messages, 80 versions supported, 11 Oracle error messages, 80 versions supported, 11 Prolifics Gallery, 25, 47 Windows initialization file, databases defined in, 53 QuickStart, 25, 47 REPORTLOG, 60 Samples, web applications, 47 Server executables, 37 web, executables, 14...

This manual is also suitable for:

Panther

Table of Contents