Completing the initial DB2 database configuration on AIX or Linux
On AIX or Linux, after the installation completes, open the SafeLinx Administrator to complete the initial configuration. A wizard guides you through the process of configuring the SafeLinx Server to use the DB2 database where you want the SafeLinx Server to store persistent data.
The SafeLinx Server 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 SafeLinx Server. 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 SafeLinx Server. In a remote installation, you install the IBM Data Server client on the same workstation as the SafeLinx Server, 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.
- Database and instance names
- Database server location - IP address or host name and port number
- Database administrator user ID and password
Before you begin the configuration procedure, log in as a user who has permission to create and catalog DB2 databases. To ensure that a user has sufficient privileges, you can add the user to the DB2 administrative group that is created when DB2 is installed.
You must also assign a database name and an administrative ID and password. The database name must be 8 characters or less. The default name of the session information database is wgdata. The default name of the accounting and billing information database is wgacct. You can assign a unique administrative ID or you can use the instance ID, wgdb. In a local installation, the SafeLinx Server can connect to DB2 using the instance ID, wgdb, which has a default password of sl1nx8hcl. In a remote installation, choose the administrative ID and password from the remote server that you want to use.
Start the SafeLinx Administrator.
If you are starting the SafeLinx Administrator for the first time on this computer, a Login Profile Details window might open.
Before the SafeLinx Administrator can connect to the access manager, you might have to add a login profile. If no login profile exists, add a standard login profile now. Later, you can create a secure login profile for this SafeLinx Server. You can also create standard or secure login profiles to enable SafeLinx Administrator to manage other SafeLinx Servers.
For information on how to set up a login profile, see Setting up an access manager login profile.
- After you add a login profile, select the profile, then click OK.
In the SafeLinx Administrator-Login window, type
admin in the Administrator ID field, type
sl4!admin, the default password, in the Password field,
and then click Log In.
After you configure the access manager, you can create other administrator IDs.The Configure the SafeLinx Server Access Manager wizard opens, along with the license agreement and the SafeLinx Administrator Help.
- Read and accept the license agreement and then review the information in the SafeLinx Administrator Help topic Initial configuration wizard.
- From the Configure the SafeLinx Server Access Manager wizard, click An ODBC-compliant relational database.
In the field SafeLinx Server DB2 client instance ID, accept the
default instance name (wgdb) or specify a different name. The instance ID that
you specify is used for the session database and for the accounting and billing database, if you
The DB2 instance name has a maximum length of 8 bytes. The default SafeLinx Server DB2 client instance name (wgdb) is the same as the default operating system user ID.
In a local installation, the instance name, 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.
If you use a remote DB2 server, be sure that the DB2 administrator ID that you log in with has access to manage the instance that you specify.
If the attempt to create the wgdb instance fails, you might receive the following error message: ERROR:DBI1281E The database manager configuration file could not be initialized. If this error occurs, try to create a DB2 instance manually. If instance creation fails again, and you receive the following message: <db2 install path>/bin/db2imdbm: not found you might have to change permissions on the directory <db2 install path>.
For example, if the following permissions are set on /opt/HCL:
Use the following command to change the permissions on the directory:
drwxr----- 5 root system 512 Nov 14 13:40 IBM
chmod 755 /opt/HCL
Permissions for other folders in this path might also need to be changed. The error might also indicate problems unrelated to permissions. For more information about error messages, see the Error messages reference in the DB2 documentation.
- In the field Home directory for DB2 client instance ID, accept the default directory (/home/wgdb), or specify a different directory.
- In the Database name field, accept the default name (wgdata) or specify a different name.
In the Database administrative ID field, accept the default name
(wgdata) or specify a different name, and then type and confirm the account
Specify the ID for the DB2 Administrator account that you want the SafeLinx Server to use to create and access the database.For example, provide the credentials for the default db2admin account.
Specify the location of the DB2 database.
- If the database server is on the same computer as the SafeLinx Server, in the field Location of DB2 database, type the path to the database instance, for example, /home/wgdb
- If the database server is on a different computer, type the host name or IP address of the server and the port number that the DB2 service listens on.
- For an upgrade or re installation of the SafeLinx Server, select Erase existing database (including all tables and data) and create a new database if you want to remove any old SafeLinx Server databases.