lawson: administering system foundation for...

Lawson: Administering System Foundation for Windows Training Workbook

Infor Lawson Version 10.x

December 18, 2013 Course Code: 01_0121000_IEN0200_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 © 2013 Infor. All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All other trademarks listed herein are the property of their respective owners. www.infor.com.

@ 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.infor.com/

Table of contents About this workbook ................................................................................................................................ iii Course overview ...................................................................................................................................... iv Training environment access ................................................................................................................... v Course description and agenda ............................................................................................................... vi

Lesson 1: Infor Lawson 10 architecture and foundation overview ...................................................... 1 Terminology ............................................................................................................................................. 2 Architecture overview .............................................................................................................................. 5 Check your understanding....................................................................................................................... 7 Infor Lawson System Foundation overview ............................................................................................. 8 Infor Lawson System Foundation review ................................................................................................. 9 Infor Lawson System Foundation core components .............................................................................. 10 LSF training environment review ........................................................................................................... 11 Check your understanding..................................................................................................................... 12 Infor Landmark Technology overview .................................................................................................... 13 Infor Landmark Technology review ....................................................................................................... 15 Infor Landmark Technology training environment review ...................................................................... 16 Check your understanding..................................................................................................................... 17

Lesson 2: Administrator interfaces ....................................................................................................... 18 Administrator interfaces overview .......................................................................................................... 19 LSF10 administrator interfaces .............................................................................................................. 20 Infor Landmark administrator interfaces ................................................................................................ 26 Check your understanding..................................................................................................................... 30

Lesson 3: End-user interfaces ............................................................................................................... 31 Infor Lawson Enterprise Applications presentation interfaces ............................................................... 32 Infor Lawson presentation tier communication ...................................................................................... 35 Check your understanding..................................................................................................................... 36

Lesson 4: Infor Lawson System Foundation directory structure ....................................................... 37 Infor Lawson Core Technology components ......................................................................................... 38 Infor Lawson System Foundation directory structure ............................................................................ 39 Check your understanding..................................................................................................................... 41

Lesson 5: Infor Lawson server administration ..................................................................................... 42 Infor Lawson Application Server ............................................................................................................ 43 Infor Lawson Batch Server .................................................................................................................... 44 Infor Lawson Database Server .............................................................................................................. 45 Infor Lawson Security Server ................................................................................................................ 46 Infor Lawson Compile Queue Server .................................................................................................... 47 Check your understanding..................................................................................................................... 48 Infor Lawson Environment and IOS configuration files .......................................................................... 53 Check your understanding..................................................................................................................... 54

Lesson 6: The Infor Lawson Environment, productlines, and database structures ......................... 55 Infor Lawson Enterprise Applications productline .................................................................................. 56 Lawson Core Technology productlines.................................................................................................. 60 Check your understanding..................................................................................................................... 61 Infor Lawson database structure ........................................................................................................... 63 Check your understanding..................................................................................................................... 65

Lesson 7: IOS services, batch, and online transaction processing ................................................... 66 Internet Object Services (IOS) ............................................................................................................... 67 Data Service execution.......................................................................................................................... 68 Drill Service execution ........................................................................................................................... 69 Transaction Service ............................................................................................................................... 70 Check your understanding..................................................................................................................... 72 Batch and transaction processing components ..................................................................................... 73 Check your understanding..................................................................................................................... 76

@ 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 Lawson printers ............................................................................................................................. 77 Infor Lawson job queues ....................................................................................................................... 79 Check your understanding..................................................................................................................... 81

Lesson 8: Infor Lawson System Foundation maintenance ................................................................. 82 System maintenance ............................................................................................................................. 83 Check your understanding..................................................................................................................... 85 Lawson System Foundation maintenance overview .............................................................................. 86 Infor Lawson Enterprise Applications maintenance ............................................................................... 87 Infor Lawson Core Technology maintenance ........................................................................................ 93 Check your understanding..................................................................................................................... 97 Installing Infor Lawson product .............................................................................................................. 98 ssoconfig utility .................................................................................................................................... 100 Schema Editor ..................................................................................................................................... 101 LDAP administration ............................................................................................................................ 103 Check your understanding................................................................................................................... 104

Lesson 9: IBM WebSphere® administration ....................................................................................... 105 IBM WebSphere® architecture overview ............................................................................................. 106 Requirements for Infor Lawson System Foundation ............................................................................ 107 Terminology ......................................................................................................................................... 108 IBM WebSphere® directory structure .................................................................................................. 109 Integrated Solutions (Administrative) Console ..................................................................................... 112 Check your understanding................................................................................................................... 129

Lesson 10: Authentication and federation .......................................................................................... 130 Distributed Security Package overview ............................................................................................... 132 Infor Security Services overview ......................................................................................................... 134 Federation overview ............................................................................................................................ 136 Check your understanding................................................................................................................... 145 Authentication vs. federation overview ................................................................................................ 146 Authentication protocol ........................................................................................................................ 147 SSO services, agents, and identities ................................................................................................... 153 Single sign-on ...................................................................................................................................... 154 Federation ........................................................................................................................................... 155 Check your understanding................................................................................................................... 160

Lesson 11: User administration and security monitoring ................................................................. 161 User administration ............................................................................................................................. 162 User security monitoring ...................................................................................................................... 173 Check your understanding................................................................................................................... 180

Lesson 12: Infor Lawson Security ....................................................................................................... 182 Infor Lawson Security administration ................................................................................................... 183 Check your understanding................................................................................................................... 193

Lesson 13: Infor Ming.le™ and end-user interfaces .......................................................................... 194 Infor Ming.le™ Foundation .................................................................................................................. 195 Infor Lawson for Ming.le™................................................................................................................... 205 Infor Lawson for Ming.le™ roles .......................................................................................................... 208 Bookmarks .......................................................................................................................................... 210 Infor Lawson for Ming.le™ customizations .......................................................................................... 212 Infor Smart Office ................................................................................................................................ 214 Check your understanding................................................................................................................... 218

Lesson 14: Additional end user topics ............................................................................................... 220 Process management.......................................................................................................................... 221 Reporting ............................................................................................................................................. 227 Check your understanding................................................................................................................... 234

Course summary ................................................................................................................................... 236

ii Course introduction © 2013 Infor Education

@ 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.

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 Windows and UNIX 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

Lawson: Administering System Foundation for Windows Training Workbook iii © 2013 Infor Education

@ 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/

Course overview This course introduces the components, requirements, and procedures to maintain an Infor Lawson System Foundation 10.0.x system.

Course length 5 days (38 hours)

Course goal The purpose of this course is to provide technical foundational skills for performing System Administration functions within the Infor Lawson system on a Windows platform.

Note: Infor Landmark Technology is covered only at the support level for Infor Process Automation and Administrators should attend Infor Landmark Foundation and Administration (4-day) course for exposure to detailed architecture and maintenance procedures for Infor Landmark Technology products.

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

• Identify Infor Lawson System 10 architecture and directory structure. • Describe key Infor Lawson System concepts and terms. • Describe how to maintain Infor Lawson servers, system processing and job processes. • Explain how to apply product installation or updates, maintenance releases and patches. • Explain how to manage Infor Landmark Technology Runtime for Infor Process Automation only. • Describe how to maintain IBM WebSphere, user administration with Infor Security Services,

Lawson LDAP, Infor Ming.le™ Foundation, and Infor Lawson for Ming.le™, and Infor Lawson Security administration.

Audience • System Administrators • Support Personnel • Business Analysts • Security Administrators, Database Administrators

System requirements • This course is taught on Microsoft Windows 2008 R2 servers (Lawson System Foundation,

Landmark, and Microsoft SharePoint).

Prerequisite knowledge • Attendees should have knowledge of their organization’s licensed Lawson applications, products

and installation. This will allow for more detailed discussions and understanding of how they will maintain their Lawson System Foundation.

iv Course introduction © 2013 Infor Education

@ 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 environment access You will use Citrix to log in to the training environment.

Steps 1. Go to https://inforeducation.infor.com/vpn/index.html.

2. Type LSF### in the User name field. (### number 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

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 Ming.le™

lawson Tr@in123

Infor Enterprise Search Server Ussplu147

Green Ussplu147.lu147training.lawson.com • Infor Enterprise Search

lawson Tr@in123

Lawson: Administering System Foundation for Windows Training Workbook v © 2013 Infor Education

@ 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.

https://inforeducation.infor.com/vpn/index.html

Course description and agenda The purpose of this course is to prepare System Administrators or Business Analysts on the architecture and maintenance procedures of Infor Lawson System Foundation 10x. This training is applicable for the Infor Lawson System Foundation version 10x. This course is 38 hours of delivery as an instructor-led course (course code: 01_0121000_IEN0200_LSU).

Note: Infor Landmark Technology is covered only at the support level and Administrators should attend the Infor Landmark Foundation and Administration (4-day) course for exposure to detailed architecture and maintenance procedures for Infor Landmark Technology products.

Lesson Lesson title Learning objectives Estimated time

Course overview • Review course expectations. 30 minutes

Lesson 1 Infor Lawson 10 architecture and foundation overview

• Define the terminology for Infor Lawson 10.

• Describe the basic architecture of servers and products for Infor Lawson 10.

• Describe the architecture of Infor Lawson System Foundation 10.

• List the components of Infor Lawson System Foundation 10.

• Describe the architecture of Infor Landmark Technology.

5 hours

Lesson 2 Administrator interfaces

• Describe all the LSF10 administrative interfaces and uses.

• List the requirements for Infor Lawson System Mobile Monitor.

• Describe the access procedures for Infor Lawson System Mobile Monitor and Infor Landmark Administrator.

1 hour

Lesson 3 End-user interfaces

• Compare and contrast two main Infor Lawson Enterprise application presentation interfaces.

• Describe how to access Infor Ming.le™, Infor Lawson for Ming.le™, and Infor Smart Office.

• List the components and supporting components for presentation tier.

• Explain how the user interface communicates with the other Infor Lawson tiers.

1 hour

Lesson 4 Infor Lawson System Foundation directory structure

• List the location of files within the Infor Lawson System Foundation directory structure.

• Identify the three major Infor Lawson core technology directories and the major purpose of each.

2 hours

vi Course introduction © 2013 Infor Education

@ 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 Infor Lawson server administration

• Explain the importance of each of the main Infor Lawson servers.

• Identify the location and purpose of each server, environment, and IOS configuration file.

2 hours

Lesson 6 Infor Lawson Environment, productlines, and database structures

• Define the terms productline, application, program, form and data table.

• Explain the relationship between a productline, application, program, and form.

• List the location of data tables updated by a particular form.

• Identify major communication components for the Infor Lawson database structure.

1 hour

Lesson 7 Infor IOS services, batch, and online transaction processing

• List the three IOS services. • Describe the purpose and function of IOS

servlets. • List the Infor Lawson Environment

utilities. • Name the key batch processing

components. • Name the key online transaction

processing components. • Describe how to define an Infor Lawson

printer. • Explain how to define a job queue.

2 hours

Lesson 8 Infor Lawson System Foundation maintenance

• Identify routine maintenance concerns for the Infor Lawson System.

• Explain how to remove unneeded Infor Lawson files.

• List all the LSF10 required products and where to locate the update procedures.

• Explain how to apply Critical Transfer Packages (CTP) to Infor Lawson applications.

• Describe the enhancements to the Infor Lawson Enterprise Applications update process.

• Describe the new procedures for copying an Infor Lawson Enterprise Applications productline.

• Explain how to apply environment patches to the Infor Lawson Core Technology.

• Describe how to access Infor Lawson Information Investigator, collect information, interpret the data, and create

6 hours

Lawson: Administering System Foundation for Windows Training Workbook vii © 2013 Infor Education

@ 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.


a package for Global Support. • Explain how to install or update Infor

Lawson Employee and Manager Self-Service.

• Explain how to work with Lightweight Directory Access Protocol (LDAP) Administration tools (ssoconfig, ldifgen and LDAP browser).

Lesson 9 IBM WebSphere® administration

• Describe the IBM WebSphere® architecture and directory structure.

• Define IBM WebSphere® terminology. • Explain how to apply the IBM update

installer and fix packs. • Explain the IBM WebSphere® processes

and startup procedures. • Describe how to manage the IBM

WebSphere® Deployment Manager, application server configuration and Enterprise Application.

• Describe how to generate the plug-in cfg.xml and propagate.

• Explain how to conduct troubleshooting. • Describe the process to review log files.

2 hours

Lesson 10 Authentication and federation

• List the components of the Distributed Security Package (DSP).

• Identify where the Infor Security Services is installed.

• Describe the Infor Security Services purpose and features.

• Explain how to navigate within the Infor Security Services administrative tool.

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

• Define synchronization and potential conflicts.

• Explain differences between authentication protocol, federation, and Primary Authentication Service.

• Describe LS as STS and Kerberos as authentication protocol.

• Explain federation procedures. • Explain how to access the

Security_Provisioning log and use it for troubleshooting synchronization.

• Describe the Primary Authentication Service designation.

• Describe how to use Infor Security Services (ISS) to control Primary

3 hours

viii Course introduction © 2013 Infor Education

@ 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.


Authentication Service.

Lesson 11 User administration and security monitoring

• Describe the ways of provisioning a user in an LSF10 federated system.

• Explain how to define users for LSF and Infor Landmark Technology Runtime using the ISS Administrator tool.

• Explain how to use the ISS Administrator tool to update user information.

• Describe how to execute ISS synchronization to resolve potential user data inconsistencies.

• Describe the benefits of user monitoring. • List the required setup for user

monitoring. • Explain how to use the ISS administrative

tool to view user monitoring, history, and usage.

3 hours

Lesson 12 Infor Lawson Security

• List the key components of Infor Lawson Security.

• Describe how to build a role-based security policy using simple security rules of Grant and Unconditional for action.

• Describe conditional security rule capabilities.

3 hours

Lesson 13 Infor Ming.le™ and end-user interfaces

• Describe how Infor Ming.le™ supports the use of Infor Lawson applications.

• Compare and contrast the differences between Infor Ming.le™ Foundation and Infor Ming.le™ Enterprise versions.

• Explain how to administer access to Infor Ming.le™ and Infor Lawson for Ming.le™, and Infor Smart Office.

• List the requirements for Infor Ming.le™, Infor Lawson for Ming.le™, and Infor Smart Office.

4 hours

Lesson 14 Additional end user topics

• List the capabilities of Infor Lawson Design Studio.

• Describe how to create an Infor Process Automation (IPA) process.

• Describe the administration process for IPA.

• Explain the reporting options of ION Enterprise Search, Infor Lawson Add-ins for Microsoft Office, and Infor Spreadsheet Designer.

• Describe the process of configuring a standard report with Infor Lawson Smart

2 hours

Lawson: Administering System Foundation for Windows Training Workbook ix © 2013 Infor Education

@ 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.


Reports.

Course summary • Debrief course. 30 minutes

TOTAL ESTIMATED TIME 38 hours

Estimated times represent estimated teaching times only. Breaks and lunch are held at the instructor’s discretion, depending on factors such as the course schedule, course content and audience.

x Course introduction © 2013 Infor Education

@ 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 1: Infor Lawson 10 architecture and foundation overview Estimated time 5 hours

Learning objectives After completing this lesson, you will be able to:

• Define the terminology for Infor Lawson 10. • Describe the basic architecture of servers and products for Infor Lawson 10. • Describe the architecture of Infor Lawson System Foundation 10. • List the components of Infor Lawson System Foundation 10. • Describe the architecture of Infor Landmark technology.

Topics • Terminology • Architecture overview • Check your understanding • Infor Lawson System Foundation overview • Infor Lawson System Foundation review • Infor Lawson System Foundation core components • LSF training environment review • Check your understanding • Infor Landmark Technology overview • Infor Landmark Technology review • Infor Landmark Technology training environment review • Check your understanding

Lawson: Administering System Foundation for Windows Training Workbook 1 © 2013 Infor Education

@ 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.

Terminology The following table provides terminology used for Infor Lawson System Foundation, Infor Landmark, and user interfaces.

Term Definition Authentication The mechanism by which a user presents credentials for

accessing a system, such as Infor Lawson System Foundation. The following authentication choices are available for customers with Release 10 of Infor Lawson and Infor Landmark Technology: • Lawson Security as Security Token Service (LS as STS) • Kerberos

Kerberos An industry-standard authentication protocol used by Microsoft Active Directory / Microsoft Windows.

Infor Security as Security Token Service (IS as STS)

Infor Security serves as the authenticating authority.

ldapbind (Lawson utility) Infor Lawson utility for configuring Infor Lawson users to authenticate against the customer corporate directory. Customers can choose to use ldapbind in conjunction with LS as STS.

Federated system

Infor Lawson uses this term to refer to two systems (for example, Infor Lawson System Foundation and Infor Landmark Technology Runtime) sharing user information so that both systems can participate in "single sign-on." One system serves as the "primary authentication service." Federated systems must use the same "assertion protocol"; both must be either HTTP or HTTPS.

Infor Security Services (ISS) A system that lets security system administrators perform such tasks as federating a system and performing some tasks related to user provisioning. Information about using this tool is in Infor Security Services Configuration Guide.

Primary authentication service In a federated system, the system designated to authenticate the user (SSOP or SSOPV2).

Single sign-on When single sign-on is configured, users can access multiple Infor Lawson systems in a single session while authenticating only one time.

Distributed Security Package (DSP)

This is the Infor Lawson deliverable that contains tools to enable single sign-on. Distributed Security Package delivers the following components of the Lawson Security solution: • Distributed Single Sign-on (DSSO), which enables single sign-

on between applications on remote servers and the Infor Lawson System Foundation.

• Infor Security Services (ISS), which provides user provisioning, synchronizing, and federating services in

2 Lesson 1: Infor Lawson 10 architecture and foundation overview © 2013 Infor Education

@ 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.

Term Definition environments where Infor Lawson System Foundation and Infor Landmark Technology Runtime are installed and federated.

The Distributed Security Package is available both as a LifeCycle Manager installation package (recommended for applications which are installed with LifeCycle Manager) and a Java installer package.

Microsoft SharePoint Microsoft Windows platform for web-based collaboration and information sharing. Infor Ming.le™ is built on this technology.

Infor Ming.le™ The foundation of the web user interface.

Infor Lawson for Ming.le™ Infor Lawson for Ming.le™ is the web user interface for Infor Lawson Enterprise Applications, Self-Service applications and other Infor Lawson products. The installation consists of three components: • The core components, installed on the Infor Lawson System

Foundation server. • Web components, installed on the web server configured for

Infor Lawson System Foundation. • The Infor Lawson for Ming.le™ plug-in, installed and

configured on the Infor Ming.le™ Microsoft SharePoint server. Lawson plug-ins for Infor Ming.le™

Lawson plug-ins for Infor Ming.le™ enable Infor Lawson applications to run in Infor Ming.le™. Each Infor Lawson product that runs in Infor Ming.le™ has a corresponding plug-in. The plug-ins are installed on the Infor Ming.le™ server and provide essential configuration information to Infor Ming.le™.

Lawson Security Administrator An Infor Lawson System Foundation (LSF) tool for performing most security-related tasks, including writing security rules. If used to update fields in LSF, then will be out of sync with Landmark.

Lawson Core Technology Lawson Core Technology is the first Infor Lawson package installed on your system. It provides the infrastructure necessary to run the Infor Lawson Business Applications. The following components are delivered: • Lawson Core Administration Services • Lawson Security, including Resource Management, single

sign-on (SSO), and predefined templates for application security setup

• Internet Object Services (IOS) • Process Server components, which manage communication

with Infor Process Automation • Applications run time programs, configuration files, and

utilities • Application Maintenance Toolset • Bouncy Castle automated install and update

LID The Lawson Interface Desktop (often referred to as LID or the Desktop Client) is a user interface that provides access to the Lawson Environment utilities and command line. LID is installed on the desktop machines of users who need administrator access to the Lawson Environment.


@ 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.

Term Definition Infor Lawson Smart Reports Designer

Infor Lawson Smart Reports Designer (LSR Designer) provides the user a tool for enhancing the existing layout of report templates generated using Infor Lawson report programs. This desktop application uses a drag-and-drop design environment, with preview function to let the user evaluate any modifications applied on the LSR template.

Infor Lawson UNIX Utilities (LUU) -Microsoft Windows only

The Infor Lawson UNIX Utilities are a set of utilities that allow Infor Lawson System Foundation and related applications to run on the Microsoft Windows platform. You install LUU prior to installing Lawson Core Technology. Microsoft Subsystem for UNIX-based Applications (SUA) and Cygwin are required to be installed prior to LUU. • LUU directory is identified in laconfig.exe.

Infor Infocenters The Infor Infocenters are the installed user and administration guides provided for your release. All application and technical guides are available through the Infor Infocenter.


@ 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.

Architecture overview The following diagram illustrates ONE possible architecture and components for the Lawson Core Technology configuration. This generic diagram is used for illustration purposes only and is NOT a mandatory architecture.

Infor Lawson 10 architecture

If you are not using Infor Process Automaton/Integration or any other Infor Landmark Technology Runtime-based application, then you will not need the Infor Landmark server.

Refer to the Infor Lawson Compatibility Matrix for details and a list of supported products and component versions. Go to https://www.inforxtreme.com > Documentation > Search. Select S3 in the Search field and click Browse. Select the Compatibility Matrix – Infor Lawson document.


@ 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.

https://www.inforxtreme.com/

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

Check your understanding

1) Name the major components of Infor Lawson System Foundation.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Name the major components of Infor Landmark Technology Runtime.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) Define the requirement of LUU for Windows OS with Infor Lawson 10.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson System Foundation overview

Infor Lawson System Foundation Architecture Guide

Infor Lawson System Foundation is a platform that enables development and running of Infor Lawson Enterprise Applications.

The following components are installed with Infor Lawson System Foundation:

Component Description User interfaces Infor Lawson for Ming.le™ or Infor Smart Office

(optional/chargeable).

Lawson Core Technology Lawson Core Technology is a container name for the many services and utilities that run the Infor Lawson system. The term "Lawson Environment" or "Environment" refers to a single instance of Lawson Core Technology.

Internet Object Services (IOS) Technically a part of the environment, IOS, which specifically supports web-based components like Infor Lawson for Ming.le™, has some unique characteristics.

Multi-database system Refers to significant aspects of what Infor Lawson calls the Multi-Database System (MDBS), the interface to customer data which is stored in a third-party relational database system (RDBMS).

Batch and online transactions Batch refers to job processes executed in the background using the Lawson Batch Server (LAJS). Online refers to interactive processes executed directly from a form using the Lawson Application Server (LATM).

Security Refers to the Lawson Security connection to the Infor Lawson system, authentication, and authorization.

Infor Process Automation Infor's Business Process Management (BPM) product is an Infor Landmark application that is fully compatible with the Infor Lawson System Foundation 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.

Infor Lawson System Foundation review

Infor Lawson System Foundation review worksheet


@ 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 Lawson System Foundation core components

LSF core components

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

LSF training environment review The instructor will explore the Infor Lawson System Foundation server. Each attendee will receive four unique IP addresses representing LSF, Infor Landmark, Microsoft SharePoint, and Infor Enterprise Search servers. Infor Landmark will be reviewed in Lesson 3. Microsoft SharePoint will be reviewed in Lesson 9. Infor Enterprise Search will be explored in Lesson 10.

You will use the Remote Desktop Connection to explore the servers.

Server Server color

IP address Access to: User name \ Passwords

Lawson System Foundation Server Ussplu143

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

Intelligence

lawson Tr@in123

The following areas will be explored on the Usspl143 (LSF) server:

• Services (review of all Windows services running) • Location of administrative and end-user tools or clients • Directory 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.


1) What parts of LSF enable communication at the web layer?

______________________________________________________________________ ______________________________________________________________________

2) How would you describe Infor Ming.le™ Foundation (general definition)?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Landmark Technology overview

Infor Landmark Technology Server Setup and Maintenance

Infor Landmark Technology is a platform that enables development and running of Java applications.

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, and 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

The Lawson: System Foundation Difference 9x to 10x course is not a replacement for the Infor Landmark Foundation and Administration course. The Infor Landmark information provided in this course is to assist administrators in their understanding of the full LSF10 architectural footprint and is not designed to enable attendees as administrators of Infor Landmark Technology Runtime.

Infor ION Grid for Infor Landmark The Infor ION Grid is an application server that you install separately from Infor Landmark Technology Runtime and within which several Infor Landmark components run.

The Infor ION Grid contains the following standard components:

Component Description

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, for each grid for which it is a member, needs a grid agent.

Node A node is a Java Virtual Machine (JVM) that is registered as part of a grid where grid applications are running. The Infor ION Grid for Infor Landmark typically has several nodes running different Infor Landmark component applications. All nodes run on the grid host.


@ 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.


Registry The registry is a special type of node 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 is made accessible through firewalls, when applicable, because it must be reachable from clients. The default name for the grid router for Infor 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.

Bindings

A binding defines where and how to run nodes of a specific node type. You can view a binding 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 grouping of one or more application modules. An application may be running in more than one node. It is then said to have more than one application instance. 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.

Infor Landmark Technology review

Infor Landmark Technology review worksheet


@ 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 Landmark Technology training environment review The instructor will explore the Infor Landmark Technology server. Each attendee will receive four unique IP addresses representing LSF, Infor Landmark, Microsoft SharePoint, and Enterprise Search servers. Use the Remote Desktop Connection to explore the 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

The following areas will be explored on the Usspl141 (Landmark) server:

• Services (review of all Windows services running) • Location of administrative and end-user tools or clients • Directory structure • Active Directory (Domain 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.


1) Describe the Infor ION Grid for Infor Landmark.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

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

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) How could Infor Landmark be considered a requirement in Infor Lawson 10?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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: Administrator interfaces Estimated time 1 hour


• Describe all the LSF10 administrative interfaces and uses. • List the requirements for Infor Lawson System Mobile Monitor. • Describe the access procedures for Infor Lawson System Mobile Monitor and Infor Landmark

Administrator.

Topics • Administrator interfaces overview • LSF10 administrator interfaces • Infor Landmark administrator interfaces • Check your understanding

18 Lesson 2: Administrator interfaces © 2013 Infor Education

@ 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.

Administrator interfaces overview The table below introduces the various administrator interfaces available, location, and usage of each.

Administrator interface Location and usage

Lawson Interface Desktop (LID) Resides on the LSF server and used to maintain the Lawson Core Technology (Environment).

Landmark Command Window (LCW) Resides on the Infor Landmark server and used to maintain the Infor Landmark Environment and Grid.

Landmark Grid Manager browser-based Resides on the Infor Landmark server and used to maintain and support the Infor Landmark Grid, configuration, and running JVMs.

Landmark Rich Client Admin Resides on the Infor Landmark server and used to maintain Infor Landmark information including Infor Process Server (IPS) setup, Landmark Security, and Configuration Console.

