In WebSphere Application Server 4.0 there is no way to
change the system or sysplex name used in a WebSphere Application Server
runtime environment. If these names must be changed because of your
disaster recovery procedures, the recommended approach is to use the
prepare for Cold Start process, if this is viable in your scenario.
If the prepare for Cold Start process is not acceptable, the
only other alternatives are:
- Have a recovery system with identical names to the
original WebSphere Application Server system
or
- Reinstall WebSphere Application Server onto your recovery
system with the new system and/or SYSPLEX and/or DB2 subsystem names.
Another scenario starts with the assumption that, as part of the disaster
recovery, you have the same system, sysplex and DB2 subsystem names as on
the original WebSphere Application Server system. If the daemon IP address
is also the same, you should be able to recover your WebSphere Application
Server system using all of the backed-up data described in the document
"Operations and Administration" Chapter 5, "WebSphere for z/OS backup
guidelines and procedures."
All of the backups must be the same snapshot of time as in your
WebSphere Application Server environment. If this is not the case, your
disaster recovery plan must redefine the servers, then redeploy the
applications onto the newly-defined servers.
|