Posts

Getting the version of important Lawson interfaces

Interface versions are important when debugging an issue. This way you can check whether or not a patch exists that addresses the issue or if Infor is assisting you with the problem and needs a starting point.

 

Some of the most common ones needed are:

  • Lawson System Foundation (ILSF)
  • Security Jar files (secLS)
  • Infor Landmark (ILMRK)
  • Distributed Security Package (DSP)

 

Its quite simple as long as you have access to LID, Infor Security Services (cloud) and Landmark Command Line (cloud) access.

 

Starting with LID:

  • For Lawson System Foundation (ILSF) version run command: univver lawsec.jar
  • For Security Jar files (secLS), change directory to %GENDIR%/java/thirdparty and run this command: univver secLS.jar
  • For Distributed Security Package (DSP), change directory to %LAWDIR%/lss/system
    • Type command: lashow install.log
    • This will display the inside of the file, you can copy the version or export as needed.

Infor Security Services (ISS):

  • Click the lower case “i” on the upper right-hand corner of the page

Landmark Command Line (ILMRK):

  • Simply type univver -V

 

That’s all there is to it!

 

Best Way to Document Your Interfaces

Is documenting your interfaces challenging? Do you find yourself confused as to what you should focus on and how to best format things? Do you feel that the work you’re creating is not going to get used and you are not sure where to store it all? Join our webinar to get answers to all those questions and learn a new way to create accurate, valuable and well written documentation for your team. We’re going to cover a host of topics including:

  • How documentation of your interfaces will impact things
  • What you should include in your interface documentation
  • How to effectively create a document that has value to the organization
  • How to store your documents for best value, retention, correctness, and accountability
  • Q/A