PowerBuilder components on EAServer
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 libpbvm125x.so.
|
Windows |
UNIX |
Description |
|---|---|---|
|
pbvm125.dll |
libpbvm125x.ext |
PowerBuilder virtual machine (required |
|
pbshr125.dll |
pbshr125.ext |
Required by PowerBuilder virtual machine |
|
pbdwe125.dll |
libpbdwe125x.ext |
DataStore support |
|
pbjag125.dll |
libpbjag125x.ext, pbjag125.ext |
PowerBuilder support in EAServer |
|
pbdwr125.pbd |
pbdwr125.pbd |
Web DataWindow support (requires PBDWE) |
|
htmldw.js |
htmldw.js |
Web DataWindow support |
|
pbRTC125.dll and additional |
— |
RichText support |
|
PBXerces125.dll, |
libxerces125x.ext, libxerces-c_2_1_0.ext |
XML support |
|
pbdom125.pbx |
libpbdom125x.ext |
PBDOM support |
|
EasySoap125.dll, ExPat125.dll, |
— |
SOAP clients for EasySoap and .NET Web |
|
pbo90125.dll |
libpbo90125x.ext (Solaris |
Oracle9i database |
|
pbo10125.dll |
libpbo10125x.ext (Solaris |
Oracle 10g database |
|
pbora125.dll |
libpbora125x.ext (Solaris |
Oracle 11g database |
|
pbodb125.ini |
pbodb125.ini |
PowerBuilder ODBC initialization file |
|
pbodb125.dll |
libpbodb125x.ext |
PowerBuilder ODBC interface |
|
pbsnc125.dll |
libpbsnc125x.ext |
SQL Native Client native database interface |
|
pbsyj125.dll |
libpbsyj125x.ext |
Adaptive Server Enterprise native database |
|
pbjdb125.dll |
libjdb125x.ext |
JDBC database driver for Sun Java VM |
|
— |
libpbwfr125.ext |
PowerBuilder UNIX extension library |
|
pbjdbc12125.jar |
pbjdbc12125.jar |
Java classes for PowerBuilder JDBC drivers |
On Windows
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.5 version of the Web DataWindow
server component (HTMLGenerator125) and the PBDebugBroker125 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.
On UNIX
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.