Lawson: Administering Landmark Foundation - Inforlearning.infor.com/production/vLab/Lawson10/IEN0382/IEN0382.pdf · Your notes Scenario Question Note Answer @ Copyright 2014 Infor

Lawson: Administering Landmark Foundation Training Workbook

Infor Landmark March 31, 2014

Course code: 01_0121010_IEN0382_LSU

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Legal notice Copyright © 2014 Infor. All rights reserved. Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and all supplemental related materials ("Purpose"). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause. Without limitation, U.S. export control laws and other applicable export and import laws govern your use of this material and you will neither export or re-export, directly or indirectly, this material nor any related materials or supplemental information in violation of such laws, or use such materials for any purpose prohibited by such laws. Trademark Acknowledgements The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Table of contents Table of contents ........................................................................................................................................ i About this workbook .................................................................................................................................. iii Course overview ....................................................................................................................................... iv Course description and agenda ................................................................................................................ v

Lesson 1: Landmark system overview ..................................................................................................... 1 Landmark architecture and technology ..................................................................................................... 2 What is Landmark? .................................................................................................................................... 5 Landmark tiers (or layers) .......................................................................................................................... 7 Landmark management pages .................................................................................................................. 9 Landmark administrative tools ................................................................................................................. 10 Check your understanding....................................................................................................................... 12

Lesson 2: Training environment and user interface ............................................................................. 13 Training environment ............................................................................................................................... 14 User interfaces overview ......................................................................................................................... 16 Command window for Environment ........................................................................................................ 17 Landmark Environment and links ............................................................................................................. 19 Web User Interface (UI) tools .................................................................................................................. 20 Infor Rich Client ....................................................................................................................................... 21 Landmark applications via Infor Rich Client ............................................................................................ 24 Other Web user interfaces....................................................................................................................... 26 Check your understanding....................................................................................................................... 29

Lesson 3: Landmark directory structure ................................................................................................ 30 Landmark directory structure overview ................................................................................................... 31 System files ............................................................................................................................................. 33 Install and log files ................................................................................................................................... 39 Check your understanding....................................................................................................................... 42

Lesson 4: Landmark servers ................................................................................................................... 43 Lawson Grid overview ............................................................................................................................. 44 Lawson grid node types and application modules .................................................................................. 46 Grid administration tools .......................................................................................................................... 50 Monitoring Landmark using the Lawson Grid .......................................................................................... 58 Check your understanding....................................................................................................................... 62

Lesson 5: Landmark applications: End-user support ........................................................................... 63 Landmark applications overview ............................................................................................................. 64 What is a product line? ............................................................................................................................ 67 Source code management: Subversion .................................................................................................. 69 Landmark application requests ............................................................................................................... 73 Infor Spreadsheet Designer for Microsoft Excel ...................................................................................... 79 Check your understanding....................................................................................................................... 82

Lesson 6: Landmark database ................................................................................................................ 83 Landmark database overview ................................................................................................................. 84 Landmark Database Service ................................................................................................................... 85 Landmark data structure .......................................................................................................................... 88 Landmark data dictionary ........................................................................................................................ 89 Landmark database utilities ..................................................................................................................... 90 Check your understanding....................................................................................................................... 92

Lesson 7: Landmark queues ................................................................................................................... 93 Queue mapping overview ........................................................................................................................ 94 Landmark system queues ....................................................................................................................... 95 Asynchronous processing flow ................................................................................................................ 96 Queue mapping ....................................................................................................................................... 98 Managing queues .................................................................................................................................. 103 Check your understanding..................................................................................................................... 106

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

ii Course introduction © 2014 Infor Education

Lesson 8: Maintain and troubleshoot Landmark ................................................................................. 107 Maintaining Landmark ........................................................................................................................... 108 Starting and stopping Landmark components ........................................................................................ 110 Troubleshooting Landmark .................................................................................................................... 114 Check your understanding..................................................................................................................... 119

Lesson 9: Landmark services ................................................................................................................ 120 Landmark service overview ................................................................................................................... 121 Types of services ................................................................................................................................... 122 Adding and modifying services ............................................................................................................... 124 End points .............................................................................................................................................. 126 Check your understanding..................................................................................................................... 128

Lesson 10: User administration ............................................................................................................ 129 Landmark user overview ....................................................................................................................... 130 Process for adding actors in Landmark ................................................................................................. 132 Creating and defining Landmark users via the secadm command. ...................................................... 137 Check your understanding..................................................................................................................... 139

Lesson 11: Landmark Security .............................................................................................................. 140 Landmark Security overview ................................................................................................................. 141 Landmark Security setup ....................................................................................................................... 143 Landmark authorization model .............................................................................................................. 144 Configuring user access ........................................................................................................................ 145 Landmark run-time security enablement ............................................................................................... 149 Security administration utility - secadm ................................................................................................. 150 Security reporting .................................................................................................................................. 155 Security terms ........................................................................................................................................ 156 Check your understanding..................................................................................................................... 157

Lesson 12: Landmark Configuration Console ..................................................................................... 158 Configuration Console overview ............................................................................................................ 159 Configuration and personalization ......................................................................................................... 160 Security classes ..................................................................................................................................... 162 Configuration data utilities ..................................................................................................................... 167 Configuration development process........................................................................................................ 169 Check your understanding..................................................................................................................... 170

Lesson 13: Distributed Security Package, Infor Security Administration, and federation overview .................................................................................................................................................................. 171

Distributed Security Package overview ................................................................................................. 172 Infor Security Administration overview .................................................................................................. 174 Federation overview .............................................................................................................................. 176 Synchronization overview ...................................................................................................................... 179 Check your understanding..................................................................................................................... 191

Lesson 14: Infor Process Automation .................................................................................................. 192 Infor Process Automation overview ....................................................................................................... 193 Infor Process Automation user setup .................................................................................................... 195 Monitoring Infor Process Automation work units ................................................................................... 198 System administration ............................................................................................................................ 202 Grid configuration for IPA ...................................................................................................................... 204 Check your understanding..................................................................................................................... 208

Lesson 15: Updating Landmark ............................................................................................................ 209 Update Infor Landmark Technology ...................................................................................................... 210 Update a Talent Management Suite product line .................................................................................... 213 Check your understanding..................................................................................................................... 219

Course summary ..................................................................................................................................... 220 Course review ........................................................................................................................................ 221

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Lawson: Administering Landmark Foundation Training Workbook iii © 2014 Infor Education

About this workbook Welcome to this Infor Education course! We hope you will find this learning experience enjoyable and instructive. This Training Workbook is designed to support the following forms of learning:

Classroom instructor-led training Virtual instructor-led training

This Training Workbook is not intended for self-study or as a product user guide.

Activity data

You will be asked to complete some practice exercises during this course. Step-by-step instructions are provided in this guide to assist you with completing the exercises. Where necessary, data columns are included for your reference.

Your instructor will provide more information on systems used in class, including server addresses, login IDs and passwords.

Reference materials

Landmark reference materials are available from the following locations:

Infocenter of your installed applications or products Xtreme Support (www.inforxtreme.com) Accessing Help of your installed applications or products

Symbols used in this workbook

Hands-on exercise (“Exercise”)

For your reference

Instructor demonstration (“Demo”)

Your notes

Scenario

Question

Note

Answer

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://www.inforxtreme.com/

iv Course introduction © 2014 Infor Education

Course overview This is a five-day course for system administrators to learn how to manage a Landmark Environment. The course features hands-on exercises in a live Landmark Environment.

The course is designed for system administrators who are working with an established Landmark Environment.

The class does not teach how to install or set up applications.

Course duration

5 days

Learning objectives

Upon completion of this course, you will be able to:

Describe Landmark technology and components. Explain tools and procedures used to manage Landmark processes, users, security, and updates. Define ways to troubleshoot issues.

Audience System Administrator Technical Consultant Support

System requirements Infor Landmark Training Environment

Prerequisite knowledge To optimize your learning experience, Infor recommends that you have the following knowledge prior to attending this course:

It is helpful to have experience with basic system administration (e.g. operating system, command line, Rich Client, etc.).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Lawson: Administering Landmark Foundation Training Workbook v © 2014 Infor Education

Course description and agenda This course provides the technical fundamentals needed for understanding Landmark system and applications. It also provides Landmark administrators with knowledge about tasks associated with effective implementation and maintenance of Landmark, and hands-on practice in performing these tasks.

Previous course name/code: Landmark Foundations & Administration (LMRKFNDADMLW-10UW-03)

Lesson Lesson title Learning objectives Day

Course overview Review course expectations. Day 1

Lesson 1 Landmark system overview

Describe the architecture and components that form the foundation of the Landmark system.

Define key Landmark terminology. List the tiers (or layers) of the Landmark

system. Describe key Landmark administration

tools.

Day 1

Lesson 2 Training environment and user interface

Identify the utilities available through the Landmark command prompt.

Recognize the version and products within a Landmark Environment.

Identify the various ways to access the Landmark user interface: Landmark through a Web browser /

Landmark Web10x Landmark Grid Management Pages

through a Web browser Landmark using Rich Client and

Rich Client Applet Landmark using Workspace Plugin

and Ming.le Landmark using Mobile Client

Day 1

Lesson 3 Landmark directory structure

Identify file and directory locations on Landmark Server.

Describe and use environment variables. Identify locations of important

configuration and log files.

Day 1

Lesson 4 Landmark servers Describe how to use Grid Management Pages for administration of JVM servers.

Identify each of the JVM servers and explain their importance in processing.

Describe the grid configuration file responsible for JVM starts and behaviors.

Describe how to administer this file from within the current grid user interface.

Day 2

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

vi Course introduction © 2014 Infor Education


Define the uses of configuration bindings.

Lesson 5 Landmark applications: end-user support

Define Landmark Pattern Language (LPL).

Describe what a product line and multiple product lines consist of.

Describe the Source Code Repository (Subversion/SVN).

Define how Infor Spreadsheet Designer (ISD) can be used to extract data to and from and between Landmark Environments taking into account decryption and encryption.

Day 2

Lesson 6 Landmark database

Identify the connection and configuration to relational database management system (RDBMS).

Define Landmark Database Service (LADS)

Outline db.cfg files and <dataarea>.xml files.

Describe the purpose and benefits of data dictionaries, data areas, and database utilities.

Provide examples of how database utilities are used.

Day 2

Lesson 7 Landmark queues Describe the architecture of the Async framework.

Describe the purpose of queues and queue mapping.

Identify processing of each queue. Define how to map transactions to the

queue.

Day 2

Lesson 8 Maintain and troubleshoot Landmark

Identify backup requirements. Define process for application data

process. Describe proper starting and stopping of

Landmark components. Describe the benefits of using the

ValidationURLs for troubleshooting. Identify errors, locate log, and resolve

some errors. Introduce Infor Lawson Information

Investigator’s (LII function in troubleshooting.

Day 3

Lesson 9 Landmark services Explain the purpose of a service. Describe how to execute service

additions or updates. Describe endpoints of access (external

Day 3

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Lawson: Administering Landmark Foundation Training Workbook vii © 2014 Infor Education


and internal).

Lesson 10 User administration

Describe how to add or maintain actors (User Wizard).

Describe how to add or maintain actor identities and agents.

Describe the components used to add a Landmark user: Actor Identity Role Agent ActorContext

Define Landmark users via the secadm command.

Day 3

Lesson 11 Landmark Security Define Landmark Security: Authentication and application authorization overview.

Describe how to add and apply security roles.

Describe the provided security classes and rules of access.

Explain when you would enable or disable Landmark Security.

Describe how to add security policies using the secadm utility.

Identify where to locate the security reports.

Day 3

Lesson 12 Landmark Configuration Console

Describe the purpose and role of the Configuration Console.

Describe the differences between configuration and personalization.

List the items a user can personalize. Identify the items available for

configuration. Describe how to assign the Configuration

Console Access to an administrator user for all configuration categories including: Application objects Security Web services MIME types.

Define why you would apply MIME configurations.

Provide concrete examples of using the cdexport and cdimport utilities.

Day 4

Lesson 13 Distributed Security Package, Infor Security

Describe the components of the Distributed Security Package (DSP).

Identify where the Infor Security Administration is installed.

Day 4

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

viii Course introduction © 2014 Infor Education


Administration, and federation overview

Describe the Infor Security Administration purpose and features.

Describe how to navigate within the Infor Security Administrative tool.

Describe federation and value for multiple systems on administration, authentication, and authorization.

Define synchronization and potential conflicts.

Lesson 14 Infor Process Automation

Identify the two components that run Infor Process Automation (IPA).

Describe the user setup for Infor Process Automation.

Define what a work unit is and what tools are available for a system administrator to monitor its process.

Describe the tracking of IPA work units. Describe the function of thread pools. Identify ways to manage security in IPA.

Day 4

Lesson 15 Updating Landmark

Define the steps to apply Landmark Environment updates.

Define the steps to apply Landmark application updates.

Describe WebSphere updates and settings.

Describe Java and Perl updates.

Day 5

Course summary Describe Landmark technology and components.

Explain tools and procedures used to manage Landmark processes, users, security, and updates.

Define ways to troubleshoot issues.

Day 5

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Lawson: Administering Landmark Foundation Training Workbook 1 © 2014 Infor Education

Lesson 1: Landmark system overview Estimated time

4 hours

Learning objectives

After completing this lesson, you will be able to:

Describe the architecture and components that form the foundation of the Landmark system. Define key Landmark terminology. List the tiers (or layers) of the Landmark system. Describe key Landmark administration tools.

Topics Landmark architecture and technology What is Landmark?

Landmark basic components Landmark tiers (or layers) Landmark management pages Landmark administrative tools Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

2 Lesson 1: Landmark system overview © 2014 Infor Education

Landmark architecture and technology

Infor Landmark Technology Server Setup and Maintenance Guide

Infor Landmark Technology User Setup and Security Guide

The figures on the following pages show the key Landmark components and the application architecture used for processing.

Application architecture with Web applications

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Application architecture with Grid

@

Cop

yrigh

t 201

4 Info

r

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark architecture

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


What is Landmark? Infor Landmark Technology is a platform that enables development and running of Service Oriented Architecture (SOA) applications on platforms supporting J2EE architecture application servers.

The Infor Landmark Technology platform includes both a program model and a runtime (production) system:

Program model

Built on the specifications of Landmark Pattern Language (LPL) and managed through a tightly controlled application source code repository.

Production system

Includes an application server, fully-featured relational database implementation, system administration, and configuration utilities.

Infor Landmark Technology Runtime provides the runtime environment needed to run Infor Landmark applications. The installation delivers the following components:

Infor Landmark Technology Runtime Infor Process Server Infor Rich Client user interface

Infor Landmark Technology implementation

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark basic components

Landmark Pattern Language (LPL)

Environment (Grid-> JVMs)

Configuration Console

Client and Web-based user interfaces

Web Server

Database

WebSphere Application Server

Infor Process Automation (IPA)

Infor Process Designer (IPD)

Infor Spreadsheet Designer (ISD)

Landmark component categories

Landmark components can be grouped into categories listed below. This section will discuss these components and their configurations.

Servers

Servers are Java Virtual Machines (JVMs) that comprise Landmark's functionality and run within the Grid. These will be accessed through Grid Manager or utilities.

Services

The primary Landmark service is SSOPV2, which handles authentication for most internal Landmark applications. Other external Landmark applications will also be set up as unique services providing users authentication.

Database

A relational database containing the data from Landmark system and applications. The JVM handles interaction between the Landmark Database (GEN / LTM / Strategic Sourcing etc.).

Applications

Landmark applications include both those associated with the Environment and any Landmark products installed. Unique to think of Landmark Environment as built with same structure as the applications that run within.

Network

Landmark includes Web applications that can be deployed inside or outside a firewall. Each deployment requires access and security configuration and setup. These applications also interact with WebSphere creating the path to Landmark Environment for processing.

User interfaces

Rich Client and Application Spaces establish user interfaces (UIs) for Landmark applications.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark tiers (or layers) Landmark employs a multi-tiered architecture, exposing applications enterprise-wide. Landmark consists of several tiers, or layers, including the Presentation layer, the Servlet Container layer, the Application Server layer, the Third- party Products layer, and the S3 and M3 Tier layer.

Multi-tiered means that the presentation layer is separated from the application tier, including the application server.

Enterprise-wide means the application can be exposed over the internet as well as the intranet.

Presentation layer (browser or desktop) The Landmark Web UI presentation layer is a remote application user interface. It is generated

from Landmark LPL specifications, and is mainly used for application pages that allow data entry and initiate transaction processing.

The Infor Rich Client is a remote application user interface that displays the applications pages so that users can access Landmark applications and data.

Servlet Container layer Web-facing data presentation in the Landmark system is provided by an industry-standard servlet

container (WebSphere). Servlets process commands received by a browser.

Application Server layer Application and transaction management in Landmark is provided by an industry-standard, J2EE

application server and by the Landmark Grid. The J2EE application server manages Landmark Environment services and Landmark web

applications whereas the Grid service manages various Landmark grid applications.

Third-party Products layer

The Landmark system interacts with the operating system and other standard products at this level, such as a relational database management system (RDBMS) and source control systems.

Operating system The Landmark interface with the operating system requires very little configuration. Most

Landmark configuration is accomplished at the time of installation. Java programming language

Landmark is powered by Java on both the server and client. Data persistence layer

The data persistence tier includes the RDBMS, physical data files, and the Lawson database API. JDBC database drivers communicate with the database and the application tier.

Source control tools Landmark system integration with a source control and content management system allows

more customer control over versioning, revision control, and patch deployment. The administrator uses source control tools mainly to manage test/production environments and product updates. Subversion (SVN) is used as the repository for source LPL control.

Additional components An LDAP server may optionally be used to store the information for user authentication

purposes. Bouncy Castle is used for Lawson Security encryption. Bouncy Castle is configured at

installation time.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


S3 and M3 tiers Landmark is designed to connect with S3 and M3, so that Landmark applications are not isolated

from other Lawson applications, and data integrity is carefully maintained.

Landmark can display S3, M3, and Landmark fields on the same form and update their values simultaneously when the form is saved.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark management pages Landmark includes a set of application management pages tailored to the administration and configuration needs of Landmark. Some of the tasks that you can accomplish through the Landmark application management pages can also be performed through the Grid Management Pages. However, the Landmark management pages provide a central location for working with Landmark.

There are five Landmark management pages:

Environment Async Effective Dated Requests BLExecutor Common Services

Environment management page

The Environment page is the main management page for Landmark. On this page, you can:

Stop and start the environment, or set it in admin mode (these are essentially equivalent to the startlaw, stoplaw, and adminlaw commands).

Stop and start the grid nodes for Landmark components. Monitor the status of the Landmark Environment, the data areas within the environment, and the

grid nodes for Landmark.

Note: When the system checks the status of the data areas, it is checking for all the bindings that have been defined. In some cases, the status for the gen data area may be listed as "NOT OK." However, this should be of no concern if the message you see when you click "NOT OK" indicates a binding not needed for GEN, such as Embedded Analytics.

Access the log files for each grid node.

Async management page

The Async management page allows you to manage the Async framework queues, including suspending and resuming processing, and disabling types of processing.

Effective Dated Requests management page

The effective dated requests management page allows you to manage scheduled, suspended, failed and complete effective dated actions.

BLExecutor management page

The BLExecutor management page provides a detailed view of the nodes that perform business logic processing such as the LmrkBLDoc and LmrkInteractive nodes. Three different views are provided, sorted by node, execution type, or data area. From any of these views, you can manage the processing pools.

Common Services management page

The Common Services management page allows you to review the status of connection pools and repository caches for the nodes.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark administrative tools A Landmark Environment includes several tools an administrator can use to set up and modify security.

Landmark command prompt The Landmark administrator will perform many tasks from a command prompt. When you are

instructed to use a Landmark command prompt, you should be sure you are in the Landmark Environment that you want to use, and that all environment variables are set correctly.

Some of the common command line utilities that the administrator will use include the Security Administration utility (secadm), database utilities, and the Landmark build and deploy processes. This guide presents the syntax needed to accomplish various tasks at a command prompt. For a description of the full syntax of a utility, see the Landmark Utilities Reference Guide.

For Windows 2008, you must perform some tasks from the administrator command window. If you run a task and receive the error "Open SCManager Failed with error 5: Access is denied," open a command window to "Run as administrator" and run the task again. It is also useful to have a command window configured to run as administrator that you can use whenever working with your Landmark system.

Infor Rich Client The Infor Rich Client is a user interface that allows access to data and applications on the Lawson

Landmark server. It is installed on users' and administrators' desktop machines and accesses the Lawson Landmark server through a web server connection. There are user and administrative modes to the Infor Rich Client. The administrative mode allows access to table data as well as the application forms.

Infor Landmark Administrator Mobile The Infor Landmark Administrator is a mobile application for iPhone, iPad, and iPod Touch

devices that provides an administrator with an alternative interface to monitor and manage Landmark security, process automation and async queue information.

The functionality available is the same as through the forms in the Infor Rich Client except that some minor features may not be included. For example, you can access actions to create an actor or add an actor to an existing role in the Infor Landmark Administrator, but in the Infor Rich Client you will also see menu items for such things as viewing the audit log, creating a report, exporting the record to CSV, and so on.

The Infor Landmark Administrator employs standard navigation techniques for mobile applications, such as tapping and scrolling gestures. In addition, you will find useful buttons in the upper left corner and sometimes the bottom for going back to the previous page or for going to other pages.

Configuration Console (Landmark 10) The Configuration Console is a tool within the Infor Rich Client that allows users to make changes

to the Infor Rich Client user interface without needing to make any changes to source code. There are two types of changes that can be made: Personalization - changes that apply to the user who makes them. Configuration - changes that apply globally to all users.

Security applications Through the Infor Rich Client, you can access applications for administering security and users,

including a Create User Wizard. Through these applications, you can perform many of the functions that are available through the secadm command line tool.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Web User Interface – Web UI The Web User Interface (Web UI) is a remote application user interface for several modules that

are for administration or are part of a Landmark application. These modules rely on Javascript and HTML that is generated from LPL page specifications with Lawson tools, rather than being manually coded.

The Web User Interface (Web UI) executes through a J2EE-compliant application server. With an application server, multiple client requests are serviced through a single service (the application server) running instantiated Lawson code. This allows Lawson to run applications remotely through the web.

The Grid Management Pages The Grid Management Pages is a web-accessible tool for managing and monitoring the Grid.

Through this tool, you can view the status of the grid registry system, the grid router system, the grid nodes, and the grid applications on the grid nodes. You can also use the Grid Management Pages to stop and start various grid components.

Landmark Infocenters Landmark Infocenters are a Web-based help system for Lawson products. The help system is an

Eclipse Help infocenter, built with Eclipse Platform technology. (For more information on the Eclipse Help project, see www.eclipse.org.)

You install the infocenters by deploying .war files as part of the Landmark Environment web application and as part of the web application for your Landmark application suite. When users click the Help button from a form, they can access the infocenter for either Landmark administration or for the Landmark application, depending on what form they are currently on. The infocenters provide concepts and basic user tasks. Users can display, browse, search, and print topics.

You install a Lawson Infocenter for each application occurrence. If you have multiple application servers or multiple application product lines, run the Lawson Infocenter installation process for each product line.

Examples of some common Landmark Administrator duties Monitor and manage Infor Landmark security, Infor Process Automation, and async queue

information. Administering the Grid: put something in off-line state, start/stop application, manage application,

monitor app, configure app. Manage access to table data as well as the application forms. Managing and monitoring the Grid in an Infor Landmark Environment. View the status and manage the Grid applications. View grid configurations and manage the JVM from the Grid page. Add and administer Landmark users. Note: Infor Security Services will be used after federation. Install critical updates (CUs), backup data. Create test plans and regression test plans from source code in source code repository.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://www.eclipse.org/


Check your understanding

The _____ model is built on the specifications of Landmark Pattern Language (LPL) and managed through a tightly controlled application source code repository.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Name the three major user or administrative interfaces for Infor Landmark.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 2: Training environment and user interface Estimated time

2.0 hours

Learning objectives


Identify the utilities available through the Landmark command prompt. Determine the version and products within a Landmark Environment. Identify the various ways to access the Landmark user interface:

Landmark through a Web browser / Landmark Web10x. Landmark Grid Management Pages through a Web browser. Landmark using Rich Client and Rich Client Applet. Landmark using Workspace plugin and Ming.le Landmark using MobileClient.

Topics Training environment User interfaces overview Command window for environment Landmark Environment and links Web User Interface (UI) tools Infor Rich Client Landmark applications via Inform Rich Client Infor Landmark Administrator (mobile) Other Web user interfaces Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

14 Lesson 2: Training environment and user interface © 2014 Infor Education

Training environment This section presents technical information about the class environment, including how to start it, how to log on, and details about its configuration.

It includes hands-on examples of managing a Landmark Environment. These hands-on examples are performed in a virtual machine that contains a live Landmark Environment.

Demo: Access the virtual environment and launch the command window to access the Landmark Environment

Your instructor will demonstrate how to access the virtual environment and then use the command window to access the Landmark Environment.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Note: Your instructor will provide your login and password to access your virtual machine for your Landmark training environment access

You will use Citrix to log in to the training environment.

Steps

1) Go to the Citrix internet page. (Provided by your instructor.)

2) Type <CitrixIDXXX> in the User name field. (Provided by your instructor.)

3) Type <password> in the Password field. (Password provided by your instructor.)

4) Click Log On. The Citrix menu displays with four available servers.

Citrix Main menu

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Training servers

Server Server color

IP address Access to: User name \ Passwords

Infor Landmark Server Ussplu141

Red Ussplu141.lu141training.lawson.com Landmark Active

Directory

lawson Tr@in123

Lawson System Foundation Server Ussplu143

Blue Ussplu143.lu141training.lawson.com LSF Smart Office Lawson

Business Intelligence

lawson Tr@in123

Microsoft SharePoint Ussplu145

Teal Ussplu145.lu141training.lawson.com Infor Ming.le™ Server

Infor Lawson for Workspace

lawson Tr@in123

Infor Enterprise Search Server Ussplu147

Green Ussplu147.lu147training.lawson.com Infor Enterprise Search

lawson Tr@in123

Exercise 2.1: Access your virtual machine and launch the command window

In this exercise, you will access your training environment and use the command window.

Exercise steps

1. Select the Ussplu141.lu141training.lawson.com. (Click only once.)

2. Click the Command Window for LMKENV on the desktop. @

Cop

yrigh

t 201

4 Info

r

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


User interfaces overview


Landmark includes interfaces an administrator or user can use to modify the system.

Command window for Landmark Environment Web user interface Rich Client interface Ming.le interface

The following sections provide an overview of these tools.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Command window for Environment An administrator can perform many tasks from a command prompt. These tasks will be centered on the execution of Landmark utilities. Some common command line utilities are:

Security (secadm) Database utilities (dbmaint, dbverify, dbdisplay) Landmark build and deploy processes (buildprod or enterpriseapp) Grid (managegrid) Managegrid list

Who can run command prompt tools?

The user must have an OS account for server connection and have an Actor set up in Landmark with the role of SecurityAdministrator.

The “lawson” administrator account is set up by default with the necessary access to run command prompts initially from install. Do not change the Roles associated with the “lawson” account.

Demo: Execute the managegrid list command

Your instructor will demonstrate executing the managegrid list command.

_____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

Exercise 2.2: Execute the managegrid list command

In this exercise, you will execute the managegrid list command.

Exercise steps

1. Go to the command window for LMKENV on the desktop. (You should already have the command window for LMKENV launched from the 2.1 exercise.)

2. Type managegrid list in the command line.

managegrid list lists the grid nodes and their status.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Assessing a Landmark Environment

Your instructor will demonstrate areas of the server which will better prepare you for managing the Landmark Environment assigned to you in class.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

You are handed a Landmark Environment. What steps do you take to analyze the environment?

You can examine the following:

Windows Services for an understanding of the running components web servers, IBM WebSphere, RDBMS, and Lawson Landmark Environment.

The config.bat file at C:\lawson\environment\LMKENV can be used to understand physical directory locations from install. This file contains the Environment Variables and corresponding physical paths.

install.log and install.cfg files at C:\LMKENV\system can be used to understand installation of products and set configurations executed at time of install.

