Lawson Grid

Matt-
We are an AIX shop running LSF 9.0.1.12 and have had Smart Office running for about 18 months. We started LSO (ISO in today's verbiage) at v10.0.1 and had help with the original install from LPS because I am a unix admin and all the parts of LSO run on windows. I don't believe you can put any other pieces of LSO on aix so I would recommend putting it all on your windows box and then it is all in a nice, compact spot. My experience was good having outside help to do the original install, as far as updates, I was able to do the 10.0.1 to 10.0.5 update without outside help, except when I needed to involve Infor support and they got me through any problems I had. My next jump will be to ISO 10.1.2.....
Hope this helps.

I'd recommend keeping everything on the same server for Smart Office; there is an option to scale across multiple servers, but honestly I don't know of anyone on the S3 side that's done this (or needed to do this).

We have two Windows servers for Smart Office, one for prod and one for test.  On the test server, we have two grids installed - one running LSO 10.0.5 and another running ISO 10.1.2.  We use the second grid for testing the new release, basically a dev environment before asking the users to test it.

The installation has a lot of moving parts, which is why I'd recommend hiring professional services to assist:

LCM Server
LCM Service
Grid
GDBC
DSSO Session Provider
Smart Office
Companion

The pieces that tend to be the most challenging are the LCM installation (making sure the pre-requisites are met, Java versions are correct, etc) and the DSSO Session Provider (determining which versions to use, making sure that required LSF patches are in place, etc). 

I hope this helps and good luck with your implementation of Smart Office!  As a side note, Smart Office 10.2 for S3 will be available soon and has some nice new features.  Check out the developer blog:
http://smartofficeblog.co...smart-office-10-2-2/

I want to be able to use Smart Office (same version preferably, say 10.1.2) to access either my Test or Production Lawson server. It is my understanding that I cannot have the same instance/grid/Smart Office(? not sure of terminology) accessing two different Lawson LSF environments. If that is the case, how are people setting up their test and prod areas for both ISO and Lawson apps?

You can have single smart office instance accessing multiple Lawson environments. It is done by creating multiple profiles and user selects which one when logging into smart office.

As long as the user credentials are the same in TEST and PROD (or whatever environments you would like to connect to in Smart Office), you can set up multiple profiles to point to different environments.

We chose to have different grids because this allows us to upgrade the grid, grid extensions and Smart Office itself in test before moving the changes to production. 

Anna, when you login to Smart Office, you enter your credentials and then (assuming you have the option available) select a profile...so why does that matter ( user credentials are the same in TEST and PROD ) ?

Hi John,

Smart Office for S3 requires DSSO for the session provider and DSSO must point to a specific security server. So, let's say that DSSO was installed against PROD, which is bound to AD, but that TEST isn't bound and uses different credentials entirely... the user will attempt to login to TEST profile and the system will check that the user exists with the provided credentials in PROD (because this is where DSSO is pointed) and authentication will fail.

I'm guessing that this would be rare, as most people just bind to the same AD for all LSF instances and therefore credentials are the same across all the environments.

OK, thanks.

This is awesome! I was under the impression it wasn't supported to use Profiles for Prod and Test.

I would agree with Anna that LCM and DSSO are the more complex parts of the install. Like everything else, it just takes a little practice.

Excellent thread! I'm in the process of working on step 2 of Anna's list above (LCM Service). Certainly complicated thus far.

Thank you all for this helpful information,
Jared