IPA Designer log in woes

Since v11, I've noticed that IPD behaves the same way the HTML spaces do after a server reboot - ie "Your application is warming up...please refresh". This is ok in a browser because to can wait a few seconds and refresh the browser and all is ok. But this happens in IPD too and it forces you close the designer, re-open, log in, repeat a few times and you are in. Is anyone else experiencing this? Is there another way around this? Thanks! Chris

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

robert-canham

We ran into this as well. Our installer found a way to get Landmark to warm up right away rather than waiting for the first user to hit it.

This line has to be added to the environment.properties file:

com.lawson.ServletStartupListener.enableStartup=true

Clinical Bridge - Customer Day Webinar_20200529 Distribution.pdf

Simple steps to create Inherited Source.doc

russel-cornelson

IPA Support Approved.

Adding that line to LASYSDIR/environment.properties makes the system automatically load applications into WebSphere whenever it starts up after a stop/crash. It saves your end users from seeing the "application has restarted and is warming up" messages.

All comments

robert-canham

We ran into this as well. Our installer found a way to get Landmark to warm up right away rather than waiting for the first user to hit it.

This line has to be added to the environment.properties file:

com.lawson.ServletStartupListener.enableStartup=true

Clinical Bridge - Customer Day Webinar_20200529 Distribution.pdf

Simple steps to create Inherited Source.doc

cmcconke

From my understanding, this file is used when we install or update landmark, not on an ongoing basis. do you know where in WebSphere where we can update this now that we have already updated landmark.

robert-canham

As far as I know, this is all we had to do and it references it on startup.

russel-cornelson

chris-mccullough

This is awesome. Thank you all. Russ - before I recommend to team, they will ask

1. any repercussions to adding this?

2. Is it easily backed out if something goes wrong?

3. Does it matter where the line is added to the file or can it be anywhere?

Thank you.

cmcconke

thanks. updated our test systems and it worked

bella-fritz

Russel, did you answer the questions entered by 928670? We would be interested in the answers.

1. any repercussions to adding this?

2. Is it easily backed out if something goes wrong?

3. Does it matter where the line is added to the file or can it be anywhere?

Thank you

chris-mccullough

Note, I did put this into place in our test, train dev systsm..so far, so good. Easily backed out as its just one line. Put it anywhere. Hope this helps.

Landmark technology and architecture Overview

russel-cornelson

Sorry for the delay in getting back to you.

1. Is there any repercussions to adding this?

The only repercussion you should get is a positive one, people should stop complaining to administrators about the "application is warming up message"

2. Is it easily backed out if something goes wrong?

Very, it's as simple as removing the line from environment.properties. FYI: I've had this set on my system for as long as I have had my 2012 server without a problem.

3. Does it matter where the line is added to the file or can it be anywhere?

It does not matter where the line is added, but my experience tells me when you are adding a setting that is not default put it somewhere easy to find and use comments to identify the area as something modified/customized. Or even a note as to where you found the information suggestion to add it.

Copyright © 2025 Infor. All rights reserved.