# Infor ION On-Premises Grid and Connector Health Checklist

> Source: https://netray.co/tools/infor-ion-on-premises-grid-health-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A periodic health check for ION running on the Infor Grid on premises: grid, ION services, monitoring, security and recovery readiness.

## Category

developer

## Erp

Infor ION

## Audience

- ION administrator
- Infor OS administrator
- ERP infrastructure engineer

## Tool

**Kind:** checklist

**Groups:**

#### Infor Grid

**Items:**

**Text:** All grid hosts are up and visible in the Grid Management Pages

**Critical:** true

**Text:** ION grid application nodes are running on every expected host

**Critical:** true

**Text:** Grid Management Pages reachable with the grid administrator credentials, and those credentials are stored in the password vault

**Critical:** true

Grid Bootstrap status page shows no failed nodes

Grid Status report generated and reviewed this cycle

**Text:** Grid and ION certificates do not expire within the next 30 days

**Critical:** true

Free disk space on grid hosts checked; Log Archiver configured so logs do not fill the disk

JVM memory use of ION nodes is not close to the configured maximum

Grid notifications reviewed and resolved

Grid database reachable and its backup ran successfully

#### ION services and data flows

**Items:**

**Text:** Number of active data flows in ION Desk matches the expected list

**Critical:** true

**Text:** Every connection point passes its test action

**Critical:** true

No connection point left paused after maintenance

**Text:** COR_INBOX_ENTRY / COR_INBOX_HEADERS cleaned by the application; oldest row age recorded

**Critical:** true

Outbox tables: unprocessed message count in the ION Desk management view is near zero

Message backlog per connection point checked and trending down

ION OneView purge settings reviewed and the last purge completed

Listeners started for every file and database connection point that needs one

#### Monitoring and alerts

**Items:**

**Text:** Alerts for business process errors and for exceptions configured and assigned to a monitored distribution list

**Critical:** true

E-mail setting for ION notifications points to a working SMTP server and address

Unhandled error messages in ION OneView reviewed and marked handled

Monitors for overdue documents active for critical flows (for example orders not acknowledged)

A named owner checks errors on a schedule, not only when users complain

Logging levels set back to normal after any troubleshooting

#### Security

**Items:**

**Text:** Service accounts used by connection points have current passwords and least privilege

**Critical:** true

ION API authorized apps reviewed; unused apps and service accounts removed

TLS enabled on ION endpoints and grid web access

Database accounts for Database connection points cannot write outside staging tables

Grid security roles reviewed against the current admin team

Protected content and mappings exported only to secured locations

#### Change and recovery

**Items:**

**Text:** Export of ION configuration (data flows, connection points, mappings, monitors) taken and stored off the server

**Critical:** true

**Text:** ION database backup verified by a test restore at least once a year

**Critical:** true

Important grid files backed up as listed in the Grid administration guide

Documented start order: database, grid, ION, then connected applications; stop in reverse

Smoke test after patching: one document per critical flow traced in ION OneView

Change log kept for every data flow activation or deactivation

**Scoring Note:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the checklist

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is the Infor ION Grid?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

infor ion grid, infor ion grid management credentials, infor ion on premise, why is ion not working, infor ion status overview email address, ion grid management pages, ion oneview purge, infor ion health check

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