Infor Landmark Administrator (App) Resides on the Infor Landmark server and used to provide administrative accessibility for Infor Landmark server through smartphone or tablet devices. Supports only Apple iOS systems currently.

Infor Security Services (ISS) browser-based Resides on the LSF server and used for federation, synchronization, user maintenance, and user monitoring for LSF and Infor Landmark.

Lawson Security Administrator (LSA) and Resource Manager (RMA)

Resides on the LSF server and used to add roles, groups, structures, and Lawson Security configuration for Lawson Lightweight Directory Access Protocol (LDAP). User information can be view but the preferred method of update is with ISS.

Lawson Schema Editor Resides on the LSF server and is used to modify the LSF Lawson LDAP. Requires ldifgen and ldifde/ldapmodify to complete modification.

Infor Lawson System Mobile Monitor (App) Resides on the LSF server and is used to provide administrative accessibility for the LSF server through smartphone or tablet devices. Supports Android and Apple iOS 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.

LSF10 administrator interfaces

Getting Started with Lawson Interface Desktop (LID) Infor Lawson Interface Desktop (LID) Installation Guide

Lawson Interface Desktop (LID) Lawson Interface Desktop (LID) is the main administrative tool for Lawson Core Technology. This administrative interface allows access to the environment services and utilities. LID is used to maintain the environment, access runtime information or logs and control settings for Lawson Core Technology.

Demo: Accessing the Infor Lawson Interface Desktop Your instructor will demonstrate how to access the Infor Lawson Interface Desktop, execute simple navigation, and access utilities.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.1: Accessing the Infor Lawson Interface Desktop In this exercise, you will access the Infor Lawson Interface Desktop. From here you will be able to run utilities, access server logs, and adjust settings. You will use the Ussplu143 (LSF) image.

Exercise steps 1. Access the Lawson Interface Desktop icon on the desktop.

2. Select the green phone icon on the toolbar.

3. Select the USSPLU143 server.

4. Type Tr@in123 in the User Name field.

5. Type lawson in the Password field.

6. Click OK to access the command prompt of LID.

7. Type laenv in the Command line prompt and press Enter to access the menu of utilities.

8. Select User Desktop > Print Technical Text to access the laenv utility.

9. Type APPS10 in the Product Line field.

10. Type HR in the System Code 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.

11. Type HR11 in the Program Code field.

12. Press Enter to view the technical text about the HR11 program.

13. Press the ESC key twice to exit the utility.

14. Click Exit on the laenv menu to return to command line.

15. Type laservstatus at the Command prompt.

16. Press Enter to view running environment services.

Infor Security Services Configuration Guide

Infor Security Services Infor Security Services is a web browser-accessible administrative tool for managing actors/users and for configuring the security system for Infor Lawson System Foundation and Infor Landmark Technology Runtime.

Infor Security Services administration tool

Exercise 2.2: Accessing Infor Security Services (ISS) In this exercise, you will access the ISS tool and explore the available areas. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > Infor > Infor Security Services.

2. Type lawson in the User 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.

3. Type Tr@in123 in the Password field and press Enter. 4. Explore the Resources, Configuration, SSO, and Federation menus.

ISS usage and exercises are covered in Lessons 10 and 11.

Infor Lawson Core Technology Installation Guide Infor Lawson System Foundation Server Setup and Maintenance

Infor Lawson System Mobile Monitor The Infor Lawson System Mobile Monitor is an application for Android and Apple iPhone / Apple iPad devices which enables administrators to monitor Infor System Foundation and perform some administrative tasks. Infor Lawson System Mobile Monitor has a client (mobile device) and a server (LSF) side install and configuration.

The following features are accessible with Infor Lawson System Mobile Monitor:

• View Environment settings • Start and stop the Environment • View the status of the Environment services • View diagnostic information, such as CPU, memory, user sessions, and processes • View job status and restart Needs Recovery jobs • View compile status and error logs • View patch information • View network diagnostics information • View diagnostics information and run smoke tests for the Infor Lawson Environment

To access these features an administrator would tap the icons on the initial screen for the Infor Lawson System Mobile Monitor, as shown in the following illustration (screens may differ based on the OS version and type of mobile device).


@ 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.

Initial screen for the Infor Lawson System Mobile Monitor

Summary of server-side install of Infor Lawson System Mobile Monitor

1. Verify of Java SDK version.

2. Install Hyperic Sigar 1.6.4 (required for Mobile App).

3. Establish a Web Server for the Mobile Monitor.

4. Configure IBM WebSphere with an Application Server for the Mobile Monitor.

5. Deploy lsmm.ear and lawsec.ear for the IBM WebSphere Application Server.

6. Create lsmm.xml Service and load in ssoconfig.

7. Establish SYSADMIN category of required Mobile Monitoring Form IDs.

8. Establish lsmm Service with same user and password as SSOP.

9. Connect authorized users with the roles S3MobileITAdminRole and S3MobileSysAdminRole (the roles and security classes are established prior to assignment to user).

Summary of client-side install of Infor Lawson System Mobile Monitor

1. Download the Infor Lawson System Mobile Monitor from the app store off the device.

2. Create a profile for connection to the server (server name and port).

3. Access the Infor Lawson System Mobile Monitor.


@ 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: Accessing the Infor Lawson System Mobile Monitor Your instructor will demonstrate how to access and highlight some of the uses of the Infor Lawson System Mobile Monitor.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Infor Lawson System Mobile Monitoring

Access the free application from your Android or iOS device after downloading from the app store. The application will require a VPN connection to provide access to your network.

Infor Lawson System Mobile Monitor and New Profile 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.

Use the application to Stop/Start Environment, monitor Environment services or administer batch jobs.

Settings, Service, Jobs 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.

Infor Landmark administrator interfaces

Infor Landmark Technology Runtime Server Setup and Maintenance

Infor strongly recommends the Infor Landmark Administration course to learn how to administer Infor Landmark Technology Runtime.

The following Landmark administrator interfaces are available:

• Common command line utilities • Infor Landmark Grid manager • Infor Rich Client • Infor Landmark Administrator (mobile)

Infor Landmark command prompt An administrator can perform many tasks from a command prompt. These tasks will be centered on the execution of Infor Landmark utilities.

Some common command line utilities are:

• stoplaw/startlaw • Security (secadm) • Database utilities (dbmaint, dbverify, dbdisplay) • Infor Landmark build and deploy processes (buildprod or enterpriseapp) • Grid (managegrid list )

For Microsoft Windows 2008, open the Command window with "Run as administrator" to avoid error: "Open SCManager Failed with error 5: Access is denied”. For Windows 2008 the Command window should be configured to “Run as administrator”.

Demo: Accessing the Infor Landmark Command window Your instructor will demonstrate how to access the Infor Landmark Command window and execute a basic command and 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.

Exercise 2.3: Accessing the Infor Landmark Command window In this exercise, you will access the Infor Landmark Command window and execute a basic command/utility. You will use the Ussplu141 (Landmark) image for this exercise.

Exercise steps 1. Click the Command Window for LMKENV desktop shortcut.

2. Type univver –v at the command prompt.

3. View the returned output of the running Infor Landmark Technology Runtime version.

Infor Landmark Grid Management The Infor Landmark Grid Management is a web-accessible JVM tool for managing and monitoring the Grid in an Infor Landmark Environment. Through this tool an administrator can view the status and manage the Grid applications. The Infor Lawson Grid Management is launched via a browser.

Demo: Accessing the Infor Landmark Grid Manager Your instructor will demonstrate how to access the Infor Landmark Grid Manager, view grid configurations, and manage the JVM from the Grid page.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.4: Accessing the Infor Landmark Grid Manager In this exercise, you will access the Infor Landmark Grid Manager. From here you will be able to view grid configurations and manage the JVM from the Grid page. You will use the Ussplu141 (Landmark) image for this exercise.

Exercise steps 1. Access the LMKENV_grid Grid Manager shortcut.

2. View the JVMs running for the Infor Landmark Technology Runtime from the LMRK_ENV Grid 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.

Infor Rich Client administration The Infor Rich Client is a user interface that allows access to data and applications on the Infor Landmark server. It is installed on an administrator’s desktop and accesses the Infor Landmark server through a router JVM connection. Administrator access to table data as well as the application forms will be granted.

Demo: Accessing the Infor Rich Client Your instructor will demonstrate how to access the Infor Rich Client, launch process boards, and access Async.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 2.5: Accessing the Infor Rich Client In this exercise, you will access the Infor Rich Client. From here you will access process boards and Async. You will use the USSplu143 (LSF) image.

Exercise steps 1. Click the Rich Client Admin desktop shortcut.

2. Type lawson in the Login field.

3. Type Tr@in123 in the Password field.

4. Verify that GEN Data Area in the upper left and Process Boards (collection of applications) display on the Rich Client desktop.

5. Access Start > Applications > Async Administrator > Async Overview.

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


@ 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.

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 then with server name and port, access to the app should be achieved.

Infor Landmark Administrator mobile app


@ 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) Name three types of uses for Infor Lawson System Mobile Monitor. What can an administrator accomplish?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) If an administrator suspects there’s a problem with the running of the Infor Landmark system, what administrative tool should be used to view the state of the processes?

______________________________________________________________________ ______________________________________________________________________


@ 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 3: End-user interfaces Estimated time 1 hour


• Compare and contrast two main Infor Lawson Enterprise application presentation interfaces. • Describe how to access Infor Ming.le™, Infor Lawson for Ming.le™, and Infor Smart Office. • List the components and supporting components for presentation tier. • Explain how the user interface communicates with the other Infor Lawson tiers.

Topics • Infor Lawson Enterprise Applications presentation interfaces • Infor Lawson presentation tier communication • 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 Lawson Enterprise Applications presentation interfaces


Interfaces that can be used to access the Infor Lawson system include:

• Infor Lawson for Ming.le™ (from Ming.le Foundation) • Infor Smart Office

Infor Ming.le™ (formerly Infor Workspace) 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.

Infor Lawson for Ming.le™ is the user interface for Infor Lawson Enterprise Applications and Self-Service applications.

Demo: Accessing Infor Lawson for Ming.le™ Your instructor will review and demonstrate how to access Infor Lawson for Ming.le™.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

32 Lesson 3: End-user interfaces © 2013 Infor Education

@ 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.1: Accessing Infor Lawson for Ming.le™ In this exercise, you will access and navigate Infor Lawson for Ming.le™. You will use Ussplu143 (LSF).

Exercise steps 1. Access IE shortcut on desktop (defaults to Ming.le home).

2. Type lawson in the User Name field.


4. Select the Lawson Applications option (globe icon on header of Ming.le).

5. Type HR11 in the Application Search field and press Enter. 6. Type 4321 in the Company field.

7. Type 1003 in the Employee field.

8. Click Inquire.

9. Select the Employee field.

10. Right-click in the Employee field and select Drill Around.

11. Explore the form options.

12. Explore the Infor Lawson for Ming.le™ general options (Bookmarks & Preferences).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo: Accessing Infor Smart Office Your instructor will review and demonstrate how to access Infor Smart Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.2: Accessing Infor Smart Office In this exercise, you will access the Infor Smart Office. You will use Ussplu143 (LSF).

Exercise steps 1. Access Infor Smart Office desktop shortcut.



4. Type HR11 in the Application Search field and press Enter. 5. Type 4321 in the Company field.


7. Click Inquire.

8. Select the Employee field right-click and Drill Around.

9. Explore the form options.

10. Explore the Infor Smart Office general options (Navigator & Settings).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson presentation tier communication There are various Infor Lawson presentations (Infor Lawson for Ming.le™, Infor Smart Office and LID for administration) that communicate with the rest of the Infor Lawson system.

User interface connection to S3 Lawson System Foundation

Infor Lawson for Ming.le™ Following are Infor Lawson for Ming.le™ components:

• Web browser • Web server • Application server

Infor Smart Office Following is the Infor Smart Office component:

• Application server

Infor Lawson Interface Desktop (LID) Following are the LID components:

• TCP/IP based emulator • Command line access • Administrative utilities 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.


1) List some requirements of Infor Lawson for Ming.le™.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Identify the target audience for Infor Lawson for Ming.le™ versus Infor Smart Office user interface.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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: Infor Lawson System Foundation directory structure Estimated time 2 hours


• List the location of files within the Infor Lawson System Foundation directory structure. • Identify the three major Infor Lawson core technology directories and the major purpose of each.

Topics • Infor Lawson Core Technology components • Infor Lawson System Foundation directory structure • 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 Lawson Core Technology components


In this lesson we will examine the Infor Lawson System Foundation directories. The purpose of this lesson is to expose a new system administrator to the location of information and files within their Lawson server.

Lawson Core Technology (LCT) is also known as the Lawson Environment.

What is the Infor Lawson Core Technology? In the following sections we will identify and discuss the Infor Lawson Core Technology/Environment and its major functions.

Infor Lawson environment components The Environmental components of Infor Lawson include:

• Lawson Application Server (LATM) • Lawson Batch Server (LAJS) • Runtime System (LACOBRTS) • Lawson Database Server (LADB) • Lawson Security Server (LASE) • Environment utilities • Active Data Repository (GEN)

Environment utilities Environment utilities are used to control the setup/configuration, processing and administration of the Lawson System Foundation. You have already had experience with some Environment utilities in this course, although there are many more.

Example: Database

• blddbdict • dbcreate • dbdef • dbreorg

Environment Utility menu - laenv

38 Lesson 4: Infor Lawson System Foundation directory structure © 2013 Infor Education

@ 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 Lawson System Foundation directory structure This section introduces the Infor Lawson System Foundation directory structure.

Lawson System Foundation includes the location of 3rd party products; IBM WebSphere, Perl, Java, web servers and RDBMS.

Demo: Locating files in the Lawson System Foundation directory structure Your instructor will demonstrate how to navigate within the directory structure to locate files.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Major Infor Lawson Core Technology directories There are three major Infor Lawson Core Technology directories. You will review these directories and what is contained within them. These also represent environment variables set within your server identifying physical directory paths.

• GENDIR • LAWDIR • LADBDIR

The environment variables will interpret to the physical paths identified in the LACONFIG utility on Windows OS. Use a %VARIABLE% syntax to identify the variable to be interpreted.

Demo: Locating files in the LCT directory structure Your instructor will demonstrate how to navigate within the directory structure to locate 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 4.1: Navigating within the Infor Lawson Core Technology directory structure In this exercise, you will practice navigating within the Infor Lawson Core Technology directory structure.

Exercise steps 1. Access LID Desktop Client or Windows Explorer. 2. Type lawson in the User Name field.


4. Find the following directories/files and identify their location:

ladb.cfg __________________________________________________________________

iosconfig.xml ______________________________________________________________

APPS10 (PDL) ____________________________________________________________

print (directory) ____________________________________________________________

dict (directory) _____________________________________________________________

blddbdict _________________________________________________________________

lajs.log ___________________________________________________________________

40 Lesson 4: Infor Lawson System Foundation directory structure © 2013 Infor Education

@ 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) What kinds of files does GENDIR contain?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What kinds of files does LAWDIR contain?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) What kinds of files does LADBDIR contain?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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: Infor Lawson server administration Estimated time 2 hours


• Explain the importance of each of the main Infor Lawson servers. • Identify the location and purpose of each server, environment, and Internet Object Services (IOS)

configuration file.

Topics • Infor Lawson Application Server • Infor Lawson Batch Server • Infor Lawson Database Server • Infor Lawson Security Server • Infor Lawson Compile Queue Server • Check your understanding • Infor Lawson Environment and IOS configuration files • Check your understanding

42 Lesson 5: Infor Lawson server administration © 2013 Infor Education

@ 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 Lawson Application Server

Infor Lawson Administration: Server Setup and Maintenance Guide

In this section, you will review the Infor Lawson Application Server, latm.

Managing the Infor Lawson Application Server Operation of the Infor Lawson Application Server requires two files; the configuration file and the log file.

• latm.cfg • latm.log

Application Server utilities In addition there are three utilities to support the Application Server.

• tmmon • tmcontrol • pgmtmdef

Demo: Configuring the Infor Lawson Application Server and viewing the log file Your instructor will demonstrate how to configure the Infor Lawson Application Server and how to view the Application Server log 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.

Infor Lawson Batch Server In this section, you will review the Infor Lawson Batch Server, lajs.

Managing the Infor Lawson Batch Server Operation of the Infor Lawson Batch Server requires two files; the configuration file and the log file.

• lajs.cfg • lajs.log

Infor Lawson Batch Server utility In addition, there is a utilities to support the Batch Server.

• jqcontrol

Demo: Configuring the Infor Lawson Batch Server Your instructor will demonstrate how to configure the Infor Lawson Batch Server and how to view the Batch Server log 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.

Infor Lawson Database Server In this section, you will review the Infor Database Server, ladb.

Managing the Infor Lawson Database Server Operation of the Infor Lawson Database Server requires two files; the configuration file and the log file.

• ladb.cfg • ladb.log

Infor Lawson Database Server utilities In addition, there are several utilities to support the Database Server.

• dbmode • -n = No New User • -s = Single User • -m = Multi-user

• dbusers • –p = current process • –u = users

• listusermap • jobschd

Demo: Configuring the Infor Lawson Database Server and viewing the log file Your instructor will demonstrate how to configure the Infor Lawson Database Server and how to view the Database Server log 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.

Infor Lawson Security Server In this section, you will review the Infor Lawson Security Server, lase.

Managing the Infor Lawson Security Server Operation of the Infor Lawson Security Server requires configurations within Lawson LDAP and log files.

• lase.log • lase_server_#.log • SecurityLoggerConfiguration.xml

Demo: Configuring the Infor Lawson Security Server Your instructor will demonstrate how to configure the Infor Lawson Security Server and how to view the Lawson Security 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.

Infor Lawson Compile Queue Server In this section, you will review the Infor Lawson Compile Queue Server.

Managing the Compile Queue Server Operation of the Compile Queue Server requires the following file and utilities.

• queue.log • qcontrol

QUEUE does not have a configuration file.

Infor Lawson Compile Queue utilities In addition, there are several utilities to submit programs for compile and support compile queue server.

• cobcmp • qcompile • patchcompile • qstatus

Demo: Configuring the Compile Queue Server Your instructor will demonstrate how to configure the Compile Queue server.

Example: qcontrol –jlocal,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.


Infor Lawson Application Server

1) What is the importance of the Infor Lawson Application Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) How would you change the configuration of the Infor Lawson Application Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) The system makes a record of activity associated with latm. Where is this record found?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) What utility can you use to control the Infor Lawson Application 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.

Infor Lawson Batch Server

5) What is the role of the Lawson Batch Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

6) How would you change the configuration of the Lawson Batch Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

7) What happens to waiting jobs and jobs in progress when you stop lajs?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

8) The system makes a record of activity associated with lajs. Where is this record found?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson Database Server

9) What is the importance of the Infor Lawson Database Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

10) When might you need to view and adjust parameters for the Lawson Database Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

11) How would you change the configuration of the Lawson Database Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

12) What must you do for changes to the ladb configuration to take effect?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

13) What file can you check to view ladb activity?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson Security Server

14) What is the importance of the Infor Lawson Security Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

15) When might you need to view and adjust parameters for the Lawson Security Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

16) How would you change the configuration of the Lawson Security Server?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

17) What must you do for changes to the lase configuration to take effect?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

18) What file can you check to view lase activity?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson Compile Queue Server

19) What types of jobs does the Compile Queue Server manage?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

20) How would you change the configuration of the Compile Queue 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.

Infor Lawson Environment and IOS configuration files In this section, you will review the main Infor Lawson Environment and IOS configuration files.

Environment and IOS configuration files Configuring the Infor Lawson Environment and IOS requires the following files.

• laconfig.exe • iosconfig.xml

Demo: Configuring the Infor Lawson Environment and IOS Your instructor will demonstrate how to use the laconfig.exe utility to configure the Environment and IOS configuration files.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 5.1: Accessing laconfig.exe In this exercise, you will access the laconfig.exe utility and explore the environment settings. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access %GENDIR%\bin.

2. Locate and open the laconfig.exe utility.

3. Explore the settings contained within laconfig.exe for the Lawson Core Technology.


@ 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) What is the main function of the laconfig.exe utility?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Describe the categories of settings contained within laconfig.exe.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) What is the purpose of the iosconfig.xml file and where is it located?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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: The Infor Lawson Environment, productlines, and database structures Estimated time 1 hour


• Define the terms productline, application, program, form and data table. • Explain the relationship between a productline, application, program, and form. • List the location of data tables updated by a particular form. • Identify major communication components for the Infor Lawson database structure.

Topics • Infor Lawson Enterprise Applications productline • Lawson Core Technology productlines • Check your understanding • Infor Lawson database structure • 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 Lawson Enterprise Applications productline


Infor Lawson Enterprise Applications structure and application database files include the following:

• Infor Lawson Enterprise Applications • Productline (PDL) • System codes (Categories) • Programs (PD) • Forms (Tokens) • Data dictionary

Infor Lawson Enterprise Applications structure

Infor Lawson system code and program naming convention Infor Lawson Enterprise Applications uses a two character representation for the installed application within a productline. Example: Accounts Payable is AP, Human Resources is HR, Inventory Control is IC. This two character representation of the application is known as a system code or category. The system code is a collection of application programs.

Infor Lawson Enterprise Applications uses a two or three position number representation for the programs. The two position number represents online programs. The three position number represents batch programs. Online programs are interactive and the information is immediately viewed or updated. Batch programs are background executions and output reports of information or updates.

56 Lesson 6: The Infor Lawson Environment, productlines, and database structures © 2013 Infor Education

@ 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 table below illustrates the Infor Lawson Enterprise Applications general guidelines for numbering programs.

System code + range

Description

00-19 Online Setup

20-49 Online Processing

50-99 Miscellaneous

100-199 Batch Update

200-299 Online Listings and Reports

300-399 Special Processing (i.e. Purge and Reorganization)

400-499 Currently not in use (available for user defined programs)

500-599 Non-Lawson Conversion/Interface

600-799 Miscellaneous

800-899 Lawson-to-Lawson Conversion

900-999 Upgrade and Data Structure Loads

MN Menus

Environment utilities pgmdef and dbdef used in this lesson are interactive and live against the programs and database structure. No changes should be made during their use and care should always be taken when accessing with these utilities. The pgmdef changes would require recompile of program and dbdef changes would require blddbdict and dbreorg.


@ 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: Locating applications, programs, and forms Your instructor will demonstrate how to locate applications, programs, and forms using pgmdef.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 6.1: Exploring applications, programs, and forms In this exercise, you will explore online and batch programs using the AP system code pgmdef. You will use the Ussplu143 (LSF) server in this exercise.

Exercise steps 1. Access the LID desktop shortcut.

2. Select the USSPLU143 server.



5. Click OK to access the command prompt.

6. Type pgmdef at the Command prompt.

7. Press F4 to access the APPS10 productline and AP system code to select values.

8. Fill out the diagram below.

a. Press F6 to define on items.

b. Press ESC to leave submenus.

c. Choose one online program (ex. AP10) and write examples of some of its forms/tokens in the appropriate boxes.

d. Choose one batch program (ex. AP210) and write it in the batch program box.


@ 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, programs, and forms worksheet

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Technical text and data file text Environment utilities are used to explore the programs and view/edit updated and referenced files. These utilities assist system administrators with application support questions. The utilities can be launched with lapm preceding or from the laenv menu at the command prompt of LID.

• Print technical text – dburf • Print data file text – dbdoc • Print user text – userdoc • Edit program technical text – pgftxt

Demo: Accessing information through utilities Your instructor will demonstrate how to execute technical and data file text from the Environment using dburf and dbdoc.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Core Technology productlines This section introduces the Infor Lawson Core Technology “Environment” productlines and the components contained within each.

Three types of productlines There are three productlines that exist in every Lawson Environment.

These productlines include:

• Application productline (discussed earlier in Lesson 6) • LOGAN productline • GEN productline

GEN is a pseudo productline. It is identified as a productline but contains no source code or applications. GEN is updated through utilities in the Environment.


@ 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.


Productlines

1) How would you describe the relationship between an application productline, system code, program, and form?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) How would you find out which data tables a particular program or form updates? Where is this information available?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) What is an application productline?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) What does the LOGAN productline contain?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) What is unique about the GEN productline?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson database structure


This section introduces the Infor Lawson database structure, including how data is stored in your RDBMS and characteristics that may be assigned to the data such as indexes, conditions and relationships.

Multi-database system The multi-database system (MDBS) is a generic term for the components that support interaction between Lawson and the data, both customer application and Lawson metadata, that is stored in an RDBMS. These components include the database driver and the client application program interfaces (APIs).

Lawson database server (ladb) and RDBMS JDBC driver The ladb server is invoked only to open and close the database connection. At all other times, the user application interacts directly with a database JDBC driver. This design improves performance by avoiding a potential bottleneck in the execution of ladb.

Productline vs. data area A productline is a set of applications source code installed within the Lawson Core Technology. A data area is a set of tables to support the source code in execution and storage of data. The productline and data area are often used as one-to-one relationship. However, the productline may have a one-to-many relationship with a data area if unique data is required under the processing of the same source code.

Example:

APPS10 (PDL) connects to APPS10 (Data Area) and generates APPS10 Dictionary for control of database structure. This is a one-to-one relationship.

APPS10 (PDL) connects to APPS10 (Data Area), APPS10TST (Data Area), APPS10DEV (Data Area) and generates APPS10, APPS10TST, APPS10DEV Dictionaries for control of database structure. This is a one-to many-relationship.

LOGAN and GEN productlines are only allowed a one-to-one relationship.

Lawson database structure includes:

• Data area • Data tables/files • Records • Fields • Indexes • Conditions • 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.

Demo: Locating files and fields Your instructor will demonstrate how to locate database tables/files and fields using dbdef.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 6.2: Exploring files and fields In this exercise, you will explore online and batch programs using the AP system code dbdef. You will use the Ussplu143 (LSF) server in this exercise.

Exercise steps 1. Access LID Desktop Client and log in:

• User Name: lawson • Password: Tr@in123

2. Type dbdef at the Command prompt.

3. Press F4 to access the APPS10 productline and select values.

4. Press F6 to define and ESC to leave menus; locate the following:

• Table (APVENMAST) • Fields • Indexes • Relationships

Environment utilities maintain the structure of the RDBMS. In earlier discussion the utilities blddbdict and dbreorg were discussed for generating the database dictionary and keeping the RDBMS structure in sync with this metadata 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.


Database structure

1) What file contains and controls the database structure of the RDBMS?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What is the primary function of ladb?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) What is the purpose of an index?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) Describe 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.

Lesson 7: IOS services, batch, and online transaction processing Estimated time 2 hours


• List the three IOS services. • Describe the purpose and function of IOS servlets. • List the Infor Lawson Environment utilities. • Name the key batch processing components. • Name the key online transaction processing components. • Describe how to define an Infor Lawson printer. • Explain how to define a job queue.