Can you determine the location of Landmark Environment or Java (JDK) version used or the location of WebSphere Application Server (WAS)?

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Environment and links

Element Detail

Environment Name LMKENV C:\LMKENV

Rich Client Menu http://ussplu141.lu141training.lawson.com/canvas/

Rich Client Applet http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-A%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm Note: This allows data area changes. Applet forces user to stay in the data area selected. In this case ltm.

IBM WAS Console http://ussplu141.lu141training.lawson.com:9060/ibm/console

Grid Management http://127.0.0.1:50003

Candidate Space http://ussplu141.lu141training.lawson.com:81/ltm/CandidateSelfSer

vice/controller.servlet?dataarea=ltm

Demo: Determine the version and products within the Landmark Environment

Your instructor will demonstrate how to determine the version and products within the Landmark Environment.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.3: Determine the version and products within the Landmark Environment

In this exercise, you will determine the version and products within the Landmark Environment.

Exercise steps

1. Go to the Command Window for LMKENV on the desktop.

2. Type univver -v to see the version.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://ussplu141.lu141training.lawson.com/canvas/

http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-A%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm

http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-A%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm

http://127.0.0.1:50003/


Web User Interface (UI) tools

Lawson Grid Management The Landmark Grid Management is a web-accessible JVM tool for managing and monitoring the

Grid in a Landmark Environment. Through this tool, you can view the status and manage the Grid applications.

The Lawson Grid Management is launched through URL: http://gridhostmanager:gridwebstartport/

Note: To locate your gridhostmanager and gridwebstartport, navigate to: http://ussplu141.lu141training.lawson.com:50003

Locate the HOSTADDRESS and WEBSTARTPORT tags and use the default value. The default value is 5003.

Demo: Access the Grid Management Pages through a Web browser

Your instructor will demonstrate how to access the Grid Management Pages through a Web browser.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.4: Access the Grid Management Pages through a Web browser

In this exercise, you will access the Grid Management Pages through a Web browser.

Exercise step

1. Double-click the LMRKGRID shortcut on the desktop.

Note: Use the Back button to return from nested windows in this product.

Note: The shortcut points to this server URL: http://<yourserverinfo>:50003.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://ussplu141.lu141training.lawson.com:50003/


Infor Rich Client

Infor Rich Client User Guide

The Infor Rich Client is a user interface that allows access to data and applications on the Lawson Landmark server. It is installed on users' and administrators' desktop machines and accesses the Lawson Landmark server through a web server connection. There are user and administrative modes to the Infor Rich Client.

The router used for the user mode is: ussplu141.lu141training.lawson.com:44412.

The router used for the administrative mode is: ussplu141.lu141training.lawson.com:50002.

Note: An admin can turn off an end user’s Rich Client access on port 44412 and yet still continue to have access to the Rich Client via the admin port of 50002.

Rich Client relies on Java to support its installation. Once installed it communicates directly to the Grid Router port and uses an internal (private) copy of Java to run.

Landmark Application via browser

The Rich Client Applet can be accessed via a Java Applet. The url is: http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-g%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm

Data menu

Accessed under the Start menu and displays the Business Classes and Modules within the data area chosen.

Data area

A data area is a set of database tables potentially representing a product line. A product line is a group of modules. Example: Gen.

Business classes

Business classes are objects that contain data and business logic. They are essentially tables within the database. Example: Gen > person > Business Classes > Actor.

Process board

Graphic representation of the Roles the users have access to that display in the Rich Client canvas.

Landmark applications

A set of user interface forms to view and modify business class data.

Canvas

The canvas is a background desktop for the Rich Client that displays widgets and shortcuts with multiple spaces for customizing user experience.

Modules

Modules are containers for business classes that group them together in subject areas. Example: Gen > person.

Security module

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-g%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm

http://ussplu141.lu141training.lawson.com/richclient/richclientapplet.html?opt=-g%20-m%20ussplu141.lu141training.lawson.com:50002%20ltm


GEN > security Contains System setup business classes Service, ServiceProperty, HTTPEndpoint, Security, SSODomain

Person module

GEN > person Contains Actor business classes

Aysnc module

GEN > async Contains queue-related business classes such as AsyncActionRequest, AsyncActionTrigger

Demo: Download Infor Rich Client user and admin modes

Your instructor will demonstrate downloading the user and admin modes of Rich Client.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.5: Download Infor Rich Client user and admin modes

In this exercise, you will download both the user and admin modes of Infor Rich Client.

Exercise steps

1. Go to Internet Explorer > Favorites > Infor > Rich Client Menu. The router (44412) is listed.

2. Click Infor Rich Client Admin ussplu141.lu141training.lawson.com-44412.

3. Click OK to accept the terms and conditions.

4. Double-click the Infor Rich Client Admin shortcut on your desktop.

Note: Your desktop will now contain the shortcuts to the Infor Rich Client applications that you downloaded.

5. Type lawson in the Login field.

6. Type Tr@in123 in the Password field.

7. Click Login.

Note: The Rich Client may be downloaded by data area to allow access directly without requiring a change of data area from the base Rich Client.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exploring Infor Rich Client

The Infor Rich Client has two menus: application and data. Application navigation requires one or more form LPL (UI) and a web application definition for each business class. Data navigation works directly from the business logic definitions, if forms and lists are not defined in a user interface business class.

The Infor Rich Client canvas is your workspace. You can add widgets such as the Calendar, Data Menu or Tools from the Start menu, and you can personalize the settings to suit your preference.

Demo: Change the settings on the canvas

Your instructor will demonstrate changing the settings on the canvas.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.6: Change the settings on the canvas

In this exercise, you will change the settings on the canvas.

Exercise steps

1. Go to the Infor Rich Client Admin shortcut on your desktop.



4. Click Login.

5. Click Start. (This is the Start button on the upper right hand of the screen.)

6. Select Settings.

7. Click the Theme drop-down menu in the Details tab.

8. Click FlatBlack to change the current setting from Infor3 (white).

9. Click OK.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark applications via Infor Rich Client

Talent Management application

Your access to applications is limited to the role or roles that you have been assigned by the administrator.

All Talent Management applications, with the exception of Candidate Space are now accessible only on Infor Rich Client and have a unified user interface.

Users have access to all their roles on the same desktop. Each role has a graphic representation (called process board). All users have an employee process board. administrators, compensation analysts, HR generalists, managers, mentors, and recruiters each have their own process board which are all aligned on a grid and can be moved or reordered. Users access their process boards on the desktop when they want to perform tasks related to the role.

For example, managers will access Manager > Review Performance to complete performance appraisals for their direct reports, and Employee > My Reviews to access their own personal appraisals. Managers can have their manager process board and their employee process board opened concurrently.

Within process boards, major groupings of processes are also represented by a graphic. Hover over a graphic to see the menu items associated with the processes. An arrow at the end of a menu item indicates submenus. If no menu appears, click the graphic to display the form, list, or dashboard. For example, as an employee, click My Profile to access your profile information.

Note: For users who prefer a standard tree view, it is available under Start > Applications, or can be dragged to the desktop from Start > Library > Widgets > Navigator.

Use the Search box at the top of your desktop to locate a form. Users can find the following under the Start drop-down menu:

My Notifications My Inbasket My Print Files My Actions Set As Of Date Clear As Of Date Proxy Management Switch to Proxy Help InfoCenters

This list is not all inclusive. It includes only items that are relevant to navigation. For configuration and personalization information, see the:

Infor Rich Client User Guide

Demo: Access the Talent Management data area from Infor Rich Client and link to an employee profile

Your instructor will demonstrate accessing the Talent Management data area from Infor Rich Client and linking to an employee profile.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.7: Access the Talent Management data area from Infor Rich Client and link to an employee profile

In this exercise, you will access the Talent Management data area from Infor Rich Client, link an employee (actor) to an employee agent and then view the employee profile.

Exercise steps

Part 1: Access the Talent Management data area

1. Go to the Infor Rich Client Admin shortcut on the desktop.



4. Click the arrow next to the GEN data area.

5. Select LTM. (Note: When accessing the Infor Rich Client Admin you are logged in and viewing the GEN data area applications and data.)

6. Double-click Employee on the desktop.

7. Click My Profile. You will receive the error “Cannot open Profile Employee Default 150. Create action is not available.”

8. Click OK to close the error dialog window.

Part 2: Link to an employee profile

1. Click Start (in the upper right hand corner of the screen).

2. Select Data > person > Business Classes.

3. Double-click Agent.

4. Click the Search button (magnifying glass).

5. Type 7004, 700402 in the Name column. (700402 is the Employee ID for Mary Tyler.)

6. Press Enter.

7. Select Employee.

8. Right-click and select Link to Actor.

9. Type lawson in the Actor field.

10. Click OK. 11. Navigate back to Employee on the desktop. 12. Click My Profile. (Note: With the Agent Employee now linked to the Actor lawson in Landmark,

the employee profile for Mary Tyler opens without errors.)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Other Web user interfaces

Infor Landmark Administrator (mobile)

The Infor Landmark Administrator is a mobile application for apple iPhone, Apple iPad, and Apple iPod Touch devices that provides an administrator with an alternative interface to monitor and manage Infor Landmark security, Infor Process Automation, and async queue information.

To install the Infor Landmark Administrator, download it from the application store for your device. Before an administrator can access the Infor Landmark Environment with the Infor Landmark Administrator the account must be assigned a role that includes the MobileAdministrationWebappAccess_ST security class. Upon starting the Infor Landmark Administrator an administrator will be prompted to provide an account, password, server name, the Infor Landmark port, and the SSL setting (on or off).

The functionality available is the same as through the forms in the Infor Rich Client except that some minor features may not be included.

The Infor Landmark Administrator employs standard navigation techniques for mobile applications, such as tapping and scrolling gestures. Administrators will find useful buttons in the upper left corner and sometimes the bottom for going back to the previous page or for going to other pages.

The Infor Landmark Administrator is accessible from the Infor Landmark Technology Runtime without additional installation procedures. If an administrator has the Infor Landmark Administrator application installed and the administrator’s account has the appropriate role with server name and port, access to the app should be achieved.

Infor Landmark Administrator mobile app

Infor Ming.le™ (formerly Infor Workspace)

Infor Ming.le is a web application framework that provides a common user interface for integrated Infor Enterprise Resource Planning (ERP) applications. Infor Ming.le™ resides within the Microsoft SharePoint framework. All of the integrated Infor applications in Infor Ming.le™ use Microsoft SharePoint functionality, navigational elements, and connectivity to social media outlets, providing access for Infor partners and customers.

Demo: Launch Infor Ming.le

Your instructor will demonstrate launching Info Ming.le and add an external website to

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


your Home page.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.8: Launch Infor Ming.le and Rich Client Applet

In this exercise, you will launch Infor Ming.le and add an external website to your Home page.

Exercise steps

1. Go to Internet Explorer > Favorites > Infor > Ming.le.



4. Click Login.

5. Select Rich Client Applet site. (Rich Client Applet may also be reached at Internet Explorer > Favorites > Infor > Rich Client Applet.)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Application Infocenters “Help”

A Landmark Application Infocenter is a Web-based help system for Lawson products. The help system is an Eclipse Help Infocenter, built with Eclipse Platform technology.

Administrators can access help information about Landmark applications including “GEN” which links to the administration documentation.

You install a Landmark Infocenter for each application occurrence. If you have multiple application servers or multiple application data areas, run the Landmark Infocenter installation process for each data area.

Demo: Launch Infocenter from the LTM Rich Client

Your instructor will demonstrate launching Infocenter from the LTM Rich Client.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.9: Launch Infocenter from the LTM Rich Client

In this exercise, you will launch Infocenter from the LTM Rich Client.

Exercise steps

1. Go to the Infor Rich Client Admin shortcut on your desktop.



4. Click Login.

5. Select LTM.

6. Double-click Administrator.

7. Hover over Resources and select Resources. The Resource Search page opens.

8. Click the Infocenter icon (question mark) in the upper right hand of the screen.

9. Select Application Help. The Infocenter Help for Talent Management opens up.

The Infocenter can also be reached from within the Rich Client by Start > Settings > Help > Application or Environment. In addition, Infocenter can be accessed by direct URL outside of the Rich Client ex. Internet Explorer > Favorites > InfoCenters.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Identify the various ways to access Infor Landmark Technology state information.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

What command line utility displays the version and products within the Landmark Environment’s subversion?

a) listproduct –a b) univver -v c) listprod –r -a d) managegrid list

Identify three Infor Rich Client widgets.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

30 Lesson 3: Landmark directory structure © 2014 Infor Education

Lesson 3: Landmark directory structure Estimated time

2 hours

Learning objectives


Identify file and directory locations on Landmark Server. Describe and use environment variables. Identify locations of important configuration and log files.

Topics Landmark directory structure overview

Landmark Environment variables Landmark Environment variable settings

System files Install and log files Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark directory structure overview


This section discusses the structure of Landmark directories and files on the server. It answers the question "Where does Landmark exist?”

You will learn about Landmark’s environment variables which represent physical paths within server. In addition, you will be exposed to configuration, system, log and installation files.

Landmark environment variables

Landmark uses environment variables to reference physical file paths in order to use consistent commands on various systems. The instructor will expose each of the main directories for administration.

LADIR (Landmark directory)

The base directory for the Landmark Environment (C:\LMKENV).

LAENVDIR (Landmark environment directory)

The main file tree used to implement the Environment. Sub-directories are referenced in Appendix A of the Lawson Landmark Technology Server Setup and Maintenance Guide. (C:\LMKENV\env)

LASRCDIR (Landmark source directory)

Directory containing the business applications running under source control for Landmark. Most files under $LASRCDIR/productlineName are under source repository control (SVN) and should only be edited or updated when the file in the repository is updated/edited. (C:\LMKENV\src)

The files under source control must stay in sync with source code in the repository.

LARUNDIR (Landmark run directory)

Directory containing the major files and directories used by the Landmark runtime system. (C:\LMKENV\run)

LACFGDIR (Landmark configuration directory)

Directory containing configuration files specific to the Landmark system, for example, or install.cfg. (C:\LMKENV\system) This directory may be established as conf\.

LASYSDIR (Landmark system directory)

Directory containing additional Landmark system-related configuration files. (C:\LMKENV\system)

Most of the time the install will combine this variable with the logical file system of LACFGDIR.

LALOGDIR (Landmark log directory)

Stores log files generated in order to provide monitoring and management of the Landmark system. (C:\LMKENV\log)

Not all log files are stored in here. For example, grid node logs are stored in LAENVDIR/EnvName_grid/log.

LAPRTDIR (Landmark print directory)

Space for print files generated from the reporting subsystems.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


LAWRKDIR (Landmark work directory)

Landmark-specific temporary work area, for example, space for temporary files used in the processing of large objects, such as Character Large Objects (CLOBs) and Binary Large Objects (BLOBs) by the database interfaces.

Landmark environment variable settings

The following table lists the environment variables that must be set each time you access a Landmark Environment.

Landmark environment variable Default location

%LADIR% (Landmark directory)

The base directory for the installation of the Landmark Environment and applications.

(C:\LMKENV)

%LAENVDIR%

The main file tree used to implement the Environment. %LADIR%\env

%LASRCDIR%

Business applications source files.

%LADIR%\src

%LARUNDIR%

The files and directories used by the Lawson run time system.

%LADIR%\run

%LASYSDIR%

Additional Lawson system-related files.

%LADIR%\system

%LACFGDIR%

Lawson-specific configuration files specific to the Lawson system, such as environment.properties.

%LADIR%\conf

%LALOGDIR%

Generated log files provide monitoring and management of the

Lawson system.

%LADIR%\log

%LAPRTDIR%

Print files generated from the reporting subsystems.

%LADIR%\print

%LAWRKDIR%

Lawson-specific temporary files used in processing large objects

by the database interfaces.

%LADIR%\work

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


System files The following tables lists files used by the Landmark Environment or by components of the Landmark Environment.

File Description

%LACFGDIR%\environment.properties Contains properties related to the configuration of the Landmark Environment and applications in the WebSphere application server. environment.properties

%SYSTEMROOT%\Lawson\environment\environmentName\config.bat

This configuration file is created by the installation program. It contains the settings for the environment variables needed by the Landmark Environment. When you enter the enter.cmd command in the Landmark Environment root directory, the environment variable settings in this file are applied to your session.

%LACFGDIR%\borg.properties Contains the configuration settings for the source repository for this Environment, including the repository type, location, and authorized users. Contrast with receipt.cfg. borg.properties (Receipt and Selection)

%HOME%\receipt.cfg Contains user-specific settings for the source repository.

%LACFGDIR%\lads.cfg Used to configure the Lawson Database Server (lads), such as setting the listener port and turning debugging on and off.

%LARUNDIR%\dataarea\db.cfg Data area configuration file that contains settings for connecting to the database.

%LACFGDIR%\AsyncLoaders.xml Lists the loader classes for the Async system

%LACFGDIR%\configuration.properties Lists the configuration files for the logging system. You can also add the following properties to this file in order to cause the system to reload configuration parameters on a periodic basis: ReloadFiles=TRUE RefreshTimeOut=minutes A refresh timeout of 30 minutes is the default. If you change this file, restart the system so that the new values are in effect.

%LACFGDIR%\grid.properties Contains the properties for the Lawson Grid as well as properties for enabling and tuning proxy caching.

%LACFGDIR%\lawson-cache.properties Controls security data caches used within the Landmark Environment. This file is optional. If it is not present or is present and contains no RefreshInterval parameter, the refresh interval for security changes is 900 seconds.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://infocenter.lpc.lawson.com:81/help_lmrk_win101/topic/com.lawson.help.administration/com.lawson.help.lmrksrv-w_10.1.x/L14551146506608.html#L14551146506608

http://infocenter.lpc.lawson.com:81/help_lmrk_win101/topic/com.lawson.help.administration/com.lawson.help.lmrksrv-w_10.1.x/L14551133799653.html#L14551133799653


File Description

%LACFGDIR%\lsservice.properties Contains host and port information for the security server.

%LASYSDIR%\xssvalidator.properties Contains settings to enable and configure cross-site scripting vulnerability mitigation.

%LASYSDIR%\ldsconfig\org.eclipse.update/bookmarks.xml

Contains bookmarks to the Lawson Application Designer help system.

%LASYSDIR%\ldsconfig\org.eclipse.update\platform.xml

%LASYSDIR%\ldsconfig\org.eclipse.update\history\1186412589000.xml

GRID_HOME\applications\Landmark-lmrkEnvName\GRID-INF\application.xml

Contains settings for the Landmark grid application. Do not edit by hand.

GRID_HOME\config\runtime.xml Contains grid settings used at runtime, such as bindings. Do not edit by hand. Use the Grid Management Pages to modify these settings.

GRID_HOME\config\topology.xml Contains basic grid configuration settings, such as the grid host and grid ports. Do not edit by hand. Use the Grid Management Pages to modify these settings.

_____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

Configuration files

This section will explain configuration files. The most commonly used configuration files are listed below.

Infor Landmark Technology Server Setup and Maintenance Guide (Appendix B)

config.bat

This file is created by the installation program. It contains the settings for the environment variables needed by the Landmark Environment. When you enter the enter.cmd command in the Landmark Environment root directory, the environment variable settings in this file are applied to your session

Environment variables are defined in the config.bat file. (C:\lawson\environment\LMKENV)

environment.properties

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Contains properties related to the configuration of the Landmark Environment and applications in the WebSphere Application Server.

receipt.cfg

Contains user-specific settings for the source repository. (Subversion)

db.cfg

Contains settings for connecting to the database. There is a db.cfg file for each data area. After the initial installation there is one data, called GEN, used for system data.

borg.properties

Contains settings for the source repository, including type, location and authorized users.

Demo: Check if the environment variable is set

Your instructor will demonstrate how to use command window to check if the environment variable is set.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 3.1: Check if the environment variable is set

In this exercise, you will use command window to check if the environment variable is set.

Exercise steps


2. Type echo %LAENVDIR%.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Set the environment variable

Your instructor will demonstrate how to set the environment variable.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 3.2: Set the environment variable.

In this exercise, you will set the environment variable.

Exercise steps

1. Go to Windows Explorer > C: Drive > Lawson folder > environment > LMKENV.

2. Right-click config.bat.

3. Select Edit. The environment variable settings are displayed in Notepad.

4. Click File > Exit to close the config.bat.

5. Click the back arrow several times to navigate back to C: drive > LMKENV.

6. Scroll down and right-click enter.cmd.

7. Select Edit. The command to call config.bat file is displayed.

8. Click File > Exit to close enter.comd file.

9. Right-click Command Window on the desktop.

10. Select Properties.

11. View the Command Property enter.cmd in the Shortcut tab, in the Target field.

Demo: Locate and view configuration files

Your instructor will demonstrate how to locate and view configuration files.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 3.3: Locate and view configuration files

In this exercise, you will locate and view the contents of the following configuration files: Environment properties Receipt.cfg db.cfg for the GEN data area borg properties

Exercise steps

1. Go to C: > LMKENV > system (%LACFGDIR%).

2. Access environment properties.

3. Go to C: > Users > lawson.

4. Access receipt.cfg file.

The receipt.cfg file contains a password in clear text. This file should be secured at the operating system level.

a. Go to C: > LMKENV > run > GEN (%LACFGDIR%). Access db.cfg for GEN located in (%LARUNDIR%\GEN). This is the database configuration file for the GEN data area. Details are explained in Appendix C of the Landmark Technology Server Setup and Maintenance Guide. (C:\LMKENV\run\GEN)

The db.cfg file may contain a password in clear text. This file should be secured at the operating system level. The Lawson Landmark Technology User Setup and Security Guide contains procedures in replacing password in clear text with Privilege ID or User specific DB Authentication.

Go to C: > LMKENV > system (%LACFGDIR%). Access borg properties. This file contains the connection credentials of the version repository supporting the environment. Details are explained in Appendix D of the Lawson Landmark Technology Server Setup and Maintenance Guide. (C:\LMKENV\system)

The borg-properties file contains a password in clear text. This file should be secured at the operating system level.

ConfigurationParameter table and runtime parameters

The ConfigurationParameter table (shown below) stores various runtime parameters.

Installers load the parameters into the ConfigurationParameter table by running the migrateplconfig utility. This utility loads any parameters in a data area’s config.properties file plus selected parameters from the prodline.properties file.

This ConfigurationParameter table is maintained through the Infor Rich Client by navigating to the Start menu > Data > la > Business Classes. Double-click ConfigurationParameter.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


These parameters are by data area. There are different settings required for every Landmark application based on functionality.

Configuration Parameter List

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Install and log files


Log files

The Landmark system includes several files for setting up logging and tracing, and also numerous log files that are created when the system is in operation.

Rolling log files

Setting the rolling log file is helpful, because even with default log levels these files can grow quite large. With rolling parameter on size, it eliminates the need to manually maintain.

Use the procedure detail in the Infor Landmark Technology Server Setup and Maintenance Guide to set up the log files so that new files are created based on a number of days or on the file size. This can prevent individual log files from becoming too large.

A roll to a new file is only triggered when the system writes a log message. For example, if the number of days is set to 1 and a new day has started, a new log file is not created until the system writes a new message. For a roll to a new file to occur based on file size, the file is rolled if the size is greater than or equal to the roll size before the system attempts to write the log message. That is, the system does not include the size of the current message. If the writing of a message causes the file size to equal or exceed the roll size, then a new log file is created upon the writing of the next message.

If you set both the number of days and the size parameters, then rolling occurs based on whichever event occurs first. If you set neither, then no rolling occurs (the effect is just as if you were using the standard log file publisher).

Demo: View install and log files

Your instructor will demonstrate how to view install and log files.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 3.4: View install and log files

In this exercise, you will view the various log and log configuration files listed in Appendix B of the Infor Landmark Technology Server Setup and Maintenance Guide.

Exercise steps

1. Go to C: drive > LMKENV > system (%LACFGDIR%).

2. Locate and right-click the AsyncConfiguration.xml file.

3. Select Edit.

4. Search for “AsyncLogFileOut.” (See Rolling File specification example image.)

AsyncLogFileOut

To create a rolling log file for the Async.log, add the following parameters to the AsyncConfiguration.xml at AsyncLogFileOut publisher name.

Add Rolling parameter between .logging and LogFile as noted in the screenshot below.

Add additional parameter values size=10k as noted below.

Rolling file specification example

Click File > Save to save the configuration change.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Installation files

Installation files are detailed in Appendix B of the Lawson Landmark Technology Server Setup and Maintenance Guide.

The main installation file for Landmark is located at: LASYSDIR%\install.cfg.

The main installation file for the Landmark applications are located in: %LASRCDIR%/prodline/install/install.cfg.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Describe the use of environment variables.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Which of the following file contains user-specific settings for the source repository?

a) %HOME%\receipt.cfg b) %LACFGDIR%\AsyncLoaders.xml c) %LACFGDIR%\grid.properties d) %LACFGDIR%\borg.properties

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 4: Landmark servers Estimated time

2.0 hours

Learning objectives


Describe how to use Grid Management Pages for administration of JVM servers. Identify each of the JVM servers and explain their importance in processing. Describe the grid configuration file responsible for JVM starts and behaviors. Describe how to administer this file from within the current GridUI. Define the uses of configuration bindings.

Topics Lawson Grid overview

Lawson Grid for Landmark Grid concepts

Lawson grid node types and application modules Grid profiles

Grid administration tools Grid management pages Landmark management pages Configuration manager

Monitoring Landmark using the Lawson Grid Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

44 Lesson 4: Landmark servers © 2014 Infor Education

Lawson Grid overview


Infor Landmark Utilities Reference Guide

Landmark is a collection of servers. Seven JVMs (Java Virtual Machines) provide the Landmark functionality. They process business logic requests, authenticate and authorize, interpret Lawson Pattern Language (LPL), access database tables, manage process flows and background processing, call S3 and M3, display help pages, and send email.

Landmark servers (JVMs) run inside a Java application called the "Grid." Landmark is a library of JVMs managed by the Grid.

Lawson Grid for Landmark

The Lawson Grid is an application server that you install separately from Landmark and within which several Landmark components run.

The Lawson Grid contains several standard parts:

Host

A host is a server machine that is participating in a grid. The host may be a physical or a virtual machine.

Grid agent

The grid agent is a service-like application that the grid uses to start all nodes that are configured to run on the host. Each host needs a grid agent for each grid it is a member of.

Node

A node is a JVM that is registered as being part of a grid where grid applications are running. The Lawson Grid for Landmark typically has several nodes running different Landmark component applications. All nodes run on the grid host.

Registry

The registry is a special type of node that is needed when new nodes are started. A grid has exactly one registry.

Router

A router acts as a well-defined entry point that client applications can connect to. A router is configured to listen for client requests on a given network interface and port number. Normally, the selected port number has to be made accessible through firewalls, when applicable, since it must be reachable from clients. The default name for the grid router for Landmark is: Landmark - YourLandmarkEnvName.

Administrative router

A special router used for administrative purposes.

Grid concepts

Node types

A node type defines what to run in a specific node. Each node is of exactly one node type. More precisely, the node type defines what application to run in nodes of this type and may also define default values for properties (for example, heap size). Node types are defined by the application developer.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Bindings

A binding defines where and how to run nodes of a specific node type. It can be seen as an association between a node type and a set of hosts. In order to start a specific node type on a particular host, a binding that associates the node type with the host is needed. Properties needed by the node or the application running in the node may be defined per binding.

Bindings are defined when applications are installed and/or by a grid administrator at runtime.

Applications

A grid application is a logical collection of one or more application modules grouped into one or more node type definitions that execute in one or more nodes. An application may be installed multiple times. It is then said to have more than one application instance, each of which may be running in one or more nodes. Applications for the grid are packaged in gar files. A gar file is a type of zip file that can be installed in a grid. It contains Java class files (jar files) and any other resources that the application may need.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lawson grid node types and application modules Infor delivers for the Lawson Landmark framework a set of application modules and node types. Each node type represents a collection of one or more application modules. Depending on the grid profile option you chose during Landmark installation, you will have one of several sets of bindings that define the currently used node types for the grid host, and thus indicate how many nodes to start with which application modules.

All grid configurations for Landmark must include the following nodes to be running:

ManageLandmark

This node provides overall coordination of multiple running grid nodes and is also an interface point between Landmark-supplied commands and the grid. Examples of Landmark commands that execute partially or in full via ManageLandmark include startlaw, stoplaw, adminlaw, and managegrid.

