How-toInfor XA (MAPICS XA, IBM i)Net.Link / Web Access

Infor XA Net.Link: what it is, how it is configured and common issues

Question
infor xa net-link

Also searched as

  • infor xa netlink
  • mapics net.link
  • infor xa web interface

Short answer

Net.Link is the web access layer associated with Infor XA (formerly MAPICS XA) that exposes XA functions through a browser, running on an IBM i web application server. It depends on the IBM i version, the web server profile and Java runtime, so most problems after changes trace to those components. Details vary by XA release, so confirm against your installation guide.

Applies to: Infor XA (MAPICS) on IBM i. Component names and versions vary by release.

Check and troubleshoot a Net.Link installation

  1. 1Find the installation guide and release notes for your XA release in the Infor support portal.
  2. 2Identify the web application server instance and profile serving Net.Link on the IBM i.
  3. 3Check that the web server and application server jobs are active (WRKACTJOB).
  4. 4Check the Java version and the IBM i PTF level against the supported matrix.
  5. 5Review the application server and HTTP server logs for the failing request.
  6. 6Verify user profiles, authority and library lists used by the web sessions.
  7. 7Check certificates and TLS settings if browsers refuse the connection.
  8. 8Test with a single user and a simple function before testing full workflows.

What Net.Link does

XA's core is RPG and COBOL code with 5250 green-screen interfaces on IBM i. Net.Link presents selected functions to browser users through a web application running on the same platform, so users need no 5250 emulator. It is an interface layer: the business logic and data remain in XA's libraries and files.

I am describing the role rather than every component, because the exact architecture changed across releases. Use your installation documentation for specifics.

Typical problems

Most failures after a change are version drift. An IBM i upgrade, a Java change, an expired certificate or a PTF level that no longer matches the supported matrix can stop the web layer. Other common issues include authority problems for the web user profile, library list differences between 5250 and web sessions, and memory or job limits on the application server.

Slow pages usually point to the application server's resources or to long-running underlying programs, not to the browser.

WRKACTJOB SBS(QHTTPSVR)
WRKACTJOB SBS(QWAS9)   (subsystem name varies by version)
DSPLOG PERIOD((*AVAIL *CURRENT))

Modernisation options

Many XA shops are deciding between staying on the web layer, moving to a newer Infor product, or integrating around the core. A pragmatic middle path is to keep XA running and add integration through IBM i web services or ION, which gives modern applications access without replacing the core. See the REST page linked below.

Try it here, free

Infor XA (MAPICS) Migration Readiness Assessment

Open full tool

Ten questions that score how ready you are to move off Infor XA (MAPICS), covering customizations, IBM i dependencies, data quality and ownership.

Common pitfalls

  • !Upgrading IBM i or Java without checking the XA support matrix.
  • !Letting a certificate expire unnoticed.
  • !Giving the web profile too much authority instead of the least needed.
  • !Different library lists for web and green-screen users.
  • !Lack of documentation after the original consultant leaves.

How an ERP-grounded AI assistant handles this

Netray's approach to XA does not touch the web layer: a read-only connection to the IBM i data plus documents gives an on-prem assistant that answers questions about orders, inventory and costs. This suits shops whose Net.Link knowledge is thin and who want value without a migration.

See ERPray

Frequently asked questions

Is Net.Link still supported?

Support depends on your XA release and support contract. Check with Infor for the current status and the supported IBM i levels.

Do users need 5250 emulation?

Not for functions exposed through the web layer, but many XA functions are still used through 5250 sessions.

Why did it stop after an IBM i upgrade?

Usually a mismatch between the new OS or Java level and the web server or application server version. Check logs and the supported matrix.

Related

How-to

Infor XA REST API: expose XA through IBM i Integrated Web Services or ION

Infor XA has no single built-in REST API. Practical routes are IBM i Integrated Web Services (IWS), which turns RPG or SQL routines into REST endpoints on the same machine, and Infor ION where your environment supports it. For reads, SQL-backed services are straightforward. For writes, call XA's own programs so business rules run.

How-to

Infor XA costing: cost types, roll-up and standard cost setup

Product costing in Infor XA builds an item's cost from its material, labor, and overhead using the bill of material and routing. Standard cost is the frozen planning cost used to value inventory and measure variance, while other cost sets are used for current or simulated views. A cost roll-up calculates costs from the lowest BOM level upward. Exact program names and options vary by release.

How-to

Infor VISUAL system requirements: server, SQL Server, client and network

VISUAL runs on Windows with Microsoft SQL Server, using Windows client workstations. The exact supported Windows and SQL Server versions depend on the VISUAL release, so take them from Infor's release documentation, not from memory. This page lists what to verify, how to size, and where upgrades commonly break.

How-to

Infor XA User List Report: Users, Status and Access for an Audit

Infor XA runs on IBM i, so a complete user list is built from two layers: the IBM i user profiles (who can sign on, status, last sign-on, group profiles, special authorities) and the XA application security tables (which menus, functions and facilities each user may run). Export the first with DSPUSRPRF or the QSYS2.USER_INFO view, add the second from your XA security setup, and join them by user ID.

Advanced

Infor XA PowerLink (Power Link), SIWA and Net-Link: What Each Does and Your Options

Infor XA runs on IBM i with a 5250 green-screen core. PowerLink (also written Power Link) and Net-Link are the interface layers Infor offered to put a more modern or web face on that core, and SIWA is another piece of XA's interface and integration tooling. Because naming and packaging changed across releases, confirm exactly what is installed before planning any change.

How-to

Infor XA Factory Track: What It Does and How to Plan Shop Floor Data Collection

Factory Track is the shop floor data collection offering associated with Infor XA. It captures labor, job and material transactions at the work centre, often with bar code terminals, and posts them to XA production control so that job status, costs and inventory stay current without re-keying. Details differ by release, so check your documentation before configuring anything.

AI for ERP

AI for Infor XA on IBM i: On-Prem, No Replatforming Required

Add AI to Infor XA on IBM i (AS/400) without a migration project. Read DB2 for i directly, ground answers in live XA data, keep everything on-prem.

AI for ERP

AI Agents Over Infor ION API, BODs, and the Infor Data Lake

Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.

Stuck on Infor XA (MAPICS XA, IBM i)?

Talk to engineers who work inside Infor XA (MAPICS XA, IBM i) every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software