Empirum Service Bus Publishing Options

+ More

Table of Contents

Control What Is Published (Empirum Options)

Control What Is Published (Empirum Options)

An Empirum Options (EmpOption) for published objects can contain the following values:

EmpValue Description
0 Do not publish objects of the related type.
1 Execute initial publishing of all objects of the related type.
2 Publish single objects of the related type if they change.

The Options table in the Empirum database stores feature toggles — referred to as Empirum Options — that control the publishing behavior for various Empirum objects.

After the initial installation and once the first synchronization cycles have completed (i.e., all objects of a given type have been published), the value for each toggle is typically set to 2.

The following values are supported:

  • 0 — Disables publishing entirely for that object type
  • 1 — Triggers a full re-publish of all objects of that type
  • 2 — Normal operating state; publishing runs incrementally as needed

An initial sync — which publishes all objects of a specific type at once — is supported for most object types.

The available options depend on the installed Empirum version.

 
EmpOption Initial Sync Support Related Empirum Object
UemDeviceSyncActivated Yes Client computer
UemInventorySoftwareSyncActivated
(set to '0' by default as not all license management processes are supported yet - do not enable this value for now as it will lead to duplicate fingerprints)		 Yes: only Initial Sync Installed applications (Inventory) found on a managed client
UemBootImageSyncActivated Yes Boot configuration for OS deployment
UemPmStatusSyncActivated No Patch Management status
UemPatchManagementGroupSyncActivated Yes Patch Management group
UemSoftwarePackageSyncActivated Yes

Any Empirum (software) package: UEM Agent Template, Software Application, OS Install Image, OS Language Pack.

Trigger a full sync to publish all listed objects.

Re-import the OS Install Images from the disk using EMC will find all OS (Install) Images (metadata) and publishes then on the Service Bus.
UemStatusSyncActivated No

(But could be done indirectly using 'UemSoftwareInstallationStatusLastRun' option described below)		 UEM Agent status / Last software installation status
UEMBootImageSyncActivated Yes Boot Configurations
UEMAgentTemplateSyncActivated Yes Agent Template Configurations
UEMHardwareDriverSyncActivated Yes Hardware Drivers for WinPE based OS deployments
UEMVariableConfigurationSyncActivated Yes Variable Configurations
UEMDhcpEntriesSyncActivated Yes PXE not qualified computers

Additionally, there are Empirum options that have different values but are also used to control publishing.

EmpOption EmpValue Description
UemSoftwareInstallationStatusLastRun Last processed ID from table ArchiveDistJobs Software package installation status Or UEM Agent status. This Empirum Option is directly related to the 'UemStatusSyncActivated' option described upon.

All software depot logs are stored in that table and the ID of the last processed record is stored in UemSoftwareInstallationStatusLastRun. 

It is possible to RE-publish all the history by setting the value to '0'.
Be aware that WinPE-based,there could be tens of thousands of records in that table.

Changes can only be made directly through the DB.

Additional settings:

EmpOption EmpValue sentDescription
UemServiceBusDisplayName Name to be shown in node information on DWP Sets the name string that is sent as a request to the heartbeat message from the DWP.

Related Articles