Configuration Requirements for Windows Vista and Later
When you run PowerBuilder on Windows Vista or Windows 7 under a standard user account, and attempt to deploy Web Forms or Web Service projects, the User Account Control (UAC) dialog box appears. This dialog box allows you to elevate your privileges for the purpose of deployment.
| Settings for | Required changes |
|---|---|
| Windows firewall | Enable exceptions for WMI and file and printer sharing |
| UAC (When you are not running PowerBuilder with the built-in Administrator account) | If the development and deployment computers are in the same domain, connect to the remote computer using a domain account that is in its local Administrators group. Then UAC access token filtering does not affect the domain accounts in the local Administrators group. You should not use a local, nondomain account on the remote computer because of UAC filtering, even if the account is in the Administrators group.
If the development and deployment computers are in the same workgroup, UAC filtering affects the connection to the remote computer even if the account is in the Administrators group. The only exception is the native �Administrator� account of the remote computer, but you should not use this account because of security issues. Instead, you can turn off UAC on the remote computer. and if the account you use has no remote DCOM access rights, you must explicitly grant those rights to the account. |
| DCOM | Grant remote DCOM access, activation, and launch rights to a nondomain user account in the local Administrators group of the remote computer if that is the type of account you are using to connect to the remote computer. |
Deploying to the default application pool
Virtual directories in IIS 7 and later are hosted in an application pool. An application pool is the host process for one or more Web applications. When you deploy a PowerBuilder Web Forms application to IIS 7 or later, the application is deployed to a PowerBuilder-specific application pool named PBAppPool. On 64-bit operating systems, the PBAppPool pool is configured to run 32-bit applications.
To avoid compatibility issues with some features, Web Forms applications deployed from PowerBuilder to IIS 7 or IIS 7.5 must run in an application pool that uses the classic managed pipeline mode, where ASP.NET runs as an ISAPI extension. The PBAppPool application pool uses the classic managed pipeline mode by default.
- Changing Application Pool Identity for IIS 7.5
IIS7.5 includes a new identity type, ApplicationPoolIdentity, and sets it as the default identity for application pools. - Creating an Application Pool
Create and configure an application pool to host PowerBuilder Web Forms applications. - Enabling 32-bit Applications on 64-bit Operating Systems
On 64-bit operating systems, you must enable the application pool to run 32-bit applications. - Moving an Application into a Different Application Pool
If you have created and configured a new application pool for PowerBuilder, you must move your PowerBuilder Web Forms applications into the pool. - Application Directory Permissions
When you deploy a new Web Forms target, a temp directory is created in the Inetpubwwwrootapplication_name directory, where application_name is the name of your application, and several subdirectories are created in the Inetpubwwwrootapplication_name_root directory.