Lads

This provides coordination and synchronization services for database structure change management as well as a point from which a client copy of the Infor Rich Client can be installed onto a client machine.

GLoader

Provides a download service for the Lawson Rich Client, whether installed onto a client machine, or executed in applet mode in a web browser.

Lase

This hosts the Landmark security server process providing security authentication and authorization services.

A Landmark application router node

In addition to these nodes, a Landmark grid will have nodes for the grid registry, the grid administrative router, and the grid agent. Your system will then have more nodes based on the profile specified when you installed Landmark. Over time, you may also modify the binding configuration and thus your system will contain perhaps different nodes, a different number of nodes, and different properties for the nodes.

Grid profiles

The following tables describe four different grid profiles:

Small Grid Profile Medium Grid Profile Large Grid Profile Procurement Grid Profile

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Small grid profile

Binding name Node type Application module Description

LmfkInteractiveS LmrkInteractiveExecutor BLExecutor General business logic execution support

LmrkBLDoc LmrkBLDoc BatchExecutor Document

Business logic execution support for general usage as well as list retrieval and background set action processing. This also includes report document creation support.

LmrkDeferred LmrkDeferred AsyncShared LPA

Background processing scheduler, process automation, and embedded analytics support processing.

GLoader GLoader GlawLaunch Handles the downloading of the Infor Rich Client.

Medium grid profile

Binding name Node ype Application module Description

LmrkInteractiveM LmfkInteractiveExecutor BLExecutor General business logic execution support, but defined with two LmrkInteractiveM nodes starting from the same binding.

LmrkDeferred AsyncShared

LPA

Background processing scheduler and process automation engine.

GLoader GlawLaunch Handles the downloading of the Infor Rich Client.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Large grid profile

Binding name Node type Application module Description

LmrkInteractiveL/ LmrkInteractiveExecutor BLExecutor General business logic execution support with maximum heap size of 4GB, and defined with two LmrkInteractiveL nodes starting from the same binding.

LmrkListBatch/ LmrkListBatchExecutor BatchExecutor Business logic execution support for list retrieval and background set action processing with maximum heap size of 4GB.

LmrkDocument/ LmrkDocument/ Document Report document creation services

LPA LPA LPA Process automation engine

Async Async AsyncStandalone Background processing scheduler


Procurement grid profile

This profile is useful if you have a large data volume, such as a high number of order lines being created in your Infor Lawson Supply Chain Management Landmark application and sent to Lawson System Foundation. Be sure you have sufficient system resources for the heap sizes used in this profile.

Binding name/Node type Application module

Description

LmrkInteractiveL/LmrkInteractiveExecutor BLExecutor General business logic execution support with maximum heap size of 6GB, and defined with two LmrkInteractiveL nodes starting from the same binding.

LmrkListBatch/LmrkListBatchExecutor BatchExecutor Business logic execution support for list retrieval and background set action processing with maximum heap size of 8GB.

LmrkDocument/LmrkDocument Document Report document creation services

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Binding name/Node type Application module

Description

LPA/LPA LPA Process automation engine

Async/Async AsyncStandalone Background processing scheduler


Additional bindings

There are two additional binding definitions created for all configuration profiles. These are LmrkProfiler and TraceLogger. They are configured to be available, but not by default started and can be manually started if needed.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Grid administration tools The Lawson Grid provides several tools for administrators to use to work with a grid.

Grid Management pages

When you are running grid applications in a grid, it is important to monitor the state of both the applications and the grid itself. This monitoring enables you to see if an application is having problems that must be addressed or if the grid itself has problems. Typical things to monitor are errors or warnings in the log files. Also, making sure that applications are configured with sufficient memory is very important.

Monitoring of both the grid and its applications is done from the Grid Management pages. Of the many Grid Management pages, those that are particularly useful for monitoring the grid are described below.

The Topology Overview page

The Topology Overview page is the initial Grid Management page that you see. It shows a logical view of the hosts running in the grid and all nodes running on them. The page is intended to give information on all individual runtime artifacts: grid agents, the grid registry, grid routers, and application nodes. Technically, each runtime artifact, except hosts, corresponds to a JVM.

The top of the page above displays:

The name of this instance of the Lawson Grid A stop button that lets you stop the grid or applications in the grid A link to the status page A link to the logging page A link to pages showing more advanced details of the grid A link to a page with application focus (in contrast to the runtime artifact focus of this page)

For each runtime artifact, the page displays the following: Column Description Comment Type The type of runtime entity

displayed on a row, for example: host, grid agent, registry, router, or node.

For hosts, this column also includes a start button that allows you to start nodes (bindings) on that particular host.

Name The name of the runtime entity. For nodes, this is the name of the binding used to start the node.

Status The general status of the entity. Normally this should be OK, but it may also be OFFLINE, or STOPPING.

When a node is off-line, it will take no new requests while letting already processing requests finish.

Stop node A stop button for all entities except hosts and grid agents

This is useful when an individual application node needs to be shut down, for example, because it is in an error state.

ID A unique ID for each runtime artifact.

The ID consists of address, port, and process ID.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Column Description Comment Log Link that displays the log file

belonging to this runtime artifact.

This is the default place to look for information if a node is showing signs of having problems.

Log Status Number of errors and warning in the log.

View the log for details. If errors or warnings are indicated, the cause should be investigated. When the problems have been taken care of or they have been deemed unimportant or irrelevant, it is possible, and recommended, to reset the loggers using the “Reset Loggers” button at the top of the page. This will reset the error and warning counts to zero so that it is easier to see if new errors appear. It is only the count that is reset. No information is removed from the log files.

Up Time How long this runtime artifact has been running (time since last started).

A short up time could indicate that a node has been automatically restarted due to some problem. Obviously, the short up time could also have a natural explanation.

CPU% Approximate CPU usage. Different applications use the CPU in different ways. What is normal depends on the application. This information can indicate if and application does not behave as it usually does.

Heap Usage Memory usage of the runtime artifact (JVM).

Typically the application should not be short of memory in order to perform well (there are exceptions).

You can expand hosts so that more information is displayed. To do so, click the small plus icon to the far left of each host row in the list or click the Expand All button. When expanded, routers will list information about external addresses and ports used. Nodes will list individual application modules.

At the bottom of the page are links to all applications. If the applications provide management pages of their own, a link to them is also displayed. These links are useful to get more information about a particular application.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


The Status page

This Status page is accessed from a Status link at the top of the Topology Overview page.

The Status page is intended to give a condensed view of the status of the grid itself and of each application. The page is constructed so that it only show problems if they exist. This means that the less information that is shown the better it is. Once an application has some form of problem, this will be indicated on this page and the actual problem will have to be investigated using the other management pages. The application names and problems that are displayed often form a link to a page that is relevant to the problem at hand.

The nature of this page makes it suitable when you want a high level view of how the grid and its applications are performing.

The Applications page

The Applications page is accessed from an Applications link at the top of the Topology Overview page.

This page displays the same information as the Topology Overview page but the information is rearranged with a focus on applications. Normally, an overview of each application is listed. If a particular application is selected, that application is moved to the top of the page and more information about that application is displayed. The detailed information is essentially the same as in the topology overview but only the runtime artifacts that are related to the application are displayed.

This page also provides convenient ways to access the configuration of the applications as well as starting, stopping, and managing the off-line state of the applications.

Landmark Management pages

Landmark includes a set of application management pages tailored to the administration and configuration needs of Landmark applications. Some of the tasks that you can accomplish through the Landmark application management pages can also be performed through the grid management pages. However, the Landmark Management pages provide a central location for working with Landmark.

There are four Landmark Management pages:

Environment Async BLExecutor Common Services

Demo: Access the Landmark Management pages

Your instructor will demonstrate how to access the Landmark Management pages.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo steps

1. Double-click the Grid for Landmark on the desktop. The Grid opens to the Topology page. Clicking the house icon brings you back to this page.

2. Click the Landmark application link at the bottom of the page. The link will have the name "Landmark-yourLandmarkEnvironmentName". For example: Landmark – LMKENV.

3. Click back to the Topology link from the Application page.

4. Click the Management Pages link next to the Landmark – LMKENV. The Environment page displays.

Configuration Manager

The Configuration Manager is used to change the runtime aspects of a grid. This includes configuration of installed grid applications and also configuration of the grid itself. The changes made here are kept persistent in the grid configuration area and will survive a restart of the grid and the nodes in it.

Note: Running nodes are not affected by changes made in the Configuration Manager until they are restarted.

The first page of the Configuration Manager consists of links that let you configure different aspects of the grid. These links are described on the following pages.

Application

The Application page lists all installed grid applications and provides basic information about them.

Applications can be configured for one of the following properties:

Application properties Bindings Connection dispatchers Context roots

To edit, you would do this from the Application configuration page where it will also display information about the deployed status of the application.

Application properties:

Column Description

Property The property title if defined (the property name otherwise).

Value The grid-wide value of the property if defined.

Unit The unit of the property, for example: seconds or MB.

Type The type of the property, for example: Integer or String.

Description A description of the property.

Name The property name, which may be different from the title shown in the Property column.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Grid property

When editing a property you will be shown a matrix that lets you define and override the value for this property in different contexts.

Routers page

Defined routers are listed.

Column Description

Name The name of the router. Running Indicator if the router is running. A green bullet means that the router is running. Host The host that the router is configured to run on. Port The port the router is listening on. External Address

Optional external address (IP number). If undefined, the router listens on the same address as the grid agent is using on this host. If the host has several network interfaces, it is possible to select a different one here.

Http Port The HTTP port of the router if defined. The HTTP port serves web applications and web services.

Https Port The HTTPS port of the router if defined. The HTTPS port serves web applications and web services.

Dispatcher A list of connection dispatchers exposed by this router (if any). Remove button

Removes this router.

Context root mappings

Grid applications may expose web applications and web services via an HTTP or HTTPS port in one of the routers. In order to distinguish between web applications and web services provided by different applications, each web application and web service needs to be given a context root that will be part of the address used by a client when connecting.

It is possible to configure context roots in this page, but it is better to do so from the application configuration page. Consult the documentation of each application.

For the Landmark application this is configured automatically and SHOULD NOT be changed or the integrity of the system might be impaired.

Bindings

All bindings in the configuration are listed on the page.

Column Description

Name Binding name.

Node Type The node type that the binding is using when starting a node.

Min The minimum number of nodes (started with this binding) that are allowed. If the number of running nodes is below this value, the system will automatically start new nodes in order to meet this minimum.

Initial How many nodes to start at system start (Min < = Initial < = Max).

Actual The actual number of running nodes that were started using this binding.

Max The maximum number of nodes allowed (started with this binding).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Column Description

Hosts A set of hosts that this binding may use. This binding may only be used to start nodes on this set of hosts.

Remove button Removes this binding.

Note: Bindings to application-defined node types are best configured on the configuration page of each application even though it is possible to do so here also.

Session providers

This section of the Configuration Manager displays basic information about configuring a session provider. The installation of the Landmark application into the grid will automatically configure the provider LmrkProvider, together with appropriate user and role mappings to enable the Lawson user to have administration access to the grid. This provider delegates the actual processing of authentication to the Lawson Security Server executing within the Landmark grid application.

User and role mappings

You can configure role mappings belonging to a particular application on a configuration manager page belonging to that application (a page with an application centric focus) or you may configure role mappings on a global page enabling you to operate on all application defined roles including the ones defined by the Lawson Grid itself (grid-admin, grid-poweruser and grid-user). Which is most convenient for you depends on the situation.

For the Landmark application you should configure appropriate role mappings for any user other than the Lawson user that should have administration access to the grid .

All entities

This page displays a view of what is currently running and where it is running in the grid. A green bullet in one of the host columns means that at least one node of the binding, on this row, is running on that host. A white bullet means that it is possible to start this binding on that host but none is started at present.

Advanced configuration

The following advanced configuration options are available:

Configuration files

Display and compare the topology.xml and the runtime.xml files on all hosts. This option could be useful if there is a problem in the grid, as a way of making sure that the same configuration applies to all hosts (which it should).

Property overrides

Display a view of all property overrides grouped by override context. This is a very complex view and is only included for support reasons.

Defined ports

Display a list of all ports that this grid defines and on which network interface they are bound.

Linked resources

Not used in a customer scenario.

Certificates

Not applicable to a grid for Landmark.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Access the Configuration Manager

Your instructor will demonstrate how to access pages in the Configuration Manager.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps

1. From either the Grid Management page or from the Environment page from the previous demo, click the cog wheel icon in the upper right hand corner of the screen to launch the Configuration Manager. The Configuration Manager page displays links you can use to configure different aspects of the grid.

2. Click the Grid Properties link to see a matrix view of the Lawson Grid.

Configuration bindings

Bindings are needed in order to start applications. A binding is a mapping from a node type, which the application defines, to a set of hosts. So, in order to start an application on a particular host, at least one binding has to exist that associates the application (and one of its node types) with that host.

The bindings are also used to govern the minimum and maximum number of application node instances that should be allowed. This means that if a binding is configured with a minimum of two, the grid will always try to make sure that at least two application node instances referenced by that binding are running in the grid. If the number of nodes becomes fewer than the configured value, the grid will automatically start nodes until the minimum is met.

The maximum works in the same but reverse way. It is impossible to start more application node instances using this binding than the configured maximum.

It is also possible to configure the initial number of application nodes you want for a binding. If configured, the initial value will be considered when the application starts. In fact, starting applications is just a matter of honoring the initial value for all the bindings that belong to the application.

Also, as described in Grid properties, the bindings are one of the different contexts that you may use when defining property overrides. This enables you to define different property values for your application depending on which binding is used to do the launch. Configuring bindings is done from the Configuration Manager.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Edit bindings

Your instructor will demonstrate how to edit a binding via the Configuration Manager.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps

1. Navigate back to the Configuration Manager main page.

2. Click the Applications link.

3. Select the application you want to configure bindings for from the list.

4. Click one of the bindings in the list on the page to edit existing bindings.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Monitoring Landmark using the Lawson Grid The Lawson Grid provides many sources of information about the configuration and runtime status of a grid and the applications running within the grid. These include:

Log files

Log files are available for each node.

Counters

Counters are available for each grid node as well as a counter history.

Configuration history

You can review a history of changes to the grid configuration so that you can, for example, identify changes that caused a problem or revert to a previous configuration.

Heap dumps and thread dumps

You can view heap dumps and thread dumps for individual grid nodes.

Grid Status report

The Grid Status report is a generated report that shows the overall status of the grid, and also includes log files, configuration files, counter history, and thread dumps.

What is the grid.jvm.maxHeapMB setting for the nodeType=LmrkInteractiveExecutor?

In the topology.xml file, what is the registry port number?

Configuring memory given to applications

The next demo explains the procedure to set a global application value for the Max Heap property. The Max Heap property as defined in the grid configuration controls the maximum memory amount that can be allotted at node start to an application in a particular node. This property is one of the most commonly configured properties. It enables you to accomplish the important task of ensuring that application nodes have sufficient amounts of memory.

As with any grid property, it is possible to configure the Max Heap property differently for different contexts. One example could be that you want an application node to have more memory if it is running on a particular host. Sometimes applications define several node types and you may want to configure the Max Heap property differently for different node types. The same goes for bindings.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Configure application memory

Your instructor will demonstrate how to configure application memory.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps

1. Navigate back to the Configuration Manager main page.

2. Click the Applications link.

3. Click the Landmark-LMKENV application.

4. Click the Edit Properties link.

5. Locate the Max Heap property in the Grid Defined Properties section. The section is below the application defined properties. You may need to expand it to see the Max Heap property.

6. Click the Value link in the Value column to edit the Max Heap for the application you would like to change the value.

Note: We will not make any changes to the Max Heap value for this demonstration.

Log files and reports

Applications create log entries using one or more named loggers. The TraceLogger binding is not enabled by default but may be enabled in order to get more fine-grained information. This may be useful in a situation where you are trying to find out the cause of a problem.

Why change log levels?

Changing the log level for an application is a way of changing the amount and type of information that is added to the log files. The most common reason to change the log level is that you are having some problem with an application and you want to get more information in the logs in order to find the cause. In this case, you typically enable the Trace and or the Debug level.

Applications may log information under different categories referred to as levels.

ERROR - Log entries in this level are marked as errors in the management pages. WARN - Warnings are less critical than errors but should still be investigated. INFO and NOTE - Represent general information and information that is slightly more noteworthy

than general information but still not a warning. DEBUG and TRACE - This may be useful in a situation where you are trying to find out the cause

of a problem.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Configure the TraceLogger binding

Your instructor will demonstrate how to configure the TraceLogger binding.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 4.1: Configure the TraceLogger binding

In this exercise, you will configure the TraceLogger binding.

Exercise steps

1. Double-click the Grid for Landmark on the desktop.

2. Click the cog wheels icon in the top right corner to launch the Configuration Manager. (If you’ve been following along with the previous demos, you will already have the Configuration Manager open).

3. Click Applications.

4. Click Landmark-LMENV.

5. Select the TraceLogger binding name.

6. Type 1 in the initial binding field. This will include the binding during an initialization when running startlaw.

7. Click Save Binding.

8. Click the Save button and then Save again to save your changes.

9. Double-click the Grid for Landmark on the desktop. Notice the TraceLogger has been started.

10. Click the cog wheels icon in the top right corner to launch the Configuration Manager.



13. Select the TraceLogger binding name.

14. Type 0 in the initial binding field.

15. Click Save Binding.

16. Click the Save button and then Save again to save your changes.

17. Go to the Landmark Command Prompt on the desktop.

18. Type managegrid stop TraceLogger.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Grid status

Grid can be checked by:

managegrid list command Log files Grid for Landmark shortcut Windows services

Command line

Command line: managegrid list

Each time a grid module starts, a new log is created. It is a good idea to clean up this directory periodically. C:\LMKENV\LMKENV_grid\log.

To view a fresh batch of grid log files, issue a stoplaw command and archive the current contents of the grid log directory. When the grid starts up with issuing a startlaw it will create a new batch of log files with names that incorporate newly created JVM process IDs.

Note: Grid is now a service that can be managed in your Windows > Services Console as a GridAgent listing.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



True or false? Each time a grid module starts, a new log is created.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Define the purpose of the Grid Management page.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Which of the following is an example of a grid node type?

a) Application page b) ManageLandmark c) Max Heap d) Grid agent

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 5: Landmark applications: End-user support Estimated time

2.5 hours

Learning objectives


Define Landmark Pattern Language (LPL). Describe what a product line and multiple product lines consist of. Describe the Source Code Repository (Subversion/SVN). Define how Infor Spreadsheet Designer (ISD) can be used to extract data to and from and

between Landmark Environments taking into account decryption and encryption.

Topics Landmark applications overview

Landmark applications What is LPL? Configuration Console

What is a product line? Multiple product lines in production systems Multiple product lines in development/test systems

Source code management: Subversion Landmark application requests Infor Spreadsheet Designer for Microsoft Excel Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

64 Lesson 5: Landmark applications: End-user support © 2014 Infor Education

Landmark applications overview This section introduces you to Landmark as a technology.

It is important for you to understand what Landmark is so that you know, for example, why you can usually skip incremental updates, why you should not create direct access to the database, and why you cannot significantly change the user interface.

Topics in this section include:

How Landmark applications are created What Landmark applications look like Landmark's components and architecture

Landmark applications

Landmark is Lawson technology to develop and run industrial-strength business applications. Landmark applications include:

Enterprise Financial Management

Cash and Treasury Management (CTM)

Infor Lawson Cash and Treasury Management (CTM) helps organizations’ cash and treasury departments address the challenges of manual processes, disparate systems, and redundancy. It meets these challenges by driving automation, increasing visibility, and improving collaboration, while helping to analyze enterprise-wide cash requirements, maximize liquidity, and optimize the use of cash resources.

AP Invoice Automation

Infor Lawson AP Invoice Automation (APIA) aims to simplify invoice entry, review and approval, reduce costs for processing invoices, and provide easy access to complete information about invoices.

Travel Expense Management

Lawson Travel Expense Management provides a centralized system for reporting, processing, approving, reimbursing and analyzing employee expenses.

Student Activity System

Lawson Student Activity System provides a centralized system for collecting, tracking, processing, reporting and analyzing student fees and activity funds.

Supply Chain Management

Strategic Sourcing Strategic Sourcing is used to set up, maintain, and analyze complex bidding events. In addition, Strategic Sourcing provides a robust system for requesting bids and quotes, awarding events, and analyzing spending patterns and supplier use.

Contract Management

Contract Management is the process of creating and managing a supplier contract that is based on items or services purchased over the life of the contract.

Supplier Order Management

Supplier Order Management is a way for your organization to collaborate with your suppliers. Supplier Order Management is closely coupled with other Lawson applications, including S3 Enterprise Applications such as Inventory Control (IC), Accounts Payable (AP) and Purchase Order (PO).

Recall Management

Lawson Recall Management application helps you manage the recalls, safety notices, and device corrections your organization receives.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Global Human Resources Management

Infor Talent Management

The Infor Talent Management is an integrated suite of products that provides the tools to manage human resources from recruiting to hiring, salary awarding, and performance assessment.

Talent Acquisition

This application manages the external and internal recruitment process from the time a requisition for a position is created to the point when a candidate is hired and processed through onboarding. It includes defining, managing, and approving staffing requisitions, posting job openings to multiple job boards, matching candidates to jobs, coordinating the assessment, interviewing, the hiring process, and onboarding new hires.

Compensation Management

This application provides a comprehensive solution for managing salary planning and administration. It allows customers to align compensation programs with corporate objectives. Compensation Management also supports variable pay, complex salary structures, and rate progression rules, and it offers employees visibility into their total rewards.

Goal Management

This application is closely integrated with Performance Management, Compensation Management, and Learning and Development. It is used to set up goal components and to define strategic (organizational) goals for organization units that resource goals can be aligned to. Goals can be incorporated in resource performance reviews and associated with development activities.

Performance Management

This application combines performance assessment, data collection, and ongoing goal management. It is used for workforce planning, succession management, expanded learning and development, and total reward management.

Learning and Development

This optional application manages the development activities for the resources in an organization. It provides automated tools to align organization and personal development goals with development activities; to prepare and implement the organizations' development plans and budgets; to maintain centralized information on development activity providers, contracts, and instructors; to build a catalog of available development activity sessions; and to manage session registrations.

Succession Management

Succession Management is an application in Lawson Talent Management Suite that shares a common competency and skill infrastructure with other applications with the goal of assisting organizations in the management of talent.

Position Budget Management

Position Budget Management is an optional feature that let you set up and monitor budgets for your work force, and enforce budget controls when personnel actions are initiated in the system.

Employee Relations

Employee Relations tracks an organization's interactions with employees, so that these interactions may be handled in a consistent and fair manner. Organizations can configure Employee Relations to develop rules, regulations, standards, guidelines, or processes around coaching, discipline, and grievances.

Health and Safety Management

The Health and Safety Management application – Occupational Health System – allows you to create and track job or occupational health-related requirements.

Safety Management

This application provides process-driven solutions for gathering incident data, tracking incident-related follow-ups, performing notifications, incident reporting, and incident data analysis.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Pattern Language (LPL)

LPL is the source code language of Landmark. It is a proprietary specification language developed by Lawson Software that applies programmatic patterns to business applications. It describes the following application components:

Logical representation of a database structure Data and business object life cycles Business transaction processing logic User interactions with data and objects

For business patterns to perform correctly, additional information and definitions are required. Within the LPL system, these are found in the source components that comprise and define the business objects. As a pattern is further developed, it can be refined to provide a highly specialized and constrained definition.

There are two commands to transform LPL into a Landmark application:

1. buildprod – Packages and timestamps the LPL.

2. dbupgrade – Extracts the data, builds the tables, and loads the data. Also processes database changes and data transformations specified for the framework tables that are common to the GEN product line and the application product lines.


The Configuration Console is a feature in Infor Rich Client that allows changes to be made, and in some cases distributed to more than one user, without modifying LPL source code. Changes are made in various editors and saved to a database as LPL.

When using Configuration Console, you never have to make code modifications—the base Landmark Programming Language of an application is never changed. This allows Lawson to continue to deliver updates, and the customer must determine how to resolve any conflicts with their configurations.

The Configuration Console is accessible within the Infor Rich Client to those that have the Configuration Console role. The Console enables administrators to make several types of changes that affect Landmark users.

Note: We will cover Configuration Console in more detail in Lesson 12.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


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 Landmark installation process.

A product line includes:

Application programs and data tables The product line dictionary One or more data areas built on the product line

You may have multiple product lines, depending on your business needs. For example, you might have one product line for testing and another product line with the same applications that is used for production. A product line generally has a unique name that identifies the version of the applications it contains.

An RDBMS database is a collection of information organized into interrelated tables of data and specifications about that data.

Multiple product lines in a production system

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 application. 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 a separate database. All of the data areas can be in the same database instance, including the data areas for another system such as a Lawson System Foundation system. In fact, if you have a direct data access requirement between Landmark and an Lawson System Foundation system (such as would be the case if you had the Procurement application and the Landmark Supply Chain Management applications), the data areas for the Lawson System Foundation system applications and the Landmark Supply Chain Management applications must be in the same database instance.

Example product line configuration for a production system

Landmark Environment Lawson Talent Management Suite S3 Supply Chain Management Applications

gen product line prodltm product line prodproc product line

S3 Lawson System Foundation S3 Applications S3 Supply Chain Management Applications

gen product line logan product line application product line

Database instance lmrk_gen lmrk_ltm lmrk_proc lsf_gen lsf_logan lsf_lawapps

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


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 data area, but all data areas can be in the same database instance. If your development and test Landmark system have applications that require direct data access to an Lawson System Foundation system, the data for the product lines or data areas from the test/development 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 data areas for both Landmark and Lawson System Foundation in the same database instance.

Example product line configuration for development/test system

Landmark Environment Lawson Talent Management Suite S3 Supply Chain Management Applications S3 Enterprise Financial Management

Applications Landmark product lines gen devltm testltm devproc testproc devfin tesfin

Data Areas lmrk_gen lmrk_devfin lmrk_testfin lmrk_devproc lmrk_testproc lmrk_devltm lmrk_tesltm lsf_gen lsf_logan lsf_apptest lsf_appdev

S3 Lawson System Foundation S3 Applications

LSF product lines gen logan lawapptest (test application product line)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Source code management: Subversion Even though the source code repository is application-specific, it is a part of the Landmark Environment third-party requirements.

What is Subversion?

Landmark uses the Subversion product as the system’s source code management repository. Subversion can be referred to as the “svn.” Subversion is an open-source version control system. It manages files and directories.

Subversion is used to hold Landmark application source files delivered in each Lawson release and update. Local, client customizations are also maintained in the Subversion repository. The creation of product line instances is done using components in the Subversion repository, and in this context, Subversion can be seen as a secure staging area that separates the receipt of application source files from Lawson and the creation of a customized business solution for the client.

Purpose of application source code management

The purpose of application source code management is to ensure the integrity of the source code and to maintain a historical record of all updates and modifications to the source code. Adhering to Lawson's best practices will help you maintain the integrity of your code branches and will make it easier to troubleshoot issues.

You acquire the Landmark application source through the delivered application package. Each Landmark application package contains cumulative releases through the current release. These packages are an executable .jar file that is received into your system by executing the .jar file. The packages are platform neutral and only a Java Virtual Machine (JVM) of the correct version is required for delivery.

You receive or unpackage the application source into a Subversion version repository. This repository is a source control system that enables you to manage delivered source artifacts and customized code, and allows you to control which code lines to build into product lines. Lawson provides various tools to maintain the released source in the repository, select which product and version to generate and deploy, and perform a number of other administrative and customization activities.

At the heart of the application source code management process is the concept of using multiple product lines, where each may be at a different point of modification or updating. Typically, you will have development, staging, and production product lines. Each of these has a specific purpose and its own process and strategy for being kept up-to-date. With multiple product lines and careful use of the version repository, you will be able to customize Lawson products at the same time that you update your system with Lawson bug fixes and feature enhancements.

The version repository

Lawson requires the use of a Subversion repository to manage the Landmark application source code. The repository may be installed on any Windows server on the same network that the Landmark application servers and any development servers or machines are running on.

