Accessing an Existing Runtime Database to Debug an AB Suite Application

Existing runtime database can be used for AB Suite debug session in the following ways:

To access locally deployed runtime database, perform the following:

  1. In the Administration Tool on the Developer workstation, create a Database Server Registration to LOCAL HOST.

  2. Right-click the Database Server Registration, and then select All Tasks > Attach Existing Database

  3. Select the Runtime Development Database, and then click OK.

  4. Setup the Debug Configuration to specify the Database Server Registration and Database Name under Test Database. Set Reorganise Database to NO.

  5. Perform a build for the Debug Configuration.

    It adds the Debugger System name under the Database Name in the Administration Tool.

To access remotely deployed runtime database, perform the following:

  1. In the Administration Tool on the Development Runtime Server, right-click the Dev AB Suite Runtime System, and select Change DB Password. Set the DB Password, and then select Apply this password change to the schema.

  2. In the Administration Tool on the Developer workstation, create a Database Server Registration to the AB Suite Development Runtime Server.

  3. Right-click the Database Server Registration, and then select All Tasks > Attach Existing Database.

  4. Select the Runtime Development Database, and then click OK.

  5. Setup the Debug Configuration to specify the Database Server Registration and Database Name under Test Database. Set Reorganise Database to NO.

  6. Perform a build for the Debug Configuration.

    It adds the Debugger System name under the Database Name in the Administration Tool.

  7. In the Administration Tool, right-click the Debugger System Name, and select Change DB Password. Set the DB Password to the same value set in Step 1. Deselect Apply this password change to the schema, and then click OK.

    You can run the Debugger session, and it connects to the shared Development Runtime Database.

To use backup or restored runtime database for debug session, perform the following:

  1. In case, the backup or restored runtime database using another name is too huge it is required to set Reorganise Database Flag to YES.

  2. Set the same Database Schema Name as the one initially used while deploying the runtime database for each involved user or configuration by using the debugger for restored runtime database.