Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 

 
 
CLICK TO EXPAND NAVIGATION
CLICK TO EXPAND NAVIGATION
 
 
 
 
Support > Technical Documents > Document Types > White Paper-Technical > Deployment Files for PowerBuilder, InfoMaker, and ...  
RSS Feed
 
 
 

Deployment Files for PowerBuilder,
InfoMaker, and the Web DataWindow
Page 2

[Back to page 1] [Next to page 3]

Adaptive Server Anywhere files

If your PowerBuilder application uses an Adaptive Server Anywhere database, you need to deploy the Adaptive Server Anywhere DBMS as well as Adaptive Server Anywhere's ODBC database drivers. If your application uses a standalone database, you can deploy the Adaptive Server Anywhere Desktop Runtime System to users' computers without incurring additional license fees. The runtime system allows the user to retrieve and modify data in the database, but does not allow modifications to the database schema. It does not support transaction logs, stored procedures, or triggers.

Note:  Restrictions Enterprise Application Studio includes Adaptive Server Anywhere for use during the development process. However, this product cannot be deployed royalty-free to your users.

If your application requires the data definition language (DDL), a transaction log, stored procedures, or triggers, see your Sybase sales representative.

For more information about deploying Adaptive Server Anywhere databases and applications, see the Adaptive Server Anywhere User's Guide.

A full installation for the Adaptive Server Anywhere driver, runtime engine, and supporting files is available in the \Support directory on Install Disk 2. The following table lists the files that are installed when you select Common Files and the Runtime Server in the install program. You can also choose to install Help files, SQL Anywhere 5.0 compatibility DLLs, and client files that allow 16-bit applications to access Adaptive Server Anywhere databases.

Install options Name Description
Common Files DBODB6.DLL ASA ODBC driver
  DBBACKUP.EXE ASA backup utility
  DBCON6.DLL Connection dialog, required if you do not provide your own dialog and your end users are to create their own data sources, if they need to enter user IDs and passwords when connecting to the database, or if they need to display the Connection dialog for any other purpose
  DBISQL.EXE Interactive SQL utility
  DBLGEN6.DLL Language-specific string library (EN indicates the English version)
  DBLIB6.DLL Interface library
  DBODTR6.DLL ODBC translator, required if your application relies on OEM to ANSI character set conversion
  DBTOOL6.DLL ASA database tools
  DBUNLOAD.EXE ASA unload utility
  DBVALID.EXE ASA validation utility
Runtime Server RTENG6.EXE Restricted runtime engine
  DBCTRS6.DLL Performance utility
  DBEXTF6.DLL External interface
  DBSERV6.DLL Server utility
  DBWTSP6.DLL Tools support

Installed path C:\Program Files\Sybase\Adaptive Server Anywhere 6.0\win32

Deployment path Same directory as the application, in a directory on the system path, or in the App Path registry key.

Registry entries See "App Path registry key" and "Configuring ODBC data sources and drivers".

Notes: Supporting files should be installed in the same directory as DBODB6.DLL. If you are not using the English string library, make sure you deploy the appropriate version of the language-specific string library.

Configuring ODBC data sources and drivers

ODBC.INI To allow the user to connect to a particular data source, your installation program must provide a definition for that data source in the ODBC.INI key in the registry on the computer that accesses the data source, in HKEY_CURRENT_USER for a user DSN or in HKEY_LOCAL_MACHINE for a system DSN. The data source definition specifies the name and location of the database driver as well as the command required to start the database engine. The data source in the ODBC Data Sources key must also be listed in ODBC.INI.

The following shows typical registry entries for a data source called MyApp DB that uses Adaptive Server Anywhere. Registry keys are enclosed in square brackets and are followed by string values for that key in the format "Name"="Value" :
   [HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\MyApp DB]
   "Driver"="C:\Program Files\Sybase\Adaptive 
   		Server Anywhere 6.0\win32\dbodbc6.dll"
   "Start"="c:\program files\sybase\Adaptive 
   		Server Anywhere 6.0\win32\rteng6.exe -c8m"
   "UID"="dba"
   "PWD"="sql"
   "Description"="Database for my application"
   "DatabaseFile"="C:\Program Files\myapps\myapp.db"
   "AutoStop"="Yes"

   [HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\
ODBC Data Sources]
   "MyApp DB"="Adaptive Server Anywhere 6.0"

