Database Setup

If you are not at the Database tab yet, click the - icon in the toolbar to go to Database tab. DB AppMaker can connect to MySQL, PostgreSQL, Microsoft SQL Server, Oracle and SQLite.

Load Table Dynamically
If this option is enabled, a table will only be loaded when you select it in the database pane. If you just use a few tables out of a large database, this feature enables you to work faster. To enable this feature, simply check Load tables dynamically BEFORE pressing the Connect button.

 

MySQL

Select MySQL as database type.

There are 2 connection methods you can choose:

Direct Connection (default)

  1. Enter your database host/server name (or IP address), username, password and port number (default is 3306 for MySQL),
  2. Select your database,
  3. Click the [Connect] button to load the database information.
Note The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection info in the advanced setting Connection info of production server before you upload it to your production server. For example, if you have a testing MySQL Server installed on the same computer, you can use "localhost" as server name when you connect to it with DB AppMaker. The generated scripts will then try to connect to a MySQL Server on the same computer as the production Web server, if this is not the case, the connection will fail.

URL Connection (for remote database)

While the direct connection method is quick and easy, some remote MySQL server may not allow direct connection. DB AppMaker provides an alternative simple way to connect remote servers:

  1. Upload the PHP connection script provided by DB AppMaker to your site. Note that:

    1. The script is named "phpmaker.php" and can be found under your installed folder, usually C:\Program Files (x86)\DB AppMaker <version>\,
    2. Always use the script shipped with your version of DB AppMaker. DB AppMaker may not work with script shipped with previous versions.

  2. If it is the first time that you use this script, you may want to test the script with your browser:

    1. Browse to this script with your browser,

    2. Enter the connection info,
    3. Click "Get Database List" and then "View Schema", you should be able to view the schema of your database in XML properly. Now go back to DB AppMaker.

  3. Enter the SAME connection information, select URL for connection method, enter the URL of the script (e.g. http://servername/path/phpmaker.php), you can test the URL by clicking the [Test] button,




  4. Click the [Connect] button to load the database information. DB AppMaker will connect to the database server through the PHP script over HTTP.

 

PostgreSQL

Select PostgreSQL as database type.

There are 2 connection methods you can choose:

Direct Connection (default)

  1. Enter your database host/server name (or IP address), username, password and port number (default is 5432 for PostgreSQL),
  2. Select your database,
  3. Click the [Connect] button to load the database information.
Note The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection info in the advanced setting Connection info of production server before you upload it to your production server. For example, if you have a testing PostgreSQL Server installed on the same computer, you can use "localhost" as server name when you connect to it with DB AppMaker. The generated scripts will then try to connect to a PostgreSQL Server on the same computer as the production Web server, if this is not the case, the connection will fail.

URL Connection (for remote database)

Similar to above for MySQL.

 

Microsoft SQL Server

Notes

  1. If you have installed SQL Server 2012 Native Client (x86) on your computer, then Microsoft SQL Server database type will be available for selection. You can use this database type for connection to SQL Server 2000, 2005 or newer. You can download SQL Server 2012 Native Client from the Microsoft website. See System Requirements. The native client must also be installed on the web server. (ODBC or the old OLE DB provider for SQL Server are NOT supported.)
  2. DB AppMaker connects to the SQL Server by TCP/IP (NOT Windows authentication), make sure TCP/IP protocols is enabled for your SQL server, you can use SQL Server Configuration Manager to check and configure.
  3. If the SQL Server is a remote server (not on the same machine as DB AppMaker), make sure your SQL Server allows remote connection, you can use SQL Server Management Studio to check and configure.
  4. If you have firewall enabled on the server, make sure it allows inbound traffic on port 1433 for TCP/IP. If the SQL Server uses another port number, make sure you have set up the firewall rules accordingly. 
  • Select Microsoft SQL Server as database type,
  • Enter the name or IP of the SQL server,
  • Enter the User ID and Password,
  • Select the database you want or just enter the name of your database,
  • Click the - Connect button to load the database information.
Notes
  1. If Microsoft SQL Server 2005 or newer, make sure the server name includes the instance name, if any, e.g. localhost/SQLEXPRESS.
  2. The server name or IP should be valid on your production Web server also. Otherwise you'll need to modify the generated connection string in the advanced setting Connection info of production server before you upload it to your production server. For example, if you have a testing SQL Server installed on the same computer, you can use "(local)" as server name when you connect to it with DB AppMaker. The generated scripts will then try to connect to a SQL Server on the same computer as the production Web server, if this is not the case on the server, the connection will fail. It is common that SQL Server is installed on a different server in production environment.

-

 

Oracle

Note If you have installed Oracle client on your computer, this database type will be available for selection. You can download Oracle client from the Oracle website. Make sure the path of your Oracle client (e.g. oci.dll) is among the Path variable under Windows Environment Variables -> System variable.
  • Select Oracle as database type,
  • Enter the Oracle Service name,
  • Enter the User ID and Password,
  • Select the Schema you want or just enter the Schema name,
  • Click the - Connect button to load the database information.
Note The service name should be valid on your production Web server also. Otherwise you'll need to modify the generated connection info in the advanced setting Connection info of production server before you upload it to your production server. The service name must be set to the appropriate Net8 name which is known to the naming method in use. For example, for Local Naming, it is the alias in the tnsnames.ora file; for Oracle Names, it is the Net8 Service Name.

-

 

SQLite

  • Select SQLite as database type,
  • Select the SQLite database file by clicking the - button,
  • Specify the database path where the database file will reside under the your application root,
  • Click the - Connect button to load the database information.

-

 

 ©2018 e.World Technology Limited. All rights reserved.