You only need one Subversion server to manage application source across all Landmark servers for development, test, stage and production.

The version repository is normally configured with a security policy permitting only a privileged user (lwsnrcpt) to receive product releases, while developers and application managers may have different access policies to the versioned application sources.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


This source control management system keeps track of the following:

The original application source delivered by Lawson Application product changes delivered by Lawson Custom modifications

The delivered source and any developer modifications or customizations are reorganized in the following repository model:

Lawson branch - A Lawson-managed part of the repository into which you receive the delivered source. Source files are automatically committed to this branch as part of the receipt process. Each application package from Lawson contains metadata with information on dependencies, products, releases, and build numbers. You can create a product line and a corresponding product line branch by selecting the product and release you want from the list of those you have received into the repository.

As a customer, you can make no changes to this branch except to receive new releases. Only the lwsnrcpt user can perform the receipt.

Product line branch or branches - The client-managed part of the repository, available to deployment machines and development machines. This type of branch is typically created by selecting the desired product and release from the Lawson branch. Each product line branch may also contain developer modifications that must be merged with future updates of Lawson source code.

"Marks" placed by developers at the tip of a customization branch make the corresponding revision of code available for selection with Lawson commands for the purposes of testing, development, and production deployment.

How you update these branches depends on the purpose of the product line branch. Lawson recommends that only your development branch is updated by Lawson application releases and by any customizations. Other branches are then updated after those application releases and customizations have been reconciled and tested. For example, after you are confident of the functioning of a set of new application releases or customizations in your development branch, you would update your stage branch from a mark on the development branch.

Product line - A product line is created by obtaining the application's source code from the repository. It exists within a Landmark Environment, and provides the collection of files on a local machine from which a runtime application can be built and deployed. If this is a developer's product line, you can customize the source files here and then check them back into the development branch. @

Cop

yrigh

t 201

4 Info

r

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Flow of receiving a new release or critical update into your application


Command line utilities for repository management

Utility Use

createprod The utility creates the basic directory structure of your product line and the necessary files for it to operate. It also creates a customization branch by default, to which any changes to the local product line may be checked in.

updateprod The utility applies changes from the old revision to the new revision, assigns a new revision number, and displays the locations of the changes.

markprod The utility saves the state of a customized product line and makes it available for checkout from the customization development branch using Landmark commands, such as createprod and updateprod.

Svndiff Use this utility to compare two releases, branches, or marks within a Subversion repository. It logs the output to %LAWRKDIR%\svndiff. This output file includes a list of files that have been modified, added, or deleted between the two releases, branches, or marks you are comparing. You can also use this utility to create diff files for the source code files that were modified. To use the svndiff utility, type svndiff at a Landmark Environment command line, and then respond to the prompts. Note: You will want to execute the svndiff command before you update or patch a new version of an application. You will run this command during the Lesson 15 scenario exercise.

listprod This utility displays information for product lines associated with products in the version repository

listproduct This utility is used to view the contents of the Landmark version repository.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Commands to update for Stage, Development, and Production with modified code

Demo: Execute the listprod and listproduct commands to view version repository information for a product line

Your instructor will demonstrate executing the listprod and listproduct commands.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.1: Execute the listprod, listproduct, and svndiff commands to view version repository information for a product line

In this exercise, you will execute the subversion commands: listprod, listproduct, and svndiff to check what release/version of an application you have in the version repository.

Exercise steps


2. Type listprod –a (displays list of the application branch and versions currently installed in your system).

3. Type listproduct –ieb –N -<branchname> -a (displays which branch is associated with what product line).

4. Type svndiff (compares two releases, branches, or marks within a Subversion repository. You will do this command again in Lesson 15 when you apply patches).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark application requests Users initiate action requests as they are performing tasks in a Landmark application. The request is created and parameters are saved that represent the user input, keys to data and other information the request will need to process. In addition, a request is sent to the Lawson Process Server, which then creates a work unit in the Lawson Process Server. The Lawson Process Server uses the work unit to route the action and gather information.

Action requests are set up within a Landmark application in Landmark Pattern Language (LPL). A business class contains the definition of the action request. An action request triggers an action to be taken on the specific business class. Any number of action requests can be created to serve different business needs. In fact, requests can be created for any business class. Requests can include an action reason and effective date for the request. They follow a routing and approval process, indicating who needs to review the request and approve it. The request is sent to the appropriate approvers by the Lawson Process Server.

In the LTM application, an example of an action request is a manager requesting approval to promote an employee (resource). The request is automatically sent to the administrator, who can approve, reject, or return the request to the manager. Another example is an administrator requesting personal leave for an employee (resource). The request is sent to the employee’s manager for approval. If approved, it is then sent to the administrator for final approval.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Action request flow

The figure below shows the process flow for an action request in Landmark.

Flow of action requests

As of dates

The “as of” date feature gives you a way of viewing records. You can view the same record as it was in the past, as it is today, and as it will be in the future. By specifying an “as of” date in the lower right-hand corner of a record, you can view that record as it existed at any point in time.

For example, you want to view a list of jobs that were assigned to a specific HR organization as of a month ago. Access the Jobs form within Global HR Setup and look in the lower-right hand corner of the form. Click the calendar icon and select the date for which you want to view available jobs. If today were August 30, 20XX, you would select a date of July 30, 20XX. The display of jobs changes to reflect those jobs that were available as of July 30, 20XX.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Using effective dates

When you select an effective date, you are telling the application when the change you are making to a record is to go into effect. This lets you actually schedule a change to a record (if the date you select is other than today’s date). In other words, you decide when the change to that record should occur—in the past or in the future. The change itself does not actually happen until the date that you selected is met.

If you made future changes for a record, you must change the date back to the current date. If not, changes to other records are unintentionally delayed.

What happens when an effective action is executed?

An end user enters a future effective date for an action. The effective date gets passed to the back-end and is used in processing the request. All business objects participating in the action will get the following created on their behalf:

A effective log entry with all change deltas An EffectiveDatedEntry Object with a reference to the Business Object and Effective

Entry An EffectiveDatedGroup will be created to group together all the EffectiveDateEntry

objects (All will have the same "audit transaction id")

(Note: The "audit transaction id" is the EffectiveDatedGroup Key)

An AsyncActionRequest will be created and scheduled for midnight on the effective date.

Where do I go to manage the effective requests in the system?

There is a new Effective Dated Request page delivered as part of Landmark. It is in Infor Rich Client, Start > Applications > Async Administrator >Effective Dated Requests.

Effective Dated Requests page

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Viewing the audit log

The audit log for a record lists a history of changes that were made to that record, including:

The period in which the change was made (past, current, or future) The effective date User ID of the person who made the change The action that the user performed What field change was made

You access a record’s audit log by accessing the record and then performing the action View Audit Log or View Full Audit Log.

Demo: Update a resource’s name preference, set the effective date, and perform view audit log

Your instructor will demonstrate updating a resource’s name preference, set the effective date, and perform view audit log.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.2: Update a resource’s name preference, set the as of date, effective date, and perform view audit log

In this exercise, you will update a resource name preference, set the as of date to today and then change the effective date back to yesterday in order to see the change in the audit log. Finally, you will perform the action view audit log to review the log.

Exercise steps

Part 1: Update a resource name preference

1. Go to the Infor Rich Client on the desktop.



4. Click GEN > LTM.

5. Double-click Administrator.

6. Hover over Resources and select Resources.

7. Type Anders in the Last Name field of the Resource Search tab.

8. Click Search.

9. Scroll to search for Anders, Marc, Employee 300033.

10. Right-click Anders, Marc, Employee 300033 and select Update. The Marc Anders Profile page comes up.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


11. Type Marcus in the First Name Given and First Name Preferred fields in the Name section of the At A Glance page.

12. Click Save. You will be prompted to set the As Of Date.

13. Select <today’s date> for an Effective Date from the Calendar selection.

14. Click OK.

15. Close the application and notice that the Resource List has been updated.

Part 2: Set the effective date to yesterday’s date

1. Click the Start menu in Infor Rich Client.

2. Select Set ‘As of Date’.

3. Select <yesterday’s date> for an effective date from the Calendar selection.

4. Click OK.

Notice the resource’s name preferences have changed to the prior name. Also notice the red box at the top of the screen showing the as of date.

Click Start > ‘Clear As of Date’ to return the date to today’s date.

Notice the resource name is back to Marcus Anders.

Part 3: View and print the audit log

1. Right-click Anders, Marcus, Employee 300033 and select View Audit Log.

2. Verify the audit lines.

Demo: Edit the Resource Search form by adding a field

Your instructor will demonstrate editing the Resource Search form by adding a field.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.3: Edit the Resource Search form by adding a field

In this exercise, you will edit the Resource Search form by adding a field.

Exercise steps

To add a field called TotalPayRate to the Resource Search page:

1. Navigate back to the Resource Search form. (From the previous exercise, simply close the View Audit Log screen.)

2. Click the Resources drop-down menu on the Resource Search tab (upper right-hand section of the screen).

3. Select Options > Personalize. The List Editor – Resources form opens.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


4. Click Add Field.

5. Click the select arrow in the Field box and type TotalPayRate.

6. Press Enter.

7. Select TotayPayRate from list of results and click OK.

8. Click OK twice more to return to the Resource Search form.

Notice that the form now displays the TotalPayRate column/field.

9. Select Exit Page Editor. This saves your changes.

Demo: Print and export the Resource Search results

Your instructor will demonstrate printing and exporting the Resource Search results.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.4: Print and export the Resource Search results

In this exercise, you will print the Resource Search results.

Exercise steps

Part 1: Print the Resource Search results report and export to CSV

1. Click the Resources drop-down menu on the Resource Search tab.

2. Select the Search (magnifying glass icon) and filter to all Resources with Last Name A*.

3. Select Options > Print to File while still in the Resource Search form.

4. Select the preferred orientation.

5. Type <the Report file name>.

6. Click Print. The In Progress box will display while it builds the PDF output. The PDF report displays.

Part 2: Export to CSV

1. Close the PDF output and navigate back to the Resource Search form.

2. Select Options > Print Files. The Print File form opens listing the Resource Search report created in PDF.

3. Select the <the Report file name> and click the Resources drop-town menu.

4. Select Options > Export to CSV.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Infor Spreadsheet Designer for Microsoft Excel Spreadsheet Designer for Microsoft® Excel is an Excel add-in for Landmark applications. This is similar conceptually to Lawson add-ins for Microsoft Office for S3 apps.

The end user can download data from Landmark using the Query tool and can update data in Landmark using the Upload tool. Infor Spreadsheet Designer limits the user access by restricting authorization to objects granted with Landmark Security Roles. The user can only query data granted by Business Class access or change data through Business Class access. Therefore, if the user is not allowed access to data or restricted from change actions on data then Infor Spreadsheet Designer will adhere to those same restrictions.

Infor Spreadsheet Designer (ISD) features

Infor Spreadsheet Designer features include:

Define multiple queries or uploads in a single Excel worksheet. Update the entire worksheet or selected ranges of data. Save defined query or upload parameters for future use. Leverage Landmark “Effective Dating” to constrain queries or make pending changes. Application of Landmark Application Security. Use the full functionality of Excel such as pivot tables, conditional styling, formatting, charting, find

and replace, and others with Landmark application data.

Demo: Enable Spreadsheet Designer in the Excel toolbar

Your instructor will demonstrate how to enable Infor Spreadsheet Designer to Excel if disabled by a user.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.5: Enable Infor Spreadsheet Designer

In this exercise, you will enable Infor Spreadsheet Designer.

Exercise steps

1. Select Program > Microsoft Office > Excel 2010.

2. Select File > Options > Addins.

3. Search for Infor Spreadsheet Designer. If you don’t see ISD, it means it has been disabled.

To re-enable Infor Spreadsheet Designer:

1. Select Disabled Items in the Manage field.

2. Click Go.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


3. Select Infor Spreadsheet Designer and then select the Enable check box.

4. Click Close and then click OK. Infor Spreadsheet Designer is re-enabled.

Note: If the Infor tab does not appear, restart Excel.

Demo: Define a query

Your instructor will demonstrate how an end user would access Landmark data via the Query tool in Microsoft Excel. The demo will also highlight how a system admin can view the audit log.

______________________________________________________________________ ______________________________________________________________________

Exercise 5.6: Define a query in Microsoft Excel

In this exercise, you will define a query.

Exercise steps

1. Select Program > Microsoft Office > Excel 2010.

2. Click Infor in the Excel tool bar.

3. Click Insert Query.

4. Type lawson in the User field.


6. Select ltm in the Data Area.

7. Select Employee from the Business Class list. (Hint: type Employee and it will find from the list.)

8. Select HR Organization > Employee > Name.GivenName > Name.FamilyName > Start Date.

9. Select Insert of the Query.

10. Right-click HR Organization.

11. Select Add to Filter. The filter now shows HR Organization.

12. Right-click Employee.

13. Select Add to Filter. The filter now shows Employee.

14. Type 3000 in the Set Value field for HR Organization.

15. Type 30033 in the Set Value field for Employee.

16. Click Refresh (next to Insert Query). The query results will populate.

17. Verify Employee 300033 was retrieved and notice Marcus.

18. Execute the query with a backwards Effective Date and notice Employee 300033 is back to Marc.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Troubleshooting connection issues with Spreadsheet Designer

Users need to know the following pieces of information which are not available in the Lawson Help file.

How to locate the Infor Spreadsheet Designer deployment for download to their pc. How to log on to the Infor Spreadsheet Designer. Users need the fully-qualified server name and

web port number. Location of the Infor tab which houses the Infor Spreadsheet Designer menu options. How to locate Infor Spreadsheet Designer end-user help. From the Infor globe logo on the top-left

of the worksheet, click the arrow (under "Infor") and then click Help.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Define the purpose of the version repository.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

What is the advantage of having multiple product lines?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

List the two commands that transform LPL into a Landmark application.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 6: Landmark database Estimated time

2 hours

Learning objectives


Identify the connection and configuration to RDBMS. Define Landmark Database Service (LADS). List db.cfg files and <dataarea>.xml files. Describe the purpose and benefits of data dictionaries, data areas, and database utilities. Provide examples of how database utilities are used.

Topics Landmark database overview Landmark Database Service (lads) Landmark data structure Landmark data dictionary Landmark database utilities Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

84 Lesson 6: Landmark database © 2014 Infor Education

Landmark database overview

Infor Landmark Technology Data Access Guide using Oracle; Microsoft SQL Server or IBM DB2 Infor Landmark User Setup and Security Guide

How are Landmark database tables created?

After creating the database in Oracle and specifying the database configuration in the %LASRCDIR%\dict\<dataarea>.xml file, the Landmark Environment and application installation program will create the required tables in the Oracle database. The schema name provides the logical grouping of tables within the Oracle database.

What is the Landmark database interface configuration file?

The database interface configuration file is used to specify how Landmark accesses the database. It includes values such as the database server, name, port, and login information. The file is initially populated with the values you entered when you installed Landmark or your Landmark application.

You can specify more than one database configuration in the db.cfg file by adding a new section for each database. A section name can only exist once per product line.

The file location is: %LARUNDIR%\<DATAAREA>\db.cfg

Changes in the database interface configuration file take effect without stopping or starting the database.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Database Service The Landmark Database Service (lads) manages resource locks for various resources in the Landmark Environment. The main resource is the Landmark data area lock.

When the Landmark system or an application needs to access the database, the process acquires a lock on the resource from the LADS service. For normal runtime interaction this is a shared lock on the resource. In this scenario, many users with shared locks can access the same resource at the same time.

Some Landmark utilities, such as dbupgrade or dbcopy, need exclusive access to the data area. If there are any shared locks on the data area, then the request for the exclusive lock will be denied. Once all shared locks are released then the exclusive lock will be granted. Once the utility has an exclusive lock on the resource, any future shared lock requests will be denied.

In the event that a process is unable to communicate with the lads service, e.g. due to network issues, then all current locks held by that process are invalidated because we no longer can rely on the lock validity. In this scenario it is required to restart the process that is attempting to acquire an lads resource lock.

Beginning in Landmark technology 10.1, currently held locks are invalidated but new locks will be allowed in which case the process does not need to be restarted. Additionally if the lads that is managing the locks is stopped while active locks are held, a restart of lads will refuse new lock attempts for a short period of time (2 minutes) to give processes holding locks managed by the previous instance of lads time to be notified that their locks have been invalidated. If there was an exclusive lock held when the lads instance is stopped, then the program that acquired the exclusive lock (e.g. dbupgrade) must be used to release the lock in the new instance of lads.

Lads also provides sequence values to auto-sequenced business classes that implement auto-sequence with minimal contention. When appropriate we can eliminate database lock contention on business classes that implement auto sequence by handling the locks outside of the RDBMS. In this case the lads service provides the lock control and hands out new sequence values.

Runtime administration of the Landmark Database Service is available through the ladsadmin utility and the Grid Management UI.

The database server’s error messages are recorded in the %LALOGDIR%\ladb.log file and the grid log for the lads grid node.

Demo: Using the Landmark command line to see the status of the Landmark Database Service

Your instructor will demonstrate how to see the status of lads using the command line.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 6.1: Use the Landmark command line to see the status of the Lawson Database Service

In this exercise, you will use the Landmark command line to see the status of the Landmark Database Service (lads).

Exercise steps


2. Type ladsadmin status at the command line. This will allow you to see state of lads.

3. Type ladsadmin resources at the command line. This will allow you to see current usage.

4. Access Grid Manager and tie back the Java processes that are currently being accessed.

Note: This only shows grid jvm processes; any command line jvms like ‘dbexport’ would not be visible to the Grid Manager.

5. Navigate to the Global Management Pages under the Lads tab. Resources are shown here as well and access to ladb.log is available.

Note: Under the Lads Manager section of the Application Properties in the Grid Management UI, we can configure the Lads connection timeout. This determines how long a process will wait for the lads resource lock request to complete.

Demo: Use the Landmark command line to see the status of the Landmark Auto Sequence Manager

Your instructor will demonstrate how to view the status of Landmark Auto Sequence Manager using the command line.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 6.2: Use the Landmark command line to see the status of the Landmark Auto Sequence Manager

In this exercise, you will use the Landmark command line to see the status of the Landmark Auto Sequence Manager.

Exercise steps


2. Type ladsadmin autosequence stats <DataArea> at the command line. Show/clear statistics gathered by the Auto Sequence Manager.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


3. Type ladsadmin autosequence clearstats <DataArea> at the command line. Clear statistics gathered by the Auto Sequence Manager

Note: Landmark Auto Sequence Manager can also be disabled through a Grid Property found under the Auto Sequence Manager section of the Application Properties in the Grid Management UI. The ladsadmin autosequence disable/enable can be executed at Command Window. In addition, ladsadmin autosequence reset <DataArea> can be run to reset values.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark data structure

Landmark Pattern Language (LPL) files are the logical representation of database structure and constraints, plus business logic. LPL files describe a collection of business classes, business tasks, modules, fields, and other miscellaneous files. A runtime dictionary is generated from these files that includes the structural metadata for the persistent data portion of the business classes. Business Class, Module, Key Field, and Field files built using Landmark Pattern Language (LPL) encapsulate all application business logic.

To view the data dictionary components (for example, files, elements, or indexes) you would run viewdict <prodline>.

What is a data area?

A data area corresponds to a pool of physical data stored in a database. When you install an application and create an application product line, a data area (with the same name as the product line) is created for the product line. The data area includes only the data structure. Generally, you have only one data area within a product line in production environments.

Parameters for each data area are stored in the following location: %LASRCDIR%\dict\dataArea.xml and can be viewed by running displayda <prodline>.

Landmark data structure

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark data dictionary

The data dictionary is a binary file that captures the structure of the database, including tables, columns (representing fields) on the tables, indexes on the tables, and relationships between tables. The data dictionary files are binary-optimized forms of the product line definitions defined in LPL files.

File location: %LARUNDIR%\dict\<dataarea>.dict

The database dictionary is the source of the timestamp used to identify the data area directory (%LARUNDIR%\<dataarea>.timestamp).

How is the Landmark dictionary built?

Landmark LPL source defines the structure of the data, and the data area deployment file %LASRCDIR%\<dataarea>.xml which defines initial data area and database parameters. These files are used by the Build Product Line utility (buildprod) to create or update the data dictionary. The Build Product Line utility builds, compiles, and deploys a product line or product line fragment.

The dictionary consists of two physical files.

The data structure defined by the LPL source. Data structure changes are all tracked through timestamp versioning.

File location: LARUNDIR%\dict\<dataarea>.timestamp

The dictionary built from the <dataarea>.xml deployment file.

File location: %LARUNDIR%\dict\<dataarea>.dict

Use displaydict to view the file, elements or indexes of a data dictionary. Example:

viewdict [-cfirCD] dataarea [files ...]

viewdict -m dataarea

viewdict -s[D] dataarea

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark database utilities


Verify Database (dbverify) utility

The Landmark dictionary contains descriptions of all Landmark tables and indexes. In some cases, the database driver will need to translate the Landmark description for storage in the database. For Landmark applications to work properly with Landmark tables stored in the database, Landmark dictionary descriptions must match the expected translations.

Mismatches in these definitions can lead to performance problems (index definition mismatches) or even application failure (column definition mismatches).

The dbverify utility checks for these differences when it compares the Landmark dictionary with what is found on the database:

Missing columns or indexes

The utility checks to make sure that each column and index defined in the Landmark dictionary has a matching column and index in the database.

Extra columns or indexes

The utility checks to make sure that all objects defined in the database have counterparts in the Landmark dictionary.

Mismatched column or indexes

The utility checks to ensure each column and index definition matches what is at the database.

Mismatched charset

The utility checks to ensure the character set specified within the dictionary translates to that which is specified at the database

Note: If you run dbverify without options, it prints out a line that notifies you as it checks each table in the specified product line, system code, or file. If you run the utility in quiet mode (using the –q option), it prints out only the messages that identify the differences between the definitions, followed by a summary

Build Data Definition (dbmaint) utility

The dbmaint utility generates SQL statements for creating or deleting selected tables and/or indexes. The utility can operate on specific tables, all tables in a system code, or all tables in a product line or data area. The utility creates Data Definition Language (DDL) text according to the highest possible version with the given compatibility. The definitions that generate the SQL statements reside in the Landmark dictionary.

The dbmaint utility can be used to:

Generate DDL for the Landmark tables and indexes. Repair problems that are identified by the dbverify utility. Drop and recreate tables or indexes that are out of sync with the Landmark data dictionary or are

somehow missing, or to conserve space and enhance performance. Generate DDL statements to a file for examination or making minor changes. Drop indexes before you load data, then rebuild the indexes after the data is loaded. Remove data from a table by dropping and recreating it.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Note: If a table or index needs rebuilding or modification without going through the reorganization process, or if you want to make changes to the definition statements issued by Landmark to database, use the dbmaint utility.

Viewing data (dbdisplay)

dbdisplay displays data stored in a file. Options allow filtering for subsets of data, or viewing only specified fields.

Note: The data cannot be exported to a file or modified in any way using this utility. The dbexport utility must be used if you want to save or modify the data.

Importing data (dbimport)

dbimport can import both binary and CSV-formatted data files into the Landmark database.

Exporting data (dbexport)

dbexport creates a binary or CSV file containing data from a Landmark-defined database file. You can load this data into the Landmark system using dbimport.

Do not use this utility to export data from a non-Landmark defined database file. Do not use this utility to copy GEN (Environment) data from one machine to another.

Demo: Execute commands to verify and display data stored in a file

Your instructor will demonstrate how to execute commands to verify and display data stored in a file.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 6.3: Execute commands to verify and display data stored in a file

In this exercise, you will execute commands to verify and display data stored in a file.

Exercise steps


2. Type dbverify –l GEN Actor. (Note that “-l” is an L, not an I.) Notice the table and indices.

3. Type dbdisplay –h GEN Actor > Actor.txt. Notice the Actor.txt file containing the display output.

4. Type displaydict GEN Actor > ActorLayout.txt. View the file and notice the information contained within is the structure of the table; fields, indexes and relationships.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Which of the following is used to specify how Landmark accesses the database for a data area?

a) LASRCDIR b) db.cfg c) buildprod d) startlaw

True or false? dbdisplay - creates a binary or CSV file containing data from a Landmark- defined database file.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 7: Landmark queues Estimated time

2 hours

Learning objectives


Describe the architecture of the Async framework. Describe the purpose of queues and queue mapping. Identify processing of each queue. Define how to map transactions to the queue.

Topics Queue mapping overview Landmark system queues Asynchronous processing flow Queue mapping Managing queues Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

94 Lesson 7: Landmark queues © 2014 Infor Education

Queue mapping overview


Async framework

The Async framework provides background execution processing for a Landmark system, including the processing of set actions and instance actions.

The Async framework uses queues for background processing.

A Landmark Environment contains several queues at delivery; you can create additional queues as well.

A system will typically have the following types of queues:

S3 transaction queues M3 transaction queues Lawson process server queues E-mail queues Document queues Default queue (for everything else)

Async is written with the LPL (Landmark Pattern Language) and consists of the following key business classes, viewable through the Data Menu for gen:

AsyncActionRequest (Request)

This represents a request for asynchronous execution of a task. The request may include scheduling information.

QueueMapping

When a request is ready for execution, QueueMappings are used to determine in which queue to create the trigger.

QueueDefinition (Queue)

Any number of queues may be defined with different behaviors regarding throughput and tracking. This can be used for resource management and action execution control in regard to, for instance, mutual exclusiveness.

AsyncActionTrigger (Trigger)

This represents an actual execution instance of an AsyncActionRequest. A request with periodically recurring execution will have multiple triggers (one for each execution).

These are the entities that get queued.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark system queues

Queue Usage Default process frequency

Default reset frequency

AGS/S3 Transaction Processes asynchronous requests for S3 Transactions

Every 5 seconds Every hour

Document Processes asynchronous requests for PDF and CSV generation


ProcessFlow Processes asynchronous requests for ProcessFlow


Email Processes asynchronous requests for email


Lcalc Processes asynchronous requests for analytics for multidimensional reporting

M3 Transaction (not fully implemented)

Processes asynchronous requests for M3 Transaction calls

NA NA

WS Transaction Processes asynchronous requests for Workspace

EffectiveDated Queue Processes effective dated transactions

Default Queue Created upon first reference of a non-queue defined action

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Asynchronous processing flow

Asynchronous process flow

Each queue is administratively given a number of worker threads. This is how system resources are divided between different types of activities.

The flow of events from an end user's perspective begins in one of three ways, which is the execution of a task, which runs asynchronously. The three possible ways to run are:

Run once as soon as possible. Run once at a specified time. Repeatedly execute the task according to a schedule (e.g. every Monday).

Physical flow of events

1. The process begins through a task or user action in a Landmark application that calls for background asynchronous processing.

2. The task or user action causes Landmark to create an async action request.

3. A background task scans for async action requests. It determines when to execute unprocessed tasks, and, for requests whose execution time has come, it determines the best queue mapping for the request. If no queue mapping is found, the default queue is used.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


4. A trigger is created for the request on the queue the request was assigned to.

5. A background task scans the triggers for each enabled queue and, if it finds triggers and the queue has available worker threads, it updates the trigger status and finds a place to run the trigger's action.

6. The trigger status is updated to acknowledge that processing has started, and then is updated again when the action is executed.

7. A background task scans all running triggers on a regular basis and updates the trigger status for any that it cannot find to indicate that the action has been lost.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Queue mapping

Set up queue mapping

Use this procedure to set up queue mapping. Queue mapping allows you to control which tasks and actions are processed by which queue. When setting up the queue mapping, two things you should consider are the types of actions that are mapped to each queue and the priorities you set on the triggers that match each queue mapping. By controlling which actions go to which queues, you can, for example, send actions that typically use few resources but occur frequently to a queue with a higher number of maximum actions or worker threads allowed. You can then send resource-intensive actions to a separate queue that has perhaps only one worker thread, thus preventing multiple large jobs from tying up the system resources.

Setting the priority on queue mappings allows you to control when requests are processed within an individual queue. It does not apply across all queues. Thus, a critical priority request on one queue may be processed at the same time as a normal request on another queue. However, it will be processed before all lower priority requests on its queue.

You set up queue mapping on queues other than the default queue. The default queue is used whenever the system cannot find a match. Queue mapping can be done by actor, data area, business class, and action. You can set up levels of mapping, specifying one or more of these.

