Home
Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
Database schema information
HCL SafeLinx uses a DB2, Oracle, MySQL, or SQL database to store tables of information about current and past activity of SafeLinx Server sessions. The following tables are created and accessed by using the qualifier name wg for DB2 installations.
Reclaiming space after records are deleted
Under normal conditions, when rows are deleted in a DB2 table, the disk space taken up by those rows is not released. Rather, the disk space is reused when additional rows are inserted. Over time, this means that a database and its tables can grow to be large and use more disk space.

Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
- Overview
  HCL SafeLinx uses standards-based protocols to enable secure access from mobile computing devices outside the firewall to business applications and data on your organization's internal network.
- Security
  HCL SafeLinx includes a range of options for configuring the security of your network, applications, and data.
- Installation planning
  Before you install HCL SafeLinx, verify that you meet the hardware and software requirements, and that the network connections that you want to use are available.
- Roadmaps: Installing and setting up SafeLinx
  The following "roadmap" topics guide you through installing and initially configuring SafeLinx. Refer to the topic that corresponds to your relational database and server operating system.
- Installing and initial configuration
  Initial configuration and installation of HCL SafeLinx varies based on your operating system and relational database.
- Adding a secure login profile
  By default, the SafeLinx Administrator communicates with the access manager over an unencrypted connection. If you want the connection between the SafeLinx Administrator and the access manager to use transport layer security (TLS) protocols, add a secure login profile to the SafeLinx Administrator.
- Adding and configuring resources
  After you complete the installation and initial configuration, continue to prepare the deployment by configuring other network resources.
- Administering
  The SafeLinx Administrator administration client is the primary tool for viewing, adding, configuring, and managing HCL SafeLinx resources. Along with the SafeLinx Administrator, you can use the HCL SafeLinx Monitor to view information about packet flow through the SafeLinx Server. You can also use a set of command line tools to perform common SafeLinx Server tasks.
- Programming reference
  There are several programming considerations of which you might want to take advantage.
- Database schema information
  HCL SafeLinx uses a DB2, Oracle, MySQL, or SQL database to store tables of information about current and past activity of SafeLinx Server sessions. The following tables are created and accessed by using the qualifier name wg for DB2 installations.
  - Accounting and billing database schema
    The accounting and billing database schema is provided so that you can use a structured query language (SQL) reporting tool to audit and sort data. This tool is also used to generate queries and produce usage reports. The default database name is wgacct.
  - Session database schema
    The session database schema is provided so that you can use a structured query language (SQL) reporting tool to audit and sort data. The schema is also used to generate queries and produce usage reports. The default DB2 database name is wg.
  - Reclaiming space after records are deleted
    Under normal conditions, when rows are deleted in a DB2 table, the disk space taken up by those rows is not released. Rather, the disk space is reused when additional rows are inserted. Over time, this means that a database and its tables can grow to be large and use more disk space.
- Step by step: Nomad configuration
  Here are step-by-step instructions that serve as an example of how to install and configure HCL SafeLinx for Nomad on MySQL on Linux.

Reclaiming space after records are deleted

Under normal conditions, when rows are deleted in a DB2 table, the disk space taken up by those rows is not released. Rather, the disk space is reused when additional rows are inserted. Over time, this means that a database and its tables can grow to be large and use more disk space.

About this task

If it is necessary to recover the space used by deleted accounting records, you can choose one of two options. Both options require first stopping the SafeLinx Server and any applications that access the accounting database (for example, wg_acct).

Procedure

After all database applications that access the accounting database are stopped, connect to the database with the appropriate database instance and either:

Run db2 reorg table wg.tablename, where tablename is one of acctinfo, acctdiscinfo, acctsmsinfo.
Run db2 drop table wg.tablename, where tablename is one of acctinfo, acctdiscinfo, acctsmsinfo. This option can be used only if the table is already empty, that is that all rows are deleted.