Completing the initial DB2 database configuration on Windows

On Windows, after the Installation wizard completes, the First steps portal opens to guide you through the initial configuration. The First steps portal includes a link to open the Database Configuration Wizard, which guides you through the process of configuring the Connection Manager to use the relational database where you want the Connection Manager to store persistent data.

Before you begin

The Connection Manager can store data on a DB2® database that is local or it can connect to a remote database. Before you start database configuration process, the database that you want to use must be installed and available. Make sure that you install the DB2 language support for the installed language version of the Connection Manager. Use the DB2 Instance wizard to ensure that the DB2 database instance is installed and configured correctly.

In a local installation, the IBM® Data Server client and DB2 server are installed on the same workstation as the Connection Manager. In a remote installation, you install the IBM Data Server client on the same workstation as the Connection Manager, and configure it to connect to a DB2 server a network-attached computer.

For more information about supported database clients and servers, see System requirements.

Note: If you use a remote database server and that server grants access to designated database administrators only, you might not be able to use the following instructions to configure the database. Instead, you can run database definition language (DDL) scripts to complete the configuration. For more information, see Configuring databases for IBM Mobile Connect with DDL
To use DB2, be prepared to provide the following information:
  • Database and instance names
  • Database server location - IP address or host name and port number
  • Database administrator user ID and password
  • Before you run the Database configuration wizard, log in to Windows as a user who has permission to create and catalog DB2 databases. To ensure that the user account has sufficient privileges, add the user to the DB2 Administrators group (DB2ADMNS) that is created when DB2 is installed.

About this task

To enable the Connection Manager to use IBM DB2 to store data, use the Database configuration wizard to complete the following procedure:

Procedure

  1. If the First steps wizard does not open automatically, click Start > Programs > IBM Mobile Connect > First Steps.
  2. From the Welcome page, open the Database Configuration page, and then click Database Configuration Wizard.
  3. Choose IBM DB2 as the database type to use for configuration and accounting data.
  4. Complete the following fields:
    1. In the Enter the DB2 instance name field, type the name of the DB2 instance that you want to use. No default name is specified. The DB2 instance name has a maximum length of 8 bytes.

      If you use a remote DB2 server, be sure that the DB2administrator ID that you log in with has access to manage the instance that you specify.

      In a local installation, the instance name, for example, wgdb, becomes an operating system user ID. Make sure that other services, including operating system services, such as FTP, Telnet, and SSH, cannot use this account.

      For example, wgdb.

      Note: After you specify the name and location for the instance ID, you must delete the Connection Manager configuration from Gatekeeper to change it.
    2. In the DB2 Administrator ID and Password fields, type the credentials of a DB2 Administrator account that you want the Connection Manager to use when it accesses the database. For example, provide the credentials for the default db2admin account.
    3. Type the name of the configuration database in the Name field, and then click Local or Remote to specify where the database is hosted. If the DB2 server is hosted on a computer other than the Connection Manager, complete the Host name and the Port fields. To determine the port number, check the services file on the DB2 server.
      Note: If you are updating an existing version of the Connection Manager, and the databases already exist, you might be prompted to delete the old databases. If the database contains current configuration data, do not delete it unless you have a verified backup of the existing configuration. For more information about backing up the Connection Manager configuration, see technote #1295525, Backing up the Connection Manager Configuration.
    4. Type the name of the accounting database in the Name field, and then click Local or Remote to specify where the database is hosted.
    Note: If you are updating an existing version of the Connection Manager, and the configuration database already exists, you might be prompted to delete the original version. If you want to preserve configuration information from the original database, do not delete it until you have a verified backup. For more information about backing up the Connection Manager configuration, see technote #1295525, Backing up the Connection Manager Configuration.

What to do next

You can now return to the First Steps portal to open the Gatekeeper and configure the access manager.