When the system needs to map a task or action to a queue for processing, it will evaluate the mappings in the following way. It looks for a match first for all categories (actor, data area, business class, and action), and then successively for less specific matches, with preference given first for the first category (actor), then the second category (data area), and so on. This results in the following order to matching tries:

Matching

try

Actor Data area Class Action

1 Match Match Match Match

2 Match Match Match

3 Match Match

4 Match Match Match

5 Match Match

6 Match

7 Match Match Match

8 Match Match

9 Match

10 Match Match

11 Match

Queue mapping: Example 1

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Consider the following scenario. Assume you have the following queue mappings and requests:

Queue mappings Requests

Mapping Queue Actor Data area

Class Action Request Actor Data area

Class Action

1 Q1 John GEN X Y 1 John GEN X Y

2 Q2 GEN X Y 2 Jane GEN X Y

3 Q3 Jane 3 Paul GEN X Y

4 Q1 GEN X 4 Paul GEN X Z

5 Paul LTM X Z


In the above scenario, the requests will match the queue mappings as follows:

Request Mapping match

Queue Match try Comments

1 1 Q1 1 All fields match.

2 3 Q3 6 Even though there is a mapping that matches on the data area, class, and action, there is another mapping (3) that matches on the higher category of actor. The mappings say, in effect, that all requests by Jane go to Q3.

3 2 Q2 7 No mappings exist for the actor Paul, but mapping (2) matches for the other three categories.

4 4 Q1 8 No mappings exist for the actor Paul and the Z action, but a mapping (4) exists for the GEN data area and the X action.

5 None Default Queue

When there is no match, the requests are mapped to the Default Queue.


@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Create, map, and schedule a new queue

Your instructor will demonstrate how to create, map, and schedule a new queue, and then view the scheduled request.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 7.1: Create, map, and schedule a new queue

In this exercise, you will create and map a queue, and then schedule and view the scheduled request.

Exercise steps

Part 1: Create the queue:

1. Go to the Infor Rich Client Admin shortcut on the desktop.


3. Type Tr@in123 in the Password field. Verify that the GEN data area is currently accessed.

4. Click Start > Application > Async Administrator > Async Framework Components.

5. Double-click Queues.

6. Click Actions > Create.

Use the following data to create the queue:

Field Value

Name User

Description User Queue

Save History Checked

Max Actions 1

7. Click Save.

The other two fields in the dialog box have important functions:

Suspend: If you select the Suspend check box, no action request will run until you resume the queue. For example: You have a big running job that people submit to during the day but you don’t want it to run until the evening when there are fewer queues running.

Save History: It removes a request once it is complete. You may want to check this box if you want go back and see how often the action ran, and other debugging tasks. Typically, this box is unchecked.

The Default Queue is a catch all for all queues where you don’t specify parameters such

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


as business class, action, or actor. The Save History check box should be checked for this queue because this is where the backup and upgrade jobs are run. Because of this, the Save History file can get quite large. We recommend purging the Save History file on a weekly basis.

Part 2: Map the request to a queue:

1. Click the Queue Mapping tab.

2. Click Actions > Create. The Async Queue Mapping form opens.

3. Type lawson in the Actor ID.

4. Type GEN in the Data Area field.

5. Click the Save icon.

6. Close the Queue application.

Any transaction initiated by the user lawson that doesn’t fall within the system queues will now be processed and tracked through this Async queue.

Part 3: Schedule the queue:

1. Open Queues from the Async Application menu.

2. Select Actions > Suspend Queue in the Queue tab. A scheduling form will open up.

3. Select Document queue from the Queue drop-down list.

4. Click Schedule in the lower right-hand corner of the form.

5. Type <the action’s name> in the Scheduled Action Name field.

6. Type <your email address> in the Email Address field.

7. Select Always from the Notification Type list menu. [Selects the frequency of when you want to receive notices.]

8. Select Run Once in the Schedule Type field.

9. Type <five minutes from current time> in the First time to Run field.

10. Select Next > Finish > OK to close the form.

Part 4: View your scheduled Actions:

1. Select Start > My Actions. This opens the My Scheduled Actions window.

Part 5: View your scheduled Requests:

1. Go to Infor Rich Client on the desktop.

2. Select Start > Applications > Async Framework Components > Requests.

3. Search for the Actor: lawson and data area: GEN.

4. View the request before execution.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Part 6: View your User Queue upon completion:


2. Select Start > Applications > Async Framework Components > Queues.

3. Select the UserQueue and notice the trigger has finished.

4. Close the UserQueue and locate the Document queue in the list. Notice the Document queue is suspended.

5. Select Actions > Resume on Document queue row.

Note: The job ran on the UserQueue because we mapped this queue to run any request ran by Actor lawson and data area to GEN to run on this queue.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Managing queues

Queue monitoring and management

Monitoring from a system administrator’s perspective

The system administrator’s main concern with Async will be managing the available system resources on the back end server or servers.

The back end system has a limited set of resources (CPU and memory).

In Rich Client, you can use the Async Framework Components and Async Overview applications to monitor and manage the queues. For example, you can monitor queue processing to identify resource-intensive programs and transaction failures.

You can also examine the log files Async.log and Grid Management > Topology Page for the Async Node (LmrkDeferred) log to find errors and misfires.

There are multiple ways to view the Async framework and queues within Rich Client.

Demo: View and manage a queue

Your instructor will demonstrate how to open Async Overview and navigate the various tabs to view queue status and reports.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps

1. Navigate back to Infor Rich Client.

2. Click Start > Applications > Async Administrator > Async Overview.

Queue View View specific queues. Helpful if you already know the queue’s name.

Request Management View all requests – not specific.

Queue Management View all queues.

Processing Viewer Shows all queues that are currently running. Shows a dashboard view. You can view all queues that are active, failed, misfired, etc.

Failed View failed queues regardless of queue or request.

Misfires View misfired queues.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Queue management tasks

You have the following options to manage queues within the Async framework in a Landmark Environment.

Queue definition and configuration

You can:

Define additional background processing queues. Configure both delivered and created queues. Set up queue mapping in order to control which actions and tasks are processed by which

background processing queue.

Task and task stream definition

You can create tasks that will be processed in the background and you can create task streams, which are sets of tasks to be processed successively. Tasks can be any action available in a business class. When you define the task, you also define the data needed to process the task. You can also schedule the processing of a task or task stream.

Notification and failures

Failures need user intervention to resolve.

For LTM, failed flows will send a notification to the user identified in Data Menu > LTM > la > ConfigurationParameter.

Failed Async records can be viewed directly in the “Triggers” component.

Misfires

If a request, that is specified to execute on a certain time, is not processed until much later, we have a misfire. What "much later" means is configurable and expressed by each request in the field "MisfireThreshold."

In the request there is also the field "MisfireReportMode" that controls if and how misfires are managed. See Request for more information.

Once a request has been processed into a queued trigger, it will not be considered a misfire even if it stays in the queued state for a long time. This situation is managed by reconfiguring queues and priorities or by adding more processing resources.

Misfires - fields and actions

Fields – Misfire

Field Type Description

AsyncActionRequest AsyncActionRequest The requests that this misfire belong to

AsyncActionMisfire Numeric size 9 Auto sequence

RequestedStart Timestamp The missed start time (the time that the request should have been executed)

TriggerCreated Boolean Has a trigger been created for

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Field Type Description

this misfire? If it hasn't, an administrator may manually create a trigger from a misfire and if that has been done this field will be true.

Actions – misfire

Action Type Description

ReQueue Instance If no trigger has been created for this misfire, use this action to manually start the requested action that was missed (this misfire).

Demo: Requeue a trigger

Your instructor will demonstrate how to requeue a trigger.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 7.2: Requeue a trigger

In this exercise, you will requeue a trigger.

Exercise steps

1. Navigate back to Infor Rich Client.

2. Click Start > Applications > Async Administrator > Async Framework Components.

3. Double-click Triggers.

4. Select the Action you want to requeue from the Queue list.

5. Click Actions > Requeue.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Identify the four categories for which queue mapping can be done.

a) Actor b) Business class c) Subversion d) Data area e) Action

Describe the function of the Async framework.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 8: Maintain and troubleshoot Landmark Estimated time

3 hours

Learning objectives


Identify backup requirements. Define process for application data copy process Describe proper starting and stopping of Landmark components. Describe the benefits of using the ValidationURLs for troubleshooting. Identify errors, locate log, and resolve some errors. Introduce Lawson Information Investigator’s (LII) function in troubleshooting.

Topics Maintaining Landmark

Identify backup requirements Copying Infor Landmark application data copy

Starting and stopping Landmark components Troubleshooting Landmark

Environment issues Configuration issues Infor Lawson Information Investigator


@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

108 Lesson 8: Maintain and troubleshoot Landmark © 2014 Infor Education

Maintaining Landmark


Backup strategies

Below are four important backup strategies to follow when maintaining Landmark:

a. Database backups using third-party software.

b. File system backups:

LADIR Subversion Lawson (/etc/lawson or C:\lawson) Third-party dependencies

Perform dbexports of GEN and LTM (application) prior to applying any critical updates.

Perform cdexport to export the configuration data for the Landmark system prior to making any Configuration Console changes or applying any “critical updates.”

Infor Landmark application data copy process

The goal of copying application data is to move the data for an application in one Landmark Environment to another Landmark Environment such that the Landmark application in the second environment is equivalent to the one in the first environment. This involves more than copying only the data for the application. Because a Landmark application also interacts with security and user data, you must take steps to synchronize the encryption and set up equivalent actors and identities. In addition, if your Landmark system and the Landmark application you are copying data from are connected to an Infor Lawson System Foundation environment, you must copy additional data for the Lawson Enterprise application.

General application data copying prerequisites:

Operating system

The source and destination must be the same operating system for both Landmark and, if applicable, Infor Lawson System Foundation.

Infor Landmark Technology

The source and destination Infor Landmark Technology environments must be the same version. The data copying process is valid for Infor Landmark Technology releases 9.2.2, critical update 3 and higher.

Infor Landmark Technology application

The Infor Landmark Technology application in the source and destination environments must be the same version.

Infor Lawson System Foundation

If the data copying also involves data from a Lawson Enterprise application, the source and destination Infor Lawson System Foundation environments must be the same version.

Lawson Enterprise application

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


If the data copying also involves data from a Lawson Enterprise application, the source and destination Lawson Enterprise applications must be the same version. You can duplicate the Lawson Enterprise application product line by using the process described in the "Product Line Copying" section of the Infor Lawson Administration: Server Setup and Maintenance Guide.

Destination system

This process assumes that the data contained initially in the destination Infor Lawson System Foundation environment, Lawson Enterprise applications, Infor Landmark Technology environment, and Infor Landmark Technology application is only the data from the installation of these.

Data copy overview - Standalone

The standalone scenario is when you are copying data from an Infor Landmark Technology application where there is no connection to a Lawson Enterprise application in an Infor Lawson System Foundation system. This can occur, for example, if the Infor Landmark Technology application is Infor Talent Management or Infor Lawson Enterprise Financial Management. In this case, the main steps are:

1. Export the encryption files, Landmark application data, and identities from the source Infor Landmark Technology environment.

2. Import the encryption files, Landmark application data, and identities into the destination Infor Landmark Technology environment.

Data copy overview - Connected

The connected scenario is when you are copying data from an Infor Landmark Technology application where there is a connection to a Lawson Enterprise application in an Infor Lawson System Foundation system. This can occur, for example, if the Infor Landmark Technology application is Infor Supply Chain Management or Infor Lawson Enterprise Financial Management. In this case, the main steps are:

1. Export the source Lawson Enterprise application data. (You do not export the source Infor Lawson System Foundation GEN data.)

2. Import the Lawson Enterprise application data into the destination Lawson Enterprise application.

3. Export the encryption files, Landmark application data, and identities from the source Infor Landmark Technology environment.

4. Import the encryption files, Landmark application data, and identities into the destination Infor Landmark Technology environment.

5. Manually set up users in the destination Infor Lawson System Foundation system to duplicate the users existing in the source Infor Lawson System Foundation system.

Additional notes:

The source Infor Landmark Technology obtains the encryption files from the source Infor Lawson System Foundation system via the Infor Landmark Technology installation steps.

The data copy process puts those same encryption files in the destination Infor Landmark Technology environment.

In both the source and destination systems, Infor Landmark Technology provides the authentication (that is, Infor Landmark Technology is "primary").

The destination Infor Landmark Technology and destination Infor Lawson System Foundation systems remain connected because the data copy process does not overwrite the destination Infor Landmark Technology configuration data for services, endpoints, domains, and so on that define the connection.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Starting and stopping Landmark components

Lawson Landmark Technology Server Setup and Maintenance Guide

Starting and stopping Landmark

To keep the system in a consistent state, the order of startup should be:

1. Database

a. LDAP*

2. Landmark

3. WebSphere (node agent followed by the app server)

4. Web Server**

This is a "full start" and the reverse is a "full stop."

*LDAP does not factor into this stop and start process as Landmark would only need LDAP for the bind to your Corporate Active Directory and it would be assumed that this would be up and not be part of any routine stop and start procedure.

**The Web Server can remain up or down and doesn’t impact the stability of the environment or access to the environment. However, if the Web Server is down while everything else is up, you won’t be able to access the Web applications.

Syntax Definition

stoplaw When you run stoplaw, the Landmark grid application is placed in an off-line state and all Landmark-related nodes are shut down except the ManageLandmark and DSSOSessionProvider nodes. Note: You must stop the application server (such as WebSphere) before you stop the Lawson servers.

startlaw When you run startlaw, the Landmark nodes are restarted.

adminlaw The adminlaw command will start or stop nodes so that only the Lase, lads, ManageLandmark, and DSSOSessionProvider nodes are running. This command is appropriate, for example, during a Landmark update process. This command runs only lad and Lase, stopping all other processes. This command is used for installation or deployment.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Grid commands

Syntax Definition

gridservice stop/start [noapps]

This will start stop the gridservice which contains all grid nodes. The noapps value will start the gridservice without any grid nodes.

managegrid [start] [stop] –a This command will start/stop all apps with exception of any binding names. For example: managegrid start –a Lase will start all grid nodes except the Help grid node.

managegrid [start] [stop] This command will start/stop an individual grid node. For example, managegrid start Lase will just start the Help grid node.

Start and stop Landmark Environment individual components

In many cases, you can stop and start the individual components of the Landmark Environment rather than stop and start the entire system through stoplaw and startlaw.

The following table lists the start and stop commands you can use for these components. These commands start and stop the node types defined in the %LADIR%\LMKENV_gridl\config\runtime.xml file.

Component Start program Stop program

Landmark Database Lock Server managegrid start Lads managegrid stop Lads

Landmark Security Server managegrid start Lase managegrid stop Lase

Landmark Async Server managegrid start Async managegrid stop Async

Lawson Process Server managegrid start LPS managegrid stop LPS

LmrkBatch (node type set up for batch processing)

managegrid start LmrkBatch

managegrid stop LmrkBatch

LmrkInteractive (node type set up for transaction processing)

managegrid start LmrkInteractive

managegrid stop LmrkInteractive

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Stop and start Landmark components

Your instructor will demonstrate how to stop and start Landmark components.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.1: Stop and start Landmark components

In this exercise, you will stop and start Landmark using stoplaw, adminlaw, and startlaw commands.

Exercise steps


2. Type adminlaw.

3. View Grid Manager or managegrid list. Confirm that only lads, and Manage Landmarklase are running.

4. Type startlaw.

Stopping and starting WebSphere

In Landmark, each application module is modeled as a service, and each HTTP endpoint is meant to model a web server. The WebSphere administrative console is used to map modules (services) to web servers (HTTP endpoints).

Demo: Stop and start WebSphere

Your instructor will demonstrate how to stop and start WebSphere.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 8.2: Stop and start WebSphere

In this exercise, you will stop and start WebSphere.

Exercise steps

1. Go to Windows Services.

2. Stop the IBM WebSphere Landmark Node.

3. Stop the IBM WebSphere Node_Agent for Node.

4. Start the IBM WebSphere Node_Agent for Node.

5. Start the IBM WebSphere Landmark Node.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Troubleshooting Landmark


Remember that Landmark is a multi-tiered application and has several moving parts in several layers. When troubleshooting Landmark, you should locate which layer the issue is occurring in by testing Landmark in its various access points:

Command prompt tools Rich Client tools Web tools

Environment issues

You can use command utilities to troubleshoot different aspects of the environment. For example:

Syntax Definition

dbcount Verify database connectivity by running a simple command like dbcount to determine whether you can connect to the database.

managegrid list Verify that all grid applications are running.

Configuration issues

You have a choice of several tools to help you identify configuration issues. These are in addition to any error messages that you may see as you are working in the Configuration Console on a configuration. These tools can help you identify invalid configurations, locate specific errors within configurations, and compare different versions of a configuration in order to better understand what may be causing a problem.

Tool Definition

cdverify utility The cdverify utility can be used to quickly list invalid configurations and show any syntax errors in configurations.


The Configuration Console itself includes tools for comparing configurations, locating invalid syntax, and identifying invalid configurations.

Infor Rich Client - Configuration business class forms

Through the Data menu in the Infor Rich Client, you can view a list of configurations of a single type, and then identify invalid ones of that type and compare any two versions of the configuration.

Running ValidationURL tests

The ValidationURL tests are a browser based point and click link which allows you to test the basic Landmark Environment functionality. It is advised to use these after any updates to Landmark or your application or if there are issues occurring, which will assist in the process of troubleshooting your issue.

You will find the ValidationURL in %LADIR% directory and there is one URL for each product line type.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


For example: ltm_ValidationsURLs.htm, Landmark_ValidationURLs.htm, and financials_ValidationURLs.htm.

SSO configuration

Used to view SSOCONFIG information in XML format. Validates your SSO layer is functional.

Web login

Validates that the web UI is functional.

InfoCenter

Validates your InfoCenter is installed and functional.

*Canvas login

Validates the Rich Client installs and login is operational as well as the Rich Client loads.

*Canvas Admin login

Validates the login to the Admin Rich Client is functional and the GEN data area is accessible.

Canvas menu

Click this link to open an html page that has the links to both the Infor Rich Client and Infor Rich Client admin log ins.

*Note: You may see a Java version warning, and the installation may download an older Java version to use.

Demo: Run ValidationURL tests

Your instructor will demonstrate running a couple of ValidationURL tests.

______________________________________________________________________ ______________________________________________________________________

Demo steps

1. In a browser, open %LADIR%\landmark_ValidationURLs.htm.

2. Click the SSO Configuration link. This will bring up the SSOCONFIG information in XML format.

3. Click the Web login link. This brings up the web login screen.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Checking Grid JVM logs for errors

Check the logs to see what errors are occurring in the system. This is best viewed in the Grid Management Console for the individual grid node that may be responsible for the issue.

Demo: Display error logs

Your instructor will display common error logs via the Grid Management Console.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Viewing grid node logs

Log files are associated with each grid node. Because each application is running in one or more grid nodes, you can obtain valuable information about an application by viewing these log files. You typically access log files from the Topology Overview page, Status page, or Applications page. Once a logfile is opened, you can filter and search for relevant information. It is also possible to view log files of old nodes that are no longer running and to download log files in order to, for example, e-mail them to someone.

Demo: View grid node logs

Your instructor will demonstrate how to view grid node logs.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.3: View a grid node log

In this exercise, you will view a grid node log.

Exercise steps


2. Go to the Grid Management Pages for the grid whose log files you want to view:

Topology Overview page

Status page

Applications page

3. Click the appropriate link, depending on which Grid Management page you are on.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


For Topology Overview page:

a. Click the runtime artifact button in the Log column for whose log file you want to view.

For Status page:

a. Click the Log link for the item whose log file you want to view

b. Click the button in the Log column on the Application Logs dialog box

For Application page:

a. Click the Logs button for the application whole log file you want to view.

Infor Lawson Information Investigator

The Lawson Information Investigator (LII) is a Perl-based tool used to collect hardware and software information from servers, including information on Lawson product installations.

Demo: Explore Infor Lawson Information Investigator

Your instructor will demonstrate how to access the LII web interface and view the versioning data on the servers.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 8.4: Explore Infor Lawson Information Investigator

In this exercise, you will access the LII web interface and explore the versioning data on your servers.

Exercise steps

1. Access IE > Favorites > Infor > Lawson Information Investigator. (http://ussplu143.lu141training.lawson.com:9999/ui)

2. Select the LII menu.

3. Select the collect link. Ussplu143 is the central server and this command collects all the information for configured servers on execution. A “Collection was started” message displays.

4. Close the Message tab.

5. Select the logrpt link from the LII menu.

6. Verify there are no errors in collection.

7. Close the logrpt tab.

8. Close the LII menu tab.

9. Expand the down arrow icon next to ussplu141.lu141training.lawson.com.

10. View all the collected data concluding on LMKEnv.

11. Select the Graphical option to view same information in a different presentation.

12. Close the LII Web User Interface browser.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

http://ussplu143.lu141training.lawson.com:9999/ui



Which of these Landmark command line utilities start or stop nodes so that only the Lase, Lads, ManageLandmark, and DSSOSessionProvider nodes are running?

a) managegrid list b) stoplaw c) svndiff d) adminlaw e) dbverify

In what order should startup be done to keep the Landmark system in a consistent state?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

120 Lesson 9: Landmark services © 2014 Infor Education

Lesson 9: Landmark services Estimated time

1.5 hours

Learning objectives


Explain the purpose of a service. Describe how to execute service additions or updates. Describe endpoints of access (external and internal).

Topics Landmark service overview Types of services

Primary service: single sign-on Reference services Application services

Adding and modifying services End points Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark service overview


Any component of the Lawson system that requires authentication has a service associated with it. Among other things, the service stores specifications about how a user can access that component. When a user attempts to launch the component, the component’s service authenticates the user behind the scenes. If the user’s identity is assigned to the service (or to a referenced service), the user can use the service without having to log in again.

In general, a service must exist before users can start working with a product or component.

Some services are delivered and installed by Lawson. You may need to create or configure others as described by your Lawson documentation for the particular Lawson product.

There are three services installed as part of the Landmark Environment:

SSOPV2 – Primary Authentication Service (LDAP bind to single server director) Lsuserapp – Service managing passwords for Lawson Lawson-struts – Service supporting connections or interactions with other services (OLEDB)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Types of services

Primary service: single sign-on

The Landmark primary service is the single sign-on service, called SSOPV2. It is an authenticating service that manages all interactions between Landmark services, external services (such as S3 Lawson System Foundation), and Landmark users.

When users log in to the system, they log in to a single sign-on (SSO) domain, or a collection of services that reference the primary service for that domain. Users who have identities on multiple services and agents need to authenticate only one time to have access to all Lawson components in that domain that require authentication.

All "internal" users (Actors) are assigned identities on SSOPV2. Without this identity, a user will not be functional or able to gain access within the Landmark system.

SSOPV2 service

Reference services

Reference services inherit all or some of the properties of the service they refer to. One important use for reference services is to access the same pool of users as the primary service. For example, many services are typically set up to reference the single sign-on service, thus allowing that service to perform the user authentication for the other services.

Application services

Another example of a primary service is the authentication service for Lawson Talent Management (LTM) candidate self-service. For LTM, the primary service for "external" users is <productline>.hcmapp.candidateselfservice. This would be the main authenticating service for candidates. Without an identity registered to this service, a candidate would not be allowed full access to the cascading style sheet CSS.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


LTM uses <prodline.hcmapp.CandidateSelfService> as the primary services for the Candidate interface. Strategic Sourcing uses an external service for suppliers.

Candidate Self Service

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Adding and modifying services All services are stored in the Landmark GEN database and can be updated through various user interfaces.

Below are possible scenarios that would cause a change of services:

Change of FQDN Addition of a new endpoint Change of port Change of protocol (http or https) New functionality Lawson delivers (for example, LTM created new functionality for sending an

email to a candidate if the candidate forgot his/her password, and a service property needed to be created for this functionality to work).

Identifying system services and properties in the system

The secadm service properties command maintains service properties in the system. The following tasks can be performed:

List defined service properties

Display the value of a service property

Add a property to a service

Update a service property value

Remove a property from a service

These procedures provide command line syntax for each of these options. If you have a large number of changes to make, the secadm menu interface may be useful. It will ask for the values shown in the command line syntax, allowing you to enter each one separately.

Services using secadm

secadm –p lawson service list

secadm -p lawson service display SSOPV2

secadm service property list servicename

Updating services in the Infor Rich Client

View services using the Service List in Infor Rich Client.

Demo: View services in the Infor Rich Client

Your instructor will demonstrate how to view services using the Service List in the Infor Rich Client.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 9.1: View a service in Infor Rich Client

In this exercise, you will view the service for the SSOP in Infor Rich Client.

Exercise steps




4. Click Start > Applications > Security Systems Management > Service in the GEN data area.

5. Scroll down the list and select SSOP.

6. Double-click SSOP. The Service Summary page comes up.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


End points Landmark defines its network with endpoints. Endpoints are Landmark objects that associate web access URLs with domains and authentication services (such as SSOPV2).

A Landmark network typically references web applications inside and outside the firewall. Each deployment requires its own access and security configuration and setup.

For example, assume that your Landmark application includes a Supplier web application that is deployed externally for internet access and a Buyer application that is deployed internally for intranet use. This is a simple deployment example that illustrates the concepts and steps involved in creating multiple endpoints.

Deployment example with multiple endpoints

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Rich Client data menu endpoint information

To view data menu endpoint information in Infor Rich Client:

1. Select GEN > Start > Data > security > Business Classes > ServiceHTTPEndpoints.

To view the http endpoint for SSOPV2:

2. Navigate back to the Service Summary Details page from the previous exercise. Click the HTTP Endpoint page link (bottom).

Landmark LTM endpoints

Landmark LTM has two endpoints: internal and external.

Internal endpoint

LTM's internal endpoint handles all internal user communication/access (Rich Client, ESS, MSS).

External endpoint

LTM's external endpoint handles all external user communication/access (CSS).

GEN access

Components of GEN are accessible through both endpoints. The <Landmark envName>-gen-law-env application will be mapped accordingly.

Note: Endpoints and module mappings go hand-in-hand.

Troubleshooting HTTP endpoint configuration

You can create a temporary log file to help troubleshoot HTTP endpoint configuration issues.

Demo: Create a temporary log file to troubleshoot HTTP endpoint configuration issues

Your instructor will demonstrate how to create the log file to troubleshoot HTTP endpoint configuration issues.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps

1. Go to Command Window for LMKENV on the desktop.

2. Type touch %HOME%\Http_client.log.

Be sure to delete this file after you have completed the troubleshooting or debugging process. This file can grow to be very large.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



In which data area are services stored?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Which of the following are the services installed as part of the Landmark Environment? (Hint: There are three.)

a) Infor Rich Client b) Application services c) End points d) SSOP/SSOPV2 e) OS

Define the function of the primary service single sign-on or SSOPV2?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 10: User administration Estimated time

2 hours

Learning objectives


Describe how to add or maintain actors (User Wizard). Describe how to add or maintain actor identities and agents. Describe the components used to add a Landmark user:

Actor Identity Identify Role Agent ActorContext

Explain how to create and define Landmark users via the secadm command

Topics Landmark user overview

Actors, Identities and Agents Process for adding actors in Landmark

Creating and defining a Landmark user Infor Rich Client – User Wizard

Creating and defining Landmark users via the secadm command Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

130 Lesson 10: User administration © 2014 Infor Education

Landmark user overview


A Landmark user is an entity set up on your Lawson system that allows a person or system process to be authenticated to Landmark applications and services.

A Landmark user is not an operating system user, or user account set up on the machine where your Lawson system runs, and it is not a Lawson user previously set up for a Lawson System Foundation Environment.

To create a fully defined Landmark user, you must link together the following components:

Actors Identities Roles Actor Agents Actor Context

After you define a user, you provide them with access to services and applications by linking them to roles. The user’s access rights are then determined by the rules within the security classes.

An Actor represents a person or individual in Landmark.

Identities are user password credentials used to access Landmark services such SSOPV2 (saved in Landmark).

Roles are collections of security classes with securable object policies/rules that are associated with users, such as Manager (saved in the Landmark application).

Agents are application-specific data sets that are associated with a generic Landmark user, such as Employee (saved in the Landmark application).