Topics • Internet Object Services (IOS) • Data service execution • Drill service execution • Transaction service • Check your understanding • Batch and transaction processing components • Check your understanding • Infor Lawson printers • Infor Lawson job queues • Check your understanding

66 Lesson 7: IOS services, batch, and online transaction processing © 2013 Infor Education

@ 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.

Internet Object Services (IOS)


In this section, you will review IOS servlets and services, which include:

• Router • Transaction (formerly known as AGS) • Drill (formerly known as IDA) • Data (formerly known as DME)

• Profile • IOSCacheRefresh • Xpress / Transform • Jobserver


@ 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.

Data Service execution In this section, you are introduced to the background process that takes place when data is requested (Data Service) from the Infor Lawson portal.

Data is the new name for DME.

Data Service execution cycle


@ 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.

Drill Service execution This section introduces to the background process that takes place when a Drill Around is performed within the Infor Lawson portal.

Drill Service is the new name for IDA.

Drill Service execution cycle


@ 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.

Transaction Service This section introduces the background process that takes place when an action within a form is performed with the Infor Lawson portal.

Transaction Service is the new name for AGS.

Transaction Service execution cycle


@ 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 Lawson System Foundation Architecture Guide (Access IE > Favorites > InfoCenters >Lawson Environment InfoCenter > Server Administration > Infor Lawson System Foundation Architecture Guide > Lawson Core Technology > IOS Servlets)

Demo: IOS servlets Your instructor will demonstrate the additional IOS servlets Profile, IOSCacheRefresh and JobServer.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) What are the three Infor Lawson IOS router servlet services?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Name some of the IOS servlets and brief description of purpose.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) Identify the difference between the Data and Drill Service.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) Identify two main differences between the Data/Drill and Transaction 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.

Batch and transaction processing components


In this section, you will review the components that perform batch and online transaction processing. All of the components discussed reside in the Infor Lawson Environment.

The components that perform online transaction processing are:

• Job Executors (execjob and tcpexecjob) • Lawson Cobol Runtime System (LACOBRTS) • Lawson Application Server (LATM) • Lawson Batch Job Server (LAJS)

Batch and online processing components


@ 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.

Batch processing Batch processing within Lawson Core Technology leverages several areas including:

• JOB Table in GEN • QUEUED JOB Table in GEN • LAWDIR\print directory

Batch processing components

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

Job statuses are important to understand for system administrators. Your instructor will define the potential statuses and causes for the following statuses:

• Active • Completed • Waiting • Invalid Parameters • Needs Recovery

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) What are the key components in Lawson batch and online transaction processing?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What table contains the submission and current status of a batch request?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) What options are available to see jobs and their status within the Lawson Core Technology?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson printers

Infor Lawson Administration Job and Reports

In this section, you will review defining a printer in the Lawson Core Technology.

Printer definition A Lawson printer must first be defined or accessible to the operating system (OS). After accessible by the server it can be identified as a resource in Lawson Core Technology. Standard Infor Lawson for Ming.le™ functionality allows a user to print from their print manager using network printers. However, there may be a need to send directly from the job or print manager to a defined Lawson printer.

A Lawson Security role must then provide authorization to the printer for users attempting to access the printer. Security for the Lawson printer will be discussed in Lesson 12.

Demo: Defining a printer Your instructor will demonstrate how to define a Lawson printer in prtdef.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 7.1: Defining an Infor Lawson printer In this exercise, you will define a Lawson printer. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access a LID command line.

2. Log in using the following information:

• User name: lawson • Password: Tr@in123

3. Type prtdef in the Command line and press Enter. 4. Type CLSPrinter in the Printer Name field.

5. Type CLSPrinter in Description field.

6. Type laprint CLSPrinter in the Command field.

7. Click Enter twice to save the printer definition.


@ 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. Access Infor Lawson for Ming.le™.


• User name: lawson • Password: Tr@in123

10. Navigate to the Job and Reports bookmark.

11. Select Print Manager.

12. Right-click on CU201 > CLSPrinter to print.


@ 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 Lawson job queues In this section, you will review defining a job queue in Lawson Core Technology.

Job queues Following are job queues that are created when using the Infor Lawson system:

• Default job queue (*********) • Additional job queues • Specify a job queue for a system code

Job queues are defined by system administrators to pool jobs together and determine the priority for system resources on execution. Typically job queues are created for the different areas of applications such as HR, AP, and GL etc. Where system administrators can then assign the priority which can allows an area jobs to access system resources at run with more importance.

A Lawson Security role must then provide authorization to the job queue for user attempting to access. Security for the Lawson job queues will be discussed in Lesson 12.

Demo: Defining a job queue Your instructor will demonstrate how to define a Lawson job queue in jqdef.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 7.2: Defining a job queue In this exercise, you will define a Lawson job queue. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Type jqdef at the Command line of LID and press Enter. 2. Type FINANCE in the Job Queue Name field and press Tab.

3. Type 2 in the Max Number field and press Tab.

4. Type 2 in the Max Number Update field and press Tab.

5. Type 28 in the Priority field and press Tab.

6. Press F4.

7. Click the down arrow to Active and press Enter.


@ 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. Type HR in the Job Queue Name field and press Tab.

9. Type 2 in the Max Number field and press Tab.

10. Type 2 in the Max Number Update field and press Tab.

11. Type 24 in the Priority field and press Tab.

12. Press F4.

13. Click the down arrow to Active and press Enter.

14. Press Enter twice to save the job queue definition.

15. Access Infor Lawson for Ming.le™.



17. Navigate to the Job and Reports bookmark.

18. Select Job List. 19. Click the magnifying glass icon.

20. Search for JobName=CU201.

21. Right-click CU201 > FINANCE job queue to submit.

22. Select Job Scheduler from Job and Reports and notice the job ran in the FINANCE queue.

The priority of a job queue should be between 21-39 and never 20 or lower. The online default priority for resources is 20 which would create contention between the batch jobs running and the online programs.

Demo: Defining a job queue default for system code Your instructor will demonstrate how to define a Lawson job queue as a default for a system code or a productline using jqdflt.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) What Lawson command will invoke a printer on Windows OS?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What is the lowest priority a system administrator should assign a job 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.

Lesson 8: Infor Lawson System Foundation maintenance Estimated time 6 hours


• List routine maintenance concerns for the Infor Lawson System. • Explain how to remove unneeded Infor Lawson files. • List all the LSF10 required products and where to locate the update procedures. • Explain how to apply Critical Transfer Packages (CTP) to Infor Lawson Applications. • Describe the enhancements to the Infor Lawson Enterprise Application update process. • Describe the new procedures for copying an Infor Lawson Enterprise Applications productline. • Explain how to apply environment patches to the Infor Lawson Core Technology. • Describe how to access Infor Lawson Information Investigator, collect information, interpret the

data, and create a package for Global Support. • Explain how to install or update Infor Lawson Employee and Manager Self-Service. • Explain how to work with LDAP Administration tools (ssoconfig, ldifgen and LDAP browser).

Topics • System maintenance • Check your understanding • Lawson System Foundation maintenance overview • Infor Lawson Enterprise Applications maintenance • Infor Lawson Core Technology maintenance • Check your understanding • Installing Infor Lawson product • ssoconfig utility • Schema Editor • LDAP administration • Check your understanding

82 Lesson 8: Infor Lawson System Foundation maintenance © 2013 Infor Education

@ 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 maintenance

Infor Lawson Server Administration: Server Setup and Maintenance Guide

This section introduces to routine maintenance concerns with the Infor Lawson System.

Backups

• Perform backups of DB, LSF server directories, LDAP etc. • Perform backups of Microsoft SharePoint and Ming.le. • Perform backups of Landmark DB and server directories. • Perform backups of web servers. • DerbyDB space until RDBMS option is provided for federation synchronization.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

File cleanup

• LAWDIR\Print (.dtl and .rpt) “deljobhst” • LAWDIR\PDL\rptmap (versions) • LAWDIR\PDL\work • LAWDIR\system\*.logs • LAUNTDIR\ • Additional Landmark server maintenance is covered in the Landmark Foundation and

Administration course however; logs for JVMs and others require rotation or 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.

Demo: Using the deljobhst utility Your instructor will demonstrate how to use the Delete Job History utility (deljobhst).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.1: Using deljobhst to remove batch job and print files In this exercise, you will use deljobhst to remove batch jobs and print files created during class. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access a LID command line.



3. Type deljobhst in the Command line and press Enter. A list of parameters will display.

4. Type deljobhst –ckrv –uUSSPLU143\lawson –fmmddyy mmddyy in the Command line (where -fmmddyy is the start of the class and mmddyy is through tomorrow).

5. Use the up arrow to recall the last command.

6. Remove k and press Enter. This will remove the files.

7. Confirm that the files have been deleted in Job Scheduler and from the LAWDIR\print directory structure.

8. Type deljobhst –ckrv curdate – 30 in the Command line and press Enter. This will remove any files older than 30 days from the system date.

9. Use the up arrow to recall the last command.

10. Remove k and press Enter. This will remove the files.

11. Confirm that the files have been deleted in Job Scheduler and from the LAWDIR\print directory structure.

To capture results of the deljobhst utility add > deljob.log on the end of the command. A file will be created from the directory in which deljobhst was executed.


@ 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) What kinds of files does the Lawson System generate as it runs?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Why would you want to delete such 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.

Lawson System Foundation maintenance overview The following table includes a list of required products to use with Infor Lawson System Foundation 10 and the associated documentation for each product.

LSF10 required products Procedure

Infor Ming.le™ Foundation Download from Xtreme to the Infor Ming.le server and execute from the Infor Ming.le installer (.exe). Follow instructions in the Infor Ming.le Installation and Configuration Guide.

Infor Lawson for Ming.le™ Download from Xtreme to LSF and the web server executing the install (.jar). Follow instructions in the Infor Lawson for Ming.le™ Installation Guide. (Plug-in update via SharePoint/Ming.le server. Follow instructions in the Infor Lawson Plug-ins for Infor Ming.le™ Installation Guide applying update.)

Infor Smart Office Download from Xtreme to the ISO server and apply via LifeCycle Manager. Follow instructions in the Infor Smart Office Installation Guide for LifeCycle Manager 10.x.

Landmark Technology Download from Xtreme to the Landmark server executing the install (.jar). Follow instructions in the Infor Landmark Installation Guide. (The Landmark Administration course is highly recommended for administering and maintaining.)

Infor Security Services and DSSO Download the Distributed Security Package from Xtreme to the LSF server. Follow instructions from the Infor Lawson Distributed Security Package Installation Guide.

Infor Lawson System Foundation Download the SP or LSFCT from Xtreme to the LSF server. Follow instruction from the Infor Lawson Core Technology Installation Guide applying updates.

Infor Lawson Enterprise Applications Download the Maintenance Service Package (MSP) or Critical Transfer Package (CTP) from Xtreme to the LSF server. Follow instructions from the Critical Transfer Package (CTP) Installation Guide applying updates.

Check Xtreme Support for all critical updates.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson Enterprise Applications maintenance

Infor Lawson Application Maintenance Toolset (AMT) Infor Lawson Application Maintenance Toolset (AMT) is delivered as part of the Infor Lawson System Foundation (LSF). AMT includes the lawappinstall perl script located in GENDIR\bin.

Process overview MSPs and CTPs are applied to your productline using lawappinstall. The lawappinstall utility has five directives:

• Preview • Update • Stage (new parameter) • Activate • Uninstall

The preview directive updates the preview.log and appinstallanalysis.log within the PDL\Admin directory.

The update directive will execute a backup of source based on patch and delivers the new source code and updates the install.log within the PDL\Admin directory.

The stage directive will execute a blddbdict and compiles the new application, but in the PDL\stgcmp directory to reduce the time of activate.

The activate directive will execute blddbdict, dbreorg, and compile the new application. (No users can be on the system.) If the stage directive was used then activate will use the components in the stgcmp directory.

The uninstall directive will remove a patch from the system updating the source code from the backup of patch delivery. The install.log is updated. (Patches must be backed off in reverse order of application until desired patch removal and then applied again.)

Whenever the preview, activate, or uninstall directives are executed, information is appended to the appinstallanalysis.log.

Library Impact Analysis overview Library Impact Analysis produces the appinstallanalysis.log when applying an MSP and CTP. This log is a report of the true impact the patch has on programs. The report identifies if a program is actually affected by pdlib functional code changes. Not every program is affected by library code changes and this new report will help you identify those that are. This can help in determining a testing plan for the MSP and CTP.

The Library Impact Analysis report is produced on all supported platforms and is found in the applicable location:

LAWDIR > productline > Admin > appinstallanalysis.log

Content of appinstallanalysis.log Each preview, activate, and uninstall appends to the appinstallanalysis.log with a report section starting and ending with a header and corresponding footer. The following example for PATCH85212 was produced by performing:

perl GENDIR/bin/lawappinstall preview <productline>


@ 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.

Appinstallanalysis preview started at 08/22/2013 10:28:23 for the following deliverables: PATCH85312.preview.

Summary:

Source Files Changed: 2 Programs Compiles: 4 Programs Changed: 3

Detail:

Program Compiled Functionality Changed Called Programs(s) with Changes

RQ10 YES YES RQ11 YES YES RQ35 YES YES RQIH YES NO

Appinstallanalysis preview completed at 08/22/2013 10:28:24 for the following deliverables: PATCH85312.preview.

A report section starts and completes with a matching header and footer starting with “Appinstallanalysis preview.”

• The Program column identifies all the programs being updated by the installation. • Compiled indicates the program will be compiled due to MSP or CTP. • The Functionality Changed column indicates if the program was affected by any functional

changes in the program or pdlib. • Called Program(s) with Changes identifies programs that are affected because they call a

program being directly affected by the MSP or CTP.

Patch 85312 produced a report section indicating that four programs were identified as needing to be compiled. Only three programs were identified as “Functionality Changed.” The highlighted RQIH uses a changed PDLIB but the routine within the PDLIB used by RQIH was not changed. All programs with “Functionality Changed” of YES should be tested. Programs denoted with NO “Functionality Change” would be optional.

The productline is updated with CTP 85312, but it has not yet been activated. The lawappinstall preview produces a consolidated analysis for all‐updated‐not‐yet‐activated installations in addition to the CTP being previewed. Appended to appinstallanalysis.log, is a report section containing the consolidation of all‐updated‐not‐yet‐activated installations plus the CTP being previewed.

This is an example of a report section where the productline was updated with PATCH85312 and PATCH86840 is being previewed. PATCH85312 has not been activated.

Appinstallanalysis preview started at 08/22/2013 11:54:21 for the following deliverables: PATCH86840.preview PATCH85312.4.

Summary:

Source Files Changed: 6 Programs Compiles: 9 Programs Changed: 8

Detail:

Program Compiled Functionality Changed Called Programs(s) with Changes

AC160 YES YES AM115 YES YES AM117 YES YES AM15 YES YES AP13 YES NO


@ 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.

RQ10 YES YES RQ11 YES YES RQ35 YES YES RQIH YES YES

Appinstallanalysis preview completed at 08/22/2013 11:55:26 for the following deliverables: PATCH86840.preview PATCH85312.4.

This report section is delimited by “Appinstallanalysis preview” and contains the programs affected by PATCH86840 and PATCH85312.4. Notice that functionality changes have been introduced in PATCH86840 such that RQIH has been identified as “Functionality Changed” (via a YES). All programs with “Functionality Changed” of YES should be tested and those with NO can be optionally tested.

Summary of modified files overview

In the past, identification of modified files impacted by applying an MSP or CTP was difficult to locate in the log files as they were disparately distributed among non‐modified files. The Modified File List enhancement produces a summarized list of all impacted modified files when the preview or update directive is used.

Modified file 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.

Modified file summary list

Demo: Applying Infor CTP for Lawson Enterprise Applications using the Stage option in Application Maintenance Toolset Your instructor will demonstrate how to apply a CTP with the new stage parameter 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.

Exercise 8.2: Applying a CTP with the Stage option In this exercise, you will access and update the productline with a CTP using the Stage parameter option. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access the Desktop > ClassInfo10x folder.

2. Copy the CTP folder.

3. Access GENDIR\install (C:\LSFENV\gen\install).

4. Paste the CTP folder in the GENDIR\install directory.

5. Access the CTP folder and open in Winzip extracting the patch to the GENDIR\install\CTP folder.

6. Access Lawson Interface Desktop (LID) from the desktop.

7. Select the Uss143 server settings.


9. Type cd %GENDIR%\install\CTP in the Directory field to change the directory location of the CTP.

10. Type ls –l in the Search field to validate the patch is in the directory.

11. Type perl %GENDIR%\bin\lawappinstall preview APPS10 at the Command line to run the patch in preview mode.

12. Type perl %GENDIR%\bin\lawappinstall update APPS10 at the Command line to run the patch in update mode.

13. Type perl %GENDIR%\bin\lawappinstall stage APPS10 at the Command line to run the patch in stage mode. (The compiles are completed at the new stage with reorgs upon activate.)

14. Type perl %GENDIR%\bin\lawappinstall activate APPS10 at the Command line to run the patch in active mode.

15. Access LAWDIR\apps10\Admin and review the logs generated.

After application compiles are complete using the qstatus to verify, the LAWDIR\ProductLine should be checked for *.err. Search folders for *.err and resolve when present.

When a “Stage” is in process qcompile must be used with –O or –A depending if you want to compile directly or include in the stage directory LAWDIR > PDL > stgcmp.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

Copying a productline The Copy Productline procedure has been updated to include creating a new productline, overlaying an existing productline, clarifying appmetadiff differences, and scenarios for appmetadiff resolution. The new procedures are available in the Server Setup and Maintenance Guide and should be followed on LSF10.

For class discussion on the copy productline procedure open the Server Setup and Maintenance Guide from the Infocenter.

1. On Ussplu143 access IE > Infocenter > Lawson System Foundation.

2. Open Lawson System Foundation > Server Administration > Server Setup and Maintenance Guide > Product Line Maintenance > Product Line Copying, Data, and Other Objects.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 Lawson Core Technology maintenance This section introduces applying patches to the Infor Lawson Core Technology.

Demo: Applying the LCT patch Your instructor will demonstrate how to apply the LCT patch.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.3: Applying the LCT patch In this exercise, you will apply the LCT patch. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Stop WebSphere Services then the Lawson Environment Service:

a. In Services, stop IBMWAS70Service - LSFENV (App Server).

b. In Services, stop IBMWAS70Service – LSFENV-Mobile (App Server).

c. In Services, stop lawson.insight.environment “LSFENV”.

2. Access the Desktop > ClassInfo10x folder and copy the LCT folder.


4. Paste the LCT folder in this directory.

5. Access the LCT folder and open in Winzip extracting the patch to the GENDIR\install\LCT folder.

6. Select Start > Run and cmd (windows prompt).

7. Type cd C:\LSFENV.

8. Type enter (sets environment variables).

9. Type cd %GENDIR%\install\LCT.

10. Type java –jar *.jar.

11. Select Next.

12. Select the LSFENV environment to update.

13. Select Next to start the process.

14. Select Finish with Patch Completed Successfully.

15. The Lawson Environment should be started post LCT completion. Verify the Environment is running then start the WAS Application Servers (LSFENV and LSFENV-Mobile).


@ 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.

16. Execute a quick test by accessing IE shortcut and logging into Ming.le and open Infor Lawson for Ming.le™.



%GENDIR%\assembly\components\ear has received three new core technology and one mobile monitor files requiring deployment in WebSphere. Lesson 9 discusses components of WebSphere and the deployment process for the .ear files.

Infor Lawson Information Investigator Installation and User Guide

Infor Lawson Information Investigator (LII) The Infor Lawson Information Investigator (LII) is a Perl-based tool used to collect hardware and software information from servers, including information on Infor Lawson product installations.

The Infor Lawson Information Investigator collects data from the following:

• Operating systems • Microsoft Windows Server • IBM AIX • HP-UX • Sun Solaris • OS/X • IBMi • Server data • CPU • Memory • Disk space • Software versions • Java • Perl • Subversion • AccuRev • CVS • Microsoft SQL Server • Oracle database • IBM DB2 • IBM WebSphere • MKS Toolkit • Environment information • Infor Lawson System Foundation and Infor Landmark Technology Runtime environments • Infor Lawson System Foundation and Infor Landmark Technology Runtime productlines • Server configuration (database, application server, productline source control, languages

installed) • Infor Lawson Budgeting and Planning • Infor Lawson Business Intelligence


@ 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 the LII on all servers hosting Infor Lawson-provided software as well as servers providing support for Infor Lawson-provided software, such as database and LDAP servers.

Install the LII in one of the following configurations:

Centralized configuration

The LII uses an integrated web-based interface to view the information collected and to manage the LII on each server. The client hosts can communicate with the central server, allowing tool updates and data collection to run in a semi-automatic mode.

You do not need to install the central server on the same server as other Infor Lawson-provided software. Additionally, the server may or may not be dedicated for LII reporting. The LII is not intended to have production vs. test instances, but is a comprehensive reporting of all configured servers.

For security reasons, you may not want to install LII in your "DMZ." The LII presents minimal risk, but it does not use authentication or encryption, and is currently intended for in-network use.

There should only be one central server configured on your network.

Standalone configuration

A standalone configuration is treated like a centralized configuration, but the central server is localhost.

Note: While Infor does not recommend this configuration, it can be used for testing.

LII installation summary:

1. Install the central LII server (host).

2. Install secondary servers communicating back to the central LII server.

3. Configure LII.

Demo: Exploring 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: Exploring Infor Lawson Information Investigator In this exercise, you will access the LII web interface and explore the versioning data on your servers. You will use Ussplu143 (LSF) for this exercise.

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 collectall 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. Click the down arrow icon next to ussplu143.lu141training.lawson.com.

10. View all the collected data concluding on LSFEnv.

11. Select the Graphical option to view the same information in a different presentation.

12. Close the tab.

13. Collapse the down arrow icon next to ussplu143.lu141training.lawson.com.

14. Expand the down arrow icon next to ussplu141.lu141training.lawson.com.

15. View all the collected data concluding on LMKEnv.

16. Select the Graphical option to view same information in a different presentation.

17. Close the LII web user interface (UI) browser.

The Package All Information option will create a single package.xml file that you can transfer to Infor Xtreme Support.

Additional LII features

• The Update command will rebuild the versioning information on the servers where collect is a retrieval.

• Create a purpose.txt file in the LII directory and any information contained within will be pulled into the server.xml. The server.xml represents the server data.

• Create a purpose.txt file in the LAWDIR system for LSF or LASYSDIR for Landmark and any information contained within will be pulled into the ENV_name.xml. The ENV_name.xml represents the environment data. There can be multiple ENV_name.xml depending on the number of environments installed on the server.

• A collection can be scheduled through the command line LII processing. The web UI commands may be executed from the perl lii.pl command execution where command represents the required process. For scheduling a collection execute perl lii.pl schedule then to disable perl lii.pl noschedule.


@ 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) What log would show all LCTs applied to an environment?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What log would show all CTPs applied to a productline?

______________________________________________________________________ ______________________________________________________________________

3) What are the benefits of the 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.

Installing Infor Lawson product In this section, you will experience installing an Infor Lawson product. Installing and updating most products follow the same procedures.

Demo: Installing Employee and Manager Self-Service Your instructor will demonstrate how to install the Self-Service products.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.5: Installing Employee and Manager Self-Service Self-Service center instructions are from the Lawson Employee and Manager Self-Service Installation Guide and modified for classroom images. In this exercise, you will install Employee and Manager Self-Service update. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access the Desktop > ClassInfo10x folder and copy the SelfServiceBase folder.


3. Paste SelfSeviceBase folder.

4. Select Start > Run and cmd (windows prompt).

5. Type cd C:\LSFENV in the Window prompt.

6. Type enter in the Window prompt.(sets environment variables).

7. Type cd %GENDIR%\install\SelfServiceBase in the Window prompt.

8. Type java –jar *.jar in the Window prompt.

9. Select the everything option to install all components.

10. Click Next. 11. Select the LSFENV environment.

12. Click Next. 13. Select WEBDIR and browse to C:\LSFENV\webdocs.


@ 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. Click Next. Notice: InstanceDir C:\lawson\emss.

15. Click Install if ready to proceed.

16. Check for errors in the log.

17. Access the Desktop > ClassInfo10x folder and copy the SelfServicePatch folder.


19. Paste SelfSevicePatch folder.

20. Type cd %GENDIR%\install\SelfServicePatch in the Windows prompt.

21. Type java –jar *.jar in the Windows prompt.

22. Select the everything option to install all components.

23. Click Next.

24. Select the LSFENV environment.

25. Click Next. The emss instance is used to determine WEBDIR.

26. Click Install if ready to proceed.

27. Check for errors in the log.


@ 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.

ssoconfig utility In this section, you will be exposed to the ssoconfig utility of Infor Lawson System Foundation. The ssoconfig utility is used to control many settings and setup for the environment and LDAP.

Demo: ssoconfig utility Your instructor will demonstrate the properties and menu for ssoconfig.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

Schema Editor Resources have predefined attributes required for Lawson processes. Lawson delivers the ability to add additional attributes for clients’ unique requirements.

The process of adding new attributes has four steps:

1. Add/modify and associate the new attribute to an object such as a resource.

2. Use the idifgen utility to compare the existing LDAP schema to the new one after additions and changes. This utility creates files in the format needed for the LDAP modification.

3. Load the update files into the existing LDAP schema using the modify command from AD LDS or TDS.

4. Stop and start of the Lawson Security Service. This allows for Lawson to recognize the additions and changes to LDAP.

Demo: Schema Editor Your instructor will demonstrate how to use the Schema Editor to change or add attributes to the Lawson LDAP.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.6: Working with Schema Editor / LDIFGEN / adding an attribute In this exercise you will add an additional attribute. This can then be used later in determining security access for a user. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access Schema Editor > RM Attributes. All attributes should appear on the right section.

2. Right-click and select Create Attribute.

3. Type USSRequestingLocation in the Name and Display Name fields.

4. Add a list containing SURG, FL1, FL2, FL3, FL4 and FL5 for a multi-valued list.

5. Select 5 in the Size field to designate a string.


@ 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. Select Write permissions.

7. Type USSUserType in the Name and Display Name fields.

8. Add a list containing HR, Payroll, Finance, AP, ESS, MSS, and RQC for a multi-valued list.

9. Select 25 in the Size field.

10. Select Write permissions.

11. Select RM Object > People.

12. Right-click Add Attribute.

13. Connect the USSRequestingLocation by adding and accepting the defaults until the end.

14. Click Finish.

15. Repeat steps 13 – 14 for USSUserType.

16. Launch LID.



18. Type cd %LAWDIR%\system in the Command line.

19. Execute:

ldifgen xmltoschemaldif RmMeta_Default.xml -r reorg.ldif -f schema.ldif -m update.ldif -D CN=ldapadmin,CN=Users,DC=lu141training,DC=lawson,DC=com -h localhost -p 389 -w Tr@in123

