The content of this article will describe changes made to Smart Office 10.0.4 from an installation and configuration view.
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.8 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.3 (or later), GDBC is part of the Grid extensions package 10.1.9. The Grid Database Connectivity (GDBC) Grid Extension is a collection of database-related tools geared towards aiding the usage of a database in a grid application. With GDBC, each grid application has an implicit database that it may choose to use. The GDBC provides an individual database connection string and database drivers for the grid application to use.
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 Smart Office binding have failed to start due to GDBC was not started, start GDBC and then stop the Smart Office binding. Smart Office wills automatically startup again.
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.
Important: If upgrading from LSO 10.0.0, 10.0.1 or 10.0.2 a fix must be downloaded through CCSS (Customer Correction Self Service). When the fix has been downloaded it must be saved to disk and executed.
Smart Office administrator
In Smart office 10.0.3 and earlier Smart Office administrators where maintained in the lib\userroles.xml file. From Smart Office 10.0.4 the administrators are maintained in another way.
From now on the Smart Office administrators are maintained in the same way as Smart Office users, i.e. with Grid application roles.
In Smart Office the following two 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 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). The difference between a role and a group is that having a certain role will give you rights in the application while a group is a way of grouping users together in order to ease maintenance.
The picture below shows the dialog where adding users or groups to a role.
If there are no roles listed in the Session Provider area verify that the active Session Provider 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 add a specific user, use the custom field in the Global 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.
When Smart Office is upgraded to 10.0.4 the content from the userroles.xml is not migrated and there are no default users added to the Administrator role. Be sure to configure the Administrator group after the upgrade is finished.
Mango.properties 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 LSO 10.0.4.
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. Within a few weeks there will be a new blog post about the Export/Import manager.
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.
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.