Job timeout on mobile app

[Doug]

We're using the mobile app on handheld devices in a warehouse environment. Every now and then a device looses connection leaving the server job active. Sometimes these 'zombie jobs' end up holding record locks causing issues for other users. Is there any way to set a server side timeout value specific to the mobile app? I'd like these jobs to end after 30 minutes of inactivity. I don't want this value to affect desktop users accessing the system via a browser though. Their timeout value would need to be much longer. Thanks

[Scott Klement]

It doesn't differentiate between a mobile job and any other sort of job. As far as it knows, it's just an http request coming in over the network.

One possible solution is to set up a separate instance of Profound UI to use for mobile. You'd configure your mobile apps to use a different port, and configure the server on that port to use a different timeout.

Since Profound UI is licensed by the LPAR/Machine, having multiple instances on the same LPAR/Machine does not cost you anything.

[Doug]

Thanks Scott. That sounds like it could work for us.

Just so I understand, we'd need to do a fresh install of the product calling it let's say PROFOUND_M. It will install to a library and folders under that name and we'll change the URL on the mobile devices to point there.

So we'll need to manage two instances and replicate any customization to both I assume. Any other downsides to this approach?

[Scott Klement]

Hi Doug,

The only down side I can think of is that you have two areas to maintain the configuration and any special customizations. (Note that customized Rich Displays should work fine in both environments -- so in terms of "customizations" we'd be talking about things like images, CSS files, custom javascript files, etc. These could actually just be symlinked across the environments, so shouldn't be hard.)