Infor LN

Infor LN ION API Integration Guide

Infor ION (Intelligent Open Network) is the integration backbone for Infor LN and the broader Infor ecosystem. ION provides three integration mechanisms: BOD (Business Object Document) messaging for event-driven integration, ION API Gateway for REST API access, and ION Connect for file-based data exchange. Understanding when to use each mechanism and how to configure them is essential for connecting LN to external systems, other Infor products, and cloud services.

ION Architecture and Integration Patterns

ION operates as a middleware layer between LN and external systems. BODs are XML-based messages that flow through the ION messaging infrastructure when business events occur in LN—order creation, shipment confirmation, inventory adjustment. The ION API Gateway exposes LN functionality as REST endpoints for real-time request-response integration. ION Connect handles batch file transfers for high-volume data exchange. Choose the pattern based on latency requirements and data volume.

  • Use BOD messaging for event-driven integration where LN pushes notifications to subscribing systems
  • Use ION API Gateway for real-time request-response integration requiring immediate data retrieval or updates
  • Use ION Connect for high-volume batch data exchange where real-time processing is not required
  • Combine patterns when needed: BODs for events, APIs for data lookup, Connect for bulk synchronization

BOD Configuration and Custom BODs

LN publishes standard BODs for common business events: SyncItem, ProcessPurchaseOrder, ShipmentReceipt, and dozens more. Each BOD contains a structured XML payload with the business data. Configure BOD publishing in the ION desk by activating the relevant document flows and mapping them to connection points. For events not covered by standard BODs, LN supports custom BOD development through the BOD extension framework.

  • Activate standard BOD document flows in ION desk for the specific business events your integrations need
  • Configure connection points that route BODs from LN to the appropriate receiving systems or queues
  • Build custom BODs for LN-specific events not covered by standard Infor BOD definitions
  • Implement BOD error handling with dead-letter queues and alerting for failed message processing

API Gateway and Security Configuration

The ION API Gateway provides secure, authenticated REST API access to LN data and operations. Configure API access by defining API resources in the ION Gateway, mapping them to LN sessions or data objects, and setting up OAuth 2.0 authentication for client applications. Rate limiting, request logging, and access policies protect LN from API abuse while providing the visibility needed for integration troubleshooting.

  • Configure OAuth 2.0 client credentials for service-to-service integrations through the ION API Gateway
  • Define rate limits per API client to prevent integration overload from affecting LN interactive performance
  • Enable API request logging for troubleshooting integration issues with complete request and response capture
  • Test API integrations in a non-production ION environment before promoting connection configurations to production

Building LN integrations with ION? Our integration architects design scalable, reliable ION architectures.