[EXTERNAL]Re: Omnis & Azure

Brian A O'Sullivan brian.a.o-sullivan at axalta.com
Tue Mar 16 19:04:46 UTC 2021


Thanks, Alan & Andrew for your replies! I should provide a bit more context- this is a "thick" client application that connects to an Oracle database on a separate server; no Omnis-native DF1. The Omnis runtime and library files are all installed on the Azure app-servers. Users connect using Microsoft's WVD-Remote-App service. Users see the app as a double-clickable icon in the WVD service on their computer. Launching the app establishes the WVD connection, opening Omnis & our library on the remote server in its own session window on the user's computer.

Overall the WVD service has worked pretty reliably over the past 6 months in our production environment (after 4 months of testing). The app-launch is much simpler for our end-users compared to our old Citrix environment. But as time goes on, the environment is less stable with increasingly long launch times. The WVD app-servers get rebooted on weekends to help with stability (still find it crazy that unix servers can go without reboot for years, but it's considered standard practice to reboot Windows servers with frequency).

Several years back when our company was beginning its venture into "the cloud", my group lobbied for AWS, but the Microsoft crowd won out. I've heard nothing but good things about AWS! Being in a corporate setting I don't have direct control over the Azure services - have to live with what the IT-infrastructure specialists provide. These WVD app-servers are persistent, they don't spin-up on demand. I suspect we're using basic-level servers, so trying to gather some "real life" data to make a case for upgrading to a higher class of Azure server.


Brian A. O'Sullivan


Sensitivity: Business Internal

-----Original Message-----
From: omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> On Behalf Of Andrew Stolarz
Sent: Tuesday, March 16, 2021 2:17 PM
To: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
Subject: [EXTERNAL]Re: Omnis & Azure

Brian,

We strictly use Amazon Ec2 and dont have the issues you describe, in fact it's been a bullet proof type setup over the years.

However, we also have clients that deploy on their own cloud environments, including Azure and im not aware of any issues.

Have you tried pinging the server before trying to establish a connection from your app to see if it's available ? sounds to me like some kind of network issue.

I'm not familiar with WVD, but the similar offering from Amazon I believe is WorkSpaces, and I know you have it setup so that the instance is "on demand" rather than persistent (to save $$), then it could very well be that all the instance services are not fully available at the time of the app launch attempt. Doing a ping to the server should validate that.


Andrew


On Tue, Mar 16, 2021 at 1:31 PM Brian A O'Sullivan via omnisdev-en < omnisdev-en at lists.omnis-dev.com> wrote:

> Wondering if anyone else is hosting Omnis applications in Microsoft
> Azure via WVD?
>
> My team's Omnis apps had been hosted via Citrix for many years, but
> recently moved to WVD since our company is standardizing so much on
> MS-Azure. Things worked pretty well at first, but we've found the
> environment has become less stable over time. Most of the problems we
> are seeing are in launching the application - sometimes connections
> simply don't complete, mostly though it just takes a looong time to open.
> Wondering what types of server class others are using?
>
> Brian O'Sullivan
> Axalta Coating Systems, USA
>
>
>
> Sensitivity: Business Internal
>
>
> This communication is for use by the intended recipient and contains
> information that may be Privileged, confidential or copyrighted under
> applicable law. If you are not the intended recipient, you are hereby
> formally notified that any use, copying or distribution of this
> e-mail, in whole or in part, is strictly prohibited. Please notify the
> sender by return e-mail and delete this e-mail from your system.
> Unless explicitly and conspicuously designated as "E-Contract
> Intended", this e-mail does not constitute a contract offer, a
> contract amendment, or an acceptance of a contract offer. This e-mail
> does not constitute a consent to the use of sender's contact
> information for direct marketing purposes or for transfers of data to
> third parties. For more information regarding how we collect and use
> your personal data, and any related rights you may have, please review
> our Privacy Statement. <
> https://www.axalta.com/corporate/en_US/privacy.html>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com Start a
> new message -> mailto:omnisdev-en at lists.omnis-dev.com
>
_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com


This communication is for use by the intended recipient and contains information that may be Privileged, confidential or copyrighted under applicable law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-mail and delete this e-mail from your system. Unless explicitly and conspicuously designated as "E-Contract Intended", this e-mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-mail does not constitute a consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. For more information regarding how we collect and use your personal data, and any related rights you may have, please review our Privacy Statement. <https://www.axalta.com/corporate/en_US/privacy.html>


More information about the omnisdev-en mailing list