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 41-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 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 libpbvm105x.so.

Table 41-16: PowerBuilder files required on EAServer host

Windows

UNIX

Description

PBVM105.DLL

libpbvm105x.ext

PowerBuilder virtual machine (required for all PowerBuilder components)

PBSHR105.DLL

pbshr105.ext

Required by PowerBuilder virtual machine

PBDWE105.DLL

libpbdwe105x.ext

DataStore support

PBJAG105.DLL

libpbjag105x.ext, pbjag105.ext

PowerBuilder support in EAServer

PBDWR105.PBD

pbdwr105.pbd

Web DataWindow support (requires PBDWE)

htmldw.js

htmldw.js

Web DataWindow support

PBRTC105.DLL and additional runtime files listed in Table 41-4

RichText support

PBXerces105.dll, xerces-c_2_6.dll, xerces-depdom_2_6.dll

libxerces105x.ext, libxerces-c_2_1_0.ext

XML support

pbdom105.pbx

libpbdom105x.ext

PBDOM support

EasySoap105.dll, ExPat105.dll, libeay32.dll, ssleay32.dll, pbsoapclient105.pbx, pbwsclient105.pbx, pbnetwsruntime105.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)

PBO84105.DLL

libpbo84105x.ext

Oracle 8.0.x and Oracle8i 8.1.x database driver

PBO90105.DLL

libpbo90105x.ext (Solaris and Linux only)

Oracle9i database driver

PBO10105.DLL

libpbo10105x.ext (Solaris and Linux only)

Oracle 10g database driver

PBODB105.INI

pbodb105.ini

PowerBuilder ODBC initialization file

PBODB105.DLL

libpbodb105x.ext

PowerBuilder ODBC interface

PBSYJ105.DLL

libpbsyj105x.ext

Adaptive Server Enterprise native database interface

PBJDB105.DLL

libjdb105x.ext

JDBC database driver for Sun Java VM JRE 1.1 or later

libpbwfr105.ext

PowerBuilder UNIX extension library

pbjdbc12105.jar

pbjdbc12105.jar

Java classes for PowerBuilder JDBC drivers (required for JRE 1.2 or later)

On Windows

You can use the PowerBuilder VM installer, available in the PBVM folder on the CD, to install the files listed in Table 41-16. The PBVM setup program also installs the PowerBuilder 10.5 version of the Web DataWindow server component (HTMLGenerator105) and the PBDebugBroker10 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 41-16 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 41-16 in order to use connection caches. When a PowerBuilder component uses a connection cache, the appropriate PowerBuilder driver is loaded.

To create a connection cache for an Informix or DB2 database, you can use a DataDirect ODBC driver that is included with EAServer. After creating an ODBC data source using the file shown in Table 41-17, create an EAServer connection cache to the ODBC data source.

Table 41-17: PowerBuilder DataDirect ODBC files for UNIX

Name

Database

PBinf914.ext

Informix 7.x, 9.x by means of Informix-Client SDK 2.x

PBdb214.ext

DB2 Universal Database (UDB)