Infor ION With Data Integration Developer - Remote with Travel

Key Responsibilities
 

• Design, build, and support inbound and outbound integrations between Infor XA and systems such as WMS, supplier portals, finance, ERP/CRM platforms, data platforms, and third-party applications.
• Configure and maintain Infor ION connection points, document/data flows, logical IDs, tenants, Authorized Apps, service-account credentials, IMS via API Gateway, and Enterprise Connector-based integrations.
• Configure and support XA IDF System-Link destinations, replication settings, publish jobs, BOD generation, XA outbox/inbox processing, and inbound BOD handling.
• Develop and maintain mappings and transformations for BOD/XML, XSLT, JSON, CSV/flat files, SQL/JDBC, REST/SOAP APIs, and message-based integrations.
• Support core manufacturing and supply-chain data flows such as Item/Material Master, Vendor/Supplier, BOM, Purchase Orders, Sales Orders, Supplier Invoices, Inventory, Warehouse, and Supplier Exchange.
• Troubleshoot integration failures using ION Desk, OneView, Error BODs, XA Transaction Status, System-Link logs, SLO/SLS/NLS logs, API Gateway errors, credential issues, certificate issues, and logical ID mismatches.
• Implement integration logging, retry/error handling, validation, monitoring, documentation, and deployment support across Dev/Test/Prod.
• Work with functional analysts, ERP SMEs, infrastructure teams, vendors, and business users to translate process requirements into reliable integration designs.
• Infor’s XA configuration guidance describes XA generating BODs through System-Link, placing them in the XA ION outbox, ION Connect routing them through data flows, and inbound BODs returning through the System-Link inbox for processing.

4. Required Qualifications

• Must-have: Hands-on experience developing or supporting integrations involving Infor XA / MAPICS.
• Must-have: Hands-on experience with Infor ION / ION Desk, including connection points, document flows/data flows, BODs, and production troubleshooting.
• Must-have: Practical understanding of XA IDF System-Link, including destinations, replication settings, publish jobs, outbox/inbox concepts, and BOD processing.
• Must-have: Strong working knowledge of BOD-centric integration, including XML payloads, BOD verbs such as Sync/Process/Acknowledge/Get/Show, system-of-record concepts, and event-driven data publishing.
• Must-have: Experience with REST/SOAP APIs, XML, XSLT, JSON, CSV/flat files, SQL, authentication, error handling, and data transformation.
• Must-have: Ability to troubleshoot failed integrations end to end across application, middleware, data, credential, network, and payload layers.
• Must-have: Familiarity with IBM i / AS400 / Power Systems environments supporting XA integrations; RPGLE, CL, RPGXML, or DB2 for i experience is strongly relevant.
• Must-have: Prior experience supporting integration testing, deployment, documentation, and production support.
• Infor documentation and market postings support these requirements: ION integrations use connection points and data flows; XA/ION work commonly involves System-Link, IMS via API Gateway, Enterprise Connector, RPGLE/RPGXML, REST APIs, BODs, and troubleshooting through ION/XA tools.

• Experience with Boomi AtomSphere, including process building, connectors, profiles, maps, API Management, Boomi Runtime/Atom, and Boomi API Gateway.

• Experience with Boomi Gateway for API exposure, authentication, deployment, and API traffic management.

• Experience with IBM MQ / IBM Message Queue, JMS, queues, channels, listeners, topics/subscriptions, certificate management, stuck-message troubleshooting, and message-based integration support.

• Experience with EDI X12, AS2, SFTP/FTP, trading partner integrations, WMS, logistics, supplier exchange, or manufacturing supply-chain integrations.

• Scripting or programming experience in Java, Groovy, JavaScript, Python, C#, RPGLE, CL, or SQL/PL SQL.

• Boomi Developer certification, Infor ION training, IBM MQ experience, or similar integration-platform credentials.
• ​​​​​​​Boomi postings commonly emphasize process development, connectors, API integration, mapping, JSON/XML, error handling, and Dev/Test/Prod support; Boomi Gateway documentation positions the gateway as an API front door and decoupling layer. For this XA/ION-focused role, Boomi is best treated as complementary unless your environment uses Boomi as a primary runtime.