20. Run ldifde process to load new reorg.ldif, schema.ldif and update.ldif to LDAP created in the previous step.

21. Execute: ldifde -s localhost -t 389 -i -f reorg.ldif

(0 byte file – Unable to read message will result.)

1. Execute: ldifde -s localhost -t 389 -i -f schema.ldif

2. Execute: ldifde -s localhost -t 389 -i -f update.ldif 3. Execute: stoplase (active users would be affected).

4. Execute: startlase.

5. Access Lawson Security Administrator from desktop shortcut.

6. Select User Management > User Maintenance.

7. Type lawson* in the query field and press Enter to locate lawson.

8. Right-click and select Edit RM Information. Verify that both attributes are now present on lawson.

9. Type ESS in the Designation field for USSUserType.

10. Close the window and Save upon exit.

For Tivoli LDAP ldapmodify –D user –w password –v –a –c –f *.ldif 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.

LDAP administration Infor Lawson System Foundation requires an LDAP of Microsoft AD LDS or IBM Tivoli. The LDAP directory will contain all resources, roles, groups, structures, security information and configurations. Understanding the LDAP directory and schema is an important function of a Lawson System Administrator.

LDAP may require maintenance outside of Lawson’s presentation options of Resource Administrator or Infor Lawson Security Administrator. An LDAP browser will allow a System Admin to view the LDAP schema and data without accessing Lawson. An LDAP browser will be required as a System Administrator, most commonly to assist in support cases where Lawson needs a view directly to LDAP. There are several shareware browsers available. The “jxplorer” LDAP browser was selected in support of this training and can be downloaded from http://www.jxplorer.org.

Demo: LDAP browser and LDAP structure Your instructor will demonstrate how to use an LDAP browser to view the LDAP structure and data.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 8.7: Navigating in LDAP browser Learning to navigate the Lawson LDAP tree may help in times of data corruption or user errors, or if a client was to lock themselves out of Security by eliminating from any user the Super Admin Role. Or, a client could lock Mass Assignment and not have access to the user locking to execute a reset. The Lawson Support and Delivery may instruct a System Admin to correct through a browser. In this exercise, you will navigate in the LDAP browser. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access Start > All Programs > JXplorer > JXplorer browser.

2. Execute a file/connect and from the saved connection options choose ussplu143.

3. Type Tr@in123 in the password field.

4. Notice lwsnrmdata and lwsnSecData for Schema.

5. Expand lwsnrmdata > Resources.

6. Locate lwsnSecData.

7. Use idxref for the user’s information of Identities. Generally explore how Lawson organized its LDAP schema.

8. Close JXplorer.


@ 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) List the discussed steps for properly installing or updating an Infor Lawson product.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What utility is used for changing LDAP settings?

______________________________________________________________________ ______________________________________________________________________

3) What file contains the current structure of Lawson LDAP and in what directory can it be found?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 9: IBM WebSphere® administration Estimated time 2 hours


• Describe the WebSphere® architecture and directory structure. • Define WebSphere® terminology. • Explain how to apply the IBM update installer and fix packs. • Explain the WebSphere® processes and startup procedures. • Describe how to manage the WebSphere® Deployment Manager, application server

configuration and Enterprise Application. • Describe how to generate the Plugin-cfg.xml and propagate. • Explain how to conduct troubleshooting. • Describe the process to review log files.

Topics • WebSphere® architecture overview • Requirements for Infor Lawson System Foundation • Terminology • IBM WebSphere® directory structure • Integrated Solutions (Administrative) Console • Check your understanding

This section does not cover installing, tuning or non-Lawson uses of 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.

IBM WebSphere® architecture overview In this section, you will review the architecture of IBM WebSphere and its importance in Infor Lawson System Foundation.

WebSphere architecture

• User interface – Infor Lawson for Ming.le™ via Internet Explorer • Plug-in – location defined in IBM Http Server • IBM Http Server • Application server – one per environment • Java servlet – jar files • Administrators console

106 Lesson 9: IBM WebSphere® administration © 2013 Infor Education

@ 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.

Requirements for Infor Lawson System Foundation The Infor Lawson System Foundation must be deployed in an application server within a node that is federated to the WebSphere® Network Deployment Manager. For each Environment on your system, you create the following within the node:

• A custom profile for each Environment. Lawson recommends that you include the Environment name in the profile name, for example lsfprod1_profile

• A WebSphere® application server, configured with values specific to the Environment. • A virtual host, which defines the unique ports over which the web server and application server

communicate. • A web server with a unique listening port.

A configured WebSphere® instance includes your servlet container. WebSphere® also can include an installation package for IBM Http Server which once installed is embedded within the WebSphere® server. Clients can opt to use Information Investigator Services (IIS) if on Windows and can also configure for a remote or local web server.

All web traffic from a user’s web browser and traffic from the deployment manager admin console travel to WebSphere® via http/https calls. A call from within Infor Lawson uses servlet technology. An http web server is specifically for http requests, therefore, to process a servlet call we use a plugin-cfg.xml file to redirect servlet calls to the application server. The location of your plugin-cfg.xml file is defined in your httpd.conf file.

JVM classpath entries and environment variables are configured within the application server, which is typically a one-to-one ratio with the Infor Lawson Environment. If you are doing vertical scaling it is possible to have multiple application servers in a cluster pointing to one environment. This allows for better performance and would be implemented with your 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.

Terminology Application server: A software engine that delivers applications to client computers or devices, typically through the Internet and using the HyperText Transfer Protocol. Application servers are distinguished from web servers by the extensive use of server-side dynamic content and frequent integration with database engines (as defined on http://en.wikipedia.org/wiki/Application_server).

Cell: A collection of nodes managed by a Deployment Manager.

Federated (managed): A federated or managed application server is a node defined in the cell of a WebSphere® Application Server Network Deployment topology that has a node agent running to manage its process. Lawson uses this type of deployment for its application server.

Network Deployment Manager: Provides an operating environment with advanced performance and availability capabilities in support of dynamic application environments. In addition to all of the features and functions within the base WebSphere® Application Server, this configuration delivers advanced deployment services that include clustering, edge-of-network services, web services enhancements, and high availability for distributed configurations.

Node: A logical grouping of application servers

Node agent: A process that manages a single node. It allows for communication of administrative information to reach the application.

Profile: defines the runtime environment for the application server. The configuration for every defined application server process is within the profiles directory unless you specify a new directory when you create a profile. The following list shows default installation locations for root users on supported platforms:

/usr/IBM/WebSphere/AppServer

/opt/IBM/WebSphere/AppServer

C:\Program Files\IBM\WebSphere\AppServer

The app_server_root/profiles directory is the default directory for creating profiles.

Default installation locations for supported platforms

Virtual host: Configuration that lets a single host machine resemble multiple host machines. Each virtual host has a logical name and a list of one or more domain name system (DNS) aliases by which it is known. It is acceptable for Lawson Developers to use the default_host.


@ 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://en.wikipedia.org/wiki/Application_server

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.express.doc/info/exp/ae/rins_dircon.html

IBM WebSphere® directory structure As part of the implementation planning you will determine if the IBM WebSphere® default directory locations below will work for your system. The paths on your server may be different. These locations can be changed during the install process.

The recommendation is to set variables for your app_server_root (i.e., WAS_HOME) and your web_server_root (i.e., IBMHTTP_HOME) and enter these in the appropriate location on your system (i.e for Unix and iSeries in /etc/lawson.env, Windows enter.cmd file).

By default, IBM WebSphere® application server (app_server_root) is installed in:

• AIX - /usr/IBM/WebSphere/AppServer • HP and Solaris - /opt/IBM/WebSphere/AppServer • Windows – C:\Program Files\IBM\WebSphere\AppServer • iSeries - /QIBM/ProdData/WebSphere/AppServer/V61/ND

By default, the Profile (profile_root) directory is installed in:

• AIX - /usr/IBM/WebSphere/AppServer/profiles • HP and Solaris - /opt/IBM/WebSphere/AppServer/profiles • Windows – C:\Program Files\IBM\WebSphere\AppServer\profiles • iSeries -/QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/profile_name

By default, the IBM-HTTP Server* (web_server_root) is installed in:

• AIX - /usr/IBM/HTTPServer • HP and Solaris - /opt/IBM/HTTPServer • Windows – C:\Program Files\IBM\HTTPServer • iSeries - /www/web_server_name

By default, the plug-ins* (plugin_root) is installed in:

• AIX - /usr/IBM/HTTPServer/Plugins • HP and Solaris - /opt/IBM/HTTPServer/Plugins • *Windows – C:\Program Files\IBM\HTTPServer\Plugins • iSeries - /QIBM/ProdData/WebSphere/Plugins/V61/webserver

*NOTE: When using IIS your path for the plugin-cfg.xml can be found in plugins_install_root \bin\IIS_ Web_servername/plugin-cfg.loc

IBM Update Installer The IBM Update Installer is used to apply updates and fix packs to IBM WebSphere Portal and affiliated products.

The WebSphere Portal Update Installer is version-specific and is used to install or uninstall interim or cumulative fixes, fix packs, and other maintenance delivery vehicles.

More information regarding the Update Installer can be found here:

http://www-01.ibm.com/support/docview.wss?uid=swg24006942


@ 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-01.ibm.com/support/docview.wss?uid=swg24006942

IBM WebSphere® processes on your system To locate the application server processes that have been configured on your system you will need to go to the profile_root directory. Within this directory is a directory for the dmgr01 process, which is your deployment manager process. Also in this directory you will find the profile for your application server. Typically this gets named to reflect your server name.

The WebSphere® Deployment Manager process must be running in order to use the Administrative Console to manage the WebSphere® Application Server and the Lawson Enterprise Applications deployed in it. The Administrative Manager Console allows the maintenance of multiple tasks for multiple environments from one point of access.

Typically all stop and start commands for processes are located within the bin directory beneath the parent directory for that process. For example, to find the start command for the deployment manager you would have to go to /usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin. In this directory you would use the startManager command to start the deployment manager process.

The start process rules are as follows as set forth by IBM:

Rules for process startup The order of process startup needs to adhere to the following rules:

• A node agent can be running while the deployment manager is not, and vice versa. When the stopped process is started, discovery will occur automatically.

• The deployment manager can be running while a managed server is not, and vice versa. The execution of a managed server is not dependent on the presence of a running deployment manager. The deployment manager is only required for permanent configuration changes written to the master repository.

• The node agent should be started before any application servers on that node. The node agent contains the Location Service Daemon (LSD) in which each application server registers on startup.

• The node agent is purely an administrative agent and is not involved in application serving functions. Each managed server has the data necessary to start itself.

With Lawson the recommended start/stop process of all servers/services is as follows:

Starting the system 1. Database

2. LDAP Server

3. Lawson Environment

4. WebSphere®

a. Network Deployment Manager - $WAS_HOME/profiles/Dmgr01/bin/ execute: ./startManager.sh

b. Node Agent - $WAS_HOME/profiles/AppSvrNode/bin/ execute: ./startNode.sh

c. Application Server - $WAS_HOME/profiles/AppSvrNode/bin execute: ./startServer.sh servername


@ 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.

Stopping the system 1. Web Server

2. WebSphere®

a. Application Server - $WAS_HOME/profiles/AppSvrNode/bin/ execute ./stopServer.sh

b. Node Agent - $WAS_HOME/profiles/AppSvrNode/bin/ execute ./stopNode.sh

c. Network Deployment Manager - $WAS_HOME/profiles/Dmgr01/bin/ execute ./stopManager.sh

3. Lawson Environment

4. LDAP Server

5. Database

Typically if there are issues with your system, you will find that you do not always need to stop or restart your database, LDAP server and web server. The stop and start of the WebSphere® Application Server within the Admin Console and Lawson Environment will usually resolve most issues.

WebSphere Deployment Manager must be running to use the console for starting and stopping applications or servers or deploying ear files. The Deployment Manager will allow the maintenance of multiple environments from one area of access. Deployment Manager is already running on Windows therefore only a demonstration of Cell Manager Service is required.

Demo: Starting and stopping IBM WebSphere® Deployment Manager process Your instructor will demonstrate how to verify the Deployment Manager is running or starting and stopping.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Options:

1. From LID as user lawson

2. cd \IBM\WebSphere\AppServer\profiles\Dmgr01\bin

3. ./startManager.bat (./stopManager.bat can be used to stop deployment manager)

Or

1. Services> IBM WebSphere Application Server Cell Manager and right-click Start

Or

1. Click Start > Programs > IBM WebSphere > Application Server Network Deployment v6 > Profiles > Dmgr01 > Start the deployment manager or Start WebSphere Manager 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.

Integrated Solutions (Administrative) Console To access the WebSphere® Administrative Console (note with 6.1 it is now called the Integrated Solutions Console):

Launch a web browser window and go to http://yourservername:9060/ibm/console. You can also go to http://yourservername:9060/admin. Either of these URLs will launch the Administrative Console.

Launch the Administrative Console at IE > Favorites > WebSphere Integrated Solutions Console.

The login page displays.

Integrated Solutions Console

On this installation, security is NOT enabled, no login is needed. Your admin users do not have to authenticate to log in to the Administrative Console.

The port number is determined during the installation of WebSphere®. The default port for the Administrative Console is 9060. Check exit documents from the installer for the port # at your location.


@ 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://yourservername:9060/ibm/console

http://yourservername:9060/admin

After logging into the Administrative Console, the Welcome screen displays.

Administrative Console Welcome screen

At the top right corner of the screen are a Logout and a Help link. If you click the WebSphere® Application Server link in the middle under the Welcome message it will open up a four-paneled information area in the content area with links to IBM product information, a panel with version information about your WebSphere® installation, a link to the IBM developerWorks, and a link to IBM documentation. On the left side is your navigation panel with access to configuration and servers.

Some of the navigation tasks you will need to become familiar with on the Administrative Console are:

• Start and stop application server • Install, update, uninstall, stop and start Lawson web applications • Configure WAS for Lawson • Start and stop web server (IHS only) • Generate web server plug-in • View information about cells and nodes • Configure logs and tracing • Configure virtual hosts


@ 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.

IBM WebSphere® Application Server Within the Administrative Console on the left side of the page is the navigation pane. Navigate to Servers > Server Types and expand that link.

Administrative Console navigation pane

You will then see a listing of any application servers you have installed on your system. In this case we have one application server that corresponds with our LSF9 environment.

Note the node that this application server is installed in. Typically you would install similar applications under one node. For instance, Mobile Supply Chain Management (MSCM) is a different type of application, in other words it is not a full LSF9 installation so you may want to install that in a different node. The same goes for Landmark; if you were to install Landmark you would want to create a different node for that as well.

Across the top of the application server window are your function buttons. To stop and start the application server you would place a check mark next to the application server to select it and click stop or start.


@ 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 your Classpath When installing a new application server for a new Lawson environment, there is some configuration that you need to do. Essentially you will need to configure your classpath for your servlet processing, as well as environment entries so WebSphere® knows how to find your environment. Below are the three areas within your WebSphere® Application Server that need to be configured.

Configure classpath in the following three areas:

• Application server configuration • Servlet processing • Environment variables and paths

To view these entries using the Administrative Console:

1. Access Servers > Server Types > Applications servers.

2. Click the highlighted application server in blue. The server configuration screen displays. In this example, server1.

Server1 configuration 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.

Configure the application server with values specific to Infor Lawson

1. Beneath the Server Infrastructure section, click Java and Process Management.

2. Click Process Definition.

Java and Process Management options

The Java Virtual Machine is your servlet classpath.

Process Definition

3. Provide the locations to the Infor Lawson files for the JVM classpath of the application server. The entries for the Lawson Core Technology are:

\WAS70\AppServer\plugins \GENDIR\java\jar\lawsonrt.jar \GENDIR\java\jar\lawsec.jar \GENDIR\java\\thirdParty\ecLS.jar \GENDIR\java\\thirdParty\ldapbp.jar \LAWDIR\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.

The entries are populated in the screen below:

Classpath field populated with the JVM classpath

4. Under Custom Properties, define the environment values for the servlet classpath. Click Process Definition to go back to the main page.

Custom 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.

Configure your environment variables and paths 1. On the Process Definition page, click Environment Entries to define the environment values for

your system.

Process Definition

To define these variables on a new setup use the New button. To edit an existing value, click the name of the variable in blue you want to edit to open the variable definition page.

Complete detailed instructions for setting up WebSphere® can be found in the Lawson Core Technology Installation Guide for your release.

Terminology

Classpath: Specifies the standard class path in which the JVM code looks for classes. This is defined within your application server with Lawson-specific class files.

Java Virtual Machine: An interpreter and runtime environment for compiled Java code. Java Virtual Machines exist for most operating systems including UNIX, Macintosh, and Windows.

Java TM Native Interface (JNI): A standard programming interface for writing Java native methods and embedding the JavaTM virtual machine into native applications. The primary goal is binary compatibility of native method libraries across all Java virtual machine implementations on a given platform.


@ 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 server An application server can be stopped and started from command line execution or done through the WebSphere Deployment Manager. Windows clients do not typically stop and start WebSphere Application Server (WAS) using this process. The Windows services will not correctly show WAS status if executed through this process. Due to this, it’s a demonstration only.

Demo: Starting and stopping IBM WebSphere® Server Your instructor will demonstrate how to start and stop the WebSphere Application Server.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Options

From the Administrative Console http://servername:9060/ibm/console.

1. Click Servers >Server Types in the left navigation pane.

2. Click WebSphere Application Servers.

3. Check the select box next to the Application Server that needs to be stopped.

4. Click Stop.

5. When the message appears that the server has stopped successfully, click OK.

6. Notice the change in status for the server.

7. Check the select box next to the Application Server that needs to be started.

8. Click Start.

9. Notice the change in the status for the server.

Stopping Infor Lawson and IBM WebSphere® Before stopping the Lawson system using stoplaw, the IBM WebSphere® Application Server needs to be stopped. If Lawson is stopped before the IBM WebSphere® Application Server, the IBM WebSphere® Application server will stop, but not in a clean fashion. The reason behind stopping IBM WebSphere® before Lawson is that Lawson uses JNI to create a link between it and the WAS Application Server.

The Node Agent and Deployment Manager are used to manage the application server instance. These do not link to Lawson via a JNI therefore do not have to be stopped prior to shutting down 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.

http://servername:9060/ibm/console

Starting Infor Lawson and IBM WebSphere® Start the Lawson Environment and then the IBM WebSphere® Application Server. Lawson needs to be started first because the IBM WebSphere® Application Server needs to load shared libraries from Lawson when it starts.

Enterprise Applications The three main Lawson Enterprise Applications that Lawson delivers with the Core Technology installation are:

• LawsonSecurity.ear which contains servlets for Lawson Security. • BPM.ear which contains servlets for ProcessFlow. • IOS-ws.ear which contains servlets for IOS.

All of the .ear files associated with Lawson will be delivered to the GENDIR/assembly/components/ear directory. On an initial installation of the Core Technology, the installer will perform an “install” of the Enterprise Applications. When applying Core Technology patches or service packs, you will need to update the Enterprise Applications which is also referred to as deploying the application or *.ear file.

After the .ear files are deployed, the applications reside in: $WAS_HOME/AppServer/profiles/localhostNode01/installedApps/localhostCell01

The Cell01 directory contains lawsec.ear, IOS.ear and bpm.ear. Each of those .ear files contain the jar and class files deployed with each ear.

IOS Enterprise Application Common servlet and contents listing of IOS Enterprise Application:

IOS-ws.ear

Router

Drill

Transaction

Data

Profile

Xpress

JobServer

Report

Cgi-lawson

What

Tesla-ejb.jar

Manifest.mf


@ 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 IOS.ear contains three files: IOS.war, Manifest.mf and tesla-ejb.jar. The IOS.war is made up of all the servlet and class files necessary to run IOS. Listed are some of the most prominent ones.

The manifest.mf is a special file that can contain information about the files packaged in a JAR file. Tailoring this "meta" information that the manifest contains, enables the JAR file to be used for a variety of purposes.

Infor Lawson Enterprise Applications

The lawsec.ear is made up of the .war files necessary to run Lawson security. The application.xml file is the deployment descriptor for Enterprise Application Archives.

The Business Process Model Enterprise Application

The bpm.war file includes the war file necessary to run the Infor Lawson Process Automation product. In this case, there is only one war file. The application.xml and manifest.xml contain the information as described in the previous screen.

Deploying / Updating Enterprise Application files (*.ear) Deploying and updating applications in WebSphere® is done via the Deployment Manager console.

Under the Applications area of WAS Deployment Manager select the Enterprise Application navigation task to choose the Enterprise applications to update. Installing new enterprise applications is also done from this navigation task. Once the appropriate application is selected, click Update.

Lawsec.ear

Rmwebapp.war

Scwebapp.war

Sso.war

Ssoconfig.war

Application.xml

Manifest.mf

BPM.ear

Application.xml

Bpm.war

Manifest.mf


@ 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: Deploying and updating an .ear file Your instructor will demonstrate how to update the .ear files received during the LCT patch from Lesson 8.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 9.1: Deploying an .ear file In LSF10 an application or environment patch may require a deployment of an ear file. An ear file contains the jar and classes required for the application to run. In this exercise, you will deploy an .ear file. You will use Ussplu143 (LSF) in this exercise.

Exercise steps 1. Access IE > Favorites > WebSphere Integrated Solutions Console to launch the WAS

Console.

2. Select Applications > Application Types.

3. Select WebSphere Enterprise Applications.

4. Select *-IOS.

5. Click Update.

6. Select *-IOS.

7. Click Stop. Refresh status to view X stopped.

8. Select Remote File System > Browse.

9. Click ussplu143Node1.

10. Click the C:\ (drive).

11. Navigate to the %GENDIR%\assembly\components\ear path.

12. Select IOS-ws.ear file to deploy and then click OK. Verify the .ear matches the application to be updated.

13. Select Fast Path and click Next.

14. Accept all the defaults on the Select Installation Options screen and click Next. 15. Verify that all modules on Map Modules to Servers have both the application and web server

listed. If they do not, select the module with the missing paths then select both of the servers in Clusters and Servers section.

16. Click Apply.

17. Click Next to continue.


@ 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.

18. Click Finish on the Summary screen.

19. Select Save to Master Configuration.

20. Scroll down to review and look for the message that the Application *-IOS installed successfully.

21. Click Review.

22. Select Synchronize changes with Nodes (if not selected) and click Save.

23. Click OK when the message “ADMS0208l: The configuration synchronization complete for cell” displays.

The Deployment Process is captured in the Reference Section of this Lesson for future review and additional information.

Web Server Plugin-cfg.xml Generating the PlugIn-cfg.xml

The web server plug-in is installed during the installation process. A default plug-in file with basic WebSphere® information is included. After the Lawson Core Technology has been installed or updated, the plug-in configuration needs to be updated so the web server knows how to direct the Lawson servlets to the WebSphere Application server. This process is called generating web server plug-ins.

During the setup process, a web server is installed into the Deployment Manager console via the Web Server navigation task. After the web server is installed, the plug-in can be generated.

Propagating the Plugin-cfg.xml

If the web server being used is IBM HTTP Server and the web server is local, the propagation of the plug-in will automatically be written to the correct location based on information given during the plug-in installation process. The correct location of the plug-in file is determined by the path in the IHS httpd.conf file.

If the web server is remote (not installed on the application server), or IIS is being used, the plug-in file will need to be manually propagated to the correct location on your web server.

If the configuration is set up correctly, an IBM HTTP Server that is remote can propagate the plugin-cfg.xml file via the web server navigation task and the propagation button from the Admin 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.

This screenshot shows a plugin-cfg.xml file that has been updated to include the Infor Lawson servlets.

Lawson servlets

Demo: Generating and propagating plug-ins Your instructor will demonstrate how to generate and propagate plug-in for new ear files delivered.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.2: Generating the web server plug-in The web server plug-in enables the communication between a Web Server and the WebSphere® Application Server. The plug-in file needs to be updated with information about the Lawson servlets in WebSphere® upon deployment. This is done by generating the web server plug-in and propagating. In this exercise, you will generate the web server plug-in. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > WebSphere Integrated Solutions Console to launch the WAS

Console.

2. Click Servers > Web Servers.

3. Select Web Server. 4. Click Generate Plug-in. Notice the path to where the plug-in is generated.

5. Select the Web Server. 6. Click Propagate Plug-in. This step is manual if using IIS or remote.

7. Select the Web Server.

8. Stop and start the web server.

Demo: Verification of installation Your instructor will demonstrate how to validate if the update of .ear and plug-ins has been successful.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 9.3: Verifying the installation After updates have been installed and applications have been deployed, it is important to verify the system is functioning properly. In LSF10 LAWDIR\system will contain an environmentSmokeTests.html. These smoke tests will help verify that the applications were deployed successfully and the system is ready for use. In this exercise, you will verify the installation. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access the LSFSmokeTests.html in LAWDIR\system.

2. Double-click the LSFSmokeTests.html file.

3. Execute LSF SSO Configuration and LSF Profile to verify IOS is working properly.


@ 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 and log files Port conflicts

One area that can commonly cause issues within WebSphere® is port conflicts. WebSphere® itself consumes roughly 30 unique ports. When you add an application server you choose whether to allow WebSphere® to generate your unique ports or not. Port conflicts will show up in the start scripts when starting the application server and it will indicate the port with an issue. Here are some general guidelines and tips in determining or resolving port conflicts:

• Port values must be higher than 1024. • Port conflict errors will display when saving to master configuration or when running the IVT tool

(installation verification tool). • Ports in use by WebSphere® processes can be found in three locations:

• profile_home/properties/portdef.props • Deployment Manager ports: In Admin Console – System Administration>Deployment

Manager under Additional Properties select Ports. • Application Server ports: In Admin Console – Servers>Application Servers>select your

application server by clicking the link and then under Communications select Ports.

Know the ports your OS is using by reviewing:

• All WebSphere® consumed ports can be found in dmgr_profile_home>/config/cells/<cell>/nodes/<node>/ serverindex.xml as well as within the Administrative Console under each component.

• Use the netstat –na |grep PORT# command to see if a port is listening.

Web or servlet error messages If you find after applying a patch update that you are having issues, first narrow it down to which of the smoke tests failed. If, for instance, it was the IOS smoke test that failed, here are the following steps one should take to troubleshoot the issue:

• Check the web server error log for errors such as a file not found error:

Example: Wed Mar 28 19:52:31 2007] [error] [client 127.0.0.1] File does not exist: file_location

• Check log files. • Check the integrity of the system; are they all running?

• Web server • Application server • Application

Can the error be duplicated in LID? If yes then this is an application problem or an issue within the environment.

If no, then focus on the web layer.

In the next few hands-on exercises you will look at the log files involved with your web server, the application server, and Lawson.

For general errors that users report such as:

Web container errors - typically HTTP404, HTTP500 or incorrect info on web page

Check the following:

• What is the error – what is the URL they were trying to access? • Check log files – access.log and error.log as well as SystemOut log • Access.log sample:


@ 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.

127.0.0.1 - - [28/Mar/2007:19:52:31 -0400] "GET url HTTP/1.1" 404 304

127.0.0.1 - - [28/Mar/2007:20:03:48 -0400] "GET urlHTTP/1.1"500 5348

The URL the web server was trying to contact when the error occurred is displayed. If the web server expected to serve the URL (versus passing the request to an application server), then there should be a corresponding error in the error.log that indicates where it expected to find the file.

• Error.log sample for errors such as a file not found error: • [Wed Mar 28 19:52:31 2007] [error] [client 127.0.0.1] File does not exist: file_location

If an HTTP404 is received there are many possible underlying causes.

• Check log files • Check the integrity of the system; are they all running?

• Web server • Application server • Application

Demo: Locating IBM WebSphere® log files Your instructor will demonstrate how to access IBM WebSphere® SystemOut and SystemErr 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 9.4: Viewing IBM WebSphere® log files In this exercise, you will view WebSphere® log files. The IBM WebSphere® SystemOut and SystemErr log files are located in the $WAS_HOME/profiles/profile_name/logs under the application server directory. The most helpful logs are the JVM log files, which are the SystemErr.log and the SystemOut.log.

Sample errors in SystemOut.log:

SRVE0255E: A WebGroup/Virtual Host to handle url has not been defined. (V6.1)

SRVE0017W: A WebGroup/Virtual Host to handle url has not been defined. (V6.0) NOTE: If this error occurs (vers 6.0 or 6.1) then you may have a problem with your virtual host configuration.

Exercise steps 1. Access Windows Explorer or LID.



3. Navigate to %WAS_HOME%\profiles\localhostNode01\logs\server1.

4. Open the SystemOut.log with the viewer of your choice ( i.e. vi, lashow, or Notepad).

To view log files from within the WAS Administrative Console:

1. Access IE > Favorites > WebSphere Integrated Solutions Console to launch the WAS Console.

2. Click Troubleshooting in the navigation pane.

3. Click Logs and Trace.

4. Click the <application server> that you want to view the JVM logs for.

5. Click JVM logs.

6. Click the Runtime tab.

7. Click View button for each of the log files to see what is written to the log files.

8. Click OK at the bottom of the screen to close out of the viewer.

Reviewing logs If there are issues or errors system administrators should review all logs including:

• Web server access and error logs • LAWDIR\system logs


@ 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) What file controls the redirection of calls from web server to WebSphere?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) The .ear files for Lawson Core Technology are delivered into what location?

______________________________________________________________________ ______________________________________________________________________

3) What .ear file contains the servlets that support Infor Lawson for Ming.le™ application calls?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) Where would a system administrator look if after updating Enterprise Applications there are errors in processing? (List all possible 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.

Lesson 10: Authentication and federation Estimated time 3 hours


• List the components of the Distributed Security Package (DSP). • Identify where the Infor Security Services is installed. • Describe the Infor Security Services purpose and features. • Explain how to navigate within the Infor Security Services administrative tool. • Describe federation and value for multiple systems on administration, authentication, and

authorization. • Define synchronization and potential conflicts. • Explain differences between authentication protocol, federation, and Primary Authentication

Service. • Describe LS as STS and Kerberos as authentication protocol. • Explain federation procedures. • Explain how to access the Security_Provisioning log and use it for troubleshooting

synchronization. • Describe the Primary Authentication Service designation. • Describe how to use ISS to control Primary Authentication Service.

Topics • Distributed Security Package overview • Infor Security Services overview • Federation overview • Check your understanding • Authentication vs. federation overview • Authentication protocol • SSO services, agents, and identities • Single sign-on • Federation • Check your understanding

130 Lesson 10: Authentication and federation © 2013 Infor Education

@ 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 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.

Distributed Security Package overview

Infor Lawson Distributed Security Package Installation Guide

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 Infor Landmark Technology Runtime are installed and federated.

The Distributed Security Package (DSP) is available both as a LifeCycle Manager Installation package and as a Java installer package.

Distributed Security Packaging and deployment

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.


@ 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 Services requires the installation of scwebadminapp.war and scwebamonitorapp.war within the IBM WebSphere Application Server to support the web administrative tool. User monitoring is covered in Lesson 11: User administration and security monitoring.

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 Services overview


Infor Security Services (ISS) 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 Services administrative 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 LSF10. 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: Accessing Infor Security Services (ISS) Your instructor will demonstrate how to access Infor Security Services (ISS).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 10.1: Accessing Infor Security Services (ISS) In this exercise, you will access the ISS tool and explore the available areas. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > Infor > Infor Security Services.

2. Type lawson in the User field.

3. Type Tr@in123 in the Password field and press Enter. 4. Explore the Resources, Configuration, SSO, and Federation menus.

ISS 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-federation 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.

LS Admin LS Runtime Rich Client security admin menus

Infor Lawson System Foundation (ILSF)

Infor Landmark Technology (ILT)

Infor Lawson applications

Infor Landmark applications

User Actor

Lawson LDAP Landmark GEN


@ 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 example

After the federation procedure is performed using ISS, users/actors can log into 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 Services (ISS) to add or update users. This will prevent you from having to run the federation procedure multiple times.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

ILSF ILT

*ISS User actor

Browser

Desktop machine * Infor Security Services

Basic data record for user / actor maintained on ILSF


@ 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 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. • 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 Ming.le™ 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 ISS to execute.

Synchronization overview Federated systems (LSF and Infor Landmark) have been synchronized initially. However, if ISS 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


@ 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: Federation and synchronization Your instructor will demonstrate federation and synchronization.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 10.2: Exploring the federated systems and synchronization In this exercise, you will access the ISS tool and explore the federated systems and examine the synchronization areas. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > ISS > 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 ISS 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 resynchronize 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.

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.


@ 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.

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.

Do not include spaces in role names; use an underscore as a separator 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.

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.

• 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.


@ 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 example

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

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.


1) Infor Security Services is delivered in what manner for installation and updating? What server does the ISS component get installed on?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) Identify two major administration functions that will be performed in ISS. (Hint: there are more than two.)

______________________________________________________________________ ______________________________________________________________________

3) What is the major benefit of having systems federated?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.

Authentication vs. federation overview The following table includes some of the differences between federation and authentication service.

Authentication protocol • LS as STS (uses SSOP or SSOPV2 password for authentication,

supports ldapbind to CORP LDAP) • Kerberos (Windows authentication using Active Directory

authentication) Federation • Configuration when multiple Infor Lawson systems sync user

repository information • Federated configuration requires Infor Security Services (ISS)

Primary authentication service

• When two systems are federated, one system is “Primary” for user authentication

• The “Primary Authentication Service” is the system that authenticates users for access to both systems (SSOP 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.

Authentication protocol

Infor Lawson 10 Authentication Configuration Guide

Authentication protocols LSF10 provides authentication protocol choices for Infor Lawson for Ming.le™. Infor Lawson for Ming.le™ requires Microsoft SharePoint and therefore one of the following protocols:

• Lawson Security as Security Token Service (LS as STS) • Kerberos

Deciding if LS as STS or Kerberos is the best authentication protocol for an organization will depend on several factors:

• If a customer is on a prior release of LSF and using ldapbind to tie the LSF LDAP to the corporate LDAP then LS as STS is likely the best decision based on experience.

• If a customer uses Kerberos already for other applications within the organization then Kerberos

is likely the best choice.

Features Kerberos STS

Global standards Yes Infor Lawson standard

Single sign-on with Infor products Yes Only with Lawson S3 suite

Requires Microsoft knowledge Yes No

Active Directory bound Yes Optional

Remote access to Infor Lawson products No Yes

Mobile applications accessible No Yes

Seamless SSO Yes Only for Lawson products

Login prompt No Yes

Shared computers/kiosks available No Yes

Session timeout No Yes

If an organization will use Infor Ming.le™ Enterprise then Kerberos is required. You cannot use LS as STS with the Infor Ming.le™ 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.

Authentication services LSF10 requires a federated system of Infor Lawson System Foundation and Infor Landmark Technology Runtime.

One of the systems must become the Primary Authentication Service. Deciding if LSF or Infor Landmark Technology Runtime should be the Primary Authentication Service will depend on several factors.

• Select the mission critical system as it would closely support 24/7 accessibility. • Select the busiest system with the most end users. Depending on the applications used by an

organization this could be LSF or Infor Landmark Technology Runtime and may change based on application deployment.

The Primary Authentication Service (PAS) is not fixed and can be changed if required based on new organizational needs. Primary Authentication is set in the Infor Security Services (ISS) application. Before editing PAS contact Infor Global Support or Infor Consulting Services to understand the impact to your server.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Lawson Security as Security Token Service (LS as STS) authentication In this method, Lawson Security authenticates users. The system is federated (both Infor Lawson System Foundation and Infor Landmark Technology Runtime are used), one system provides the authentication service for both 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.

LS as STS authentication

Browser-based sign-on: LS as STS

Infor Ming.le™ Foundation Infor Ming.le™

Foundation

LS as STS LS as STS

1. Initial request

2. Redirect to STS 3. Sign-in

6. Continue to application

5. Send claims 4. Create session

DSP

LMRK

LSF (primary)

Requestor / user (via browser)

SharePoint / Infor Lawson for Ming.le™

1. Request for access to application, data, etc.

Federated system; LSF is primary in this example

2. Request redirected to LSF for authentication. 3. Successful authentication;

user can access content.


@ 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 for LS as STS

• LSF and Infor Landmark Technology Runtime must be using the same “assertion protocol,” HTTP or HTTPS.

• Distributed Security Package (DSP) which contains security and distributed single sign-on

(DSSO) must be configured within both systems.

SharePoint user Access needs

User who runs application pools (for example, LocalSystem, spfarm)

The Microsoft SharePoint application pools user must also be a user on the Infor Lawson primary authentication system.

spinstall Default Microsoft SharePoint user for performing the Microsoft SharePoint installation. The user must have an identity on the primary service of the Infor Lawson system.

spservices Default Microsoft SharePoint user for running Microsoft SharePoint services. This user performs initial setup and smoke testing for applications running on the Infor Ming.le™ server. The user must have an OS identity on the Infor Lawson system.

lawson The domain lawson user is used to install and smoke test most Infor Lawson products. The user needs to exist on the operating system, in the domain, and in Microsoft SharePoint.

SQL Server service account

This domain account is automatically assigned the appropriate permissions as part of the SQL server installation.


@ 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.

Kerberos authentication Kerberos is an industry-standard authentication protocol that is used by Active Directory / Microsoft Windows. It is a supported authentication option for Infor Lawson 10. In this method, Active Directory authenticates users. Users must exist in both Lawson and in Infor Active Directory.

Kerberos authentication protocol

DSP

LMRK LSF (primary)

Requestor / user (via browser)

SharePoint / Infor Ming.le™

Kerberos

Active Directory (AD) (domain controller)

1. Request for access to application, data, etc.

2. Request redirected to AD for authentication.

3. Successful authentication; user can access content.

Federated system; LSF is primary in this example.


@ 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.

Kerberos browser-based sign-on

Configuration for Kerberos

• LSF and Infor Landmark Technology Runtime must be using the same “assertion protocol,” HTTP or HTTPS.

• Distributed Security Package (DSP) which contains security and distributed single sign-on

(DSSO) must be configured within both systems. SharePoint user Access needs

spinstall Default Microsoft SharePoint user for performing the Microsoft SharePoint installation. The user must have an identity on the primary service of the Infor Lawson system.

spservices Default Microsoft SharePoint user for running Microsoft SharePoint services. This user performs initial setup and smoke testing for applications running on the Infor Ming.le™ server. The user must have an OS identity on the Infor Lawson system.

lawson The domain lawson user is used to install and smoke test most Infor Lawson products. The user needs to exist on the operating system, in the domain, and in Microsoft SharePoint.

wasServer The Active Directory ID for the user who runs IBM WebSphere Application Server. Infor recommends that you use wasServer, where Server is the name of the machine where your IBM WebSphere Application Server instance is installed. wasServer Example: If your IBM WebSphere instance is installed on a machine named LSF10, this user is wasLSF10. Note: This name cannot be the same as the IBM WebSphere Administrator ID. This user must also be set up in LSF as a privileged user.

wasadmin This is the Active Directory ID for the IBM WebSphere console administrator. When using Kerberos authentication, your IBM WebSphere administration console will always be secured and you will need the wasadmin user name and password to sign in.

SQL Server service account

This domain account is automatically assigned the appropriate permissions as part of the SQL Server installation.

LS LS

Infor Ming.le™ Infor Ming.le™ 1. Initial request

3. Sign-on

2. Get Kerberos Token

6. Create session

5. Redirect to Lawson application

4. Get Security Token


@ 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.

SSO services, agents, and identities

Infor Lawson System Foundation Architecture Guide Security

Lawson Security important concepts:

Term Definition

Service An Infor Lawson system that participates in single sign-on. A set of attributes that defines how a user is identified in the sign-on engine for Infor Lawson components. LSF Resource: SSOP: User/password Landmark Actor: SSOPV2: User/password LSF ENV: OS Login/password

Identity An identity is a user entity on a particular Infor Lawson service. User’s electronic passport to the service or agent. All users who need access to an Infor Lawson component defined by a particular service or agent must have an identity on the service.

Agent A type of identity that does not require credentials. A special kind of service used only with Infor Lawson self-service applications. LSF PROD_EMPLOYEE: Company/Employee

Examples

SSOP (LSF) or SSOPV2 (Infor Landmark) Service

• Resource/Actor Identity: • User: jsmith • Password: summer2013 (ldapbind can eliminate password requirement)

PROD_EMPLOYEE Service

• Resource Agent • Company: 1234 • Employee: 9876

At a minimum, all Infor Lawson System Foundation installations must have the following services:

• OS / Environment service

Users who need command line access or who run batch jobs must have identities on this service.

• SSOP service and SSOPV2

All Infor Lawson users must have a unique identity on these services. Either SSOP or SSOPV2 is selected as the Primary Authentication Service.

For customers who are federated, use ISS to administer users assigning SSOP identity for LSF and SSOPV2 identity for Infor Landmark Technology Runtime. If ldapbind is executed for LSF SSOP then ldapbind is required for Infor Landmark SSOPv2 to allow for Primary Authentication Service switching.


@ 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.

Single sign-on Single sign-on is a Lawson Security feature that lets a user log in one time to the Infor Lawson system and authenticates them as a valid user as they move through the system.

While single sign-on is for the most part behind-the-scenes processing, initial set up for each user is required. Part of the user set up involves creating identities for the user on the services and agents the user needs.

Single sign-on provides the Infor Lawson system the ability to perform session timeout. When a session is inactive (no user interaction) for a programmed number of minutes, the session terminates.

Single Sign-on Service (SSO) Single Sign-on Service (SSO) is a servlet-driven system that resides in the servlet container layer of the Environment.

Information about a user’s session is stored in a session ID, an object with a unique identifier that is created when a new session is launched.

Distributed Single Sign-on (DSSO) Distributed Single Sign-on (DSSO) performs authentication for DSSO-enabled Infor Lawson applications against a single, central repository of users in cases where the Infor Lawson Environment and Enterprise applications run within a different server than the application that needs to access them. DSSO makes it easier to administer user accounts, with the added advantage of guaranteeing that Infor Lawson application passwords are always in sync. DSSO links to the primary SSO service, residing on the server with the Infor Lawson Environment, which then authenticates to the LDAP repository where user data is stored.

DSSO is only required on application servers that do not run the Infor Lawson Environment. For example, if you run Infor Lawson Business Intelligence (LBI) under the same IBM WebSphere application server instance as the Lawson Environment and applications, you do not install DSSO. Instead, in the LBI configuration, you specify SSOP as the service name. The Distributed Security Package used to install the DSSO delivered for the product in LSF10 will automatically configure Bouncy Castle encryption settings.

DSSO can be used with these Infor Lawson applications:

• Infor Ming.le™ (on Microsoft Windows) or Infor Smart Office (on Microsoft Windows) • Infor Lawson Business Intelligence suite (on Microsoft Windows) • Mobile Supply Chain Management applications (on Microsoft Windows or UNIX) • Infor Lawson Budgeting and Planning (on Microsoft Windows) • ION Enterprise Search (on Microsoft Windows) • Infor Workforce Management

In each of these cases, the Infor Lawson Environment may be on a different platform than the DSSO-enabled 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.

Federation


Federation is the act of tying multiple systems together for single source of authentication and administration. It takes advantage of the DSP and DSSO for authentication. It uses ISS for the administration. ISS is installed only on the LSF server and used to control the Primary Authentication Service.

In prior releases a federated (coupled) Infor Landmark Technology Runtime and LSF was SSOPV2 only for Primary Authentication Service. LSF10 allows the PAS of SSOP or SSOPV2 and this can be switched based on the customer requirement.

Federation requirements Federation requires the following:

• Authentication protocols for LSF and Infor Landmark Technology Runtime must be the same (LS as STS or Kerberos).

• If LS as STS and ldapbind to CORP LDAP has been executed for either SSOPV2 or SSOP then both must have the ldabind done against the service. This allows for the ability to switch Primary Authentication Service seamlessly.

• LDAP schema for LSF must be updated per the DSP requirements and all required patches for the DSP release are applied.

Federating procedures overview The federation of Infor Landmark Technology Runtime 10 and Infor Lawson System Foundation 10 is supported through the following process.

Federation is executed through ISS administration console/tool.

There are three basic steps:

1. Federate a new system (LSF the local system or “TO” and Infor Landmark Technology Runtime the remote system or “FROM”).

2. Perform synchronization.

3. Configure the primary authentication service.

Federate a system

This step is performed to ensure that ISS is aware of the remote system before executing the synchronization between two systems. This procedure is only performed one time and done by the installer.

1. From the main security administration dashboard > Federation > Register System. Or Federation > Federated Systems and then click the Federate New System icon (top-left of screen).

2. At the prompt for system type, select LANDMARK.

3. At the next screen, populate the following fields:

• Server name: The fully qualified name of the Landmark server. • Lase port: The security server port 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.

• Lase SSL port: The SSL port for Landmark (LASYSDIR\lsservice.properties file on Landmark server contains this information.)

4. Click Federate.

When the federation process completes a list will display showing all federated systems. A prompt appears to remind you that you should have performed a backup of your system before beginning this process. You can cancel the federation or click again to continue.

Synchronization of system information

This part of the process ensures that both systems in the federation have the same data. You can perform this process as often as necessary to ensure the systems are in sync.

You will perform this process in Lesson 11: User administration and security monitoring, including the removal of LAWDIR\system security_provisioning.log where synchronization errors are identified.

1. From the Federation Systems list start the synchronization, double-click the dual arrows icon located to the left of the name of the system to synchronize.

The synchronization / conflict resolution process begins.

2. For roles: If no conflicts exist, Sync continues. If a list of conflicts appears, perform the appropriate step:

• If you want the default behavior (ignore the conflict) to be applied to all conflicts, click the Ignore icon. Continue with step 3.

Or

• If you want to handle each role conflict individually, click the appropriate icon for reviewing the conflicts. If you select the rename option, you are prompted to type a new name. When you are finished working with this set of conflicts continue with the step 3.

3. For actors: If no conflicts exist, Sync continues. If a list of conflicts appears, perform the appropriate step:

• If you want a default behavior to be applied to all conflicts, click the Change All icon and then select Update Local or Update Remote. With this choice you are saying that when a conflict exists, the selected machine (Local or Remote) contains the correct information. Match differences on other systems to this system's information. Continue with step 4.

Or

• If you want to handle each conflict individually, select the conflict and then click the Update Local or Update Remote icon. When you are finished working with this set of conflicts, continue with Step 4.

4. For services: If no conflicts exist, Sync continues. If a list of conflicts appears, perform the appropriate step:

• If you want the default behavior (ignore conflict) to be applied to all services with conflicts, click the Ignore icon. Continue with step 5.

Or

• If you want to handle each conflict individually, select the conflict and then click the Update Local or Update Remote icon. Continue with step 5.

5. For domains: If no conflicts exist, Sync continues. Or if a list of conflicts appears, click the Ignore icon and then click Perform Sync.

6. For endpoints: If no conflicts exist, Sync continues.


@ 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.

7. For endpoint groups: If no conflicts exist, Sync continues.

8. For identities: If no conflicts exist, Sync continues. If a list of conflicts appears, perform the appropriate step:

a. If you want a default behavior to be applied to all conflicts, click the Change All icon and then select Update Local or Update Remote. With this choice you are saying that when a conflict exists, the selected machine (Local or Remote) contains the correct information. Match differences on other systems to this system's information.

Or

If you want to handle each conflict individually, select the conflict and then click the Update Local or Update Remote icon. When you are finished working with this set of conflicts, continue with step b.

b. Click OK.

The synchronization wizard ends.

Manage the primary authenticating service

This process establishes the Primary Authenticating Service.

1. From the Federation page, select Set Primary Authenticating Service link.

2. On the next screen, establish the PAS by setting:

• Domain: Select the appropriate domain from the list. • Default service: Select SSOP if you want LSF to be the PAS.

Or

• Select SSOPV2 if you want Infor Landmark Technology Runtime to be the PAS.

3. Click Finish. Upon selecting finish the Synchronization process must be executed to complete the PAS switch.

4. Follow the Synchronization option on the lower section of the PAS settings form.

Restart federated systems

Restart all federated systems, Infor Landmark Technology Runtime and LSF, in order for changes to take effect.

Troubleshooting Most issues experienced are from data conflicts. When resolved, federation issues are eliminated.

If unable to access applications such as Rich Client or Infor Ming.le™ then validate you are entering the correct password. If SSOP is now the PAS then the password for the SSOP service should now be used. If ldapbind was done for LS as STS then your CORP password should be in effect.

Viewing and resubmitting failed federation tasks

Tasks created during a federation procedure are saved and you can view them online. Use this feature to view details about tasks that failed during federation or synchronization.

Some tasks that you attempt to perform using Infor Security Services, including tasks related to federating and adding users, you can retry if they fail initially. Failed tasks are maintained on the system and you can resubmit as 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.

For example, suppose your Infor Landmark Technology Runtime and Infor Lawson System Foundation systems are federated.

When you add a new user to one system, for example, Infor Landmark Technology Runtime, Infor Lawson System Foundation (LSF) should automatically add the same user. However, if there was a problem on the Infor Lawson System Foundation server so that the user was not added, you can either:

• Correct the problem on the LSF server that caused the auto-add of the user to fail. • Rerun the "add user to LSF" task manually.

You will perform the process of working with Configuration > Tasks in ISS in Lesson 11: User administration and security monitoring. Resubmitting and updating a failed task is not currently available.

Summary of how to view failed tasks and retry from ISS:

1. From the ISS dashboard, select Configuration > Manage Tasks. A list of failed tasks displays. You can think of this list as an online log file.

2. Locate the task you want to retry and then click it. A page of details about the specific tasks displays with the following tabs:

• Target system: Displays general information about the system running the task. • Transaction details: Displays information about the task, including type of task, user who

attempted to perform it and so on. • Transmission details: Date and time create details about the failed task. • Retry details: If a retry attempt is made, this tab contains general information about the retry

task.

3. Rerun the task by clicking the Retry button from any tab.

4. If you have more failed tasks to view and rerun, you can click the return arrow for the details tab to return to the list of failed tasks.

Federation process creates a lock (ssoconfig utility)

When a federation or synchronization process is started from Infor Security Services, it is put into a locked status that prevents another of these processes from being started. Best practice is to let a federation complete normally, without (manually) releasing a lock or making changes to any of the federated systems during the federation process.

If the federation lock is released then upon synchronization the process will start at the beginning. It is recommended that you open a support case for the reason behind the failure before unlocking with permission of support. The need for manually unlocking an in-progress federation is unusual and might only be necessary in the case of a disaster recovery situation.

To unlock an in-progress federation

1. From the command line, run the ssoconfig utility, ssoconfig -c.

2. Upon prompt, type the ssoconfig security password.

3. From the menu that appears type "12" for Manage Locked Processes. The locked processes display on your screen.

4. Select the number of the process that you want to unlock.

The process number and other information for the federation you want to stop appear.


@ 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.

Enabling Security_Provisioning log in LAWDIR\system

When enabled the security_provisioning log in LAWDIR\system will capture any errors that might occur during the federation process. This logging is disabled by default but you should enable during the initial federation and synchronization. The Infor Security Services Configuration Guide contains the detailed steps to enable the security_provisioning log.

Remove the security_provisioning log before any synchronization is executed to reflect only the errors from the current process.

View the synchronization log in LAWDIR\system. If an error occurs at any phase during the synchronization process, a window displays the record that failed. The administrator running the synchronization process must click “Stop” to fix the problem. Details about the error are written to the security_provisioning.log file. After fixing the problem, the administrator can restart the synchronization process at the phase where the error occurred.

Demo: Viewing the enablement of federation logging Your instructor will demonstrate how to access the SecurityLoggerConfiguration.xml file in LAWDIR\system and view the parameters added to enable generating the security_provisioning log.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Performance improvements for synchronization

Administrators can fine-tune fetch size to attempt to improve performance when running synchronization processes. For example, if the synchronization processes are running more slowly than desired. By default, this number is 500.

Suppose that you have the following settings on your system:

• Infor Landmark Technology Runtime is the primary system in the federation. • You have 2,000 users on your system. • Page size is currently set to 1,000.

Changing page size to 500 on the Infor Landmark system should make the synchronization process run more quickly because it will process in four smaller batches instead of two large batches.

This change requires a system restart to take effect. You must execute the update before synchronization.

1. Open the configuration file LAWDIR\system\lsservice.properties in a text editor.

2. Add the following property to the file:

server.pagesize = <value>

where <value> is the page size you want

Example: server.pagesize = 800 3. Save and close lsservice.properties when you are finished making the update.

4. Perform a system restart to make this change take effect.


@ 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) Describe the significant difference between LS as STS and Kerberos authentication protocols.

______________________________________________________________________ ______________________________________________________________________

2) Define the Primary Authentication Service.

______________________________________________________________________ ______________________________________________________________________

3) Where would you look to resolve issues in the synchronization part of federation? (Hint: two locations can help identify errors.)

______________________________________________________________________ ______________________________________________________________________

4) Define why Infor Lawson System Foundation is known as the “To/Local” system and Landmark Technology Runtime is the “From/Remote” in a federation.

______________________________________________________________________ ______________________________________________________________________

5) Describe what DSSO is and the benefits to the overall architecture by leveraging 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.

Lesson 11: User administration and security monitoring Estimated time 3 hours


• Describe the ways of provisioning a user in an LSF10 federated system. • Explain how to define users for LSF and Infor Landmark Technology Runtime using the ISS