Some applications require a context such as HROrganization in Lawson Talent Management (saved in the Landmark application).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Actors, identities and agents

Actor record

An actor represents a user who can act upon a Landmark service. Actors can authenticate to a service if they have a set of credentials, called an identity, for that service.

Actor data is stored in the GEN data area, and all data areas share the same actor data.

Identity record

An identity is a set of credentials—a user name and a password—that uniquely identifies a subject for a particular Landmark service.

Identity-actor record

An actor must have an identity for the service in order to access that service. An actor can have multiple identities, for example, one for the operating system and one for the single sign-on service.

Agents*

An agent is a unique subject within a specified application domain. For example, a Requester is an agent in the Buyer application

Actor-agent record

An actor could be a Requester when accessing the Buyer application, and an Employee when accessing the Human Resources system. Agent data is stored in the data area the agent is associated with; each data area has its own agent data. In the case of self-provisioning actors, such as those created through the Candidate Space, such links are created programmatically. However, in other cases, such as when employees are added, you must add the links.

Actor context* record

Some applications require users to be set up with an Actor Context record. For example, LTM requires all users to be associated with a particular HROrganization which will limit the user’s access to the specific HROrganization the user belongs to.

*Note: Application-specific

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Process for adding actors in Landmark

Creating and defining a Landmark user via Infor Rich Client

Creating a user and assigning roles via Create User wizard in Infor Rich Client:

Adding a user is a seven-step process, the first four of which are done through the Create User wizard.

1. Add the actor

2. Add the identity

3. Link the identity and actor

4. Assign roles to the actor

5. Assign an agent to an actor

6. Add ActorContext records for a user

7. Add Infor Process Automation users for the Landmark users you added

Demo: Create and define a new user via the Create User wizard in Infor Rich Client

Your instructor will demonstrate how to create and define a user via the Create User wizard in Infor Rich Client.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 10.1: Create and define a new user via the Create User Wizard in Infor Rich Client

In this exercise, you will create and define a new user via the Create User Wizard in Infor Rich Client.

Exercise steps




4. Double-click User Management.

5. Click Create User Wizard. The General User Information form opens.

Add

Actor

Assign Actor to Identity

Assign Role to Actor

Add Actor

Context

Assign Agent to

Actor

Add

Identify

Add IPA

User

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


6. Type Amckinley in the Actor field.

7. Type Allison in the First Name field. (This field is optional.)

8. Type Mckinley in the Last Name field. (This field is optional.)

9. Click Next. The Actor Contact Info form opens.

10. Fill in any fictional address on the Address fields.

11. Type <your email address> in the Email Address field. (Note: Make sure you can access this email during class.)

12. Click Next. The Create Identity for User window opens.

13. Click the select arrow to the right of the **SSO Domain field. The SSO Domain List window opens.

14. Select the Internal SSO Domain and SSOP Primary Service and click Select.

15. Type Amckinley in the Identity field.

16. Type Tr@in123 the Password field.

17. Type Tr@in123 in the Confirm Password field.

18. Click Next. The Actor Identity Assignment window opens with Amckinley listed in the Actor Identify List.

19. Select Amckinley and click Next. The Actor Role Assignment window opens.

20. Click New.

21. Select Assign Existing Role to Actor.

22. Click the arrow to the right of the Role field.

You will assign three roles to Amckinley:

CompensationAnalyst_ST

DirectSupervisor_ST

Employee_ST.

23. Scroll and select the first role: CompensationAnalyst_ST. (Note: You can also search using the search box.)

24. Click OK.

25. Repeat steps 18-22 to assign the other two roles and then click Finish. The Summary window opens.

26. Validate the information for Amckinley is correct.

27. Click Exit.

Assign an agent to an actor.

In this exercise, you will assign the Employee agent to the Amckinley actor you created in the previous exercise. You will use the Landmark Talent Management (LTM) data area for this exercise. The example calls for you to enter the values for the HRO Organization (7004) and the Amkinley Employee number (700410).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Adding a user is a seven-step process, the fifth step assigns an agent to an actor.

1. Add the actor

2. Add the identity





7. Add Infor Process Automation users for the Landmark users you added

Demo: Assign an agent to an actor via Infor Rich Client

Your instructor will demonstrate how to assign the Employee agent to an actor in Infor Rich Client.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 10.2: Assign an agent to an actor via Infor Rich Client

In this exercise, you will assign the Employee agent to an actor via Infor Rich Client

Exercise steps

1. Navigate back to Infor Rich Client on the desktop.

2. Click the GEN > LTM data area.

3. Click the Start menu > Data > person > Business Classes.

4. Double-click Agent. This opens the Agent List window.

5. Type Employee in the Agent Type column.

6. Type 7004, 700410 in the Name column.

7. Press Enter.

8. Highlight 7004, 700410.

9. Click Actions.

10. Select Link to Actor. The Link to Actor forms opens.

11. Highlight Amckinley and click Select. The Link to Actor form displays Amckinley.

12. Click OK.

The Employee Agent is now linked to Allison Mckinley, user: Amckinley.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Add ActorContext to a User

In this exercise, you will add ActorContext records to Amckinley.

Adding a user is a seven-step process, the sixth step adds an ActorContext record for a user.

1. Add the actor

2. Add the identity





7. Add Infor Process Automation users for the Landmark users you added. (Note: We will complete this step in Lesson 14.)

Demo: Add ActorContext records for a user via Infor Rich Client

Your instructor will demonstrate how to add ActorContext records for a user via Infor Rich Client

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ ______________________________________________________________________

Exercise 10.3: Add ActorContext records for a user via Infor Rich Client

In this exercise, you will add ActorContext records for a user via Infor Rich Client.

Exercise steps

Part 1: Add ActorContext

1. Navigate back to Infor Rich Client > LTM.

2. Click the Start menu > Data > person > Business Classes.

3. Double-click ActorContext. The Context List form opens.


5. Click the select arrow in the *Actor field. The Actor List form opens.

6. Highlight Actor Amckinley and click Select.

7. Click Unique ID (second one) and select Context from the Context Property List.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


8. Select HROrganization.

9. Type 7004 in the Value field.

10. Click Save. The Actor Context is created.

Part 2: Validate that the Amckinley user exists

1. Go to Rich Client.

2. Type Amckinley in the Login field.

3. Type Tr@in123 in the password field.

4. Select LTM as the Data Area.

5. Double-click Employee process board.

6. Click My Profile.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Creating and defining Landmark users via the secadm command. You can add users with the following secadm commands. You can either run these commands individually or collectively in a batch file.

Individual secadm commands

Creates an Actor

secadm actor add <actorname> --firstname <firstname> --lastname <lastname>

Creates an Identity

secadm identity add SSOPV2 <identityname> --password <password>

Assign the Actor to Identity

secadm actor assign <actorname> SSOPV2 <identityname>

Provide an ActorContext record for the Actor

secadm actor context add <actorname> <data area> <HROrganization key name> <key value>

Link an Actor to an Agent in the application

secadm actor link add <actorname> <data area> <agent type> <HROrganziation key value> <key value>

Batch secadm commands

Using batch secadm is one of two ways to bulk load users into the system. If you have a Landmark standalone application, then secadm is the only way to bulk load users. Otherwise, if you have Lawson System Federation (LSF) then you can also use LSF to bulk load users.

Multiple secadm commands can be aggregated into a file and executed:

secadm –f <filename>

secadm provision os (Loads Landmark Actor based on OS)

secadm load classic (Loads Landmark Actor based on S3 users)

Demo: Create a new user in Landmark using a secadm batch script file

Your instructor will demonstrate how to create a new user in Landmark using a secadm batch script file.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 10.4: Create a new user in Landmark using a secadm batch script file

In this exercise, you will create a new user in Landmark using a secadm batch script file. You will use this user in future exercises.

Exercise steps

1. Launch Windows Explorer and navigate to %LADIR% (C:\LMKENV).

2. Review the file: AddTRAINUser.bat in Notepad and validate that it matches the sample batch file below (case sensitive):

Sample batch file called secadmAddUser: actor add Vsantos --firstname Valeria--lastname Santos identity add SSOP Vsantos --password Tr@in123 actor assign Vsantos SSOP Vsantos role assign Vsantos Employee_ST role assign Vsantos DirectSupervisor_ST role assign Vsantos CompensationAnalyst_ST actor context add Vsantos LTM HROrganization 7004

actor link add Vsantos LTM Employee 7004 700408

3. Go to Command Window for LMKENV on the desktop.

4. Run the command: secadm -f AddTRAINUser.bat.

5. Go to the Infor Rich Client on the desktop.

6. Type Vsantos in the Login field.


8. Change the data area from GEN to LTM.

9. Double-click Manager.

10. Click My Staff. Notice user Vsantos has direct reports. (You will use this user in the Infor Process Automation Lesson 14.)

11. Exit out of Infor Rich Client.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



True or false? The user’s access rights are determined by the rules within the security classes.

_______________________________________________________________________ _______________________________________________________________________

List the components required to define a Landmark user.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Which term means a set of credentials—a user name and a password—that uniquely identifies a subject for a particular Landmark service?

a) Identity b) Actor c) Actor d) ActorContext e) Agent

In which data area are Actor records stored?

a) Async b) GEN c) Apps10 d) LTM e) Configure Console

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

140 Lesson 11: Landmark Security © 2014 Infor Education

Lesson 11: Landmark Security Estimated time

3 hours

Learning objectives


Define Landmark Security: Authentication and application authorization overview. Describe how to add and apply security roles. Describe the provided security classes and rules of access. Explain when you would enable or disable Landmark Security. Describe how to add security policies using the secadm utility. Identify where to locate the security reports.

Topics Landmark Security overview

Application system architecture Landmark Security setup

Important best practices Main Security administrator functions

Landmark authorization model Configuring user access Landmark run-time security enablement Security administration utility - secadm

Individual secadm commands Batch script commands

Security reporting Security terms Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Security overview


Infor Landmark User Setup and Security

Landmark Security provides features for authentication and authorization.

Authentication refers to control over which users can log in and how they can log in.

Authorization refers to control over each user's access after he or she has logged in.

Whether a user accesses a Landmark system through a browser or through the Infor Rich Client, the Landmark Environment and applications provide security through authentication and authorization security.

Application system architecture

Web architecture

Application and security architecture for applications accessed through browser

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security points

1. When a user accesses a Landmark application through a browser, the user must supply a user name and password as credentials. These travel over HTTP or HTTPS to the security authentication servlets.

2. The credentials are validated using the authentication policy in place (LDAP bind or match against local storage). A new session for the user is created if the credentials are valid.

3. Any requests for data or transactions are checked for the proper authorization. If the user is authorized to access data or perform an action on data, then the data is retrieved or the data changes are executed. The authorization system uses a role-based access control model.

4. Appropriate data is returned for that request. Any data not authorized for the user to see is not returned (that is, it is not simply hidden from the user; it is not even sent). The authorization model is the same as in #3.

5. Credentials and sensitive data are stored in the application database in an encrypted form.

Application accessed through Infor Rich Client

Application and security architecture for applications accessed through Infor Rich Client

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark Security setup

Important best practices Never turn off security. If you do, all encrypted data will be stored and visible in an unencrypted

condition thereafter. Never run security with all roles set to Allowed all actions to all securable objects. This is the

same as running without security on. Before having a new user log in for the first time, finish assigning all appropriate roles to the user.

Or if assigning a new role to an existing user, clear the cache before the user logs in again.

Main Security administrator functions in Landmark 10.x

For the following functions you will need to use the Configuration Console as described in the Landmark User Setup and Security Guide:

Add a role for the current OS user or other OS users that you want to become security administrators (GEN administrators).

Create security roles. Assign security classes to roles. Create ("provision") actors. Assign actors to roles, including to the security administrator role. Create, copy, and modify security classes with Configuration Console. Create Actor Context records for the actors as recommended for application requiring access. Enable process rules in GEN. Create and activate an Account Lockout Policy and a Password Reset Policy for the service or

reference another service's policies for these. (If ldapbind is not executed on internal service.)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark authorization model The Landmark authorization model includes a delivered set of security classes. The delivered classes are designed to reflect common authorization needs for an application.

Security classes are defined in the same product line structure, using the same LPL syntax and framework, and the same pattern-based philosophy as the rest of the application. The mechanism for executing security rules is contained in the application itself, and is generated, compiled, and run just like the rest of the application code.

Security classes can provide security for numerous securable objects, including:

Securable object types, such as: Business classes (BusinessClass), fields (Field), and key fields (KeyField) Business tasks (BusinessTask) Executables (Executable) Web applications (WebApp) Data area (DataArea), module (Module), menu (Menu), menu item (MenuItem) Securable object type (Type)

Securable objects, such as: Individual business class, business task, executable, and web application objects Data views, including a business object and its fields, and related business objects and their

fields Fields, including compound, derived, display, and key fields Drills and audit logs

Default access determination

Every object type has a defined default access. For example, the default access for data areas, product lines, and business classes is no access. Securable objects belong to a hierarchy, or tree, of objects. For example, a business object such as the Company business class belongs to the containing objects module and product line. The content of the business object—its persistent fields, for example—reside below the object on the tree.

If a contained object has access granted, then the containing object access is evaluating. Otherwise, the containing object is not accessible. When the security engine does rule evaluation, it evaluates the rules and defaults in this order:

1. Rules written against the explicit object name (direct rule).

2. Rules written against any applicable ontological names (does the object exist in the context of another object, and are there rules written against that object). Ontology exists for Business Classes only.

3. Rules written against that object type (does the object extend another object, and are there rules written against that object).

4. Rules written against securable object type (Type), if it exists. For example, BusinessClass Type. This kind of rule is applicable to all securable objects of given type

5. Default access for that object type. Evaluation stops at any level (1 – 5) if the rule exists.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuring user access

Roles, security classes, and rules

Roles

A role is a set of access rights that allow a user access to the system. Roles are task-based meaning that they are intended to describe a job that a user performs, rather than describing the user.

Roles contain security classes and determine what objects, applications, data an actor has access to, and the action an actor can perform.

Security classes

Security classes are designed to contain the rules needed to provide the access a user needs to perform a task. After creating roles and security classes, an administrator can assign security classes within the application product line, and then assign roles to actors within the GEN product line.

There are security classes for both environment (GEN) applications/functions as well as the Landmark applications.

All GEN security templates are located at: %LASRCDIR%/gen/security/src. The delivered standard templates will have an _ST in the name of the security class. Lawson-delivered security templates _ST define what objects, business classes, and access

actors have and the functions an actor can perform.

Rules

Rules are contained in security classes. They determine how the application information modeler wants to allow user access to a securable object.

If you are updating your Lawson System Foundation system with Talent Management, then you will need to reinvent and redefine your Lawson roles, as well as process flows.

How is access granted to users, actors, or identities?

Roles are defined to assign access to system components—to provide authorization. Each actor should have one or more roles assigned to it, providing authorization to system components and data.

An actor is linked to an identity in order to allow the actor to log in. A user has an identity for one or more services in the system.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security model

Actor context attributes

Actor context attributes are additional key fields that can be assigned to an actor for authorization and system defaulting purposes. The basic setup procedure is to designate a key field as a context property and then assign context values for this context property for individual users. Recall context properties are the key fields that you designate to be available for setting up actor contexts.

The Actor context must be a key field. A single actor can have many associated key field contexts, but for each key field only one value can be assigned.

In the following security class example, the Buyer business class may be accessed only when the Buyer matches the specified Buyer context for the actor.

Buyer business class

Security administrators can add or modify actor context values for individual actors. In addition, security administrators can modify a set of properties for actor contexts.

Any application that has a full JVM (which includes the security classes) behind it must be re-launched to pick up security class changes.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Create a new security role, assign the role to an actor, and assign a security class based on a desired access

Your instructor will demonstrate how to create a new security role, assign the role to an actor, and assign a security class based on a desired access.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.1: Create a new security role, assign the role to an actor, and assign a security class based on desired access

In this exercise, you will create a new security role, assign the role to an actor, and assign a security class based on desired access.

Exercise steps

Part 1: Create a role




4. Select LTM in the data area.

5. Click Start > Configure > Security. The Configure Security window opens.

6. Select Role.

7. Click Actions > Create Role in the Role List section.

8. Type HRTemp in the Role Name and Description fields of the Detail tab.


Part 2: Assign a role to an actor

1. Click the Role Assigned to Actor tab from the Role form.

2. Click Actions.

3. Select Assign Existing Role to Actor.

4. Click the search arrow in the Actor field. The Actor List form opens.

5. Type Santos in the Last Name field.

6. Press Enter.

7. Highlight Valeria Santos from the results.

8. Click Select and then click Save.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Part 3: Assign a security class

1. Click the “x” to exit out of the Actor List form and return to the Role form.

2. Click the Security Classes Assigned to Role tab.


4. Click the search arrow in the Data Area field to select LTM.

5. Click the search arrow in the Security Class field.

6. Type GHRGENEmployeeOrgUnitAccess_ST in the Security Class field and press Enter.

7. Click Actions > Save. Click the “x” to close the form.

8. Navigate back to the Actor menu in the Configure Security.

9. Click the search icon (magnifying glass) in the Actor List section.

10. Type Vsantos in the Actor ID field and press Enter.

11. Highlight Valeria Santos and click Actions > Assign Role to Actor.

12. Click the search arrow in the Role field.

13. Type ProcessServerAllAccess_St to search for the role.

14. Highlight ProcessServerAllAccess_ST and click Select.

15. Click Actions > Save.

16. Close all Configure related forms.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Landmark run-time security enablement

How does the security run-time system work?

When performing a user action on an object, the object calls out to the security run-time, which pulls in the appropriate execution plan for that class or task, and mines the described metadata. Using the plan information, the security run-time system creates an executor that executes the request, pulls back the user security classes and mines the appropriate rules, applying them to the request and its results, and finally returning the resulting securable object or a security exception.

Run-time authorization is enabled through a parameter in the Security table of the GEN product line database before performing any evaluation. This parameter sets authorization to All Access, No Access, or Process Rules for the security classes and execution plans. If the record does not exist, all access is granted to all users.

Demo: Enable run-time authorization using the Infor Rich Client

Your instructor will demonstrate how to enable run-time authorization using the Infor Rich Client.

Demo steps

1. Navigate back to Infor Rich Client on the desktop.

2. Click GEN.

3. Double-click Security Author Management.

4. Click Security Activation.

5. Select the data area.

6. Click Actions. Select the authorization setting for the data area (ALL_ACCESS, NO_ACCESS, or PROCESS_RULES).

7. Exit out of Infor Rich Client.

Don’t choose NO_ACCESS on GEN otherwise the administrator will not be able to do anything. Restart any Landmark programs that were running when you made this change.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security administration utility - secadm


The Security Administration utility (secadm) is a powerful tool that allows you to configure a wide range of settings for system, user authentication, or authorization.

This secadm utility can be used in three ways from command prompt.

a. Single command - A fully qualified command with all parameters identified. For example: You can use the secadm security activate <data area> command to enable run-time authorization rather than using the Infor Rich Client as was just demonstrated in the previous activity.

Go to the Landmark Command Prompt. Type secadm security activate <data area>. Select update access ALL_ACCESS, NO_ACCESS,PROCESS_RULES

b. Menu prompt - Using –m to launch menu driven option for parameters.

c. Script execution - Using –f to submit formatted file in batch mode.

The secadm utility maybe password protected. If so, the –p parameter must contain the current password for the command to be executed. See demo below.

Demo: Set a password requirement for the secadm utility

Your instructor will demonstrate how to set a password requirement for the secadm utility.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps


2. Type secadm admin setup.

3. Press Enter without entering a value in the Enter the OS login Lawson Single Sign On Service prompt.

4. Type 2 for Yes when prompted to Enforce password prompts for this utility.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


5. Type a new <password>for the password for the secadm utility.

6. Type the same <password> again to confirm the password.

Note: If you want to enable password recovery through e-mail, press Enter again once you enable password to arrive at the Enable email mechanism for password recovery prompt.

Controlling user access to a specific operating system user group

If you require that users belong to a specific operating system user group, users not in that group will be denied access to secadm.

Demo: Control user access to a specific operating system user group

Your instructor will demonstrate how to control user access to a specific operating system user group.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps


2. Type secadm admin setup.

3. Type <the name of the group> when prompted for the user group to use to authorize access to secadm.

Single command

The following are typical uses for single command:

User maintenance (Rich Client recommended) User security listings Security maintenance (Rich Client recommended)

Demo: Execute the secadm security list for user (actor) lawson to view its associated actor context, roles, and assigned security classes

Your instructor will demo executing the secadm security list for user lawson to view its associated actor context, roles, and assigned security classes.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


_____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

Exercise 11.2: Execute the secadm security list for user lawson to view its associated actor context, roles, and assigned security classes

In this exercise, you will execute the secadm security list for user lawson to view its context, roles, and assigned security classes.

Exercise steps

1. Go to the Command Window for LMKENV on the desktop. (If you followed along on the previous demonstration, you will already have the Command Window for LMKENV open.)

2. Type secadm security list user lawson.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


How to read the output:

secadm security list output

Menu

This command is used to manage system services and other security objects using the security administration menu –m.

The menu interface prompts you for the same information that can be entered at a command prompt. Additionally, the syntax can be abbreviated to create scripts to submit to secadm.

In this next exercise, you will view the security status for a product line by selecting one of the secadm report commands, secadm report status, from the secadm – m menu option. Secadm report commands enable you to view security information on the security system status, security classes and roles, securable objects, and actors.

Demo: Access menus using the -m option to view the security status for a data area

Your instructor will demonstrate how to access menus using the -m option to view the security status for a data area.

_____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 11.3: Access secadm menus using the -m option to view the security status for a data area

In this exercise, you will access menus using the –m option to view the security status for a data area.

Exercise steps


2. Type secadm –m and press Enter.

3. Type 24 to select option 24 – Security Data Reports.

4. Press Enter.

5. Type 4 to select option 4 – List Security Status for Product Line.

6. Press Enter.

7. Type LTM when prompted to enter the data area.

8. Press Enter. Note: The LTM data area displays PROCESS_RULES for its status.

9. Type e and press Enter to exit from secadm.

Script (batch file) execution

The secadm utility can be run in batch mode by creating a text file with a single line for each command and then running the file by entering the following command: secadm –f filename.txt

The secadm –f submits a script containing multiple commands to secadm.

Typical uses (same as single command):

User maintenance or security maintenance

Note: It is a good idea to capture the output of a batch file command in a file for reviewing execution.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security reporting There are several ways to retrieve information from the Landmark Security setup. The Rich Client contains reports under the Application Menu of GEN >Security System Management > Security Reports. The secadm utility contains command or menu driven reports. Information may also be sent to PDF and CSV from the forms under Options. (Lists can be modified to contain fields required.)

Demo: Locate security reports

Your instructor will demonstrate how to locate security reports.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.4: Locate security reports

In this exercise, you will locate a security report.

Exercise steps




4. Double-click Security System Management in GEN.

5. Click Security Reports.

6. Click Role Security Classes by Actor.

7. Click Options > Search in the Actor List panel.

8. Type Santos in the Last Name field.

9. Highlight Actor ID Vsantos, Santos, Valeria and select Options > Print to File (this creates a PDF).

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security terms

User proxies

A user proxy is a means to temporarily transfer the access privileges of one user to another user. User proxies can be set up by administrators or by individual users. As an administrator, you can set up proxies for any user and assign them to other users. As an individual, non-administrator user, you can set up a proxy only for yourself and assign it to another user.

Proxies are set up for grantors and grantees. The grantor is the one whose access privileges you need to assign to some else. The user to whom you assign the proxy is the grantee. When you set up the proxy, you can set it up only for one or more of the roles that the grantor has. You can set up multiple proxies for a grantor such that one proxy assigns some roles to one grantee and another proxy assigns other roles to another grantee.

Your ability to set up user proxies is controlled by the following security classes:

ProxyAdminAccess - Enables a user to set up proxies for any user. ProxyGrantorAccess - Enables users to set up proxies only for themselves. ProxyInquireAccess - Enables users to view any proxies assigned to them.

If a proxy is assigned to you, when you use the Lawson Rich Client and some web applications, you can switch to the proxy and perform actions based on the security privileges of that proxy.

Anonymous user

An anonymous security role allows internet users to access some web application functionality. The anonymous user is a valid actor, automatically created within the Landmark system.

Anonymous access is enabled by the security administrator for web services using an LPL construct allow anonymous access on actions and assigning appropriate roles to the anonymous actor. The actual access of the anonymous user depends on the roles as signed to the anonymous actor and on the security classes assigned to those roles.

During run-time, a session is created for the anonymous user on first access to system. The session can be authenticated by explicit login or registration. Session contents are preserved, and the session will not time out.

Self-provisioned actors

An example of a self-provisioned actor occurs in the Supplier Self Service application. The Supplier Self Service self-registration process creates a contact. The contact has an associated agent, an identity, and an actor. Supplier contacts are agents intended to be actors on the system. The roles of these self-provisioned actors are determined within LPL source code specification for this application.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



What two types of controls does Landmark Security provide?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

What is the impact of running security with all roles set to “all access”?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

List four security object types.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Which one of the following is an example of a securable object?

a) Async b) Key fields c) Grid node d) Web server

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

158 Lesson 12: Landmark Configuration Console © 2014 Infor Education

Lesson 12: Landmark Configuration Console Estimated time

2 hours

Learning objectives


Describe the purpose and role of the Configuration Console. Describe the differences between configuration and personalization. List the items a user can personalize. Identify the items available for configuration. Describe how to assign the Configuration Console Access to an administrator user for all

configuration categories including: Application objects, Security, Web services, and MIME types.

Define why you would apply MIME configurations. Provide concrete examples of using the cdexport and cdimport utilities.

Topics Configuration Console overview Configuration and personalization Security classes Configuration data utilities Configuration development process Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuration Console overview

Infor Configuration Console User Guide

The Configuration Console is a tool within the Infor Rich Client which enables administrators to make several types of changes that affect Landmark users.

Application: Look-and-feel changes to menus, pages, and various user interface objects and actions associated with a business class, and configuration changes for features that apply across a data area, including: Enabling/disabling data translation (multi-language field configuration) Creating business subjects Creating and modifying MIME types

Security: Creation and modification of security classes, actors, identities, and roles

In addition, you can use the Configuration Console for the maintenance of actor, identity, and role records.

Web services: Creation of new web services

Web services enable non-Landmark systems to view or update Landmark data.

When you make configuration changes through the Configuration Console, the changes apply to all users. This is in contrast to the changes made through the My Personalizations console, which apply only to the user making the change unless that user has the privilege to make the change global and chooses to do so.

A personalization will trump a global configuration—that is when a user personalizes his/her experience, that personalization will be the default for that employee's view, not the configuration made by another user and set to default.

The Configuration access for administrators will be a role tied to a security class, allowing access to the Configuration Console. All end users will be able to use "My Personalization."

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuration and personalization

Configuration

Configurations are created as overrides to the basic application functionality. We start with the definitions that are delivered with the product.

The client may choose to apply configurations redefining the delivered application to become the new global standards.

By default, configurations also override any delivered updates to the application. You do have the option of allowing the application updates to take effect.

Personalization

A user may override the configurations by personalizing his/her experience. That personalization will be the default for that employee's view, not the configuration made by the administrator. Personalizations allow the end user to customize application components to help them increase efficiencies by modifying forms, menus and pages by:

Hiding irrelevant fields to their workflow. Changing label text to make the fields stand out on the form. Rearranging fields to make a form easier to navigate. Creating a main list menu to efficiently navigate from form to form. Creating watches to send an alert when certain conditions are met.

The end user has the option push the personalization to global users with the “Make Global” options.

Both personalization and configuration can be inactivated, deleted or further modified, all in real-time.

What can be personalized?

Application components (listed below) can be personalized by any end user.

Menus

End users can create and modify menus to hold application objects (pages and lists) that meet their specific job needs.

Pages

End users can add or remove lists from the page and change the layout to suit their preferences.

Lists

End users are able to modify lists by adding fields, deleting fields, and rearranging fields to make their work efforts more efficient.

Forms

Like lists, end users can add related fields or delete irrelevant fields to their form. Forms are built very dynamically in Landmark—what shows up depends on who the user is etc. In

