Infor Technology

« | Main | »

Installation and configuration changes in Lawson Smart Office 10.0.4

July 9, 2012

By Rickard Eklind

Lawson Smart Office 10.0.4 was recently released. The content of this article is technical in nature and will describe changes made to Lawson Smart Office 10.0.4 from an installation and configuration point of view.

Upgrade path
Upgrading to Smart Office 10.0.4 can only be made from versions between 10.0.0 and 10.0.3. During the upgrade all roamed user data and settings file will be migrated into the GDBC database and this process can take a while. DO NOT TURN OFF Smart Office until the status is set to OK.
The upgrade process can be followed in the log file.

New requirements
Lawson Smart Office 10.0.4 requires Lawson Grid version 10.1.9 (Technical version 1.9.1) and also the latest version of the used session provider. These are the versions supported.
- LDAP Session Provider (previously named Grid Session Provider) 1.9.7 or higher.
- Windows Session Provider 1.9.14 or higher
- DSSO Session Provider 1.3.6 or higher

The session providers listed above are all included in the Grid extension package 10.1.9.
Smart Office also requires GDBC version 2.0 (or later), GDBC is part of the Grid extensions package 10.1.9. By default GDBC installs two bindings, one that is the actual database and one that is the broker of JDBC drivers. Read more in the documentation that follows GDBC.

For GDBC to work smoothly I would recommend to change the default GDBC to allow a memory consumption to at least 512 MB.  If GDBC is not installed, not running or is set offline Smart Office will fail to start. If the Lawson Smart Office binding have failed to start due to GDBC was not started, start GDBC and then stop the Lawson Smart Office binding. Lawson Smart Office wills automatically startup again.

Lawson Smart Office Administration

In Lawson Smart office 10.0.3 and earlier administrators where maintained in the lib\userroles.xml file. From Lawson Smart Office 10.0.4 the administrators are maintained in the generic role grid UI at the same place as where allowed Lawson Smart Office users are maintained. When Lawson Smart Office is upgraded to 10.0.4 the content from the userroles.xml is not migrated.
In Lawson Smart Office the following application roles are used:
– Administrator: Users that belongs to the Administrator role will have access to the Administration tools in the Smart Office client.
– User: All users that belong to this role are allowed to start the Smart Office client. By the default the special group authenticated is added. A user that is authenticated in the grid will always belong to the group authenticated.
The picture above shows that the user 11914 is a Smart Office administrator and that all authenticated users are allowed to start the Smart Office client.

It is also possible to add a user group instead of specific users. Members of the groups are maintained in the user repository that the current Session Provider is configured to use. For example are the members of groups listed by the LDAP Session Provider maintained in the LDAP (probably Active Directory).
If there are no roles listed verify that the Session Provider Configuration and the user repository are correct configured.

If you already have a configured another application role in the Grid with the correct users, that role can be used as well and is selected in the Application area.

To see what a application roles you have visit the page https://<gridserver>: <https_port>/grid/user in an Internet Explorer
Remember that is it the Grid application roles that is listed and not the groups that the active Session Provider delivers. is a file that very rarely needed to be changed by an administrator. In Smart Office 10.0.3 and earlier the file was located in the lib folder. From LSO 10.0.4 the file is not used anymore and the properties from the file have been moved to Grid properties.
The only property that is meant to be changed is the Retrieve display name property and it is new in version 10.0.4. Read more about the new feature in this blog entry.

Settings files

Settings files, roamed user files and the pre-defined widgets file are all in the GDBC database now. The Settings files and pre-defined widget file can still be exported or imported with the new Export/Import Manager administration tool in Smart Office. There is a separate blog entry about the Export/Import manager <here link>.

LDAP Session Provider

If LDAP Session Provider is used LSO requires that the Group Element Mapping is correctly configured. Use the “Configure Session Provider” link in the LCM client
to start LDAP Session Provider Editor and go to the Group Element Mapping. Use the Validate button to verify that some groups are found.



In Smart Office version 9.1.3 to 10.0.3 the Smart Office server parts consisted of four Lawson Grid node types that executed separately. Each node type where executed in a separate JVM.
In Smart Office 10.0.4 there is only one Lawson Grid node type. image
This change has been made in order to reduce the amount of java processes and does not affect the functionality in Smart Office.


The backup routines for Smart Office 10.0.4 have slightly changed. Earlier all files where located in the LSOFiles folder. In 10.0.4 the LSOFiles folder still exists but the settings files, user files and pre-defined widget file have all moved into the GDBC database. That actual GDBC database file for LSO is located on the host where the GDBC H2 binding is running. In the file system that will be, <lcm service>\grid\<grid name>\applications\GDBC\h2db\LSO.h2.db. It is important that the database file is backed up together with the LSOFiles folder.


Leave a Reply

Your email address will not be published. Required fields are marked *

About this Blog

The latest on Infor Technology

Copyright Notice

© Copyright . Infor. Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Infor and with appropriate and specific direction to the original content.