2–Tier Installation April 1999
This software manual is documentation for Panthert. It is as accurate as possible at this time; however, both this manual and Panther itself are subject to revision. Prolifics and JAM are registered trademarks and JAM/TPi and Panther are trademarks of JYACC, Inc. BEA TUXEDO is a registered trademark and BEA WebLogic Enterprise is a trademark of BEA Systems, Inc. DynaText is a registered trademark of Inso Corporation. FLEXlm is a registered trademark of GLOBEtrotter Software, Inc.
Table of Contents About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keyboard Conventions . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3 Chapter 4 Chapter 5 iv Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Database Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client: Post-Installation for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create New Prolifics Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
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 expression KEYWORDS Monospace (fixed-spaced) text is used to indicate: ` Code examples.
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 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.
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.
Online Documentation ` Proximity searches If desired, you can include proximity search parameters in your text searches. For example: connection within 5 words of database screen within 2 words before editor ` Boolean searches You can also include Boolean search parameters in your text searches using the following keywords: and, not, or. For example: procedure or module ` Search forms Prolifics provides additional search forms which search for library functions and for text within code examples.
Online Documentation For more information on using DynaText, refer to the Using DynaText title in the Collection window. Collateral Documentation The following information is also provided with your Prolifics installation: Additional Help Contact Prolifics for more information on the following services: About this Guide ` Online README file.
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. p. 4 - Based on architecture, decide which components to install. p. 4 - Satisfy hardware and software requirements for the components you plan to install. Windows: p. 7 Windows Web: p. 19 UNIX: p. 27 UNIX Web: p.
1 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.
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. Application Architecture Choose the appropriate architecture for your application based on your requirements.
For More Information For More Information After Panther is installed and configured, you can refer to the online documentation for information on specific topics. The preface, About this Guide, contains a suggested reading path and more information about the documentation. Refer to: For: Getting Started Step-by-step instructions for building a two-tier application, including setting up a client environment as well as a web application server. online New Features Guide New features in Panther.
2 Client: Windows Installation Client: Pre-Installation for Windows This section discusses hardware and software requirements and upgrade information 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 documentation).
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. To compile Java programs, the JDK is required. If you are using Microsoft’s Virtual Machine for Java, use version 5.00.
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.
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: 1. Insert CD-ROM. 2. Choose Start⇒Run. In the Run dialog box, type D:/setup (where D is the letter of the drive from which you are installing). 3. Choose to install database drivers. 4. Select appropriate database. 5. Select from the following options: 6.
Client: Installation for Windows For more information, refer to readme.inf in the Prolifics notes subdirectory. If you don’t know your Informix version, check the release number listed in the text files provided in INFORMIXDIR\release where INFORMIXDIR is the root Informix installation.
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.
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 application. The details of the steps are provided in the pages that follow. 1. Create new Prolifics executables if required. 2. Configure the client environment (refer to page 15). 3.
Client: Post-Installation for Windows 5. Uncomment the appropriate database in the makefile and edit the databasespecific makevars.dbs (where dbs is the extension of the database) file to choose the correct version of your database software. For further information, refer to page 15. 6. Type nmake at the command line to build the executable. By default, the makefile in the current directory is used for the make (and nmake) command. Specifying the Executables 7.
Client: Post-Installation for Windows Linking in the Database If you are using a database for which DLLs are not provided, you must edit the makefile in your application directory to link in the appropriate database. To include the appropriate database in your executables: 1. Uncomment the appropriate include statement in the SELECT DATABASE SOFTWARE section of the makefile. By default, JDB is uncommented.
Client: Post-Installation for Windows ` JAVA_HOME and CLASSPATH — These path names are specific to Java files and event handlers and need to be set to the location where your Java classes sit. Additionally, you can change the defaults for SMJAVAEDITOR and SMJAVAFACTORY and SMJAVALIBRARY. For more information, refer to the Developer ’s Guide. Verify the Installation After you install and configure the Prolifics client, you should verify that it starts up properly.
Client: Post-Installation for Windows Windows PATH Settings ` Ensure that libsti.ini (distributed in the config directory) resides in the Windows directory and contains the correct paths in it for the IPT variable. ` Ensure that libsti.dll (distributed in the util directory) can be found in a directory along the PATH. If you are upgrading from JAM or an earlier version of Prolifics, remember that Prolifics’s util directory must be on your PATH.
3 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.
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. It also saves disk space. Before Installing Before installing a Prolifics web application server, determine the HTTP server name and the name of the CGI or ISAPI or NSAPI program directory.
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.
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 (*.lcl) in the licenses subdirectory of your Prolifics installation directory for each component installed on a given machine. To obtain the license file: 1. Submit the license request file (for each component on a given machine) to the Prolifics License Desk.
Web Application Server: Post-Installation for Windows 3. Create the license.dat: Choose Start⇒Run, and type: SMBASE\licenses\create_license All .lic files for the machine are merged into a single license.dat file in the licenses directory and the Start-up License is saved as license.bak. Location of the License File Prolifics searches for the license file in the following order: ` The pathname given by the setting of LM_LICENSE_FILE in the prol4w32.ini files.
Web Application Server: Post-Installation for Windows • AppDirectory — Full pathname to the Prolifics samples subdirectory to provide initialization information for the sample web application. • Dispatcher — Full pathname of the dispatcher.exe program in the util subdirectory of the installation directory. • Server — Full pathname of the jserver.exe program in the util subdirectory of the installation directory. • SMBASE — Full pathname of the Prolifics installation directory.
Web Application Server: Post-Installation for Windows ` 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. Choose QuickStart on the Start menu.
4 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. Hardware and Software Requirements ` Prolifics software requires a maximum of 138 MB of disk space, of which 41 MB is for online documentation.
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. For more information, consult the database-specific release notes located in the notes directory.
Client: Pre-Installation for UNIX Determine File Location After deciding who is going to own the Prolifics files (root or a dummy login ID), determine where they will be installed (referred to as the Prolifics installation directory or SMBASE). Once this directory is set up, do not change it, since users are likely to embed the directory name in makefiles, shell scripts, and so forth. The default installation directory is /usr/prolifics.
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. To install Panther, you need to perform the following steps.
Client: Installation for UNIX 4. Mount the CD-ROM device as /cdrom. 5. In /usr/prolifics, to uncompress and extract the contents of the Panther distribution, type: zcat < /cdrom/CompressedTarFilename | tar –xvf – On HPUX, type: zcat < /cdrom/”CompressedTarFilename“ | tar –xvf – Filenames for the Panther distribution are: Filename Product prlstd2t400.tar.Z Two-tier Client prlstdwb400.tar.Z Two-tier Web Application Server prldbs400.tar.
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. Copy the license.
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.
Client: Post-Installation for UNIX To obtain the license file: 1. 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). 2. Install the license file or files. 3. Start the license manager daemon.
Client: Post-Installation for UNIX Note: After installing the license, if your environment has an old LM_LICENSE_FILE setting, you need to unset it as follows: Bourne or Korn shell: unset LM_LICENSE_FILE C Shell: unsetenv LM_LICENSE_FILE Or you can explicitly set it to the license file.
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. ` Using IXI Motif libraries. To create a new Prolifics executable: 1.
Client: Post-Installation for UNIX Specifying the Executables To indicate the executables to build, edit the makefile in your application directory: 1.
Client: Post-Installation for UNIX • In the databaseName PARAMETERS section of makevars, verify your database engine’s version. Uncomment the appropriate block of parameters based upon this version. Also, verify and correct the pathnames if necessary. • Set the flag dbs_ENGNAME to specify the default engine name. Before changing these values, refer to the online Database Drivers for additional information on database engines and on case handling.
Client: Post-Installation for UNIX • JAVA_HOME and CLASSPATH — These path names are specific to Java files and event handlers and need to be set to the location where your Java classes sit. Additionally, you can change the defaults for SMJAVAEDITOR and SMJAVAFACTORY and SMJAVALIBRARY. For more information refer to the online Developer’s Guide. • SMTERM — Specifies the type/model console the client is using. For Motif, set SMTERM to X.
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 with the full pathname to the Prolifics config directory, for example, /usr/prolifics/config/setup.sh. 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. 6.
Client: Post-Installation for UNIX Post-Installation Notes The following additional information might be required to configure and run Prolifics software on your system. Several character-mode specific utilities, mbedit.cm (menu bar editor) and Implementing Character-Mode showkey.cm (key translation utility), are provided in the distributed util directory. You may need to use these if you are running Prolifics using characterUtilities mode and your system does not have Motif installed.
Client: Post-Installation for UNIX ` Ensure that the grafcap file (distributed in the config directory) is located in one of the directories pointed to by SMPATH. ` Ensure that the files gdsp and swsdrvr (distributed in the util directory) can be found along the search PATH for executables (Prolifics must be able to execute these programs). Online Help and Prolifics’s online help and manuals are built and displayed with DynaText by Inso Corporation.
5 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. Prolifics supports some of the industry favorites, such as Netscape’s Enterprise Server, and Apache Server.
Web Application Server: Post-Installation for UNIX Preliminary Steps If you plan to install a Prolifics web application server on UNIX, you must create a user account called proweb. To prepare your UNIX system for installing a web application server: 1. Add a user called proweb (this name assignment is required) to the /etc/ passwd file on the machine on which your HTTP server is running. This creates a user account for the web application server. 2.
Web Application Server: Post-Installation for UNIX 1. Obtain a permanent license file before the Start-up License file expires (refer to page 33). 2. Create new Prolifics executables if required (refer to page 36). 3. Configure the web server environment (refer to page 45). 4. Verify the web application server installation (refer to page 46). 5. Look at sample applications (refer to page 47).
Web Application Server: Post-Installation for UNIX • Server — Full pathname of the jserver program in the util subdirectory of the installation directory. • SMBASE — Full pathname of the Prolifics installation directory. • PATH — Full pathname to the util subdirectory of the installation directory. Determine File Locations Determine the following: ` The location of your HTTP server’s program directory, such as /usr/web/ cgi–bin.
Web Application Server: Post-Installation for UNIX ` 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.
A Notes for Microsoft Windows The information in this appendix provides troubleshooting notes for installing and running Prolifics on Microsoft Windows. DLLs for JPEG Decoding WECJLIB.DLL is a dynamic link library which performs JPEG decoding. There are two versions of the DLL. The version that comes with Prolifics can be freely distributed. An enhanced version, which has added functionality, can be ordered from Express Compression Labs (ECL).
Environment Space Environment Space If COMMAND.COM runs out of environment space when you issue a SET command, add the following line to your CONFIG.SYS file: SHELL=C:\COMMAND.COM /E:1000 /P If COMMAND.COM resides on a different drive or directory, modify the line accordingly.
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++.
B Initialization and Databases The installation procedure for Windows automatically modifies PROL4W32.INI to 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 Settings Microsoft Open Database Connectivity (ODBC) Version 2 [databases] installed=odbc [dbms odbc] driver=odb2dm32.dll model=tmodb132.dll [databases] installed=odbc [dbms odbc] driver=odb3dm32.
Database and Version Settings Sybase Version 10 using DB-Library [databases] installed=sybase [dbms sybase] driver=db10dm32.dll model=tmsyb132.dll [databases] installed=sybase [dbms sybase] driver=ct10dm32.dll model=tmsyb132.dll [databases] installed=sybase [dbms sybase] driver=db11dm32.dll model=tmsyb132.dll [databases] installed=sybase [dbms sybase] driver=ct11dm32.dll model=tmsyb132.
Database and Version Settings Oracle Version 7.3 using Pro*C [databases] installed=oracle [dbms oracle] driver=em73dm32.dll model=tmora132.dll [databases] installed=oracle [dbms oracle] driver=ora8dm32.dll model=tmora132.dll [databases] installed=oracle [dbms oracle] driver=emb8dm32.dll model=tmora132.dll Oracle Version 8 using OCI Oracle Version 8 using Pro*C For Windows NT: Database and version Settings Informix Version 7.10 [databases] installed=informix [dbms informix] driver=inf7dmnt.
Database and version Settings Oracle Version 8 using OCI [databases] installed=oracle [dbms oracle] driver=ora8dmnt.dll model=tmoral132.dll [databases] installed=oracle [dbms oracle] driver=emb8dmnt.dll model=tmora132.
C License 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. ` lmcksum — Performs a checksum of a license file.
Licensing in Prolifics ` lmstat — Monitors the status of all licensing activity. ` lmswitchr — Switches the log file for the specified feature. ` lmver — Reports the FLEXlm version of a library or binary. 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.
Options File file. However, there might be other license daemons managing other license files. lmgrd runs on the license host. ` License Types Vendor daemon (prold) — Works with lmgrd to dispense tokens. Each feature of a floating (development client) license has a limited number of tokens.
Options File Contents of the Options File The options file has the following basic format: {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.
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 REPORTLOG line has the following format: REPORTLOG filename RESERVE RESERVE reserves the specified number of licenses for the specified user, host, display, or group. Reserving a license decreases the number of generally available licenses.
FLEXlm Utilities lmcksum Performs a checksum of a license file lmcksum [–k] [–c license_file] –k Force the encryption code checksum to be case-sensitive (in general, lmcksum is not case-sensitive) and not prompt for any input. –c license_file Name of license file to checksum. By default lmcksum operates on license.dat in the current directory. If this switch is not specified, lmcksum looks for the environment variable LM_LICENSE_FILE.
FLEXlm Utilities 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, lmdiag looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, lmdiag looks for the file /usr/local/flexlm/licenses/license.dat. –n Non-interactive mode; lmdiag does not prompt for any input. In this mode, extended connection diagnostics are not available.
FLEXlm Utilities lmdown Takes down license daemons lmdown [–c license_file] [–q] –c license_file Use the specified license_file. If this switch is not specified, lmdown looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, lmdown looks for the file /usr/local/flexlm/licenses/license.dat . –q Quiet mode; lmdown does not ask for confirmation. If the switch is not specified, lmdown asks for confirmation before asking the license daemons to shut down.
FLEXlm Utilities lmgrd Starts up the license manager daemon lmgrd [–2] [–b] [–c license_file] [–d] [–l logfile] [–p] [–s interval] [–t timeout] –2 Specify V2 startup arguments, in contrast to the –b switch. This switch is required if you intend to use the –p switch (available in lmgrd v2.4 and later). –b Specify backward compatibility mode. Use this switch if you are running a v2.1 or later lmgrd with a v1.5 or earlier vendor daemon. This is the default switch in FLEXlm v2.4 and later.
FLEXlm Utilities lmhostid Prints the correct hostid value on any machine supported by FLEXlm lmhostid [type] type The type of the hostid to print. type must be one of long, idmodule, ether, or string, and is currently used only on HP and SCO systems. On HP, type specifies the ID module, the machine id as returned from the uname command, or the Ethernet address. The HP default is long–uname. On SCO, long specifies the pre-3.
FLEXlm Utilities 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, lmremove looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, it looks for the file /usr/local/flexlm/licenses/license.dat. feature Remove only from the specified feature. user The user to be removed.
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, lmreread looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, it looks for the file /usr/local/flexlm/licenses/license.dat. Description lmreread allows the system administrator to tell the license daemon to reread the license file.
FLEXlm Utilities 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] –a Display everything. –A List all active licenses. –c license_file Use the specified license file. If this switch is not specified, lmstat looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, lmstat looks for the file /usr/local/flexlm/licenses/license.dat .
FLEXlm Utilities lmswitchr Switches the FLEXadmin log file (REPORTLOG) for the specified feature lmswitchr [feature] [new-file] feature Any feature this daemon supports. new-file New file pathname. Description The FLEXlm daemons create an ASCII log file on stdout. There are several processes 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.
FLEXlm Utilities lmver Reports the FLEXlm version of a library or binary lmver [filename] filename Use the specified license file. If a filename is not specified, lmver looks for the environment variable LM_LICENSE_FILE. If the environment variable is not set, lmver looks for the file /usr/local/flexlm/licenses/license.dat . Description If the filename is specified, the FLEXlm version incorporated into this file is displayed; otherwise lmver looks for the library file liblmgr.a to detect its version.
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.
Contents of the License File SERVER sname hostid port sname — Server’s name. hostid — Host ID of the server. port — TCP/IP port number used by this server. DAEMON Specifies the name and location of the license manager vendor daemon for the Prolifics development client. It also provides the location of the Prolifics options file. It has the following format: DAEMON daemon-name path [options_file] daemon-name — Name of the daemon; always prold. path — Full path for the daemon.
Contents of the License File date — Date issued. The license is not valid before this date. serial number — Product serial number; more than one feature can share a serial 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 — Verifies that the license has been entered correctly by the end-user. INCREMENT Describes the license for the Prolifics development client.
E 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 is in order.
Prolifics Installation Error Messages Windows: Set the variable to win in PROL4W32.INI. If you are running in character mode and the screen appears disorganized, with all the text bunched together along with special characters, check the value of SMTERM; you probably only need to change its value, but you may also need to create a new video file.
DLL Messages UNIX: Make sure that the variable is exported (via the export sh/ksh command or setenv csh command). SMVARS: No such file or directory Cause: SMVARS is not set correctly. Action: Check that the full pathname (including drive letter under Windows) of the file is included and correct. 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.
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 ODBC software. Action: Check that the Prolifics util directory is on the PATH. If you do not wish to use the Prolifics database driver DLLs, edit PROL4W32.INI to remove the database name from the install entry. Oracle-Specific Messages Cannot load DLL ora7dm32.dll Cannot load DLL emb7dm32.
Graph-Related Messages Sybase-Specific Messages Cannot Cannot Cannot Cannot Cannot load load load load load DLL DLL DLL DLL DLL db10dm32.dll ct10dm32.dll db11dm32.dll ct11dm32.dll tmsyb132.dll Cause: Windows is unable to find the Prolifics database driver DLLs or the Sybase software. Action: Check that the Prolifics util directory is on the PATH. If you do not wish to use the Prolifics database driver DLLs, edit PROL4W32.INI to remove the database name from the install entry.
License Manager Error Messages Prolifics License-Related Messages The messages described in this section can appear when the screen editor is invoked. All License Types Prolifics License Manager: Bad date in license file. Cause: The date on one of the FEATURE or INCREMENT lines is not correct. Action: Verify that the FEATURE and INCREMENT lines in the license file are correct or contact your system administrator. Prolifics License Manager: Bad encryption code in license file.
License Manager Error Messages 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. Prolifics License Manager: Invalid data received from license server.
License Manager Error Messages Prolifics License Manager: Unknown vendor key type Cause: Program’s object file is corrupt. Action: Contact your system administrator. Floating Licenses Prolifics License Manager: All [product] licenses are currently in use. Cause: All available licenses for [product] are in use. If your license request has been queued, you get a series of messages showing who has the licenses reserved or how many licenses are in use.
License Manager Error Messages Prolifics License Manager: Cannot find ethernet device. Cause: On most systems, the license manager must locate an ethernet board to verify the password on the FEATURE or INCREMENT lines. 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. Prolifics License Manager: Version [version] not supported.
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 node. CONNECTED, master is name Cause: License daemon logs this message when a quorum is achieved and everyone has selected a master. DENIED: N feature to user (mm/dd/yy hh:mm) Cause: user was denied access to N licenses of feature.
License Manager Error Messages MASTER SERVER died due to signal nnn Cause: License daemon received fatal signal nnn. MULTIPLE xxx servers running. Please kill, and restart license daemon Cause: License daemon has detected that multiple copies of vendor daemon xxx are running. Action: Kill all xxx daemon processes and restart the license daemon. OUT: feature feature by user (N licenses) (used: d:hh:mm:ss) Cause: user has checked out N licenses of feature at d:hh:mm:ss.
License Manager Error Messages SIGCHLD received. Killing child servers. Cause: Vendor daemon logs this message when a shutdown is requested by the license daemon. Started name Cause: License daemon logs this message whenever it starts a new vendor daemon. Trying connection to node Cause: Daemon is attempting a connection to node. FLEXlm Configuration Problem Messages hostname: Not a valid server host, exiting Cause: This daemon was run on an invalid hostname.
License Manager Error Messages NO DAEMON line for name Cause: Vendor daemon logs this error if it cannot find its own DAEMON name in the license file. Action: Edit license file. NO DAEMON lines, exiting Cause: License daemon logs this message if there are no DAEMON lines in the license file; with no vendor daemons to start, there is nothing to do. Action: Edit license file. No features to serve! Cause: Vendor daemon found no features to serve. This could be caused by bad data in the license file.
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 children (daemon number xxx). BAD SCONNECT message: (message) Cause: An invalid server connect message was received. Cannot create pipes for server communication Cause: The pipe system call failed. Action: Report error to Prolifics technical support. Can’t allocate server table space Cause: A malloc error.
License Manager Error Messages Not enough descriptors to re-create pipes Cause: Top-level daemon detected the death of one of its sub-daemons. In trying to restart the chain of sub-daemons, it was unable to get the file descriptors to set up the pipes to communicate. Action: This is a fatal error. The daemons must be restarted. read: error message Cause: An error in a read system call was detected.
Index A Application, samples, 16, 40 Windows, 25 autoexec.
F File protection, 28 FLEXlm, 57 configuration errors, 88 error messages, 86 utilities, 61 Floating license, 59 messages about, 84 G Graph widget, error messages, 81 remove user, 67 REPORTLOG, 60 schemes, 58 status, 69 types, 59 version of file, 71 License administration, 57 utilities, 61 License file location of, 23, 35 requesting, 22, 34 License manager determining version, 35 messages, 81 start, 65 License options file, 59–61 H License request file, 22, 33 license.
N SMTERM, 39, 40 Start–up License, backup, 23, 34 Node–locked license, 59 messages about, 84 Sybase error messages, 81 versions supported, 12 O ODBC error messages, 80 versions supported, 11 Oracle error messages, 80 versions supported, 11 P Prolifics Gallery, 25, 47 Windows initialization file, databases defined in, 53 Q T Two–tier application, 4 U UNIX requirements, client, 27 verifying installation of client, 40 Upgrade on UNIX, 29 on Windows, 8 Utilities character–mode, renaming, 41 using in Win
