Checklist for deployment

For all .NET targets

For deployment of all .NET target types, production servers or target computers must have:

For .NET Web Forms and Web Service targets

For .NET Web Forms and Web Service targets, production servers must also have:

For information on three different methods for deploying .NET Web Forms applications to a production server, see “Deploying to a production server”. These methods are also valid for deployment of .NET Web Service components.

Deploying PowerBuilder runtime files

The simplest way to deploy PowerBuilder runtime DLLs and .NET assemblies to production servers or target computers is to use the PowerBuilder Runtime Packager tool. The Runtime Packager creates an MSI file that installs the files you select, registers any self-registering DLLs, and installs the .NET assemblies into the global assembly cache (GAC).

NoteRuntime file version When you deploy any PowerBuilder application or component, you should always make sure that the version and build number of the PowerBuilder runtime files on the target computer or server is the same as the version and build number of the DLLs on the development computer. Mismatched DLLs can result in unexpected errors in all applications. If the development computer is updated with a new build, PowerBuilder .NET applications and components must be rebuilt and redeployed with the new runtime files.

For information on all the steps required to migrate .NET applications and components that you first deployed with earlier releases of PowerBuilder, see the “Migration information” section of your current Release Bulletin. PowerBuilder release bulletins are available from links on the Product Manuals Web site.

For more information about using the Runtime Packager, see the chapter on “Deploying Applications and Components” in Application Techniques. That chapter lists the base components deployed when you select PowerBuilder .NET Components in the Runtime Packager. The Runtime Packager also installs additional components depending on your selections in the tool’s user interface.

You can choose to use another tool to install the runtime files on the server or target computer. You should install the runtime files listed in Table 1-3 that your application requires. You should also install the database interfaces your application uses. The database interfaces are listed in Table 1-4.

Sybase.PowerBuilder files are strong-named .NET assemblies that can be installed into the GAC. For more information about the GAC, see “Installing assemblies in the global assembly cache”.

Table 1-3: PowerBuilder runtime files for .NET targets

Name

Required for

pbshr120.dll, Sybase.PowerBuilder.ADO.dll, Sybase.PowerBuilder.Common.dll, Sybase.PowerBuilder.Core.dll, Sybase.PowerBuilder.Interop.dll, Sybase.PowerBuilder.Web.dll, Sybase.PowerBuilder.Win.dll

All

pbrth120.dll

.NET Web Forms and ADO.NET

pbdwm120.dll, Sybase.PowerBuilder.Datawindow.Web.dll, Sybase.PowerBuilder.DataWindow.Win.dll, Sybase.PowerBuilder.Datawindow.Interop.dll

DataWindows and DataStores

pbdpl120.dll

Data pipelines (Windows Forms only)

Sybase.PowerBuilder.EditMask.Win.dll, Sybase.PowerBuilder.EditMask.Interop.dll

Edit masks

Sybase.PowerBuilder.Graph.Web.dll, Sybase.PowerBuilder.Graph.Win.dll, Sybase.PowerBuilder.Graph.Core.dll, Sybase.PowerBuilder.Graph.Interop.dll

Graphs

pbrtc120.dll, Sybase.PowerBuilder.RTC.Win.dll, Sybase.PowerBuilder.RTC.Interop.dll, tp13.dll, tp13_bmp.flt, tp13_css.dll, tp13_doc.dll, tp13_gif.flt, tp13_htm.dll, tp13_ic.dll, tp13_ic.ini, tp13_jpg.flt, tp13_obj.dll, tp13_pdf.dll, tp13_png.flt, tp13_rtf.dll, tp13_tif.flt, tp13_tls.dll, tp13_wmf.flt, tp13_wnd.dll, tp4ole13.ocx

Rich text

PBXerces120.dll, xerces-c_2_6.dll, xerces-depdom_2_6.dll

XML export and import

Sybase.PowerBuilder.WebService.Runtime.dll, Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll

Web service DataWindows

ExPat120.dll, libeay32.dll, ssleay32.dll, xerces-c_2_6.dll, xerces-depdom_2_6.dll, EasySoap120.dll, pbnetwsruntime120.dll, pbsoapclient120.pbx, pbwsclient120.pbx, Sybase.PowerBuilder.WebService.Runtime.dll, Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll

Web service clients

pblab120.ini

Label DataWindow presentation-style predefined formats

pbtra120.dll, pbtrs120.dll

Database connection tracing

Table 1-4 lists the files you need to deploy if your application uses a PowerBuilder database interface.

Table 1-4: Database connectivity runtime files for .NET targets

Name

Required for

pbin9120.dll

Informix I-Net 9 native interface

pbo84120.dll

Oracle8i native interface

pbo90120.dll

Oracle9i native interface

pbo10120.dll

Oracle 10g native interface

pbsnc120.dll

SQL Native Client for Microsoft SQL Server native interface

pbdir120.dll

Sybase DirectConnect™ native interface

pbase120.dll

Sybase Adaptive Server® Enterprise native interface (Version 15 and later)

pbsyc120.dll

Sybase Adaptive Server Enterprise native interface

pbado120.dll, pbrth120.dll, Sybase.PowerBuilder.Db.dll, Sybase.PowerBuilder.DbExt.dll

ADO.NET standard interface

pbjvm120.dll, pbjdb120.dll, pbjdbc12120.jar

JDBC standard interface

pbodb120.dll, pbodb120.ini

ODBC standard interface

pbole120.dll, pbodb120.ini

OLE DB standard interface

Installing assemblies in the global assembly cache

When the Common Language Runtime (CLR) is installed on a computer as part of the .NET Framework, a machine-wide code cache called the global assembly cache (GAC) is created. The GAC stores assemblies that can be shared by multiple applications. If you do not want or need to share an assembly, you can keep it private and place it in the same directory as the application.

If you do not want to use the Runtime Packager to deploy your application, you should use Windows Installer or another installation tool that is designed to work with the GAC. Windows Installer provides assembly reference counting and other features designed to maintain the cache.

On the development computer, you can use a tool provided with the .NET Framework SDK, gacutil.exe, to install assemblies into the GAC, or you can use Windows Explorer to drag and drop assemblies into the Windows\assembly directory.

You can also use the .NET Framework Configuration tool to add assemblies to the GAC. In the Windows Control Panel, select Administrative Tools>Microsoft .NET Framework 2.0 Configuration, then select Manage the Assembly Cache. The configuration tool is installed with the .NET Framework 2.0 SDK.

Assemblies deployed in the global assembly cache must have a strong name. A strong name includes the assembly’s identity as well as a public key and a digital signature. The GAC can contain multiple copies of an assembly with the same name but different versions, and it might also contain assemblies with the same name from different vendors, so strong names are used to ensure that the correct assembly and version is called.

For more information about assemblies and strong names, see the Microsoft library.