Creating Your First Event Broker Service
Before you start, you must have a user account for PubSub+ Cloud. If you haven't already, complete the Accessing PubSub+ Cloud tutorial.
This tutorial shows you how to:
Creating an event broker serviceon PubSub+ Cloud is easy because we take care of deploying and operating the service so that you that can focus on building client applications to stream events. You first must create an event broker service using Cluster Manager. After the service has been created, you can see the connection details, which is important for connecting from clients that publish and subscribe events with your service.
To see these steps in action, you can watch the Overview Videos.
Before You Begin
Before you start this tutorial, you must have a PubSub+ Cloud account. If you haven't already, complete the Accessing PubSub+ Cloud tutorial.
Create an Event Broker Service
After you have logged into the PubSub+ Cloud Console, you'll see a welcome page with a navigation bar on the left-hand side of the page:
On the navigation bar, is Mission Control. Mission Control allows you create and configure event streaming. In particular, you use Cluster Manager to create and manage your event broker service. When you launch Cluster Manager, you go to the Services page. This page shows you the event broker services that are available to you. If this your first service on the account, there won't be any services. Follow these steps to create your event broker service:
- If you aren't logged into PubSub+ Cloud, in a browser, go to the PubSub+ Cloud login page.
- In the PubSub+ Cloud Console, on the navigation bar, select Cluster Manager .
- On the Services page, click Create Service located on the top right corner of the page or click the Create Service card.
- In the Service Name field, type "My-First-Service".
In the Service Type, list select
Service types that provide various levels connections, message spools, and messaging performance.
For more information, see PubSub+ Event Broker: Cloud Pricing. If you have a trial account, you will only have access to one Developer service.
- In the Cloud drop-down list, select a cloud provider. For example, select Google Cloud.
- In the Region map, choose where the you want the service to run. To do this, click the map and choose a region for the provider you selected, and then click OK. For your first event broker service, choose the region closest to your geographical location. For example, if you live in the United States, choose GKE - US Central (Iowa).
- In the Broker Version drop-down list, leave the default version selected.
Click Create Service to create your first event broker service.
You've now created your first event broker service! Next, take a look at the service's details to find other information, such as connection details for your service.
Find Your Event Broker Service Connection Information
After you've clicked Start Service, your event broker service takes a few minutes to start.
After your service has started, you can see the following tabs across the top of the page.
- Status: View the overall status and health of your event broker service. You can also view information such as your event mesh details (if the service is part of an event mesh), the service information such as the cluster name/password, the status of authentication schemes used for the event broker service, and login information.
- Connect: See the connection information for your event broker service by selecting your language or protocol of choice.
- Manage: Perform tasks such as configuring queues or managing clients.
- Monitoring: If you have PubSub+ Insights, you can see advanced visualizations and graphs to manage and understand the performance of your event broker service.
- Configuration: View the details of the event broker service that you created, such as the cloud provider, region, and connection limits.
Try Me!: Try your event broker service using embedded CodePen examples.
The TryMe! functionality that's accessible in the PubSub+ Cloud Console uses public Internet and both services must have the Solace Web Messaging protocol enabled on the event broker services.
For broker versions 9.13 and later, event broker service that use private endpoints (or where you have a mix of a private endpoint and public endpoints), you must have connectivity to the same private network from the browser. For example, if you have a computer which has a VPN connection to the private region where the event broker services are located and also public Internet access, TryMe! works as expected.
To find your event broker service's connection information:
- Select the Connect tab and choose the messaging protocol your application will be using. If you're not sure, you can also change the View by drop-down to Language so you can see the connection details for the language your client application is written in. For example, we have selected Solace Messaging.
- Based on the connection information you have chosen, select the client library you would like to use. The connection information for that library is shown.
For example, we have selected the Go API.
The following information is summarized on this page:
- Get API—Information about how to get and use the client library.
- Connect to Service—Code snippets about how to connect to the service.
- Learn More—Explore links to tutorials and API documentation.
You've now learned how to see connection information for your service, in particular the connection details for your service for a particular API. This is important when you want to develop or test applications that publish and subscribe to events from your service.
Awesome! You have learned how to create services event broker service and now have a basic understanding of how to find connection information about your service. Want to learn more?
- Try exchanging some messages with your new event broker service in the next tutorial: Trying Out Your Event Broker Service.
- If you want to learn about the advanced options for service creation, see Creating Event Broker Services .