Administrator tool. • Explain how to use the ISS Administrator tool to update user information. • Describe how to execute ISS synchronization to resolve potential user data inconsistencies. • Describe the benefits of user monitoring. • List the required setup for user monitoring. • Explain how to use the ISS administrative tool to view user monitoring, history, and usage.

Topics • User administration • User security monitoring • 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.

User administration


Upon federation of systems the user administration will switch from the Lawson Security Administrator for LSF and Rich Client Actor Management in Infor Landmark Technology Runtime to the Infor Security Services (ISS) Administrator tool. The ISS tool will be used to manage user setup and ensure synchronization between LSF resources in Lawson LDAP and Landmark actors in Landmark GEN actor tables.

The following table includes current user administration tools and utilities that this lesson will cover a summary of impacts of use in a federated systems setup.

User administration options

The following table describes the federation impact when the following tools are used for user administration.

Administration tool or utility Federation impact

Infor Security Services Main point of user administration and provisioning in LSF10 upon federation with another system. The synchronization process ensures the systems contain the same data and resolves conflicts.

Lawson Security Administrator (LSA) or Resource Administrator

LSA can be used to view user information only. User/resource information should not be updated or established in this tool. If LSA is used to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data.

loadusers (load utility for LSF)

The loadusers utility can be used for updating or loading user/resource information; however, if the loadusers utility is used to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data. No actor records are created or updated to match LSF resources via the loadusers utility thus requiring ISS sync.

ssoconfig (menu for LSF)

The ssoconfig menu should not be used to update or establish user/resource information with this utility. If ssoconfig is used to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data. No actor records are created or updated to match LSF resources via the ssoconfig utility thus requiring ISS sync.

RM Update node (IPA Designer)

The RM Update node within the IPA Designer can be used for updating or loading user/resource; however, if the RM Update node is used to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data. No actor records are created or updated to match LSF resources via the RM Update node thus requiring ISS

162 Lesson 11: User administration and security monitoring © 2013 Infor Education

@ 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.

Administration tool or utility Federation impact sync.

Actor Management (via Rich Client) Actor Management can be used to view user information only. User/actor information should not be updated or established in this tool. If Actor Management is used to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data. No resource records are created or updated to match Landmark actors via the Actor Management tool thus requiring ISS sync.

secadmn (menu or load utility for Landmark)

The secadmn menu can be used to view user information only. User/actor information should not be updated or established in this utility via menu. The secadm utility can be used for updating or loading user/actor. If secadm is used to update information, synchronization through ISS will be required to ensure Federated systems continue to have synchronized data. No resource records are created or updated to match Landmark actors via the secadm utility thus requiring ISS sync.

Landmark node (Actor Business Class, Infor Process Designer, or Microsoft Spreadsheet Designer)

The Landmark node within the IPA Designer can be used for updating or loading user/actor information; however, if the Landmark node is used with Actor Business Class to update information, synchronization through ISS will be required to ensure federated systems continue to have synchronized data. No resource records are created or updated to match Landmark actors via the Landmark node thus requiring ISS sync.

Infor Security Services is the recommended way of administering users as it will maintain the data integrity of the LSF Lawson LDAP resources and Landmark GEN actors.

ISS user provisioning procedures summary 1. Enter “Basic Information”, which represents a super-set of information that links all user data in

a federated system. (Security roles are entered at this level for the LSF and Infor Landmark Technology Runtime systems.)

2. Enter Infor Landmark specific attributes, which represent the fields directly tied to an actor affecting the Infor Landmark system and processing for the user.

3. Enter LSF specific attributes, which represent the fields directly tied to a resource affecting the LSF system and processing for the user.

4. Enter identities, which represent the user credentials and agents for Infor Landmark Technology Runtime and LSF for the 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.

Demo: Provisioning 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 11.1: Provisioning a new user in the federated system In this exercise, you will access the ISS tool and establish a new user for both LSF and Infor Landmark Technology Runtime required access. In LSF10, an actor must be established in Infor Landmark Technology Runtime to establish Infor Process Automation users. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > INFOR > Infor Security Services.

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. Enter the following information:

Field Data

Actor ID vstudent1

Roles Connect (check these options): BatchRole Employee InforWorkspaceBookmarkAccess ProcessServerAllAccess_ST

Given Name Vivian

Family Name Student1

Email Address [email protected]

ISOLanguage en (en represents English)

Run As Enabled No

Disabled No


@ 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]

7. Click Next. The Landmark Server tab displays. No fields are required.

8. Click Next. The LSF screen displays.

9. Enter the following information:

Field Data

ProductLine APPS10

ISO Local en

Resource Name Vivian Student1

10. Click Add actor “Save icon”. The following message displays: User has been added successfully.

11. Select Yes in the Identity Configurations page.

12. Select the SSOP service.

13. Enter 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

14. Click Add.

15. Click OK. The following message displays: Operation completed successfully.

16. Select the LSFENV service.

Field Data

Domain User LU141TRAINING\vstudent1

Password Tr@in123

Confirm Password Tr@in123

17. Click Add.


19. Select the APPS10_EMPLOYEE service.

Field Data

Company 4321

Employee 1044

20. Click Add.


22. Use Ussplu143 (LSF) to access IE > File > New Session to access the Ming.le™ home 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.

23. Log in as vstudent1.

24. Notice the Infor Lawson Applications is not available, only the Infor Ming.le™ entry home page displays.

25. Access the Rich Client shortcut link on desktop from Ussplu143 (LSF).


Demo: Updating an existing resource Your instructor will demonstrate how to create a user through Lawson Security Administrator and synchronize using ISS to properly establish the record in the federated systems.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.2: Updating an existing resource In this exercise, you will establish a user through Lawson Security Administrator and use the ISS synchronization process to establish the record properly in the federated systems. You will use Ussplu143 (LSF) for this exercise.

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 actor “Save icon”. The Success! Update completed Successfully message displays.

11. Click OK.

12. Access IE > File > New Session > Ming.le or refresh open vstudent1 IE session from earlier step.


14. Notice the Infor Lawson Applications in Infor Lawson for Ming.le™ is now available.


@ 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.

ISS to synchronize updates You should execute all user provisioning in the ISS Administrator tool. If Lawson 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: Synchronizing federated user data Your instructor will demonstrate how to synchronize a user added through Lawson Security Administrator using ISS to establish the record properly in the federated system.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.3: Synchronizing federated user data In this exercise, you will establish a user through a method which is supported but not recommended for LSF10 (see the User administration options table). Upon completion you will use the ISS synchronization process to establish the record properly in the federated systems. You will use Ussplu143 (LSF) for this exercise.

Exercise steps Part 1: Create new user step 1 of 3

1. Click the Lawson Security Administrator desktop shortcut.




5. Select the New User wizard in the upper left Toolbar. Step 1 of 3 will display for the user you are creating.

6. Double-click the Locale attribute.

7. Type en in the Locale field.

8. Double-click the Product Line attribute.


10. Double-click the Role attribute.

11. Select the InforLawsonForWorkspaceAccess role in the Role 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.

12. Type Helen in the First Name field.

13. Type hstudent2 in the ID field.

14. Type Student2 in the Last Name field.

15. Type [email protected] in the Email field.

16. Type Helen Student 2 in the Name field.

17. Click Next.

Part 2: Manage identities step 2 of 3 1. Highlight LSFENV.

2. Double-click the Domain User field.

3. Type LU141TRAINING\hstudent2 in the Domain User field and press Tab.

4. Type <password> in the Password field and press Tab. Confirm the password.

5. Select the SSOP Service.

6. Click Yes to save changes.

7. Double-click the Password field.

8. Type Tr@in123 in the Password field and press Tab.

9. Confirm the password Tr@in123 and press Tab.

10. Type hstudent2 in the User. 11. Select the APPS10_Employee Service.


13. Type 4321 in the Company field and press Tab.


15. Select Edit from top of window.

16. Click Add.

17. Click Next.

18. Select Finish.

Note: At this time the LSF Lawson LDAP has received the new resource record but the Landmark GEN actor table did not receive the record creating out of sync in the federation user data.

Lawson environment information Step 3 of 3 1. Click the Rich Client desktop shortcut.



4. Verify GEN Data Area in upper left corner.

5. Click the User Management Process Board > Actor Management.

6. Confirm hstudent2 is not an actor. (Search for *student* Actor ID.)

7. 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.


@ 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. Access ISS > Federation > Federated Systems. (You still should use Ussplu143 (LSF).)

9. Click the Sync icon next to the Landmark federated server.

10. Select Yes on Federation Manager prompt for synchronization of data between systems.

11. Click the Ignore icon for Role conflicts. (All roles are in conflict because they already exist from the previous sync.)

12. Click the Ignore icon for Services conflicts. (All services are in conflict because they already exist from the previous sync.)

13. Click the Ignore icon for Domain conflicts. (All domains are in conflict because they already exist from the previous sync.)

14. Click the Ignore icon for Endpoint Groups conflicts. (All endpoint groups are in conflict because they already exist from the previous sync.)

15. Click OK on the Federation Manager.

16. Select Configuration >Tasks > Manage Tasks.

17. Verify no failure tasks/records exist.

18. Click the Rich Client desktop shortcut. (You are still on Ussplu143 (LSF).)




22. Access User Management Process Board > Actor Management. 23. Confirm hstudent2 is now an actor. (Search for *student* Actor ID.)

The synchronization process should be executed upon any use of user administration tools or utilities outside of the Infor Security Services (ISS) Administrator tool. The “ignore” on conflicts should be used only after analysis and verification of that desired option.

Demo: Resolving errors in synchronization for federated systems Your instructor will demonstrate how to synchronize a user added through Lawson 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 11.4: Resolving errors in synchronization for federated systems In this exercise, you will establish an error and resolve the error before the synchronization will complete. You’ll establish a user without a proper syntax of email address and during synchronization the record will fail. You will access the security_provisioning.log and Configuration > Task areas to research and resolve. Upon completion you will use the ISS synchronization process again establishing the record properly in the federated systems. You will use Ussplu143 (LSF) for this exercise.

Exercise steps Part 1: Create user step 1 of 3

1. Click the Lawson Security Administrator desktop shortcut.




5. Select the New User wizard. Step 1 of 3 will appear for the user being created.

6. Double-click the Product Line Value field.


8. Type Charles in the First Name field.

9. Type cstudent3 in the ID field.

10. Type student3 in the Last Name field.

11. Type Charles Student3 in the Name field.

12. Type cstudent3 in the Email field.

13. Click Next.

Part 2: Manage identities step 2 of 3 1. Highlight LSFENV.

2. Type LU141TRAINING\cstudent3 in the Domain User field and press Tab.

3. Type <password> in the Password field and press Tab.

4. Retype the <password> to confirm.

5. Select the SSOP service.


7. Type Tr@in123 in the Password field and press Tab.

8. Retype Tr@in123 in the Confirm Password field and press Tab.

9. Type cstudent3 in the User field.

10. Select the APPS10_Employee Service.

11. Click Yes to save changes

12. Type 4321 in the Company field and press Tab.



@ 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. Click Edit. 15. Click Add.

16. Click Next. 17. Click Finish.

Part 3: Lawson environment information step 3 of 3 1. Access Windows Explorer > C: Drive (Local Disk) > LSFENV > law > system.

2. Locate the security_provisioning.log in LAWDIR\system and delete it. You should remove this log file before the synchronization to limit the records to only this federation synchronization run.

3. Access ISS > Federation > Federated Systems. (You are still on Ussplu143 (LSF).)

4. Click the Sync icon next to the Landmark federated server.

5. Click Yes on Federation Manager prompt for synchronization of data between systems.

6. Click the Ignore icon for Role conflicts (All roles are in conflict because they already exist from the previous sync.)

During the actor synchronization a synchronization report will appear with an error for Actor=cstudent3

7. Access the security_provisioning.log and notice error in the establishment of Actor. 8. Access the ISS > Configuration > Tasks > Manage Tasks.

9. Locate the failed record.

10. Access Lawson Security Administrator > User Management > User Maintenance.

11. Type * in the Name field.

12. Click Find Now.

13. Locate the cstudent3 record.

14. Right-click cstudent3 > Edit RM Information.

15. Type [email protected] in the Email field to edit the email address.

16. Save and close or Close and save upon exiting.

ISS > Configuration > Tasks > Manage Tasks will eventually allow the administrator to access the failed task and select the Retry button to complete the synchronization of the error. At this time, administrators must restart the synchronization process. This will refresh the process and include the error record in addition to finishing the rest of the synchronization.

17. Access ISS > Federation > Federated System.

18. Select the Synchronize option for the Landmark federated system to restart the process.

19. Click the Ignore icon for Services conflicts. (All services are in conflict because they already exist from the previous sync.)

20. Click the Ignore icon for Domain conflicts. (All domains are in conflict because they already exist from the previous sync.)

21. Click the Ignore icon for Endpoint Groups conflicts. (All endpoint groups are in conflict because they already exist from the previous sync.)

22. Click OK on the Federation 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.

23. Select Configuration > Tasks > Manage Tasks.

24. Verify no failure tasks/records exist beyond the first record error on cstudent3.

25. Access the Rich Client desktop shortcut. (Still on Ussplu143 (LSF).)




29. Double-click User Management Process Board > Actor Management. 30. Confirm cstudent3 is now an actor (search for *student* Actor ID).

At this point of the lesson, ISS has been used to provision a new user and change an existing one. Using ISS keeps the resource in LSF and the actor in Landmark GEN in sync. LSA was used to provision a user and see the effect of no actor creation in Infor Landmark Technology Runtime forcing ISS synchronization to resolve. Finally a synchronization process with an example of a potential error in data resolution has been executed.


@ 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.

User security monitoring


The user monitoring feature enables customers to verify software licensing compliance by providing customers with the ability to:

• Monitor peak usage. • Keep track of high-level information about users' interaction with the system (session,

connectivity, application modules accessed). • Create summary reports. • Export data in CSV format to view and manipulate using the tool of choice.

User monitoring overview User monitoring is not enabled by default. Infor recommends that installations that want to monitor user activity create an additional security server to ensure efficient processing of security tasks. Configuring multiple servers includes determining which security tasks are performed by which servers.

You can assign servers the following roles:

Server role Description

DEFAULT This role is assigned to the security server that will handle most normal security processing, including authentication and authorization. Typically the server that is assigned this role is not assigned other security roles. As the name implies, this role is assigned to a security server automatically when the server is created.

USERMONITORING Configuring for user monitoring includes assigning the USERMONITORING role to one of the security servers. The instructions are documented in the next several pages.

FEDERATION When multiple systems are federated (for example Infor Lawson System Foundation and Infor Landmark Technology Runtime), the server that handles federation tasks is assigned the role "FEDERATION." The FEDERATION and USERMONITORING roles must be assigned to the same server.

lsservice.properties file User monitoring requires enablement in the lsservice.properties file. The lsservice.properties file is a configuration file for many security-related features, including user monitoring. A new setting is required in this file for the ssoconfig utility in order to allow configuration of user monitoring.

By default, the property is not enabled. This section describes how to add and/or enable the property to the lsservice.properties file.

1. Open LAWDIR\lsservice.properties in a text editor.

2. Establish the following properties:

• server.monitor.config.enabled=true • server.scalability.enabled=true


@ 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. Save and close the file.

4. Restart your LSF server properly (WAS & stoplaw /startlaw & WAS) for changes to take effect.

Infor recommends that you setup an additional Lawson Security Server (lase) to handle the security process efficiently with user monitoring.

Viewing (lase) security servers

Use the following steps to view the security servers currently configured on your system.

1. Run the ssoconfig utility. At a command window, type ssoconfig –c and then at the prompt type the security administrative password.

2. From the main ssoconfig menu, select "Manage Security Servers."

3. From the next menu that appears, select "List Security Servers." The security servers list displays on your screen.

4. When you are finished viewing servers, select “Back” to return a previous menu.

The training image has been configured for user monitoring. The basic steps to enable: 1. Create an additional lase security server using ssoconfig –c. 2. Configure the listening port. 3. Configure the User Monitoring Interval.

Create an additional lase security server

This procedure describes how to create an additional security server. Infor recommends that customers who use user monitoring perform this procedure.

1. From the main ssoconfig menu, select "Manage Security Servers."

2. From the next menu, select "Add a Security Server."

3. At the prompt "Enter Server Port," type the port that you want to use for this server.

4. At the prompt, "Enter server instance name," type the name for the new server you are adding.

5. At the prompt, "Enter server host," type the name of the machine that will host the server in the appropriate format for your system, for example:

MyServer.MyDomain.com

6. At the prompt, "Enter Server SSL Port," type the port that you want to use for this server.

7. At the prompt, "Enter server roles," type USERMONITORING.

8. Type the word USERMONITORING exactly as shown above.

9. When you are finished adding the server, select “Back” to return a previous menu or exit.

10. Restart the LSF server properly for changes to take effect (WAS & LSF Environment).


@ 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 user monitoring listening port

You need to know the number of the UDP listening port on your security server. You will be prompted for this port when you perform the following steps.

1. From the main ssoconfig menu, select "Manage User Monitoring."

2. In the next menu, select "Configure User Monitoring Server and Services."

3. From the Configuration menu, select "Manage Security Services."

4. From the Security Server Configuration menu, select Change properties of a Security Server with User Monitoring Role.

5. At the prompt, "Please enter the NAME of the Security Server whose user monitoring properties will be updated:" type the name of the security server instance with the USERMONITORING role and then press Enter.

6. At the prompt, "Enter the Server side listening UDP port for monitoring <33333>" type the number of the listening port. By default, this is "33333." You can keep the default or specify any unused port number (range is 1024-65535).

7. Select “Back” to return to the previous menu or exit.

8. Restart the LSF server properly for changes to take effect (WAS & LSF Environment).

Configuring the user monitoring interval

By default, user data is written to the database every fifteen minutes. You can change this interval.

1. Run the ssoconfig utility. At a command window, type ssoconfig –c and then at the prompt type the security administrative password.


3. From the Configuration menu, select "Manage Monitoring Jobs."

4. From the User Monitoring Jobs menu, select "Update User Monitoring Interval."

5. At the prompt, "Enter the interval in minutes (15)," replace "15" (or whatever value is showing) with the interval you want to use. The value must be between 5 and 60 (interval is in minutes).


7. Restart the LSF the server properly for changes to take effect (WAS & LSF Environment).

Viewing user monitoring setup

To ensure that you have correctly configured the security server, view the setup now.

You can also perform this procedure any time you want to see how you have configured user monitoring.


2. From the next menu, select "Configure User Monitoring Server and Services."

3. From the Configuration menu, click "View current configuration."

The name of the security servers, listening ports, user monitoring interval, and other user monitoring information displays.



@ 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.

User monitoring can be enabled / disabled completely or for just the client-side or server-side through the ISS tool or through the ssoconfig utility. For information on the ssoconfig procedure see the User Monitoring section of the Infor Security Services Configuration Guide.

Enabling user monitoring using the Infor Security Services administrative tool User monitoring can be configured using the ISS tool as well as through the ssoconfig utility.

1. From the security administration dashboard, select Configuration and then under the User Monitoring group, select Configure Monitoring. You will be on the User Monitoring - Configure Monitoring page.

2. Populate the following fields:

• Enable Monitoring: Check this checkbox. • LASE Instance: From the drop-down menu select the security server instance that you

want to configure. • Port: Type the number of the server port that should listen for user monitoring. By default

this is "33333." • Enable Server Services: Check this checkbox. • Enable Client Services: Check this checkbox.

3. Click Submit. You must perform a proper restart of the LSF server for this configuration to take effect (WAS & LSF Environment).

User monitoring exploration After enabled, user monitoring is accessed through Infor Security Services (ISS). You must establish a session for users to show up in the monitoring.

Demo: Establishing user sessions for review in user monitoring Your instructor will demonstrate how to establish sessions for cstudent3 and vstudent1 for review in user monitoring.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.5: Establishing user sessions for review in user monitoring In this exercise, you will establish sessions for two users of the system. This exercise is to create the information for review in user monitoring. You will use Ussplu143 (LSF).

Exercise steps 1. Access IE > File > New Session > Infor Ming.le™ home page.

2. Type hstudent2 in the User Name 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.

4. Select the Lawson Applications option.

5. Type HR11 in the Application Search field and press Enter.

6. Type 4321 in the Company field.


8. Click Inquire.

9. Access IE > File >New Session > Infor Ming.le™ home page.

10. Type vstudent1 in the User Name field.


12. Select the Lawson Applications option.

13. Type AP10 in the Application Search field and press Enter.

14. Type 4321 in the Vendor Group field.

15. Type 1 in the Vendor field.

16. Click Inquire.

*hstudent2 and vstudent1 now have active sessions for view in user monitoring.

Demo: Accessing active user sessions information in ISS Your instructor will demonstrate how to access user information using ISS and user monitoring. You instructor will demonstrate how to view active user sessions, session history, peak usage history, and how to export user monitoring data to ISS.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 11.6: Accessing active user sessions in ISS In this exercise, you will access ISS and user monitoring. You will explore the information available for active user sessions. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > INFOR > ISS > Monitoring > Active Sessions.

2. Select the session for hstudent2 and view the following:

• Session ID number: Unique number assigned to a session.


@ 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.

• IP address: Of the computer that is running the session. • Client Type: Typically, this is the application running in the session. • Start Time: The time the session began. • Last Update: Most recent transaction performed by the user.

3. Select the session for vstudent1 and view the following:

• Session ID number: Unique number assigned to a session. • IP address: Of the computer that is running the session. • Client Type: Typically, this is the application running in the session. • Start Time: The time the session began. • Last Update: Most recent transaction performed by the user.

Exercise 11.7: Accessing user session history in ISS In this exercise, you will access ISS and user monitoring. You will explore the information available for historical user sessions.

Exercise steps 1. Access ISS > User Monitoring > Session History.

2. Select an historical session and view the available information.

Exercise 11.8: Accessing peak usage history in ISS In this exercise, you will access ISS and the User Monitoring. You will explore the information available for historical peak usage.

Exercise steps 1. Access ISS > User Monitoring > Usage Peaks.

2. View the available information (switch between Graphical and List display).

3. In ISS > User Monitoring > Usage Peaks by Module.

4. View the available information.

Exercise 11.9: Exporting user monitoring data in ISS In this exercise, you will access ISS and user monitoring. You will export the user monitoring information into a CSV formatted file. You will use Ussplu143 (LSF).

Exercise steps 1. Access ISS > User Monitoring > Export. 2. Select Summary Session.

3. Select Today’s Date in the Date fields from and to.

4. Select Export.

5. Write down the name of the file produced ___________________________.


@ 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. Access Windows Explorer > LSFENV > law > system (LAWDIR). 7. Locate the .zip file.

8. View the contents of the concurrent session summary.csv.

Exercise 11.10: Viewing security server performance data in ISS In this exercise, you will access ISS and user monitoring. You will review the performance of the lase security server.

Exercise steps 1. Access ISS > User Monitoring > Security Server > Server Health.

2. View the performance of the servers lase and lase2.


@ 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) Name some of the utilities that you can use to add either a resource to LSF, an actor to Infor Landmark Technology Runtime, or both simultaneously.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What LSF10 administrative tool can you use for user provisioning and user maintenance after federation?

______________________________________________________________________

3) If the Infor Security Service tool is not used for user administration after federation what process is required to verify the systems remain in sync?

______________________________________________________________________

4) Name two places where you can view failed federation records information (include their locations).

______________________________________________________________________ ______________________________________________________________________

5) Can a user be assigned a security role that is valid in both LSF and Infor Landmark Technology Runtime? If yes, what are the potential effects? If no, what prevents this from happening?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) If the ssoconfig menu is not showing the user monitoring options then what needs to be fixed for these options to become available?

______________________________________________________________________ ______________________________________________________________________

7) Where can you enable or disable user monitoring?

______________________________________________________________________ ______________________________________________________________________

8) Identify some of the benefits of user monitoring. What kind of information is available with user monitoring?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 12: Infor Lawson Security Estimated time 3 hours


• List the key components of Infor Lawson Security. • Describe how to build a role-based security policy using simple security rules of Grant and

Unconditional for action. • Describe conditional security rule capabilities.

Topics • Infor Lawson Security administration • Check your understanding

Infor Lawson Security is covered in this lesson for system administrators. For full understanding of Infor Lawson Security the 4-day administration class Lawson: Administering Infor Lawson Security should be attended.

182 Lesson 12: Infor Lawson Security © 2013 Infor Education

@ 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 Lawson Security administration Infor Lawson Security is a role-based security. Lawson System Foundation 10 requires Lawson Security.

Demo: Enabling Infor Lawson Security Your instructor will demonstrate how to enable Infor Lawson Security.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.1: Enabling Infor Lawson Security Infor Lawson Security has been disabled during the administration section of the class. In this exercise, you will enable Infor Lawson Security for the remainder of training. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access the Lawson Security Administrator desktop shortcut.



3. Click Server Management > Server.

4. Click the Security Checking tab.

5. Select Default.

6. Click the ON radio button.

7. Select Apply.

Profile A profile is a container for security classes. The objects available for security rules within a profile are determined by the data source defined. For a profile to be actively securing data for a productline or area of Lawson, it must be designated as the “Assigned Profile”. A data source cannot be actively secured by more than one profile. This is because the “Assigned Profile” is used by the Lawson Security Engine to determine where to look for the security classes assigned to the roles and determine the authorization rules.


@ 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: Establishing a profile Your instructor will demonstrate how to establish an Infor Lawson Security profile.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.2: Creating a profile In this exercise, you will create a profile. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access Lawson Security > Profile Management >Profiles.

2. Click Add.

3. Type APP in the Profile ID field.

4. Type Class Profile in the Profile Name field.

5. Type Class Profile in the Description field.

6. Select ERP in the System Type field.

7. Select APPS10 in the Data Source Definition field.

8. Select/highlight the APP profile and click Assign Profile at the top left.

9. Select the APPS10 application data source and assign to the APP profile.

Data source access A user can only perform actions within Lawson if access is granted to all required objects. Every user accessing the application needs access to the data source. This hands-on activity demonstrates pulling a consistent object requirement out into its own role. This saves on building the access into each role or security class individually. If the Environment had multiple data sources, TEST and DEV, then a data source role could be completed for each. Role assignment to users would control which could access DEV and which could access TEST or both.

Demo: Granting data source access Your instructor will demonstrate how to establish a productline security role granting access to the APPS10 data source.


@ 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: Granting data source access In this exercise, you will grant data source access. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Select the Lawson RM Administrator desktop shortcut.



3. Click Exit on the view menu.

4. Click Add > Role from the toolbar.

5. Type APPS10Role in the Role ID field.

6. Type APPS10Role in the Description field.

7. Click Edit > Add.

8. Access ISS.

9. Select vstudent1 user.

10. Click the pencil icon to edit people.

11. Double-click the Role field.

12. Scroll to and highlight the APPS10Role role.

13. Click the right arrow to assign the selected value.

14. Click Update User.

15. Access Lawson Security.

