In addition to the COM server file generated in PowerBuilder, the PowerBuilder runtime files listed in Table 41-18 should be installed on the computer on which the server will run if the component uses the feature listed in the table.
Name |
Description |
|---|---|
PBVM105.DLL |
PowerBuilder virtual machine (required for all PowerBuilder components) |
PBCOMRT105.DLL |
PowerBuilder COM runtime |
PBSHR105.DLL |
Required by PBVM105.DLL |
LIBJCC.DLL |
Required by PBVM105.DLL |
LIBJUTILS.DLL |
Required by LIBJCC.DLL |
PBDWE105.DLL |
Required if the component uses DataStores |
PBRTC105.DLL and additional runtime files listed in Table 41-4 |
Required if the component uses Rich Text |
PBODB105.INI |
PowerBuilder ODBC initialization file required for database connectivity |
PBODB105.DLL |
PowerBuilder ODBC interface required for database connectivity |
Installed path \Program Files\Sybase\Shared\PowerBuilder
Deployment path In the same directory as the COM server or a directory on the system path.
Registry entries The PowerBuilder COM server is self registering, which means that you can use the REGSVR32 utility to register it on the computer on which it will be used.
Notes For information about deploying PowerBuilder COM servers, see “Deploying a PowerBuilder COM server”.
Database drivers
If your component connects to a database, you must also deploy
the appropriate database drivers. You can use any database driver
with a COM component, but you must use ODBC if
you want to take advantage of COM+ support for transaction
management and connection pooling. If you require support for connection
pooling only, you can use any thread-safe ODBC driver. If you also require
support for transactions, you must use a driver that supports the Microsoft
Distributed Transaction Coordinator (DTC), such as the Microsoft ODBC
driver for Oracle or the Microsoft ODBC driver for SQL Server.
For more information about database drivers, see “Database connections”.
