This chapter provides the information required to deploy applications and components to users' computers and servers. It describes a tool you can use to package PowerBuilder runtime files, and lists the files you need to deploy with various kinds of targets.
These lists of files sometimes need to be updated, as, for example, when new database interfaces become available. For information about such changes, see the Release Bulletin for the version of PowerBuilder you are using.
Dll Files Com Client Registration Key
Regardless of the type of application you are deploying, you must include any supporting files such as dynamic libraries, resources like BMP and ICO files, online Help files, and initialization files. Each application type requires a different set of supporting files. The PowerBuilder runtime files, such as pbvm.dll and pbdwe.dll, and PowerBuilder database interfaces such as pbin9 and pbo10.dll, can be freely distributed with your application with no licensing fee.
Packaging an Application for Deployment helps you make decisions about deploying a PowerBuilder executable application, such as whether to use dynamic libraries, Pcode or machine code, and resource files. It also provides a checklist to make sure you install all the required pieces.
If you are deploying a Web application or a transaction server component, you will find the information about PowerBuilder dynamic libraries (PBDs) and PowerBuilder resource files (PBRs) in that chapter helpful. You should also read the documentation for specific types of applications, components, or plug-ins.
This chapter is intended to help you write installation programs using a third-party software package that creates installation configurations. It tells you which files each computer needs, where you can find the files, where they should be installed, and what registry settings need to be made. PowerBuilder also provides a tool, described in PowerBuilder Runtime Packager, to help you package the files your application needs.
The Installed path listed after some of the tables in this chapter is the location where files are installed when you install PowerBuilder and select the default installation location. When you build an installation program for your application, you can copy files from this location to your staging area.
Some tables are followed by a list of the Registry entries your installation program needs to make so that your application or component can find the files it needs. When an application runs on Windows, it looks for supporting files in these locations and in this order:
Set the data value of the (Default) string value to the directory where the application is installed and create a new string value called Path that specifies the location of shared files. The following example shows a typical registry entry for an application called myapp.exe that uses SQL Anywhere. The registry key is enclosed in square brackets and is followed by string values for the key in the format "Name"="Value":
Registry update files that have a .REG extension can be used to import information into the registry. The format used in registry key examples in this chapter is similar to the format used in registry update files, but these examples are not intended to be used as update files. The path names in data value strings in registry update files typically use a pair of backslashes instead of a single backslash, and the "Default" string value is represented by the at sign (@).
If your application uses a control that is not self registering, your setup program needs to register it manually on each user's computer. To find out whether a control is self registering, see the documentation provided with the control. Depending on the development and deployment platforms and the controls you are deploying, you might need to copy additional DLLs or license files to the Windows system directories on the target computer.
The PowerBuilder Runtime Packager is a tool that packages the PowerBuilder files an application needs at runtime into a Microsoft Windows Installer (MSI) package file or a Microsoft merge module (MSM). Windows Installer is an installation and configuration service that is installed with recent Microsoft Windows operating systems. The MSM file must be incorporated into an application MSI file using a merge tool before the components it contains can be installed on a client computer.
The Runtime Packager can be used with client applications installed on Windows systems and applications deployed to the .NET Framework. It does not install most third-party components. See Third-party components and deployment for more information.
Make sure that you read the sections referenced in Table: PowerBuilder files required for deployment that apply to your application for more information about where files that are not installed by the Runtime Packager should be installed.
The DLLs for the database interfaces you select are added to the package. For ODBC and OLE DB, the pbodb.ini file is also added. For JDBC, the pbjdbc12.jar and pbjvm.dll files are also added. The Java Runtime Environment (JRE) is not added. See Third-party components and deployment.
If your application uses the old editor (TX Text Control ActiveX 24.0 Professional/Enterprise) for a RichTextEdit control or RichText DataWindow, you should follow the vendor's documentation to package the files required for running this editor.
The Runtime Packager adds the PBDWExcel12Interop.dll and Sybase.PowerBuilder.DataWindow.Excel12.dll files to the MSM or MSI package that you generate. It does not add the .NET Framework that is also required for Microsoft Excel support.
The Sybase.PowerBuilder.DataWindow.Excel12.dll file will be automatically installed to the Windows GAC folder, for example, C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Sybase.PowerBuilder.DataWindow.Excel12, if you run the MSM or MSI package. However, if you manually copy runtime DLLs to the client (instead of using the MSM or MSI package), make sure to copy the Sybase.PowerBuilder.DataWindow.Excel12.dll file to the same directory as the application executable, as this file is a C# assembly DLL and cannot be loaded through the environment variable.
The Runtime Packager adds required files for both the EasySoap and .NET Web service engines when you select the SOAP Client for Web Service check box. For more information about required files for these services, see PowerBuilder extensions.
Web service DataWindows (OData and SOAP) and SOAP client are obsolete features. Obsolete features are still available to use, but are no longer eligible for technical support and will no longer be enhanced.
The Runtime Packager creates an MSI or MSM file that includes the files required by the components you selected, as well as the runtime DLLs for standard PowerBuilder applications listed in the following table.
The MSI file generated by the PowerBuilder Runtime Packager 2019 R3 tool has been enhanced, so that runtime files of different builds at the same major version (starting from 2019 R3 GA) can be installed and coexisting on the same computer, for example, 2019 R3 and 2019 R2 can coexist, multiple 2019 R3 MRs can coexist. And the MSI file no longer sets the runtime file path in the system PATH environment variable; therefore, the user will need to decide which build of runtime files will be loaded by the application executable file and place the application executable and the runtime files in the same folder.
The MSM file is similar to an MSI file, but the MSM file must first be merged into an installation package before its components can be installed on a client computer. A merge tool is required to merge the MSM file into an MSI installation package.
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.
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 (obsolete). For more information about Xerces, see the Xerces C++ Parser website at -c/.
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 %AppeonInstallPath%\Common\PowerBuilder\Runtime [version]\ (for 32-bit) or %AppeonInstallPath%\Common\PowerBuilder\Runtime [version]\x64 (for 64-bit) 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.
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.
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 pbjvm.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.
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. 2ff7e9595c
Comments