Posts

Nogalis Webinar: Copying Landmark Productline (October 26th, 9 AM PST)

Copying productlines in S3 is a breeze, but Landmark is a different story. There are several possible scenarios and a lot of things to consider. Join us for this one hour webinar and gain access to a free tool that will help with the process.

A few things to keep in mind:

  1. Our webinars always fill up and we only have the capacity to host 200 attendees so sign up now!
  2. The time of the webinar is 9:00am PST. So please mind your time zone.
  3. Once you sign up, you can’t share the webinar link as each link allows for one unique session. So if you have colleagues who are interested in attending, please have them signup separately or else their session will kick you out.

We use anymeeting for our webinars. The application sometimes asks you to install a plugin. In order to be ready on time. Please give yourself an additional 10 minutes before the webinar begins.

When: Thursday October 26, 2017

               9:00 AM to 10:00 AM PST

This webinar is free to attend. Register Now

How to Apply, Stage, and Revert Application Patches (CTPs) in Lawson S3

In this brief, 1 hour webinar, we will go over the application maintenance tool set (AMT) and discuss how to find and apply patches to your Lawson application. We will also discuss how to stage multiple CTPs and back them out.  Lastly, we will go over some troubleshooting tips and how to handle issues that may come up during CTP installation.

Nogalis Webinar: How to Apply, Stage, and Revert Application Patches (CTPs) in Lawson S3

In this brief, 1 hour webinar, we will go over the application maintenance tool set (AMT) and discuss how to find and apply patches to your Lawson application. We will also discuss how to stage multiple CTPs and back them out.  Lastly, we will go over some troubleshooting tips and how to handle issues that may come up during CTP installation.

When: Thursday March 23, 2017

               9:00 AM to 10:oo AM PST

This webinar is free to attend. Register Now

How to Setup Dependencies for Lawson Services

After dust from the upgrade settles, it’s usually time to automate any and everything that can be automated. When it comes to Lawson (LSF) related services though things can get a big tricky.

There’s a precise order bringing up the services on windows and one way to ensure this happens correctly is to setup service dependencies on your windows applications server.

Let’s first review what depends on what and why.

The services that need to come up are in order:

  1. ADLDS
  2. Lawson Environment
  3. IBM Webshphere Cell Manager (Optional)
  4. IBM Websphere Node Agent
  5. IBM Websphere Application Server
  6. Web server (IIS)

Obviously, since all the authentication work happens through ADLDS, it makes sense that it would be the services to come up first. And since ADLDS has it’s own set of dependencies, we don’t need to create new ones there.

Next we setup a dependencies for the Lawson Environment Service to depend on ADLDS.

To do this, bring up the services window (Start-> Run-> services.msc).

Right click on your ADLDS service and note the service name.

Right Click on your Lawson Environment Service and note the service name.

Now bring up a cmd prompt as administrator and type in the following command:

sc config [service name] depend= <Dependencies(separated by / (forward slash))>

Note: There is a space after the equals sign, and there is not one before it.

Warning: depend= parameter will overwrite existing dependencies list, not append. So for example, if ServiceA already depends on ServiceB and ServiceC, if you run depend= ServiceD, ServiceA will now depend only on ServiceD.

Example:

sc config laserv-prod depend= ADAM_ProdInfor10ADLDS

In the above example, my Lawson environment service is called “laserv-prod” and my ADLDS service is called: “ADAM_ProdInfor10ADLDS”.

Once you hit enter, a message should appear that says: “[SC] ChangeServiceConfig SUCCESS”

You have now setup a dependency for the Lawson Environment service to depend on ADLDS. You can confirm this by checking the service properties:

How to setup dependencies for Lawson services_1

Now you can continue with the rest of the services and setup dependencies as you go. Keep in mind that the Cell manager is really an optional service and you may not want it running all the time, so you can avoid that dependency if you like.

Next, you’ll want to change all the services named above to be automatic. We usually don’t setup any recovery options as they can lead to some unintended results.

In the end, your Web Server’s dependencies should look similar to this:

How to setup dependencies for Lawson services_2