What Is Porting Set?
Also known as: Baan porting set, LN porting set
Definition
A porting set is the platform-specific layer of Baan and Infor LN that adapts the application to a given operating system and database. It ships the bshell executable, the database drivers and system utilities, and is versioned and patched independently of the application software.
Porting Set Explained
Baan was designed to be portable across many operating systems and relational databases without changing the application code. The porting set is how that promise is kept. Application code is compiled to pseudo-code that knows nothing about the platform; the porting set supplies the compiled binaries that actually run on AIX, Solaris, HP-UX, Linux or Windows and that translate the application's database calls into native SQL for Oracle, Informix, DB2 or Microsoft SQL Server.
Physically the porting set lives in the Baan software environment directory tree, under the binaries location, and includes the bshell itself, the driver executables for each supported database, and the utilities administrators use for compiling, dumping and converting data. Because it is a separate deliverable, it carries its own version numbering and its own patch stream, distinct from the application VRCs and distinct from the Tools release.
The practical consequence is that porting set upgrades are the normal way to gain support for a newer operating system version, a newer database release or a security fix at the platform level, without touching application functionality at all. This is genuinely useful for organizations on older application releases: you can often modernize the infrastructure underneath a legacy application by moving to a newer certified porting set, buying time before a full functional upgrade.
Consistency is the operational rule. All application servers in an environment should run the same porting set version, and the porting set must be certified for the combination of operating system, database version and application release in use. Mismatches produce symptoms that are hard to diagnose: intermittent driver crashes, character set or sorting anomalies, and performance differences between nodes that look identical at the application level.
Why It Matters
- Porting set upgrades let you modernize operating systems and databases without a functional ERP upgrade, which buys real time and budget.
- Certification is a combination, not a single product: the porting set must match your OS, database and application release together.
- Mixed porting set versions across application servers cause intermittent, hard-to-diagnose failures that look like application bugs.
- Platform-level security fixes frequently arrive through the porting set, making it a patching responsibility, not a one-time install.
In Practice
When an environment behaves differently on one application server than another, check the porting set version before debugging application code. A node rebuilt at a different time and given a newer or older porting set is one of the most common causes of odd, node-specific behavior such as sorting differences, date handling changes or driver-level errors under load.
Frequently Asked Questions
Can the porting set be upgraded on its own?
Yes, and that is one of its main advantages. Because the porting set is versioned separately from the application VRCs, you can move to a newer certified porting set to support a newer operating system or database release without changing application functionality. It still requires regression testing, since the runtime and database drivers change, but the functional scope stays fixed.
What does a porting set actually contain?
It contains the platform binaries: the bshell runtime that executes application pseudo-code, the database driver executables that translate the application's data access into native SQL for the target RDBMS, and the administrative utilities used for compiling, exporting, importing and converting data. Everything in it is specific to one operating system and hardware architecture combination.
Related Terms
Bshell
The bshell is the Baan and Infor LN virtual machine. It loads compiled pseudo-code for sessions, scripts and reports, executes it, and translates the application's database calls into native SQL through porting set drivers - one bshell process typically serves one user session.
Baan/LN Tools Package
The Tools package is Baan and Infor LN's own development and administration layer. It holds the data dictionary, session and form definitions, the 3GL and 4GL compilers, VRC software layering, authorization management, job scheduling, company setup and the Exchange module.
Baan IV
Baan IV is the mid-1990s release of Baan Company's ERP suite, built on the bshell runtime with 3GL and 4GL development tools, package-based modules such as td, ti and tf, and multi-company table sharing.
Go Deeper
Infor LN Upgrade Cost Estimator
Estimate the services cost and timeline for an Infor LN version upgrade or CloudSuite migration based on your users, sites, customizations, and integrations.
Baan ERP: History, Versions, and Modern Migration Paths
Baan ERP history from Triton to Baan IV, Baan V, and Infor LN, plus practical migration paths for manufacturers still running Baan today. Get a proven roadmap.
Infor LN to CloudSuite: Migration Playbook
Infor LN to CloudSuite migration playbook: Baan and LN version paths, extension conversion, ION integration rework, timelines, and defense compliance steps.
Working with Porting Set in a live environment? Our engineers do this every day - and our AI agents automate most of it.