HP Panter 2Tier manual Before Installing

Page 30

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. Also, verify that your HTTP server is running. Consult your system administrator or your web server administrator to determine the correct names. Enter the names here for future reference:

`My HTTP server name is _____________________________________

`My HTTP server \www\scripts directory is

_________________________________________________________

The \scripts\ directory stores the server’s gateway programs. Another common name for this directory is cgi–bin.

20

2-Tier Installation

Image 30
Contents Tier Installation Page Table of Contents Chapter Web Application Server Windows Appendix D License File About this Guide Organization of this GuideConventions Text ConventionsKeyboard Conventions Panther Documentation Panther Documentation Online Documentation Procedure or module Collateral Documentation Additional Help Page Installation Installation ChecklistPre-Installation Post-InstallationContents of the Installation Package General InformationWhich Panther Components to Install? Application ArchitectureFor More Information Client Windows Installation Client Pre-Installation for WindowsHardware and Software Requirements Upgrading Client Installation for Windows Installation ProcedureTo run the setup program Installing a Database Driver To install database driversInformix Microsoft SQL Server OracleSybase Create New Prolifics Executables Client Post-Installation for WindowsPost-Installation Overview To create a new Prolifics executableSpecifying Executables To include the appropriate database in your executables Configure the Client EnvironmentLinking Database For each Windows clientClient Installation Verify the InstallationTroubleshooting Look at Sample ApplicationsWindows Path Settings Online Help Manuals Adding Panther DocumentsWeb Application Server Pre-Installation for Windows Web Application Server WindowsBefore Installing Web Application Server Post-Installation for Windows Licensing for Prolifics Web Application ServerObtaining a Permanent License File Installing the License File To install a permanent license fileTo obtain the license file Configure the Web Application Server Environment Location License FileWeb Application Server Installation To verify the Prolifics web application server installationCreating a Web Application Look at Samples QuickStartProlifics Gallery web application Client Unix Installation Client Pre-Installation for UnixFile Ownership and Protection Implement File ProtectionDetermine File Location UpgradingClient Installation for Unix To install Panther from a CD-ROMConfiguring the Installation To configure the installationAdditional Procedures Client Post-Installation for Unix Licensing for ProlificsInstalling License File Location of the License File Starting Manager To determine the version of lmgrdTo start the license manager Create New Prolifics Executables Specifying Executables Linking in the Database Configure the Client Environment ApplicationDir/setup.sh To verify a Unix client installation Look at a Sample ApplicationLicense Manager Post-Installation NotesImplementing Character-Mode Utilities Motif Version Number Graph Functionality.ebtrc file $SMBASE/docs = Panther Web Application Server Pre-Installation for Unix Web Application Server UnixWeb Application Server Post-Installation for Unix Preliminary StepsWeb Application Server Unix Creating Your Web Application Determine File LocationsMonitor -start applicationName Windows DLLs for Jpeg DecodingUsing Prolifics Utilities Environment Space Visual C++ Floating-Point Options` Run the utilities from DOS Initialization Databases For Windows 95/98 and Windows NTFor Windows 95/98 For Windows NT Driver=ora8dmnt.dll License Administration Licensing in Prolifics License Daemons and License TypesTypes Daemons Options File License TypesContents Options File FLEXlm Utilities ExampleLmcksum Performs a checksum of a license fileDiagnoses licensing problems LmdiagLmdown Takes down license daemonsLmgrd Starts up the license manager daemonLmhostid Output from lmhostid is similar to the followingLmremove Removes a user license and returns it to the license poolLmreread Tells the license daemon to reread the license fileReports status on license manager daemons and feature usage LmstatLmswitchr Lmver Reports the FLEXlm version of a library or binaryContents of the License File License FileDaemon Increment Error Messages Prolifics Installation Error MessagesFilename No such file or directory DLL Messages Informix-Specific MessagesMicrosoft SQL Server-Specific Messages ODBC-Specific Messages Oracle-Specific MessagesSybase-Specific Messages License Manager Error MessagesGraph-Related Messages DLL Version Mismatch MessagesProlifics License-Related Messages All License TypesProlifics License Manager Initialization failed Floating Licenses Node-locked LicensesCreate License Utility Cause feature has passed its expiration date FLEXlm Informational MessagesCause 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