Adding a SafeLinx Server

After you complete the tasks in the Configure the SafeLinx Server Access Manager wizard, complete the initial configuration by defining a SafeLinx Server. Depending on your network requirements, you can then add an HTTP access service, a mobile access service, and users. You can run the Add a New SafeLinx Server wizard to initiate these tasks. If you choose not to use the wizard, you can also add and configure these resources from the SafeLinx Administrator.

You must configure the access manager before you add a SafeLinx Server.

Although the SafeLinx Server software is installed, it must be configured before it is ready to accept connections. When you use the wizard to add a SafeLinx Server resource, you have the opportunity to specify the component services that you want the SafeLinx Server to support. You can add and configure services now, or create them from the SafeLinx Administrator later. If you want, you can use wizards to create resources that have a basic configuration, and then fine-tune the configuration later. The Add a New SafeLinx Server wizard guides you through the process of adding network services to support different types of mobile connections.

  1. From the Add a New SafeLinx Server wizard, type a name for the SafeLinx Server in the SafeLinx Server identifier field. If you want to, you can also add a description to enable administrators to identify the SafeLinx Server.
    The identifier can be the host name of the server, or any other name that makes sense in your environment. In the Description field, you might include information about the release level of the SafeLinx Server, the operating system, or the services that it supports.
  2. In the Primary organizational unit field, specify where in the organizational hierarchy you want to store the SafeLinx Server and then click Finish.
    Information about every SafeLinx object, including the SafeLinx Server, is stored in the configuration database within a branch of an organizational hierarchy. For more information about OUs, see Organizational units.
    For example, you might create an OU specifically for SafeLinx Servers and store all of your SafeLinx Server resources within that OU.
    All of the information that is needed to create the SafeLinx Server is now available. The database connections that you configured are now tested and the tables within the WGDATA database are created. The SafeLinx Server object is also created and saved in the database configuration. It might take several minutes for these operations to complete.
  3. After the wizard closes, you are prompted to add an HTTP service. Click Yes to add the service.
    To enable HTTP applications, such as Traveler and SametimeĀ® to connect to the SafeLinx Server, most deployments add at least one HTTP access service. You can specify a basic configuration now and then edit the configuration from the SafeLinx Administrator later. For more information about configuring HTTP access services, see Adding HTTP access services
  4. After you complete the Add an HTTP Access Service wizard, you are prompted to add mobile access services. Click Yes if you want to support VPN connections from SafeLinx Clients. For more information about adding mobile access services, see Adding a mobile access service.
    If you choose to add a mobile access service, you are also prompted to create a mobile network interface (MNI). The Add a New Mobile Network Interface wizard guides you through the creation of the MNI.
  5. Next, you are prompted to add a SafeLinx Server user account. Click No if you store user account information in a third-party directory.
    SafeLinx Server user accounts enable SafeLinx Client access to the SafeLinx Server for users in environments that do employ a separate directory server. Most deployments do not use SafeLinx Server user accounts. For more information about user accounts, see User accounts.
  6. When prompted, click Yes to start the SafeLinx Server.
    A message displays to notify you that the start command was issued.

The initial configuration is now complete. The initial configuration does not result in a production ready service. Before you can use SafeLinx services, further configuration is necessary.

Although you can configure your network resources in any order, a logical next step is to configure a directory service to enable user lookup and authentication. For more information, see Configuring a directory server

For more information about adding and configuring other resources in your environment, see Configuring resources.