Locations of Other Important Components

In addition to the locations specified by environment variables, Lawson stores other important system information, including data, on the customer system. The following sections provide a high level overview of the kinds of information and where it is located.

User Data

Lawson stores globally interesting information about users, such as, names, IDs, passwords, and attributes, in an LDAP directory. Lawson customers install an LDAP server specifically for Lawson or load Lawson data into a separate container within an existing LDAP server. The installation location is determined by the customer, and typically is on a different physical machine than the application sever and the HTTP server.

Customer Application Data

Data that customers store for use with Lawson applications is stored in an RDBMS. The naming convention for folders within an application system is predefined by Lawson starting with the product line name and including the system code. Typically Lawson customers dedicate at least one hardware resource to application data.

Lawson Metadata (GEN and LOGAN)

Metadata required by the Environment is stored in a repository called GEN. (Additional information about the contents of these product lines is in another section of this document. Environment Metadata Product Lines)

Another set of metadata, that contains primarily Lawson Portal bookmark information and Process Server metadata, is stored in a repository called LOGAN.

GEN and LOGAN are considered product lines and are installed into their own data spaces in the customer RDBMS. The diagram that follows shows a typical setup.

Customer RDBMS setup

Lawson Portal

Most files associated with Lawson Portal are installed on the customer HTTP server under the document root location. Document Root is defined by the customer.

Process Server

Process Server components are installed in several locations throughout . Many components are in LAWDIR/BPM. A database of user, flow, and workunit information is in the LOGAN database.

Servlet Container

Lawson servlets reside in a servlet container that is deployed into the Environment on the Lawson server. The Lawson WebSphere folders are under the structure: WAS_HOME.

After the servlets have been deployed into the servlet container, the Lawson portion of the path is:

.../IOS-tc/WEB-INF/lib/classes/com/lawson/servlet

IBM i Differences

On IBM i, some important Lawson components are stored in the Integrated File System (IFS), including some application source and work files for GENDIR, LAWDIR, and LADBDIR, configuration and print files.

The IBM i native library system uses a standard naming convention, which includes the Lawson Environment name (for example, LAWENV9). The following describes the contents of libraries and how they are named:

Library name What it contains

ENVNAME

For example: LAWENV9

  • Environment utilities

  • LOGAN product line programs and source files

  • Service programs (for example, LARPGRTS)

  • Binding directories

ENVNAMEPGM

For example: LAWENV9PGM

Compiled applications programs.