Automatically convert your TIBCO BW processes into modern, serverless Azure Functions. Complex workflows become Durable Functions, simple processes become lightweight HTTP Functions.
A complete Azure Functions project with all the code and infrastructure you need
Complex TIBCO processes become Durable Function orchestrators with state management, sub-process calls, and fault tolerance.
Lightweight processes become stateless HTTP or Timer Functions. Fast, efficient, and cost-effective.
TIBCO activities become typed Activity Functions with DI for database, messaging, and HTTP.
Complete Bicep templates for Azure deployment with all required resources.
The tool automatically analyzes each TIBCO process and chooses the optimal Azure Function type
Used for long-running workflows that need state persistence between asynchronous operations.
Used for synchronous operations that complete in a single execution without state persistence.
Durable Functions are only needed when you must persist state between async operations. Most TIBCO patterns compile to standard C# code:
Four simple steps to migrate your TIBCO processes to Azure
Export your TIBCO BusinessWorks project as a ZIP archive and upload it.
Review the tree view, see Durable vs Simple assignments, and select which to migrate.
Watch in real-time as processes are converted to C# Azure Functions.
Download the generated project and deploy using the included Bicep templates.
Generated code follows Azure best practices and modern .NET patterns
ProjectName/
├── Orchestrations/ # Durable orchestrators
├── Activities/ # Activity functions
├── Models/ # Request/Response DTOs
├── Services/ # Database, Messaging
├── Program.cs # DI configuration
├── host.json # Functions config
├── local.settings.json
└── infrastructure/
├── main.bicep
├── parameters.dev.json
└── parameters.prod.jsonFollow these steps to deploy your generated Azure Functions project
Install the required tools on your development machine:
# Install .NET 8 SDK brew install dotnet@8 # macOS # Install Azure CLI brew install azure-cli # Install Azure Functions Core Tools brew install azure-functions-core-tools@4
Update local.settings.json with your connection strings:
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "UseDevelopmentStorage=true",
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated"
},
"ConnectionStrings": {
"DefaultConnection": "Server=your-server;Database=...",
"ServiceBus": "Endpoint=sb://your-namespace..."
}
}Build and run the Functions locally to verify everything works:
# Start Azurite (Azure Storage emulator)
azurite --silent --location /tmp/azurite &
# Build and run
cd YourProject
dotnet build
func start
# Test an orchestration
curl -X POST http://localhost:7071/api/YourProcess \
-H "Content-Type: application/json" \
-d '{"ExecutionId": "test-001"}'Use the included Bicep templates to provision Azure resources:
# Login to Azure az login az account set --subscription "YOUR_SUBSCRIPTION_ID" # Create resource group az group create --name rg-yourproject-dev --location westeurope # Deploy infrastructure cd infrastructure az deployment group create \ --resource-group rg-yourproject-dev \ --template-file main.bicep \ --parameters @parameters.dev.json
Publish and deploy your Functions to Azure:
# Build for release dotnet publish -c Release -o ./publish # Create deployment package cd publish && zip -r ../deploy.zip . && cd .. # Deploy to Function App az functionapp deployment source config-zip \ --resource-group rg-yourproject-dev \ --name yourproject-func \ --src deploy.zip
How TIBCO concepts translate to Azure services
| TIBCO Concept | Azure Equivalent |
|---|---|
| Complex Process | Durable OrchestrationDURABLE |
| Simple Process | HTTP/Timer FunctionSIMPLE |
| Activity | Activity Function |
| Timer Starter | Timer Trigger |
| HTTP Receiver | HTTP Trigger |
| JMS/RV Subscriber | Service Bus Trigger |
| JDBC Query | IDatabaseService |
| AE Publisher | IMessageService |
| Global Variables | App Settings / Key Vault |
Upload your TIBCO export and get your Azure Functions project in minutes.
Sign In to Start