the console, the editor is much more abstract, more powerful and somewhat more risky. Configurations are made by adding properties that closely resemble LPL statements.

Labels

End users can change the appearance of a label on a field, hide fields, or change the name of the field.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Customization

Any application component that can be personalized can also be customized.

Application components New fields, (e.g., in forms) User actions Action requests

Data translation (DET) Personal watches / Alerts MIME types

MIME types

MIME type – ex, define an “exe” MIME type and build application code around it to prevent the customer from loading the executable.

MIME types form a standard way of classifying file types. A MIME type has two parts: a type and a subtype, and they are separated by a slash (/).

One example, the MIME type for Microsoft Word files is application and the subtype is msword. Together, the complete MIME type is application/msword.

We deliver a standard set of MIME types to the client. Through Configuration Console, the client can configure the system to add or delete MIME types to meet their requirements.

Configuring MIME types allows you to control the types of attachments that can be uploaded into the system, for example, a candidate needs to attach a resume in the Candidate Space. What types of files will you allow them to attach? A Word document or PDF?

By controlling the type of files you allow into the system you will prevent and limit harmful or malicious attachments such as executable files.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Security classes

Security

Lawson delivers a set of security classes with the Landmark Environment and with each Landmark application.

Security Actors Roles Identities Security classes

These delivered security classes have names ending in "_ST" to indicate that they belong to the "standard template" set of security classes.

You cannot modify these security classes, if these do not suit your business needs, you must create customized security classes. Customized security classes can then be assigned to roles, and actors (users) can be assigned to the roles, so that they have the appropriate access to your Landmark system.

You create customized security classes in the Configuration Console, which is accessible through the Infor Rich Client. You can create an empty security class or, as is usually easier, you can create the new security class by copying an existing class. Once you create a new security class, you can add or modify security rules for that class in the Configuration Console.

If you have created new security classes in a test environment, you can use various utilities to export the data and then import it to your production system.

Example: Use the scexport z zipfilename dataarea [SecurityClass…] to export a security class. Use the scimport [-f] z zipfilename dataarea [SecurityClass…] to import in to your production system.

Configuration Console security access

A user or administrator must have one of the security roles below to access the Configuration Console and perform configuration tasks:

ConfigurationAccess_ST DataMenuAccess_ST SecurityConfigAccess_ST ConfigAdminAccess_ST GlobalUIConfigAccess_ST

Following are configuration tasks you might want to perform and the relevant security classes needed for those tasks.

Application configuration (menus, pages, lists, and forms)

To modify application objects, a user must have the GlobalUIConfigAccess_ST security class or its equivalent.

MIME types and web services configuration

To create or modify MIME types and web services through the Configuration Console, a user must have the GlobalUIConfigAccess_ST security class or its equivalent, plus create and change action access for the appropriate module and business class. In the case of MIME types, a user needs access to the la module and the MimeType business class. In the case of web services, a user needs access to the wsbuilder module and the WebService business class.

Security class configuration

To modify security classes, a user must have the SecurityConfigAccess_ST and the ConfigAdminAccess_ST security classes or their equivalents.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Actor, identities, and roles

To work with actors, identities, and roles in the Configuration Console, a user must have the SecurityConfigAccess_ST security class or its equivalent, as well as a security class that gives access to actors, identities, and roles, such as UserAdminAllAccess_ST. (If a user has the UserAdminAllAccess_ST security class but not the SecurityConfigAccess_ST security class, that user can work with actors, identities, and roles outside of the Configuration Console.)

In this next exercise, you will assign the ConfigurationAccess_ST role to the actor lawson. After you have the role assigned, you will see the Configure task in your Start menu:

Assigning the ConfigAccess_ST security class to a role

Demo: Assign the ConfigAccess_ST security class to a role

Your instructor will demonstrate how to assign the ConfigAccess_ST security class to the user lawson via the Configuration Console.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.1: Assign the SecurityConfigAccess_ST security class to user lawson via the Configuration Console

In this exercise, you will assign the Security ConfigAccess_ST security class to lawson via the Configuration Console.

Exercise steps




4. Double-click User Management from the GEN data area.

5. Click Actor Management.

6. Click the Filter icon (magnifying glass).

7. Type lawson in the Last Name field to locate the user lawson.

8. Press Enter.

9. Select and double-click lawson from the list of results.

10. Click the Roles tab.

11. Verify the role ConfigurationAccess_ST is assigned to the lawson user.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Accessing Configuration Console

Once the security class is assigned to the role, you can log in as lawson and launch the Configuration Console.

Demo: Access the Configuration Console

Your instructor will demonstrate how to access the Configuration Console.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.2: Access the Configuration Console

In this exercise, you will access the Configuration Console.

Exercise steps

1. Navigate back to the Infor Rich Client Admin on your desktop.

2. Click the Start > Configure. [Alternatively, you may also select Security Configuration. Which option is available, depends on the security classes assigned to your roles.]

3. Select the type of configuration you want to work with: Application, Security, or web services.

Creating new security classes using Configuration Console

You create customized security classes in the Configuration Console, which is accessible through the Infor Rich Client. You can create an empty security class or, as is usually easier, you can create the new security class by copying an existing class. Once you create a new security class, you can add or modify security rules for that class in the Configuration Console.

Demo: Copy a security class and modify its rules using Configuration Console

Your instructor will demonstrate how to copy a security class and modify its rules using Configuration Console.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.3: Copy a security class and modify its rules using Configuration Console

In this exercise, you will copy the ActorAdminAccess_ST security class using Configuration Console. Once copied, you will modify the security rules to have limited actions to the BusinessClass > Actor.

Exercise steps

Part 1: Copy the security class

1. Click Start > Configure > Security in Infor Rich Client. The Configure Security window opens.

2. Expand the Security Classes list in the left pane.

3. Select ActorAdminAccess_ST.

4. Click the Copy button at the top of the right pane. The Copy ActorAccessAdmin_ST window opens.

5. Type ActorAccessAdminLimited in the Security Class Name field.

6. Click OK.

7. Click the back arrow in the left pane.

8. Type <a short description> in the Description field on the right pane. Example: Limited access security class.

9. Click the Save button.

Part 2: Modify the security class rule from All Actions to Inquire and Update only

1. Click the Configure button in the right pane.

2. Expand BusinessClass in the left pane.

3. Select Actor.

4. Click the Edit Policy button on the right lane. (It is the pencil icon.)

5. Click the select arrow in the For Actions field.

6. Highlight the All Actions data item from the right pane and click the Remove button to move it to the left pane.

7. Select all inquiries from the left pane and add it to the right pane by clicking the Add button.

8. Select all updates from the left pane and add it to the right pane by clicking the Add button.

9. Click the Save button to save the edits to the ActorAccessAdminLimited security class. Notice the changes to the BusinessClass > Actor is limited to Inquiry and Update actions only rather than All Actions.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Restricting a MIME type using Configuration Console

Demo: Restrict a MIME type using Configuration Console

Your instructor will demonstrate how to restrict a MIME type using Configuration Console.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.4: Restrict a MIME type using Configuration Console

In this exercise, you will restrict a MIME type using Configuration Console.

Exercise steps

1. Click Start > Configure > Application in Infor Rich Client. The Configure Application window opens.

2. Click DataArea.

3. Select Mime Types.

4. Double-click application/futuresplash. The Mimetype window opens.

5. Select Blocked in the Status field.

6. Select <today’s date> in the Effective Date field.

7. Click Actions > Save. [Alternatively, you can click the Save icon.] @ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuration data utilities To copy specific configurations, such as security classes, several data import and export utilities can be used. It is recommended you take an export of your configurations prior to any updates applied to your system. Also keep in mind that you should review your application update notes so that you are aware of which forms or business classes are affected and prepare to manually update either the end user’s personalizations or the configurations that have been set up for your users.

To view the business class data stored for each user’s personalizations:

Start > Data > repository > Business Classes and double-click the User* business classes.

Security class copy

sccopy [-f] dataArea securityClass newSecurityClass [existingSecurityClass]

The sccopy utilities enable you to create a new security class by copying an existing one, or to modify an existing security class by overwriting it with another security class.

Security class export

scexport z zipfilename dataarea [SecurityClass…]

The scexport utility enables you to export the customized security classes for a data area to a zip file so that they can be imported to a different system.

Security class import scimport –l z zipfilename

scimport [-f] z zipfilename dataarea [SecurityClass…]

The scimport utility enables you to import the security classes into a data area from a zip file created through scexport or delivered by Lawson.

Security class update

scupdate [F | -f] –z zipfilename dataarea [dataarea…]

The scupdate utility enables you to update the security classes for a data area from the zip files containing the delivered framework and application data area security classes.

Configuration data export

cdexport –o OutputDirectory dataarea [--application --authsecurity – mimetype –processflow –webservices] [--noactor | --onlyactor] [Actor …]

cdexport –z ZipFile dataarea [ --application –authsecrutiy – mimetype –processflow –webservices] [--noactor | --onlyactor] [Actor …]

The cdexport utility enables you to export configuration data for a Landmark system to either a directory or zip file. This data includes configuration data for applications, security authorization, MIME types, Infor Process Automation, and web services. You can choose to export all configuration data or just select types of data. You can also choose to export configuration data for specific actors or for the “global” actor.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Export the ActorAccessAdminLimited security class using Configuration Console

Your instructor will demonstrate how to export the ActorAccessAdminLimited security class using Configuration Console.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.5: Export the ActorAccessAdminLimited security class to your desktop using Configuration Console

In this exercise, you will export the ActorAccessAdminLimited security class using Configuration Console.

Exercise steps

1. Navigate back to Rich Client on the desktop.

2. Click Start > Configure > Security. The Configure Security window opens.

3. Select the Actions > Export.

4. Expand the Security Classes section and select ActorAccessAdminLimited.

5. Click the Browse button to save the exported configuration to your desktop.

6. Click Export to export the security class configuration to your desktop.

Configuration data import

cdimport –l InputDirectory | ZipFile

cdimport –l InputDirectory | ZipFile [-beioquVNF] [-M nn] [-x transactionSize] dataarea –application –authsecurity –mimetype – processflow –webservices –keepactor {--noactor | onlyactor} [Export_Actor[=Import_Actor] …] [--noerrorfile] [--noenverrorfile]

The cdimport utility enables you to import configuration data for a Landmark system from either a directory or zip file created through cdexport. This data includes configuration data for applications, security authorization, MIME types, Lawson Process Automation, and web services. You can choose to import all configuration data or just select types of data. You can also choose to import configuration data for specific actors of for the “global” actor.

Unless you specify that error files are not created if there are import errors, zip files containing CSV and log files of the errors are created in the current directory. The names of the error files are based on the data area you are importing the data into.

This section describes a few tips and recommendations meant to make your use of the Configuration Console more effective.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuration development process When you create configurations in the Configuration Console, it is best to do so in a provisional or test scenario before making the configurations available to all users. If you make the configuration changes directly to a production environment, the changes will be applied as soon as you save them in the Configuration Console. There are two ways to test the changes before committing them to all users:

1. Use the My Personalizations console to try out changes.

The My Personalizations console allows a user to make most of the same changes as an administrator who uses the Configuration Console. However, those changes are available only to the user who made them. Thus, you can review the changes and then use the Make Global button in My Personalizations to make the configuration available to all users. The configuration will then be listed in the Configuration Console where you can modify it further.

b. Use a test environment to develop configuration changes.

If you take this approach, you can fully develop the configuration changes you want and then move them to the production environment by using the configuration export and import utilities. For more information, see the previous section on Configuration data utilities.

Should you edit the LPL?

In a word, no. LPL is the Lawson Pattern Language, which is the language that many of the source files in Landmark are written in, such as those for business classes and user interface objects. In the Configuration Console, the LPL is exposed through Edit LPL buttons and "view base LPL" links. To edit the LPL you would need a detailed knowledge of it and of the application objects it is for. This is beyond the scope of this Training Workbook.

However, you may find it useful to view the LPL in order to better understand possible configuration changes. For example, you might want to view the LPL for your configuration and then compare that to the original LPL.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Describe the purpose and role of the Configuration Console.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Describe the differences between configuration and personalization.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

List the items a user can personalize.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Identify the three security roles a user must have to access the Configuration Console and perform configuration tasks.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 13: Distributed Security Package, Infor Security Administration, and federation overview Estimated time

2 ½ hours

Learning objectives


Describe the components of the Distributed Security Package (DSP). Identify where the Infor Security Administration is installed. Describe the Infor Security Administration purpose and features. Describe how to navigate within the Infor Security Administrative tool. Describe federation and value for multiple systems on administration, authentication, and

authorization. Define synchronization and potential conflicts.

Topics Distributed Security Package overview Infor Security Administration overview Federation overview Synchronization overview Check your understanding

The content in this lesson is NOT for installation purposes. The purpose is to provide information for the administrator on what has been installed by the installer.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

172 Lesson 13: Distributed Security Package, Infor Security Administration, and federation overview © 2014 Infor Education

Distributed Security Package overview

Infor Lawson Distributed Security Package Installation Guide Infor Security Services Configuration Guide

The Distributed Security Package (DSP) is available both as a LifeCycle Manager installation package and as a Java installer package.

Distributed Security Package delivers the following components of the Infor Security solution:

Distributed Single Sign-on (DSSO)

The DSSO component enables single sign-on between applications on remote servers and Infor Lawson System Foundation.

Infor Security Services (ISS)

Provides user provisioning, synchronizing, and federation services in environments where Infor Lawson System Foundation and Landmark Technology Runtime are installed and federated.

Infor Security Administration (ISA)

A web browser accessible administrative tool for managing actors/users and for configuring the security system for Infor Lawson System Foundation (LSF) and Infor Landmark Technology Runtime.

Distributed Security Packaging and deployment

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


The DSP can be downloaded from the Infor Xtreme Support site under Download > Products > Technology > Infor Lawson System Foundation > Lawson Security. Apply all required patches to Lawson Core Technology and read any readme documents for the Lawson Security release being applied.

Infor Security Services requires the installation of scwebadminapp.war and scwebamonitorapp.war within the IBM WebSphere Application Server to support the web administrative tool.

IBM Integrated Solutions Console

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Infor Security Administration overview

Infor Security Administration Configuration Guide

Infor Security Administration (ISA) is a web browser-accessible administrative tool for managing actors/users and for configuring the security system for Infor Lawson System Foundation (LSF) and Infor Landmark Technology Runtime.

Infor Security Administration tool

The tool is used to:

Add and maintain actor / user records, including all attributes related to users. Federate multiple systems, such as Infor Lawson System Foundation and Infor Landmark

Technology Runtime.

For example, suppose users at your site use the Talent Management suite (an application suite based on Infor Landmark Technology) and other users run Infor Lawson Accounts Payable (AP) (an application based on Infor Lawson System Foundation), and some use both applications. Infor Security Services lets you add all users to both systems at one time.

User administration through ISS is recommended in LSF 10. This tool will keep the LDAP resources of LSF and the GEN actors of Infor Landmark Technology Runtime in sync.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Access Infor Security Administration (ISA)

Your instructor will demonstrate how to access Infor Security Administration (ISA).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.1: Access Infor Security Administration (ISA)

In this exercise, you will access the ISA tool and explore the available areas.

Exercise steps

1. Access IE > Favorites > Infor > Infor Security Administration (ISA).

2. Type lawson in the User field.

3. Type Tr@in123 in the Password field and press Enter.

4. Explore the Resources, Configuration, SSO, Monitoring, and Federation menus.

ISA is only accessible by resources/actors with the LSSSuperAdmin role.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Federation overview

Federating

Federating a system means associating two Infor Lawson systems (for example, Infor Lawson System Foundation and Infor Landmark Technology Runtime) so that users (actors or people resources), roles (which include security classes), and groups can be "seen" by either system.

The following diagrams illustrate the problem that federating solves.

Non-federated example

Before federation users/actors who use content on both Infor Lawson platforms must log in to each separately. This is what your system looks like before the installer federates.

@

Cop

yrigh

t 201

4 Info

r

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Federation example

After the federation procedure is performed using ISA, users/actors can log in to either system (ILSF or ILT) and use applications they have been granted access to. New users/actors are added through ISS.

After a system has been federated, you should always use Infor Security Administration (ISA) to add or update users. This will prevent you from having to run the federation procedure multiple times.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Federation prerequisites

The federation prerequisites have been or will be completed by your installer. Before systems (for example, Infor Lawson System Foundation and Infor Landmark Technology Runtime) are federated, the following prerequisite procedures must be completed:

Infor Lawson System Foundation:

Perform a complete backup of your LDAP user repository. Back up all security-related Infor Lawson configuration files in LAWDIR\system.

lsservice.properties ssokeystore

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


authen.dat .ssortruststore

Verify the Lawson LDAP schema has been updated if coming from version 9.x. Verify the Readme file for Lawson Security has been examined and all requirements for patching

or updating to LSF or DSP have been completed.

Infor Landmark Technology Runtime:

Perform a complete backup of GEN data area. Back up all security-related Infor Lawson configuration files in LASYSDIR:

lsservice.properties ssokeystore authen.dat .ssortruststore

Both systems:

Complete all authentication-related configurations. Both pre-federated systems must use the same authentication protocol (LS as STS or Kerberos). If LS as STS then both systems need to either be bound or the password natively authenticated.

Test user authentication on each system before federating. To test authentication, log in to LSF Infor Lawson for Workspace or Landmark Rich Client. This process will cause the SSOServlet to run proving that authentication is working prior to federating.

After federation, an administrator is required to keep the data in sync. If a change to Primary Authentication Service or removal of federated systems is required then contact Infor Global Support or Infor Consulting Services to understand the impact on your system before using ISA to execute.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Synchronization overview Federated systems (LSF and Infor Landmark) have been synchronized initially. However, if ISA is not used as the primary tool for updating users then resynchronization may be required.

Synchronization occurs for the following areas:

Roles Actors Services Domains Endpoints Endpoint groups Identities

Demo: Explore the federated systems and synchronization

Your instructor will demonstrate federation and synchronization.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.2: Explore the federated systems and synchronization

In this exercise, you will access the ISA tool and explore the federated systems and examine the synchronization areas. You will use Ussplu143 (LSF).

Exercise steps

1. Access IE > ISA > Federation > Federated Systems.

2. Note that the systems of LSF are the main system and federated to the remote system of Infor Landmark.

3. Note that ISA is showing a connection between the two systems.

4. Note the areas of Roles, Actors, Services, Domains, Endpoints, Endpoint Groups, and Identities are all marked green.

5. Note the Sync column. This column allows the ability to synchronize the remote system (Infor Landmark) to LSF.

An important job of the federation wizard is synchronizing systems that make up the federation. Synchronization means determining if conflicts exist between the systems being federated. Conflicts occur when one of the systems has the same record (for example, the same security role name exists on both systems). The wizard assists in the process of resolving identified conflicts.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


The wizard groups conflicts by type of data. The sub-sections that follow describe the choices that are available in the wizard to resolve conflicts found between the “Local” system being federated TO and the “Remote” system being federated FROM.

Infor Lawson System Foundation is always the “Local” or “To” system due to ISS being installed on that server. Infor Lawson Landmark Runtime is always the “Remote” or “From” system.

Role conflicts

A role conflict means that the synchronization process has found that the system it is currently attempting to federate has at least one role name in common with the system to which it is being federated. The wizard presents the following choices.

Federation choices Default behavior Risks/Implications

Ignore all conflicts Applied to all conflicts The default behavior results in the roles being merged so that they contain all security classes for the role on each system. All users from both systems are assigned the role.

Take this action if you know that the role provides access to classes that users on both systems should have.

This action could have potential security risks. For example, you have a role on System A called "AppAdmin" that gives access to all programs and data in the Accounts Payable (AP) system. On System A this role is assigned to the AP department managers. On System B, you also have a role called "AppAdmin" that gives access to all programs and data in the Talent Management system that is assigned to HR managers. If you selected "Ignore all conflicts" in this case, the AP managers would be able to see confidential HR information and HR managers would have access to enterprise vendor payment tools.

Rename the role on the "local" machine (the machine that you are federating to) OR Rename the role on the "remote" machine (the machine that you are federating)

Using the AppAdmin role as an example, and assuming that System A is the local machine, if you select Rename the role on the local machine (new name = APAppAdmin), the remote system would retain the role AppAdmin role (full access to Talent Management) and System A users would be removed from the role. The role APAppAdmin would also exist on the federated system and only the System A users of the "old" AppAdmin role would be attached to APAppAdmin.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Do not include spaces in role names; use an underscore as a separator if needed.

Role conflicts example

Actor conflicts

Actor conflicts occur when the unique ID of an actor (user) is found on both systems but some attributes that must be the same (for example, LastName and FirstName) are not the same. This could happen for a number of reasons, including, a misspelling of LastName on one system, using a nickname for FirstName on one system, or incorrectly assigning a unique ID.

When the synchronization process identifies actor conflicts, they are displayed in a list. The wizard presents the following choices:

Handle all conflicts in the same way. For this response, you select Update Local Actor or Update Remote Actor. With this choice you are indicating that when a conflict exists, the selected machine (Local or Remote) contains the correct information. Match differences on the other system to this system's information.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Handle each conflict individually. For this option, you select a conflict from the list and, when a dialog box showing the attributes that are in conflict appears, make changes as needed to the attributes.

Actor examples

Service, domain, endpoints, and endpoint group conflicts

Service conflicts arise when both systems have a service with the same name. These conflicts are handled the same as roles.

Identity conflicts

An identity conflict arises when the same identity is found across both systems. These conflicts are handled the same as actors. Example: The SSOP identity and the SSOPV2 identity password do not match.

Resolve conflict icons

An example of the kinds of icons that the synchronization process displays when it encounters a conflict differs depending on the type of resource and type of conflict. In general, the icons to the left of the blue vertical bar are for displaying conflicts. The icon to the right is for taking action.

BusinessClasses Actor = jsmith

ActorIdentity = SSOPV2 Agent = Co. & Emp.

Attributes First Name = Jane

RM ID = jsmith Last Name = Smith

Manage Identities SSOP = jsmith

PROD_Employee = Co. & Emp.

Landmark Lawson System Foundation

Lawson Security Server

LDAP PeopleObject Attributes in Resource

Management FirstName

ID LastName

GEN DB Actor

ActorIdentity LTM DB

Agent = Co. & Emp. ActorContext = HROrg User: jsmith

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Conflict icons

Synchronization conflicts

Conflicts occur when one of the systems has the same record. For example, the same security role name exists on both systems. This is only true for a role, service, domain and endpoint groups, but not for actor, endpoints, and identities.

Federation options

There are several options available for configuring LSF and Infor Landmark Technology Runtime which will allow for federation.

LSF and Infor Landmark Technology Runtime installed on the same server

This is recommended only for those customers who will use Infor Landmark Technology Runtime only to support the Infor Process Automation application. This type of installation will reduce the overall footprint of servers for Infor.

LSF and Infor Landmark Technology Runtime installed on separate servers

This is recommended for those customers who will have additional Infor Landmark applications installed on the Infor Landmark Technology Runtime. This is normally recommended due to performance and required resources of the LSF applications and Infor Landmark applications.

LSF and Infor Landmark Technology Runtime sharing the same database instance

This is required for Infor Landmark applications with a dependency on LSF tables. For example, Contract Management.

LSF and Infor Landmark Technology Runtime in separate database instances

This is possible for any Infor Landmark application with no dependency on LSF tables. For example, Infor Talent Management.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Federation review

The following diagram illustrates federation with Infor Landmark.

Federation with Infor Landmark

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo: Provision a new user in the federated system

Your instructor will demonstrate how to establish a new user in both LSF and Infor Landmark Technology Runtime in the federated system.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.3: Provision a new user in the federated system

In this exercise, you will access the ISA tool and establish a new user for both LSF and Infor Landmark Technology Runtime required access. In LSF 10, an actor must be established in Infor Landmark Technology Runtime to establish Infor Process Automation users.

Exercise steps

1. Access IE > Favorites > INFOR > Infor Security Administration.

2. Type lawson in the User name field.

3. Type Tr@in123 in the Password field and press Enter.

4. Select Resources > Manage Users.

5. Select the Basic tab.

6. Type or select the following information:

Field Data

Actor ID vstudent1

Roles Connect (check these options): BatchRole Employee (ESS) Employee_ST (Employee Space) InforLawsonforWorkspaceBookmarks LSF Application All Access PDL ProcessServerAllAccess_ST

Given Name Vivian

Family Name Student1

Email Address [email protected]

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

mailto:[email protected]


Field Data

ISOLanguage en (en represents English)

Run As Enabled No

Disabled No

7. Click Next. The Landmark Server tab displays.

8. Type the following information:

Field Data

Municipality Chicago

State Province IL

Country US

Address Line 1 123 Home Street

9. Click Next. The LSF screen displays.

10. Type the following information:

Field Data

ProductLine APPS10

ISO Local en

Resource Name Vivian Student1

11. Click Add User. The following message displays: User has been added successfully.

12. Select Yes in the Identity Configurations page.

13. Select the SSOP service.

14. Type the following information for the SSOP service:

Field Data

User vstudent1

(if Kerberos, format is [email protected])

Password Tr@in123

(would not be required if LDAP bind)

Confirm Password Tr@in123

15. Click Add.

16. Click OK. The following message displays: Operation completed successfully.

17. Select the LSFENV service.

Field Data

Domain User LU141TRAINING\vstudent1

Password Tr@in123

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Field Data

Confirm Password Tr@in123

18. Click Add.


20. Select the APPS10_EMPLOYEE service.

Field Data

Company 4321

Employee 1044

21. Click Add.


23. Select IE > File > New Session to access the Ming.le™ home page.

24. Log in as vstudent1. Notice the Infor Lawson Applications is not available, only Infor Ming.le™ entry home page displays.

25. Access the Rich Client shortcut link on the desktop from Ussplu143 (LSF).

26. Log in as vstudent1.

Demo: Update an existing resource in ISA

Your instructor will demonstrate how to create a user through Infor Security Administrator and synchronize using ISS to properly establish the record in the federated systems.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 13.4: Update an existing resource in ISA

In this exercise, you will establish a user through Infor Security Administrator and use the ISS synchronization process to establish the record properly in the federated systems. You will use Ussplu141 (Landmark).

Exercise steps

1. Access IE > Favorites > Infor > ISS.

2. Select People in the Search area.

3. Type vstudent1 in the Search field.

4. Click the Pencil (edit resource icon) next to the People record for vstudent1.

5. Select the Basic Information tab.

6. Click the Roles field to edit.

7. Select the InforLawsonForWorkspaceAccess role.

8. Move the role to the right box to connect.

9. Click OK.

10. Click Update User. The Success! Update completed Successfully message displays.

11. Click OK.

12. Access IE > File > New Session > Ming.le or refresh the open vstudent1 IE session from the earlier step.

13. Log in as vstudent1. Notice the Infor Lawson for Workspace Lawson Applications is now available.

ISS to synchronize updates

You should execute all user provisioning in the ISS Administrator tool. If Infor Security Administrator, loadusers, ssoconfig, RM Update node, Actor Management, secadm, or Landmark node is used, then potentially user data across federated systems may no longer be synchronized.

To validate the data is synchronized the ISS Administrator tool is used to resynchronize and any conflicts or issues should be resolved.

Demo: Synchronize federated user data

Your instructor will demonstrate how to synchronize a user added through Infor Security Administrator using ISS to establish the record properly in the federated system.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Exercise 13.5: Synchronize federated user data

In this exercise, you will validate AMckinley and VSantos are not established in LSF before federation. After validation, you will synchronize and then re-validate that the users now exist in the federated environment. You will use Ussplu143 (LSF).

Exercise steps

Note: At this time the Landmark GEN actor table has received new actors from earlier in Lesson 10, but the LSF Lawson LDAP did not receive these resource records creating out of sync in the federation user data.

1. Click the Security Administrator desktop shortcut.

2. Type lawson in the User Name field.


4. Select User Management > User Maintenance.

5. Confirm AMckinley and VSantos are not listed as a resource. (Search for AMckinley and VSantos Resource ID.)

6. Locate the security_provisioning.log in LAWDIR\system (C:\LSFENV\law\system) and delete it. You should remove this log file before the synchronization to limit the records to only this federation synchronization run.

7. Access IE > Favorites > Infor > ISS > Federation > Federated Systems. (You still should use Ussplu143 (LSF).)