16. Double-click the APP profile created.

17. Access Security Classes > Add.

18. Type APPS10SecClass in the Security Class Name field, to create a security class to grant access to the application productline.

19. Type APPS10SecClass in the Description field. Do not base the security class on another security class.

20. Click Add.

21. Click 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.

22. Double-click the APPS10SecClass security class.

23. Click the Add Rule box.

24. Select the Securable Types box.

25. Select Data Sources > APPS10 > Grant All Access > Apply.

26. Select Return to verify rule.

27. Click Class Assignment.

28. Select your APPS10Role > Assign Security Classes.

29. Select your APPS10SecClass and click the right arrow box.

30. Click Close.

31. Select Server Management > Clear Cache.

32. Open IE.


• User Name: vstudent1 • Password: Tr@in123

34. Launch Infor Lawson for Ming.le™.

35. Select Preferences/User Options and verify that APPS10 is listed in the Data Area field.

Grant access Infor Lawson Security allows for granting access by Grant Access, Unconditional for Actions, or Conditional Access. Grant Access assigns full action access without restriction for objects receiving this type of rule.

Demo: Granting access to forms and files Your instructor will demonstrate how to establish a security role granting access to Infor Enterprise Application forms and 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 12.4: Granting access to forms In this exercise, you will grant access to a role for online objects. The user will be able to access application forms. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access Resource Administrator > Add > Role.

2. Type PurchasingClerk in the Role ID field.

3. Type PurchasingClerk in the Description field.

4. Select Edit > Add.

5. Access ISS.

6. Select the vstudent1 user.



9. Scroll to and highlight PurchasingClerk. Assign the selected value by selecting the right arrow.

10. Select Update User.

11. Access Lawson Security Administrator. 12. Double-click the APP profile.

13. Select Security Classes > Add.

14. Type BuyerMaintenance in the Security Class Name field.

15. Double-click BuyerMaintenance.

16. Select Add Rule.

17. Select Securable Types > Online.

18. Check the box next to the following objects:

• PO • PO04 • PO04.*

19. Click Grant All Access > Apply.

20. Select Securable Type > Batch.


• PO • PO204

22. Select Select Grant All Access > Apply.

23. Select Return.

24. Select Security Classes > Add.

25. Type POFileAccess in the Security Class Name field.

26. Double-click POFileAccess and select Add Rule.

27. Access Securable Types > 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.

28. Check the box next to PO.

29. Right-click Select Next Level. All PO files should now be selected.

30. Select Grant All Access > Apply.

31. Select Return.

32. Select Class Assignment > PurchasingClerk > Assign Security Classes.

33. Highlight BuyerMaintenace and POFileAccess.

34. Click the right arrow > Close.


36. Access IE.




39. Type PO04.1 in the Search field. When the program launches access has been granted to vstudent1 for the form properly.

40. Select the Procurement Group drop-down menu. If the selection results in values being returned then access had been granted to vstudent1 for the files properly.

Unconditional access Often a user is required to have inquiry rights only to an area of Lawson. If no data restriction is also required then the Unconditional Access for Actions rule type grants appropriate access. This rule type grants access to objects but with limited Lawson actions. In this example, access is granted to set up forms but only for Inquiry, Next, Previous, Page Up and Page Down where available. The user is able to access the forms and selects but without the ability to modify the forms.

Demo: Granting unconditional form access Your instructor will demonstrate how to establish a security rule granting only view access to Infor 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.

Exercise 12.5: Setting unconditional access for action forms This exercise builds upon the previous one. You will grant an Unconditional Access for Actions rule type. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access Lawson Security Administrator > Security Classes > Add.

2. Type POSetupInquiry in the Security Class name field.

3. Double-click POSetupInquiry.

4. Select Add Rule.

5. Select Securable Types > Online.


• PO • PO06

7. Select Grant All Access.

8. Click Apply.

9. Check the box next to the following object:

• PO06.1

10. Select the Unconditional Access option in the Action field.

11. Type I+- in the Unconditional Access field.

12. Click Apply.

13. Go to Class Assignment. 14. Select the PurchasingClerk role.

15. Select Assign Security Classes.

16. Highlight POSetupInquiry and select the right arrow.

17. Click Close.

18. Open IE.




21. Type PO06.1 in the Search field. When the program launches if only Inquire, Page-up and Page-down are available then access has been granted properly.


@ 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: Granting printer and job queue access Your instructor will demonstrate how to establish a security role granting access to Infor Lawson Core Technology printers and job queues created in Lesson 7.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 12.6: Securing printers and job queues Users will require access to areas of Lawson which are not application-related. In the following exercise the user will be receiving access to a printer and job queue. The printer and job queue were defined to the environment in Lesson 7 and now will be assigned to a user for accessing/use. In this exercise, you will secure printers. You will use Ussplu143 (LSF).

Exercise steps 1. Access Resource Administrator.

2. Create a role called PrinterJQAccessRole.

3. Access ISS.

4. Locate vstudent1 user.



7. Scroll to and highlight PrinterJQAccessRole.

8. Select the right arrow to assign the selected value.

9. Select Update User.

10. Access Lawson Security Administrator. 11. Select Profiles.

12. Access ENV Profile > Security Class.

13. Add a Security Class called PrinterJQAccess.

14. Select Securable Type > Printers to add a rule in the PrinterJQAcccess security class.

15. Select CLSPrinter > Grant Access.

16. Click Apply.

17. Select Securable Type > Job Queues to add a rule in the PrinterJQAccess.

18. Select FINANCE and click Grant Access.

19. Click Apply.

20. Select Class Assignment. 21. Assign the PrinterJQAccessRole role to the PrinerJQAccess security class.


@ 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.


23. Access IE.




26. Access PO204.

27. Type PO204 in the Job Name field.

28. Select LGE in the Procurement Group field.

29. Click Add to add the Job.

30. Select the Reports option.

31. Select the Destination > Printer radio button.

32. Verify the printer CLSPrinter is accessible. If the printer is accessible then the security role granted access properly.

33. Close the Reports window.

34. Select Submit.

35. Verify the job queue FINANCE is accessible. If the job queue is accessible then the security role granted access properly.

Demo: Lawson Security reporting and lsdump/lsload utilities Your instructor will demonstrate how to run Lawson Security reports and manage security through the lsdump and lsload utilities.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo: Disabling Infor Lawson Security Your instructor will demonstrate how to disable Infor Lawson Security.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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.7: Disabling Infor Lawson Security Infor Lawson Security has been enabled during this lesson and needs to be disabled. In this exercise, you will disable Infor Lawson Security for the remainder of training. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access the Lawson Security Administrator desktop shortcut.



3. Select the Server Management > Server > Security Checking tab.

4. Select Default. 5. Click the OFF radio button.

6. Select Apply.


@ 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) What is the first level of access in the hierarchy of Infor Enterprise Application?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) What must be granted before the form desired can be granted?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) If the select or drop-down/drill is not returning data, then what access is missing on the user?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) Name the six required Infor Lawson Security profiles (six are a minimum).

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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: Infor Ming.le™ and end-user interfaces Estimated time 4 hours


• Describe how Infor Ming.le™ supports the use of Infor Lawson applications. • Compare and contrast the differences between Infor Ming.le™ Foundation and Infor Ming.le™

Enterprise versions. • Explain how to administer access to Infor Ming.le™ and Infor Lawson for Ming.le™, and Infor

Smart Office. • List the requirements for Infor Ming.le™, Infor Lawson for Ming.le™, and Infor Smart Office.

Topics • Infor Ming.le™ Foundation • Infor Lawson for Ming.le™ • Infor Lawson for Ming.le™ roles • Bookmarks • Infor Lawson for Ming.le™ customizations • Infor Smart Office • Check your understanding

194 Lesson 13: Infor Ming.le™ and end-user interfaces © 2013 Infor Education

@ 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 Ming.le™ Foundation

Infor Ming.le™ Installation and Configuration Guide

Infor Ming.le™ (formerly Infor Workspace) 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.

The Infor Ming.le™ interface includes a header with menu options and icons that activate the display of Infor ERP applications in the area below the header. To the right of the application area is a collapsible panel, which hosts a series of Infor Ming.le™ contextual applications.

Infor Ming.le™ provides drill-back capability among Infor applications so that users can navigate from one application to another to track transactions, the transfer of data, and report updates. Additionally, Infor Ming.le™, along with HTML and JavaScript technologies, provides an infrastructure for sharing content among Infor ERP applications and Infor Ming.le™ contextual applications.

There are two version of Infor Ming.le™:

• Infor Ming.le™ Foundation • Infor Ming.le™ Enterprise

Infor Ming.le™ Foundation

• Default browser-based user interface for Infor Lawson applications • No charge • No Infor social collaboration • Infor ION is not required

Infor Ming.le™ Enterprise

• $ Chargeable $ • Includes all Infor Ming.le™ Foundation feature functionality • Infor social collaboration • ION is required and is $ chargeable $

Infor Ming.le™ supported browsers

Infor Ming.le™ has been tested in the following browsers:

• Microsoft Internet Explorer 8.0 (32-bit version only and Compatibility view setting off) • Microsoft Internet Explorer 9.0 (32-bit version only) • Microsoft Internet Explorer 10.0 (32-bit version only) • Mozilla Firefox 2.0 for Windows and Mac OS • Safari 6 for Mac OS (Basic testing of functionality) • Chrome 26 for Windows and Mac

Please see the Infor Lawson Compatibility matrix published in Infor Xtreme’s Knowledge Base for more details.


@ 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.

On Microsoft Internet Explorer browsers that access Infor Ming.le™, you must enable the “display of mixed content” setting.

To enable the display of mixed content on Microsoft Internet Explorer:

1. On Microsoft Internet Explorer (IE), select Tools > Internet Options.

2. Click the Security tab. Select the zone where the Infor Ming.le™ server and other Infor applications are running. Most likely this is the local intranet.

3. Click Custom level and on the Security Settings dialog box, locate the Display mixed content options under Miscellaneous.

4. Select Enable.

5. Click OK to save your settings and close the dialog box.

6. If you continue to receive security warnings about content that was not delivered securely, you may need to repeat this configuration for the Internet and Trusted sites zones.

Security requirements

There are several accounts required for Infor Ming.le™ installation and configuration.

In a Microsoft SharePoint farm installation, Microsoft recommends separate accounts for each of these tasks:

• Administrative tasks such as installation • Running the Microsoft SharePoint Farm application pools and the Infor Ming.le™ configuration

wizard • Running the Microsoft SharePoint services and Infor Ming.le™ web application in Microsoft

SharePoint • Running the Microsoft SQL Server services

These are domain accounts that you create in Active Directory. See the appropriate Microsoft documentation for creating domain accounts.

These are the required accounts and their privilege requirements. Although the names provided are only suggestions, it is strongly recommended that you use similar names to facilitate communications with Infor Xtreme Support:

Account Suggested name Purpose Requirements

Setup User Account SPInstall This account is used to do all administrative tasks including but not limited to: • Run SharePoint

installation • Run SharePoint

Products Configuration wizard

• Configure server farm and management from SharePoint Central Administration

• Run IFS Security Administration

• Domain account • This user must be

assigned an SQL Server logon with the dbcreator and securityadmin security roles

• Member of the Administrators group on the SharePoint and SQL Servers.

• As part of the SharePoint products and technologies configuration wizard, this 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.

Account Suggested name Purpose Requirements • Run social

integration tool • Log on to the server

form Remote Desktop

automatically will be made a farm administrator in SharePoint Central Administration

Server Farm Account SPFarm Used to: • Act as the

application pool identity for the SharePoint Central Administration website.

• Run Microsoft SharePoint Foundation Workflow Timer Service jobs under the context of this user.

• Run Infor Ming.le™ feature activation.

• Domain account • This user is

automatically assigned the appropriate permissions by the SharePoint Products and Technologies Configuration wizard

SharePoint Services Account

SPServices Use this account to run the Infor Ming.le™ web application.


automatically assigned the appropriate permissions when the Infor Ming.le™ web application is created in SharePoint Central Administration.

SQL Server Service Account

SQLService Use this account to run the SQL Server related services.


automatically assigned the appropriate permissions as part of the SQL Server installation.

Authentication requirement of Microsoft SharePoint for Infor Ming.le™ Foundation/Enterprise

For users to access the Infor site they must first be configured with grant rights to the site in Microsoft SharePoint. Infor Ming.le™ expects that upon sign-in, the user belongs to a pre-determined security group in the Active Directory used by the domain. For access to the Infor Ming.le™ site, all users must have their domain account associated with the “Infor” security group in the Active Directory.


@ 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.

Granting access to Infor Ming.le™ Foundation/Enterprise

A user would require base access to the Infor Ming.le™ Foundation. Infor Ming.le™ Foundation does not include application access. The Infor Ming.le™ Foundation should be granted in a manner to address the users for an organization.

Options:

• Selecting all Authenticated Users • Selecting an Active Directory group or Active Directory user (Kerberos) • Selecting an RM role or Resource/user (LS as STS)

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Demo: Exploring Infor Ming.le™ Foundation access grants Your instructor will demonstrate how to access the Infor Ming.le™ Foundation as an administrator, and view the established permissions.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.1: Exploring Infor Ming.le™ Foundation access grants In this exercise, you will access Infor Ming.le™ Foundation as an administrator and view the established permissions that grant access to the Infor Ming.le™ user base. Infor Ming.le™ is installed on Ussplu145, however, the application is accessible from Ussplu143 (LSF). You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > Infor > Ming.le.

(http://ussplu145.lu141training.lawson.com/default.aspx) Note: Infor Ming.le™ is installed on Ussplu145 server on the training image.



4. Select Site Actions > Site Permissions (upper right).


@ 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. Select the Infor Ming.le Owner (Full Control) link. Notice the lawson user has been associated with this area allowing Administrative rights to Infor Ming.le™.

6. Click Back to return to the Infor Ming.le™ Site Permissions.

7. Select Infor Application Group. Notice that All Authenticated Users has been designated. With this option, any user who can authenticate would gain access to the base Infor Ming.le™ Foundation.

8. Open a new session IE > Favorites > Infor > Ming.le. You are still using Ussplu143.

9. Type cstudent3 in the User Name field.

10. Type Tr@in123 in the Password field. Notice that cstudent3 has access to the Infor Ming.le™ Foundation home but not the Infor Lawson for Ming.le™ (Infor Lawson). A later part of Lesson 13 will show how to grant access to a plug-in application within Infor Ming.le™.

Infor Ming.le™ Enterprise requires additional configuration completed through IFS for users, administrators, controlling activity feed, tasks, and alerts. See the Infor Ming.le™ Installation and Configuration Guide for Active Directory or Active Directory Federated Services.

Demo: Verifying Infor Ming.le™ Foundation deployment and services Your instructor will demonstrate how to access the Infor Ming.le™ Server and verify the Infor services are deployed. Your instructor will use Ussplu145 (SharePoint) for this demonstration.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Infor Ming.le™ Foundation update procedures can be found in the Infor Ming.le™ Installation and Configuration Guide. These procedures are executed on the Microsoft SharePoint/Ming.le™ 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.

Infor Ming.le Administration Guide

Administration of Infor Ming.le™

Based in Microsoft SharePoint the Infor Ming.le™ Foundation is configurable and extensible. Administrators have the ability to edit application sites or create additional sites for potential non-Infor requirements. The Infor Ming.le™ experience and options can be controlled as well. These next examples are a collection of exercises to expose an administrator to the potential of Infor Ming.le™ for their organization.

Demo: Adding a new site/application to Infor Ming.le™ Foundation Your instructor will demonstrate how to access the Infor Ming.le™ Foundation and create a new site to a non-Infor application or URL callable location.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.2: Adding a new site/application to Infor Ming.le™ Foundation In this exercise, you will access Infor Ming.le™ Foundation and create a new site to a non-Infor application or URL callable location. You will use Ussplu143 (LSF).


(http://ussplu145.lu141training.lawson.com/default.aspx) Note: Infor Ming.le™ is installed on the Ussplu145 server on training image.



4. Select Site Actions > New Ming.le Site.

5. Select the Infor Ming.le Plugin Web Feature for Generic Applications.

6. Click Desktop > ClassInfo10x > Ming.le > cnn.png. The icon is now added to the system.

7. Select the icon locating the cnn.png.

8. Type CNN in the Title field.

9. Type CNN in the Sub Site Name field.

10. Type http://www.cnn.com in the Application Name URL field.

11. Select Create.

12. Select the Home icon to load Infor Ming.le™ post Site Created message.


@ 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://ussplu145.lu141training.lawson.com/default.aspx

http://www.cnn.com/

13. Select CNN as a site/application now available. CNN will load. (If subscript message error appears on first load select Do not Show and No.)

14. Select Site Actions > Site Permissions.

15. Select Grant Permissions.

16. Select Browse > All Users > All Authenticated Users.

17. Select All Authenticated users.

18. Click OK.

19. Select the Contribute option.

20. Click OK. All authenticated users will now have access to the site.

Demo: Configuring Infor Ming.le™ Foundation settings Your instructor will demonstrate how to access Infor Ming.le™ Foundation properties stored in the Microsoft SharePoint property bag to configure settings.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.3: Configuring Infor Ming.le™ Foundation settings In this exercise, you will access Infor Ming.le™ Foundation properties stored in Microsoft SharePoint property bag to configure settings. This will require Infor Ming.le™ Property Bag Configuration tool. For this scenario the edit will allow a user to log out of Infor Ming.le™ and log in as a different user. This option has been disabled as you can notice by selecting the user in Infor Ming.le™ Foundation and only have Logout as an option. You will use Ussplu145 (Microsoft SharePoint/Infor Ming.le™) for this exercise.

Exercise steps 1. Access the Start > All Programs > Infor Ming.le > Infor Ming.le Property bag Configuration

tool.

2. Type lu141training\spinstall in the Domain \ User ID field.


4. Select Site Collection:http:Ussplu145.lu141training.lawson.com > Fetch.

5. Select Infor_Workspace_RemoveSignInAsDifferentUser_MenuItem.

6. Change the current value from true to false.

7. Click Submit. This will restore the option in Infor Ming.le™.


@ 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. Return to Ussplu143 (LSF) Ming.le.

9. Refresh the browser.

10. Notice under the User option in the upper right there is now a Sign in as Different User option.

Demo: Customizing Infor Ming.le™ Foundation display Your instructor will demonstrate how to access Infor Ming.le™ Foundation site settings and how to customize the Infor Ming.le™ Foundation user interface by changing the company logo.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.4: Customizing Infor Ming.le™ Foundation display In this exercise, you will access Infor Ming.le™ site settings and execute an example of customizing the Infor Ming.le™ user interface. This scenario will simply change the icon designated for the company logo. You will use Ussplu143 (LSF).


(http://ussplu145.lu141training.lawson.com/default.aspx) Note: Infor Ming.le™ is installed on Ussplu145 server on training image.



4. Select Site Actions > Site Settings.

5. Select Customize Ming.le User Interface under Infor Ming.le™ Site.

6. Select the Upload Icon option next to the Company Logo Image icon.

7. Click Add File from Desktop > ClassInfor10x > Ming.le > CompanyLogo.png. The icon is now added to the system.

8. Select Icon next to the Company Logo Image icon.

9. Locate the CompanyLogo.png.

10. Click Save. Notice the company logo has been changed.


@ 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 Ming.le User Guide

User configurations of Infor Ming.le™

The Infor Ming.le™ Foundation home page has many productivity enhancing features. There is a built in calendar, the ability to follow other Infor Ming.le™ users, and create alerts and links for quick access to other URL callable locations. In addition, users can manage their settings of Infor Ming.le™. This next exercise is to expose user options within Infor Ming.le™.

Demo: Exploring the Infor Ming.le™ Foundation home Your instructor will demonstrate how to access Infor Ming.le™ and explore the additional user options by accessing applications through Infor Ming.le™ Foundation.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.5: Exploring the Infor Ming.le™ Foundation home In this exercise, you will access Infor Ming.le™ and explore the additional user options by accessing applications through the Infor Ming.le™ Foundation. You will use Ussplu143 (LSF).





4. Locate Whereabouts at the home page. This area allows you to follow a group of users or simply selected users.

5. Select click “here”.

6. Type cstudent3 in the User field.

7. Select from the return results.

8. Click Add.

9. Click OK. The Infor Lawson user is now following cstudent3.

10. Locate Announcements in the lower left of the 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.


11. Select Add to add a new announcement.

12. Type System Maintenance Today at 8pm CST in the Title field.

13. Type The System will require maintenance from 8pm CST to 9pm CST today, please be advised that the system will NOT be available during this time in the Body field.

14. Type <Tomorrow’s Date> in the Expiration field.

15. Click Save. This announcement is now viewable by all Infor Ming.le™ 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.

Infor Lawson for Ming.le™

Infor Lawson for Ming.le™ Installation Guide Infor Lawson for Ming.le™ Administration Guide Getting Started with Infor Lawson for Ming.le™ Lawson Plugins for Infor Ming.le Installation Guide

Infor Lawson for Ming.le™ is the user interface for Infor Lawson Enterprise Applications and Self-Service applications. The installation consists of three components:

• Core components

Installed on the Infor Lawson System Foundation server

• Web components

Installed on the web server configured for Infor Lawson System Foundation

• Infor Lawson for Ming.le™ plug-in

Installed and configured on the Infor Workspace Microsoft SharePoint server

Infor Lawson for Ming.le™ can be summarized as infrastructure of WEBDIR\lawson\portal on web server and LAWDIR\persistdata on the LSF Server. In addition, there’s a plug-in installed within Infor Ming.le™ Microsoft SharePoint to allow access to that application. Technically the Infor Lawson for Ming.le™ can be called directly as done in the past with “server”/Lawson/portal, however this is not a supported use. The supported use is accessing Infor Lawson for Ming.le™ through the Infor Ming.le™ Foundation. Accessing through Infor Ming.le™ Foundation allows access to contextual applications.

Lawson plug-in for Infor Ming.le™

Lawson plug-in for Ming.le enables the Infor Lawson applications to run in the Infor Ming.le™ user interface. Each Infor Lawson product that runs in Infor Ming.le™ has a corresponding plug-in. The plug-ins are installed on the Infor Ming.le™ server and provide essential configuration information to Infor Ming.le™.

Before a plug-in for any Infor Lawson application can be installed the DSSO for Infor Ming.le™ must be installed from the DSP.

Summary of the Lawson plug-in for Infor Ming.le™ installation process:

1. Install and configure plug-ins on the Microsoft SharePoint server to enable the Infor Lawson products in Infor Ming.le™.

2. Log in to the Infor Ming.le™ Server as the spinstall account and verify that Microsoft SharePoint services are running.

3. Download the plug-in to the Infor Ming.le™ server from Infor Xtreme Support.

4. Execute the installer delivering the plug-in to the proper directory and allow “Everyone” to install.

5. Access the Infor Ming.le™ configuration as spfarm account and configure the plug-in for the designated site collection.

6. Grant permission to the “lawson” user account through site permissions as spinstall.

7. Verify the installation by accessing the Infor Lawson Applications in Infor Ming.le™.


@ 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 Infor Lawson for Ming.le™ requires the Infor Lawson Application plug-in to be updated then follow the instructions in the Lawson Plugins for Infor Ming.le™ Installation Guide.

Granting access to Infor Lawson for Ming.le™

A user would require access to the application. Infor Lawson for Ming.le™ should be granted in a manner to address the users for an organization.

Options:

• Selecting all authenticated users • Selecting an Active Directory group or AD user (Kerberos) • Selecting an RM role or resource/user (LS as STS)

Demo: Exploring Ming.le™ for Infor Lawson access grants Your instructor will demonstrate how to view permissions established to grant access to the user base of Infor Lawson for Ming.le™.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.6: Exploring Infor Lawson for Ming.le™ access grants In this exercise, you will access Ming.le > Ming.le™ for Lawson as an administrator and view the permissions that have been established to grant access to the user base of Infor Lawson for Ming.le™. You will use Ussplu143 (LSF).

Exercise steps 1. Access IE > Favorites > Infor > Ming.le




4. Select Workspace for Lawson.

5. Select Site Actions > Site Permissions.

6. Select Lawson S3 (Contribute) link.

Notice the lawson user has been associated with this area allowing access. In addition, the InforWorkspaceForLawson RM role has been configured to allow access.

7. Access IE > File > New Session > Ming.le.



@ 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.



Notice that cstudent3 has access to the Infor Ming.le™ Foundation home but not the Infor Lawson for Ming.le™ (Infor Lawson).

10. Access IE > File New Session > Infor > Infor Security Services on Ussplu143.



13. Select People in the Search area.

14. Type cstudent3 in the Search field.

15. Select the pencil icon next to the People record for cstudent3.

16. Select Basic Information.

17. Edit Roles.

18. Connect InforWorkspaceForLawson.

19. Select Update User. The fields required are not populated on cstudent3 because the account was added through Lawson Security Administrator and not ISS. Select the “Show only required” option and fill in the required fields. The en value should be used for ISO Locale. The following message displays: Success! Update completed successfully when Update User is successful.

20. Return to the IE session for cstudent3 and press F5 to refresh.

21. Notice the Infor Lawson for Ming.le™ application is now accessible.


@ 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 Lawson for Ming.le™ roles An Infor Lawson for Ming.le™ user’s experience can be controlled with a PortalRole assignment. An Infor Lawson for Ming.le™ role allows a Portal Administrator to customize how the Portal will look and what options the user will be allowed. An Infor Lawson for Ming.le™ role is on every user of the Lawson user. It may just be the default.xml which is delivered. Creating Infor Lawson for Ming.le™ roles for different types of users can help control options and reduce issues of navigation for end users

Demo: Creating and assigning a Infor Lawson for Ming.le™ role Your instructor will demonstrate how to create an Infor Lawson for Ming.le™ role.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.7: Creating and assigning a Infor Lawson for Ming.le™ role In this exercise, you will create and assign an Infor Lawson for Ming.le™ role to a user. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE.

2. Log in with the following information:


3. Select Infor Lawson for Ming.le™.

4. Select Common Tasks > Manage Roles option.

5. Select Migrate and accept OK on migration to 10.0.3 version.

6. Click New.

7. Type classess.xml in the Name field for the new role (Note: ***.xml role files are stored in LAWDIR\persistdata\lawson\portal\data\roles).

8. Click the General tab.

9. Disable the following options:

• Allow use of Search • Allow use of Favorites • Allow keyboard customizations

10. Click the Menus tab.

11. Disable Content and User Options.

12. Access Locks > Subscribe and Layout.

13. Lock the Employee Self-Service Bookmark.


@ 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. Click Apply and OK.

15. Access ISS.

16. Find the hstudent2 user.


18. Access LSF.

19. Type classes.xml in the PortalRole field.

20. Select Update User. (Note that additional fields not filled in when using the LSA tool in Lesson 11 are now required in Basic, Landmark and LSF, the same as the previous exercise.)

21. Access IE > File > New Session.


• User name: hstudent2 • Password: Tr@in123


24. Verify Infor Lawson for Ming.le™ experience forced on hstudent2 the following:

• No Search Box. • Content missing under Preferences. • Employee Self Service Bookmark is already present.


@ 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.

Bookmarks Access to bookmarks can be allowed or denied. If left globally allowed then any user of the portal with Content option can subscribe to the open bookmark. Note that bookmark access does not give user authorization to the area connected to the bookmark. Security must still allow the user access for the bookmark to be fully functional. If a bookmark is denied then either the user must be explicitly granted access by their ID or participate in a group that is allowed to use the denied bookmark. Using the right combinations of Allow and Deny bookmarks on an Infor Lawson for Ming.le™ role can create unique setup even for those users sharing the same xml PortalRole assignment.

Demo: Assigning bookmarks controlled by groups in Infor Lawson for Ming.le™ Your instructor will demonstrate how to assign bookmarks controlled by groups in Infor Lawson for Ming.le™.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.8: Assigning bookmarks controlled by groups In this exercise, you will assign a bookmark that is allowed through a group. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access RM Administrator. 2. Select Add > Group.

3. Type Manager in the ID field.

4. Type Manager in the Description field.

5. Select Edit > Add.

6. Select File > New View > Resources > People.

7. Select * in the Name field.

8. Click Find Now.

9. Select Helen Student2 and right-click Edit RM.

10. Double-click the Group field.

11. Connect the Manager group to the right and select Finish.

12. Select Edit > Change.

13. Close the hstudent2 record window.

14. Access IE.


@ 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.



16. Select the Infor Lawson for Ming.le™.

17. Select Common Tasks > Manage Bookmarks.

18. Right-click Manager Self-Service > Edit Access.

19. Select close or lock on the icon next to Default Access.

20. Select the Add option directly across from Group.

21. Click Manager > Close.

22. Select Update Cache. (Only those users in the Manager group can access the Manager Self-Service bookmark.)

23. Select Home to return to Infor Lawson for Ming.le™.

24. Select Manage Roles and classess.xml. 25. Select the Locks tab.

26. Lock Manager Self-Service under both Subscription Lock and Layout Lock.

27. Click Apply and OK.

28. Select Home to return to Infor Lawson for Ming.le™.

29. Clear IOS Cache and Submit.


31. Notice Manager Self Service Bookmark is now present.

32. Close the 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.

Infor Lawson for Ming.le™ customizations

Shortcuts and hotkeys A portal administrator can remap the hotkeys for any portal role assignment and thereby changing the hotkeys for all users with that xml. Or they can allow the end users to customize their hotkeys individually. In addition, portal administrators can allow users to create shortcuts. Shortcuts can be created for any Lawson form but not limited to just Lawson. Shortcuts created by users are assigned to their unique xml stored in the persistdata directory of the user environment.

Demo: Shortcuts and hotkeys Your instructor will demonstrate how shortcuts and hotkeys can be changed in Infor Lawson for Ming.le™.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.9: Changing hotkeys and shortcuts In this exercise, you will change Infor Lawson portal hotkeys and shortcuts. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE.



3. Select Infor Lawson for Ming.le™.

4. Select Preferences.

5. Click the User Options > Hotkeys tab.

6. Change the Select Hotkeys Set from Portal to ERP Applications.

7. The Open/Select Field Context action is currently assigned to the Enter key. To change the assignment to the F4 key select Record > F4 > Esc > Assign.

8. Select Apply and OK.

9. Launch HR11.1 and notice that Company select is now F4 and not the Enter key.

10. Select User Options > Favorites tab.

11. Add new favorite to Google and URL http://www.google.com and select open in new window.

12. Add new favorite to Employee and URL LAWFORM|TKN=HR11.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.

13. Select Apply and OK.

14. Launch Favorites to Google and HR11.1 from menu.

15. Launch Windows Explorer and navigate to LAWDIR\persistdata\lawson\portal\data\users.

16. View lawson.xml file using Notepad. Notice the favorites and hotkeys changes are captured.


@ 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 Smart Office

Infor Smart Office Administration Guide

Infor Smart Office provides a user interface that lets you conveniently access Infor applications. Its framework is designed to host and enable interaction among multiple Infor applications. Using the canvas, you can navigate and switch between applications with ease. You can use the personal widgets, event notifications, bookmarks, and process monitors to better manage your organization's data.

The Infor Smart Office installation includes the following components:

• Infor Smart Office server

This is where authentication, settings, and configuration data are defined. The server is bundled with the installation point, which hosts the Infor Smart Office client component for download to users' desktop machines.

• Infor Smart Office client

This is installed on end users’ desktop machines. End users update Infor Smart Office client from the installation point.

There are two options for installing the client:

• The Click-once installation option, where end users access an installation point URL to install the client and get automatic updates.

• The framework option, which is recommended for virtualized desktop environments where

multiple users access a single client machine. In this scenario, the Infor Smart Office client framework is installed on the client machine. The features are loaded from the installation point.

The LifeCycle Manager is used to install or update the Infor Smart Office product on the designated server. Infor Smart Office requires a DSSO installation. This process is also done in LifeCycle Manager.

Infor Smart Office user administration

Infor Smart Office is accessible for any basic user established properly in LSF LDAP. All Lawson Security roles will apply for authorization.

• An additional role of FormPersonalizationRole should be assigned if the Infor Smart Office user should be allowed to customize the user interface experience. Users without this role will not be allowed to make personalizations.

For Infor Lawson Enterprise Applications in Infor Smart Office, users have several options for customizing their experience. These personalizations are stored on the Infor Lawson System Foundation 10 server in LAWDIR/persistdata/lawson/SmartClient/data/forms/Data Area.

There are three sub-directories:

• /global • /roles/RoleName • /users/UserName


@ 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: Personalization of Infor Smart Office Your instructor will demonstrate how to access Infor Security Services and grant the proper role to allow personalization.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.10: Personalization of Infor Smart Office In this exercise, you will access Infor Security Services and grant the proper role for allowing personalization. In addition, access the Infor Smart Office Client and perform a personalization. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > Infor > Infor Security Services (ISS). 2. Select People in the upper right Search option.

3. Type cstudent3 in the Search field.

4. Select the Edit Resource (pencil) icon next to the People record for cstudent3.

5. Select Basic Information.

6. Edit Roles.

7. Connect FormPersonalizationRole.

8. Select Update User. The message: Success! Update completed successfully, displays.

9. Click the Infor Smart Office Train desktop shortcut.



12. Click the default Application tab.

13. Access Navigator > Start. 14. Type AP10 in the Search field to launch the form.

15. Access Tools > Personalization >Show/Hide Fields > Unconditional. 16. Uncheck the boxes next to the label and the field for Tax ID.

17. Click Save.

18. Notice the Tax ID field and label are gone.

19. Click Log-off to exit Infor Smart Office.

20. Access Windows Explorer and navigate to: C:\LSFENV\law\persistdata\lawson\SmartClient\data\forms\APPS10\users\cstudent3

Infor Smart Office administrators require additional setup in the Lawson LifeCycle 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: Exploring administrator setup for Infor Smart Office Your instructor will demonstrate how to set up an administrator for Infor Smart Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 13.11: Exploring administrator setup for Infor Smart Office In this exercise, you will access the Infor Smart Office LifeCycle Manager and explore the setup of an administrator for Infor Smart Office. You will use Ussplu143 (LSF).

Exercise steps 1. Access Start > All Programs > Lawson > LifeCycle Manager Client 2.0.

2. Type LCMadmin in the User Name field.

3. Type Lawson123 in the Password field.

4. Click the default Application tab.

5. Select Lawson Grid 10.*

6. Select the LCMGrid.

7. Right-click and select Lawson Grid 10.*> Configuration Manager. 8. Select User and Role Mappings.

9. Select Edit from Members Column under the Administrator row. Lawson is listed currently as the only administrator.

10. Select Add to display the Add Role Mappings to Administrator.

11. Type cstudent3 in the Custom field under Global.

12. Select Add on row for Custom field.

13. Click OK.

14. Click OK again.

15. Click the Save (disk) icon on the Grid Application User and Role Mappings page.

16. Click the Infor Smart Office Train desktop icon.



19. Notice in the Navigator area the Administration Tools are now available.


@ 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 Smart Office allows for personalization at a role assignment level. This process mirrors the Infor Lawson for Ming.le™ role creation process. The role is defined in Infor Smart Office and assigned as the Portal Role Attribute in Infor Security Services. In addition, user personalization can be done by an administrator and pushed to a user or set of users through Administration Tools. For more information on this process view the Infor Smart Office Administration Guide.


@ 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) Name some of the differences noted between Infor Ming.le™ Foundation and Infor Ming.le™ Enterprise.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) In Infor Ming.le™ Foundation how is a user established as an administrator?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) List the general installation process for Infor Lawson for Ming.le™. (Hint: there are three major steps.)

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

