Persistent data storage requirements

The SafeLinx Server has specific requirements that are necessary to successfully store, manage, and use persistent data.

The Mobile Connect SafeLinx Server stores the following types of data:
  • User profile information
  • Real-time session information for each active user, including information about all of the activities that are related to establishing, maintaining, and releasing connections to the SafeLinx Server.
  • Configuration information about the network resources that Mobile Connect interacts with
  • Accounting and billing information (optional)

To store configuration data about resources, the SafeLinx Server requires an ODBC-compliant relational database.

Note: If you are installing a proof-of-concept deployment, other storage options might be available. For more information, speak to your IBM® Sales representative.

The type of database that you can use depends on the operating system on which the Connection Manager is installed. On Linux™ or AIX®, you can use IBM® DB2® or Oracle Database. For Windows™ Server deployments, you can use DB2® or Microsoft™ SQL Server.

The relational database can be installed separately from the SafeLinx Server. To enable communication between SafeLinx Server and a remote database, install a database client or driver on the SafeLinx Server. SQL drivers are installed automatically when you install the Connection Manager on Windows™ Server.

Mobile Connect does not support the use of the Oracle Database Client. To store Connection Manager data in Oracle Database, you must install a licensed copy of Data Direct Connect driver on the SafeLinx Server server.

You are prompted to specify the method for storing persistent data during installation or during the initial configuration. After you implement a storage method, it can be difficult to change the method, and the process can risk data loss. If you must alter the method that you use to store data, create a backup beforehand to protect against data loss. For more information about backing up and restoring the Mobile Connect configuration, see the Backup & Imports technotes available in the Featured documents for IBM® Mobile Connect page of the IBM® support site.

To prepare for configuring persistent data storage, collect the information that is listed in the table that applies to the type of database you plan to use.

Table 1. DB2® relational database worksheet
Description Gather your information here
Database name - The default value of the session database is wgdata. The default value of the accounting and billing database is wgacct.
Database administrator ID
Database administrator password
Database instance
Table 2. SQL Server relational database worksheet
Description Gather your information here
Database name - The default value of the session database is wgdata. The default value of the accounting and billing database is wgacct.
Server and instance name - The name of the instance and SQL Server to which the SafeLinx Server connects.
Login name and password - SQL Server requires that each database user is authenticated with a login name and a login password. Also, specify the SQL Server authentication mode.
Authentication mode - Choose from:
  • Windows™ - SQL Server validates the login name and password by using information in the Windows™ operating system. This method is considered more secure than using SQL Server authentication. When you choose Windows™ authentication, the services that are installed to begin when the operating system starts also use these login credentials.
  • SQL Server - The SafeLinx Server uses the user ID and password that is defined only to SQL Server and SQL Server completes the authentication itself.