The PowerBuilder installable cloud apps support the following database types: SQL Anywhere (ODBC), PostgreSQL, SQL Server (including Azure SQL), MySQL, Informix, Oracle, and Adaptive Server Enterprise (ODBC). Please refer to Supported database types & versions for more information about the supported database types and versions.
A successful database connection will be required by the installable cloud app at the following two stages:
-
Stage 1: Configuring the database connection for project compilation
The database cache created in the PowerBuilder IDE will be used by the project compilation (PowerServer Toolkit will connect to the target database when converting the DataWindows to C# models).
The database cache will also be deployed to the PowerServer solution and then used for the database connection by the application at runtime.
-
Stage 2: Configuring the database connection for app runtime
For the application to successfully connect with the database at runtime, the database configurations (including downloading the database driver, creating the database cache, mapping the transaction object etc.) will be required.
This tutorial will provide step-by-step instructions to help you complete both stages.
Here is some information that you shall be noticed before reading this tutorial:
-
The database server to be connected should be configured properly.
-
PowerBuilder IDE is installed in a Windows 10 64-bit machine in this tutorial.
-
ODBC Data Source (64-bit) is used whenever ODBC is needed in this tutorial.
-
The IP address in this tutorial should be replaced with your actual IP address.
-
Be sure to complete both stages if you want to make the installable cloud app connect with the database successfully.
-
When the PowerServer project is built and deployed in the PowerBuilder IDE, the database connection configured in the Database Configuration dialog box and the transaction-to-cache mappings will be deployed and stored in the PowerServer C# solution. You can manually change these settings in the PowerServer C# solution later.
