HP Panter 2Tier manual Configure the Client Environment

Page 47

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.

Configure the Client Environment

A Prolifics client provides the development environment required to build two-tier applications. The environment must contain properly set application variables in order to run Prolifics. To set up the development environment, complete the following platform-specific steps. Refer to the online Developer’s Guide for more details on setting up the client environment.

1.For each client, copy the following files in the installation config directory to each developer’s home directory:

.ebtrc — Used by the online help systems. Copy the file or set the EBTRC variable to point to it; refer to Step 4.

Prolifics — X resource file used by the Prolifics client. Copy to each user’s app-defaultsdirectory (if there is one) or to the user’s home directory.

2.The setup shell scripts are useful for setting Prolifics application variables. The setup program determined values for some of these variables, based on your system’s configuration, and modified the scripts accordingly. Review setup.sh (Bourne or Korn shell users) and setup.csh (C shell users) in the application directory (if it exists) or the file $SMBASE/config/setup.sh ($SMBASE/config/setup.csh) to ensure proper settings for the following application variables:

SMBASE — Full pathname of the Prolifics installation directory. The installation recommends /usr/prolifics; therefore, SMBASE would be set to equal /usr/prolifics. If Prolifics was installed in a different directory, use that directory’s name.

PATH — Identifies directories to search when looking for executable programs. PATH should include the path to Prolifics’s util directory so that the system can find the development executable (prodev) and Prolifics utilities. If Prolifics’s util directory is not on the PATH, business graphs and online help will not work.

38

2-Tier Installation

Image 47
Contents Tier Installation Page Table of Contents Chapter Web Application Server Windows Appendix D License File Organization of this Guide About this GuideKeyboard Conventions ConventionsText Conventions Panther Documentation Panther Documentation Online Documentation Procedure or module Collateral Documentation Additional Help Page Post-Installation Installation ChecklistPre-Installation InstallationGeneral Information Contents of the Installation PackageApplication Architecture Which Panther Components to Install?For More Information Hardware and Software Requirements Client Windows InstallationClient Pre-Installation for Windows Upgrading To run the setup program Client Installation for WindowsInstallation Procedure Informix Installing a Database DriverTo install database drivers Oracle Microsoft SQL ServerSybase To create a new Prolifics executable Client Post-Installation for WindowsPost-Installation Overview Create New Prolifics ExecutablesSpecifying Executables For each Windows client Configure the Client EnvironmentLinking Database To include the appropriate database in your executablesLook at Sample Applications Verify the InstallationTroubleshooting Client InstallationOnline Help Manuals Adding Panther Documents Windows Path SettingsWeb Application Server Windows Web Application Server Pre-Installation for WindowsBefore Installing Obtaining a Permanent License File Web Application Server Post-Installation for WindowsLicensing for Prolifics Web Application Server To obtain the license file Installing the License FileTo install a permanent license file Location License File Configure the Web Application Server EnvironmentCreating a Web Application Web Application Server InstallationTo verify the Prolifics web application server installation Prolifics Gallery web application Look at SamplesQuickStart Client Pre-Installation for Unix Client Unix InstallationImplement File Protection File Ownership and ProtectionUpgrading Determine File LocationTo install Panther from a CD-ROM Client Installation for UnixTo configure the installation Configuring the InstallationAdditional Procedures Licensing for Prolifics Client Post-Installation for UnixInstalling License File To start the license manager Location of the License File Starting ManagerTo determine the version of lmgrd Create New Prolifics Executables Specifying Executables Linking in the Database Configure the Client Environment ApplicationDir/setup.sh Look at a Sample Application To verify a Unix client installationMotif Version Number Graph Functionality Post-Installation NotesImplementing Character-Mode Utilities License Manager.ebtrc file $SMBASE/docs = Panther Web Application Server Unix Web Application Server Pre-Installation for UnixPreliminary Steps Web Application Server Post-Installation for UnixWeb Application Server Unix Determine File Locations Creating Your Web ApplicationMonitor -start applicationName DLLs for Jpeg Decoding WindowsEnvironment Space Visual C++ Floating-Point Options Using Prolifics Utilities` Run the utilities from DOS For Windows 95/98 and Windows NT Initialization DatabasesFor Windows 95/98 For Windows NT Driver=ora8dmnt.dll License Administration Types Daemons Licensing in ProlificsLicense Daemons and License Types License Types Options FileContents Options File Example FLEXlm UtilitiesPerforms a checksum of a license file LmcksumLmdiag Diagnoses licensing problemsTakes down license daemons LmdownStarts up the license manager daemon LmgrdOutput from lmhostid is similar to the following LmhostidRemoves a user license and returns it to the license pool LmremoveTells the license daemon to reread the license file LmrereadLmstat Reports status on license manager daemons and feature usageLmswitchr Reports the FLEXlm version of a library or binary LmverLicense File Contents of the License FileDaemon Increment Prolifics Installation Error Messages Error MessagesFilename No such file or directory Microsoft SQL Server-Specific Messages DLL MessagesInformix-Specific Messages Oracle-Specific Messages ODBC-Specific MessagesDLL Version Mismatch Messages License Manager Error MessagesGraph-Related Messages Sybase-Specific MessagesAll License Types Prolifics License-Related MessagesProlifics License Manager Initialization failed Node-locked Licenses Floating LicensesCreate License Utility FLEXlm Informational Messages Cause feature has passed its expiration dateCause License daemon received fatal signal nnn FLEXlm Configuration Problem Messages Daemon Software Error Messages Cause An invalid server connect message was received Cause An error in a read system call was detected Index Tier Installation Odbc