To run PowerBuilder components in EAServer, the runtime libraries for the version and build number of PowerBuilder in which the components were developed must be available on the server. When you install a maintenance release of PowerBuilder and deploy new or updated components to EAServer, make sure that the PowerBuilder VM on the servers is also updated.
The files listed in Table 36-14 are required on the EAServer host on which components generated in PowerBuilder will run. 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 server. The PowerBuilder VM also requires the EAServer libjcc file and its dependent files. In the UNIX column of the table, ext represents the platform-specific extension for library names; for example, on Solaris this file is libpbvm120x.so.
Windows |
UNIX |
Description |
|---|---|---|
pbvm120.dll |
libpbvm120x.ext |
PowerBuilder virtual machine (required for all PowerBuilder components) |
pbshr120.dll |
pbshr120.ext |
Required by PowerBuilder virtual machine |
pbdwe120.dll |
libpbdwe120x.ext |
DataStore support |
pbjag120.dll |
libpbjag120x.ext, pbjag120.ext |
PowerBuilder support in EAServer |
pbdwr120.pbd |
pbdwr120.pbd |
Web DataWindow support (requires PBDWE) |
htmldw.js |
htmldw.js |
Web DataWindow support |
pbRTC120.dll and additional runtime files listed in Table 36-5 |
— |
RichText support |
PBXerces120.dll, xerces-c_2_6.dll, xerces-depdom_2_6.dll |
libxerces120x.ext, libxerces-c_2_1_0.ext |
XML support |
pbdom120.pbx |
libpbdom120x.ext |
PBDOM support |
EasySoap120.dll, ExPat120.dll, libeay32.dll, ssleay32.dll, pbsoapclient120.pbx, pbwsclient120.pbx, pbnetwsruntime120.dll, xerces-c_2_6.dll, xerces-depdom_2_6.dll, Sybase.PowerBuilder.WebService.Runtime.dll, Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll |
— |
SOAP clients for EasySoap and .NET Web services (for .NET Web services, the two Sybase.PowerBuilder DLL files must be deployed to the EAServer\Bin directory) |
pbo90120.dll |
libpbo90120x.ext (Solaris and Linux only) |
Oracle9i database driver |
pbo10120.dll |
libpbo10120x.ext (Solaris and Linux only) |
Oracle 10g database driver |
pbora120.dll |
libpbora120x.ext (Solaris and Linux only) |
Oracle 11g database driver |
pbodb120.ini |
pbodb120.ini |
PowerBuilder ODBC initialization file |
pbodb120.dll |
libpbodb120x.ext |
PowerBuilder ODBC interface |
pbsnc120.dll |
libpbsnc120x.ext |
SQL Native Client native database interface |
pbsyj120.dll |
libpbsyj120x.ext |
Adaptive Server Enterprise native database interface |
pbjdb120.dll |
libjdb120x.ext |
JDBC database driver for Sun Java VM JRE 1.1 or later |
— |
libpbwfr120.ext |
PowerBuilder UNIX extension library |
pbjdbc12120.jar |
pbjdbc12120.jar |
Java classes for PowerBuilder JDBC drivers (required for JRE 1.2 or later) |
You can use the PowerBuilder VM installer, available in the PBVM folder on the DVD, to install the files listed in Table 36-14. The PBVM setup program also installs the PowerBuilder 12.0 version of the Web DataWindow server component (HTMLGenerator120) and the PBDebugBroker120 component required for remote debugging.
You can use other database drivers with EAServer components, but you must use one of the drivers listed in the table above if you want to take advantage of EAServer support for transaction management and instance pooling.
If the files listed in Table 36-14 were not installed when you installed EAServer, they might be available for your platform from the Sybase Downloads site on the EBFs/Maintenance page.
PowerBuilder components deployed to EAServer on a UNIX platform can have neither graphical dependencies nor dependencies on the Windows application programming interface. The shared libraries must be installed in the EAServer lib directory on the UNIX server. The Java classes required for the PowerBuilder JDBC driver must be installed in the EAServer html/classes/com/sybase/powerbuilder/jdbc directory.
Connection caches on UNIX PowerBuilder components require the database drivers listed inTable 36-14 in order to use connection caches. When a PowerBuilder component uses a connection cache, the appropriate PowerBuilder driver is loaded.
