Managing a Relational Database Server

Edit online

About this task

By adding a relational database server, you can correctly configure the connection between IBM AD Build and IBM AD Analyze. This task is step 5 of configuring an IBM AD installation through IBM AD Configuration Wizard. You can add, update, or delete a relational database server as follows.

Procedure

  1. Access Start Menu > IBM Application Discovery and Delivery Intelligence > Launch IBM Application Discovery Configuration Service Admin, and go to Configure > Environments > "Your environment" > Servers and security > Relational database server. The Relational Database Server settings page is displayed.
  2. To add a relational database server, click the Add button. The Add Relational Database Server page is displayed.
  3. Enter the following information:
    Server Name (alias)
    Enter an appropriate name (alias) for the relational database server.
    Note: For a Db2 for LUW (Linux®, UNIX, and Windows) database server, the server name must follow the general Db2 object naming rules. This alias will be used to catalog Db2 for LUW server node into local node directory in case that you decide automatically create the databases within IBM ADDI (Project database, Cross Service database, Annotation database).
    Select Database Server Type
    Select the appropriate relational database type.
    Host
    Enter the host name or the IP of the computer where the relational database server is installed. IBM AD Build Configuration uses the server to publish projects.
    Port
    Enter the relational database server port. The default ports are:
    For Microsoft SQL Server
    The default port for Microsoft SQL Server is 1433.
    For Db2 for LUW (Linux, UNIX, and Windows)
    If the Db2 11.5.5 and previous versions are used, the default port for Db2 for LUW is 50000.
    If the Db2 11.5.6 and later versions are used, the default port for Db2 for LUW is 25000.
    Security
    If the security is enabled, you can select the security communication from the drop-down list.
    Attention:
    • The Trust server certificate option establishes a secure connection between clients and servers, especially for database servers. If this option is checked, the JDBC connection will be established without needing a certificate because the client will trust the server certificate. If the option is cleared, you need to provide the server certificate for the database to enable the secure communication with the database server.
    • For Microsoft SQL Server database server, two options are available: TLS 1.2 and TLS 1.3. If TLS 1.2 is selected for a Microsoft SQL Server instance, the check box of Trust Server Certificate is checked by default.
    • For Db2 for LUW (Linux, UNIX, and Windows) database server, three options are available: TLS 1.2, TLS 1.3, and HTTP (not secure).
    • If a warning messages indicated that the TLS communication with Database Server is not enabled, you need to enable HTTPS communication from the Security tab first. For more information, see Configuring Security Settings.
    Restriction: There is a limitation in supporting TLS 1.3. When Java™ Semeru 8 was used, Db2 for LUW cannot be connected successfully.
    Database Name (optional)
    If IBM Db2 is selected as the database server type, the Database Name (optional) field is displayed. You can enter the name of any database on the selected server to validate the connection. This field is optional.
    Instance (optional)
    If Microsoft SQL Server is selected as the database server type and multiple instances are installed on the same machine, enter the required relational database server instance name (if exists).
    Username and Password
    1. For Microsoft SQL Server instance, enter the username and password for the IBM AD SQL Identity as previously defined in Microsoft SQL Server Configurations.
    2. For Db2 for LUW (Linux, UNIX, and Windows) instance, enter the username and password.
    Note: If you need to update the name of the AD SQL Identity user for your Microsoft SQL Server environment, complete the following steps:
    1. Create a new SQL Identity user in SQL Server Management Studio, and grant the same permissions to the new user as the existing SQL Identity user. For the detailed steps, follow the description in Microsoft SQL Server Configurations.
    2. After you define the new AD SQL Identity user in SQL Server Management studio, return to the IBM Application Discovery Configuration Service Admin graphical user interface in the web browser. Then, click Relational database server tab, and click the pencil icon under the Actions tab to edit an existing relational DB server definition.
    3. After the Edit relational database server page is displayed, scroll to the Username and Password fields, and update the name of the SQL Identity user and password if appropriate in the Relational database server definition in AD's Configuration Server as described at this step.
      Update username and password
  4. By clicking Test Connection, you can test the connection to your database. If the test connection succeeds, click Save.
  5. To edit a relational database server, go to the Actions column and select the Edit button.
  6. To delete a relational database server, go to the Actions column and select the Delete button.