Third-party components and deployment
PowerBuilder applications have some dependencies on third-party components
that are installed with PowerBuilder. Most of these components are not installed
with the PowerBuilder Runtime Packager. You may redistribute some
of these components with your application, but others must be obtained
from the vendor.
For information about components that can be freely downloaded,
see the free download terms document. A copy of this document is
located in the Support directory on the DVD
and on the Sybase Web site
.
Apache files
You may redistribute Apache files included with PowerBuilder
to your users. Any use or distribution of the Apache code included
with PowerBuilder 11 must comply with the terms of the Apache License
which is located in the free download terms document for PowerBuilder
11.
Version 0.20.4 of the Apache Formatting Objects Processor
(FOP) is required if your application uses XSL-FO to save files
as PDF. For more information about FOP, see the Apache FOP Web site
.
The Apache Xerces files xerces-c_2_6.dll and xerces-depdom_2_6.dll are required
for XML Web DataWindow support, XML support for DataWindows and DataStores,
PBDOM, and SOAP clients for Web services. For more information about Xerces,
see the Xerces C++ Parser Web site
.
Microsoft files
When you deploy the core PowerBuilder runtime files, you must
ensure that the msvcr71.dll and msvcp71.dll Microsoft
Visual C++ runtime libraries and the Microsoft
.NET Active Template Library (ATL) module, atl71.dll,
are present on the user’s computer or server. The PowerBuilder
runtime files have a runtime dependency on these files and they
are required for all applications and components that require the
PowerBuilder runtime. For more information about obtaining and using
these files, see the Microsoft Web site
.
The PowerBuilder runtime files also have a runtime dependency
on Microsoft Windows GDI+ (gdiplus.dll).
PowerBuilder .NET targets cannot be launched if gdiplus.dll is
not available on the system. GDI+ is the subsystem of the Windows
XP or Windows Server 2003 operating system that implements enhanced
graphic capabilities for screens and printers. It is included with Windows
Vista but it is not part of the Windows 2000 operating system, therefore
if you deploy your PowerBuilder application to Windows 2000, you must
make sure that gdiplus.dll is available on
the target computer and in the system path. GDI+ can be
downloaded from the Microsoft Web site
.
Files must be installed before running MSI file Some files installed by the MSI file generated by the PowerBuilder
Runtime Packager have dependencies on these files. For example, atl71.dll and gdiplus.dll must
be installed on the user’s computer before the pbjvm110.dll file
can be registered. Make sure these files are on the target computer
before you run the MSI file generated by the Runtime Packager.
Microsoft.Ink, Microsoft.Ink.dll,
and Microsoft.Resources.dll are required if your
application uses InkEdit and InkPicture controls. These files are
part of the Microsoft Windows XP Tablet PC Edition Software Development
Kit 1.7, which is available on the Microsoft Web site
.
Microsoft has discovered some incompatibility issues between
these DLLs and the .NET Framework 2.0. You can obtain an update
to address these issues from Microsoft
.
PowerBuilder .NET Web Forms use Internet Explorer Web Controls
to display correctly and to provide functionality for the Tab, TreeView,
and Toolbar controls. You can download IE Web Controls from the Microsoft Web site
. For detailed information about
installing the controls, see Deploying Applications and
Components to .NET
.
Sun Microsystems files
The Java Runtime Environment (JRE) is required for JSP targets,
EJB clients, JDBC connections, and saving as PDF using XSL-FO. For
a copy of third-party terms and conditions for the JRE,
see the free download terms document.The JRE can be downloaded from
the Sun Developer Network
.
Software used for SOAP clients for Web services
PowerBuilder includes the EasySoap++ library
in executable form in EasySoap110.dll, which
is dynamically linked to PBSoapClient110.pbx.
The EasySoap++ library and its use are covered
by the GNU Lesser General Public License (LGPL). For a copy of this
license, see the free download terms document. You may distribute
the EasySoap++ library to third parties subject
to the terms and conditions of the LGPL. Please read the LGPL prior
to any such distribution.
The complete machine-readable source code for the EasySoap++ library
is provided in the EasySoap.zip file in the SupportWSExtn folder
on the DVD. In addition, the object code and Microsoft Visual C++ project
file for the PBSoapClient110.pbx are provided
in the soapclient.zip file in the same directory.
These files are provided under the terms of the LGPL so that
you can modify the EasySoap++ library and then
relink to produce a modified EasySoap110.dll.
You can also relink PBSoapClient110.pbx with
the modified EasySoap++ import library. According
to the terms of the LPGL, it is understood that you will not necessarily
be able to recompile PBSoapClient110.pbx to
use the definitions you have modified in the EasySoap++ library.
Follow the instructions in the Readme.txt file
in the soapclient.zip file to build PBSoapClient110.pbx.