Skip to content

Latest commit

 

History

History
73 lines (54 loc) · 5.21 KB

File metadata and controls

73 lines (54 loc) · 5.21 KB

Introduction

Azure Service Bus Provider for Data Exchange Framework (DEF) allows you to get data from the Azure Service Bus to Sitecore. By contrast to typical providers that are supporting both ways of data transport, this provider is limited just for the getting data from Service Bus to Sitecore.

Technically, this repository contains:

  • source code of all supporting classes
  • the necessary configuration files
  • the required Sitecore items (in form of TDS project)
  • the SC installation package of the provider

Logically, the provider consist of:

  • ServiceBus endpoint
  • troubleshooter
  • processor for reading data from ServiceBus
  • all the ServiceBus specific business logic (to connect to, to create entities and to read data)

Versions

The master branch holds the version suitable for DEF 2.1.0 (Sitecore 9.1, .NET Framework 4.7.1).

Getting Started

To start using the provider you need to have installed already:

As the next step, simply install the package.

Finally, configure the system and start using the provider.

Endpoint configuration

Connection section

  • Connection String - a connection string to the selected Azure namespace from where the provider will read the data
  • Topic - Azure topic from where the messages will be read (e.g. consultant specific data are sent into the consultantdata topic)
  • Market - a two letter upper case abbreviation of the selected market (e.g. CN for China)
  • Sender - identification of the sender from which the provider will consume the messages

Every message should contain Sender and Market info stored in meta data section of the message (they are not mixed up with the data of the message itself). According these two values the correct subscription is created by the provider:

  • Subscription name has this syntax: SC9_MARKET_Sender, e.g. SC9_CN_Orisales
  • The proper MarketingAutomation filter is created (filtering the messages for selected market and sender only)

ReadingDataSettings section

  • Batch Size - Each time we are going to read messages from Service Bus, we are reading them in a batch of messages (rather than reading them one by one). This parameter specifies the size of this batch.
  • Max Number of Messages - This is a maximum number of messages that are read during the one reading process.

For example, the following settings:

  • BatchSize=100
  • MaxNumberOfMessages=2000

mean that the system will try to read 2000 messages in 20 subsequent batches (by 100 messages).

Continuous Integration & Continuous Deployment/Delivery

Local development

When you are done with your changes you need to copy the changed assemblies to your wwwroot manually to test the result.

Versioning

Initial version of the provider is delivered in form of the standard Sitecore ZIP package.

The subsequent adjustments / changes should be delivered via Sitecore update packages. For this purpose the existing TDS project (TDS.Master) should be utilized. For more info see, for example, this link.

Important: One of the basic responsibility of the developer who is updating the provider is to ensure that all affected environments / developers will be informed / updated.

Note: Please provide the new version of the provider each time the DEF is upgraded. Use a separate branch (or any other git instrument) to keep it in this repository.