What Is a Product Line?

A product line is a group of business logic programs and their data. You create a product line using the installation process for a Landmark application.

A product line includes:

  • Application programs and data tables

  • The product line dictionary

  • A data area built on the product line

A system will generally have multiple product lines due to one of the following scenarios. In all of these cases, you will need to carefully manage resource requirements and data storage. Note especially that there are important differences between production systems and development/test systems in terms of how multiple product lines can be configured.

Multiple Product Lines in Production Systems

Landmark production systems will have a GEN product line and can have one or more product lines for Landmark applications. Each Landmark application product line must be for a different Landmark applications. That is, you cannot have two product lines for the same Landmark application in a production system.

The data for each product line must be stored in separate database schemas. All of the schemas can be in the same database instance, including the schemas for another system such as an Infor Lawson System Foundation system. In fact, if you have a direct data access requirement between Landmark and an Infor Lawson System Foundation system (such as would be the case if you had the Infor Lawson Procurement application and the Landmark-deployed Infor Lawson Supply Chain Management applications), the schemas for the Infor Lawson System Foundation system applications and the Landmark-deployed Infor Lawson Supply Chain Management applications must be in the same database instance.

Illustration: Example product line configuration for a production system

Key:

ltm in "prodltm" and "lmrk_ltm" refers to items for the Infor HR Talent.

proc in "prodproc" and "lmrk_proc" refers to items for the Infor Lawson Supply Chain Management applications.

application and lsf_lawapps refer to items for Lawson applications.

Multiple Product Lines in Development/Test Systems

In order to perform any testing or customization of a Landmark application, you must set up additional product lines for that application. One way to do this is to set up a test system that mirrors your production system and a separate development system that also mirrors your production system. However, you also have another choice. You can set up one system that contains the product lines for both testing and development. In this case, all Landmark test and development product lines exist within a Landmark environment and WebSphere application server that are separate from your production Landmark environment and WebSphere application server.

Each product line must have its data in a separate schema, but all schemas can be in the same database instance. If your development and test Landmark system have applications that require direct data access to an Infor Lawson System Foundation system, the data for the product lines or data areas from the test/development Infor Lawson System Foundation system must be in the same database instance as the Landmark application that requires the direct data access. The illustration below shows all Landmark product lines within one Landmark environment and all database schemas for both Landmark and Infor Lawson System Foundation in the same database instance.

Illustration: Example product line configuration for development/test system

Key:

ltm in "devltm," "testltm," "lmrk_devltm," and "lmrk_testltm" refers to items for the Infor HR Talent.

proc in "devproc," "testproc," "lmrk_devproc," and "lmrk_testproc" refers to items for the Infor Lawson Supply Chain Management applications.

fin in "devfin," "testfin," "lmrk_devfin," and "lmrk_testfin" refers to items for the Infor Lawson Enterprise Financial Management applications.

lawapptest in "lawapptest" and "lsf_lawapptest" refers to items for Lawson applications.