[THIN] Re: Application Availability
- From: "Shonk, Joe - Perot" <JShonk@xxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 7 May 2004 08:32:02 -0700
For several reasons:
A dept/project buy a set of servers to deploy a single application
Healthcare apps are very flaky. If an application takes down a
server, only that application is down. It does not affect other critical
systems
Application limitations only allow 1 instance of whatever (database,
group etc). There are many hospitals
Application loads. Single applications can have 200-300 concurrent
users a piece.
Security/HIPAA requirements. Finance doesn't need access to
clinical apps and doctors do not need access finance applications.
Compatibility issues with multiple apps on a server (again see the
flaky line above)
Application maintenance. Different application sets have different
maintenance schedules. Taking one application offline and booting off the
users should not affect access to other applications. (Remember this is a
24/7 shop)
Oh, and I forgot... The number #1 reason: Politics
Never said it was perfect,
Joe
-----Original Message-----
From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
Sent: Friday, May 07, 2004 1:26 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Application Availability
Comments inline...
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Shonk, Joe - Perot
> Sent: 06 May 2004 17:36
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Application Availability
>
> Why not use a custom load evaluator for the custom app? Then
> script a logoff to force the users out of the application?
> If the application set is isolated on it's own server then a
> scheduled logoff ica-tcp is all that is needed.
Why restrict yourself to only having an application on one server - this
sort of thing (logging off user sessions, based on the published app
they are running) then means you only take an application down, and can
balance it, and have it benefit from the redundancy of being able to run
over more than one server.
> -----Original Message-----
> From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
> Sent: Thursday, May 06, 2004 7:49 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Application Availability
>
> I'd say you'd have to get busy with some custom scripting to
> pull that off (you'll likely need the Citrix SDK).
>
> Unless there's something truly magical in the CMC that I've
> not encountered, or Metaframe v3 is truly whizz-bang.
>
> Neil
>
> > -----Original Message-----
> > From: thin-bounce@xxxxxxxxxxxxx
> > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Armstrong, Robert
> > Sent: 06 May 2004 15:33
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Application Availability
> >
> > Greetings,
> >
> > Could someone please tell me how I can implement restrictions
> > (preferably on automatic scheduling) on when certain
> > published applications are available to users. For example,
> > I have an application that I want to take offline between
> > 8:00 PM and 11:00 PM every night. I want any users who are
> > in the application at 8:00 PM to be forced out of the
> > application and then have the application unavailable until
> > 11:00 PM. I am running Metaframe XPe FR2 on Windows 2000 Server.
> >
> > Any advice would be greatly appreciated.
***********************************************
This e-mail and its attachments are confidential
and are intended for the above named recipient
only. If this has come to you in error, please
notify the sender immediately and delete this
e-mail from your system.
You must take no action based on this, nor must
you copy or disclose it or any part of its contents
to any person or organisation.
Statements and opinions contained in this email may
not necessarily represent those of Littlewoods.
Please note that e-mail communications may be monitored.
The registered office of Littlewoods Limited and its
subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB.
Registered number of Littlewoods Limited is 262152.
************************************************
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
