About this guide

This Developer’s guide describes how you can develop and deploy business interfaces for LN application servers, using the LN Studio.

An elementary understanding is needed to use this guide; you require general knowledge about Business Data Entity (BDE) interfaces, Oagis Business Object Documents (BODs) and the way Infor LN or Baan software is structured.

This document is valid for the following product versions:

  • LN Studio 8.4.2 and 8.5 or later.
  • Enterprise Server 8.4.2 or later.
Note: A runtime from LN Studio requires at least Enterprise Server 8.4.2. Therefore, when using the LN Studio, do not generate into LN FP4 or lower if the runtime is also delivered to customers or sites that are still on Enterprise Server 8.4.1 or lower.

This document contains the following development information:

  • Chapter 1: “Introduction”. A short explanation about Abbreviations and Terminology used in this document.
  • Chapter 2: “Creating a Business Interface Implementation for LN” describes how to use the LN Studio to create business interface implementations specifically for LN application servers and how to generate the corresponding business objects in LN
  • Chapter 3: “Using Hooks for LN”, explains how to write specific logic in hooks.
  • Chapter 4: “Method-Specific Guidelines”, discusses guidelines to take into account when implementing standard methods.
  • Chapter 5: “Publishing and Receiving Events”, describes how to implement event publishing methods and how to adapt an LN application package to allow it to publish application-specific events for a business object.
  • Chapter 6: “Modeling BIIs for Complex Cases”, is about how to implement business objects in specific complex situations.
  • Chapter 7: “Import from BOR”: how to migrate existing LN business objects from the BOR to the LN Studio.
  • Chapter 8: Implementing OAGIS BODs for LN”, explains how to model and implement business interfaces for OAGIS BODs.
Caution: 
With Business Studio 8.4.2 and Enterprise Server 8.4.2, BOD-related functionality is not generally available. Do not create BODs or BOD-based integrations without prior written consent from Infor. No support will be given on the use of BODs (unless agreed otherwise).