5.5 Configuring Listener scenario.

The Listener scenario is recommended for users who want to audit only AlwaysOn databases on the Primary node using LISTENER. If you want to audit read-only Secondary nodes, use the Nodes scenario.

Review the following steps to successfully configure your Listener:

1. Install cluster agent services on all Listener nodes using the SQL Compliance Manager Cluster Configuration Console
2. Install cluster agent services on all Listener nodes using
3. Add the Listener to SQL Compliance Manager 

1. Install cluster agent services on all Listener nodes using the SQL Compliance Manager Cluster Configuration Console

Use the following steps on each node involved in the AlwaysOn group before adding the listener to SQL Compliance Manager for auditing.

1. Run SQLCMInstall.exe in the root of the SQL Compliance Manager installation kit. 

2. Review the information you need to start the installation and click Next.
3. Follow the steps in the Setup wizard to install and configure SQL Compliance Manager in a clustered environment. 
4. Once the installation is complete, go to the SQL Compliance Manager install path. Unless you have specified a different path, the one by default is C:\Program Files\IDERA\SQLCompliance.

5. Run SQLcomplianceClusterSetup.EXE.

6. Once the setup wizard launches, click the Next button to proceed to the License Agreement. 
7. Read the license agreement, select the option to accept the terms of the license agreement, and click Next.
8. Select the destination path in which you want to install the IDERA Cluster Configuration Console. Define the permissions for the software and click Next. 

9. Click Install to complete the installation. 


10. The Cluster Configuration Console lauches automatically after installation.
    
11. Click Add Service to specify the listener. SQL Compliance Manager displays the Add SQLcompliance Agent Service - General window.
    
12. On the General dialog window, type the name of the clustered instance to be audited by SQL Compliance Manager and click Next. If you receive a message stating that the selected SQL Server instance is not clustered, click Yes. This is correct behavior when configuring a Listener scenario and confirms that the selected SQL Server instance is hosted on a Windows Failover Cluster.
    
13. On the Collection Server dialog window, specify the name of the server where SQL Compliance Manager is installed, and click Next. 
    
14. On the SQLcompliance Agent Service Account dialog window, specify the login credentials for the Agent service account, and click Next. This account must have administrator privileges. IDERA recommends that you use the same account as used for the Collection Server. 
    
15. On the SQLcompliance Agent Trace Directory dialog window, specify the path on which trace files will temporarily reside before being transferred to theSQLcompliance Collection Serviceand click Next. Note that the administrator account specified for the cluster agent service has read/write permissions for this trace directory folder. 
    

16. On the CLR Trigger Location dialog window, Specify the location where you want the SQLcompliance Agent to store the corresponding CLR trigger assemblies, and click Next.  Note that the administrator account specified for the cluster agent service has read/write permissions for this assembly folder. 

    Ensure the Agent Trace directory and the CLR Trigger location specified exist by creating the folder structure manually through Windows Explorer.

17. Review the configuration Summary and click 
    
    

    
    

18. The IDERA Cluster Configuration Console displays a confirmation message stating that you have successfully added the SQLcompliance Agent. 
    Click OK.