![]() ![]() For example, if you loaded version 10.1.0.19 of the PubSub+ Enterprise edition, use solace-pubsub-enterprise:10.1.0.19. If you loaded the image from a compressed tar archive, replace solace/solace-pubsub-standard in the example with the repository and tag that corresponds to your image.mount type=bind,source=/mnt/solace,destination=/var/lib/solace,ro=false solace/solace-pubsub-standard To run the container, enter the following command: >sudo docker run -d -p 8080:8080 -p 55555:55555 -shm-size=1g -env username_admin_globalaccesslevel=admin -env username_admin_password=admin -name=solace You must create the /mnt/solace directory on the host before creating the container. See System Resource Requirements and Managing Storage for Container Images for more information. The storage-group requires at least 5.1 GB of storage space. In the example, the storage-group (mapped to /var/lib/solace in the container) is bind-mounted to /mnt/solace on the host. ![]() For more information about the default ports that are used for each service, refer to Default Configuration for Software Event Brokers. ![]() For example, to pass AMQP encrypted traffic, you need to publish port 5671. To use additional services, you must publish each corresponding port. Port 55555-enables SMF data to pass through the container. Use this port when connecting to the container from Broker Manager (refer to PubSub+ Broker Manager for more information). Port 8080-enables SEMP management traffic to the container. publishes the following event broker container ports to the same ports on the Ubuntu host:.creates an admin user with global access permissions.runs an event broker solace using the latest PubSub+ Standard image from Docker Hub. ![]() The following example sets up a simple configuration suitable for a test deployment. There are many options that you can set with the docker create or docker run command that is used to build the event broker container. Once you've obtained the package, start Docker and load the image.įor example: >sudo docker load -i /tmp/ Step 2: Create the Container Fill in your details, and then click Get The Downloads.Ī compressed archive file called will be downloaded.Scroll to the Docker section, and then select the edition of the software event broker.Go to the Solace PubSub+ Event Broker downloads page.If you want to use another edition, you need to obtain the appropriate event broker package: This example assumes that you are using Solace PubSub+ Standard. >sudo docker pull solace/solace-pubsub-standard Pull the event broker image from the Docker repository using these two steps: Step 1: Get a PubSub+ Software Event Broker If you plan to use your event broker in a production environment, or scale your system above 1,000 connections, make sure to consult the sections above and provision your system appropriately. The example on this page is suitable for use for up to 1,000 connections, and is appropriately configured for testing and PoC activities. Information about configuring storage is at Managing Storage for Container Images. For more information, see Using System Scaling Parameters. Increasing these system limits also increases the system resources that are required. You can increase certain system limits by using System Scaling Parameters. For details about the types of system resources that are required and their characteristics, see System Resource Requirements. System resources broadly include requirements that are related to processors, memory, and storage. To achieve desired stability and performance, the infrastructure that hosts the Pubsub+ software event broker must provide a minimum set of system resources. By default, fresh installations of the event broker allow up to 100 client connections. The number of CPUs and system memory allocations that your event broker requires depends on the number of client connections that you need to support. It’s assumed that you have a stable version of the Docker daemon installed on your Linux host. Step 3: Manage the PubSub+ Software Event Broker.Step 1: Get a PubSub+ Software Event Broker.This section walks you through the steps to set up a single PubSub+ software event broker container with Docker in a non-cloud Linux environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |