Sankofa/docs/phoenix/BUSINESS_COMMUNICATIONS.md

Phoenix Business Communications Infrastructure

Overview

Phoenix provides comprehensive business communications infrastructure including AS4 gateway for B2B document exchange, workflow automation (Logic Apps equivalent), and financial messaging gateway for banking and financial transactions.

Architecture

┌─────────────────────────────────────────────────────────────┐
│         Phoenix Business Communications Stack                │
├─────────────────────────────────────────────────────────────┤
│                                                              │
│  ┌──────────────────┐  ┌──────────────────┐                │
│  │  Email Server    │  │  AS4 Gateway     │                │
│  │  (Sankofa Mail)  │  │  (B2B Exchange)  │                │
│  └────────┬─────────┘  └────────┬─────────┘                │
│           │                      │                           │
│           └──────────┬───────────┘                           │
│                      │                                       │
│           ┌──────────▼───────────┐                          │
│           │ Business Integration │                          │
│           │ Gateway (Logic Apps) │                          │
│           └──────────┬───────────┘                          │
│                      │                                       │
│           ┌──────────▼───────────┐                          │
│           │ Financial Messaging  │                          │
│           │ Gateway             │                          │
│           └─────────────────────┘                          │
│                                                              │
└─────────────────────────────────────────────────────────────┘

Components

1. Email Server (Sankofa Mail)

Purpose: Organizational email with business communication support

Features:

• SMTP/IMAP/POP3 services
• Email authentication (SPF, DKIM, DMARC)
• Business email routing
• Integration with AS4 gateway
• Integration with workflow automation

Integration Points:

• Routes business emails to AS4 gateway
• Triggers workflows via email
• Processes financial notifications

2. AS4 Gateway

Purpose: Secure B2B document exchange using AS4 protocol

Standards:

• AS4 (OASIS ebMS 3.0)
• WS-Security
• X.509 certificates
• EU eDelivery AS4 profile

Features:

• Secure message exchange (SOAP/WS-Security)
• Digital signatures and encryption
• Message reliability (receipts, acknowledgments)
• Trading partner management
• Message routing and transformation
• Compliance and audit logging

Use Cases:

• Government document exchange
• Healthcare data exchange
• Legal document transmission
• Supply chain communications
• Regulatory compliance reporting

3. Business Integration Gateway (Phoenix Logic Apps)

Purpose: Workflow automation and integration platform

Features:

• Visual workflow designer
• API integration and orchestration
• Business process automation
• Data transformation (JSON, XML, EDI)
• Event-driven workflows
• Scheduled tasks and triggers
• Connector library

Recommended Platforms:

• n8n: Open source, visual workflow automation (recommended)
• Apache Airflow: Workflow orchestration
• Camunda: BPMN workflow engine
• Temporal: Workflow orchestration

Integration Capabilities:

• REST APIs
• SOAP services
• Database connectors
• File system operations
• Email/SMS integration
• Blockchain integration
• AS4 gateway integration
• Financial messaging integration

4. Financial Messaging Gateway

Purpose: Financial message handling and envelope processing

Standards Support:

• ISO 20022: MX messages (modern standard)
• SWIFT MT: Legacy SWIFT messages
• FIX Protocol: Trading messages
• EDI X12: Financial transactions
• EDIFACT: International trade
• SEPA: Single Euro Payments Area

Message Types:

• Payment messages (pain.001, pain.002, pacs.008, pacs.009)
• Bank statements (camt.053, camt.054)
• Securities messages
• Trade finance messages
• Regulatory reporting

Features:

• Message validation and transformation
• Message routing
• Encryption and digital signatures
• Audit logging
• Compliance reporting
• Long-term message archives

Integration Flows

Flow 1: Business Document Exchange via AS4

Trading Partner → AS4 Gateway → Business Integration Gateway → Internal Systems
                ↓
         Message Archive
         Audit Log

Flow 2: Financial Transaction Processing

Banking System → Financial Messaging Gateway → Business Integration Gateway → AS4 Gateway → Trading Partner
                ↓
         Message Archive
         Compliance Report

Flow 3: Workflow-Triggered Communication

Event → Business Integration Gateway → AS4 Gateway → Trading Partner
     ↓
Email Server → Notification

Flow 4: Email to Business Process

Email → Email Server → Business Integration Gateway → Workflow Execution

Setup and Configuration

AS4 Gateway Setup

