As part of the Panther COM/MTS installation package, a set of standard Panther executables is provided for the client and the web application broker. 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 for which DLLs are not provided or if you are adding C functions to your Panther application.
Alternatively, Panther distributes workspace and project files for use with Microsoft Developer Studio. Instructions on how to use the workspace are provided in the Release Notes.
Client and Web Application Broker Executables
To create new executables, Panther distributes a single makefile that can be invoked via the command line utility,
Complete the installation process of Panther components.
SMBASE, etc.) have been applied to your environment.
linksubdirectory to it.
makefilein your application directory, commenting or uncommenting lines as needed to build the appropriate executables. For further information, refer to "Specifying the Executables."
makefileand edit the database-specific
dbsis the extension of the database) file to choose the correct version of your database software. For further information, refer to "Linking in the Database."
nmakeat the command line to build the executable. By default, the
makefilein the current directory is used for the
nmakeprocess creates a new Panther executable,
exe. Give the executable file a unique name to distinguish it from the distributed executable or others that you have built differently.
jserver), modify the
SERVERvariable in your application's initialization file to reference the new
jserverexecutable in its own directory. Do not overwrite the
jserverexecutable in the
To indicate the executables to build, edit the makefile in your application directory:
If Web application broker software has been installed, comment or uncomment the server executable as needed:
Web application broker executable (uncommented by default)
SMBASE, uncomment the appropriate lines in the
PARAMETERSsection) to the web application broker installation directory.
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:
includestatement in the
SOFTWAREsection of the
makevars.dbs (where dbs is the extension of the database) file to choose the correct version of your database software.
dbsfile, verify or update the following:
_INITto one of the following:
p. This flag controls the handling for case sensitivity. The default is
d. To find out what the default is for your database engine, refer to the online database-specific driver notes.
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.
dll is the template for Panther COM components and can be edited to enable you to link your own C functions into your COM component. Files included in the
comlink directory are:
Resource file for copyright information
Microsoft Developer Studio Workspace File
Microsoft Developer Studio Project File
For command line makes
Edit the source code in
c to include your C Functions, make a new DLL, and in the Panther editor, update the name and/or location of the template DLL on the COM tab of the Component Service interface. It is recommended that you give the new DLL a different name (other than