11 docs tagged with "event_broker"

This page walks you through the installation procedure for TeamForge Webhooks-based Event Broker (WEBR).

Here's what it takes to install and run TeamForge and other integrations supported by TeamForge.

Queue type events are provided within the TeamForge Webhooks-based Event Broker to support client server processing and http based load balancing. It provides a robust mechanism for invoking jobs asynchronously and receiving the response through callbacks.

The TeamForge Webhooks-based Event Broker v4 engine provides powerful scripting using JavaScript and custom JSON filtering capabilities that provide customization capability to products through webhooks.

A SYNC event type within the TeamForge Webhooks-based Event Broker is called as a Pre-Submit event in TeamForge. Only one subscription is allowed for this event type.

TeamForge Webhooks-based Event Broker is a webhook driven integration broker, delivered as a free technical microservice along with TeamForge. It is a replacement for the event brokering aspects of the now deprecated EventQ product.

The TeamForge Webhooks-based Event Broker related settings are discussed in this page.

TeamForge Webhooks-based Event Broker supports TeamForge—Jenkins integration. Jenkins integration plugin is used to integrate TeamForge with Jenkins using TeamForge Webhooks-based Event Broker.

TeamForge Webhooks-based Event Broker supports TeamForge-JIRA integration. A new JIRA integration plugin version 1.1 is used to integrate TeamForge with JIRA using the TeamForge Webhooks-based Event Broker.

TeamForge's native Webhooks-based Event Broker replaces EventQ as the default event broker to support TeamForge integration with TestLink. EventQ-based TeamForge—Testlink integration is no longer supported.

A TOPIC event type within the TeamForge Webhooks-based Event Broker is called as a Post-Submit event in TeamForge. The message of this event type is delivered to all the subscription endpoints.