1. Install AS4 Software:

   # Option 1: Holodeck B2B (Open Source)
   docker run -d \
     --name holodeck-b2b \
     -p 8080:8080 \
     -v /opt/as4-gateway/data:/data \
     holodeckb2b/holodeck-b2b:latest
   
   # Option 2: Hermes4AS4
   # Download from: https://github.com/hermes4as4/hermes4as4
   

2. Configure Certificates:

   # Generate X.509 certificates
   openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 365
   
   # Import to keystore
   keytool -import -alias as4-cert -file cert.pem -keystore keystore.jks
   

3. Configure Trading Partners:

   <trading-partner>
     <id>PARTNER_001</id>
     <endpoint>https://partner.example.com/as4</endpoint>
     <certificate>partner-cert.pem</certificate>
   </trading-partner>
   

Business Integration Gateway Setup

1. Install n8n (Recommended):

   cd /opt/phoenix-integration
   docker-compose -f docker-compose-n8n.yml up -d
   

2. Access Web Interface:

   • URL: http://integration.sankofa.nexus
   • Default credentials: admin / CHANGE_ME_ON_FIRST_LOGIN

3. Create Workflows:

   • Visual workflow designer
   • Drag-and-drop nodes
   • Configure connectors
   • Set up triggers

4. Configure Connectors:

   • AS4 Gateway connector
   • Financial Messaging Gateway connector
   • Email connector
   • Database connectors
   • REST/SOAP connectors

Financial Messaging Gateway Setup

1. Install Message Processor:

   # Custom implementation or commercial solution
   # Configure ISO 20022 message handlers
   

2. Configure Message Formats:

   # ISO 20022 schemas
   /opt/financial-messaging/formats/iso20022/
   
   # SWIFT MT formats
   /opt/financial-messaging/formats/swift/
   
   # FIX protocol
   /opt/financial-messaging/formats/fix/
   

3. Set Up Message Routing:

   routing-rules:
     - pattern: "pain.001.*"
       destination: "payment-processor"
     - pattern: "camt.053.*"
       destination: "statement-processor"
   

Security and Compliance

Encryption

• Transport: TLS 1.3 for all connections
• Message: End-to-end encryption for sensitive data
• At Rest: Encrypted message archives

Digital Signatures

• X.509 Certificates: For AS4 messages
• S/MIME: For email communications
• XML Digital Signatures: For financial messages

Audit and Compliance

• Message Logging: All messages logged with timestamps
• Audit Trails: Complete audit trail for compliance
• Retention: Long-term message archives (7+ years)
• Compliance Reports: Automated compliance reporting

Monitoring

Health Checks

# AS4 Gateway
curl http://as4.sankofa.nexus/health

# Business Integration Gateway
curl http://integration.sankofa.nexus/health

# Financial Messaging Gateway
curl http://financial.sankofa.nexus/health

Metrics

• Message throughput
• Processing latency
• Error rates
• Queue depths
• Storage usage

Alerts

• Message processing failures
• Queue backup
• Certificate expiration
• Storage capacity warnings

Best Practices

1. Message Archiving: Archive all business messages for compliance
2. Redundancy: Deploy redundant gateways for high availability
3. Monitoring: Set up comprehensive monitoring and alerting
4. Security: Regular certificate rotation and security updates
5. Testing: Test message flows in staging before production
6. Documentation: Document all trading partner configurations
7. Backup: Regular backups of message archives and configurations

Troubleshooting

AS4 Messages Not Delivered

1. Check trading partner endpoint connectivity
2. Verify certificate validity
3. Check message format compliance
4. Review AS4 gateway logs

Workflow Failures

1. Check workflow execution logs
2. Verify connector configurations
3. Test individual workflow steps
4. Check database connectivity

Financial Message Errors

1. Validate message format
2. Check routing rules
3. Verify encryption/decryption
4. Review message transformation logs

Next Steps

1. ✅ Deploy all three gateway VMs
2. ✅ Configure SSL/TLS certificates
3. ✅ Set up trading partners (AS4)
4. ✅ Create workflow templates
5. ✅ Configure message formats
6. ✅ Set up monitoring and alerting
7. ✅ Configure message archives
8. ✅ Test end-to-end message flows
9. ✅ Set up compliance reporting
10. ✅ Document trading partner configurations

---

Last Updated: 2025-12-08
Status: Production Ready
Maintainer: Phoenix Business Communications Team