Preparing a local development environment

In order to quickly get started with PowerServer, we will use a local development machine for all roles (development PC, client, Web server, .NET server, and database server).

"A local development environment" does not mean the development PC only; it means all roles in one machine, as illustrated in the following graph. And this represents only one supported environment (not all), for example, IIS is used as the Web server here for hosting the client app files (although Apache and Nginx web servers are also supported), the built-in Kestrel server is used as the .NET server here for hosting the PowerServer Web APIs (although IIS, Docker, Kubernetes are also supported), the SQL Anywhere database is used as an example (although PostgreSQL, SQL Server, Oracle etc. are also supported), Chrome is used as an example (although Firefox and Edge are also supported). For all supported environment, refer to Installation > Installation requirements.

"A local development environment" aims to help you get started quickly and get successful result easily. It is not intended for production use.

After you have a successful result in Guide 1, you can proceed to Guide 2 to learn more about the various environment setup such as configuring and using IIS as the .NET server (for hosting PowerServer Web APIs).


The following steps will guide you through preparing "a local development environment".

Step 1: Prepare a Windows 10 (64-bit) machine.

PowerBuilder IDE can only run on Windows 11, 10 or 8.1.

Step 2: Make sure this machine has the Internet connection.

The machine will need to access the NuGet site and the Appeon license site.

Step 3: Set up each individual role in this machine by installing the following software.

Role

Requires the following software

Web Server

.NET Server

  • Kestrel (Kestrel is automatically included in the PowerServer Web APIs, so nothing needs to be installed here)

    In the development environment (for quick running and testing purpose), you can directly run the PowerServer Web APIs on the ASP.NET Core Kestrel server (a light-weight web server automatically included and enabled in the ASP.NET Core project); and as Kestrel is by default included in the PowerServer Web APIs, there is no need to install any other software.

    For more about the .NET Server setup such as configuring IIS as the .NET server for hosting PowerServer Web APIs, refer to Guide 2.

Database Server

Development

Development

Step 1: Download the PowerBuilder Installer executable from the Downloads page on the Appeon User Center (login is required) and then run the PowerBuilder Installer.

Step 2: Select the Programs tab and make sure the following programs are selected:

  • PowerServer Toolkit 2022

  • PowerBuilder IDE 2022

Step 3: Select the Components tab and make sure the following component is selected:

  • PowerBuilder Runtime 2022

Step 4: Select the Additional Options tab and make sure the SQL Anywhere engine is selected.

A 32-bit ODBC driver is required as PowerBuilder IDE is a 32-bit program.

If you select to use the PostgreSQL engine for running the PowerBuilder demo database, make sure both the PostgreSQL client (included in Command Line Tools of the PostgreSQL Windows installer) and PostgreSQL ODBC driver (32-bit) are installed.


The demo database file is automatically installed to %Public%\Documents\Appeon\PowerBuilder 22.0\ and the corresponding ODBC data source is automatically created during the PowerBuilder installation.

  • If SQL Anywhere engine is installed and selected, the demo database file is pbdemo2022.db and the ODBC data source is PB Demo DB V2022.

  • If PostgreSQL engine is installed and selected, the demo database file is pbpostgres2022.dmp and the ODBC data source is PB Postgres V2022.

Client

  • Install Google Chrome (or Mozilla Firefox, or Microsoft Edge (Chromium-based))