Static Deliveries and Subscriptions

Time: 15-30 minutes | Goal: Set up static AMQP 1.0 endpoints for publishing and consuming data

Prerequisites

• Completed Quick Start Guide (actor, capability, policies configured)
• Certificate bundle downloaded and extracted

Overview

Static endpoints provide persistent AMQP 1.0 connections via the web interface using SASL EXTERNAL authentication with client certificates.

Best for: Development, testing, low-moderate volumes
Limitations: Single endpoint per actor/capability, manual setup, less resilient

Step 1: Create Static Delivery (Publishing)

1. Go to TLEX Interchange Admin > Deliveries
2. Click your actor → "+ CREATE NEW"
3. Configure:
   • Delivery Name: CAM-Publisher-Test
   • Selector: messageType = 'CAM' (required, must match existing capabilities)
4. Click "CREATE" and wait 2-5 minutes
5. Record endpoint details:

Host: demo-1mb6xz.azure.tlex.cloud
Port: 5671
Target: L3D-TEST

Selector Examples:

• messageType = 'CAM' - All CAM capabilities
• messageType = 'CAM' AND publisherId = 'UK12345' - Specific publisher

Step 2: Create Static Subscription (Consuming)

1. Go to TLEX Interchange Admin > Subscriptions
2. Click your actor → "+ CREATE NEW"
3. Configure:
   • Subscription Name: CAM-Consumer-Test
   • Selector: messageType = 'CAM' (required, must match accessible capabilities)
4. Click "CREATE" and wait 2-5 minutes
5. Record endpoint details (host, port, source address)

Step 3: Implementation

Required Certificate Files

• Client Certificate + Private Key: Combined PEM file ("key_and_certificate.pem")
• CA Certificate: Separate PEM file ("ca.pem")

Connection Details Needed

Host, Port, Target/Source from your endpoints

Implementation Examples

• Publishing: Direct Delivery Example (Full Examples)
• Consuming: Direct Subscription Example (Full Examples)

When publishing, make sure that the required AMQP application properties are also sent:

Step 4: Monitor & Verify

1. Open TLEX Interchange Dashboard > Message Metrics
2. Verify increasing message counts and active endpoint status
3. Check for error indicators

Troubleshooting