Quick Access report

 3 Replies
 1 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Chris Gawarecki
Advanced Member
Posts: 21
Advanced Member

Looking for a good way to see who has access Lawson Portal in the last x days. 

Nothing fancy, just date and user identifier. 

Ideally, would also have last Lawson form accessed.

My guesses where the data miht be:

A: database table?

B: Websphere (web) server logs

C: Timestates

 

Also I would ideally like the list ourside/without LSF up and running. If we're diagnosing a problem, LSD may not be available.

TTA

David Schronce
Basic Member
Posts: 6
Basic Member
I haven't dealt with this one in quite a while. The only way you'll get responses from anywhere in the database is if you have logging turned on. I don't believe you do. Next would be the websphere tables. Unless I be mistaken, you are running all your logins through an F5 which means that the logs all show exactly the same IP address for every and every transaction. Lastly, that comes to timestats. Once again that's going to be a loser for you. It does a wonderful job of showing you quantity of transactions, but no specifics on where they came from. Hate to be a Debbie Downer, but I don't believe any of those three will get you the information you're looking for. It just wasn't something that was built into Lawson. Good luck!
John Henley
Posts: 3359

Chris, you might need "LSD" cool 

Seriously, what LSF version are you on, and are you using "ISS" (Infor Security Service)?

Thanks for using the LawsonGuru.com forums!
John
Sal Serafino
Basic Member
Posts: 4
Basic Member

You can look for lines in the WebSphere IHS access log that contain UBOSET1. This line will be in the format:
client PC or name- - "GET /servlet/Router/Data/Erp?PROD=LOGAN&FILE=LOUSRBKOPT&FIELD=BOOK-MARK;&INDEX=UBOSET1&KEY=username&MAX=600&OUT=XML HTTP/1.1" 200 490

The "client PC or IP" will tell you what machine the request was made from and the "username" will tell you who logged in. As for how to find those entries depends on your OS (Windows find or UNIX grep), and you will likely need to edit the output to cull out lines you don't want. This is easier if your IHS logs are rotated. I rotate mine weekly, so they're not huge monsters and that makes it easy to work with. However, if I were to need to pull all logins going back 14 days, I would have to pull info from 3 logs and cull out the entries older than 14 days. This is not a simple "find exactly what I need without putting in any work" kind of thing, but it can be done.

There are no database entries in LSF with logins. This is all WebSphere logs, which will be accessible whether Lawson is running or not.