I have several customers distributing this product in the way Justin
describes, and it's almost too easy. Citrix customers just update the
image and others just update the network share.

For those user who put this product on the phone/pad device/laptop/device
du jour..... You will have to distribute the .jar file to them when it
changes but that's the only critical part that needs to be distributed.

Yes, it runs on an android phone, iPad, iPhone, Mac Laptops, and my
SurfacePro3 with no issues whatsoever. (screens a little small on the
phone for my old eyes) but as long as the device has Java, it's good to
go. Same set of files, with no discernible difference in performance or

IBM has promised to get the licensing bit fixed so you don't have to run
the ESS version first then the updated version, but it has not come out
yet. The technical bits are easy, IBM Legal approving it, that's hard.

On Wed, Sep 30, 2015 at 10:09 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>

I keep both versions (ESS & FTP) on a NetServer share. For a new PC, I
run the ESS version once to set the license. Then I create a local
workstation file (.HOD) and set it to open-with the FTP version of the
executable. For updates, I just overwrite the FTP version on the
NetServer. Connected users don't even see a hiccup.

-----Original Message-----
From: Argia Sbolenfi [mailto:asbole@xxxxxxxxx]
Sent: Tuesday, September 29, 2015 6:45 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: iAccess client solutions (Java): need clarification on
installation and upgrade

Hello. I'm in the process to introduce the new Java i Access in our
I can't understand how one is supposed to distribute the latest version to

Let's skip for now the confusing version / build numbering scheme of this
There's an initial package downloadable on the ESS web site.
Also, you can get updates from a public FTP site.
Instruction say that in order to upgrade the product, you just overwrite
the original installation with the files from the upgraded version.
Now let's suppose that I've a new PC, where no user has logged on before.
First, I unpack the initial package; then, I overwrite it with the latest
one from the FTP site.
Running the program for the first time, after accepting the EULA, I get a
MSGGEN048 error that says that the trial period has expired!
The only way I've found to run this program, is to execute for the first
time an untouched "initial" ESS version. Then I can run the updated version.
I've also noticed that various flags are written in
Moreover, I think that running for the first time the public FTP version
begins an evaluation period, so this is not the way to go.

I'm puzzled: what is the correct way to distribute the latest version of
this product to users?
Should I write a script that, if the user never executed the program
before, runs the ESS version, otherwise runs the updated version?
Sounds a bit silly.
At the moment, I'm distributing the initial ESS version, it works quite

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].