ODBCINST.INI Your installation program needs to make two types of entry in the ODBCINST.INI key in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC for each driver that your deployed application uses:

  • Add a string value with the name of the driver and the data value "Installed" to the ODBC DRIVERS key in ODBCINST.INI.
  • Add a new key for each driver to the ODBCINST.INI key with string values for Driver and Setup. Some drivers require additional string values in ODBCINST.INI.

If the ODBC database driver files are not located in a directory on the system path, you also need to add their location to the App Paths key for the executable file.

If you are using ODBC drivers obtained from a vendor, you can use the driver's setup program to install the driver and create registry entries.

The following shows typical registry entries for Adaptive Server Anywhere and INTERSOLV Sybase drivers. Registry keys are enclosed in square brackets and are followed by string values for that key in the format "Name"="Value" :

   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\App Paths\myapp.exe]
   "Default"="C:\Program Files\myapps\MYAPP.EXE"
   "Path"="Program Files\sybase\shared\PowerBuilder;
c:\program files\sybase\Adaptive Server
Anywhere 6.0\win32\;c:\program files\sybase
\shared\IntersolvODBC;"

   [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\
ODBC Drivers]
   "Adaptive Server Anywhere 6.0"="Installed"
   "PB INTERSOLV OEM 3.11 32-BIT Sybase"="Installed"

   [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\
Adaptive Server Anywhere 6.0]
   "Driver"="c:\program files\sybase\Adaptive 
Server Anywhere 6.0\win32\dbodbc6.dll"
   "Setup"="c:\program files\sybase\Adaptive 
Server Anywhere 6.0\win32\dbodbc6.dll"

   [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\
PB INTERSOLV OEM 3.11 32-BIT Sybase]
   "Driver"="C:\Program Files\sybase\shared\
IntersolvODBC\pbsyb13.dll"
   "Setup"="C:\Program Files\sybase\shared\
IntersolvODBC\pbsyb13.dll"
   "APILevel"="1"
   "ConnectFunctions"="YYY"
   "CPTimeout"="60"
   "DriverODBCVer"="03.00"
   "FileUsage"="0"
   "SQLLevel"="0"
   "UsageCount"="1"

For more information about the contents of the registry entries for ODBC drivers and data sources, see Connecting to Your Database.

OLE DB database providers

If your application uses OLE DB to access data, you must install Microsoft's Data Access Components software on each user's computer if it is not installed already.

You can use the MDAC_MIN.EXE setup file in the Support directory on the Install Disk 2 to update users' computers. The Microsoft OLE DB providers, SQLOLEDB and MSDASQL, will be installed when you run MDAC_MIN.EXE.

The following files are required if you use the Intersolv OLE DB data provider specified. If your application uses an OLE DB data provider from another vendor, you must still deploy PBOLE70.DLL as well as the files specified by the vendor.

Note:  Optional Help files Help (.HLP and .CNT) files need only be deployed if you expect users to perform database administration tasks.

Name Required for
PBOLE70.DLL PowerBuilder OLE DB interface required for all OLE DB connections
GLOSSARY.HLP
INODBC.LIC
IVODBC.LIC
PBADMIN.CNT
PBADMIN.EXE
PBADMIN.HLP
PBADMINR.DLL
PBBAS03.DLL
PBBAS04.DLL
PBBAS04.HLP
PBBAS04R.DLL
PBCVT01.DLL
PBUTL03.DLL
PBUTL04.DLL
PBUTL04R.DLL
License and help files and administration utilities required for all INTERSOLV OLE DB data providers
PBINF04.CNT
PBINF04.DLL
PBINF04.HLP
PBINF04R.DLL
PBINF04S.DLL
INTERSOLV Informix7
PBIF904.CNT
PBIF904.DLL
PBIF904.HLP
PBIF904R.DLL
PBIF904S.DLL
INTERSOLV Informix 9
PBOR704.CNT
PBOR704.DLL
PBOR704.HLP
PBOR704R.DLL
PBOR704S.DLL
INTERSOLV Oracle 7
PBOR804.CNT
PBOR804.DLL
PBOR804.HLP
PBOR804R.DLL
PBOR804S.DLL
INTERSOLV Oracle 8
PBSYB04.CNT
PBSYB04.DLL
PBSYB04.HLP
PBSYB04R.DLL
PBSYB04S.DLL
INTERSOLV Sybase

