Contents x
    XA Server Overview
    • 24 Mar 2023
    • 1 Minute to read
    • Contributors
    • Dark
      Light
    • PDF
    Contents

    XA Server Overview

    • Updated on 24 Mar 2023
    • 1 Minute to read
    • Contributors
    • Dark
      Light
    • PDF
    Article summary

    XA Server is the server-side component of the ExactAccess ("XA") solution. It is deployed with the XA Client installation software to provide information and communication between workstations and servers. The server is necessary for the successful implementation of the XA Solution.

    The following services are installed as part of XA Server.

    • ExactAccess Server Service - responsible for providing sign-on services to client workstations.
    • ProxCard Server Service (optional) - responsible for providing proximity badge password-save functionality to client workstations.
    • Remote Authentication Service (optional) - responsible for allowing remote authentication for non-domain-joined workstations.
    • auditSERVER Service (optional) - responsible for providing audit collection services for client workstations.
    • HCI Deploy Service (optional) - responsible for providing update services for client workstations.
    NOTE

    Each of the optional services listed above can be disabled or set to manual start. If these services are not desired (or are not necessary) in your environment, they may enabled or disabled individually as your needs change.

    TIP

    For very large organizations, each of these services can be installed and configured on different clusters of servers with different load balancing rules. This allows administrators to group clusters based on provided services so that one service load does not impact the performance of another service load as can happen if all services are running on the server.

    • A cluster of SSO servers can have all other XA services be disabled so that only the XA/SSO service is running
    • A cluster of Prox servers can have all other XA services be disabled so that only the Prox service is running
    • A cluster of Audit servers can have all other XA services be disabled so that only the Audit service is running
    • A cluster of Deploy servers can have all other XA services be disabled so that only the Deploy service is running
    • A cluster of Authentication servers can have all other XA services be disabled so that only the Authentication service is running

    Each of these clusters can have as many servers behind the load balanced IP/Port as necessary to handle the load of the respective service requests from end points.

    Was this article helpful?
    What's Next