Skip to main content
Feedback

Overview

Local Edition can support multiple pre-processing and post-processing processors per endpoint. This is done by linking multiple processors into one configuration. The entire process is called chaining

note

You can chain only pre-processing and post-processing events. The authentication event cannot be chained.

The following table describes chaining between different events.

Preprocess EventPost Process EventAuthentication Event
Pre Process Event
Post Process Event
Authentication Event

Types of Chaining

  • Chaining Processor Using Mashery_Proxy_Processor_Chain

    The processor implements pre-process or post-process traffic events. These processors can either be provided by Boomi or incorporated with the SDK.

    To chain the processors use Mashery_Proxy_Processor_Chain.

  • Chaining of Processor Using Chain Adapter

    These processors can implement pre-process or post-process traffic events and can be chained without using Mashery_Proxy_Processor_Chain and are provided by Boomi.

    The following are processors acting as chain adapters provided by Boomi.

    • OAuth2JWT Authentication Connector

    • OAuth2 Shared Token Connector

The following table provides information on various chaining combinations.

 SDK-Based AdaptersBoomi Provided AdaptersChain Adapter OAuth2JWTAuthenticationConnectorChain Adapter OAuth2SharedTokenConnector
SDK-Based Adapters

Using Mashery_Proxy_Processor_Chain

Using Mashery_Proxy_Processor_Chain

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Boomi Provided Adapters

Using Mashery_Proxy_Processor_Chain

Using Mashery_Proxy_Processor_Chain

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Chain Adapter OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Chain Adapter OAuth2SharedTokenConnector

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

On this Page