[
  {"timestamp": "0:00", "title": "Introduction and Q&A Format", "summary": "Annie explains the session is conversational, not presentation-driven, encouraging participants to ask questions, share solutions, and engage on any topics of interest related to SecureTransport."},
  {"timestamp": "1:05", "title": "File Deletion Strategy for Client Servers", "summary": "ST push cannot delete files on remote servers. For small file counts (<100/day), use pull with delete post-transfer via custom transfer site with scheduled pulls. For larger volumes, implement custom Java-based pluggable transfer site or use the API with external scheduling. SSH protocol in 5.5+ supports age-based file detection."},
  {"timestamp": "13:02", "title": "XML Export for Job Discovery", "summary": "XML export provides accounts and subscriptions (jobs). The xml_export script in the bin directory exports configuration; never use the UI button as it can timeout and hang. Export accounts with or without routes depending on setup. Business logic must be documented separately; technical routing details are in the XML."},
  {"timestamp": "20:47", "title": "XML Parsing and Subscription Visualization", "summary": "Pull the complete_subscription tag, look for partner_in/partner_out sections within transfer_configuration; site references map sources and destinations. XSD schema is available in ST's conf folder for parser validation."},
  {"timestamp": "36:54", "title": "Subscription Scheduling Failures and Recovery", "summary": "If subscriptions fail without triggering, likely database corruption if cron job isn't in DB or is misconfigured. Don't delete/recreate — get support to investigate. Cron names are ID-based, not name-based. Upgrade from old 5.5 base builds may help."},
  {"timestamp": "42:51", "title": "Multi-Subscription Single-Account Performance", "summary": "No technical limit on subscriptions per account, but UI pages slow significantly at high counts. Latest releases include folder-lookup options (recursive vs linear) and a parameter to pre-assume folder existence if checked recently. For >13,000 folders, consider multi-account strategy with cross-account site references."},
  {"timestamp": "49:39", "title": "Migration Between Servers with OS Changes", "summary": "Do not use system export when migrating with OS change — it's OS-tied and can corrupt the destination. Instead use XML export for accounts/routes, then use API (GET/PUT) to migrate restrictions and access controls. API approach avoids OS-dependent artifacts."},
  {"timestamp": "52:42", "title": "Shared Storage Selection (NFS vs GPFS vs GFS2)", "summary": "For Linux: GPFS (IBM) is best but expensive; GFS2 is good; NFS is easiest and supports most use cases (~90% of environments use NFS). For Windows: SMB shares are fastest. Selection depends on transfer volume, file size, and node count. Consult capacity guide for performance tables."},
  {"timestamp": "59:04", "title": "Fine-Tuning and Capacity Planning Approach", "summary": "Start with the support portal article 'Tuning for Secure Transport.' Use baseline recommendations from capacity guide, adjust for known customer behavior. Fine-tune iteratively with load testing. Monitor errors daily — single transfer failures can signal tuning needs."},
  {"timestamp": "62:15", "title": "Subscription-Level and Scenario Tuning", "summary": "Beyond server tuning, adjust individual subscriptions: connection count, thread pool size. Stagger scheduler times to avoid 3AM clustering. Reduce connection count to error-prone partners to lower bandwidth but increase reliability. Fine-tuning is continuous; system changes require re-tuning every 2 months."},
  {"timestamp": "67:46", "title": "Server Restart Issues on Linux (May Update)", "summary": "When restarting Linux servers, HTTP (stateless) starts before database readiness, causing some services to fail. Solution: add sleep delay (1.5-2 seconds) in start_db script or before start_http in the startup sequence. SSH doesn't have this issue because it's stateful and detects database unavailability."},
  {"timestamp": "72:30", "title": "Windows Startup Service Ordering", "summary": "Never set ST services to automatic startup on Windows — they start in wrong order. Create a wrapper service that calls start_all with a sleep delay before it. Linux doesn't have this issue; use startup scripts with sleep directly."},
  {"timestamp": "76:41", "title": "Load Testing Approaches and Tools", "summary": "No single recommended tool; Axway uses expensive proprietary tools internally. For simple tests, write custom scripts to send 10,000+ files and open 20 connections concurrently. For comprehensive testing with metrics, research open-source packages or ask community forum."}
]