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 on the Appeon Web site at https://www.appeon.com/policies/Appeon_PowerBuilder_FreeDownloadTerms.pdf.
You may redistribute Apache files included with PowerBuilder to your users. Any use or distribution of the Apache code included with PowerBuilder 2017 and later must comply with the terms of the Apache License which is located in the free download terms document for PowerBuilder 2017 and later.
Version 0.20.5 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 at http://xmlgraphics.apache.org/fop/.
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. For more information about Xerces, see the Xerces C++ Parser Web site at http://xerces.apache.org/xerces-c/.
Visual C++ runtime, Active Template, and GDI+ libraries
When you deploy the core PowerBuilder runtime files, you must ensure that 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 \Program Files\Appeon\Shared\PowerBuilder folder, or from the DLL archive Web site at https://dlldump.com or http://driverskit.com. 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.
The PowerBuilder runtime files also have a runtime dependency on Microsoft Windows GDI+ (gdiplus.dll). The GDI+ graphics design interface is included by default in the system paths of all Windows platforms currently supported by PowerBuilder.
Files must be installed before running MSI or MSM file
Some files installed by the MSI or MSM file generated by the PowerBuilder Runtime Packager have dependencies on these files. For example, atl100.dll and gdiplus.dll must be installed on the user's computer before the pbjvm170.dll file can be registered. Make sure these files are on the target computer before you run the installation module generated by the Runtime Packager.
Ink picture libraries
Microsoft.Ink, Microsoft.Ink.dll, and Microsoft.Ink.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 a redistributable package containing the DirectX runtime from the Microsoft Web site at https://www.microsoft.com/en-us/download/details.aspx?id=9894.
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.
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 http://www.oracle.com/technetwork/java/javase/downloads/index.html.
PowerBuilder includes the EasySoap++ library in executable form in EasySoap170.dll, which is dynamically linked to PBSoapClient170.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 Support\WSExtn folder on the DVD. In addition, the object code and Microsoft Visual C++ project file for the PBSoapClient170.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 EasySoap170.dll. You can also relink PBSoapClient170.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 PBSoapClient170.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 PBSoapClient170.pbx.
