Re: iAccess client solutions (Java): need clarification on installation and upgrade

Argia:

If you set the font, watermark, etc. on the base copy then everyone will
get the defaults. The local changes are saved on the local device.

If you get into the AcsConfig.properties file you can set a number of
defaults. The two I tend to use are:

com.ibm.iaccess.AcsBaseDirectory={PRODUCTDIR}

That makes the IBM folder show up in the product directory. That's were
all the customization is stored.

The other one is:

com.ibm.iaccess.ExcludeComps=KEYMAN,OPCONSOLE,HWCONSOLE

Now the user will NOT see the ops console, HMC, or key management. The
list of keywords for this parameter is :

Keywords used to disable functions are:
# DATAXFER - Data Transfer to/from IBM i
# EMULATOR - 5250 Display/Print emulation and 5250 Session Manager
# KEYMAN - SSL certificate management
# OPCONSOLE - Operations console and Virtual Control Panel
# RMTCMD - Remote Command (available from the command line)
# SPLF - Printer Output
# HWCONSOLE - Hardware management interface
# L1CPLUGIN - Navigator for i
# HMCPROBE - HMC Probe Utility

So you can see that you have a great amount of control over what the user
options are.

As to the licensing, IBM Legal is the roadblock, not technical. The fix is
done, but the Legal team has to approve it all before our friends in
Rochester can release it. Maybe soon?


On Wed, Sep 30, 2015 at 12:22 PM, Argia Sbolenfi <asbole@xxxxxxxxx> wrote:

This is weird and should be improved by IBM. Also, I think that these
settings are user-based, so if you have roaming profiles in Windows an user
has to run the ESS version only once, then he can use any pc with the
updated version on it. And probably what the ESS version does is just to
set some registry key in the user section of the registry, and this could
be simulated.. I'm just speculating
Il 30/Set/2015 17:09, "Justin Taylor" <JUSTIN@xxxxxxxxxxxxx> ha scritto:

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
organization.
I can't understand how one is supposed to distribute the latest version

to

users.

Let's skip for now the confusing version / build numbering scheme of this
product..
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
HKEY_CURRENT_USER\Software\JavaSoft\Prefs\com\ibm\iaccess\base.
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
well.

--
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 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.