If you have every had to figure out what version of a certain Java executable you have you will appreciate this simple trick. Simply point your browser to this url:
Example:
This example displays the version of the ios.jar file as shown below.
In the above case the version of ios.jar file on the server is 9.0.1.11.521.
This information can be very helpful when working with Infor support to determine if patches are needed.
During an upgrade, re-pointing all your LBI reports to your new database may seem like a daunting task. Never fear! You don’t have to do it manually (at least not all of them). Here are the steps to overwrite your data sources using a SQL update query:
So your client has scheduled LBI reports that they rely on and for whatever reason, it didn’t run on the day it was scheduled for. Now, it’s Monday and it’s too late to run the report manually! Furthermore, the client wants the report to be available in the LBI “History” section of the report viewer for later reference.
We click this past scheduled report…
Oh No! Our Revenue Check Daily – MRN didn’t run properly!
First thing we need to do is start Crystal Report and open the latest instance of our editable report. For our client, this is located on their LBI server in: D:\LawsonDocuments\60_Revenue Check Daily – MRN\
Once your report is open, either enter the date parameters for the report (if it takes parameters) or hard code the dates in the report to reflect the day it was supposed to grab data from. Don’t forget to set the front-end display dates that the end-user will see.
Once the data is verified by the end-user, export the report in crystal format.
Select a directory and name you want your crystal report to export.
Now, find the directory of the instance that didn’t run properly or simply does not exist.
For me, this was D:\LawsonDocuments\60_Revenue Check Daily – MRN\Instances\2016-04-08_1606\
If a crystal report exists in that directory, delete or move it elsewhere.
Now copy in your exported LBI report that you edited and rename it to the exact name of the report + “_instance number”.
Ours is Revenue Check Daily – MRN + _1606 so Revenue Check Daily – MRN_1606
The instance number can be found in the folder name that is generated by LBI.
That’s it! You can now go back to LBI Report Viewer and click on that report that errored out earlier.
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:
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:
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:
