Version PB12.5 of the WebService Deployment Guide

Environment: WINDOWS SERVER R2 + SQL Server 2008R2

1, install IIS 7.X

2, Installation Dot.net 4.0

3, install SQL Server R2 (note that you do not have to install SNC, SQL 2008r2 has been brought)

4, install the PB12.5 prerequisites

5, install PB. NET components (Runtime DLL): PBNETRT125. MSI, or you can install PB12.5 without trouble. If it is a decrypted version of the pb12.5, the generated pbnetrt125.msi can not be registered through the GAC, and therefore can not be installed, so it is best to simply ann a PB12.5, and then decrypt. I do not understand the decryption, you go to ask Baidu. If you want the Pbnetrt125.msi to be successful, run the PowerBuilder Runtime Packager tool to generate the installation package with a PB12.5 that is not decrypted. After the installation and decryption, there is no limit.

6, after installation, install your WebService package into IIS (you can copy it yourself, and then build the virtual directory). To change the database connection, change the properties of the connection pool:

(1) The operating mode is 32 bits, note must not be 64 bit, because PB can only run in 32-bit mode.

(2). NET version to set to 4.0, Pipeline mode is integrated.

(3) In IIS server Settings, ISAPI and CGI restrictions have been allowed to be performed by 4.0.

7, the most important step: this time must restart the server, or your program run this time, it must be said to find a Sybase DLL, Sybase does not tell you why, anxious to die you oh. The purpose of restarting the server is to enable the PB DLL path to take effect!

8, you can not put on webservice to go to the wall.

Version PB12.5 of the WebService Deployment Guide