The Empirum Service Bus Service exchanges meta-data with the Empirum depots via the Service Bus and also monitors changes to computers, software packages and installation status in the database and sends this information to Enterprise Service Management via a Service Bus system (Microsoft Azure Service Bus or RabbitMQ).

• Subscription / Queue: Messages are received by this subscription.
• Service Bus-Type: The Cloud-based Microsoft Azure Service Bus or on-premises RabbitMQ systems are currently supported.
  RabbitMQ is an open source message broker.
• Topic / Exchange: Messages are published to this topic and sent to one or more associated subscriptions.
• Connection String for Service Bus Service: String to establish a connection with the previously selected service bus type. To establish a secure connection via RabbitMQ, amqps:// must be used instead of amqp://.
  Special characters in the password must be URL-encoded (also called percentage encoding).
  To get the Microsoft Azure connection string for the topics, open your browser and: 
  • Go to Microsoft Azure https://portal.azure.com/?l=en.en-us#home.
  • Select your Service Bus Namespace.
  • Create a new topic, which will be used.
  • Select the topic.
  • Click on "Shared Access Policies" and select your policy.
  • Add a new SAS policy.
    Add a new SAS policy with the claims Manage / Listen / Send.
    

    If you have used the included PowerShell script, this was already added.

  • Click on the created policy and on the right Keys and Connection Strings will be shown.
  • Copy a Connection String (primary or secondary connection string).
    After the automated installation via RabbitMQ_InstallPackage.exe, the RabbitMQ server is also configured with standard values for the message exchange - except for the username and his password (these are requested during the script execution).
  • The standard connection string based on this installation and configuration looks like this: amqp://<Username>:<Password>@<FQDN of your RabbitMQ-Server>/matrix42
• Connection String for Depot Sync: Repeat the steps described above, but configure Listen / Send claims only for this SAS policy.
  This connection string is used by the Empirum depot(s) to connect to the service bus.
• Display Name: Optionally, you can specify a unique name for the ServiceBus service here.
  If this value is set, it is communicated via the ESB Heartbeat response. If this field remains empty, the Empirum default name is transmitted (%ServerName%\%StandortName%).
• Use Proxy Server: Configure the ServiceBus service to use a proxy server.
  • Address: Enter the address of the proxy server.
  • Port: Enter the port number of the proxy server.
• Enterprise Service Management Integration: Configures the Service Bus Service (ticked) to synchronize data between Empirum and Enterprise Service Management via the Service Bus. If the option is activated, a restart of the service is required.

After entering all parameters, click Apply, then click Install.

Your information is written to the database via the Apply button.