Re: [EXTERNAL] Re: Connecting with an Azure server

No idea, I didn't set it up.

Our data centers are in a different state, nor am I on the team that
handles that part of the AWS side.

Charles

On Thu, Feb 3, 2022 at 12:42 PM Alan Shore via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Thanks for your reply Charles
We have a meeting, tomorrow, to discuss this problem we have
I will make sure to mention this

Would you mind saying how long it took to get this up and running?

Alan Shore
Solutions Architect
IT Supply Chain Execution

[NHScsignaturelogo]

60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx

‘If you're going through hell, keep going.’
Winston Churchill

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Charles Wilt
Sent: Thursday, February 3, 2022 2:30 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] Re: Connecting with an Azure server

You might want to ask about Azure ExpressRoute
https://azure.microsoft.com/en-us/services/expressroute/#overview<
https://azure.microsoft.com/en-us/services/expressroute/#overview>

Use Azure ExpressRoute to create private connections between Azure
datacenters and infrastructure on your premises or in a colocation
environment. ExpressRoute connections don't go over the public internet,
and they offer more reliability, faster speeds, and lower latencies than
typical internet connections. In some cases, using ExpressRoute connections
to transfer data between on-premises systems and Azure can give you
significant cost benefits.


We use the AWS equivalent(?) called Direct Connect.

Charles

On Thu, Feb 3, 2022 at 9:53 AM Alan Shore via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
wrote:

Hi John
The way that you are describing it - I am definitely wrong in my

discussion

The web service call is FROM the Azure server TO the iSeries
Strange, no one has pointed out my mistake before today


Alan Shore
Solutions Architect
IT Supply Chain Execution



60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx<mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx>

‘If you're going through hell, keep going.’
Winston Churchill


-----Original Message-----
From: John Yeung [mailto:gallium.arsenide@xxxxxxxxx]
Sent: Wednesday, February 2, 2022 9:30 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx

<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>

Cc: Alan Shore <ashore@xxxxxxxx<mailto:ashore@xxxxxxxx>>
Subject: [EXTERNAL] Re: Connecting with an Azure server

Alan,

One thing that I find confusing is your use of the term "consume". It
seems to me that you are using it either inconsistently or backwards.

In the phrase "consume a web service", it is the client who is doing the
consuming. Whichever party is initiating a request is the client.
Whichever party is listening for incoming requests and sending responses
back is the server. The server is the one *providing* the web service;

the

client is the one *consuming* it.

If you aren't confident that you can keep it straight, I recommend you
just talk in terms of client versus server, or initiating requests versus
responding to requests. That will reduce the chance for confusion when
you're talking with other people.

John Y.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:

MIDRANGE-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<

https://lists.midrange.com/mailman/listinfo/midrange-l>

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:

MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<

https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:

support@xxxxxxxxxxxxxxxxxxxx> for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com