Installed path C:\Program Files\Sybase\Shared\IntersolvOLEDB

Deployment path Same directory as the application, in a directory on the system path, or in the App Path registry key.

Registry entries See "App Path registry key".

Notes: The primary OLE DB providers tested with PowerBuilder are SQLOLEDB for use with MS SQL Server 7.0 and Intersolv Sybase OLE DB.

JDBC database interfaces

The following PowerBuilder files are required if your application uses the Java virtual machine specified. The Java virtual machine and a vendor-supplied JDBC-compliant driver, such as Sybase jConnect, must also be installed and configured on the computer that accesses the data source.

Name Description
PBJDM70.DLL PB JDBC DB Driver for the Microsoft Java virtual machine
PBJDS70.DLL PB JDBC DB Driver for the Sun Java virtual machine
CLASSES.ZIP Java package for PowerBuilder JDBC drivers (required for JDM and JDS)

Installed path C:\Program Files\Sybase\Shared\PowerBuilder

Deployment path Same directory as the application, in a directory on the system path, or in the App Path registry key.

Registry entries Make sure the CLASSPATH environment variable includes the PowerBuilder classes.zip file. If you are using the Sun JDS driver, the CLASSPATH environment variable should also include the classes.zip file for the version of the JDK you are using. For example:

   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
   		\Session Manager\Environment]
   "CLASSPATH"="C:\Program Files\sybase\shared\
   		PowerBuilder\classes.zip;C:\Program Files\
   		sybase\shared\Sun\jdk118\lib\classes.zip;

Notes: See "PowerBuilder component on Jaguar server" and "Web DataWindow on Jaguar server".

PowerBuilder component on Jaguar server

The following files are required on a Jaguar server on which components generated in PowerBuilder will run.

Note:  If PowerBuilder components do not use a feature or database interface listed in the table, the file does not need to be installed on the Jaguar server.

Windows UNIX Description
PBVM70.DLL libpbvm70x.ext* PowerBuilder virtual machine (required for all PowerBuilder components)
LIBJCC.DLL libjcc.ext Required by PowerBuilder virtual machine
PBDWE70.DLL libpbdwe70x.ext DataStore support
PBJAG70.DLL libpbjag70x.ext, pbjag70.ext PowerBuilder support in Jaguar
PBRTC70.DLL -- RichText support
PBO7370.DLL libpbo7370x.ext Oracle 7.3 database driver
PBO8470.DLL libpbo8470x.ext Oracle 8.0.4 and later driver
PBODB70.INI pbodb70.ini PowerBuilder ODBC initialization file
PBODB70.DLL libpbodb70x.ext PowerBuilder ODBC interface
PBSYJ70.DLL libpbsyj70x.ext Adaptive Server Enterprise native database interface
PBJDS70.DLL libpbjds70x.ext JDBC database driver for Sun Java VM
-- libpbwfr70.ext PowerBuilder UNIX extension library
-- libsmartheap_mt.ext Required for PowerBuilder memory management
PBDWR70.PBD pbdwr70.pbd Web DataWindow support (requires PBDWE)
-- htmldw.js Web DataWindow support
CLASSES.ZIP classes/PBjdbcname Java classes for PowerBuilder JDBC drivers (required for JDS)

[Back to page 1] [Next to page 3]


 

DOCUMENT ATTRIBUTES
Last Revised: Aug 19, 1999
Product: Not Product Specific
Business or Technical: Technical
  
Content Id: 1011232
Infotype: White Paper-Technical
 
 
 

 
© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics