Jack,
Your correct for an update simply put the new files on top of the old ones,
but it's easier than that.
The only file you really need to drop on top of the older one is the jar
file.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack
Callahan
Sent: Tuesday, May 15, 2018 2:14 PM
To: midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: RE: ACS deployment questions
1) Anyone using Java Web Start?
http://www.redbooks.ibm.com/abstracts/redp5304.html?Open
Not here.
2) Are you running locally or from a central location?
Both. As currently designed, you can't server multiple users with different
functional requirements from a single location.
Developers locally with access to all ACS functions, java installed locally
for our developers (tough to run RDi without it).
General users from central location, configured to only have two 5250
display stations and 1 printer station, plus limited spool file access. jvm
installed in central location so that no users have java locally. Modified
the install script to create a shortcut on each users desktop that launches
all the sessions with a single doubleclick (the shipped default install
script creates a shortcut that launches the ACS session manager). 5250
configs stored on network share for each user. Install footprint is two
shortcuts, an icon ,and the install log.
Might be creating a separate central location for our users with a different
usage profile (adding file transfer, ...)
3) If central location, from a network share server or from IFS?
Windows network share for the general population
4) If central location, does each ACS user need a mapped drive to the
remote location (network share server or IFS)?
That's how we do it, used an existing Windows share that all users have
access.
Might not be the only way
5) If central location, when a new version is available, is there a
way to test the new version before deploying to all users?
From the info I'm reading, the applying product updates is done by
extracting the contents of a new version of the product on top of the
existing product files.
Generally have the developer staff test the updated product before
upgrading the end users.
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
