Re[4]: Mirroring Solution - HTTP Configurations -- MIDRANGE-L

Hi Jim,

You're correct, I do not want to mirror the admin server, but rather the data that tells it what other servers are installed and their properties.

I did set up mirroring /www which looks like it has the particulars for the various servers, but when accessing the target system's Admin server, those servers do not show up as being in existence.

We're using iCluster and they're looking in to this as well, but I was hoping someone here may know where the info is kept and perhaps already solved this one.

Thanks again!

------ Original Message ------
From: midrangel@xxxxxxxxxxxxxxxxx
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: 8/24/2021 3:32:53 PM
Subject: RE: Re[2]: Mirroring Solution - HTTP Configurations

When using application replication (IE: iCluster and Mimix and such) there
are quite a few places that should not be replicated. The *ADMIN server
comes to mind almost immediately, particularly if you want it running on
both sides.

I doubt the *ADMIN server replication is the part that is failing, my guess
is it's the /WWW directory (assuming that's where you keep the Apache
configurations) and the QATMHINSTC in QUSRSYS.

Maybe a review of what is being replicated and why is in order with your
vendor?

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brian
Sent: Tuesday, August 24, 2021 11:47 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re[2]: Mirroring Solution - HTTP Configurations

They're looking in to it too, but I thought the community may know better
where that info is stored.

To respond to some other comments too:
Right now we do not want any of the web servers starting on the other side
(other than Admin, that would be OK). But, I do want to see them if I log
on to the Admin web server on the target system. Then on failover, we'd
start them up.

It's more about getting the data needed for the Admin instance to see and
manage the servers. That seems to be what's missing and I am not sure were
that info is located at.

Thank you for the replies so far.

------ Original Message ------
From: "Steve McKay" <samckay1@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: 8/24/2021 12:36:20 PM
Subject: Re: Mirroring Solution - HTTP Configurations

Brian -

Your HA vendor should be more than able to help you with this.

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx

On Tue, Aug 24, 2021 at 11:10 AM Brian <belstsrv@xxxxxxxxx> wrote:

Hello,

We're currently testing some mirroring (HA) software and one of the
items we're trying to sort out is if we can mirror over our HTTP
configurations from one system to the other.

We use an Apache instance for some things and also an instance of
IWS for serving up data.

It looks like much (perhaps all) of the config for the actual
servers lives in:
/www

But, when launching the HTTP Admin instance on the target machine,
none of the servers from the Source side show up there. But, if you
try and create one of them with the same name, it says it already
exists (probably because the directory already exists on the Target

side).

The part it seems I'm missing is where the control/metadata is for
the Admin instance that tells it about the servers that are set up
and their general info.

Assuming what I want to do is possible, where would I find the info
at to make this work?

Thank you much!
--
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

--
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

--
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

--
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