You are quite correct. Support out of hours rarely requires changes to
source/objects. Normally, the support done is to keep end of day
processes moving forward. Keeping an emergency copy of ADTS for those
few times where source needs to be changed out of hours sounds like a
good solution.
Thankyou.
John
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Monday, 11 February 2008 10:03 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSociety Fireside Chat recording available?
John, I'm really not certain what the issues would be surrounding Citrix
and WDSCi. I'm not well versed in how Citrix manages the multiple
sessions. The two things I would worry about is system load and
graphics performance over the network.
I can tell you that with enough horsepower I have successfully run
multiple copies of WDSC at the same time - in fact, on my new dual-core
machine I can have multiple copies of WDSC and it doesn't even breathe
hard - and the new RDi should be lighter weight than my full-blown
WDSC. I can also tell you that I have run WDSC over a VNC connection.
It's not particularly peppy, but it's functional, and that's with a
freeware communications package. I would hope that Citrix has a better
algorithm for compressing and transmitting graphics. In general, I
would say that if you can run Office over Citrix, I would think you
ought to be able to run WDSC.
Another question is this: how often do your developers need to do off
hours work (remember, this is editing source and compiling)? I suggest
you always have a copy of ADTS for emergencies (and we've asked IBM to
make sure that's the case even if all user seats are moved to RDi -
there are times when you may need PDM/SEU in an emergency). If it's the
exception rather than the rule, you can use that emergency copy of
ADTS. You might even have one or two extra licenses available for
off-hours work. It's not like the move is necessarily all or nothing.
But to avoid the move to RDi for your regular job because you
occasionally need to use ADTS off hours, that's an argument that really
doesn't hold water. In my opinion, of course <grin>.
Joe
Hi Joe,
I have recently subscribed to WDSCI-L and have read your comments with
great interest (in particular your comments about moving all iseries
developers from ADTS across to WDSCi (RDi/RDi-SOA in future).
Our development team has been using WDSCi for about 4 years but very
few
members (out of approx. 40) have made the transition. One of the
excuses
has been that we support our systems outside business hours using
citrix
connection and we only have ADTS available via citrix. I have tried to
follow-up on the internet on how we could get WDSCi running out of
citrix but have not been able to find anything positive (all articles
I
have found seem to indicate this is not possible).
Do you have any ideas on using WDSCi via citrix?
midrange.com
