Excluding Groups From Being Processed As Part Of Dimension Files

This topic describes the steps to specify one or more groups that will not be synced and excluded in Dimension Loading files.

Excessive group processing in Dimension Loading creates additional overhead for Spark service that results in Spark service failure.

Perform the following steps to exclude groups from being processed:

Note: The following steps does not require you to stop all services from Service Monitor dashboard.

Login to the active Vocera Platform Web console.
Go to Status > Adapter Services and click Stop under column Actions for AnalyticsDataSync Service.
SSH to active Vocera Platform server.
Navigate to repository (repo) configuration:
```
cd /etc/yum.repos.d/
```

Open vocera.repo file and verify that it is pointing to the latest Vocera Platform 6.4 repository.

[Platform-6.4-Stable]
name=Platform-6.4-Stable
baseurl=https://<artifactory path>/platform-6.4-rpm-stable/
enabled=1
gpgcheck=0

Upgrade Analytics Data sync service RPM to vocera-analytics-data-sync-service-1.4.1.4-1.x86_64.rpm by using the command:
```
sudo yum upgrade vocera-analytics-data-sync-service-1.4.1.4-1.x86_64.rpm
```
The data sync service RPM used in this example is vocera-analytics-data-sync- service-1.4.1.4-1.
Type y and subsequently press Enter to upgrade.
Navigate to the AnalyticsDataSync directory by using the command:
```
cd /opt/EXTENSION/conf/AnalyticsDataSync
```
Create a new config file interface.properties.user by copying the current config file interface.properties by using the command:
```
sudo cp interface.properties interface.properties.user
```
Verify the new file and its ownership by using the command:
```
ls -ltr
```
Change the ownership of interface.properties.user file from root to extension by using the command:
```
sudo chown extension:extension interface.properties.user
```
Open the interface.properties.user file in editor by using the command:
```
sudo vi interface.properties.user
```
Add all groups to be excluded in the property "exclude.group.sync=" in the following format:
```
exclude.group.sync=site1Name:group1Name, site2Name:group2Name
```
Note: The groups to be excluded will be identified by Vocera Support. All excluded groups will not be synced in Vocera Analytics, therefore it does not capture any data.
To save the conf file:
- Click Escape button
- Type :wq!
Repeat the above steps on all nodes of the Vocera Platform server.
On the Active Platform Server, go to Status > Adapter Services on the left navigation menu to view the list of adapter services.
Locate AnalyticsDataSync and click Start to start the adapter.

Verification:

SSH to Active Platform Server.
Navigate to AnalyticsDataSync folder using the command:
```
cd /opt/EXTENSION/log/AnalyticsDataSync
```
Type ls to list the contents of the folder.
Open AnalyticsDataSyncInterface.log file.
- If no groups are configured to exclude, then the following line will be printed in the log file at the start of the analytics data sync service:
  For example, INFO : Excluded groups are not configured.
- If there are any groups that are configured to exclude, then the following line will be printed in the log file at the start of the analytics data sync service:
  For example, 2021-07-26 09:26:48,648 [pool-380-thread-1] INFO : Excluded group list is : Global:Permissions - Global Everyone All NO PHI Users, Global:Permissions - Global PHI Medical Students, Global:Permissions - Global PHI Providers, Global:Permissions - Global PHI Users, Ronald Reagan:Permissions - RR PHI Users, Santa Monica:Permissions - SM PHI Users
- If there are any subscription messages for updating the group that is excluded, then the following line will be printed in the log file:
  For example, 2021-07-26 11:42:59,955 [Thread-32 (ActiveMQ-client-global-threads)] INFO : Group [id=35499, name=Permissions - Global Everyone All NO PHI Users, facility=Global], is configured as excluded group, cannot be synced.