---
title: "How to Ensure Auditing is Enabled in Your XA Environment"
slug: "how-to-ensure-auditing-is-enabled-in-you-xa-environment"
updated: 2023-07-27T19:18:28Z
published: 2023-07-27T19:18:28Z
canonical: "healthcare.rapididentity.com/how-to-ensure-auditing-is-enabled-in-you-xa-environment"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Ensure Auditing is Enabled in Your XA Environment

## 

### This article explains how to:

1. Verify whether Auditing is enabled and running properly on an XA server
2. Verify whether Auditing is enabled and running properly on an XA Client

#### Applies To:

- All versions of XA Server 4.12.5 and higher
- All versions of XA Client 4.12.5  and higher

### Steps to verify Auditing is enabled on an XA Server

On a server with XA 4.12.5 or higher installed (refer to the online [XA Product Documentation](https://healthcast-product-guide.identityautomation.com/en/first-time-installation--sso-.html) for instructions on how to install XA Server):

1. Verify the Audit Server service is enabled and running
  1. Run Services.msc and verify that
    1. The HCI auditSERVER Service is running and that the **Startup Type** is set to **Automatic**.
    2. The HCI auditSERVER Service  is running under a domain account![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656716535254.png)
2. Verify the Database connection is correct
  1. Open the **HCI Server Configuration Tool** (C:\Program Files (x86)\HealthCast\eXactACCESS\hciserverconfigure.exe) as a user with local administrator privileges
  2. Select the **Database** button![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656717046559.png)
  3. Select the **auditServer** tab
  4. Verify that the Server(s) and [**Data Link Properties** are correct](https://healthcast-product-guide.identityautomation.com/en/auditserver-282653.html) and that you can successfully connect to the database (you must be running as a user that has access to the Audit database in order to successfully connect). If no database is configured, refer to the [XA Server Installation documentation](https://healthcast-product-guide.identityautomation.com/en/server-configuration-tool.html).![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656717295342.png)
3. Verify that Audit Data is is being written to the database
  1. Login to XA from a client system that has been configured to use Audit Server.
  2. Connect to the Audit Server database using a tool such as [SQL Server Management Studio](https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16)
  3. Open a Query Windows and query the latest records written to Audit Server using the following SQL code example. Replace the 'DOMAIN/MACHINENAME' with the domain name and machine name of the XA client system from step "a".
  4. Verify whether new audit data from the XA Client system was written to the the Audit table. If it was not, there is a problem either with the Audit Server configuration on the XA Server, or with the Audit settings on the XA Client system.
  5. PL/SQL  

```plsql
SELECT TOP 100 time_start
      ,time_complete
      ,application_name
      ,application_event
      ,user_uname
      ,user_mach_name
      ,attribs_name
      ,attribs_value
      ,timewritten
  FROM staging WHERE user_mach_name = 'DOMAIN/MACHINENAME'
  ORDER BY time_start desc
```

### Steps to verify Auditing is enabled on an XA Client

1. On an XA Client system, open the **eXactACCESS Client Configuration utility** as a user with local administrator privileges.![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656718933046.png)
2. Select the **AuditServer** tab
3. Verify whether there are auditServer Servers listed. If there are not AuditServer servers listed, you will need to add them. To add a server
  1. Click the + button
  2. Enter the name of the Audit server and click **OK**![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656719226970.png)
4. Test connectivity to the Audit Server
  1. Select an Audit Server from the list of auditSERVER servers
  2. Click the **Test Connection**button
    1. If the connection fails, no audit data will be sent to the Audit Server.![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/image-1656719330048.png)
5. Login to XA on the client system. This will trigger an Audit event.
6. Check the AuditServer database to verify that audit data is being sent properly to the Audit Server (see previous section).

###