PowerBuilder component 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.
To update a Windows server, run the setup program in the PBVM.zip file
distributed with the maintenance release. PowerBuilder VMs for UNIX
servers are available on the EBFs/Updates page on the Sybase Web
site at http://downloads.sybase.com.
The files listed in Table 39-16 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 libjcc library. However,
for components deployed to EAServer, you should always use the libjcc file
distributed with EAServer, not the libjcc file distributed
with PowerBuilder.
| Windows | UNIX | Description |
|---|---|---|
| PBVM90.DLL | libpbvm90x.ext* | PowerBuilder virtual machine (required for all PowerBuilder components) |
| PBDWE90.DLL | libpbdwe90x.ext | DataStore support |
| PBJAG90.DLL | libpbjag90x.ext, pbjag90.ext | PowerBuilder support in EAServer |
| PBDWR90.PBD | pbdwr90.pbd | Web DataWindow support (requires PBDWE) |
| htmldw.js | htmldw.js | Web DataWindow support |
| PBRTC90.DLL | — | RichText support |
| PBXerces90.DLL xerces-c_2_1_0.dll |
libxerces90x.ext, libxerces-c_2_1_0.ext | XML support |
| PBDOM90.DLL | libpbdom90x.ext | PBDOM support |
| EasySoap.DLL ExPat.dll libeay32.dll ssleay32.dll pbsoapclient90.dll |
— | SOAP clients for Web services |
| PBO7390.DLL | libpbo7390x.ext | Oracle 7.3 database driver |
| PBO8490.DLL | libpbo8490x.ext | Oracle 8.0.x and Oracle8i 8.1.x database driver |
| PBO9090.DLL | libpbo9090x.ext | Oracle9i database driver (on Solaris only) |
| PBODB90.INI | pbodb90.ini | PowerBuilder ODBC initialization file |
| PBODB90.DLL | libpbodb90x.ext | PowerBuilder ODBC interface |
| PBSYJ90.DLL | libpbsyj90x.ext | Adaptive Server Enterprise native database interface |
| PBJDB90.DLL | libjdb80x.ext | JDBC database driver for Sun Java VM JRE 1.1 or later |
| — | libpbwfr90.ext | PowerBuilder UNIX extension library |
| pbjdbc1290.jar | pbjdbc1290.jar | Java classes for PowerBuilder JDBC drivers (required for JRE 1.2 or later) |
* ext represents the platform-specific
extension for library names; for example, on Solaris this file is libpbvm90x.so.
On Windows
You can use the PowerBuilder VM installer, available in the
PBVM folder on the CD, to install the files listed in Table 39-16. The PBVM setup
program also installs the PowerBuilder 9.0 version of the Web DataWindow
server component (HTMLGenerator90) and the PBDebugBroker9 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 39-16 were not installed when you installed EAServer, they might be available
for your platform from the Sybase Downloads site on the EBFs/Updates 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 39-16 in order
to use connection caches. When a PowerBuilder component uses a connection
cache, the appropriate PowerBuilder driver is loaded.