Walter - we had to deploy the HTML solution. Java versioning was an issue and the applet does not work consistently. I would look to upgrading to at least 10.2.6 or higher if you are not already there and using the web.

Thank you for the reply! The html solution does seem to be the best option but we're hesitant because we'd have to upgrade our landmark, ltm, websphere and java (java on the S3 side as well). Word from Infor is that when you go to landmark 10.1.1.x the websphere and java for both landmark and S3 have to be the same and java 1.7 is required. You confirmed our concerns about sending people to an applet though.

All of those assessments are correct - you'll need to go to Java1.7, websphere 8.5.5 and upgrade to 10.1.1.x/Tm10.2.x at minimum for a functional HTML5 interface. We're deploying the Landmark HTML5 ESS/MSS (as we call it) now, and it's quite buggy. 

Configurations are inconsistently passed between the HTML5 UI and the Rich Client app config console, and it's very all or nothing in regard to restricting certain functionality. 

That being said, it's very promising, and if you customize the HomePages.zip file it can actually be very pleasant looking. But it's definitely got it's rough edges :)

 

Another option you may want to look into is deploying the rich client via citrix. We do that, and it meets the needs for most users.

 

Peter O, just wondering how's your experience with LTM ESS on HTML 5 now, is it still buggy? We are using the java web applet which is rich client and java issue and slow page loading is the problem. Can you share how is the performance and if there any tweak you did. thanks

Hi folks
I am wondering the same. My org is going to upgrade now to lmrk runtime 10.1.1.36 and ltm v11. Looking forward to use web UI as rich client is disappointing at times on the performance. Any feedback would be highly appreciated

We found that the LTM web applet is much slower to log in but faster to navigate between pages and function than HTML5. The HTML5 client in older browsers could take 20 seconds to load each screen. HTML5 seems to be closer to acceptable performance if browsers are current. In Mingle/Citrix both are slower than a direct link. Our Citrix load has to be very light to keep acceptable performance. No clear winner yet.

To follow up on this thread - we launched in January with the applet. I set up a simple html redirect page that sat in the S3 portal directory (requiring a login and allowing sessions to pass between systems). The Java problems soon became an issue for our client services folks so we quickly upgraded and developed the HTML5 interface, rolling it out to production this last week. Other than IE8/9 problems it has been a success and the old browsers should disappear relatively soon. We've found it to be much faster than the applet and easier for employees to navigate. Adding the s3 emss paycheck links as part of the top menu and then having them load inside the iframe gives it all a very uniform look. Our Citrix guys wouldn't touch the applet but they did add the html5 which gives us compatibility when needed. No 100% solution but I'm glad to be rid of the Java problems!

Hi All,
Our Organization has also decided to move to the HTML5 Interface. We are currently using Richclient with Landmark 10.1.1.35 and LTM v11.14. My question to you is how you ended up configuring the HTML 5 site to look the way you wanted? Did you update the EAR file or did you use homepages instead? I saw a comment from Peter O about customizing the Homepage.zip file but I did not see that as available on my end. Just trying to figure out the best option for updating the look and feel of the web UI.

We didn't get nuts with the style sheet but what I did was change the persistent menu links via the LPL for "LCMEmployeeMenu" (via the customization console in landmark).

 

As far as their stock look (all white, some grey) we just went with it, though that can be changed via the CSS in the site directory : /ENV/src/ltm/modules/hr/webapps/EmployeeSelfService/src

I did add the S3 links for payroll data (pay checks, direct deposit, payment calculator, withholdings).

Only problem was when clicked, the entire page was replaced with the S3 link, losing the persistent menu, logout, etc.

To get everything under the menu, I added some javascript to the welcome.html page that parses url parameters and pass what page I want to go to, then replace the innerHTML of the class 'inforScrollableArea' with an iframe that loads the S3 page (the iframe gets you a scroll bar in the sub content). Then the actual link is a link to the HTML5 EMSS with the appropriate parameter.

 

To make it all "live" you redeploy it via : enterprise app  hcmapp