Skip to main content Skip to complementary content

Configuring Azure Service Bus connector

The configuration of Azure Service Bus target connector is performed on the source machine, when distributing a target table.

Procedure

  1. Prepare your distribution: open the Manager and follow this procedure until step 7 only: Preparing replication.
  2. Click on Distribute to open the Property tab.
    Select Service Bus in Database type.
  3. Enter the parameters as follows:
    • Endpoint: enter the endpoint of the Shared Access Signature (SAS),
    • SharedAccessKeyName: enter the Access Key Name of the Shared Access Signature (SAS),
    • SharedAccessKey: enter the Access Key of the Shared Access Signature (SAS).
      Information noteNote: For more information, see Using Shared Access Signatures (SAS).
  4. Click Ok. The connection string is displayed in the Connection String field. Each parameter of connection string is formatted as follows: name=value, and separated by a semicolon.
    Example of connection string:
    Endpoint=sb://societe.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=XXXXXXX XX=; tk=1
  5. If needed, you can add the tk option to serialize the MessageId type of key.
    The MessageId is an identifier of the message sent to Service Bus through the connector.
    Parameter name and value Description Example
    tk=0 The MessageId is generated by Service Bus API.  
    tk=1 The MessageId is generated by Talend Change Data Capture and contains all primary keys of records in ASCII format.

    The keys are inserted in the order of the primary key number assigned in the Manager.

    If the record is
    ID1= 1, ID2=" ABCD ", ID3="EFGHI"
    then the MessageId is
    0003000110004ABCD0005EFGHI
    tk=2 The MessageId is generated by Talend Change Data Capture and contains all primary keys of records in JSON format. If the record is
    ID1= 1, ID2=" ABCD ", ID3="EFGHI"
    then the MessageId is
    { " ID1":1,"ID2":" ABCD ","ID3":" EFGHI"}
    Default value is 0.
    Information noteNote: If the message identifier exceeds 128 characters, the primary key above 128 is not inserted.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!