Exercise - Configure applications to send or receive messages through an Event Hub
You're now ready to configure your publisher and consumer applications for your Event Hub.
In this unit, you'll configure these applications to send or receive messages through your Event Hub. These applications are stored in a GitHub repository.
You'll configure two separate applications; one acts as the message sender (SimpleSend), the other as the message receiver (EventProcessorSample). These are Java applications, which enable you to do everything within the browser. However, the same configuration is needed for any platform, such as .NET.
Create a general-purpose, standard storage account
The Java receiver application, that you'll configure in this unit, stores messages in Azure Blob Storage. Blob Storage requires a storage account.
In the Cloud Shell, create a storage account (general-purpose V2) using the
storage account createcommand. Remember we set a default resource group and location, so even though those parameters are normally required, we can leave them off.
Parameter Description --name (required) A name for your storage account. --resource-group (required) The resource group owner. We'll use the pre-created sandbox resource group. --location (optional) An optional location if you want the storage account in a specific place vs. the resource group location.
Set the storage account name into a variable. It must be between 3 and 24 characters in length and use numbers and lower-case letters only. It also must be unique within Azure.
Then use this command to create the storage account.
az storage account create --name $STORAGE_NAME --sku Standard_RAGRS --encryption-service blob
If the storage account creation fails, change your environment variable and try again.
List all the access keys associated with your storage account using the
account keys listcommand. It takes your account name and the resource group (which is defaulted).
az storage account keys list --account-name $STORAGE_NAME
Access keys associated with your storage account are listed. Copy and save the value of key for future use. You'll need this key to access your storage account.
View the connections string for your storage account using the following command:
az storage account show-connection-string -n $STORAGE_NAME
This command returns the connection details for the storage account. Copy and save the value of connectionString. It should look something like:
Create a container called messages in your storage account using the following command. Use the connectionString you copied in the previous step:
az storage container create -n messages --connection-string "<connection string here>"
Clone the Event Hubs GitHub repository
Use the following steps to clone the Event Hubs GitHub repository with
git. You can execute this right in the Cloud Shell.
The source files for the applications that you'll build in this unit are located in a GitHub repository. Use the following commands to make sure that you are in your home directory in Cloud Shell, and then to clone this repository:
cd ~ git clone https://github.com/Azure/azure-event-hubs.git
The repository is cloned to your home folder.
We're going to use the built-in Cloud Shell Code editor. This is based on the Monaco editor and is similar to Visual Studio Code, but completely online.
We'll use the editor to modify the SimpleSend application and add your Event Hubs namespace, Event Hub name, shared access policy name, and primary key. The main commands are displayed at the bottom of the editor window.
You'll need to write out your edits using Ctrl+O, and then ENTER to confirm the output file name, and exit the editor using Ctrl+X. Alternatively, the editor has a "..." menu in the top/right corner for all the editing commands.
Change to the SimpleSend folder.
Open the code editor in the current folder. This will show a list of files on the left and an editor space on the right.
Open the SimpleSend.java file by selecting it from the file list.
In the editor, locate and replace the following strings:
"Your Event Hubs namespace name"with the name of your Event Hub namespace.
"Your Event Hub"with the name of your Event Hub.
"Your policy name"with RootManageSharedAccessKey.
"Your primary SAS key"with the value of the primaryKey key for your Event Hub namespace that you saved earlier.
Unlike the terminal window, the editor can use typical copy/paste keyboard accelerator keys for your OS.
If you've forgotten some of them, you can switch down to the terminal window below the editor and use the
echocommand to list out one of the environment variables. For example:
echo $NS_NAME echo $HUB_NAME echo $STORAGE_NAME
When you create an Event Hubs namespace, a 256-bit SAS key called RootManageSharedAccessKey is created that has an associated pair of primary and secondary keys that grant send, listen, and manage rights to the namespace. In the previous unit, you displayed the key using an Azure CLI command, and you can also find this key by opening the Shared access policies page for your Event Hubs namespace in the Azure portal.
Save SimpleSend.java either through the "..." menu, or the accelerator key (Ctrl+S on Windows and Linux, Cmd+S on macOS).
Close the editor through the "..." menu, or the accelerator key CTRL+Q.
Use Maven to build SimpleSend.java
You'll now build the Java application using mvn commands.
Change back to the main SimpleSend folder.
Build the Java SimpleSend application. This ensures that your application uses the connection details for your Event Hub:
mvn clean package -DskipTests
The build process may take several minutes to complete. Ensure that you see the [INFO] BUILD SUCCESS message before continuing.
You'll now configure a receiver (also known as subscribers or consumers) application to ingest data from your Event Hub.
For the receiver application, two methods are available; EventHubReceiver and EventProcessorHost. EventProcessorHost is built on top of EventHubReceiver, but provides simpler programmatic interface than EventHubReceiver. EventProcessorHost can automatically distribute message partitions across multiple instances of EventProcessorHost using the same storage account.
In this unit, you’ll use the EventProcessorHost method. You'll edit the EventProcessorSample application to add your Event Hubs namespace, Event Hub name, shared access policy name and primary key, storage account name, connection string, and container name.
Change to the EventProcessorSample folder using the following command:
Open the code editor.
Select the EventProcessorSample.java file.
Locate and replace the following strings in the editor:
----ServiceBusNamespaceName----with the name of your Event Hubs namespace.
----EventHubName----with the name of your Event Hub.
----SharedAccessSignatureKey----with the value of the primaryKey key for your Event Hubs namespace that you saved earlier.
----AzureStorageConnectionString----with your storage account connection string that you saved earlier.
----HostNamePrefix----with the name of your storage account.
Save EventProcessorSample.java either through the "..." menu, or the accelerator key (Ctrl+S on Windows and Linux, Cmd+S on macOS).
Close the editor.
Use Maven to build EventProcessorSample.java
Change to the main EventProcessorSample folder using the following command:
Build the Java SimpleSend application using the following command. This ensures that your application uses the connection details for your Event Hub:
mvn clean package -DskipTests
The build process may take several minutes to complete. Ensure that you see a [INFO] BUILD SUCCESS message before continuing.
Start the sender and receiver apps
Run Java application from the command line by using the java command, and specifying a .jar package. Use the following commands to start the SimpleSend application:
cd ~/azure-event-hubs/samples/Java/Basic/SimpleSend java -jar ./target/simplesend-1.0.0-jar-with-dependencies.jar
When you see Send Complete..., press ENTER.
jar-with-dependencies.jar SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 2018-09-18T19:42:15.146Z: Send Complete...
Start the EventProcessorSample application using the following command.
cd ~/azure-event-hubs/samples/Java/Basic/EventProcessorSample java -jar ./target/eventprocessorsample-1.0.0-jar-with-dependencies.jar
When messages stop being displayed to the console, press ENTER or CTRL+C to end the program.
... SAMPLE: Partition 0 checkpointing at 1064,19 SAMPLE (3,1120,20): "Message 80" SAMPLE (3,1176,21): "Message 84" SAMPLE (3,1232,22): "Message 88" SAMPLE (3,1288,23): "Message 92" SAMPLE (3,1344,24): "Message 96" SAMPLE: Partition 3 checkpointing at 1344,24 SAMPLE (2,1120,20): "Message 83" SAMPLE (2,1176,21): "Message 87" SAMPLE (2,1232,22): "Message 91" SAMPLE (2,1288,23): "Message 95" SAMPLE (2,1344,24): "Message 99" SAMPLE: Partition 2 checkpointing at 1344,24 SAMPLE: Partition 1 batch size was 3 for host mystorageacct2018-46d60a17-7060-4b53-b0e0-cca70c970a47 SAMPLE (0,1120,20): "Message 81" SAMPLE (0,1176,21): "Message 85" SAMPLE: Partition 0 batch size was 10 for host mystorageacct2018-46d60a17-7060-4b53-b0e0-cca70c970a47 SAMPLE: Partition 0 got event batch SAMPLE (0,1232,22): "Message 89" SAMPLE (0,1288,23): "Message 93" SAMPLE (0,1344,24): "Message 97" SAMPLE: Partition 0 checkpointing at 1344,24 SAMPLE: Partition 3 batch size was 8 for host mystorageacct2018-46d60a17-7060-4b53-b0e0-cca70c970a47 SAMPLE: Partition 2 batch size was 9 for host mystorageacct2018-46d60a17-7060-4b53-b0e0-cca70c970a47 SAMPLE: Partition 0 batch size was 3 for host mystorageacct2018-46d60a17-7060-4b53-b0e0-cca70c970a47
You've now configured a sender application ready to send messages to your Event Hub. You've also configured a receiver application ready to receive messages from your Event Hub.