Completing the initial SQL Server database configuration on Windows

On Windows, after the Installation wizard completes, the First steps portal opens to guide you through the initial configuration. From the First steps portal you can start the Database Configuration Wizard. The Database Configuration Wizard guides you through the process of configuring the SafeLinx Server to use the relational database where you want the SafeLinx Server to store persistent data.

Before you begin

SafeLinx Server installations on Windows can store data on Microsoft SQL Server. The SafeLinx Server can use a database that is local or can connect to a remote database. Alternatively, on Windows 64-bit, you can use the local storage option as described at the end of this topic.

Note: If you use a remote database server to which only designated database administrators have access, you might not be able to complete the configuration procedure. If that is the case, you can provide the database administrator with a set of database definition language (DDL) scripts to complete the configuration. For more information, see Configuring databases for HCL SafeLinx with DDL

Before you run the Database Configuration Wizard, the database that you want to use must be installed and available.

To configure SQL Server, be prepared to provide following information:

  • Server and instance names
  • Authentication type
  • Names of the databases to use for accounting and billing data, and for configuration data.

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

About this task

To enable the SafeLinx Server to use Microsoft SQL Server to store data, use the Database Configuration Wizard to complete the following procedure:


  1. If the First steps wizard does not open automatically, click Start > Programs > HCL SafeLinx > First Steps.
  2. From the Welcome page, open the Database Configuration page, and then click Database Configuration Wizard.
  3. Choose MS SQL Server as the database type to use for configuration and accounting data.
  4. Complete the following fields:
    1. In the Server name field, type or choose a server name and instance in the following format:

      The server that you specify can be on a separate computer or on the same computer that hosts the SafeLinx Server.

      Note: By default, named instances are configured to use dynamic ports, in which the listening port is specified after the SQL Server service starts. However, if there is a firewall between the SafeLinx Server and the database server, you must specify a static port. You cannot use a dynamic port because you must decide in advance which port to open in the firewall.

      For example, to use the default instance on a remote or local server, you would specify the host name, such as MYSERVER.

      To use a named instance on a remote server that is configured to listen on a specific port, you might type MYSERVER\SQLEXPRESS,1453 .
    2. In the field Failover partner FQDN (optional), specify the fully qualified domain name of the server that is configured as a database mirror for the server in Step 4a.
      If SafeLinx cannot access the primary database, it attempts to connect to the mirror database on the partner server. Leave this field blank if you do not have a failover partner server configured.
    3. In the Authentication field, choose of the following options:
      • Windows Authentication
      • SQL Server Authentication

      The option that you choose must match the Authentication mode setting that is configured for the SQL Server installation. For more information about how to choose the type of authentication, see your SQL Server documentation.

    4. In the User Name and Password fields, specify the credentials for an SQL Server Admin ID account. The values must match the name and password of the account that you used to install SQL Server. If the SQL Server uses Windows authentication, then the SafeLinx Server runs under the Windows user ID that you specify.
    5. In the Configuration database and Accounting database fields, accept or change the default names (wgdata and wgacct).
      Note: If you are updating an existing version of the SafeLinx Server, and there is an existing configuration database, you might be prompted to delete the original version. If you want to preserve information from the original database, do not delete it until you create and verify a backup. For more information about backing up the SafeLinx Server configuration, see technote, Backing up the SafeLinx Server Configuration.

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

      Local storage option