972-836-7750 Request a Demo Talk to an EDI/API Expert Search
    See all results Browse the sitemap Tip: press / to search from any page
    Talk to an EDI/API Expert Request a Demo Call Sales 972-836-7750

    Messaging and events

    Solace PubSub+ integration

    Solace PubSub+ event brokers route events across applications, clouds and sites using hierarchical topics. Retail, manufacturing, logistics and financial companies use them to build event-driven systems. ECOM connects Solace topics and queues to EDI partners, files and APIs.

    Vendor
    Solace
    Routing
    Hierarchical topics with wildcards
    Delivery modes
    Guaranteed and direct messaging
    Protocols
    SMF, AMQP, MQTT, JMS, REST
    Talk to an EDI/API Expert
    Where Solace PubSub+ fitsA hub diagram: stores, plants, warehouses and cloud services publish Solace events; the ECOM B2B gateway consumes them through topic-subscribed queues with guaranteed messaging and maps them for the ERP, warehouse, EDI partners and APIs.Where Solace PubSub+ fitsPartners, the ECOM gateway and your systemsEVENT SOURCESStoresPlantsWarehousesCloud servicesDESTINATIONSERPWarehouse (WMS)EDI partnersAPIs and appsECOM B2B gatewaySolace PubSub+Hierarchical topicsGuaranteed queuesMap events
    Where Solace PubSub+ fitsA hub diagram: stores, plants, warehouses and cloud services publish Solace events; the ECOM B2B gateway consumes them through topic-subscribed queues with guaranteed messaging and maps them for the ERP, warehouse, EDI partners and APIs.Where Solace PubSub+ fitsPartners, the ECOM gateway and your systemsEVENT SOURCESStoresPlantsWarehousesCloud servicesECOM B2B gatewaySolace PubSub+Hierarchical topicsGuaranteed queuesMap eventsDESTINATIONSERPWarehouse (WMS)EDI partnersAPIs and apps

    Events routed by Solace topics reach partners through the gateway.

    Expand diagram Download SVG

    Overview

    What Solace PubSub+ is

    Solace brokers route messages by topic. Topics are hierarchical, such as retail/orders/created/us/store123, and subscribers use wildcards to pick what they need. Brokers in different sites and clouds can be linked into an event mesh, so events reach subscribers wherever they are.

    Guaranteed messaging stores messages in queues until consumers acknowledge them; direct messaging delivers quickly without storage for data where occasional loss is acceptable. Queues can subscribe to topics, combining routing with persistence.

    Where businesses use it

    • Retail and store events

      Orders, inventory and price changes across stores, warehouses and clouds.

    • Manufacturing and logistics

      Plant, warehouse and transport events shared across sites.

    • Financial services

      Trade and payment events between systems.

    How it works

    How Solace event routing works

    A publisher sends a message on a descriptive topic. The broker matches it against subscriptions. A queue subscribed to retail/orders/> stores every order event for a consumer, which acknowledges each one after processing.

    Because the topic carries attributes such as region and store, new consumers can subscribe to exactly what they need without changes to publishers.

    An order event through a Solace brokerA sequence diagram: a store system publishes an order event on a hierarchical topic, the broker matches it to a queue subscribed with a wildcard, the ECOM gateway consumes it from the queue with guaranteed messaging, maps it and acknowledges it.An order event through a Solace brokerTopic, queue subscription, acknowledgmentStore systemSolace brokerQueueECOM gatewayPublish retail/orders/created/us/...Match queue subscriptionretail/orders/>Consume (guaranteed)Map to partner documentAcknowledge
    An order event through a Solace brokerA sequence diagram: a store system publishes an order event on a hierarchical topic, the broker matches it to a queue subscribed with a wildcard, the ECOM gateway consumes it from the queue with guaranteed messaging, maps it and acknowledges it.An order event through a SolacebrokerTopic, queue subscription, acknowledgmentStoresystemSolacebrokerQueueECOMgatewayPublishretail/orders/created/us/...Match queue subscriptionretail/orders/>Consume (guaranteed)Map to partnerdocumentAcknowledge

    The wildcard subscription on the queue captures every matching event; the acknowledgment removes it once processed.

    Expand diagram Download SVG

    In depth

    Solace integration in practice

    • Topic design

      Topic levels are agreed so consumers can filter precisely with wildcards.

    • Guaranteed or direct

      Business documents use guaranteed messaging; direct is reserved for data that tolerates loss.

    • Queues with topic subscriptions

      Queues collect events by topic and hold them until consumed.

    • Multiple protocols

      Clients connect through SMF, AMQP, MQTT, JMS or REST.

    • Event mesh

      Linked brokers route events between sites and clouds.

    • Security

      TLS, client authentication and access control lists by topic.

    In practice

    Example: store replenishment events to supplier EDI

    Stores publish replenishment events. Suppliers need purchase orders by EDI.

    Example: store replenishment events to supplier EDIFive steps: stores publish replenishment events, a queue collects them by topic, the gateway groups them per supplier, builds each supplier's X12 850, sends it and acknowledges the events.Example: store replenishment events to supplier EDIA practical example, step by step1PublishStores publishreplenishmentevents by regionand store.Step 12CollectA queue subscribesto the relevanttopics.Step 23GroupThe gateway groupsevents per supplier.Step 34Map to 850Each supplier'spurchase order isbuilt.Step 45Send andacknowledgeOrders are sent;events areacknowledged.Step 5
    Example: store replenishment events to supplier EDIFive steps: stores publish replenishment events, a queue collects them by topic, the gateway groups them per supplier, builds each supplier's X12 850, sends it and acknowledges the events.Example: store replenishmentevents to supplier EDIA practical example, step by step1PublishStores publish replenishment events byregion and store.Step 12CollectA queue subscribes to the relevanttopics.Step 23GroupThe gateway groups events per supplier.Step 34Map to 850Each supplier's purchase order is built.Step 45Send and acknowledgeOrders are sent; events areacknowledged.Step 5

    Topics make it easy to collect exactly the events each flow needs.

    Expand diagram Download SVG

    Connections

    How Solace PubSub+ connects your business

    • Trading partners

      EDI documents from partners become Solace messages for internal systems, and events become partner documents.

    • ERP and business systems

      Orders, shipments, inventory and invoices move between applications as events, without point-to-point links.

    • APIs and files

      The same data can be published to APIs or written to files for systems that do not read the platform.

    • Business workflows

      Order-to-cash and fulfillment steps react to events as they happen.

    ECOM

    How ECOM supports Solace PubSub+

    ECOM supports Solace PubSub+ with dedicated implementation, mapping, communication and support teams, and with specialists who know the industries your partners work in.

    • Implementation team

      Plans the Solace PubSub+ setup with you, configures it on the gateway and runs the tests with your partners and systems.

    • Mapping team

      Builds and maintains the maps, code conversions and validation rules between partner data and your applications.

    • Communication team

      Sets up and monitors partner connections, certificates, keys and credentials, and coordinates changes with each partner.

    • Support team

      Watches the flows, investigates failed or missing documents, and works the issue through with you and your partner.

    For Solace PubSub+ in particular

    • Solace queue and topic connections with guaranteed messaging and topic-level access control.
    • Mapping between Solace messages and EDI, XML, JSON, files and your ERP, with validation.
    • Monitoring of queues, subscriptions and failed messages, with alerts and a clear path to reprocess.

    Frequently asked questions

    What is an event mesh?

    A network of linked event brokers that routes events between applications in different sites and clouds, so publishers and subscribers do not need to know where each other are.

    What is the difference between guaranteed and direct messaging?

    Guaranteed messaging stores messages until they are acknowledged. Direct messaging delivers without storage and suits data where occasional loss is acceptable.

    Which protocols can connect to Solace?

    Solace brokers support their own SMF protocol plus open protocols such as AMQP, MQTT, JMS and REST.

    Can Solace events become EDI documents?

    Yes. Events are mapped to partner documents, and partner documents can be published as events.

    Related pages

    Talk to an EDI/API Expert

    Tell us which partners, systems and Solace PubSub+ requirements you are working with. An ECOM specialist will review them with you and outline the setup, the maps and the tests.

    Talk to an EDI/API Expert Request a Demo