×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
For our upcoming Disaster Recovery test we want to activate WebSphere
(& other Webbish things) on a DR machine.
In order to simplify the loading of the DR machine, and subsequent
testing, we want to modify the configuration on our live machine as
follows:
- Add the IP address that will be used during the test to the live
machine configuration. AFAIK, this should be as simple as adding
another interface to an existing TCP/IP comm line.
- Patch any 'Webbish' applications to allow access via the 'normal'
and 'alternate' IP addresses
== HTTP servers
== WebSphere (v6) applications
==== I found reference to running a WebSphere address change utility
if we want to change the IP address it responds to, but no mention of
how to -add- a 2nd address
== Client Access &c
== ?? any other things.
By adding the alternate address to our live system we should be able
to connect a test configuration locally and try things out before The
Big Day. The test should then be a 'simple' matter of duplicating
our work at the disaster recovery site.
I've poked at The Internet under several different searches to try
and find out what needs to be done, but nothing seems to be related
to what we're after. Can anyone point me in the right direction?
Thanks!
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Storage pools and QHTTPSVR and QUSRWRK subsystems, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.