During Ask the Experts webinar for (mainly) Lawson customers we got a lot of good questions. I’m going to try and answer some of the questions in coming posts and today I’m going to give you some tips and tricks for updating and migrating data to 10.1 and later. Continue reading
Today’s post is just a quick entry about a common error that you might get as you install a .lawsonapp file in Life Cycle Manager 9 (or Life Cycle Manager 10). I’ve received more than one question about this error message from Life Cycle Manager so I hope that this info will be of interest to the many administrators out there. The error message that you get in Life Cycle Manager is ‘Cannot find compatible location for dependency LSO. No available location exist or the user is not authorized to install application.’.
There are quite a few customers installing 10.1.1 and migrating their data from 10.0.5.2.x.
It is important to note that this is still a migration of data and not an upgrade path. There is a new stand-alone tool (Mango Admin Tool) that will help you with the export and import of data.
Some important notes to consider:
- You can only have one Smart Office installation per grid. (It does not matter if the name has hanged to MangoServer)
- If you want to use the same grid you need to: upgrade to 10.0.5.2, export the data, move the zip or download it, then uninstall and install 10.1.1.
- Separate .lawsonapplications need to be installed on 10.1.1 before importing the data, but the configuration will be imported. Installed features will not be migrated but installed Mashups will be included
- For Lawson DSSO you should NOT configure Smart Office to use the DSSO Router. You should use the Default Router with the DSSO session provider.
- You can run 10.1.1 on MS SQL server instead of the built in H2 database.
- You can use the Mango Admin tool to export and import data in the same version, cloning your production setup to test for example.
One of our customers, has blogged about his experience in his blog, Potato IT – Upgrading from Smart Office 10.0.5.2.16 to 10.1.1.0.19. He covers upgrading M3 User Adapter and Smart Office.
Smart Office 10.1.1 has been released and this service pack contains the tooling you need to migrate data from a 10.0.5.2 version to 10.1.1. Part of the work in this service pack is that we continued to move all files to a database so that we in the future can scale out Smart Office on to many Grids. We are not there yet becuase there are a few more changes needed on the server, but as of version 10.1.1 all configuration files that are related to the Smart Office server are stored in the database. Even though the name of the application in the Grid has changed to MangoServer it is still not supported to install more than one Smart Office server in the same grid (regardless of version). Continue reading
As I have mentioned in previous posts WordPress has this nice feature that allows us to read what search terms have been used in the blog. Today I spotted this: “putting smart office icon on desktop”. In most cases the search terms does not contain enough info of what the person is looking for but this time I think I got it.
Personally I usually start programs using the windows key followed by writing the name of the app. Smart Office is in the start menu once installed so that would be a quick way to launch it. But if you want to create a link to the program on your desktop there are two options. Continue reading
The content of this article will describe changes made to Smart Office 10.0.4 from an installation and configuration view. Continue reading
Why is it so hard to get Lawson Smart Office to work well with a desktop virtualized environment? I will try to answer that question is this article.
What is a desktop virtualized environment? You can read one definition on Wikipedia, http://en.wikipedia.org/wiki/Desktop_virtualization but explained briefly it is an application that makes it possible to execute other applications like they where installed locally but in fact they are executed on a server somewhere and only the “screen” is transferred to the client machine. That means no code from the application is actually executed on the client machine. Continue reading