8. Click the Sync icon next to the Landmark federated server.

9. Select Yes on the Federation Manager prompt for synchronization of data between systems.

10. Click the Ignore icon for Role conflicts. (All roles are in conflict because they already exist from previous sync.)

11. Select the available Synchronize option for the actors as no conflicts will be found.

12. Click the Ignore icon for Services conflicts. (All services are in conflict because they already exist from previous sync.)

13. Click the Ignore icon for Domain conflicts. (All domains are in conflict because they already exist from previous sync.)

14. Select the available Synchronize option for the Endpoints as no conflicts will be found.

15. Click the Ignore icon for Endpoint Groups conflicts. (All endpoint groups are in conflict because they already exist from previous sync.)

16. Select the available Synchronize option for the Identities as no conflicts will be found.

17. Click OK on the Federation Manager.

18. Select Configuration >Tasks > Manage Tasks.

19. Verify no failure tasks/records exist.

20. Click the Security Administrator desktop shortcut. (You are still on Ussplu143 (LSF).)



23. Click User Management > User Maintenance.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


24. Confirm AMckinley and VSantos are now resources. (Search for AMckinley and VSantos Resource ID.)

The synchronization process should be executed upon any use of user administration tools or utilities outside of the Infor Security Services (ISS) administrative tool. The “ignore” on conflicts should be used only after analysis and verification of that desired option.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



1) Infor Security Administration is delivered in what manner for installation and updating? What server is the ISS component installed on?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Identify two major administration functions that will be performed in ISA. (Hint: There are more than two.)

______________________________________________________________________ ______________________________________________________________________

3) What is the major benefit of having systems federated?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@

Cop

yrigh

t 201

4 Info

r

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

192 Lesson 14: Infor Process Automation © 2014 Infor Education

Lesson 14: Infor Process Automation Estimated time

2 ½ hours

Learning objectives


Identify the two components that run IPA (IPS/IPD). Describe the user setup for Process Automation. Define what a workunit is and what tools are available for a system administrator to monitor its

process. Describe the tracking of IPA (work units). Describe the function of thread pools. Identify ways to manage security in IPA.

Topics Infor Process Automation overview Infor Process Automation user setup Monitoring Infor Process Automation work units System administration Grid configuration for IPA Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Infor Process Automation overview

Infor LSF Using IPA Configuration Guide Infor Process Automation Admin Guide Infor Process Designer Installation Guide

Infor Process Automation

Infor Process Automation is a tool for automating business processes. For example, if workers at your organization perform a procedure (a series of tasks) repeatedly, automating the procedures makes sense. Doing so ensures that all steps in the procedure and that they are performed and in the correct sequence.

Infor Process Automation is the umbrella term for the business process modeling system that has both server-side and client machine software components.

Infor Process Designer

Infor Process Designer (IPD) is a desktop point-and-click tool for creating processes. A process is the XML file of instructions that carries out the process instructions.

Any user at your site who will be creating processes (these users are typically business analysts, power users, and software developers), will need to have the tool installed on their desktop machines.

1. Create – Process designs (workflows) are created in the Infor Process Designer.

2. Publish – Publishing a process design distributes it to an appropriate Infor Process Server node.

3. Interact – Users interact with Infor Process Automation or experience its results via the Lawson canvas (including Administration.)

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Infor Process Designer

Infor Process Automation Inbasket

Within a process, information can be routed to users to take action. Information can be passed to one user, based on the roles a user is assigned, the HR reporting structure, or could be routed to multiple users. Routed work is sent via the Inbasket.

The Inbasket can be in a Rich Client, Infor Smart Office, Infor Ming.le™ user interfaces, Infor Lawson Business Intelligence (LBI) dashboard or via direct web URL link.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Infor Process Automation user setup All users can be added as a Process Automation user to use the process flow actions within the application. These users will first need an Actor record prior to adding them as Process Automation users. You add these users through the Rich Client only.

Demo: Explore Infor Process Automation

Your Instructor will demonstrate how to access and navigate Infor Process Automation and the Rich Client Infor Process Server Administration areas.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 14.1: Explore Infor Process Automation

In this exercise, you will access Infor Process Designer and Rich Client’s Infor Process Server Administration areas. You will use Ussplu141 (LMK).

Exercise steps

1. Launch the Ussplu141 server.

2. Click the Infor Process Designer shortcut on your desktop.



5. Click OK.

6. Select File > New Infor Process File.

7. Select the Palette tab.

8. Drag the Email Activity node (under Common) to the process between Start and End nodes.

9. Select Connection (under Main) and click Start node then arrow to Email node, and Email node to End node.

10. Highlight the Email Activity node.

11. Select the Properties tab.

12. Type the following values on the Email Properties:

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Field Value

To your email address

From [email protected]

Subject Testing IPA

On the Error Tab Select Stop Process option

13. Select File > Save as > LandmarkTest (.lpd).

14. Select Upload Process.

15. Type a <description> in the Description field.

16. Accept other defaults.

17. Click OK.

18. Click the Rich Client desktop shortcut.

19. Type lawson in the LOGIN field.


21. Select the data area (upper left) and set to APPS10.

22. Double-click the Process Board Process Server Administration.

23. Select Scheduling > By Process Definition.

24. Select Actions > Create.

25. Select the LandmarkTest Process Name.

26. Type LandmarkTestIPA in the Work Title field.

27. Select Actions > Save.

28. Select Actions > Start.

29. Click X to close Process Triggers.

30. Select the Back < arrow to return to the Process Board main menu.

31. Select Administration > Work Units > Work Units.

32. View your Work Unit created.

Demo: Assign a user task using IPA

Your instructor will demonstrate how to assign a user task using IPA.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

mailto:[email protected]


Exercise 14.2: Assign a user task using IPA

In this exercise, you will assign a user task to Vsantos using IPA.

Exercise steps

Part 1: Configure a user


2. Select LTM.

3. Double-click Process Server Administrator > Configuration > User Configuration. The Users window opens with three views: Users, User Tasks, User Filters.

4. Double-click Users.


6. Click the Select arrow in the User field.

7. Type Vsantos in the Actor ID field and press Enter.

8. Highlight Vsantos and click Select.

9. Select the Is Filter Enabled check box.


Part 2: Assign a user task:

1. Click Actions > Create on the User Task form.

2. Select the CompAnalyst task in the Task field.

3. Click Save & New (diskette with plus sign +).

4. Select HR Administrator task in the Task field.

5. Click Save and close the form. The Vsantos Actor should now display two tasks: CompAnalyst and HR Administrator tasks.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Monitoring Infor Process Automation work units

Infor Process Automation server-side tools for administrators

Infor Process Automation delivers menus and other tools for system administrators to configure, launch, maintain, and troubleshoot processes. These tools are accessed through Infor Landmark Technology.

When a process runs, it generates work units, individual work items. For example, a purchase order approval process might require approval from several staff members. The approval action request that appears in each person's Inbasket is a work unit.

Infor Process Server Administrator

The Process Server Administrator menu provides a Work Units menu which provides tools for monitoring the process of work units. The following functions are available:

Work Units

Move a work unit or work units to history Delete work units View activity and error logs Clear logs and activities (Logs are also in your installation location/system/lps.log)

History

Move work units to history Delete work units Clear logs and activities

Tracking

Create a comparison work unit Output to analytical data

Clear work unit and activity logs Delete activity and variables

Analysis

Available on the Process Server Administrator Status

Pick specific states to chart or view all states Pie, bar or list view Exportable to CSV, print to file, or create a report

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Process Server Administrator

Analytics

Process Execution Time Comparison Execution Time

Execution time

Comparison

Running processes can generate a large amount of data in the database. Decisions about how often to archive and delete are based on how many processes you run and how much runtime data the work units generate.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


For example, if your processes generate a moderate amount of data, you might want to delete workunit data monthly. You could run the delete procedure on the last day of the month (on March 31, delete February data).

If your processes generate a large amount of data, you might want to delete the previous week's data every Monday morning.

Enabling autopurge

Autopurge can automatically delete some runtime data for completed work units.

Automatically deletes data in specific tables: PfiActivity PfiActivityVariable

Enabled when parameter is added to system

Demo: Enable an autopurge

Your instructor will demonstrate how to enable an autopurge.

______________________________________________________________________ ______________________________________________________________________

Exercise 14.3: Enable autopurge

In this exercise, you will enable an autopurge.

Exercise steps




4. Select APPS10.

5. Click Start > Application > Process Server Administrator > Configuration.

6. Double-click System Configuration. The Configuration Sets form opens.

7. Double-click system. The System Property form opens.

8. Click Action > Create.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


AUTOPURGE parameter

9. Type AUTOPURGE in the Property Name field.

10. Type TRUE in the Value field.

11. Type <description of property> in the Description field.


While autopurge does not delete all data associated with a work unit, it does delete data about activity node execution. This might be appropriate depending on your circumstances. However, if a process is new, you might want to keep autopurge disabled until you know that the process runs as intended. In addition, if your processes do not generate a large amount of data, you might want to leave autopurge disabled and delete data from work units and/or Workunit History views per the schedule you have established.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


System administration The system administration section in the Process Server Administrator consists of:

Async Security management Remove analytics data

Async page

Async manages the scheduler:

Creates an AsyncActionRequest Schedule runs as long as the Async system is up

Process Automation manages the process queue. This is not managed by Async.

Async page

Security management

Process Automation can be secured within the Landmark Security.

Securable objects:

Processes Triggers Business classes Fields Menus Web apps

Delivered security classes:

ProcessServerAllAccess Update access to everything IPS

ProcessServerReadAcess Inquire-only access

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


InbasketAdministrator Update/inquiry access to IPS and objects as needed for a global Inbasket administrator

InbasketUser Inquiry access, limited update access to IPS as needed for personal Inbasket activities

ProcessSchedulingAllAccess Inquiry access to processes and service definitions Update access to objects as needed to submit/schedule processes

Remove analytics data Removes the Workunit Activity Comparison data Filter for “Failed” status if troubleshooting

Demo: Remove analytics data

Your instructor will demonstrate how to remove analytics data from the process flow queue.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps


2. Select LTM in the aata area.

3. Click Start > Data > la > Business Classes > ProcessFlowQueue.

4. Click the filter icon (magnifying glass).

5. Type F in the Status field to filter for the Failed status.

Note: Email notifications are sent when a flow fails based on the LTM configuration parameters.

Process Flow Queue List

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Grid configuration for IPA The configuration properties for IPA can be accessed within the Grid Manager:

Demo: Access Grid configuration for IPA

Your instructor will demonstrate how to access the Grid configuration for IPA.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo steps





4. Click Edit Properties.

Application properties

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configuring Grid and other properties

Configuring some of the IPA properties can take trial and error. If database requests are being denied, you might need to increase pool sizes. If performance is not what you want, you may want to try and decrease the pool sizes. Many of these properties work in conjunction with another parameter.

Process Automation settings:

The properties in this section control the frequency with which the Process Server polls for such things as work escalation, reminders, and for new work units.

Parameter Description

pfi.escalator.pollingFrequency Polling frequency, in minutes, for the Process Server to look for work escalation and reminders messages for Inbasket Default = 30 minutes

pfi.workunit.pollingFrequency Polling frequency, in minutes, for work units needing processing Default = 30 minutes

The Process Server creates a pool of database connections to be used for making database calls. This pool ensures that a connection to the database is always available when a process execution request made. The pool also makes processes execute faster and allows connections to be reused.


pfi.dataAccessPool.min Min. number of database connections in the pool. Default = 0

pfi.dataAccessPool.max Max number of database connections in the pool. Default = 2000

pfi.dataAccessPool.holdTime Max length of time, in milliseconds, that an idle connection should remain in the pool when the pool contains more than the number of objects specified in "pfi.dataAccessPool.min." Default = 120000 (2 minutes)

pfi.dataAccessPool.maxWaitTime Maximum time, in milliseconds, to wait for a database connection to become available before timeout occurs. Default = 10000 (10 seconds)

pfi.dataAccessPool.reuseLimit Reusing an existing connection can improve performance because time is saved by not having to reestablish a database connection. This parameter specifies the number of times a database connection can be reused. Default = 2000

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Thread pools

Thread pools provide improved performance when executing large numbers of process execution requests, because the threads are created ahead of time and are waiting for the requests. Thread pools also provide a way to limit the number of threads used by the Process Server to ensure that resources are managed effectively. The following properties let you configure the number of processes the server can execute simultaneously.


pfi.dispatcher.CorePoolSize Maximum number of threads to keep in the pool. If a thread is idle for the time specified by pfi.dispatcher.KeepAliveTime, the thread will be purged. Can configure as needed. Default = 2

pfi.dispatcher.KeepAliveTime Time in seconds to keep the thread alive in the pool when a thread is idle. Default = 5 minutes

pfi.dispatcher.QueueSize The size of the queue for work units or Inbasket actions waiting for a thread. Default = unlimited

Start/Stop Process Automation

There are two ways to stop and start IPA:

Demo: Start/Stop Process Automation

Your instructor will demonstrate how to start and stop IPA.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Demo steps

Using the Grid pages:





5. Select IPA.

Using the Command line:


2. Type Managegrid – Options: list [-a]

List grid nodes and their status start bindingName1. Start a specific Grid node start [-a] exception1. Start grid nodes with exception of any listed after the –a option stop bindingName1. Stop the specified grid node Stop [-a] exception1. Stop the grid nodes with exception of any listed after the –a option.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Which one of the following is the client-side point and click business process application?

a) Infor Process Administrator b) Infor Process Designer c) Management page d) Configuration Console

Identify the three system administration sections in the Process Server Administrator.

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

Which application would you use to add Process Automation users?

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Lesson 15: Updating Landmark Estimated time

6 hours

Learning objectives


Define the steps to apply Landmark Environment updates. Define the steps to apply Landmark application updates. Describe WebSphere updates and settings. Describe Java and Perl updates.

Topics Update Infor Landmark Technology Update a Talent Management Suite product line Check your understanding

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

210 Lesson 15: Updating Landmark © 2014 Infor Education

Update Infor Landmark Technology

You will want to back up any customized configuration or settings before updating Landmark Technology Runtime


Infor Landmark Technology Server Installation Guide

Scenario: Updating Lawson Landmark Technology

In this scenario, the facilitator will work with you, step by step, through the process of updating your Landmark Technology environment.

Download the update Create a folder in %LADIR% called InstallDir. Download update from Xtreme Support into the InstallDir. Download update Landmark Infocenter (if available), and any new/updated Landmark language

packs.

If you are using Kerberos for WebSphere, during the update process you will be prompted for the WebSphere server username and password before the update can proceed. To avoid this issue, disable Administrative Security in WebSphere during the Infor Landmark Technology update installation. Re-enable Administrative Security after the update, along with Application Security, making sure to leave Java 2 security unchecked. See the Infor Lawson 10 Authentication Configuration Guide for more details.

WebSphere pre-installation cleanup tasks - Uninstall Landmark applications

From the IBM Integrated Solutions Console, access the following:

Stop and uninstall any Landmark applications currently deployed. Access Applications > Enterprise Applications. Then, select landmark-gen-law- env and click Uninstall.

Save changes. Synchronize nodes. Access System Administration > Nodes. Select the node and click Synchronize.

Update Landmark Infocenter

If there is a new delivery of Landmark Infocenter, it will speed your process to install it before updating Landmark.

Copy help_lmrk_<platform>_E421_<version>.war to %LASRCDIR%\gen\docs\help.war

Update Landmark language packs

If you have new, or update Landmark language packs to install, it will speed up the process to install them before updating Landmark.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Java –jar LM_LANGPACK_<language>.jar You do not need to do the standard post-install steps for a language pack as the update of

Landmark will do all of these steps.

Run the update installation program If you haven’t already, log in to your system as Lawson. From a Landmark command prompt, type dbverify –q GEN Change to the InstallDir. Start the installation program from Landmark command prompt, type:

java -jar <landmark.jar>

*Must execute the .jar from within the Command prompt not through standard Windows Explorer.

When the Welcome screen appears, click Next. Choose Select an existing Environment. In the drop-down list, select the Environment to update and click Next. On the Install Options window, select Update and click Next. Review the Installation Summary window. To continue the update, click Next. To view the log file, click the Log button. You can check the log file for install details, including:

The time the installation was started and completed Values you chose during installation A complete list of files installed Any errors that occurred during the install An installation summary

When the update is complete, click Finish.

Redeploy the Lawson Environment application to WebSphere Log in to your system as lawson. Verify that your WebSphere Application Server is running. From a Landmark command prompt, type: adminlaw. Run the enterpriseapp command to deploy the Lawson Environment Application to your

WebSphere Application Server: enterpriseapp gen law-env (If enterpriseapp fails, review %LALOGDIR%\was.log for errors.)

From a Landmark command prompt, type: startlaw. This is only needed if the system is not already “running.”

Generate the plug-ins In the WebSphere Administrative console, navigate to Servers > Server Types > Web

servers. Select any web servers you plan to use and click Generate Plug-in. Click Propagate Plug-in

Note: If you have configured WebSphere Administrative Console to directly manage any web servers, select them and click Propagate Plug-in.

If you have any web servers that are not being managed directly, copy the plugin-cfg.xml files listed in the Messages section to your remote web server Plugin config sub-directories. Restart the web servers to accept the new configurations.

Restart the servers Restart the internal and external web servers.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Testing the Landmark Environment

After you test the Landmark Environment, you rebuild and redeploy any Landmark applications.

Run the following tests. For the lsuserapp test, you will need to enter a user ID and password.

http://hostname:port/ssoconfig/SSOCfgInfoServlet• http://hostname:port/lsuserapp/controller.servlet?dat aarea=gen

Run the GridManager test:

http://hostname:webport/gridmanager/GridManager.html? gridservicehost&port=gridRouterPort

Rebuild/Deploy applications

If you plan to update application source code, skip to the next section.

If you are not updating application source code, then for each product line (including IPA Standalone) you must do the following steps:

Buildprod <product line> Adminlaw Dbupgrade <product line> Scupdate <product line> Startlaw Enterpriseapp <product line> <appname>

Then generate and propagate plug-ins in the WebSphere Console, and restart web servers.

Class Applications:

gen-law-env (just deployed in update)

apps10-lpa

finance-finapp

ltm-hcmapp (deployed next update)

procurement-procurement

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Update a Talent Management Suite product line

Scenario: Updating the Talent Management Suite product line – Part 1

In this scenario, the facilitator will work with you, step by step, through the process of updating the LTM suite product line.

Downloading the update Create a folder in %LADIR% called InstallDir. Download the update from Xtreme Support into the InstallDir.

Receive new release into the repository If you haven’t already, log in to your system as lawson. Ensure that you are in the InstallDir. Start the installation program. From a Landmark command prompt, type:

java -jar <ltm.jar>

(Hint: Type ltm then tab to auto-complete file.)

Review the repository information and click Next.

Note: This only needs to be done once per site. If you have multiple product lines, including on different machines (e.g. Dev, Test and Prod), they should all be pulling code from the same repository.

Check file and directory status

On Unix, before you update a product line, you will need to check that all files and directories are owned by lawson and not root.

From a Landmark command prompt, type:

cd %LASRCDIR%\<productline>

Run the following command. Type:

ls -lR | grep root

Check output for any files or directories owned by root. If you have any files or directories owned by root, complete the following:

a. Log in to your system as root.

b. Change the ownership on all files and directories by typing:

chown -R lawson:lawson *

c. Log back in to your system as lawson.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Prepare for an update

Before you update a product line, you will need to check that there are no uncommitted modifications to Subversion-controlled files. Any file under source control (Subversion) needs to be up-to-date before you update the product line.

Infor Landmark Product Line Guide

At a Landmark command prompt, type:

cd %LASRCDIR%\<productline>

Run the following command. Type:

jsvn status

Review the list of files. Each file or directory has a leading character: ? means the file or directory is not under source control. No action is needed on these files.

Check the committed file to see if the modification is something you want to keep. ! means that the product line is missing a file that is present in the repository.

If there are missing files, this indicates a problem with the previous release’s product line. To make sure that the repository is in sync with the product line in the case of missing files, do the following:

Try the jsvn revert filename to restore the file to the product line. If the jsvn revert does not work, rename the directory containing the missing file. Check out the missing file. Perform the jsvn up command on the directory for the missing file. Recheck the status using jsvn status. After the missing file issues are fixed, delete any directories you renamed.

If you want to keep the modification, at the Landmark command prompt, type:

jsvn commit -m "text" <file>

where text describes the reason for modification.

If you do not want to keep the modification, you will need to remove the changes to the file. At the Landmark command prompt, type:

jsvn revert <file>

Check the status again. At the Landmark command prompt, type:

jsvn status

The svndiff tool

The svndiff tool is useful for analyzing the differences between releases and customizations. It helps you to understand both the differences at the release level and at the individual file level. This utility combines the functionality of svn diff with a more useful interface so that you can more easily select the items you need to compare.

Demo: Execute the svndiff tool

Your instructor will demonstrate how to execute the svndiff tool.

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 15.1: Execute the svndiff tool to prepare for an update

In this exercise, you will execute the svndiff tool to prepare for an update.

Exercise steps


2. Type svndiff and <enter specific commands you want to run >

The svndiff tool can be used to generate a report used for testing or regression testing as you can compare changes to source code files, compare marks on a development branch, compare a new Lawson release with a previous release, and more. You can create a diff file for any of the files that are listed when you run svndiff. The diff files can help you understand in more detail the nature of the changes in that source file.

Scenario: Updating the Talent Management Suite product line – Part 2

In this scenario, the facilitator will work with you, step by step, through the process of updating the LTM suite product line.

Update a Talent Management Suite product line Run the following command. Type:

listproduct -abeir

This lists all product releases available for selection from the repository.

Run the updateprod command, providing the release and product line. Type:

updateprod -r <release> <productline>

For example: updateprod -r 10.2.0.2 ltm

Copy Lawson application language packs

Follow the steps to download and move Lawson language packs to the application directory structure.

If you haven’t already, download the Lawson language packs from MyLawson.com. Commit the files to the development branch of your repository before the branch is "marked."

For more information on using Subversion, see the Landmark Product Line Management Guide.

Copy each language pack into the application directory structure:

copy language_pack %LASRCDIR%\productline\i18n\

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Configure the product line for an update Type the following:

cd %LASRCDIR%\<productline>\install

Run the following script. Type:

perl install-hcm.pl

or, if you want to capture the output,

perl install-hcm.pl 2>&1 | tee installhcm.log

Run buildprod Build the product line. At a Landmark command line, type:

adminlaw

buildprod <productline>

Run dbreorg Stop the Websphere Application Server instance for Landmark. Run the following command:

dbreorg -lc <productline>

Review the proposed dbreorg changes. If everything is as you expected, you can run the actual dbupgrade command as shown in the next step.

dbupgrade <productline>

Run the post-installation script

This procedure processes any secadm changes and loads any product line configuration additions to the Configuration Parameter table.

Change directory to the %LASRCDIR%\productline\install directory.

cd %LASRCDIR%\<productline>\install

At the Landmark command line, type:

perl post-dbreorg.pl > postdbreorg.log

After the script finishes running check the postdbreorg.log for errors. Check for any secadm_script<#>.txt.err files in the

%LASRCDIR%\<productline>\install directory.

Note: The files can be used to ensure the commands are executed successfully by running the following command:

secadm -f secadm_script<#>.txt.err

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Encrypt business classes data Run the following command to ensure that any existing data in the business classes has been

encrypted. From a Landmark command prompt, type:

datamaint --encryption -U <dataarea>

Deploy the application to WebSphere Use the Landmark command prompt shortcut located on your Windows desktop or from:

%LADIR%\Shortcuts

Verify that your WebSphere Application Server is running. From a Landmark command prompt, type:

startlaw

Run the enterpriseapp command to deploy the Lawson Environment application to your WebSphere Application Server:

enterpriseapp <dataarea> hcmapp

Example: enterpriseapp ltm hcmapp

Note: If there is an error running the enterpriseapp command, review

%LALOGDIR%\was.log.

Generate the plug-ins In the WebSphere Administrative console, navigate to Servers > Server Types > Web

servers. Select any web servers you plan to use and click Generate Plug-in. Select any web servers you plan to use and click Propagate Plug-ins.

Note: If you have any web servers that are not being managed directly, copy the plugin-cfg.xml files listed in the Messages section to your remote web server Plugin config sub-directories. Restart the web servers to accept the new configurations.

Restart all web servers.

Test the Lawson Talent Management suite update Run the following to test the Lawson Talent Management Suite installation update. You must

enter a User ID and password to run the tests. In the URL that follow "<dataarea>" in braces means, "type the name of your dataarea." If

"dataarea" is not surrounded by braces, type "dataarea."

http://yourserver:999/yourdataarea/

CandidateSelfService/?dataarea=yourdataarea

Access help from the Lawson Talent Management Suite

Use the steps below to test the help function in the Lawson Talent Management Suite.

Launch the Landmark Rich Client. Log in to the following location:

http://applicationserver:GridRouterPort

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Where applicationserver is the fully qualified name of the application server.

Navigate to dataarea > Administrator Space. For example, prodhcm > Administrator Space. Double-click Resources. Click the Help button on the Resources form. (The Help button is a question mark within a

circle.) Select Application Help. If you receive an error, proceed to the online help troubleshooting procedures.

Update text search fields (This is specific to Human Capital Management.)

This process rebuilds the keyword search fields that are used in the text search process.

Note: Run this process during the critical update process if there are any database field changes made. The process runs all the update keyword set actions (Employee, Candidate, Job Posting and Requisition).

Launch the Lawson Smart Office from a PC. Log in to the following location:

http://applicationserver:GridRouterPort

Where applicationserver is the fully qualified name of the application server.

Navigate to dataarea > Administrator Space > Utilities > Data Maintenance Update Key Words > Update Key Words.

For example, LTM > Administrator Space > Utilities > Data Maintenance> Update Key Words> Update Key Words.

Click Update Candidate Keywords. Repeat third bullet for each organization.

Run the datamaint utility

Infor Landmark Technology Data Access Guide


Run the datamaint utility to generate log files that may assist with troubleshooting the application. For more information on the datamaint utility, see Maintaining Business Class Related System Data in the Lawson Landmark Technology Data Access Guide for your database configuration.

Run datamaint in verify mode. From a Landmark command prompt, type:

datamaint --auditsnapshot -Vcd <dataarea>

Review the log to identify any business classes that have the following errors: Business objects whose current data doesn’t match Audited View Business objects with inconsistent audit snapshot data

Run datamaint in update mode for business classes with either of the above two errors. Type:

datamaint --auditsnapshot -Uc <dataarea> <busClassName>

You can find the log files at:

%LALOGDIR%\datamaint\auditsnapshot.log.dataArea.Stamp

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.



Which of the following command prompt utility starts the Landmark Environment?

a) adminlaw b) startlaw c) stoplaw d) svinn diff

Identify the role of the svndiff tool and the benefits of utilizing the tool before performing an update to an application product line.

______________________________________________________________________ ______________________________________________________________________

After you test the Landmark Environment, what are you required to do if your applications are not being updated during the same maintenance?

______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

220 Course summary © 2014 Infor Education

Course summary Estimated time

30 minutes

Course objectives

Now that you have completed this course, you should be able to:

Describe Landmark technology and components. Explain tools and procedures used to manage Landmark processes, users, security, and

updates. Define ways to troubleshoot issues.

Topics Course review

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.


Course review

List four Landmark Environment tools an administrator can use to set up or modify.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Define what is meant by a multi-tiered Landmark architecture as it refers to applications.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

This node provides overall coordination of multiple running grid nodes and is also an interface point between Landmark-supplied commands and the grid.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

222 Course summary © 2014 Infor Education

List the two commands that transform Landmark Pattern Language (LPL) into a Landmark application.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

The ______ manages resource locks for various resources in the Landmark Environment.

a) Lase b) lads c) GLoader d) svinn diff

@ C

opyri

ght 2

014 I

nfor

All r

ights

reserv

ed.

Do not

distrib

ute an

d rep

roduc

e with

out a

uthori

zatio

n.

Documents

Lawson: Administering Landmark Foundation - Inforlearning.infor.com/production/vLab/Lawson10/IEN0382/IEN0382.pdf · Your notes Scenario Question Note Answer @ Copyright 2014 Infor