Step 2: Creating Applications

Creating an application

In this step you will create your producer and consumer application in the Self-Service portal.

  1. On the left-side menu, click Applications

  2. In the top-right corner of the screen, click the New application button.

Application overview

  1. Application ID: Use io.axual.examples.

Producers only supply this value as additional metadata. It’s not mandatory for functionality, but it’s recommended to be included. Consumers use this ID field to keep track of events that were already consumed.
New application view

  1. Name: Use Axual Client Examples as the application mame.

  2. Short name: Use axualclientexamples as the application short name.

  3. Owner: Select default from the drop-down.

  4. Type: Select Custom as the type.

  5. Application Kind: Select Java from the drop-down.

  6. Visibility: Select Public from the drop-down

  7. Description: Enter a Description which helps (future) colleagues understand how this application handles data: i.e. "Creates sample log-events.".

  8. Click Add application, at the bottom-right of the screen

Producer credentials

The application is created. We will now configure authentication credentials for the default environment.

applications log event producer

  1. From the drop-down on the left, select the default environment.

  2. The application box in the center of the screen has a "lock" icon in its top right corner, and a blue circle: indicating that authentication is not set-up for this environment. Click the lock icon.

Configure application Credentials modal

  1. A new modal will be displayed. Click the + Generate new pair button, under the SASL section.

  2. Store the autogenerated credentials in a file for a few minutes: we’ll use them shortly.

  3. You can now close the modal

Producer authorisation

The application is created and has configured credentials for the default environment. What’s left is requesting produce permission for a stream.

At the bottom of the page, there are 2 tabs: Pending requests and History: the former is already selected.

  1. Click + Add request, at the bottom-right of the page. A modal will pop-up.

Our configured stream request modal for producer

  1. Application type: Select Producer

  2. Stream: Select applicationlogevents from the drop-down.

  3. On environment: default is your only option, so this field is not editable.

  4. Click the Request Approval button in the bottom right.

Since this is a private environment, used for testing purposes only, you do not require explicit approval from the stream owner (which anyway is also yourself). Shared environments will incur an extra step: the stream owner has to approve your request before you gain produce access. Read more about authorizing stream access here.

Consumer authorisation

For simplicity, we’ll reuse the producer application as a consumer, as well. It’s already got a credential registered for the environment, all that’s left is to request consume permission.

  1. Click + Add request, at the bottom-right of the page. A modal will pop-up.

Our configured stream request modal for consumer

  1. Application type: Select Consumer

  2. Stream: Select applicationlogevents from the drop down.

  3. On environment: default is your only option, so this field is not editable.

  4. Click the Request Approval button in the bottom right.

The request is automatically approved, just like the producer.

Optional

If you performed the Optional section in the previous step, then you should also request producer and consumer authorisation for the example-string-stream, which is deployed in the same default environment.

Next Step: Producing data

In the next step you will actually start producing some data to the newly created stream.

Proceed to Step 3: Producing data