Developer ToolsFree checklistPDF, Excel, Word exportInfor ION

Infor ION On-Premises Grid and Connector Health Checklist

A health checklist for Infor ION running on premises on the Infor Grid, covering the grid itself, ION data flows and connection points, monitoring, security and recovery. Run it monthly and after every patch, and export the result as a record.

0%

0 of 36 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

Infor Grid

ION services and data flows

Monitoring and alerts

Security

Change and recovery

Any unchecked item in Infor Grid or ION services and data flows needs action this week; critical items there mean messages may already be failing. Unchecked items in the last three groups belong in the next maintenance plan.

Get an ION health review

Send us your completed checklist and ION version and we will point out the risks to fix first.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the checklist

Work through the groups in order, because each depends on the one above: a grid node that is down explains connection point test failures, and failed tests explain backlogs. Use the Grid Management Pages for the first group (hosts, nodes, bootstrap status, Grid Status report, notifications, log archiving), ION Desk for the second (data flows, connection points, listeners), and ION OneView for monitoring (document tracing, error messages, purge). Tick an item only when you have looked today, not because it was fine last month. Export to PDF or Excel and keep it with your change records.

Why ION stops working: the usual causes

Most outages on premises come from a short list. An expired certificate on the grid or on an endpoint breaks every call through it at once. A full disk on a grid host, often from logs, stops nodes. An application that never cleans COR_INBOX_ENTRY and COR_INBOX_HEADERS grows its database until performance drops; Infor's development guide states ION does not remove inbox messages. A connection point paused for maintenance and forgotten silently holds messages. A changed service account password breaks a database or file connection point. Each has an item above.

  • Certificates and passwords: expire on a date you can calendar
  • Disk and memory: trend them, do not wait for alarms
  • Inbox tables: the application owns the purge

Alerts and the notification email address

ION OneView and ION Desk let you receive alerts for business process errors and for exceptions, and ION notifications use an e-mail setting you configure. Send these to a shared mailbox or distribution list that someone reads, never to one person's address. Pair them with monitors for overdue documents on critical flows, such as a Process BOD that has not been acknowledged, so silent failures surface too. Review unhandled error messages weekly and mark them handled so the list stays meaningful.

Recovery readiness

Keep an export of ION configuration (data flows, connection points, mappings, monitors) outside the server, a tested ION database backup and the grid files the Grid administration guide lists for backup. Write down the start order (database, grid, ION, then connected applications) and the reverse for shutdown, and include it in patch runbooks. After each patch, push one test document through each critical flow and trace it in ION OneView before handing back to users. This guide does not state default ports or retention values, because they vary by installation; record yours on the checklist.

Frequently Asked Questions

What is the Infor ION Grid?

ION on premises runs as applications on the Infor ION Grid (Infor Grid), a Java-based platform of hosts and nodes managed through the Grid Management Pages. The grid also hosts other Infor OS components and the Enterprise Connector.

Where are the Infor ION grid management credentials?

They are the grid administrator credentials set during installation and managed under grid security, as described in the Infor ION Grid Security Administration Guide. Store them in your password vault and test access as part of each health check.

Why is ION not working after a patch?

Check grid nodes first, then connection point tests, then ION OneView errors. Common post-patch causes are nodes not restarted, changed certificates, JDK changes and connected applications started before ION was ready. Trace one test document per critical flow before handing the system back.

Which email address gets ION status alerts?

The address configured in ION's e-mail setting and the recipients of alerts for business process errors and exceptions. Use a monitored shared mailbox and confirm it receives a test alert after any mail server change.

If you want ION errors and backlogs explained in plain English by an assistant running on your own servers, we can connect one to ION OneView and your grid logs.

ArchRay builder
Design the on-prem AI stack: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations