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.

Apache Files

You may redistribute the Apache files that are included with PowerBuilder to your users.

Any use or distribution of the Apache code included with PowerBuilder 2019 R2 must comply with the terms of the Apache License, which is located in the free download terms document for PowerBuilder.

Version 0.20.5 of the Apache Formatting Objects Processor (FOP) is required if your application uses XSL-FO to save files as PDF. See the Apache FOP website at

The Apache Xerces files xerces-c_2_8.dll and xerces-depdom_2_8.dll are required for XML Web DataWindow support, XML support for DataWindows and DataStores, PBDOM, and SOAP clients for Web services. See the Xerces C++ Parser website at

Microsoft Files

Special Microsoft files are required on runtime computers for various PowerBuilder features.

Visual C++ Runtime and the Active Template Library

When you deploy the core PowerBuilder runtime files, make sure the msvcr100.dll and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft .NET Active Template Library (ATL) module atl100.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. You can obtain these DLL files from the \%Appeon%\Shared\PowerBuilder or \%Appeon%\Shared\PowerBuilder\x64 folder, or from the DLL archive website. Make sure you obtain the same version (32-bit or 64-bit) of the these DLL files as the version (32-bit or 64-bit) of the PowerBuilder application executable.


Some files that are installed by the MSI file generated by the PowerBuilder Runtime Packager have dependencies on these files. For example, atl100.dll must be installed on the user's computer before the pbjvm<version>.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.

Ink Picture Libraries

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 .NET Framework 3.5 and later, and are available at C:\Windows\winsxs and its sub-folders after .NET framework is installed.

DirectX Runtime

PowerBuilder applications can use DirectX 3D rendering to display 3D graphs (Pie3D, Bar3D, Column3D, Line3D, and Area3D) with a more sophisticated look. You can use data item or series transparency with the DirectX graph styles to improve the presentation of data.

The DirectX 3D rendering depends on the DirectX runtime. The first time you select the Render3D check box on the General tab of the Properties view for a 3D graph, PowerBuilder launches the DirectX installer. If you opt out of the installation, the Render3D property is ignored. End users of PowerBuilder applications must also have the DirectX runtime installed on their computers to view the DirectX graph styles. You can download the DirectX runtime from the Microsoft Web site at

For computers with older graphics drivers, you can check whether DirectX is supported by running dxdiag.exe. This file is typically installed in the Windows\System32 directory. The Display tab of the DirectX Diagnostic Tool that opens when you run dxdiag.exe indicates whether Direct3D is enabled.

Oracle files

The Java Runtime Environment (JRE) is required for 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 Oracle Technology Network at

Software Used for SOAP Clients for Web Services (Obsolete)

PowerBuilder applications can use EasySoap to connect to Web services. The EasySoap++ library in executable form (EasySoap190.dll), which is dynamically linked to PBSoapClient190.pbx, is distributed with PowerBuilder.

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.

The complete machine-readable source code for the EasySoap++ library is in the file in the Support\WSExtn folder on the installation package. In addition, the object code and Microsoft Visual C++ project file for the PBSoapClient190.pbx are in the file in the same directory.

These files are provided under the terms of the LGPL so you can modify the EasySoap++ library and then relink to produce a modified EasySoap190.dll. You can also relink PBSoapClient190.pbx with the modified EasySoap++ import library. According to the terms of the LPGL, you may not be able to recompile PBSoapClient190.pbx to use the definitions you have modified in the EasySoap++ library.

Follow the instructions in the Readme.txt file in the file to build PBSoapClient190.pbx.

List of Free Download Components (Including Open Source Components)

For the complete list of the free download components (including open-source components), view the Free Download Terms document on the Appeon website.