Home
Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
Security
HCL SafeLinx includes a range of options for configuring the security of your network, applications, and data.
Authentication and Encryption Between Messaging Services and Applications that Use Messaging Services and Push APIs
To ensure secure transmissions with messaging clients, you can configure messaging services to require TLS connections with message processing servers or push initiators.

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.
  - Using IPSec
    You can configure the operating system to use IPSec to secure data transmitted between the SafeLinx Server and remote servers or among cluster nodes.
  - Security Options
    You can configure SafeLinx to use several different security mechanisms to protect network resources.
  - Authentication and Encryption
    A managed set of public key certificates that are issued by a certificate authority is required to enable TLS communications.
  - Authentication Between the Mobile Access Service and SafeLinx Clients
    SafeLinx Clients must authenticate with the mobile access service before they can establish an encrypted connection.
  - Encryption Between the Mobile Access Service and SafeLinx Clients
    You can modify the type of encryption that is used to transmit data between SafeLinx Clients and the mobile access service.
  - Third-Party Authentication to the SafeLinx Server
    You can configure authentication profiles to enable third-party authentication to the SafeLinx Server.
  - Authentication and Encryption Between Messaging Services and Applications that Use Messaging Services and Push APIs
    To ensure secure transmissions with messaging clients, you can configure messaging services to require TLS connections with message processing servers or push initiators.
  - Authentication and Encryption Among Cluster Managers
    To secure communications among cluster manager, you can require transport layer security (TLS) connections among the nodes in a SafeLinx Server cluster.
  - Admin Access
    Administrators who use the SafeLinx Administrator must authenticate by providing an administrator ID and password.
- 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.
- Installing and initial configuration
  Initial configuration and installation of HCL SafeLinx varies based on your operating system.
- 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, 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.

Authentication and Encryption Between Messaging Services and Applications that Use Messaging Services and Push APIs

To ensure secure transmissions with messaging clients, you can configure messaging services to require TLS connections with message processing servers or push initiators.

When a messaging client needs to make a secure request to an HTTP server, the messaging service decodes the request and opens a TLS connection on behalf of the client.

To enable applications that use the Messaging Services and Push APIs to negotiate TLS connections between messaging services and secure HTTP servers, you install a set of public key certificates. Certificates are installed in a key file database that must be separate from key databases that you use for other purposes. For more information about enabling TLS communications for messaging services, see Configuring TLS certificates for messaging services.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.