Lawson Companion Config

You need to install WebSphere App Server, and attach it to the Lawson Grid.

Thanks John.  Do you know where that is described in any of the install documentation?

Page 6 of the Companion install guide [cid:image001.png@01CC9301.9DD2CCB0] Page 9 of the Companion install guide [cid:image002.png@01CC9301.AF0718B0]

John- Thanks for your help on this. I installed WAS 7.0.0.19 but I cannot see it within the LifeCycle Manager which is running on the same server.  Any ideas on what could be causing that?

Make sure Websphere is appearing as an entry within LifeCycle Manager; also within that Websphere entry, make sure you have an Appserver and also the nodeagent.

You have to attach the WAS instance to the grid in LCM. The process is easy and it's in one of the manuals but I don't remember off the top of my head which one.

Thanks John. I have looked in the Grid, Smart Office, and Life Cycle Manager install guides and can't find anything regarding this process. Does anyone remember where the info is?

The process of attaching WebSphere can be found in the LifeCycle manager User Guide->Action Menu->Attaching a Product or Middleware. This guide is found in the LCM client Help->Help Contents. Shortly you double click on your host and then clicks Attach product.

Guys thanks for your help. Whenever I attempt to connect WAS using the instructions, it appears that the only server I can connect WAS to is the S3 server. I want to connect to WAS on the server that has the LCM Service on it correct? If so how do I add that as one of my available Hosts? You guys are a big help.

If your WAS server is on another machine you need to install a LCM service on that machine as well. When that is done you can attach the WAS server.

Do I need to install the LifeCycle Manager service on my Life Cycle Manager Server?

Yes. You must install thye LCM servcie on every machine you want to install something on.

That is potentially misleading primarily because the question is misleading and/or incomplete.

John this whole subject is super confusing... My guess at installing LSO is the following: Install Life Cycle Manager on new Windows Server Install Life Cycle Service on S3 Server Install Grid on Life Cycle Manager with S3 server as the host Install LCM Service on same new Windows Server Install WAS on new Windows Server Attach WebSphere to LCM Install Companion within WebSphere Install LSO within LCM on S3 Host Complete Session Provider Grid Extension Config Does this sound correct?

You do not install anything on the S3 server. For a vanilla LSO install, install everything on the same Windows server: 1. Activate Microsoft AD LDS role 2. Java JDK 32 bit & 64 bit 3. WebSphere App Server ND w/ default appserver/deployment manager profile 4. .NET Framework 4.0 Full Profile 5. LifeCycle Manager Server 6. LifeCycle Service 7. LifeCycle Manager Client 8. Lawson Grid 9. Session Provider Grid Extension, which includes binding to your corporate AD/LDAP 10. Install Smart Office into Grid 11. Sign the install point 12. Attach WebSphere to LifeCycle Manager 13. Install Lawson Companion into LifeCycle Manager Service attached WebSphere

I am all the way through the process and I can login to LSO but I cannot connect LSO to S3. FOr the companion, should I be able to see an app running in IE if I go to http://fqdn:9080/companion? I cannot see anything there but should I be able to see anything?

I will also add that you need to configure Companion within the Profile editor while you are logged in as an Administrator within the actual LSO Client.

Thanks for the comments Roger. I added the Lawson ID to the administrators.

PS. Newest version of Grid Companion does not require WAS anymore. We are WAS free.