HP Panter 2Tier manual Sybase

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.

Sybase

Windows 95/98 and NT: Sybase Version 10 using DB-Library

Sybase Version 10 using CT-Library

Sybase Version 11 using DB-Library

Sybase Version 11 using CT-Library

Or latest version

Other

For versions of Sybase earlier than 10, Prolifics/Sybase requires the DB-Library interface. With Prolifics/Sybase’s support for Sybase Open Client Version 10, two interfaces are supported, DB-Library and CT-Library.

If you do not know your Sybase version, run the Sybase Windows program sqlver.exe or refer to the About menu option of any of the Sybase Windows program (for example, sybping.exe).

12	2-Tier Installation

Image 23

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