Portal 10.1 Bookmarks missing

Hello! We just upgraded portal in test to 10.1. I have added security and the bookmarks is not displaying for them to do Reqs, Shopping, line Status, ect.
What am I missing?

Thank

Starr

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Accepted answers

All comments

unknown

Portal Role layout locks, perhaps? Or the users need to add them to their layout manually?

russel-cornelson

When you make a call to http(s)://lsfserver/lawson/portal, you get routed to authentication, and are then redirected to /lawson/portal/logondone.htm.
/lawson/portal/logondone.htm has javaScript inside it that calls http(s)://lsfserver/Servlet/Profile
- this reads RM information to check if WFUSER=1 in Lawson Security.
If the user's RM Info is WFUSER=1; it uses the LSF Database to directly connect to LOGAN database and query the WFEVTSERV table which is also visible inside /bpm/menu.do's Event Server page.
Servlet Profile uses the IP Address listed for the RMI server also running on the LSF server; to connect to the RMI Service for the purpose of calling "getBookmarksURL"
RMI reads LAWDIR/system/bpm.properties: if useLPS=true in that file it will make a call to the Landmark Server. If it is false it will check LOGAN database. (Most systems should be useLPS=true unless you are on very old LSF code pre-landmark.
Assuming you are Landmark IPA; RMI uses GENDIR/bpm/jar files to connect to the Landmark System and request "getBookmarkURLs" from the Landmark system.
Landmark gets the FQDN for the inbasket from Landmark Security <DA>.LPA.LPA security service's FQDN property and adds to it the settings from the user's PfiUserProfile. This result is returned to RMI, which returns it to Servlet/Profile and portal code renders the bookmark. (index1_concat.js code accepts the response and renders the bookmark)

From that you can see there are a few failure points. To troubleshoot these efficiently I simply run "http(s)://lsfserver/Servlet/Profile" from the browser and login as the user who can't see the bookmark.

In the XML response you are looking for...
<INBASKET>
<LPA>
<Application id="pd">
<DETAILURL> bookmark link here</DETAILURL>
</Application>
</LPA>
</INBASKET>
If you see <INBASKET>, your user is WFUSER=1
If you see <LPA>, bpm.properties is useLPS=true
- if you don't see <LPA> run "pfserv config lps" and add useLPS=Y/true when asked
If you see <LPA/> << notice this tag is open with a close tag at the end
- this means you are not successfully communicating between LSF's RMI server and Landmark
  - verify grid is running
  - verify at the application of the last patch the LPSClientJars aka GENDIR/bpm/jar files were updated after the patch. These files come FROM the landmark server and are moved over to LSF for this communication.
    - packageLPSClientJars.bat command creates new files from the LMRK environment code and saves LPSCLientJars.jar in LASYSDIR/LPS directory. Move them to LSF; remove the files currently in GENDIR/bpm/jar and unpack this LPSClientJars.jar file into that directory. jar -xvf LPSClientJars.jar
    - NOTE: do not leave LPSCLientJars.jar in GENDIR/bpm/jar after unpacking the files it contains.
  - if grid is running, and you already updated GENDIR/bpm/jars ... then the issue is likely the user/password for the LPSUser and LPSPassword. We had versions where LPSUser needed to equal "identity" and some that needed to equal "actor.
    - identity = lawson@infor.com
    - actor = lawson
If there is an error in the <LPA> error </LPA> ... post it here.

NOTE: Lawson System Foundation CACHES the servlet/profile results; so if you do a restart of the system and LSF comes up before Landmark. A user could try logging in before Landmark is up and running; this would result in an empty <LPA/> tag ... after landmark came up other users are working fine.

In this case just perform a lawson IOS Cache Refresh, and verify the user can now see their bookmark

Copyright © 2025 Infor. All rights reserved.