4) Name the three ways a user can qualify for access to an installed Infor Ming.le™ application or the Infor Ming.le™ Foundation.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

5) What are some of the benefits of using Infor Ming.le™ Foundation?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) Explain the process by which an administrator can change a user’s experience in Infor Smart Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

7) Describe the type of users who would access Infor Lawson Enterprise Applications via Infor Ming.le™ Foundation vs. users who would access Infor Lawson Enterprise Applications via Infor Smart Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

8) How would you assign a PortalRole designation to control a user’s Infor Lawson for Ming.le™ experience?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

9) How would a user assign a bookmark if not delivered via PortalRole assignment for Infor Lawson for Ming.le™?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 14: Additional end user topics Estimated time 2 hours


• List the capabilities of Infor Lawson Design Studio. • Describe how to create an Infor Process Automation (IPA) process. • Describe the administration process for IPA. • Explain the reporting options of ION Enterprise Search, Infor Lawson Add-ins for Microsoft Office,

and Infor Spreadsheet Designer. • Describe the process of configuring a standard report with Infor Lawson Smart Reports.

Topics • Process management • Reporting • Check your understanding

220 Lesson 14: Additional end user topics © 2013 Infor Education

@ 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 management

Infor Lawson Design Studio Installation Guide Infor Lawson Design Studio User Guide

Infor Lawson Enterprise Applications can be enhanced through the use of additional products to customize or extend functionality. This section will introduce and give an overview of Infor Lawson Design Studio, Infor Smart Office Mashup, and Infor Process Automation. Infor Education offers specific classes on these products. Inclusion in this LSF Administration class is to help administrators support those in the organization that may use these applications.

Infor Lawson Design Studio Infor Lawson Design Studio is a browser-based, drag-and-drop graphical development environment which can be used to customize or enhance Infor Lawson applications in a variety of ways.

The Infor Lawson Design Studio is made up of the following stand-alone components:


Wizard Designer A simple-to-use tool that lets you automate form actions (like add, delete, inquire) and create help text specific to your site for an Infor Lawson form.

UI Designer A tool to customize Infor Lawson forms or create new forms.

Portal Page Designer A tool for creating portal pages. These could be your own gateway to Infor Lawson or could be used for a wide variety of other purposes.

Built into the Infor Lawson Design Studio are the following additional features:


Lawson API Builder Retrieve and send Infor Lawson data through the Internet Object Services engines. Application Programing Interfaces (APIs) created using the API Builder can be pasted into other applications that you create such as Crystal reports or Visual Basic (VB) applications.

Scripting Environment The Infor Lawson Design Studio includes a JavaScript development environment for adding functionality specific to your needs to a form or portal page. Within the environment Infor Lawson provides an Object Viewer that makes it easy to understand and access Infor Lawson objects when you create a script.

Infor Lawson Design Studio forms are accessible through the Infor Lawson for Ming.le™.


@ 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 summary:

1. Verify Java SDK and Perl version levels.

2. Download the Infor Lawson Design Studio product from Infor Xtreme into the install directory. (There are components for the Infor Lawson server and Web Server. The steps outlined below would be repeated for the LSF server and Web Server.)

3. Extract the .zip and execute the .jar file.

4. Select the Lawson Core Technology where Infor Lawson Design Studio will be installed. (This step is repeated if there are multiple environments on the server requiring Infor Lawson Design Studio installation.)

5. Execute the installation and verify error-free logs.

6. Restart the LSF instance properly including IBM WebSphere and Web Servers.

Demo: Exploring Infor Lawson Design Studio Your instructor will demonstrate how to create a simple portal form using Infor Lawson Design Studio.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 14.1: Exploring Infor Lawson Design Studio In this exercise, you will access Infor Lawson Design Studio and create a simple portal form for Vendor (AP10.1) where the change is to default the company value into the form. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Access IE > Favorites > Infor > Design Studio.

(http://ussplu145.lu141training.lawson.com/lawson/studio)



4. Access UI Designer > Form > Productline > APPS10 > System Code > AP > AP10.1 > quick Paint > Finish.

5. Select the Vendor Group value field on the form.

6. Select the Default field on the Properties panel.

7. Type 4321 in the Literal field.

8. 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.

http://ussplu145.lu141training.lawson.com/lawson/studio

9. Select View > Document Properties.

10. Select the Default Presentation checkbox.

11. Click OK.

12. Select File > Save As.

13. Select OK to use AP10_Custom and the assigned AP10.1.new.xml. 14. Exit the Design Studio browser.

15. Access IE > Favorites > Infor > Infor Ming.le.



18. Select Lawson for Ming.le™.

19. Select Clear IOS Cache link under Portal Administration.

20. Click Submit.

21. Search for the AP10.1 application and notice 4321 defaults in the Vendor Group field.

Saving as the “Default Presentation” will cause this AP10.1 form from LAWDIR > persistdata > lawson > studio > forms to be presented on any search or call for AP10.1.

Infor LSF Using IPA Configuration Guide Infor Process Automation Admin Guide Infor Process Designer Installation Guide

Infor Process Automation Infor Process Automation (IPA) 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 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 Automation server-side tools for administrators

Infor Process Automation delivers menus and other tools for system administrators to configure, schedule, launch, maintain, and troubleshoot processes. These tools are accessed through Infor Landmark Technology Runtime. This area is usually provided to the Infor Process Automation system administrator or anyone who would be responsible to manage or monitor processes. The Infor Process Server Administrator is available through the Rich Client and can be controlled through Infor Landmark security. The Rich Client is a web-deployable client application.

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. A user at your site who will be creating processes; business analysts, power users, and software developers will need to have the tool installed on their desktop machines.


@ 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 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, Smart Office, Workspace User Interface, LBI Dashboard or via direct web URL link. 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.


1. Infor Landmark Technology Runtime is required to be installed (Environment and Grid).

2. The Landmark product line for the IPA product must be created with database connectivity to the corresponding data area.

3. IPA must be deployed to the IBM WebSphere Application Server for Infor Landmark (plug-ins are generated and propagated to the web server).

4. LPSClientJars.jar are copied from Landmark to GENDIR > bpm > jar directory on LSF.

5. There is an optional migration process for those with existing process flows from LSF9.

6. Set pfserv config to point to lps (requires setting the LPS Grid Name and LPS Port).

7. Configure IPA in bpm.properties file (data area of Infor Landmark identified, email configuration, verification of jar file pointer).

8. Set up communication from Rich Client Process Server Administration to Infor Lawson Enterprise Application server.

9. Install the Infor Lawson Enterprise Services into IPA Data Area (formerly in LOGAN of LSF).

10. Configure IPA email settings.

After LSF initial configuration, updates to Infor Process Automation will take place on the Infor Landmark Technology Runtime server. The Infor LSF using IPA Configuration Guide provides the steps of configuration and update.

Demo: Exploring Infor Process Automation Your instructor will demonstrate how to access and navigate Infor Process Automation and the Rich Client Infor Process Server Administration areas.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 14.2: Exploring Infor Process Automation In this exercise, you will access Infor Process Designer and Rich Client’s Infor Process Server Administration areas. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Click the IPD desktop shortcut.



4. Click OK.

5. Select File > New Infor Process File.

6. Select the Palette tab.

7. Drag Email Activity node (under Common) to the process between Start and End nodes.

8. Select Connection (under Main) and click Start node then arrow to Email node, and Email node to End node.

9. Highlight the Email Activity node.

10. Select the Properties tab.

11. On the Email Properties:

• To: your email address • From: [email protected] • Subject: Testing IPA • On the Error Tab: Select Stop Process option

12. Select File > Save as LSFDiffTest (.lpd).

13. Select Run process.

14. Verify in the Console log that the Process Ran Successfully.

15. Select Upload Process.

16. Type a <description> in the Description field.

17. Accept other defaults.

18. Click OK.

19. Click the Rich Client desktop shortcut.

20. Type lawson in LOGIN field.

21. Type Tr@in123 in Password field.

22. Select the Data Area (upper left) and set to APPS10.

23. Double-click the Process Board Process Server Administration.

24. Select Scheduling > By Process Definition.

25. Select Actions > Create.

26. Select the LSFDiffTest Process Name.

27. Type LSFDIFFTestIPA in Work Title field.

28. Select Actions > 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.


29. Select Actions > Start. 30. Click X to close Process Triggers.

31. Select the Back < arrow to return to the Process Board main menu.

32. Select Administration > Work Units.

33. View your Work Unit created.


@ 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.

Reporting

ION Enterprise Search Installation Guide ION Enterprise Search S3 Plugin Installation Guide ION Enterprise Search Administration Guide

Infor Lawson Enterprise Applications reporting can be enhanced through the use of additional products that extend standard functionality. This section will introduce and give an overview of Infor ION Enterprise Search, Infor Lawson Add-ins for Microsoft Office, Infor Spreadsheet Designer, and Infor Lawson Smart Reports. Infor Education offers specific classes on these products. Inclusion in this LSF Administration class is to help administrators support those in the organization that may use these applications.

Infor ION Enterprise Search Infor ION Enterprise Search (IES) allows users to access application data through an intuitive, "Google-like," text search.

From a list of "hits," you can navigate links to related information. This information could be an application at a specific field or database record (row), a knowledge base article, or a website.

An Infor ION Enterprise Search installation includes:

• Infor ION Enterprise Search server. • One or more application-specific deployments, for example, for Infor Lawson or Infor M3, which

connect the Infor ION Enterprise Search server to the applications. • Interest Centers, which define the data sets that can be searched.


1. Download Infor ION Enterprise Search from Infor Xtreme support and install through LifeCycle Manager.

2. Download and install the Infor ION Enterprise Search for Infor Lawson using LifeCycle Manager.

3. Establish services.cfg for Configuring Direct IOS, Configure S3 Lawson System Foundation for Enterprise Search, configure securable types for Enterprise Search in LifeCycle Manager.

4. Add an S3 Lawson System Foundation deployment, define indexes, and searches. Modify Grid Max Heap in LifeCycle Manager.

5. Establish security for IES.

6. Test installation.

7. Configure IES and Companion in Infor Smart Office Navigator.

Demo: Exploring Infor ION Enterprise Search Your instructor will demonstrate how to access Infor ION Enterprise Search in Infor Smart Office and Infor Ming.le™ Foundation.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 14.3: Exploring Infor ION Enterprise Search In this exercise, you will access Infor ION Enterprise Search in Infor Smart Office and Infor Ming.le™ Foundation. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Click the Infor Smart Office desktop icon.



4. Select the Enterprise Search shortcut on the canvas.

5. Type Charles Holley in the Search field.

6. Click Search.

7. Select Human Resources Setup results > HR07 Supervisor link.

Infor Lawson Add-ins for Microsoft Office Installation Guide Infor Lawson Add-ins for Microsoft Office User Guide

Infor Lawson Add-ins for Microsoft Office Infor Lawson Add-ins for Microsoft Office is a desktop product used for extracting data from the Infor Lawson systems.

The Infor Lawson Add-ins for Microsoft Office consists of the following wizards:

• Query wizard - Used to create custom queries to pull data out of the Infor Lawson applications into a Microsoft Excel worksheet.

• Upload wizard - Used to upload data from a Microsoft Excel worksheet to Infor Lawson application tables.


1. Download the product (.exe) from Infor Xtreme and install with administrative rights.

2. Enable Add-ins through Excel Options.

3. Confirm user has Add-ins attribute on LSF user record set to Allow or the desired control 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.

Demo: Exploring Infor Lawson Add-ins for Microsoft Office Your instructor will demonstrate how to execute a simple query using Infor Lawson Add-ins for Microsoft Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 14.4: Exploring Infor Lawson Add-ins for Microsoft Office In this exercise, you will access Infor Lawson Add-ins for Microsoft Office and execute a simple query. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Open Microsoft Excel.

2. Select Lawson Query wizard under Add-ins.



5. Select Database Tables.

6. Select System Code IF > GLSystem.

7. Select Company field.

8. Click Finish.

9. View results.

Infor Spreadsheet Designer for Microsoft Excel Installation Guide

Infor Spreadsheet Designer Infor Spreadsheet Designer lets you access Infor Landmark data through Microsoft Office Excel. The Infor Spreadsheet Designer is different from Infor Lawson Add-ins for Microsoft Office in the sense that it follows the architecture of the Infor Landmark applications and the query or upload is from the business class object representing the data.

The end user can download data from the Infor Landmark application using the Query tool and can update data in the Infor Landmark application using the Upload tool. Infor Spreadsheet Designer limits the user access by restricting authorization to objects granted with Infor Landmark Security Roles. The user can only query data granted by Business Class access or change data through Business Class 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.

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 is installed through Microsoft ClickOnce technology. This technology enables an application desktop component to automatically update itself when application changes are detected. Each time you access your Microsoft Excel application, the application searches the previously installed location. If a new version is available, it is automatically installed.

Before end users can install Infor Spreadsheet Designer, create a ClickOnce installation point for them to install from. This installation point can be hosted in several ways, including a web server and a network fileshare. If installing to a URL, a setup.exe file is used to set up the installation point; if installing to a UNC path to a fileshare, the setup.exe file is not used and the UNC path is the actual name for the file share. You can:

• Create an Infor Spreadsheet Designer deployment that will be hosted for end users on one of the client's web servers.

• Create an Infor Spreadsheet Designer deployment that will be hosted for end users on a network file share.

• Deploy using a method that is not described here. The Microsoft Development Network (MSDN) provides good information about how to deploy products, like Infor Spreadsheet Designer, that are built using Microsoft ClickOnce technology. To find information, search the MSDN web site (msdn.microsoft.com) for "ClickOnce," "deployment," and other related topics.

Demo: Exploring Infor Spreadsheet Designer Your instructor will demonstrate how to execute a simple query using Infor Spreadsheet Designer.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

Exercise 14.5: Exploring Infor Spreadsheet Designer In this exercise, you will access Infor Spreadsheet Designer and execute a simple query. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Open Excel.

2. Click Infor in the Excel tool bar.

3. Select Insert Query.




@ 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. Click the GEN Data Area.

7. Click Actor Business Class.

8. Select the Actor field.

9. Select Insert.

10. Click Refresh (next to Insert Query).

11. View the results.


@ 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 Lawson Smart Reports Designer Installation Guide Infor Lawson Smart Reports Designed User Guide Infor Lawson Administration: Jobs and Reports

Infor Lawson Smart Reports Infor Lawson Smart Reports (LSR) Designer provides the user a tool for enhancing the existing layout of report templates generated using Infor Lawson report programs. This desktop application uses a drag-and-drop design environment, with preview function to let the user evaluate any modifications applied on the LSR template.

In Infor Lawson for Ming.le™ or Infor Smart Office, each generated job has a template file where its default formatting is defined. The user must retrieve the template file (*.rptdesign) from the Infor Lawson server and open the file in LSR Designer for editing.


1. Download the LSR Designer (.exe) from Infor Xtreme.

2. Run the executable.

The report template becomes available for editing only after generating a report job. Both the template file (*.rptdesign) and the data source (XML) must be extracted from the Infor Lawson server to open the template in LSR Designer correctly.

Before starting the editing in LSR Designer, specify a data source to be used by the template in LSR Designer. This data source connection defines the formatting details, job query, and data source type (XML) of the template. All of which are required in previewing the template to validate the modifications.

Demo: Exploring Infor Lawson Smart Reports Your instructor will demonstrate how to retrieve a template for a report, make an edit, and view the report in Infor Lawson for Ming.le™ and Infor Smart Office.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 14.6: Exploring Infor Lawson Smart Reports In this exercise, you will retrieve a template for a report, make a simple edit and view the report within Infor Lawson for Ming.le™ and Infor Smart Office. You will use Ussplu143 (LSF) for this exercise.

Exercise steps 1. Select the Infor Lawson Smart Report icon from the desktop.

2. Choose File > Open File.

3. Go to c:\Desktop\ClassInfo9-10\Lawson Smart Reports\cu201_default.rptdesign.

4. Double-click cu201_default.rptdesign.

5. Navigate to the Outline section in the lower left of page.

6. Right-click Data Sources > Edit. 7. Type the location of the data c:\Desktop\ClassInfo9-10\Lawson Smart Reports\cu201.xml.

8. Click OK.

9. Access File > Save As > c:\Desktop\cu201_default.rptdesign (notice Desktop and not folder ClassInfo9-10).

10. Select the Master Page layout tab in the main pane of the designer.

11. Click the upper left box. The image in the Outline section should be highlighted.

12. Right-click and select Edit for the image.

13. Select Embedded image.

14. Click Add Image.

15. Go to c:\Desktop\ClassInfo9-10\Lawson Smart Reports\companylogo.jpg.

16. Click Open.

17. Drag the cell to the logo size to resize the logo to fit into the corner.

18. Save the changes to the cu201_default.rptdesign.

The cu201_default.rptdesign would be copied into LAWDIR > PDL > lsr > templates > standard > CU201. The report would need to be rerun to use the template and show the changes in print manager with Lawson Smart Report view 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) What directory does the Infor Lawson Design Studio form get published to and accessed by Infor Lawson for Ming.le™?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

2) In what Data Area will an administrator find the Work unit table?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

3) Where can a user access their Inbasket for the purpose of approving with IPA?

______________________________________________________________________

4) What are the benefits of installing Infor ION Enterprise Search?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________

5) Name some differences between Infor Lawson Add-ins for Microsoft Office and the Infor Spreadsheet Designer.

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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) What are the basic steps for configuring a standard report with LSR?

______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________


@ 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 summary Estimated time 30 minutes

Course objectives Now that you have completed this course, you should be able to:

• Identify Infor Lawson System 10 architecture and directory structure. • Describe key Infor Lawson System concepts and terms. • Describe how to maintain Infor Lawson servers, system processing and job processes. • Explain how to apply product installation or updates, maintenance releases and patches. • Explain how to manage Infor Landmark Technology Runtime for Infor Process Automation only. • Describe how to maintain IBM WebSphere, user administration with Infor Security Services,

Lawson LDAP, Infor Ming.le™ Foundation,and Infor Lawson for Ming.le™, and Infor Lawson Security administration.

Topics • Course review

236 Course summary © 2013 Infor Education

@ 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 system foundation for...

Documents