PowerBuilder Runtime Packager – PB Docs 2019

Note

You must have Microsoft Visual C++ 2010 Redistributable Package
(32-bit or 64-bit) installed, if you use the EXE file generated by the
Runtime Packager. You must also have Microsoft .NET Framework 4.0
installed, if the Runtime Packager will install components such as
ADO.NET, MS Excel12 Support, and OData which rely on .NET Framework to
install and run.

To use the PowerBuilder Runtime Packager:

1. Select Programs>Appeon PowerBuilder 2019 R3>PowerBuilder
   Runtime Packager 2019 R3 from the Windows Start menu or launch the
   pbpack190.exe file in your %AppeonInstallPath%PowerBuilder
   [version]IDE directory.

   

2. Select the PowerBuilder Base Components.

3. Select the PowerBuilder Runtime Version.

4. Select whether to generate the PowerBuilder runtime files in a
   standalone MSI file or in an MSM merge module.

5. Select a location for the generated MSI or MSM file.

6. Select the database interfaces your application requires.

   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.

   Other ODBC or OLE DB files your application may require are not
   added. For information about deploying these files, see ODBC database drivers and supporting
   files and OLE DB database
   providers.

7. If your application uses the the following Web integration
   features, such as HTTPClient object, RESTClient object, OAuth 2.0, and
   WebBrowser control, select the corresponding check box.

   The Runtime Packager adds the files listed for HTTPClient
   object, RESTClient object, OAuth 2.0, and WebBrowser control in Table: Additional PowerBuilder runtime
   files.

8. If your application uses the rich text control for the
   RichTextEdit control or RichText DataWindow, select the corresponding
   check box.

   For 32-bit, you can select from

   • TX TextControl ActiveX 15.0

   • TX TextControl ActiveX 28.0

   • Rich Edit Control (TE Edit Control) (in the Obsolete
     Features section)

   For 64-bit, you can select from

   • TX TextControl ActiveX 28.0

   • Microsoft RichEdit Control (in the Obsolete Features
     section)

   The Runtime Packager adds the files listed for the rich text
   support in Table: Additional PowerBuilder
   runtime files.

   Rich Edit Control and Microsoft RichEdit Control are
   obsolete

   Rich Edit Control and Microsoft RichEdit Control are obsolete
   features. Obsolete features are still available to use, but are no
   longer eligible for technical support and will no longer be
   enhanced.

   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.

   To know more about the built-in editor and the old editor, see
   Rich text editors.

9. If your application uses the following features such as
   NativePDF, RibbonBar control, UI accessibility and automation, data
   compression, data encryption and decryption, and .NET assembly calls,
   select the corresponding check boxes.

   The Runtime Packager adds the files listed for these feature
   supports in Table: Additional PowerBuilder
   runtime files.

10. If your application saves DataWindow or graph data in Microsoft
    Excel format, select the MS Excel12 Support check box.

    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:WindowsMicrosoft.NETassemblyGAC_MSILSybase.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.

11. If your application uses the XML services provided by the
    PowerBuilder Document Object Model or if it is an EJB client
    (obsolete), select the EJB client or PB DOM check boxes.

    The Runtime Packager adds the DLLs, PBXs, and JAR files required
    by the selected component.

    EJB client is obsolete

    EJB client is obsolete features. Obsolete features are still
    available to use, but are no longer eligible for technical support
    and will no longer be enhanced.

12. If your application is a SOAP Web services client or if your
    application uses Web service DataWindows, select the SOAP Client for
    Web Service or Web Service DataWindow Support check boxes.

    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 and SOAP client are obsolete

    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.

13. Click Create.

    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.

    Base components selected	Files
    PowerBuilder components (Default file name for runtime package is PBCLTRT.msi)	libjcc.dll libjutils.dll libjtml.dll libsybunic.dll nlwnsck.dll pbacc.dll pbcomrt.dll pbcrypt.dll pbcsi.dll	pbdpl.dll pbdwe.dll pbdwr.pbd pbhttpclient.dll pbjag.dll pbjson.dll pbjvm.dll pboauth.dll	pbpdf.dll pbrestclient.dll pbshr.dll pbsysfunc.dll pbtra.dll pbtrs.dll pbuis.dll pbvm.dll