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

> Source: https://netray.co/erp-help/infor-xa-net-link-what-it-is-and-common-issues
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## 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.

## Kind

how-to

## System

infor-xa

## Erp

Infor XA (MAPICS XA, IBM i)

## Module

Net.Link / Web Access

## Query

infor xa net-link

## Alternate Queries

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

## Applies To

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

## Steps

### Check and troubleshoot a Net.Link installation

**Items:**

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

## Sections

### What Net.Link does

**Body:**

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

**Body:**

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.

**Code:**

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

### Modernisation options

**Body:**

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.

## 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.

## Ai Angle

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.

## Faq

### Is Net.Link still supported?

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

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

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

## Search terms

infor xa net-link, infor xa netlink, mapics net.link, infor xa web, mapics xa ibm i web, infor xa browser interface, mapics xa troubleshooting, infor xa modernization

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