RE: Re[2]: Mirroring Solution - HTTP Configurations

Yes, IWS (and other WebSphere servers) have configurations held in places I have not delved into. We are replacing our IWS instances with RPG CGI programs based on Scott Klement's "roll your own" examples so I have no real need to dig into it. Perhaps a call to IBM to locate those files so they can be replicated?

I don't have any iCluster customers that run anything more than basic web servers so I've not dealt with the application server replication set ups.

--
Jim Oberholtzer
Agile Technology Architects

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

Thanks Jim and Rob,

Jim: You were correct, that file QUSRSYS/QATMHINSTC does hold the baseline configs for the web servers and once replicated, I started the admin instance on the target side and the main panel does show the servers. It does not show the application server that serves up our IWS web services so that info must be kept someplace else, I presume. Or, perhaps I need to start the server on the other side and see if it recognizes that it has and application server linked to it. I'll need to investigate that a bit more.

Rob: You're correct on the IPs too. Our servers are not bound to any specific IPs but in a failover/switchover situation, we'll swap IPs between the source and target so that whichever side is "live" holds the same LAN IP all the time. We have 2 IPs on both sides for LAN access with one as active and one as inactive and in a role swap, we'll swap those too so the primary side is always the same and the backup side is always the same.

Will keep you posted on what I find out with respect to the application servers too.

Thank you both!

------ Original Message ------
From: "Rob Berendt" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: 8/24/2021 5:50:35 PM
Subject: RE: Mirroring Solution - HTTP Configurations

Also keep in mind that the IP addresses may differ between your primary and your HA machine. If your machine supports multiple IP addresses and you "bind specific" to particular IP addresses you have to be careful what you replicate.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jim Oberholtzer
Sent: Tuesday, August 24, 2021 5:15 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Mirroring Solution - HTTP Configurations

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Then it’s likely the QATMHINSTC in QUSRSYS that needs to be replicated as well. If you check the job log when you try to start an instance, it’ll tell you (assuming /www is not locked by replication).

Some of my customers will manually replicate that file since it does not change except for http configuration.

Jim Oberholtzer
Agile Technology Architects

On Aug 24, 2021, at 3:16 PM, Brian <belstsrv@xxxxxxxxx> wrote:

e QATMHINSTC in QUSRSYS.

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